http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c1 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS CC| |axel.braun@gmx.de Flags| |needinfo?(axel.braun@gmx.de | |) --- Comment #1 from Stefan Dirsch --- Looks like rebuild of kernel module didn't work for some reason. I don't see any build failures against TW kernels in my test environment. So maybe you're also running kernels from a different repository. Please attach the result of running nvidia-bug-report.sh. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c3 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Stefan Dirsch --- No, this doesn't help. Maybe the kernel module wasn't rebuild because you only updated the kernel package and not the kernel-<flavor>-devel package, which triggers the rebuild. I don't know. Whatever, apparently this can't be investigated any longer. Closing. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c5 Axel Braun changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #846445|0 |1 is obsolete| | --- Comment #5 from Axel Braun --- Created attachment 846461 --> http://bugzilla.opensuse.org/attachment.cgi?id=846461&action=edit installation log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c7 --- Comment #7 from Stefan Dirsch --- (In reply to Axel Braun from comment #5)

Created attachment 846461 [details] installation log

Looks like kernel module rebuild was successful. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c9 --- Comment #9 from Stefan Dirsch --- You're using kernel 5.10.16-1-default Old kernel modules are still available in 5.10.14.-1-default directory. weak-updates symlinks are available for 5.10.16-1-default but are symlinking to non-existing modules in 5.10.9-1-default. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c11 --- Comment #11 from Stefan Dirsch --- # rpm --triggers -qp nvidia-gfxG05-kmp-default-460.39_k5.10.9_1-34.1.x86_64.rpm [...] triggerpostun scriptlet (using /bin/sh) -- kernel-default for dir in $(find /lib/modules -mindepth 1 -maxdepth 1 -type d); do if [ ! -d $dir/kernel ]; then test -d $dir/updates && rm -f $dir/updates/nvidia*.ko fi done Maybe checking for /lib/modules/5.10.16-1-default/kernel no longer works and this file doesn't exist although 5.10.16-1-default is the currently installed and running kernel. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c13 --- Comment #13 from Axel Braun --- (In reply to Stefan Dirsch from comment #11)

Maybe checking for /lib/modules/5.10.16-1-default/kernel no longer works and this file doesn't exist although 5.10.16-1-default is the currently installed and running kernel.

The directory /lib/modules/5.10.16-1-default/kernel exists and looks OK. Surprisingly there is still a bunch of modules from the day onwards where I set-up the system (starting at 5.5.x kernels...) - this is not automatically cleaned up? Anything else I can check/lookup/try? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c15 Michael Hirmke changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse@mike.franken.de --- Comment #15 from Michael Hirmke --- Not sure if this is the same problem, but: On Leap 15.2 I actually have kernel 5.3.18-lp152.63-default. When adding the NVidia repo and installing nvidia-glG05, the files can be found in 5.3.18-lp152.19-default/updates afterwards - and nothing was copied or linked to 5.3.18-lp152.63-default. So no module is loaded on reboot. After manually copying or linking the modules to 5.3.18-lp152.63-default/updates and running "depmod -a" the modules are loaded on nex reboot. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c17 --- Comment #17 from Stefan Dirsch --- (In reply to Michael Hirmke from comment #15)

Not sure if this is the same problem, but: On Leap 15.2 I actually have kernel 5.3.18-lp152.63-default. When adding the NVidia repo and installing nvidia-glG05, the files can be found in 5.3.18-lp152.19-default/updates afterwards

This is correct behaviour.

- and nothing was copied or linked to 5.3.18-lp152.63-default.

That's an issue. weak-updates(2) should have created symlinks from 5.3.18-lp152.63-default/weak-updates to 5.3.18-lp152.19-default/updates .

So no module is loaded on reboot. After manually copying or linking the modules to 5.3.18-lp152.63-default/updates and running "depmod -a" the modules are loaded on nex reboot.

Yes, good workaround. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|axel.braun@gmx.de |sndirsch@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c19 --- Comment #19 from Michael Hirmke --- I've retried it several times on Leap - no weak-update mechanism! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c21 --- Comment #21 from Stefan Dirsch --- Ok. So the behaviour of nvidia packages is fine. As mentioned before TW doesn't use weak-updates mechanism. Just updating the kernel alsne doesn't work as expected for you (TW) and for Michael (Leap) (but it does for me (TW) and apparently also for others (TW and Leap IIRC) as I've seen on the factory ML). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c23 --- Comment #23 from Michael Hirmke --- (In reply to Stefan Dirsch from comment #21)

