Re: Why do I need mkinitrd with 2.6?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 05 April 2004 12:30 pm, Jeff Mitchell wrote:
> Hello--
>
> For whatever reason I can't boot up a 2.6 kernel (on Sarge-testing)
> without using mkinitrd to generate an initrd file. No Debian 2.6
> HOWTO I've read has this step, and a friend who has build kernels on
> Woody-testing has never had to do it.
>
> If I don't have an initrd and appropriate line in
> /boot/grub/menu.list, I get the following:
>
> VFS: Cannot open root device "hda1" or unknown-block(0,0)
> Please append correct "root=" boot option
> Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
>
> Using mkinitrd (having it scan the directory with the 2.6.4 modules),
> copying the output to /boot, and configuring menu.list to use it
> makes my kernel work just fine.
>
> Can anyone tell me why this is happening?
>
> Thanks,
> Jeff
You don't have the module needed to boot the /root fs compiled in,
and/or initrd isn't setup correctly. IMHO, you should compile into your
kernel all the drivers it takes to boot. The initrd system isn't really
needed for compiling a custom kernel for your box, esp when you know
all the hardware/fs. Caveat, if you build kernels to be portable, i.e.
for multiple boxes with differing hardware, and don't want to compile a
kernel for each, initrd can save time.
- --
Greg Madden
Debian GNU/Linux user
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAchkQk7rtxKWZzGsRAriDAJ9/prpQaEYO7ZUkrdWNVpz/FMyMLQCdErzs
hMIATgoK7lLHfKDc6c7maI4=
=6/nm
-----END PGP SIGNATURE-----
Reply to: