Hi Mulyadi, No LVM. no special drivers.. hmm.. Tell me something, who takes care of making sure that the module's init function is called (registering of the ext3 filesystem with the VFS)? I understand that these are called when the module is loaded, but what happens if it is statically compiled with the kernel? Thanks, -Joel On 12/30/09, Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx> wrote: > Hi Joel... > > I hope you don't mind that I rewrite the subject to avoid confusion... > > On Wed, Dec 30, 2009 at 11:12 AM, Joel Fernandes <agnel.joel@xxxxxxxxx> > wrote: >> Hey Mulyadi, >> >>> It acts as initial root filesystem containing modules needed to >>> proceed into complete successful booting e.g loading ext3 kernel >>> module to access real filesystem, loading LVM modules in case your >>> root filesystem stays inside LVM etc etc >> >> My root file system is ext3 and I have it compiled into the kernel. >> >> But when I don't give an initrd, then mounting of the root file system >> fails during boot, I get something like "VFS: Unable to mount root >> filesystem on block 0,0: Kernel Panic" >> >> Any idea why? > > Could be something else... is your rootfs stays inside LVM? does it > need certain SCSI/SATA drivers first (likely?)? > > In essence, it's more than just making sure ext3 module is inside > kernel image if you want to throw away initrd but successfully boot > and mount the rootfs afterward. > > -- > regards, > > Mulyadi Santosa > Freelance Linux trainer and consultant > > blog: the-hydra.blogspot.com > training: mulyaditraining.blogspot.com > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
