After the latest update, which also updated the kernel and nvidia drivers, my system failed to connect / display on an external monitor.
I booted to an older snapshot and it works well but some softare complaints that my settings are “wierd”.
I want to keep with the current driver and software. What can I do to troubleshoot this problem?
Here is my “inxi -GSaz” output:
System:
Kernel: 6.19.6-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.19.6-1-default
root=UUID=6b897b66-ba2c-4bf9-a9d4-c87c1907e5f4 quiet splash
resume=UUID=9d3228a6-6215-4b90-9c51-b14f21cf8fbe loglevel=0 nosimplefb=1
initcall_blacklist=simpledrm_platform_driver_init
rd.driver.blacklist=nouveau
Desktop: KDE Plasma v: 6.6.2 tk: Qt v: N/A wm: kwin_x11 dm: SDDM
Distro: openSUSE Tumbleweed 20260308
Graphics:
Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Lenovo driver: i915
v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:9bc4
class-ID: 0300
Device-2: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] vendor: Lenovo
driver: nvidia v: 580.126.18 alternate: nouveau,nvidia_drm
non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx)
arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: none empty: DP-1,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1f95
class-ID: 0300
Device-3: IMC Networks Integrated Camera driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:3 chip-ID: 13d3:56ff
class-ID: 0e02
Display: unspecified server: X.Org v: 21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_x11 driver: X: loaded: modesetting dri: iris gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: BOE Display 0x08e8 built: 2019 res:
mode: 1920x1080 hz: 120 scale: 100% (1) dpi: 142 gamma: 1.2
size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9
modes: 1920x1080
API: OpenGL v: 4.6 vendor: intel mesa v: 26.0.1 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
device-ID: 8086:9bc4 memory: 15.12 GiB unified: yes
API: Vulkan v: 1.4.341 layers: 3 device: 0 type: integrated-gpu name: Intel
UHD Graphics (CML GT2) driver: mesa intel v: 26.0.1 device-ID: 8086:9bc4
surfaces: N/A device: 1 type: discrete-gpu name: NVIDIA GeForce GTX 1650
Ti driver: nvidia v: 580.126.18 device-ID: 10de:1f95 surfaces: N/A
device: 2 type: cpu name: llvmpipe (LLVM 21.1.8 256 bits)
driver: mesa llvmpipe v: 26.0.1 (LLVM 21.1.8) device-ID: 10005:0000
surfaces: N/A
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: clinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
hui
March 11, 2026, 2:36pm
2
Showzypper se -si nvidia
Here is the output:
venantius-82au:~ # zypper se -si nvidia
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+----------------------------------+---------+---------------------------+--------+--------------------
i+ | kernel-firmware-nvidia | package | 20251018-1.2 | noarch | openSUSE:Tumbleweed
i+ | kernel-firmware-nvidia | package | 20251018-1.2 | noarch | openSUSE:Tumbleweed
i+ | kernel-firmware-nvidia | package | 20251018-1.2 | noarch | repo-oss
i+ | libnvidia-egl-gbm1 | package | 1.1.3-11.1 | x86_64 | repo-non-free
i+ | libnvidia-egl-wayland1 | package | 1.1.22-57.1 | x86_64 | repo-non-free
i+ | libnvidia-egl-x111 | package | 1.0.5-26.1 | x86_64 | repo-non-free
i+ | libnvidia-gpucomp | package | 580.126.18-49.1 | x86_64 | repo-non-free
i+ | nvidia-common-G06 | package | 580.126.18-49.1 | x86_64 | repo-non-free
i+ | nvidia-compute-G06 | package | 550.144.03-30.1 | x86_64 | repo-non-free
i+ | nvidia-compute-utils-G06 | package | 550.144.03-30.1 | x86_64 | repo-non-free
i+ | nvidia-driver-G06-kmp-default | package | 550.144.03_k6.12.9_1-30.2 | x86_64 | repo-non-free
i+ | nvidia-gl-G06 | package | 580.126.18-49.1 | x86_64 | repo-non-free
i+ | nvidia-libXNVCtrl | package | 595.45.04-2.1 | x86_64 | repo-non-free
i+ | nvidia-modprobe | package | 580.126.18-23.2 | x86_64 | repo-non-free
i+ | nvidia-persistenced | package | 595.45.04-2.1 | x86_64 | repo-non-free
i+ | nvidia-settings | package | 595.45.04-2.1 | x86_64 | repo-non-free
i+ | nvidia-video-G06 | package | 580.126.18-49.1 | x86_64 | repo-non-free
i+ | nvidia-xconfig | package | 595.45.04-2.1 | x86_64 | repo-non-free
i+ | openSUSE-repos-Tumbleweed-NVIDIA | package | 20250728.9adc675-1.2 | x86_64 | openSUSE:Tumbleweed
i+ | openSUSE-repos-Tumbleweed-NVIDIA | package | 20250728.9adc675-1.2 | x86_64 | openSUSE:Tumbleweed
i+ | openSUSE-repos-Tumbleweed-NVIDIA | package | 20250728.9adc675-1.2 | x86_64 | repo-oss
I can see that there is a mixture of 550, 580 and 595 drivers. Should I try and bring them all to 595 version using Yast?
hui
March 12, 2026, 4:24am
4
Yes, the version mix is the reason for the issue.
mchnz
March 12, 2026, 7:51am
5
In the past, when I’ve had to sort out accidental overlapping installs of Nvidia drivers, I’ve followed Stefan Dersch’s blog post Installation of NVIDIA drivers on openSUSE and SLE . The blog post has trouble shooting section which details how to get rid of everything and start with a clean sheet.
Depending on the Nvidia hardware, zypper sometimes seems to update to the wrong driver version, in particular, if one driver version is locked down, it might pick to update another. Stefan’s blog post details how to use locks to block such mistakes.
There are now meta-packages that can help keep things inline as described at https://en.opensuse.org/SDB:NVIDIA_drivers . However I haven’t used them, so I can’t comment on their effectivenesss.
I use the cuda variant of the drivers, which causes issues due to some packages pull from openSUSE’s repo and others from Nvidia’s repo. I have a script that keeps that pairing from getting out of alighment.
With that GPU you can use the open driver, AKA 595 or G07 version; you can install:
zypper in nvidia-open-driver-G07-signed-kmp-meta nvidia-userspace-meta-G07
and let zypper sort out the conflicts.
zypper in nvidia-driver-G06-kmp-meta nvidia-userspace-meta-G06
and let zypper sort out the conflicts.nvidia-settings or nvidia-libXNVCtrl; if those still cause problems, bring them in sync too with YaST or Myrlyn.
Apparently with the introduction of G07 drivers something in the Nvidia packaging needs further tweaking.
I do not play games only use the GPU for AI stuff. Will the open driver cover what I need to do? Need advice if open driver is good enough for everyday work.
With your card I would prefer the open driver, there is also a more conservative G06 option if you don’t need the bleeding edge:
zypper in nvidia-open-driver-G06-signed-kmp-meta nvidia-userspace-meta-G06
lag145
March 12, 2026, 12:18pm
9
Are the user space binaries finally available for g07? Because last I checked the user space g07 was missing
dth2
March 12, 2026, 12:36pm
10
I agree and would suggest that you use the G07 packages. The user rpm pack age is included in the repo:-
download.nvidia.com/opensuse/tumbleweed/x86_64/nvidia-userspace-meta-G07-595.45.04-5.1.x86_64.rpm
I would also recommend the open driver and can confirm that this works fine with my nvidia graphic card.
I have gone with the conservative propriety package because I know for sure there are no issues with it before. It works for now. I will wait a little more time before going for open driver.
Thanks for the tips and suggestions.
system
March 19, 2026, 1:18pm
12
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.