During the dracut run, it always complained > dracut-install: Failed to find module 'atiixp' for each of the kernels just before > dracut[E]: FAILED: /usr/lib/dracut/dracut-install A lot of modules are installed successfully: > dracut[I]: *** Including module: systemd *** > dracut[I]: *** Including module: systemd-initrd *** > dracut[I]: *** Including module: i18n *** > dracut[I]: *** Including module: drm *** > dracut[I]: *** Including module: plymouth *** > dracut[I]: *** Including module: kernel-modules *** > dracut[I]: *** Including module: kernel-modules-extra *** > dracut[I]: *** Including module: resume *** > dracut[I]: *** Including module: rootfs-block *** > dracut[I]: *** Including module: suse-btrfs *** > dracut[I]: *** Including module: suse-xfs *** > dracut[I]: *** Including module: terminfo *** > dracut[I]: *** Including module: udev-rules *** > dracut[I]: *** Including module: dracut-systemd *** > dracut[I]: *** Including module: haveged *** > dracut[I]: *** Including module: ostree *** > dracut[I]: *** Including module: usrmount *** > dracut[I]: *** Including module: base *** > dracut[I]: *** Including module: fs-lib *** > dracut[I]: *** Including module: shutdown *** > dracut[I]: *** Including module: suse *** > dracut[I]: *** Including module: suse-initrd *** Each one corresponds to a subdirectory of /usr/lib/dracut/modules.d, e.g. 00systemd, 50plymouth, 95suse-btrfs. But there is indeed none with ??atiixp. The next question is why that was even considered necessary.