Description of problem: Install the beta on a box with an i2o controller. The install now does the right thing. After the install the boot fails with module errors. How reproducible: 100% Steps to Reproduce: 1. install beta on box with i2o controller rootfs 2. reboot after install Actual results: i2o_pci is loaded in the initrd before i2o_core, but needs it. This causes module load failures 'unable to find root' and a panic. Not sure if thats my fault for giving you a wrong ordering at some point or just a confusion somewhere Expected results: The initrd loads i2o_core, i2o_pci, i2o_block and life is good
Fixed in mkinitrd-3.4.40-1
I'm going through Bugzilla closing some bugs that have been marked as Modified for some period of time. I believe that most of these issues have been fixed, so I'm resolving these bugs as Rawhide. If the bug you are seeing still exists, please reopen this report and mark it as Reopened.
Still present in alpha1
Jeremy do we ever write the initrd these days or do we let the kernel pkg do it?
mkinitrd does it, but it really should be getting the order right. if [ "$modName" = "i2o_block" ]; then findmodule i2o_core findmodule i2o_pci modName="i2o_block" fi Does the linuxrc actually have i2o_pci and i2o_core reversed? Also, what does the modules.conf look like?
Closing due to inactivity - please reopen if you have additional information to add.
*** This bug has been marked as a duplicate of 68796 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.