# 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 <guenter.stoehr@gs-consult-ac.de> --- 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.