https://bugzilla.suse.com/show_bug.cgi?id=1213222 https://bugzilla.suse.com/show_bug.cgi?id=1213222#c25 --- Comment #25 from Alexander Kruppa <akruppa@gmail.com> --- (In reply to Stefan Hundhammer from comment #19)
I'd be interested to hear if there was any error pop-up about that failure. I don't see anything in the logs.
I'm back. There was a pop-up which gave the full dracut output, including errors like the dracut-install: Failed to find module 'atiixp' line you already mentioned. What was missing, imho, was a notification from Yast that dracut failing results in an unbootable system. This is probably blindingly obvious for people familiar with the Linux boot process, but it wasn't for me. Ideally it would be nice to point out that the non-existant modules are listed in the INITRD_MODULES variable in /etc/sysconfig/kernel file. Finding out the former was easy, but I think it is worth pointing out during installation for casual users. Finding out the latter took me a long time. The command hwinfo | grep module | grep atiixp outputs nothing on my current system. My current system (AMD Ryzen 5 5600G/B550 chipset-based) is the result of a great many system upgrades. I don't remember when I did the last clean install, but it was certainly many years ago when I had an Intel Skylake-based system - or possibly even on an AMD Phenom-based system. Perhaps the stale entries in INITRD_MODULES originate from those older installations? I still have the SuSE 15.5 installation on a retired SSD, so I can rebuild the old Skylake system and boot it exactly the way it used to be, if that helps finding out what modules etc it used. Please tell if I should do so and what info you'd like to get from the old installation. Mostly what I'm hoping for in this enhancement bug is just a message from Yast, "dracut failed to install an initrd (initial ramdisk), the system is not bootable! Please fix any errors reported by dracut and re-install the bootloader." and information somewhere, from Yast or a knowledge base article or man page etc pointed out by Yast, saying that dracut gets additional modules to install in the initrd from the INITRD_MODULES variable in /etc/sysconfig/kernel. This info used to be available in the man page of mkinitrd-suse, but that program is retired in Tumbleweed, and the dracut man page does not say anything about INITRD_MODULES. Output of lsmod will be attached. -- You are receiving this mail because: You are on the CC list for the bug.