[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: new kernel >>> can't boot into debian (not solved yet)



On Sun, May 11, 2003 at 03:18:36AM -0600, Gezim H wrote:
> Yes, I changed lilo.conf to include /boot/kernel-2.4.20 instead of
> kernel-2.2.20-idepci, then I ran it.
> Lilo works fine, because lilo shows up but then the monitor light blinks
> twice or so, and just the black screen apears, no errors, no anything. The
> funny thing is that it seems as the monitor is off, because if I wait for a
> little while, and press <CTRL>+<ALT>+<DEL> it reboots fine.
> I'm not sure what initrd is!

see man initrd

> I compiled a whole new kernel with new options, so I don't know the options
> of 2.2.20 kernel.
> 

Not enough usefull information to figure out your problem. 

I suggest you download one of the stock 2.4.20 debian kernel-images
and install that. If you can get that to boot, you can copy its config
file from /boot to your kernel source tree and use that config file as
starting point for your custom kernel.

Assuming you still have kernel-image-2.2.20-idepci installed, add
following lines to lilo.conf to ensure you can always boot that image
by typing "2.2.20" at lilo prompt:

image=/vmlinuz-2.2.20-idepci
        label=2.2.20
        read-only

Since stock debian 2.4.x kernels use initrd, your lilo.conf should
also have lines like:

image=/vmlinuz
        label=linux
        read-only
# comment the next line for a non-initrd kernel
        initrd=/boot/initrd.img


-- 
Jerome

Attachment: pgpY8izSn_fVs.pgp
Description: PGP signature


Reply to: