custom kernel "unable to open initial console" [SOLVED]

[Mitch Wiedemann]

Alexander Dalloz wrote:

>Am So, den 14.11.2004 schrieb Mitch Wiedemann um 5:04:
>
>  
>
>>I've downloaded the 2.6.9 source from kernel.org, but after configuring, 
>>compiling, and installing, I can't boot it.  I get this message: 
>>"Warning: unable to open initial console"  and then the boot process stops.
>>
>>Google searching seems to imply some link between this problem and the 
>>switch from devfs to udev.
>>
>>Has anyone else had this problem?  Or better yet, found a solution to 
>>allow me to boot my custom kernel?
>>    
>>
>
>You compiled in initial ramdisk support into your kernel and created an
>initrd image file?
>
>Alexander
>  
>

Ah Ha! 

No, I hadn't included ramdisk support!  I'm now writing this using my 
new kernel!  THANK YOU!  I'm sure I'm not the only person on the list 
who's really glad you're here Alexander!


For others who might be in the same boat as I was:
1. Run "make menuconfig"
2. Navigate through the menus: "Device Drivers -> Block Devices"
3. Enable "RAM disk support", and "Initial RAM disk (initrd) support"
4. Enable any other kernel stuff you want/need.
5. Run "make", then (as root) "make modules_install", and "make install"

The "make install" will create your initrd and add the appropriate 
stanza in your /boot/grub/grub.conf.