On Monday 03 May 2021, J. Merkel wrote:

Hi Michael, Andrei

thanks for your swift responses! One correction: I mentioned the wrong kernel version - its 5.11.15 for build 20210425.

Michael - I've tried your suggestion but it failed complaining about a "mismatch" in nvidia-gfxG05-kmp-default-460.73.01_k5.11.11_1-37.1.x86_64.rpm [1](The file I've tee'd the output to got overwritten so regrettably I can't provide more details, grmbl) The kernel source install for 5.11.15 looked OK to me.

Your comment and Andrei's point stating the nvidia modules are compiled made me try to update to the latest available build 20210429 which employs kernel 5.12.0. (Not knowing much about the "nvidia issue" I assumed nvidia are trying to keep some stuff from others looking into, thus forcing download of some pre-complied objects rather than to compile in situ)

After the change to 5.12.0 all is fine again, I'm writing this mail on the system.

One observation: I was following the update closely (which I usually don't do ;-)) and was concerned when I saw:

------------------------------------------------------------------------------------------------------------

.......BTF [M] /usr/src/kernel-modules/nvidia-460.73.01-default/nvidia.ko Skipping BTF generation for /usr/src/kernel-modules/nvidia-460.73.01-default/ nvidia.ko due to unavailability of vmlinux make[2]: Verzeichnis „/usr/src/linux-5.12.0-1-obj/x86_64/default“ wird verlassen make[1]: Leaving directory '/usr/src/linux-5.12.0-1' ld -r -o nv-linux.o \ nvidia.mod.o nvidia/nv-interface.o ld: cannot find nvidia/nv-interface.o: No such file or directory make: *** [Makefile:113: nv-linux.o] Error 1 / depmod: WARNING: could not open modules.order at /lib/modules/5.12.0-1-default: No such file or directory depmod: WARNING: could not open modules.builtin at /lib/modules/5.12.0-1- default: No such file or directory

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 warning: %triggerin(nvidia-gfxG05-kmp-default-460.73.01_k5.11.11_1-37.1.x86_64) scriptlet failed, exit status 1

........ ---------------------------------------------------------------------------------------------------------------

Any idea whether this could turn into something serious or can it be ignored?

br

Juergen

If I grep /var/log/zypp/history for the above errors I can find all of them from various past updates all the way back to kernel 5.7.7-1-default. I'm not sure whether any of them are associated with past nvidia update issues. I've certainly not been paying any attention to them. In the past should an update cause my desktop to fail to boot to the sddm login screen, I have most often tried a forced reinstall of everything currently installed from the nvidia repo. More recently I have just tried rebuilding the module after someone here suggested that this was all that is necessary - perhaps that is insufficient in some cases, I'm not sure. Force reinstalls have often done the trick. Otherwise I just set my system to boot to the previous kernel - I don't think that has ever failed. I then raise an issue here, and wait for some suggestions or explanation. Often the explanation is along the lines the kernel API's have been changed and we're waiting for nvidia to catchup. It isn't essential that my desktop runs the very latest kernel, so this works fine for me. Michael