Ok. So the behaviour of nvidia packages is fine. As mentioned before TW doesn't use weak-updates mechanism. Just updating the kernel alsne doesn't work as expected for you (TW) and for Michael (Leap) (but it does for me (TW) and apparently also for others (TW and Leap IIRC) as I've seen on the factory ML).

Guess I found the reason. After installing again, I saw: Warning: /lib/modules/5.3.18-lp152.63-default is inconsistent Warning: weak-updates symlinks might not be created Probably this happens, because I alredy have an update directory in it, which contains drivers for my DV card. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c25 --- Comment #25 from Stefan Dirsch --- Ok. But I did not understand where your DV card modules are located exactly. You should not copy anything below weak-updates dir. The KMP or the kernel itself creates symlinks below this directory to compatible modules in different kernel module trees. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c27 --- Comment #27 from Stefan Dirsch --- Hmm. This shouldn't be a problem for weak-updates, but I'm not familiar with this /usr/lib/module-init-tools/weak-modules2 script. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c30 B changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kerossin@pm.me --- Comment #30 from B --- I believe I encountered the same problem when upgrading to snapshot 20210315. kernel-default changed from 5.11.4-1.2 to 5.11.4-1.3. /lib/modules/5.11.4-1-default/updates/ usually contains the kernel modules but after the upgrade this directory is empty and there's a new directory /lib/modules/5.11.4-1-default/weak-updates/updates/ which has broken links nvidia-drm.ko -> /lib/modules/5.10.16-1-default/updates/nvidia-drm.ko nvidia.ko -> /lib/modules/5.10.16-1-default/updates/nvidia.ko nvidia-modeset.ko -> /lib/modules/5.10.16-1-default/updates/nvidia-modeset.ko nvidia-uvm.ko -> /lib/modules/5.10.16-1-default/updates/nvidia-uvm.ko I don't have any 5.10 kernels installed anymore, there's just old dirs left over in /lib/modules but they don't have the modules anymore so I don't know why it tries to link to them. Also, this bug seems to happen when an existing kernel is reinstalled when the SUSE patch number gets bumped. In this case the upstream kernel version 5.11.4 stayed the same but the SUSE patch number went from 1.2 to 1.3 so the kernel was reinstalled. I believe the same thing happened with 20210222 when Alex reported this, kernel remained 5.10.16 but the SUSE patch also change 1.2->1.3. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c32 --- Comment #32 from Stefan Dirsch --- Thanks. Sounds like an interesting observation. So kernels with same version number but different patchlevel 1.2/1.3 result in the same kernel modules path. Maybe I can reproduce the issue with such kernels now. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c34 --- Comment #34 from Stefan Dirsch --- Hmm. After updating kernel-default kernel-default-devel kernel-devel from 5.11.2-1 to 5.11.4-1 kernel modules have been built and installed and no dangling symlinks created. X works fine, modules are loaded and active. # find . -name nvidia* | xargs ls -ld drwxr-xr-x 2 root root 4096 Feb 24 23:42 ./5.10.16-1-default/kernel/drivers/net/ethernet/nvidia drwxr-xr-x 2 root root 4096 Mar 8 11:15 ./5.11.2-1-default/kernel/drivers/net/ethernet/nvidia -rw-r--r-- 1 root root 3761000 Mar 16 21:59 ./5.11.2-1-default/updates/nvidia-drm.ko -rw-r--r-- 1 root root 49582696 Mar 16 21:59 ./5.11.2-1-default/updates/nvidia.ko -rw-r--r-- 1 root root 2203392 Mar 16 21:59 ./5.11.2-1-default/updates/nvidia-modeset.ko -rw-r--r-- 1 root root 40844136 Mar 16 21:59 ./5.11.2-1-default/updates/nvidia-uvm.ko drwxr-xr-x 2 root root 4096 Mar 16 22:03 ./5.11.4-1-default/kernel/drivers/net/ethernet/nvidia -rw-r--r-- 1 root root 3761000 Mar 16 22:06 ./5.11.4-1-default/updates/nvidia-drm.ko -rw-r--r-- 1 root root 49582696 Mar 16 22:06 ./5.11.4-1-default/updates/nvidia.ko -rw-r--r-- 1 root root 2203248 Mar 16 22:06 ./5.11.4-1-default/updates/nvidia-modeset.ko -rw-r--r-- 1 root root 40844608 Mar 16 22:06 ./5.11.4-1-default/updates/nvidia-uvm.ko Unfortunately I don't have any kernel packages available for testing with same release but different patch number ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c36 --- Comment #36 from Stefan Dirsch --- Tried installing same kernel packages version 5.11.4-1 (rpm --force), but still same result. :-( -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c38 --- Comment #38 from Stefan Dirsch --- Ok. I was able to download 5.11.4-1.2 and 5.11.4-1.3 packages and installed both. Result then is # find /lib/modules/ -name nvidia*|xargs ls -ld drwxr-xr-x 2 root root 4096 Feb 24 23:42 /lib/modules/5.10.16-1-default/kernel/drivers/net/ethernet/nvidia drwxr-xr-x 2 root root 4096 Mar 16 23:01 /lib/modules/5.11.4-1-default/kernel/drivers/net/ethernet/nvidia -rw-r--r-- 1 root root 3761000 Mar 16 23:01 /lib/modules/5.11.4-1-default/updates/nvidia-drm.ko -rw-r--r-- 1 root root 49582696 Mar 16 23:01 /lib/modules/5.11.4-1-default/updates/nvidia.ko -rw-r--r-- 1 root root 2203248 Mar 16 23:01 /lib/modules/5.11.4-1-default/updates/nvidia-modeset.ko -rw-r--r-- 1 root root 40844608 Mar 16 23:01 /lib/modules/5.11.4-1-default/updates/nvidia-uvm.ko So still works for me. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c40 --- Comment #40 from Stefan Dirsch --- But anyway I kind of doubt it's really a good idea having two kernels installed using the same kernel modules directory, i.e. with a massive number of file conflicts. Since both use /lib/modules/5.11.4-1-default ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c42 Paolo Stivanin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pstivanin@suse.com --- Comment #42 from Paolo Stivanin --- I was on 20210307, all good. Then updated to 20210312 and drivers were not loaded. Also with 20210315 they weren't being loaded. $ find /lib/modules/ -name nvidia*|xargs ls -ld drwxr-xr-x 1 root root 30 Mar 8 17:59 /lib/modules/5.11.2-1-default/kernel/drivers/net/ethernet/nvidia -rw-r--r-- 1 root root 3761168 Mar 8 18:03 /lib/modules/5.11.2-1-default/updates/nvidia-drm.ko -rw-r--r-- 1 root root 49582648 Mar 8 18:03 /lib/modules/5.11.2-1-default/updates/nvidia.ko -rw-r--r-- 1 root root 2203328 Mar 8 18:03 /lib/modules/5.11.2-1-default/updates/nvidia-modeset.ko -rw-r--r-- 1 root root 40844304 Mar 8 18:03 /lib/modules/5.11.2-1-default/updates/nvidia-uvm.ko drwxr-xr-x 1 root root 30 Mar 16 16:32 /lib/modules/5.11.4-1-default/kernel/drivers/net/ethernet/nvidia lrwxrwxrwx 1 root root 52 Mar 16 16:32 /lib/modules/5.11.4-1-default/weak-updates/updates/nvidia-drm.ko -> /lib/modules/5.10.16-1-default/updates/nvidia-drm.ko lrwxrwxrwx 1 root root 48 Mar 16 16:32 /lib/modules/5.11.4-1-default/weak-updates/updates/nvidia.ko -> /lib/modules/5.10.16-1-default/updates/nvidia.ko lrwxrwxrwx 1 root root 56 Mar 16 16:32 /lib/modules/5.11.4-1-default/weak-updates/updates/nvidia-modeset.ko -> /lib/modules/5.10.16-1-default/updates/nvidia-modeset.ko lrwxrwxrwx 1 root root 52 Mar 16 16:32 /lib/modules/5.11.4-1-default/weak-updates/updates/nvidia-uvm.ko -> /lib/modules/5.10.16-1-default/updates/nvidia-uvm.ko I then proceeded with reinstalling all nvidia related packages, and that did solve the issue for me -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c44 --- Comment #44 from Axel Braun --- (In reply to Stefan Dirsch from comment #43)

So it seems users are updating kernel-default, but not kernel-default-devel.

Hm, zypper dup should resolve/force this. Maybe it does not? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c46 --- Comment #46 from Guenter Stoehr --- Created attachment 847339 --> http://bugzilla.opensuse.org/attachment.cgi?id=847339&action=edit 2021-03-11_zypper-history.log and 2021-03-15_zypper-history.log Find attached 2 extracts of /var/log/zypp/history of the pc of related bug 1183480: 1. 2021-03-11_zypper-history.log: Updating Leap 15.2 from 5.3.18-lp152.63-default to 5.3.18-lp152.66-default. The nvidia-drivers don't work. 2. 2021-03-15_zypper-history.log: fixing the problem by re-installing "kernel-default-devel" first (didn't work) and then "kernel-devel" second. Then it worked. Hope this has some use... :) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c48 --- Comment #48 from Stefan Dirsch --- Thanks a lot for your input @B ! To me your arguments make 100% sense. I vote for 3) Make it that minor patch updates (5.11.4-1.2->5.11.4-1.3) work like regular updates (for example 5.11.4->5.11.6) where kernels are not replaced but installed alongside each other and use different directories. I would call it broken to use the same /lib/modules/<kernel-version-omitting-patch-version> directory for different kernel patchversions - especially when you are supposed to install both at the same time and switch between for booting. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c50 --- Comment #50 from Stefan Dirsch --- Hmm. I could not reproduce that /lib/modules/<kernel-version>/updates contents gets removed when updating from kernel-default 5.11.4-1.2 to 5.11.4-1.3. -- You are receiving this mail because: You are on the CC list for the bug.

sudo rpm -eh -vv kernel-default-5.11.4-1.3.x86_64 *** removed part of output *** D: %postun(kernel-default-5.11.4-1.3.x86_64): waitpid(18562) rc 18562 status 0 D: Plugin: calling hook scriptlet_post in syslog plugin D: %triggerpostun(nvidia-gfxG05-kmp-default-460.56_k5.10.16_1-35.1.x86_64):

rpm -q --scripts nvidia-gfxG05-kmp-default-460.56_k5.10.16_1-35.1.x86_64

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c52 --- Comment #52 from B --- Did some more digging, looking at the rpm scripts in kernel-default there doesn't seem to be anything that would manipulate /lib/modules/$kernel/updates/ directory so I tried removing kernel-default with the rpm tool with verbose output: scriptlet start fdio: 2 writes, 172 total bytes in 0.000011 secs D: %triggerpostun(nvidia-gfxG05-kmp-default-460.56_k5.10.16_1-35.1.x86_64): execv(/bin/sh) pid 19832 D: Plugin: calling hook scriptlet_fork_post in prioreset plugin D: Plugin: calling hook scriptlet_fork_post in selinux plugin ++ find /lib/modules -mindepth 1 -maxdepth 1 -type d + for dir in $(find /lib/modules -mindepth 1 -maxdepth 1 -type d) + '[' '!' -d /lib/modules/5.10.12-1-default/kernel ']' + test -d /lib/modules/5.10.12-1-default/updates + rm -f '/lib/modules/5.10.12-1-default/updates/nvidia*.ko' + for dir in $(find /lib/modules -mindepth 1 -maxdepth 1 -type d) + '[' '!' -d /lib/modules/5.10.12-1khz/kernel ']' + for dir in $(find /lib/modules -mindepth 1 -maxdepth 1 -type d) + '[' '!' -d /lib/modules/5.10.14-1-default/kernel ']' + test -d /lib/modules/5.10.14-1-default/updates + rm -f '/lib/modules/5.10.14-1-default/updates/nvidia*.ko' + for dir in $(find /lib/modules -mindepth 1 -maxdepth 1 -type d) + '[' '!' -d /lib/modules/5.10.16-1-default/kernel ']' + test -d /lib/modules/5.10.16-1-default/updates + rm -f '/lib/modules/5.10.16-1-default/updates/nvidia*.ko' + for dir in $(find /lib/modules -mindepth 1 -maxdepth 1 -type d) + '[' '!' -d /lib/modules/5.11.2-1-default/kernel ']' + test -d /lib/modules/5.11.2-1-default/updates + rm -f '/lib/modules/5.11.2-1-default/updates/nvidia*.ko' + for dir in $(find /lib/modules -mindepth 1 -maxdepth 1 -type d) + '[' '!' -d /lib/modules/5.11.2-1khz/kernel ']' + for dir in $(find /lib/modules -mindepth 1 -maxdepth 1 -type d) + '[' '!' -d /lib/modules/5.11.4-1-default/kernel ']' + test -d /lib/modules/5.11.4-1-default/updates + rm -f /lib/modules/5.11.4-1-default/updates/nvidia-drm.ko /lib/modules/5.11.4-1-default/updates/nvidia.ko /lib/modules/5.11.4-1-default/updates/nvidia-modeset.ko /lib/modules/5.11.4-1-default/updates/nvidia-uvm.ko + for dir in $(find /lib/modules -mindepth 1 -maxdepth 1 -type d) + '[' '!' -d /lib/modules/5.11.4-1-1khz/kernel ']' *** removed part of output *** So it seems when kernel-default is being removed the post uninstall script of nvidia-gfxG05-kmp-default is triggered. This looks like the right script: postuninstall scriptlet (using /bin/sh): flavor=default if [ "$1" = 0 ] ; then # Avoid accidental removal of G alternative (bnc#802624) if [ ! -f /usr/lib/nvidia/alternate-install-present-$flavor ]; then /usr/sbin/update-alternatives --remove alternate-install-present /usr/lib/nvidia/alternate-install-present-$flavor # get rid of *all* nvidia kernel modules when uninstalling package (boo#1180010) for dir in $(find /lib/modules -mindepth 1 -maxdepth 1 -type d); do test -d $dir/updates && rm -f $dir/updates/nvidia*.ko done fi # cleanup of bnc# 1000625 rm -f /usr/lib/tmpfiles.d/nvidia-logind-acl-trick-G05.conf fi Seems to be clear that if Nvidia kernel modules are installed before a minor patch version kernel "upgrade" there won't be any module files after. Also, if anyone will try to test this be careful with the rpm command, even though I told it to erase a specific version of kernel-default for some reason it removed all of them. Luckily I run some custom kernels and those weren't touched. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c54 --- Comment #54 from Stefan Dirsch --- Also during an update %triggerpostun is the last which is being executed. https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#orderi... At that time there should exist a /lib/modules/<kernel-version>/kernel/ directory. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c56 --- Comment #56 from Stefan Dirsch --- No, that's just a package update. First the files of the new package are installed, then the files of the old package which are not part of the new package are uninstalled. At last the %triggerpostun of nvidia-gfxG05-kmp-default is running. At that point there is kernel/ subdir. Check this out. https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#orderi... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c58 --- Comment #58 from Michael Pujos --- Created attachment 847362 --> http://bugzilla.opensuse.org/attachment.cgi?id=847362&action=edit lizypp logs for 5.11.4-1.2 to 5.11.4-1.3 kernel update I've extracted the libzypp logs for my update from 5.11.4-1.2 to 5.11.4-1.3 that caused this issue a few days ago. at 15:15:38, nvidia modules are compiled and just after (15:15:44) |kernel-default|5.11.4-1.2| is removed. I'm no expert in how exactly this is supposed to work, but this log shows the exact ordering of install/uninstall of all kernel- package and the nvidia module compilation -- You are receiving this mail because: You are on the CC list for the bug.

...

...

# 2021-03-11 19:29:11 kernel-devel-5.3.18-lp152.66.2.noarch.rpm installed ok # Additional rpm output: # Changing symlink /usr/src/linux from linux-5.3.18-lp152.63 to

...

...

# Additional rpm output: # Changing symlink /usr/src/linux-obj/x86_64/default from ../../linux-5.3.18-lp152.63-obj/x86_64/default to ../../linux-5.3.18-lp152.66-obj/x86_64/default # <<<

...

2021-03-11 19:29:25|install|kernel-default-devel|5.3.18-lp152.66.2|x86_64||repo-update|b441cf0df1888d8f6d0d9c0065ada4eeed07f190540104bee04efda96f482ea5| <<< 2021-03-11 19:29:25|install|yast2-security|4.2.19-lp152.2.12.1|noarch||repo-update|c38b83c76852a3a481564af8495164bf55574253c7d24a1351f900c208ae2a16| {...] 2021-03-11 19:29:32|install|glibc-locale|2.26-lp152.26.6.1|x86_64||repo-update|91eb4247586fffb10446e894db6b25e29aeb1d14496e7e02e8a98b1d8ac50be1| 2021-03-11 19:33:40|command|root@gs3lnx|'zypper' 'update'|

...

# 2021-03-11 19:34:12 nvidia-gfxG05-kmp-default-460.56_k5.3.18_lp152.19-lp152.35.1.x86_64.rpm installed ok # Additional rpm output: # make: *** No rule to make target 'kernelrelease'. Stop. # make: Entering directory '/usr/src/linux-5.3.18-lp152.66-obj/x86_64/default' # make: *** No rule to make target 'modules'. Stop. # make: Leaving directory '/usr/src/linux-5.3.18-lp152.66-obj/x86_64/default' # /usr/src/kernel-modules/nvidia-460.56-default / # make[1]: *** /lib/modules//source: No such file or directory. Stop. # make: *** [Makefile:80: modules] Error 2 # / # rm: cannot remove '/lib/modules//updates/nvidia*.ko': No such file or

...

...

2021-03-11 19:35:05|install|kernel-default|5.3.18-lp152.66.2|x86_64||repo-update|5e59d75b409d042614573c01acef5fcdf2c05c3332f9ed75fdc58a09391bc540| <<< ################ It seems to me, that kernel-devel and kernel-default-devel are installed first,

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c60 --- Comment #60 from Guenter Stoehr --- Sorry for writing another comment to this bug, but I have a problem and some questions. And I don't know whether the other bug is still active. I updated the PC of my son from >>> linux-5.3.18-lp152.63 to linux-5.3.18-lp152.66.<<< So this is not a patch-level-issue, as I suppose. Is that correct? But the zypper-log contains the trouble very clearly (extract from /var/log/zypp/history), as far as I can understand it: I marked the critical points with >>> <<< ################ 2021-03-11 19:29:02|command|root@gs3lnx|'zypper' 'update'| # 2021-03-11 19:29:02 ImageMagick-config-7-SUSE-7.0.7.34-lp152.12.12.1.x86_64.rpm installed ok # Additional rpm output: # update-alternatives: warning: forcing reinstallation of alternative /etc/ImageMagick-7-SUSE because link group ImageMagick-7 is broken # 2021-03-11 19:29:02|install|ImageMagick-config-7-SUSE|7.0.7.34-lp152.12.12.1|x86_64||repo-update|d1232473707f855d5799989fdcef875a7ffd33c10fe2152a10a4a9e89d9d4635| 2021-03-11 19:29:03|install|glibc|2.26-lp152.26.6.1|x86_64||repo-update|19d26c98080eedea689b4c4dacf5a78a3576e17fed2ee5cc793f2fcdbf069948| 2021-03-11 19:29:03|install|glibc-32bit|2.26-lp152.26.6.1|x86_64||repo-update|85c1d794a63b5ad712f9063b8229c4265fc1b2b97672af9814a447f15e2eee6d| 2021-03-11 19:29:04|install|kernel-macros|5.3.18-lp152.66.2|noarch||repo-update|69aba45ed532b7790e241572beaf932525f2bde457cab4322a34cbea1e5a5629| 2021-03-11 19:29:04|install|python3-bind|9.16.6-lp152.14.13.1|noarch||repo-update|2177f66e8880fa8568c8f1b9a96bea301b6881e2e8aabafbcd02049a64b97889| 2021-03-11 19:29:04|install|python3-six|1.14.0-lp152.4.3.1|noarch||repo-update|4e9ba0e615207528f5b49213c24036fab8a5a96748be895ecafed9dafd5e6c1d| 2021-03-11 19:29:04|install|yast2-logs|4.2.92-lp152.2.22.1|x86_64||repo-update|63455eb22c18f0b44bd6f55b7562471ee645a186ff8f422607c57e3eeb8d4dea| 2021-03-11 19:29:04|install|glibc-extra|2.26-lp152.26.6.1|x86_64||repo-update|bcb9faa40f8e294321f73dbc9364f2b284c2ba729476993770b34dfcf8a709a9| 2021-03-11 19:29:04|install|libavahi-common3-32bit|0.7-lp152.3.6.1|x86_64||repo-update|a0c70d299c7665334985664c88fda902cc7c33bab292ab7448c28e40d8d551ce| linux-5.3.18-lp152.66 # 2021-03-11 19:29:11|install|kernel-devel|5.3.18-lp152.66.2|noarch||repo-update|59c6fde99dcecd80e8062de952a51a79dee9a6cc927b1dc00ab927d3c71151ca| <<< # 2021-03-11 19:29:11 yast2-4.2.92-lp152.2.22.1.x86_64.rpm installed ok # Additional rpm output: # Updating /etc/sysconfig/yast2 ... # linux-5.3.18-lp152.63 2021-03-11 19:29:11|install|yast2|4.2.92-lp152.2.22.1|x86_64||repo-update|fb1d0545ead88acac0b882ff1f18cb234e242fd5b434c4b8e8fa968f997970b6| [...] 2021-03-11 19:29:24|install|libavahi-client3-32bit|0.7-lp152.3.6.1|x86_64||repo-update|64f11eeee8405f32e029b912213781de2b19daaad2a7777fee2c7cf9fedc0c64| # 2021-03-11 19:29:25 kernel-default-devel-5.3.18-lp152.66.2.x86_64.rpm installed ok directory # install: cannot stat '/usr/src/kernel-modules/nvidia-460.56-default/nvidia*.ko': No such file or directory # depmod: WARNING: could not open modules.order at /lib/modules/5.3.18-lp152.19-default: No such file or directory # depmod: WARNING: could not open modules.builtin at /lib/modules/5.3.18-lp152.19-default: No such file or directory # EFI variables are not supported on this system # # Modprobe blacklist files have been created at /etc/modprobe.d to prevent Nouveau from loading. This can be reverted by deleting /etc/modprobe.d/nvidia-*.conf. # # *** Reboot your computer and verify that the NVIDIA graphics driver can be loaded. *** # # grep: /etc/sysconfig/kernel: No such file or directory # 2021-03-11 19:34:12|install|nvidia-gfxG05-kmp-default|460.56_k5.3.18_lp152.19-lp152.35.1|x86_64||download.nvidia.com-leap|616e8a54d9b5664bcb2b1e92327caa837ceef11a09ea9e081956d46a2dadd97d| # 2021-03-11 19:34:14 nvidia-computeG05-460.56-lp152.35.1.x86_64.rpm installed ok # Additional rpm output: # /sbin/ldconfig: File /usr/lib64/libkfontinstui.so.5 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libjavascriptcoregtk-4.0.so.18 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libwebkit2gtk-4.0.so.37.49.9 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinstui.so.5.18.6 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libwebkit2gtk-4.0.so.37 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinst.so.5 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinst.so.5.18.6 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libjavascriptcoregtk-4.0.so.18.17.13 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinstui.so.5 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libjavascriptcoregtk-4.0.so.18 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libwebkit2gtk-4.0.so.37.49.9 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinstui.so.5.18.6 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libwebkit2gtk-4.0.so.37 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinst.so.5 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinst.so.5.18.6 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libjavascriptcoregtk-4.0.so.18.17.13 is empty, not checked. <<< [...] then the nvidia-drivers and kernel-default is installed later. And the installation of nvidia fails and those files in usr/lib64 are empty. What are those files good for? How can I fix it? Is it sufficient to re-install those libs? You can find the whole zypper-history of that day as attachment to comment #46 . And I have another Leap-15.2-system to update. Same configuration, that means linux-5.3.18-lp152.63 and nvidia-graphiccard. I started the update and stopped it, when zypper has told, what it was intented to update: ================================================ Die folgenden 4 NEUEN Pakete werden installiert: kernel-default 5.3.18-lp152.66.2 x86_64 Main Update Repository openSUSE kernel-default-devel 5.3.18-lp152.66.2 x86_64 Main Update Repository openSUSE kernel-devel 5.3.18-lp152.66.2 noarch Main Update Repository openSUSE ================================================ Is that the right order to install those packages? Or do I have to expect teh same trouble again? Thank you for some answers in advance. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c62 --- Comment #62 from Stefan Dirsch --- (In reply to Guenter Stoehr from comment #60)

Sorry for writing another comment to this bug, but I have a problem and some questions. And I don't know whether the other bug is still active. I updated the PC of my son from >>> linux-5.3.18-lp152.63 to linux-5.3.18-lp152.66.<<< So this is not a patch-level-issue, as I suppose. Is that correct?

No, this also looks like a patch-level issue. patch lp152.63 vs. lp 152.66. But in the logs you attached I see an update to lp152.62

19:29:04|install|kernel-macros|5.3.18-lp152.66.2|noarch||repo- update|69aba45ed532b7790e241572beaf932525f2bde457cab4322a34cbea1e5a5629| [...] # 2021-03-11 19:29:11 kernel-devel-5.3.18-lp152.66.2.noarch.rpm installed ok # Additional rpm output: # Changing symlink /usr/src/linux from linux-5.3.18-lp152.63 to linux-5.3.18-lp152.66 [...] # 2021-03-11 19:29:25 kernel-default-devel-5.3.18-lp152.66.2.x86_64.rpm installed ok

...

...

...

# Additional rpm output: # Changing symlink /usr/src/linux-obj/x86_64/default from ../../linux-5.3.18-lp152.63-obj/x86_64/default to ../../linux-5.3.18-lp152.66-obj/x86_64/default 2021-03-11 nvidia-gfxG05-kmp-default-460.56_k5.3.18_lp152.19-lp152.35.1.x86_64.rpm installed ok # Additional rpm output: # make: *** No rule to make target 'kernelrelease'. Stop. # make: Entering directory '/usr/src/linux-5.3.18-lp152.66-obj/x86_64/default'

Hmm. Seems installation of kernel-default-devel-5.3.18-lp152.66.2.x86_64.rpm failed if make -sC /usr/src/linux-obj/x86_64/default kernelrelease doesn't work. I suggest to reinstall kernel-default-devel package.

# Additional rpm output: # /sbin/ldconfig: File /usr/lib64/libkfontinstui.so.5 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libjavascriptcoregtk-4.0.so.18 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libwebkit2gtk-4.0.so.37.49.9 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinstui.so.5.18.6 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libwebkit2gtk-4.0.so.37 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinst.so.5 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinst.so.5.18.6 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libjavascriptcoregtk-4.0.so.18.17.13 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinstui.so.5 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libjavascriptcoregtk-4.0.so.18 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libwebkit2gtk-4.0.so.37.49.9 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinstui.so.5.18.6 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libwebkit2gtk-4.0.so.37 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinst.so.5 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libkfontinst.so.5.18.6 is empty, not checked. # /sbin/ldconfig: File /usr/lib64/libjavascriptcoregtk-4.0.so.18.17.13 is empty, not checked.

This is unrelated to this ticket.

It seems to me, that kernel-devel and kernel-default-devel are installed first, then the nvidia-drivers and kernel-default is installed later.

Kind of, yes.

And the installation of nvidia fails

Yes. See above.

and those files in usr/lib64 are empty. What are those files good for? How can I fix it? Is it sufficient to re-install those libs?

That's unrelated to this ticket.

You can find the whole zypper-history of that day as attachment to comment #46

Ok. I remember.

And I have another Leap-15.2-system to update. Same configuration, that means linux-5.3.18-lp152.63 and nvidia-graphiccard. I started the update and stopped it, when zypper has told, what it was intented to update: ================================================ Die folgenden 4 NEUEN Pakete werden installiert: kernel-default 5.3.18-lp152.66.2 x86_64 Main Update Repository openSUSE kernel-default-devel 5.3.18-lp152.66.2 x86_64 Main Update Repository openSUSE kernel-devel 5.3.18-lp152.66.2 noarch Main Update Repository openSUSE ================================================ Is that the right order to install those packages? Or do I have to expect the same trouble again?

I don't know. In the worst case you need to reinstall nvidia-gfxG05-kmp-default or kernel-default-devel package. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 Paolo Stivanin changed: What |Removed |Added ---------------------------------------------------------------------------- CC|pstivanin@suse.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c65 --- Comment #65 from Stefan Dirsch --- Indeed. 2021-03-15 15:15:44|remove |kernel-default|5.11.4-1.2|x86_64|| [...] 2021-03-15 15:16:31|install|kernel-default|5.11.4-1.3|x86_64||http-download.opensuse.org-ade0eb17|d1fa5e4c267fe3bb23f02258b940b4b6060f873ab480cee7a93c131258653abb| ... Oh. Well. This means I can forget about cleaning up of nvidia modules and need to revert what I implemented for boo#1164520. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c67 --- Comment #67 from B --- zypper -vv didn't really give more information on how those installations are handled, it just had more info on repo related stuff.

sudo zypper -vv in --oldpackage kernel-default-5.11.4-1.3.x86_64.rpm

Parts of output: The following NEW package is going to be installed: kernel-default 5.11.4-1.3 x86_64 Plain RPM files cache openSUSE The following package is going to be REMOVED: kernel-default 5.11.4-1.2 x86_64 openSUSE The following package requires a system reboot: kernel-default 5.11.4-1.3 x86_64 Plain RPM files cache openSUSE 1 new package to install, 1 to remove. Checking for file conflicts: ...................................................................................................................................................................................................................................[done] (1/2) Removing kernel-default-5.11.4-1.2.x86_64 ................................................................................................................................................................................................................[done] (2/2) Installing: kernel-default-5.11.4-1.3.x86_64 .............................................................................................................................................................................................................[done] CommitResult (total 2, done 2, error 0, skipped 0, updateMessages 0) The summary and the progress shows it happening in 2 steps: 1) remove old, 2) install new. Compared to regular package updates:

