Now mkinitrd is similarly crippled in that it behaves just like mkinitrd from dracut so that modules are not found. Bug #858378 has been updated. Kernel image: /boot/vmlinuz-3.13.0-rc8-smp+ Initrd image: /boot/initrd-3.13.0-rc8-smp+ KMS drivers: nouveau Root device: /dev/disk/by-id/ata-ST31000524AS_6VPBVSPA-part1 (/dev/sda1) (mounted on / as ext4) Resume device: /dev/disk/by-id/ata-MAXTOR_STM3500630AS_6QG0YKMR-part3 (/dev/sdb3) modprobe: unrecognized option '--allow-unsupported-modules' WARNING: no dependencies for kernel module 'thermal' found. modprobe: unrecognized option '--allow-unsupported-modules' WARNING: no dependencies for kernel module 'processor' found. modprobe: unrecognized option '--allow-unsupported-modules' WARNING: no dependencies for kernel module 'fan' found. modprobe: unrecognized option '--allow-unsupported-modules' WARNING: no dependencies for kernel module 'rtc_cmos' found. modprobe: unrecognized option '--allow-unsupported-modules' WARNING: no dependencies for kernel module 'ext4' found. modprobe: unrecognized option '--allow-unsupported-modules' WARNING: no dependencies for kernel module 'nouveau' found. modprobe: unrecognized option '--allow-unsupported-modules' WARNING: no dependencies for kernel module 'ahci' found. modprobe: unrecognized option '--allow-unsupported-modules' WARNING: no dependencies for kernel module 'usbcore' found. Regards Sid. On 13/01/14 11:59, Sid Boyce wrote:

Built 3.13-rc7 on 3 boxes where dracut had replaced mkinitrd.

zypper dup installed dracut. I spotted the problem on 2 systems and installed module-init-tools.

On a third system I forgot to install module-init-tools and reboot failed with no access to usb or wired keyboard, network or anything else that needed modules were started.

I had to do a fresh install, "zypper in module-init-tools", built and installed vanilla 3.13-rc7 and rebooted successfully.

I did play around with booting from CD, mounting /dev/sda2 as /tmp/2, chroot /tmp/2 and mounting /dev/sda1 as /boot but that didn't allow zypper in module-init-tools to work.

Reproducible: Always

Steps to Reproduce: 1.#!/bin/sh cp arch/x86/boot/bzImage /boot/vmlinuz-$1;cp System.map /boot/System.map-$1 rm /boot/System.map;ln -s /boot/System.map-$1 /boot/System.map cp .config /boot/config-$1 cd /boot;mkinitrd /boot/initrd-$1 $1 grub2-mkconfig -o /boot/grub2/grub.cfg 2. 3. Actual Results: mkinitrd complained it couldn't find modules for 3.13.0-rc7 although they were present and worked when module-init-tools were installed on the other 2 boxes.

Expected Results: Modules should have been picked up by mkinitrd.

Regards Sid.

-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org