[SOLVED] NVIDIA 565.77 Driver Problems

prsmr · 2024-12-18 17:13:29

Hello Arch Linux Community,

I’m facing an issue with NVIDIA drivers, and so far, I haven’t been able to find a solution.

On Monday morning, I performed a system update, during which the NVIDIA drivers were updated from 565.57 to 565.77. When I turned on my laptop at noon, I noticed that I couldn’t click on anything on the Gnome login screen, and the screen was somehow flickering. Using TTY, I enabled AutoLogin, which allowed me to access the desktop, but even there, I couldn’t click on anything.

Since it seemed to be a driver-related issue and I needed to get work done, I quickly downgraded the NVIDIA drivers using downgrade, which resolved the problem and allowed me to work.

After work, I tried to reproduce the issue. I updated the NVIDIA drivers again, but this time nothing worked. The Gnome login screen didn’t appear anymore, and all I saw was a not-blinking underscore (“_”) in the top-left corner. I couldn’t access a terminal either. I booted into the archiso via a USB stick, used arch-chroot, and downgraded the NVIDIA drivers again. However, this time even that didn’t help, so I switched to the Nouveau drivers. This allowed me to boot into my system, and I can now work using the integrated GPU. Unfortunately, my NVIDIA graphics card doesn’t work with Nouveau drivers, so I’d like to switch back to the proprietary drivers.

The problem is, as soon as I install the proprietary drivers (whether nvidia or nvidia-open), the previously described issue recurs, and I have to recover my system using a USB stick.

Can anyone help? Are there known driver issues with the latest NVIDIA drivers?

My Setup:
DELL XPS15 9510
Intel i7 i7-11800H with integrated GPU
NVIDIA RTX 3050 Ti Mobile
Gnome 47 and Wayland
Kernel 6.12.4-arch1-1

Thank you in advance and desperate regards

Last edited by prsmr (2024-12-20 14:40:32)

xerxes_ · 2024-12-18 20:40:00

Post full journalctl log run with admin rights from any of that problematic boots ('sudo journalctl -b-n', where n is number of boot ago; 'journalctl --list-boots' to list available boots).
How did you restart/shutdown system on that boot(s)?

mrtumnus · 2024-12-19 14:05:17

There are problems with the 565 driver and kernel 6.12. You may want to downgrade your kernel and the driver.

https://forums.developer.nvidia.com/t/p … -12/313260

seth · 2024-12-19 18:52:22

In any case please try to add "nvidia_drm.modeset=1 nvidia_drm.fbdev=0" to the https://wiki.archlinux.org/title/Kernel_parameters (it has! to be the kernel commandline, modprobe.conf won't do)

prsmr · 2024-12-19 21:01:44

I tried everything you described.

I downgraded nvidia to 565.57 (the last driver that works)
I switched to Linux-LTS Kernel with 565.77 (Kernel 6.6.65-1-lts)
I switched to Linux-LTS and downgraded to 565.57
I added "nvidia_drm.modeset=1 nvidia_drm.fbdev=0" to Kernel parameters with Kernel 6.12 and 6.6.65-1-lts

nothing worked.

xerxes_ wrote:

Post full journalctl log run with admin rights from any of that problematic boots ('sudo journalctl -b-n', where n is number of boot ago; 'journalctl --list-boots' to list available boots).

really? Its about 5000 lines. Should I maybe upload the log somewhere? If so: where?

But - maybe interesting - I grepped through the journalctl and found this line:

Dez 19 21:19:31 archbook kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel

xerxes_ wrote:

How did you restart/shutdown system on that boot(s)?

Well... pressed the power button...

Last edited by prsmr (2024-12-19 21:02:40)

seth · 2024-12-19 21:10:09

To post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Well... pressed the power button...

Don't!
Try to frenetically press ctrl+alt+del or use the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB

prsmr · 2024-12-20 08:54:01

My Logfile:
https://0x0.st/XCwD.txt

seth wrote:

Don't!
Try to frenetically press ctrl+alt+del or use the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB

Okay...I will try it next time (most likely this evening)

seth · 2024-12-20 09:45:34

