System is tumbleweed, video card is a 1050TI
Back in 2023, I blacklisted the " nvidia-open-driver-G06-signed-kmp-default " per these posts below, to get my system working.
I was just wondering if I need to un -blacklist this to keep my video card driver updated & prevent future issues?
Thanks
John Kilbert
@kilbert885 Hi, it should be better, can you post the output from inxi -GSaz
Thanks
Kilbert@Galactica:~> inxi -GSaz
System:
Kernel: 6.19.6-2-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.19.6-2-default
root=UUID=a605f894-f90b-4344-b5d6-32495a4ee14f splash=silent
mitigations=auto quiet
Desktop: KDE Plasma v: 6.6.2 tk: Qt v: N/A info: frameworks v: 6.23.0
wm: kwin_x11 tools: avail: xscreensaver vt: 2 dm: SDDM Distro: openSUSE
Tumbleweed 20260311
Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Gigabyte
driver: nouveau v: kernel alternate: nvidia_drm,nvidia non-free: 550-580.xx+
status: current (as of 2025-11; EOL~2026-12-xx) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
link-max: gen: 3 speed: 8 GT/s ports: active: DP-1,HDMI-A-1 empty: DVI-D-1
bus-ID: 07:00.0 chip-ID: 10de:1c82 class-ID: 0300 temp: 51.0 C
Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev,nouveau,nv,nvidia dri: nouveau gpu: nouveau
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
s-diag: 777mm (30.58")
Monitor-1: DP-1 model: 4k60-1080@240 serial: <filter> built: 2021 res: N/A
dpi: 81 gamma: 1.2 size: 480x270mm (18.9x10.63") diag: 690mm (27.2")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: primary model: MSI MAG322CQR
serial: <filter> built: 2021 res: mode: 2560x1440 hz: 60 scale: 100% (1)
dpi: 93 gamma: 1.2 size: 697x392mm (27.44x15.43") diag: 800mm (31.5")
ratio: 16:9 modes: max: 2560x1440 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
drv: nouveau inactive: wayland
API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 26.0.1 glx-v: 1.4
direct-render: yes renderer: NV137 device-ID: 10de:1c82 memory: 3.89 GiB
unified: no
API: Vulkan v: 1.4.341 layers: 1 device: 0 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
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
@kilbert885 That GPU can’t run the open driver, only the proprietary one. The latest you can ever use is G06. This one “nvidia-driver-G06-kmp-default-580.142”
Bummer. At least I know I am ok for now.
I do have a different card- rx580 my job was tossing out- would that be better to install?
Thanks for your time
@kilbert885 Why not just run that G06 driver? I have a P400 and a Tesla P4 that run fine on Leap 16.0 and Tubleweed.
I will, if I can.
it sounded like it would run into issues, but if I can just keep on plugin’ along, I am happy with what I have. Thanks for your help
Hi, new Tumbleweed (not Linux) user here.
I was dealing with Nvidia in Tumbleweed (among other things) yesterday as well.
If I omit the fact that Nvidia in TW is in overall a bit of alchemy, the G06 was broken in terms of version mismatch between kmp and userspace packages, so it wasn’t possible to get installed anyway.
G07 works just fine.
But since it’s Nvidia driver, the default and often updated kernel in TW isn’t a good companion for it.
So I went with the longterm kernel with G07, which should spare me some unnecessary headaches I hope.
Like with everything, once you know how to deal with it, it works. Just as in any other distro, nothing is perfect. And that’s good. 
@inf78 Hi and welcome to the Forum 
On a kernel update the installed kmp will rebuild, so there should not be an issue. When the driver updates it should also rebuild based on the running kernel. I think (as I don’t use the rpms on Tumbleweed, just the run file) there maybe a potential issue when both update perhaps.
But If you switch to a VT ( as in ctrl+alt+F1), log in as root user, switch to multi-user via systemctl isolate multi-user.target and then force the re-install of the kmp with zypper, zypper in -f <some kmp package> then reboot all should be good.
Yes, I was using the binary Nvidia installer in the past, but not these days.
I don’t know how much Nvidia improved its ability to keep up with newer kernels, but it wasn’t so great in the past where a new kernel made the driver impossible to build at all, hence the longterm kernel. Plus, it spares me kernel updates being downloaded too often. The default kernel must be unistalled, otherwise it will still get updated of course, whether being used for actual boot or not.
There was a few issues with the open driver a couple of kernels back, but proprietary one built fine, so easy to switch on the fly.