Putting something here so that people might have a way to find out that there’s a problem in advance. Take care of your nvidia packages and kernel updates. zypper selected me three different kernel modules and a different version userspace to them all. Of course, it won’t boot.
Can’t file a proper bug because of an LDAP error preventing login to bugzilla.o.o. I’ll try again later.
Standard cuda repo installation per instructions from Stefan. Can’t switch to the normal nvidia repos either, due to package conflicts between libnvidia-ml and the g06 compute packages.
The real problem is the login to bugzilla not working I guess it’s another server outage, there have been a few this week.
This looks like it’s going to effect users who are using the nvidia-hosted cuda repo. The TW kernel and nvidia metapackages will pull in the default kernel module which has been updated to match the updated userspace drivers in the nvidia repo, but the userspace drivers in the cuda repo have not been updated, so we end up with new kernel+new module+old userspace, which breaks.
Posted a workaround here. Basically, we force the installation of the cuda kmp package, replacing the default kmp package, and then we can zypper dup and our versions all match.
This is not a long-term solution, because when the kernel updates, that kmp will not update with it, and we can end up with a broken install in future. But it works today.
I will follow up on the suse bugzilla since it’s available.