Dez 19 21:19:43 archbook gnome-shell[2097]: Running GNOME Shell (using mutter 47.3) as a Wayland display server
Dez 19 21:19:43 archbook dbus-daemon[1254]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=120 pid=2097 comm="/usr/bin/gnome-shell")
Dez 19 21:19:43 archbook systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Dez 19 21:19:43 archbook systemd-networkd[988]: wlp0s20f3: Gained IPv6LL
Dez 19 21:19:43 archbook org.gnome.Shell.desktop[2097]: libEGL warning: egl: failed to create dri2 screen
Dez 19 21:19:43 archbook org.gnome.Shell.desktop[2097]: libEGL warning: egl: failed to create dri2 screen
Dez 19 21:19:43 archbook kernel: gnome-shell[2097]: segfault at 8 ip 00007cabf263d22f sp 00007ffd13a499c0 error 4 in libgallium-24.3.1-arch1.3.so[7cabf2618000+1779000] likely on CPU 1 (core 1, socket 0)
Dez 19 21:19:43 archbook kernel: Code: 48 89 e5 41 56 41 55 41 54 41 89 f4 53 4c 8b 6f 58 48 89 fb 0f b6 05 a1 55 64 02 84 c0 0f 84 98 00 00 00 0f b6 05 91 55 64 02 <41> 83 7d 08 03 4c 8d 35 65 a2 57 02 88 83 68 01 00 00 7e 0e 49 83
Dez 19 21:19:43 archbook systemd-coredump[2129]: Process 2097 (gnome-shell) of user 120 terminated abnormally with signal 11/SEGV, processing...
Dez 19 21:19:43 archbook systemd[1]: Created slice Slice /system/systemd-coredump.
Dez 19 21:19:43 archbook systemd[1]: Started Process Core Dump (PID 2129/UID 0).
Dez 19 21:19:43 archbook dbus-daemon[1254]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Dez 19 21:19:43 archbook systemd[1]: Started RealtimeKit Scheduling Policy Service.
Dez 19 21:19:43 archbook rtkit-daemon[2128]: Successfully called chroot.
Dez 19 21:19:43 archbook rtkit-daemon[2128]: Successfully dropped privileges.
Dez 19 21:19:43 archbook rtkit-daemon[2128]: Successfully limited resources.
Dez 19 21:19:43 archbook rtkit-daemon[2128]: Canary thread running.
Dez 19 21:19:43 archbook rtkit-daemon[2128]: Running.
Dez 19 21:19:43 archbook rtkit-daemon[2128]: Watchdog thread running.
Dez 19 21:19:43 archbook systemd-networkd[988]: br-eff27fa77080: Gained IPv6LL
Dez 19 21:19:43 archbook dhcpcd[1265]: wlp0s20f3: soliciting an IPv6 router
Dez 19 21:19:43 archbook systemd-coredump[2130]: Process 2097 (gnome-shell) of user 120 dumped core.
                                                 
                                                 Stack trace of thread 2097:
                                                 #0  0x00007cabf263d22f n/a (libgallium-24.3.1-arch1.3.so + 0x3d22f)
                                                 #1  0x00007cabf2638336 driCreateNewScreen3 (libgallium-24.3.1-arch1.3.so + 0x38336)
                                                 #2  0x00007cabda601cea n/a (libEGL_mesa.so.0 + 0x1acea)
                                                 #3  0x00007cabda603556 n/a (libEGL_mesa.so.0 + 0x1c556)
                                                 #4  0x00007cabda6025b9 n/a (libEGL_mesa.so.0 + 0x1b5b9)
                                                 #5  0x00007cabda5f097a n/a (libEGL_mesa.so.0 + 0x997a)
                                                 #6  0x00007cabfc3412c9 n/a (libmutter-15.so.0 + 0x1412c9)
                                                 #7  0x00007cabfc3db87e n/a (libmutter-15.so.0 + 0x1db87e)
                                                 #8  0x00007cabfc345c5c n/a (libmutter-15.so.0 + 0x145c5c)
                                                 #9  0x00007cabfcaa5c60 g_initable_new_valist (libgio-2.0.so.0 + 0x74c60)
                                                 #10 0x00007cabfcaa5d4c g_initable_new (libgio-2.0.so.0 + 0x74d4c)
                                                 #11 0x00007cabfc3aa652 n/a (libmutter-15.so.0 + 0x1aa652)
                                                 #12 0x00007cabfc3aab82 n/a (libmutter-15.so.0 + 0x1aab82)
                                                 #13 0x00007cabfc3ab6e2 n/a (libmutter-15.so.0 + 0x1ab6e2)
                                                 #14 0x00007cabfcaa5c60 g_initable_new_valist (libgio-2.0.so.0 + 0x74c60)
                                                 #15 0x00007cabfcaa5d4c g_initable_new (libgio-2.0.so.0 + 0x74d4c)
                                                 #16 0x00007cabfc2ca260 n/a (libmutter-15.so.0 + 0xca260)
                                                 #17 0x00007cabfc2d42b2 n/a (libmutter-15.so.0 + 0xd42b2)
                                                 #18 0x00007cabfc2d487c meta_context_setup (libmutter-15.so.0 + 0xd487c)
                                                 #19 0x00005b1c8ade62bf n/a (/usr/bin/gnome-shell + 0x22bf)
                                                 #20 0x00007cabfc034e08 n/a (libc.so.6 + 0x25e08)
                                                 #21 0x00007cabfc034ecc __libc_start_main (libc.so.6 + 0x25ecc)
                                                 #22 0x00005b1c8ade69e5 n/a (/usr/bin/gnome-shell + 0x29e5)

