http://bugzilla.opensuse.org/show_bug.cgi?id=1131028 http://bugzilla.opensuse.org/show_bug.cgi?id=1131028#c3 Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(carlos.e.r@opensu | |se.org) | --- Comment #3 from Carlos Robinson --- First I installed the 15.1 kernel and 15.1 Nvidia driver, which failed (Bug 1131029). That Nvidia rpm did not inform of the failure to build the kernel module. Then I reverted. I uninstalled 15.1 kernel and Nvidia modules, and forced reinstall of 15.0 Nvidia modules. The Nvidia rpm again failed to build the kernel module (for a different reason) but kept silent about the error. I found out the error and solved it - basically the kernel rpms of 15.0 have to be reinstalled to create the appropriate symlinks. The problem reported here, however, is the failure of the Nvidia rpms to abort on Make error and report the issue. It continues installing dracut and claims success - when it failed. Why Make failed is irrelevant now. cer@Telcontar:~> uname -r 4.12.14-lp150.12.48-default cer@Telcontar:~> rpm -qa | grep kernel kernel-source-4.12.14-lp150.12.45.1.noarch texlive-l3kernel-2017.133.svn44483-lp150.5.4.noarch kernel-source-4.12.14-lp150.12.48.1.noarch texlive-l3kernel-doc-2017.133.svn44483-lp150.5.4.noarch kernel-syms-4.12.14-lp150.12.48.1.x86_64 kernel-devel-4.12.14-lp150.12.48.1.noarch kernel-firmware-20190118-lp150.2.12.1.noarch kernel-devel-4.12.14-lp150.12.45.1.noarch kernel-default-devel-4.12.14-lp150.12.48.1.x86_64 kernel-docs-4.12.14-lp150.12.48.1.noarch nfs-kernel-server-2.1.1-lp150.4.6.1.x86_64 kernel-macros-4.12.14-lp150.12.48.1.noarch kernel-default-4.12.14-lp150.12.48.1.x86_64 cer@Telcontar:~> rpm -qa | grep -i nvidia nvidia-computeG03-340.107-lp150.12.2.x86_64 nvidia-uvm-gfxG03-kmp-default-340.107_k4.12.14_lp150.11-lp150.12.1.x86_64 x11-video-nvidiaG03-340.107-lp150.12.2.x86_64 nvidia-glG03-340.107-lp150.12.2.x86_64 nvidia-gfxG03-kmp-default-340.107_k4.12.14_lp150.11-lp150.12.2.x86_64 cer@Telcontar:~> If you wish, I can try to reproduce the error and post the thousand of lines from rpm output... But IMHO, it is pointless. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1131028 http://bugzilla.opensuse.org/show_bug.cgi?id=1131028#c5 Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(carlos.e.r@opensu | |se.org) | --- Comment #5 from Carlos Robinson --- Ok. Yes, the trick seems to be to reinstall the kernel links However, the problem I report is that the "nvidia-gfxG03-kmp-default-340.107_k4.12.14_lp150.11-lp150.12.1.x86_64.rpm" doesn't say "I failed to build the module, installation failed". Look. With the rpms I listed above (#3) I intentionally break the link: Telcontar:/usr/src/linux-obj/x86_64 # l default lrwxrwxrwx 1 root root 50 Apr 1 19:02 default -> ../../linux-4.12.14-lp151.12.48-obj/x86_64/default (I edited 150 to 151 in the target name) The target does not exist. Now, I try to install the nvidia-gfxG03-kmp-default rpm. Look: [paste begin] Telcontar:/data/... # rpm --install --force nvidia-gfxG03-kmp-default-340.107_k4.12.14_lp150.11-lp150.12.2.x86_64.rpm make: *** /usr/src/linux-obj/x86_64/default: No such file or directory. Stop. make: *** /usr/src/linux-obj/x86_64/default: No such file or directory. Stop. /usr/src/kernel-modules/nvidia-340.107-default / NVIDIA: calling KBUILD... make[1]: *** /lib/modules//source: No such file or directory. Stop. NVIDIA: left KBUILD. nvidia.ko failed to build! make: *** [Makefile:192: nvidia.ko] Error 1 / install: cannot stat '/usr/src/kernel-modules/nvidia-340.107-default/nvidia.ko': No such file or directory depmod: WARNING: could not open modules.order at /lib/modules/4.12.14-lp150.11-default: No such file or directory depmod: WARNING: could not open modules.builtin at /lib/modules/4.12.14-lp150.11-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. *** [paste pause] Notice the message that starts with: "reboot". It is claiming success. But see above: "nvidia.ko failed to build!" Make failed with "Error 1". THAT is the problem I'm reporting. Not why it failed, but that it fails and *claims success*. rpm then calls dracut to create initrd - why, when there is no module? [paste continues] *** Reboot your computer and verify that the NVIDIA graphics driver can be loaded. *** Creating initrd: /boot/initrd-4.12.14-lp150.12.48-default dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force --force-drivers "pata_jmicron ata_piix ata_generic netconsole xennet xenblk" /boot/initrd-4.12.14-lp150.12.48-default 4.12.14-lp150.12.48-default dracut: *** Including module: bash *** dracut: *** Including module: systemd *** dracut: *** Including module: warpclock *** dracut: *** Including module: systemd-initrd *** dracut: *** Including module: i18n *** dracut: *** Including module: kernel-modules *** dracut: *** Including module: resume *** dracut: *** Including module: rootfs-block *** dracut: *** Including module: suse-xfs *** dracut: *** Including module: terminfo *** dracut: *** Including module: udev-rules *** dracut: Skipping udev rule: 40-redhat.rules dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules dracut: Skipping udev rule: 80-drivers-modprobe.rules dracut: *** Including module: dracut-systemd *** dracut: *** Including module: haveged *** dracut: *** Including module: usrmount *** dracut: *** Including module: base *** dracut: *** Including module: fs-lib *** dracut: *** Including module: shutdown *** dracut: *** Including module: suse *** dracut: *** Including modules done *** dracut: *** Installing kernel module dependencies and firmware *** dracut: *** Installing kernel module dependencies and firmware done *** dracut: *** Resolving executable dependencies *** dracut: *** Resolving executable dependencies done*** dracut: *** Hardlinking files *** dracut: *** Hardlinking files done *** dracut: *** Stripping files *** dracut: *** Stripping files done *** dracut: *** Generating early-microcode cpio image *** dracut: *** Constructing GenuineIntel.bin **** dracut: *** Store current command line parameters *** dracut: Stored kernel commandline: dracut: rd.driver.pre=pata_jmicron rd.driver.pre=ata_piix rd.driver.pre=ata_generic rd.driver.pre=netconsole rd.driver.pre=xennet rd.driver.pre=xenblk dracut: resume=UUID=4feaa6f5-38c4-4674-ae54-8e22389731a1 dracut: root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 rootfstype=ext4 rootflags=rw,relatime,lazytime,data=ordered dracut: *** Creating image file '/boot/initrd-4.12.14-lp150.12.48-default' *** dracut: *** Creating initramfs image file '/boot/initrd-4.12.14-lp150.12.48-default' done *** Telcontar:/data/... # [paste ends] It is not displayed here, but when this is done from YaST, *YaST* says *nothing* about the failure to build the kernel module. The first news that something is wrong is when video fails. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1131028 http://bugzilla.opensuse.org/show_bug.cgi?id=1131028#c7 Carlos Robinson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |--- --- Comment #7 from Carlos Robinson --- I said nothing about the build structure from Nvida head quarters. I said nothing about reverting the package install. The Make process errors are not reported to the user inside yast. Yast says that the package succeeded, and proceed to reboot. Surely you can add a message telling yast that there were problems with make. Write the log somewhere and tell. I only want YaST to tell the user that something happened. This situation is not acceptable. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1131028 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1131028 http://bugzilla.opensuse.org/show_bug.cgi?id=1131028#c13 --- Comment #13 from Stephan Schöttl --- If may add a comment: Apart from error messages, it would also be nice if the kernel module were built correctly. That's for my use case anyway. Thanks anyway for the analysis above. With this information I was finally able to build the modules after doing cd /usr/src/ && ln -s linux-4.12.14-lp151.28.7-obj linux-obj -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1131028 http://bugzilla.opensuse.org/show_bug.cgi?id=1131028#c16 --- Comment #16 from Stefan Dirsch --- Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1131028 http://bugzilla.opensuse.org/show_bug.cgi?id=1131028#c20 --- Comment #20 from Carlos Robinson --- (In reply to Stefan Dirsch from comment #18) ...

if you're interested. Closing as fixed ...

Yes, I'll test that when I notice the update on servers, thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1131028 http://bugzilla.opensuse.org/show_bug.cgi?id=1131028#c23 --- Comment #23 from Carlos Robinson --- I'd like to test this, but my card needs the G03 driver, and these have not been updated in the NVidia repository since mid June (maybe mid May) -- nor has the G05, anyway: http://http.download.nvidia.com/opensuse/leap/15.1/x86_64/ nvidia-glG03-340.107-lp151.12.2.x86_64.rpm 28MB 2019-06-12 18:07 nvidia-glG04-390.116-lp151.7.1.x86_64.rpm 28MB 2019-06-12 18:07 nvidia-glG05-430.26-lp151.14.1.x86_64.rpm 26MB 2019-06-12 18:07 I'm not on any hurry, just mentioning in case you wonder why I don't report back ;-) -- You are receiving this mail because: You are on the CC list for the bug.