Got it. So, in current state, kmp package matches with sub packages, except a couple.
Delay is not an issue. But in such case, the kmp package or zypper should make sure that some dependency doesn’t get updated arbitrarily.
Got it. So, in current state, kmp package matches with sub packages, except a couple.
Delay is not an issue. But in such case, the kmp package or zypper should make sure that some dependency doesn’t get updated arbitrarily.
These kmp-drivers can (must not) work with older/newer kernels as they are build with.
The driver will then be “copied” to the old/new kernel directory (said in an simple way).
This is a normal feature in openSUSE such as using dkms on other distributions.
But I say can, not do…
I leave the driver management to smart heads. It can be a tightly locked kernel+kmp+dependecies, updating to a new version as one unit.
For now i locked these packages. To be safe, i downgraded the two updated packages, to keep all packages to 580.76.
The following 11 items are locked and will not be changed by any action:
Installed:
libnvidia-gpucomp nvidia-common-G06 nvidia-compute-G06 nvidia-compute-utils-G06 nvidia-gl-G06
nvidia-libXNVCtrl nvidia-modprobe nvidia-persistenced nvidia-settings nvidia-userspace-meta-G06
nvidia-video-G06
The following 11 package updates will NOT be installed:
libnvidia-gpucomp nvidia-common-G06 nvidia-compute-G06 nvidia-compute-utils-G06 nvidia-gl-G06
nvidia-libXNVCtrl nvidia-modprobe nvidia-persistenced nvidia-settings nvidia-userspace-meta-G06
nvidia-video-G06
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.