https://bbs.archlinux.org/viewtopic.php?id=301826
Does gnome on X11 work?
Do you actually end up w/ gnome on wayland AND nvidia on the 565.57 drivers?

prsmr · 2024-12-20 09:53:09

haven't tried it with X11 yet, as I only use Wayland, and since the boot process ended with a non-blinking underscore in the top left corner, I couldn't change that either. I'll try disabling Wayland later and then booting with the 565.57 drivers

Lone_Wolf · 2024-12-20 10:28:40

since the boot process ended with a non-blinking underscore in the top left corner, I couldn't change that either.

2nd link in Seth' signature

prsmr · 2024-12-20 10:30:53

crazy...

If I force GDM to use X11 by setting WaylandEnable=False in /etc/gdm/custom.conf my system isn't booting even with nouveau drivers.

Here's the logfile:
http://0x0.st/XCxI.txt

V1del · 2024-12-20 10:39:51

That last log suggests either xorg-server isn't installed or broken.

sudo pacman -Qkk xorg-server

Lone_Wolf · 2024-12-20 10:42:28

If V1del suggestion doesn't help

rw quiet splash nouveau.config=NvGspRm=1 loglevel=3

remove quiet so boot messages are shown on screen and add systemd.unit=multi-user.target to ensure gdm is NOT started.

reboot, do not start GUI but login as root to console and provide fresh journal .

Last edited by Lone_Wolf (2024-12-20 10:43:26)

prsmr · 2024-12-20 10:49:23

Lone_Wolf wrote:

since the boot process ended with a non-blinking underscore in the top left corner, I couldn't change that either.
2nd link in Seth' signature

Switched to multi-user.target, no I can enter a virtual console.

V1del wrote:

That last log suggests either xorg-server isn't installed or broken.
sudo pacman -Qkk xorg-server

Yes, you're right. It wasn't installed (for whatever reason). I installed it, changed custom.conf back to WaylandEnable=false and...same behavior. But now I could switched back to Wayland without USB-Stick \o/

prsmr · 2024-12-20 11:03:07

envycontrol changed the xorg.conf
Setting to default let me Login with X11

prsmr · 2024-12-20 14:29:14

With LTS-Kernel and X11 the NVIDIA drivers are working again (565.57)

I installed nvidia-open-dkms driver, because when installing nvidia-lts I get errors during mkinitcpio -P (modules not found).

But now I am not able to use Wayland, and xorg isn't really an option because I use the built-in 4K Display and external 2K Displays and xorg does not support different scales on different screens. It's exasperating.

Edit: I installed nvidia-lts and nvidia (as described here) instead of nvidia-open-dkms and tried it despite of the errors and now everything works as expected.

Thank you!

Last edited by prsmr (2024-12-20 14:40:18)

seth · 2024-12-20 15:22:25

With LTS-Kernel and X11 the NVIDIA drivers are working again (565.57)

That's no real solution, 6.12 will become the next LTS kernel in a matter of days or weeks.
Also wasn't the issue 565.77 tbw?

Post journal and xorg log for your successful run w/ 6.12.4 and 565.77

Arch Linux

#1 2024-12-18 17:13:29

[SOLVED] NVIDIA 565.77 Driver Problems

#2 2024-12-18 20:40:00

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#3 2024-12-19 14:05:17

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#4 2024-12-19 18:52:22

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#5 2024-12-19 21:01:44

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#6 2024-12-19 21:10:09

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#7 2024-12-20 08:54:01

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#8 2024-12-20 09:45:34

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#9 2024-12-20 09:53:09

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#10 2024-12-20 10:28:40

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#11 2024-12-20 10:30:53

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#12 2024-12-20 10:39:51

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#13 2024-12-20 10:42:28

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#14 2024-12-20 10:49:23

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#15 2024-12-20 11:03:07

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#16 2024-12-20 14:29:14

Re: [SOLVED] NVIDIA 565.77 Driver Problems

#17 2024-12-20 15:22:25

Re: [SOLVED] NVIDIA 565.77 Driver Problems

Board footer