Nvidia Persistance Daemon issue after update to 6.15 kernel on Tumbleweed

Just did an update a couple of days ago. The kernel was updated to 6.15.xx. Since the update I am unable to boot into X. The error message is ‘Failed to start Nvidia Persistance Daemon’. I can boot using the 6.14.xx kernel into X without issue. This problem has appeared in the past but was not related to my current situation. Suse-Prime is not installed on my machine. Does anyone have any ideas or suggestions?

Do you use the Nvidia Driver of the Tumbleweed Repo?
This one is build against Kernel 6.14 and might not work on Kernel 6.15.

Here is the Nvidia repo URL. Index of /opensuse/tumbleweed.
Definitely not working with the 6.15 kernel

This is already the second thread where somebody claims that the kernel in Tumbleweed was updated to 6.15.

Tumbleweed is still at 6.14.x.

Users of arbitrary development repos should be aware of issues which can arise by using them.

2 Likes

You are absolutely correct. Guess I had dyslexia moment. The kernel was updated a couple of days ago from 6.14.4-1 to 6.14.5-1. Nvidia is not working with 6.14.5-1 so I have been using the older 6.14.4-1.

All Nvidia boxes (desktops and Laptops with Optimus), work flawlessly with the latest kernel here.

You can try to disable the persistance service. Or uninstall the persistance package.

What does:

systemctl status nvidia-persistenced

show with the 6.14.5 kernel? Everything working here on wayland…

LT-B:~ # uname -r
6.14.5-1-default
LT-B:~ # systemctl status nvidia-persistenced
● nvidia-persistenced.service - NVIDIA Persistence Daemon
     Loaded: loaded (/usr/lib/systemd/system/nvidia-persistenced.service; enabled; preset: enabled)
     Active: active (running) since Wed 2025-05-14 09:32:32 CEST; 5h 51min ago
 Invocation: ac08aa3e2f2d46fbb777bb910a52fd64
    Process: 1856 ExecStart=/usr/bin/nvidia-persistenced --verbose (code=exited, status=0/SUCCESS)
   Main PID: 1872 (nvidia-persiste)
      Tasks: 1 (limit: 18878)
        CPU: 11ms
     CGroup: /system.slice/nvidia-persistenced.service
             └─1872 /usr/bin/nvidia-persistenced --verbose

May 14 09:32:32 LT-B systemd[1]: Starting NVIDIA Persistence Daemon...
May 14 09:32:32 LT-B nvidia-persistenced[1872]: Verbose syslog connection opened
May 14 09:32:32 LT-B nvidia-persistenced[1872]: Directory /var/run/nvidia-persistenced will not be removed on exit
May 14 09:32:32 LT-B nvidia-persistenced[1872]: Started (1872)
May 14 09:32:32 LT-B nvidia-persistenced[1872]: device 0000:01:00.0 - registered
May 14 09:32:32 LT-B nvidia-persistenced[1872]: device 0000:01:00.0 - persistence mode enabled.
May 14 09:32:32 LT-B nvidia-persistenced[1872]: device 0000:01:00.0 - NUMA memory onlined.
May 14 09:32:32 LT-B nvidia-persistenced[1872]: Local RPC services initialized
May 14 09:32:32 LT-B systemd[1]: Started NVIDIA Persistence Daemon.
LT-B:~ # 

I too am using Wayland. Ran the command you suggested. I do not know how to copy the output in terminal mode but basically persistenced went into a 5 second timeout, then complained the timeout period was too short, and then failed.

@diacobel.1 If it fails, then normally the driver (nvidia) is not working… do you get output from nvidia-smi

You are correct, the nvidia driver is not working. I am using nvidia driver 570.144 on a GeForce RTX 4060 Ti chipset.

@diacobel.1 force the re-install of the nvidia kmp when booted to the new kernel…

https://forums.opensuse.org/t/no-nvidia-driver-after-zypper-dup-today/184989/8

1 Like

Sheer genius. Worked great. Re-installing that package force a re-initialization of the kernel modules so now everything works as expected. Thank you for your expert guidance.

I had this same error on my Tumbleweed install, but the symptom was different in that only X11 could be used whereas Wayland would trigger the error.