Am Sa, den 18.10.2003 schrieb viro@parcelfarce.linux.theplanet.co.uk um 19:52: > > > Seems that something changed between test7 and test8 regarding initrd or romfs > > > support. I'm using highly modularized 2.6.0 kernel which has all filesystems > > > beside romfs compiled as modules (romfs is compiled inside of kernel). > > > > > > Modules for my rootfs are loaded from initrd (which is image with romfs as > > > filesystem) but starting from test8 kernel is not able to mount initrd > > > filesystem - stops with typical message about not being able to mount rootfs. > > > > > > cset test7 from 20031012_0407 is known to be ok so something was changed later > > > > > > I noticed this happened in 2.6.0-test6-mm4. Backing out this patch fixes > > it in the short-term. > > Even better would be to report the bug ;-/ > > I can't reproduce it here. 2.6.0-test8 vanilla, so far (last 15 minutes) > tried with > * compressed initrd image > * plain ext2 > and I'll try romfs as soon as I hunt down mkfs for that animal. All > appears to be working... I've got the same problem here. I'm using a simple ext2 ramdisk here. I also tried making a cpio archive for initramfs. The kernel doesn't say anything. No "RAMDISK:", no "checking if image is initramfs..." or something. I'm seeing that the kernel is looking for md devices and directly after that he complains that he can't find device fe01 (my ramdisk sets up lvm volumes via device-mapper) and panics. I've looked through the changes and I'm puzzled, I really don't see the problem. It looks like the initrd wasn't passed down to the kernel. I'm using lilo. Do you have an idea where it would be wise to add some debugging info? I've attached my .config, unfortunately I can't give you a boot log. I really need a nullmodem cable... :) -- Christophe Saout Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html