I tried again and updated the latest big snapshot with more then 3500 packages.
But I locked my nvidia packeges before:
The following 24 items are locked and will not be changed by any action:
Installed:
kernel-firmware-nvidia libdrm_nouveau2 libnvidia-egl-gbm1 libnvidia-egl-wayland1 libnvidia-egl-x111 libnvidia-gpucomp-G06 libnvidia-gpucomp-G06-32bit
nvidia-common-G06 nvidia-compute-G06 nvidia-compute-G06-32bit nvidia-compute-utils-G06 nvidia-driver-G06-kmp-default nvidia-driver-G06-kmp-meta
nvidia-gl-G06 nvidia-libXNVCtrl nvidia-modprobe nvidia-persistenced nvidia-settings nvidia-texture-tools nvidia-userspace-meta-G06 nvidia-video-G06
openSUSE-repos-MicroOS-NVIDIA xf86-video-nouveau xf86-video-nv
Nothing to do.
The result: black screen and after second reboot green screen on kernel 7.0.2.
I had to go back to kernel 6.19.12.
During update i had 2 conflict but I donāt now it is related to it.
Detected 2 file conflicts:
File /usr/lib64/girepository-1.0/AppIndicator3-0.1.typelib
from install of
typelib-1_0-AppIndicator3-0_1-12.10.1~bzr20200706.298-4.6.x86_64 (repo-oss)
conflicts with file from package
libappindicator-gtk3-12.10.1-9.fc43.x86_64 (@System)
File /usr/lib64/libappindicator3.so.1.0.0
from install of
libappindicator3-1-12.10.1~bzr20200706.298-4.6.x86_64 (repo-oss)
conflicts with file from package
libappindicator-gtk3-12.10.1-9.fc43.x86_64 (@System)
I will wait for a fix.
I will stick with kernel that works.
Thank you for providing this lis of package locks. By calling it āproperā, you suggest that users should know this, and should have applied these settings on their systems. I couldnāt find this clearly documented anywhere, though.
The 7.0.2-1-default kernel works with the G06 packages (580.159.03) on the RTX 4000 Ada generation, but not with G07. So this may not be a problem with the kernel, but rather with the graphics driver. To ensure a safe upgrade, it might be sufficient to simply lock or reinstall the latest G06 drivers.
Nope, still broken. Including latest 20260430. nvidia-driver-G06-kmp-default is a proprietary kernel module and it comes with files needed to compile the kernel module yourself. nvidia-open-driver-G06-signed-kmp-default and nvidia-open-driver-G07-signed-kmp-default contain open kernel modules. They are prebuilt and signed for secure boot by OpenSUSE. Hence the size difference.
If you really want a working G07 driver right now Iād recommend to temporary add https://download.opensuse.org/history/20260426/tumbleweed/repo/oss/ and download nvidia-open-driver-G07-signed-kmp-default-595.58.03_k6.19.12_1-2.8 and kernel-default-6.19.12-1.1 from there. Matching userspace binaries are available at NVIDIA:repo-non-free. Just make sure installed versions match before you reboot.
This is just an observation of the various package outputs and may be of relevance. I have only manually installed one package, the relevant kmp which is indicated by in the āSā column via a āi+ā and will pull in the required and recommended supporting packages.
I see output of various permutations where multiple packages have a āi+ā some have all āi+ā, could it be an issue?
@rektal Of course your solution of locking all the nvidia packages is a recipe for disaster as the kmp needs to match the running kernel which you did not lock, so it would never work.
@magfan your not running the open driver (which is pre-built for the kernel and signed) with the proprietary kmp on a kernel update it gets rebuilt and signed on installation and a kernel updateā¦
@akontsevich see above, but the open driver is pre-built, so you donāt need the extra header files etc for it so much smaller. The idea behind the signed open driver is less work and packages for building, signing etc. Itās easy to miss the MOK screen at boot to import the keys as well, or users donāt know what to do with this screen when it pops up on reboot.
Those i+ donāt matter as long as you donāt hop between G06 and G07. Nvidia driver packages have decent conflict specifications so zypper will remove conflicting ones. Only thing that might go wrong is that packages marked with i+ that donāt conflict with other packages wonāt be removed automatically. So there might be some leftover packages that are safe to uninstall, but I donāt think they would cause any harm.
@Lioli7k This is the first Tumbleweed install Iāve used the rpms, normally Iāve been using the run file, so a new experience for me Likewise on another setup running Leap 16.0. Both are running the open driver.
Running (trying to anyway) X11 and xfce
Xorg.0.log shows
[ 12.809] (II) NVIDIA(0): Virtual screen size determined to be 3520 x 1200
[ 12.930] (--) NVIDIA(0): DPI set to (99, 98); computed from "UseEdidDpi" X config
[ 12.930] (--) NVIDIA(0): option
[ 12.932] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[ 12.932] (II) NVIDIA: access.
[ 22.938] (EE) NVIDIA(GPU-0): Failed to initialize DMA.
[ 22.944] (EE) NVIDIA(0): Failed to allocate push buffer
[ 22.955] (EE)
Fatal server error:
[ 22.955] (EE) AddScreen/ScreenInit failed for driver 0
I think as others have said this is a kernel/kmp issue and we need a new driver from nvidia. I do have 6.19.12 or something but for the life of me I could not get the module to install/build into that tree. (maybe Iāll try the 10150426 thing above).
I also tried slowroll but that had already pushed a 7.0 kernel by then so I switched back. Since I donāt have anything else to do with this computer atm I donāt have btrfs so no snapshotsā¦
Mostly just adding info
Iāve been using opensuse forever but am somewhat new to the tumbleweed thing. This is the first time itās bitten me. But it got me pretty well stuck
You should be able to download the necessary rpms or temporarily add https://download.opensuse.org/history/20260426/tumbleweed/repo/oss/ as Liolik mentioned in this thread
Iād recommend btrfs for Tumbleweed as itās sort of considered stable now and Nvidia drivers tend to be out of sync with kernel version bumps.
Some good news. Potential fix for G07 is merged in the Factory and will be available in next snapshot. The same fix is also made for open G06 but it still pending to be merged. Also thereās potential that latest drivers (595.71.05 and 580.159.03) from Nvidia have a regression that is causing all sorts of issues.