[Build20260511] not working, black screen. G07,rtx3080
rollback to 6.19.12-1-default
1 Like
Iāve been stuck with this issue for nearly two weeks now, which is preventing me from updating my system equipped with an RTX 3070. Even todayās update ended in failure, forcing yet another inevitable snapper rollback to get things working again.
I am currently using the G06 proprietary drivers. This is mainly because every time I try to install the G07 series - even following the official guide - the resolution stays locked at 1080, and there is simply no way to get the new drivers to work properly.
Itās a shame because Iām actually very happy with Tumbleweed; Iāve been using it for almost two years without any major issues. However, Iām reluctantly starting to consider switching to another distro. It feels like Nvidia drivers are a specific āAchillesā heelā for this distribution.
Iāll wait a bit longer to see if the problem gets resolved in a reasonable timeframe before deciding what to do. For the record, the specific symptoms Iām encountering are a dark screen with corrupted characters at login, and a black screen with a frozen cursor when entering standby.
1 Like
Did you checked zypper se -si nvidia kernel-default before rebooting? Version mismatch is a common culprit of broken Nvidia driver.
1 Like
Itās been more than two years since I installed the proprietary Nvidia driversā¦ yes my card is a bit dated, but Iāve never had such a good time as I do now.
Glad to report that after todayās update (20260511) everything is back to normal.
My system:
inxi -b
System:
Host: JS-LnxWS Kernel: 7.0.5-1-default arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.6.4 Distro: openSUSE Tumbleweed 20260511
Machine:
Type: Desktop System: HP product: HP Z8 G4 Workstation v: SBKPF,DWKSBLF
serial: <superuser required>
Mobo: HP model: 81C7 v: 1.00 serial: <superuser required> Firmware: UEFI
vendor: HP v: P60 v02.95 date: 11/21/2024
CPU:
Info: 16-core Intel Xeon Gold 6226R [MT MCP] speed (MHz): avg: 1200
min/max: 1200/3900
Graphics:
Device-1: NVIDIA GA104GL [RTX A4000] driver: nvidia v: 595.71.05
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.11
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: modesetting,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
resolution: 5120x1440~120Hz
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 595.71.05
renderer: NVIDIA RTX A4000/PCIe/SSE2
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Network:
Device-1: Intel Ethernet I219-LM driver: e1000e
Device-2: Intel Ethernet X722 driver: N/A
Device-3: Intel Ethernet X722 for 1GbE driver: i40e
Drives:
Local Storage: total: 2.29 TiB used: 900.68 GiB (38.5%)
Info:
Memory: total: 64 GiB available: 62.49 GiB used: 6.69 GiB (10.7%)
Processes: 515 Uptime: 0h 38m Shell: Bash inxi: 3.3.40
Hi, thanks for the suggestion!
Yes, Iāve checked for version mismatches between the kernel and the driver before rebooting, but everything seemed to align. Iāve followed the official guide to the letter and tried several workarounds - including the one you mentioned - but unfortunately, the result remains the same.
I havenāt found any other alternative paths to solve this, Iām running out of ideas.
You do not need to rollback with snapper every time: just install longterm kernel like mentioned above. That already helped me to return my system to normal state.
Then, with the longterm kernel, you can update your system to whatever latest version without having to wait or depend on a fix.
1 Like
Nvidia RTX 4060 card, and from 20260428, after updating with zypper dup, a black screen. Nothing helped. Changing Nvidia drivers, new kernels, nothing helped. Constant black screen, sometimes red/pink. Another update, kernel 7.0.5-1-default, and a black screen. There was a thread saying that switching from SDDM to GDM helped someone. I had SDDM and Plymouth installed, and something seemed to be conflicting. I uninstalled all Plymouth packages (-branding-openSUSE, -dracut,-lang, -plugin-label, -plugin-two-step, -scripts, -theme-gbrt, -theme-spinner), and the tumbleweed finally started. Nvidia-open-driver-G07 and kernel 7.0.5-1 drivers and it works.
1 Like
Thanks for the advice! I was actually considering this route.
Plymouth is not the cause - it works fine for me, however after login graphical effects are unstable. And You said nothing whether you tried longterm kernel or not?
Updated to 20260511. No luck on 595.71.05_k7.0.5_1-2.3. Behaviour remains the same.
Hi,
I reinstalled the kerne:7.0.5-1 and install the NVIDIA-Linux-x86_64-595.71.05.run. It was succesfully installed.
The problem probably is in wayland.
If I login to xfce_x11, I donāt lost connection with the monitor and it is working.
If I login to xfce-wayland, wayfire and labwc, as soon as I login, the monitor becomes disconnected. Itās just fortunate that the keyboard still works and I was able to use my custom shortcut key to logout from the wayland session.
Iāve studied GSP a bit. Normally it is enabled for all GPUs that support it (RTX 20 series or newer). It is possible to disable it according to Nvidia manual. Then it claims to not be using GSP firmware according to sort /proc/driver/nvidia/params. What actually happens? GSP firmware is loaded unconditionally. What happens if itās missing? GPU is guaranteed to fail initialisation (at least in my case with RTX 4070 Ti).
nvidia 0000:01:00.0: Direct firmware load for nvidia/595.71.05/gsp_ga10x.bin failed with error -2
NVRM: RmFetchGspRmImages: No firmware image found
NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x61:0x56:2074)
NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Considering that normally Nvidia modules are loaded shortly after filesystems are mountedā¦ It is quite possible that Nvidia driver silently fails when reading GSP firmware.
It is not a X11 or Wayland issue.
2 Likes
Yep. You were right, thanks. 
Edit:
I am using SDDM and plymouth and grub efi
@conram The nvidia modules should not be in the kernel, they are omitted by a dracut config. If they were then thatās a bug of some sortā¦
Do you have the splash=silent (as pointed out by @dart364) in your boot options, removing may help?
Iām running systemd-boot, no plymouth, been fine since day one of kernel 7.x.x.
@malcolmlewis
Yep I have the splash=silent, Itās ok, Iām not going to remove it. It is working now in wayland.
Could be the twice reboot I did made the way to loging in wayland made it possible 
As long as this is working now Iām not going to touch anything.
I wanted to update to confirm that, following your suggestions, Iāve finally resolved the stability issues with my RTX 3070.
The decisive step was switching to the Longterm kernel branch. After setting it as the default and completing a massive DUP, the system is now perfectly stable and even standby functionality is finally working again.
Iām glad this workaround is holding up, but I still hope a proper solution for the most recent kernels will be found in a reasonable timeframe.
Thanks to everyone for the help!
1 Like
I am in the same boat.