Failed to load module "glxserver_nvidia"

PhotonX · 2020-08-21 12:25:32

Hi guys,

I stumbled upon a very rather strange problem. For some weeks now (worked flawlessly earlier), compositing and 3D is very slow, Compiz crashes on closing a window, animations are sluggish, Steam games only give 1FPS. However, on some boots the problem is not present. I have the impression that it is a race condition, since the working boots are those when a file system check is being executed.

For a broken boot, I see following output in my Xorg.0.log:

[     4.769] (II) Loading sub module "glxserver_nvidia"
[     4.769] (II) LoadModule: "glxserver_nvidia"
[     4.769] (WW) Warning, couldn't open module glxserver_nvidia
[     4.769] (EE) NVIDIA: Failed to load module "glxserver_nvidia" (module does not exist, 0)
[     4.769] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[     4.769] (EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
[     4.769] (EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
[     4.769] (EE) NVIDIA(0):     you continue to encounter problems, Please try
[     4.769] (EE) NVIDIA(0):     reinstalling the NVIDIA driver.

while for a working boot it looks much nicer:

[    91.421] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[...]
[    91.454] (II) Loading sub module "glxserver_nvidia"
[    91.454] (II) LoadModule: "glxserver_nvidia"
[    91.454] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[    91.511] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[    91.511] 	compiled for 1.6.99.901, module version = 1.0.0
[    91.511] 	Module class: X.Org Server Extension
[    91.512] (II) NVIDIA GLX Module  450.57  Sun Jul  5 14:43:44 UTC 2020

Note that the line with timestamp 91.421 is missing in the broken boot log.

I found some threads/reports with similar symptoms like https://bugs.archlinux.org/task/64465 and https://bbs.archlinux.org/viewtopic.php?pid=1816559 but somehow it looks like the problem disappeared by itself and none of the proposed fixes worked out. So I'm a bit puzzled about how to go from here...

Using nvidia-dkms with a GTX 670, everything up to date. Unfortunately, I don't remember exactly when the problem started appearing first, but it might be the nvidia driver update from 440 to 450, not sure though.

Thanks for any hints in advance!
Photon

Last edited by PhotonX (2020-09-01 16:56:30)

seth · 2020-08-21 12:29:25

https://bbs.archlinux.org/viewtopic.php?id=258201

PhotonX · 2020-08-21 12:38:38

Thanks for the link, seth! I have a question about it: As far as I understood, the solution proposed in this thread is to put the nvidia module into /etc/mkinitcpio.conf and create a pacman hook. Is this compatible to using nvidia-dkms (which I do use) though? Since I believe that nvidia-dkms already has some sort of pacman hook installed somewhere which takes care of rebuilding the module whenever the kernel is updated.

seth · 2020-08-21 12:44:08

Yes.
How the kernel module makes it onto your system doesn't matter - the relevant part is that it's included.

(The mkinitcpio hook should™ run after dkms but I've never really paid attention to this)

You may also want to pass "nvidia-drm.modeset=1" to the kernel.

PhotonX · 2020-08-21 13:17:27

Seems to have worked, thanks a lot!

I have put "nvidia-drm.modeset=1" as boot flag, added "nvidia nvidia_modeset nvidia_drm" as my (previously empty) MODULES array in /etc/mkinitcpio.conf and regenerated the initramfs with "mkinitcpio -P", then copy&pasted the pacman hook from https://wiki.archlinux.org/index.php/NV … de_setting into /etc/pacman.d/hooks/nvidia.hook only changing the second Target field from nvidia to nvidia-dkms. It booted up fine so far, hopefully, the hooks will work on the next kernel or driver update.

I will post back if any problems occur, but for now the issue looks like solved!

Last edited by PhotonX (2020-08-21 13:18:55)

PhotonX · 2020-09-01 17:01:53

I fear, there is a problem now, indeed.

After the changes I made, I cannot switch to TTY any more, the display gets no signal and switches to standby. The boot flag "nvidia-drm.modeset=1" seems to have no effect on this, so it's not the issue. I found https://wiki.archlinux.org/index.php/NV … _over_HDMI where it says to reload some modules, because otherwise "If you are running your TTY on nvidia, put the lines in a script so you don't end up with no screen. " But I am not sure if it applies to my situation...

seth · 2020-09-01 19:26:18

No, that comment is supposed to help you to reload the nvidia module (if you were to unload it "by hand", you'd have to reload it blindly)
I'm not sure that this is caused by the early KMS setup, but you could try to enforce a video mode on the console, https://raw.githubusercontent.com/torva … modedb.rst or use a text console, eg. if you're using grub: https://wiki.archlinux.org/index.php/GR … ramebuffer

lm808 · 2021-04-05 14:09:10

I have recently experienced a very similar issue, which is temporarily resolved and I have filed a bug report:

https://bugs.archlinux.org/task/70287

Not sure if it is indeed a bug, but hopefully this helps whoever gets here by the direction of Google.

Last edited by lm808 (2021-04-05 14:13:14)

Arch Linux

#1 2020-08-21 12:25:32

Failed to load module "glxserver_nvidia"

#2 2020-08-21 12:29:25

Re: Failed to load module "glxserver_nvidia"

#3 2020-08-21 12:38:38

Re: Failed to load module "glxserver_nvidia"

#4 2020-08-21 12:44:08

Re: Failed to load module "glxserver_nvidia"

#5 2020-08-21 13:17:27

Re: Failed to load module "glxserver_nvidia"

#6 2020-09-01 17:01:53

Re: Failed to load module "glxserver_nvidia"

#7 2020-09-01 19:26:18

Re: Failed to load module "glxserver_nvidia"

#8 2021-04-05 14:09:10

Re: Failed to load module "glxserver_nvidia"

Board footer