It feels like a recurring theme. Every time i do a dup it breaks the NVIDIA drivers and i have to do everything from scratch again. Is there a more permanent way to fix this?
Please post zypper se -si nvidia
My solution on my Slowroll:
Once you have a working setup, lock the NVidia packages. I also lock the kernel and additional kernel modules like virtualbox*kmp. When there are new NVidia packages, check if their version numbers match, and if they do, unlock, update and lock again.
I don’t know if this is the best approach, but it works for me.
1 Like
S | Name | Type | Version | Arch | Repository
—±---------------------------------±--------±-----------------------±-------±-------------
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-gbm1 | package | 1.1.3-11.1 | x86_64 | nvidia
i | libnvidia-egl-gbm1-32bit | package | 1.1.3-11.1 | x86_64 | repo-non-free
i | libnvidia-egl-gbm1-32bit | package | 1.1.3-11.1 | x86_64 | nvidia
i | libnvidia-egl-wayland1 | package | 1.1.22-57.1 | x86_64 | repo-non-free
i | libnvidia-egl-wayland1 | package | 1.1.22-57.1 | x86_64 | nvidia
i | libnvidia-egl-wayland1-32bit | package | 1.1.22-57.1 | x86_64 | repo-non-free
i | libnvidia-egl-wayland1-32bit | package | 1.1.22-57.1 | x86_64 | nvidia
i | libnvidia-egl-x111 | package | 1.0.5-26.1 | x86_64 | repo-non-free
i | libnvidia-egl-x111 | package | 1.0.5-26.1 | x86_64 | nvidia
i | libnvidia-egl-x111-32bit | package | 1.0.5-26.1 | x86_64 | repo-non-free
i | libnvidia-egl-x111-32bit | package | 1.0.5-26.1 | x86_64 | nvidia
i | libnvidia-gpucomp | package | 580.142-46.1 | x86_64 | repo-non-free
i | libnvidia-gpucomp | package | 580.142-46.1 | x86_64 | nvidia
i | libnvidia-gpucomp-32bit | package | 580.142-46.1 | x86_64 | repo-non-free
i | libnvidia-gpucomp-32bit | package | 580.142-46.1 | x86_64 | nvidia
i | nvidia-common-G06 | package | 580.142-46.1 | x86_64 | repo-non-free
i | nvidia-common-G06 | package | 580.142-46.1 | x86_64 | nvidia
i | nvidia-compute-G06 | package | 580.142-46.1 | x86_64 | repo-non-free
i | nvidia-compute-G06 | package | 580.142-46.1 | x86_64 | nvidia
i | nvidia-compute-G06-32bit | package | 580.142-46.1 | x86_64 | repo-non-free
i | nvidia-compute-G06-32bit | package | 580.142-46.1 | x86_64 | nvidia
i | nvidia-compute-utils-G06 | package | 580.142-46.1 | x86_64 | repo-non-free
i | nvidia-compute-utils-G06 | package | 580.142-46.1 | x86_64 | nvidia
i | nvidia-driver-G06-kmp-default | package | 580.142_k6.19.6_1-46.1 | x86_64 | repo-non-free
i | nvidia-driver-G06-kmp-default | package | 580.142_k6.19.6_1-46.1 | x86_64 | nvidia
i | nvidia-gl-G06 | package | 580.142-46.1 | x86_64 | repo-non-free
i | nvidia-gl-G06 | package | 580.142-46.1 | x86_64 | nvidia
i | nvidia-gl-G06-32bit | package | 580.142-46.1 | x86_64 | repo-non-free
i | nvidia-gl-G06-32bit | package | 580.142-46.1 | x86_64 | nvidia
i | nvidia-modprobe | package | 580.142-24.1 | x86_64 | repo-non-free
i | nvidia-modprobe | package | 580.142-24.1 | x86_64 | nvidia
i | nvidia-persistenced | package | 580.142-2.1 | x86_64 | repo-non-free
i | nvidia-persistenced | package | 580.142-2.1 | x86_64 | nvidia
i | nvidia-userspace-meta-G06 | package | 580.142-37.1 | x86_64 | repo-non-free
i | nvidia-userspace-meta-G06 | package | 580.142-37.1 | x86_64 | nvidia
i | nvidia-video-G06 | package | 580.142-46.1 | x86_64 | repo-non-free
i | nvidia-video-G06 | package | 580.142-46.1 | x86_64 | nvidia
i | nvidia-video-G06-32bit | package | 580.142-46.1 | x86_64 | repo-non-free
i | nvidia-video-G06-32bit | package | 580.142-46.1 | x86_64 | nvidia
i+ | openSUSE-repos-Tumbleweed-NVIDIA | package | 20250728.9adc675-1.2 | x86_64 | repo-oss
I don’t see nvidia-driver-G06-kmp-meta among installed packages.
Try to install it by zypper in nvidia-driver-G06-kmp-meta and check again.
The other packages seem OK, so what exactly is “broken again”?
(And please use pre-formatted text to paste computer output, the </> button above the editing area, and please include the full command and the trailing prompt, so we can be sure of what the exact state of the system is)
1 Like
Yeah taht worked. Then i did dup again and all is good. I had to enroll Moot but after that all gud.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.