[SOLVED] Problems with OpenGL

iCykres · 2025-02-17 10:29:23

Whenever I am running

glxinfo

I get the following error:

X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  156 (NV-GLX)
  Minor opcode of failed request:  6 ()
  Value in failed request:  0x0
  Serial number of failed request:  32
  Current serial number in output stream:  32

and I do not know how to proceed with this issue. I tried running

nvidia-xconfig

which resolved the issue but disabled the internal display of my laptop. I have a system with an Intel iGPU and a dedicated nVidia card.

Does anybody know what might cause this issue? Any help would be greatly appreciated.

Last edited by iCykres (2025-02-18 08:18:06)

V1del · 2025-02-17 16:04:17

Remove the config nvidia-xconfig generated and remove xf86-video-intel and read https://wiki.archlinux.org/title/PRIME# … er_offload

Which exact iGPU and dGPU are involved?

If the above didn't help post a xorg log and a journal

sudo journalctl -b | curl -F 'file=@-' 0x0.st
curl -F 'file=@-' 0x0.st < /var/log/Xorg.0.log

iCykres · 2025-02-17 18:38:24

V1del wrote:

Remove the config nvidia-xconfig generated and remove xf86-video-intel and read https://wiki.archlinux.org/title/PRIME# … er_offload

Performing these steps made the problem above go away. However, this lead to new problems. E.g. running anything with prime-run made the program render in a black window (internal one was fine). I then tried to follow the steps here https://wiki.archlinux.org/title/PRIME# … ack_screen, which also did not resolve the issue.

I now opted to use wayland instead.

Last edited by iCykres (2025-02-17 18:39:09)

seth · 2025-02-18 00:45:30

V1del wrote:

Which exact iGPU and dGPU are involved?
… post a xorg log and a journal
sudo journalctl -b | curl -F 'file=@-' 0x0.st
curl -F 'file=@-' 0x0.st < /var/log/Xorg.0.log

iCykres · 2025-02-18 08:17:25

Sorry, as it seems I was not verbose enough: The problem was xorg related and switching to wayland resolved the issue.

seth · 2025-02-18 08:23:20

No, the problem was you-related and there's a decent chance you're now running wayland in software emulation, but fine.

iCykres · 2025-02-18 08:34:07

The xorg related thing was definitely me-related. If you bring it up already, care to explain how to check?

seth · 2025-02-18 20:58:26

This depends on the specific compositor, a basic (but not 100% reliable) way would be to check "glxinfo -B" to see what makes it to the xwayland layer.

I'm btw. pointing this out because there just was that scenario the other day in https://bbs.archlinux.org/viewtopic.php?id=303416 where switching to wayland "fixed" problems w/ the nvidia driver by simply not using it or the GPU at all.

iCykres · 2025-02-18 22:01:21

Ok, I would actually be interested in seeing whether everything works correct, so here is journalctl -b: http://0x0.st/8btU.txt and I have an Intel iGPU and an nVidia dGPU (I have the nvidia-open drivers installed if this helps).

When running glxinfo I get:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) UHD Graphics 630 (CFL GT2) (0x3e9b)
    Version: 24.3.4
    Accelerated: yes
    Video memory: 15868MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.3.4-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.3.4-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.3.4-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

whereas prime-run glxinfo prints this:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 4096 MB
    Total available memory: 4096 MB
    Currently available dedicated video memory: 3418 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Quadro T2000/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 570.86.16
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 570.86.16
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 570.86.16
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

seth · 2025-02-18 22:47:05

The glxinfo looks fine.
You're actually running GDM on wayland (default) then log into an X11 gnome session and 25s later gnome on wayland.
There's a borderline pointless

Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (==) Using config file: "/etc/X11/xorg.conf"
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (==) Using config directory: "/etc/X11/xorg.conf.d"
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (==) ServerLayout "layout"
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (**) |-->Screen "intel" (0)
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (**) |   |-->Monitor "<default monitor>"
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (**) |   |-->Device "intel"
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (**) |   |-->GPUDevice "nvidia"
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (**) |   |-->GPUDevice "Device0"
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (==) No monitor specified for screen "intel".
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]:         Using a default monitor configuration.
Feb 18 22:42:21 nico /usr/lib/gdm-x-session[1589]: (**) |-->Inactive Device "nvidia"

to explicitly configure the default prime behavior.

If you have any issues w/ the setup add "nvidia_drm.modeset=1" to the kernel parameters to block the simpledrm device and restore the normal card order (electron/wayland is otr crashing for the reversed order)

gnome-notes crashes all the time as is common… and keyboxd has problems to initialize but those are off-topic concerns.

iCykres · 2025-02-19 09:52:16

I think modeset was already set to 1, as cat /sys/module/nvidia_drm/parameters/modeset returns Y as indicated here https://wiki.archlinux.org/title/NVIDIA … de_setting, but I still added it now.

I will get rid of the configuration file. Apart from that, I do not experience any other issues for now. Somehow I also realized that making the internal laptop screen the main one seems to resolve the issue with the black rendering on xorg, too, though I have no idea why.

seth · 2025-02-19 15:26:15

I think modeset was already set to 1

It's active by default, but that is not the same as the kernel parameter which will implicitly prevent a sythetic device from stepping in and causing the card order to be reversed (what apparently a bunch of clients cannot deal with)

making the internal laptop screen the main one

What *exactly* does that mean (this doesn't exist as universal concept, there's a "primary" output but it has limited meaning)

I suspect the effort (improperly) configured the system for reverse prime (running on the nvidia GPU and forwarding the framebuffer to the IGP for the eDP)

Arch Linux

#1 2025-02-17 10:29:23

[SOLVED] Problems with OpenGL

#2 2025-02-17 16:04:17

Re: [SOLVED] Problems with OpenGL

#3 2025-02-17 18:38:24

Re: [SOLVED] Problems with OpenGL

#4 2025-02-18 00:45:30

Re: [SOLVED] Problems with OpenGL

#5 2025-02-18 08:17:25

Re: [SOLVED] Problems with OpenGL

#6 2025-02-18 08:23:20

Re: [SOLVED] Problems with OpenGL

#7 2025-02-18 08:34:07

Re: [SOLVED] Problems with OpenGL

#8 2025-02-18 20:58:26

Re: [SOLVED] Problems with OpenGL

#9 2025-02-18 22:01:21

Re: [SOLVED] Problems with OpenGL

#10 2025-02-18 22:47:05

Re: [SOLVED] Problems with OpenGL

#11 2025-02-19 09:52:16

Re: [SOLVED] Problems with OpenGL

#12 2025-02-19 15:26:15

Re: [SOLVED] Problems with OpenGL

Board footer