-   Linux - Newbie (
-   -   Necessity of initrd in building a kernel? (

Erik_the_Red 08-13-2005 07:48 PM

Necessity of initrd in building a kernel?
I followed all the steps here, but that guide made no mention of the INITRD. A more advanced guide - found here - did mention it.

So, in GRUB, I simply have this typed:


title          Ubuntu, kernel
root            (hd0,0)
kernel          /boot/vmlinuz- root=/dev/hda1 ro quiet splash

However, the one I boot into is like this:


title          Ubuntu, kernel 2.6.10-5-386
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.10-5-386 root=/dev/hda1 ro quiet splash
initrd          /boot/initrd.img-2.6.10-5-386

What should I do about initrd?

sudo mkinitrd /boot/initrd- did not seem to work.

btmiller 08-13-2005 09:21 PM

You only need an initrd if there are drivers that your kernel needs to boot (such as the filesystem driver for the root filesystem) that are not built into it and have to be loaded as modules. These modules would be put on the initrd so the kernel could load them. For custom compiled kernels, I personally just compile everything necessary in and don't bother with the initrd.

Erik_the_Red 08-13-2005 09:48 PM

I guess I need them because when I tried booting into, I got a kernel panic.

Erik_the_Red 08-13-2005 09:53 PM

I ran a search on google with the keywords 'Compile 2.6 Kernel' and the first result I got was a compile howto geared towards Debian.

I guess the command is:


mkinitrd -o /boot/initrd.img-

All times are GMT -5. The time now is 09:13 AM.