Yes, i will open a new thread.
@Lioli7k Does the suggestion from Stefan work for you (see bug)? Not for me. Added my results to the bugreport.
Havenāt tested it yet but Iām planning to try it shortly.
Newest nvidia-open-driver-G07-signed-kmp-default - 595.71.05_k7.0.5_1-2.3 still works for me however still very unstable - this error pops-up every few seconds: "The desktop effects settings were reset due to a graphics reset.ā So staying on longterm for now.
Tested, works for me. I wouldnāt call it a solution but it sure proves that there is a race condition during GPU initialisation.
595.71.05_k7.0.5_1-2.3 itself is fine but you need either to include Nvidia modules into initrd or reset GPU after boot for it to work. Since it requires workarounds I would still recommend sticking to kernel-longterm for now.
1 Like
Alright, I see a lot of people coming to this thread are confused. So Iām gonna summarise various posts from forums and discussions at bugzilla.
All those problems are caused by improper GPU initialisation during boot on 7.0 kernels. Iām yet to find why and how but that much is confirmed by me and other people working on this issue.
It is not caused by GRUB/systemd-boot/X11/Wayland/SDDM/GDM or whatever. Problem occurs even before you get to see plymouth showing Tumbleweed logo. Kind of problem youāre gonna get depends on when your GPU is initialised. It could be pretty much anything: working system, black screen, random crashes, color distortionā¦ We got them all.
I have tried countless things since Iāve started this thread. You name it, odds are Iāve tried it already. Only things that I didnāt tested much yet is modifying initrd and kernel parameters. I was testing nearly everything down the stack, all the way down to compiler and even compiler itself. Iāve tested every 7.0 kernel release (7.0.1, 7.0.2, 7.0.3 and now 7.0.5), open G06, proprietary G06, open G07, proprietary G07, both rpm and run file methods.
Iām absolutely sure issue occurs when kernel-default used with either of nvidia-driver-G06-kmp-default, nvidia-open-driver-G06-signed-kmp-default or nvidia-open-driver-G07-signed-kmp-default (cuda variants are also affected).
Changing any other packages may improve situation for you, but it wonāt solve the core issue for everyone. Iām looking for a solution that will work for everyone and wonāt require changing bootloaders, login screens, Nvidia driver versions (unless that particular version is known to be problematic), desktop environments or anything like that.
This is kernel level problem, not in the user space. Ideally I need someone with Linux kernel expertise to fix this. Hope this post covers everything so far and clears the confusion.
5 Likes
@Lioli7k do you see much in the output from journalctl -b | grep -Ei "nvidia|drm|nvrm"?
Still all good hereā¦
If you are affected I recommend switching to LTS kernel until this issue is fixed. You can do so by running sudo zypper in kernel-longterm -kernel-default
You should get output similar to this:
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: 1: the installed nvidia-open-driver-G07-signed-kmp-default-595.71.05_k7.0.5_1-2.3.x86_64 requires 'ksym(default:__acpi_video_get_backlight_type) = 727e57a3', but this requirement cannot be provided
deleted providers: kernel-default-7.0.3-1.1.x86_64
Solution 1: deinstallation of nvidia-open-driver-G07-signed-kmp-default-595.71.05_k7.0.5_1-2.3.x86_64
Solution 2: keep kernel-default-7.0.5-1.1.x86_64
Solution 3: break nvidia-open-driver-G07-signed-kmp-default-595.71.05_k7.0.5_1-2.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 1
Resolving dependencies...
Resolving package dependencies...
The following 2 NEW packages are going to be installed:
kernel-longterm nvidia-open-driver-G07-signed-kmp-longterm
The following 3 packages are going to be REMOVED:
kernel-default-7.0.3-1.1 kernel-default-7.0.5-1.1 nvidia-open-driver-G07-signed-kmp-default
The following package requires a system reboot:
kernel-longterm
2 new packages to install, 3 to remove.
Package download size: 206.3 MiB
Package install size change:
| 288.0 MiB required by packages that will be installed
-283.9 MiB | - 571.9 MiB released by packages that will be removed
Note: System reboot required.
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y):
Make sure kmp package is going to change from kmp-default to kmp-longterm.
nvidia-driver-G06-kmp-default ā nvidia-driver-G06-kmp-longterm
nvidia-open-driver-G06-signed-kmp-default ā nvidia-open-driver-G06-signed-kmp-longterm
nvidia-open-driver-G07-signed-kmp-default ā nvidia-open-driver-G07-signed-kmp-longterm
After running the command, run zypper se -si nvidia kernel-default kernel-longterm and check that version of Nvidia packages match version kmp-longterm and version of kmp-longterm after k matches kernel-longterm. Itās OK if version of kmp-meta doesnāt match the rest. If anything else doesnāt match youāll have to manually install correct version by specifying version after package name to zypper in like this: sudo zypper in nvidia-userspace-meta-G07-595.71.05-15.1. If zypper says The selected package has lower version than the installed one. you need to also add --oldpackage flag, command would look like this: sudo zypper in --oldpackage nvidia-userspace-meta-G07-595.71.05-15.1. To look up versions of a package use zypper se -s name-of-the-package
For reference output of zypper se -si nvidia kernel-default kernel-longterm should look similar to this:
S | Name | Type | Version | Arch | Repository
---+--------------------------------------------+---------+--------------------------+--------+------------------
i | kernel-firmware-nvidia | package | 20260408-1.1 | noarch | repo-oss
i | kernel-longterm | package | 6.18.28-1.1 | x86_64 | repo-oss
i | libnvidia-cfg | package | 595.71.05-13.1 | x86_64 | repo-non-free
i | libnvidia-egl-gbm1 | package | 1.1.3-11.2 | x86_64 | repo-non-free
i | libnvidia-egl-wayland1 | package | 1.1.22-57.4 | x86_64 | repo-non-free
i | libnvidia-egl-x111 | package | 1.0.5-26.2 | x86_64 | repo-non-free
i | libnvidia-gpucomp | package | 595.71.05-13.1 | x86_64 | repo-non-free
i | libnvidia-ml | package | 595.71.05-13.1 | x86_64 | repo-non-free
i | nvidia-common-G07 | package | 595.71.05-13.1 | x86_64 | repo-non-free
i | nvidia-compute-G07 | package | 595.71.05-13.1 | x86_64 | repo-non-free
i | nvidia-compute-utils-G07 | package | 595.71.05-13.1 | x86_64 | repo-non-free
i | nvidia-gl-G07 | package | 595.71.05-13.1 | x86_64 | repo-non-free
i | nvidia-modprobe | package | 595.71.05-2.2 | x86_64 | repo-non-free
i | nvidia-open-driver-G07-signed-kmp-longterm | package | 595.71.05_k6.18.28_1-2.3 | x86_64 | repo-oss
i | nvidia-open-driver-G07-signed-kmp-meta | package | 595.71.05-16.1 | x86_64 | repo-non-free
i | nvidia-persistenced | package | 595.71.05-2.2 | x86_64 | repo-non-free
i | nvidia-userspace-meta-G07 | package | 595.71.05-16.1 | x86_64 | repo-non-free
i | nvidia-video-G07 | package | 595.71.05-13.1 | x86_64 | repo-non-free
i | openSUSE-repos-MicroOS-NVIDIA | package | 20260423.1a6a0f3-2.1 | x86_64 | repo-oss
Only after verifying that reboot. Ignoring step above might cause broken Nvidia driver and you wonāt be able to log in. If that happens youāll have to rollback using snapper.
1 Like
Nothing unusual after kickstarting 7.0.5. No errors, nothing. 
Both kernel and Nvidia modules seem to work correctly. So they donāt error out at all. But getting a working or borked system depends on when Nvidia modules are loaded. I really should inspect order in which DRM/KMS modules are loaded. Something is clearly conflicting there.
1 Like
Hi, Iāve been following the thread for a few days, Iāve also experienced similar issues as other people here.
Iāve seen this mentioned at the start of the thread, but not since so Iām adding this input. Iāve been able to avoid almost completely any issue by pressing the ESC key during splash screen to show boot logs. When I do that, I boot normally, and I donāt encounter any other issue after that.
Hopefully this can help !
Hiya. It is a band-aid fix. Thatās why Iām not recommending it to anyone coming here.
1 Like
Nothingā¦ Order of video related events stays the same. I canāt find any issuesā¦
I might be going skittles, but I donāt remember seeing a single report of this issue on GTX 10 series or older.
What if I canāt find it because it is a GSP bug?
new update released with nvidia driver G07 for kernel 7.0.5. Did this fixed the issues? Can anyone confirm?
Can confirm broken on my system. 20260510
1 Like
I removed the splash=silent kernel boot option, I can now boot with no issues. I know itās not a fix but at least I can boot in the system with no issues. Iām running kernel 7.0.5 with open driver 580.
2 Likes
The latest update doesnāt work on my system (RTX 3060 Ti with G07 driver)
So having now replaced the 4070 Super with an AMD GPU and done the distro update, I can confirm that this is again a problem with NVidiaās idiot software drivers. Glad to never have this be an issue again.
1 Like
Issue comes back for me after first boot which works normally but glad itās working for you.
After updating to 7.0.5-1-default and 595.71.05 today I can confirm my system is booting correctly and has done so several times. I previously was seeing first boot success with subsequent failures before downgrading to 6.19.12 and 580.142 and staying with that setup untilI did the update today, removing completely the 580 series and installing 595.71.05 after todayās dup. RTX 5050
2 Likes