http://qa.mandrakesoft.com/show_bug.cgi?id=3614
------- Additional Comments From [EMAIL PROTECTED] 2003-03-31 12:07 ------- Created an attachment (id=413) --> (http://qa.mandrakesoft.com/attachment.cgi?id=413&action=view) another possible fix: check modules.dep This potential fix is more complex than my first one. It greps the appropriate kernel's modules.dep file to see if aes.o is needed. This patch basically assumes that the modules.dep file exists -- if it doesn't exist, this patch obliviously assumes that aes.o is not needed. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: When a loopback file is used as the root "partition," mkinitrd includes loop.o but not aes.o in the initrd. Any attempt to use this initrd to boot the system results in the initrd being unable to mount the root filesystem and, hence, the system being unbootable. I first encountered this problem during a fresh 9.1 install (I used a Knoppix rescue CD to manually modify the initrd so I could boot after the install). It's 100% reproducible with mkinitrd from the command line after installation, too. In any case, this bug makes Mandrake 9.1 loopback installs *totally unusable* unless you manually hack the initrd. I'm taking a look at the mkinitrd source code now, and I'll see if I can put together a patch (or maybe a few patches which use different approaches) to fix this.
