Bugzilla – Bug 1227702
Tumbleweed repo rpm nvidia packages script unable to regenerate systemd-boot initramfs in order to blacklist nouveau
Last modified: 2024-07-12 12:56:33 UTC
By trying to install on a environment with systemd-boot the nvidia drivers through repo-non-free, even if it generates kernel loader blacklists as such: grep -i 'blacklist nouveau' /etc/modprobe.d/* /etc/modprobe.d/blacklist-nouveau.conf:blacklist nouveau grep -i 'blacklist nouveau' /lib/modprobe.d/* grep -i 'blacklist nouveau' /usr/lib/modprobe.d/* it is unable to deactivate nouveau. The only hacky solution was through kernel parameters such as rd.driver.blacklist. After some debugging, it was clear that GRUB2 was in fact working just right, requiring just a simple restart after installation and the culprit was in fact systemd-boot. Basically, systemd-boot isn't using directly dracut -f for initramfs regeneration, but sdbootutil mkinitrd. So after installation, I had to use sdbootutil mkinitrd manually in order to actually blacklist nouveau. The package scripts should be able to distinguish between a GRUB2 and systemd-boot to use the required regeneration tools. Same applies to nvidia own run script tool. SDB:NVIDIA drivers wiki should indicate this case too. Ref. https://forums.opensuse.org/t/unable-to-blacklist-nouveau-even-with-blacklist-nouveau-conf/176785/31
KMP relies on /usr/lib/module-init-tools/kernel-scriptlets and calls kmp-post/kmp-posttrans. With suse-module-tools-scriptlets these scripts regenerate initrd. With sdbootutil-rpm-scriptlets those scripts are linked to /usr/bin/true.
The merge to suse-module-tools-scriptlets is in its way to Factory. There are some openQA issues related with transactional-update that are being addressed
Thanks, guys. I think we can close this as duplicate. @Albert If you think this is wrong feel free to reopen. *** This bug has been marked as a duplicate of bug 1224773 ***