sudo zypper dup

The following 2 packages are going to be upgraded: iscan iscan-data Checking for file conflicts: ...................................................................................................................................................................................................................................[done] (1/2) Installing: iscan-data-1.39.1-5.30.noarch ................................................................................................................................................................................................................[done] (2/2) Installing: iscan-2.30.4-5.30.x86_64 .....................................................................................................................................................................................................................[done] -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c69 --- Comment #69 from B --- (In reply to Stefan Dirsch from comment #68)

Fixed this issue now. Should fix this issue for TW and Leap.

------------------------------------------------------------------- Thu Mar 18 15:07:02 UTC 2021 - Stefan Dirsch

- Unfortunately removing no longer used kernel modules via %triggerpostun doesn't work since kernel updates are not considered "atomar" when using YaST/zypper (only safe when using rpm) [boo#1182666, boo#1164520]

I hope there will be still a driver update this week.

I created a kernel bug report 1183739, maybe the kernel maintainers could make so that kernels are installed into their own directories or propose some other fixes because never removing those modules is not ideal. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1182666 http://bugzilla.opensuse.org/show_bug.cgi?id=1182666#c71 Sebastian Turza��ski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dpbasti@wp.pl --- Comment #71 from Sebastian Turza��ski --- I think I may have similar issue kernel: nvidia: disagrees about version of symbol module_layout this happened after June2021 updates I thought I had 2 kernel versions installed but then made sure only 1 was present and forced reinstall of nvidia but still the same error my kernel packages : sudo rpm -qa |grep kernel kernel-firmware-qcom-20210503-1.2.noarch kernel-firmware-network-20210503-1.2.noarch kernel-firmware-radeon-20210503-1.2.noarch kernel-firmware-ath11k-20210503-1.2.noarch kernel-firmware-realtek-20210503-1.2.noarch kernel-firmware-sound-20210503-1.2.noarch kernel-firmware-usb-network-20210503-1.2.noarch kernel-firmware-qlogic-20210503-1.2.noarch kernel-firmware-chelsio-20210503-1.2.noarch kernel-firmware-bnx2-20210503-1.2.noarch kernel-firmware-all-20210503-1.2.noarch kernel-firmware-ti-20210503-1.2.noarch kernel-firmware-marvell-20210503-1.2.noarch kernel-firmware-atheros-20210503-1.2.noarch kernel-firmware-liquidio-20210503-1.2.noarch kernel-firmware-bluetooth-20210503-1.2.noarch kernel-firmware-mediatek-20210503-1.2.noarch kernel-firmware-serial-20210503-1.2.noarch kernel-firmware-intel-20210503-1.2.noarch kernel-firmware-nfp-20210503-1.2.noarch kernel-firmware-nvidia-20210503-1.2.noarch kernel-firmware-mellanox-20210503-1.2.noarch kernel-firmware-dpaa2-20210503-1.2.noarch kernel-firmware-iwlwifi-20210503-1.2.noarch kernel-firmware-amdgpu-20210503-1.2.noarch purge-kernels-service-0-8.1.noarch kernel-firmware-i915-20210503-1.2.noarch kernel-firmware-ueagle-20210503-1.2.noarch kernel-firmware-brcm-20210503-1.2.noarch kernel-firmware-mwifiex-20210503-1.2.noarch kernel-firmware-media-20210503-1.2.noarch kernel-firmware-ath10k-20210503-1.2.noarch kernel-firmware-platform-20210503-1.2.noarch kernel-syms-5.12.9-1.1.x86_64 kernel-firmware-prestera-20210503-1.2.noarch kernel-devel-5.12.9-1.1.noarch kernel-default-devel-5.12.9-1.1.x86_64 kernel-source-5.12.9-1.1.noarch kernel-default-5.12.9-1.1.x86_64 kernel-macros-5.12.9-1.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.