LILO?

[Kronos]

So I set up the /etc/lilo.conf file and ran lilo. (I emerged it, because I like LILO). However - it does not work. The config file is correct, I'm pretty sure. I've set them up before. It comes up at boot like this:

LI

The LO is missing and it stalls there. Usually in the past that meant (for me) the "prompt" line was missing in the config, but such is not the case here.

Any help?

[Sassur]

I'm think it will be easyer to help you if you post your lilo.conf here.

[de4d]

kernel image outside 1024 cyl. boundary?

maybe visit lilo manual - start message
_________________
void main(){fork();main();}

[Kronos]

my lilo.conf:

# Author: Ultanium
# Start LILO global section
menu-scheme=Wb
boot = /dev/hdb1
prompt
#boot=/devices/discs/disc0/disc
map = /boot/System.map
#compact # faster, but won't work on all systems.
lba32
#if lba32 do not work, use linear
#linear
delay = 5
vga = normal # Normal VGA console
# End LILO global section
# Linux bootable partition config begins
image = /boot/bzImage
root = /dev/hdb3
#root = /devices/discs/disc0/part3
label = Gentoo
# read-only # read-only for checking
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
#other = /devices/discs/disc0/part1
label = Windows
table = /dev/hda
# DOS bootable partition config ends


I did the normal Gentoo partitioning, except on /dev/hdb instead of /dev/hda. My windoze is on /dev/hda.

When I run lilo:

Warning: /dev/hdb1 is not on the first disk
Added Gentoo *
Added Windows

There you go...

And as far as my kernel image being outside the 1024 cyl. boundary - I don't think so, but I don't know how to check.

/dev/hdb1 - /boot
/dev/hdb2 - swap
/dev/hdb3 - /root

Thanks.

[de4d]

how do u make your bios boot from /dev/hdb instead of /dev/hda?
if - as i would assume - ur CMOS setup allows boot from HD0 to HD3 (and u switched to HD1), maybe this screws up your HD adressing by faking a /dev/hda which is actually @ /dev/hdb (?) during the boot process.
ok - this may be a dry hole, but i was wondering about that.
... far from having any serious idea :|
_________________
void main(){fork();main();}

[Kronos]

You are right in the method of the CMOS as far as booting goes, but I doubt this poses a problem to the HDD addressing schemes. I've done such things with it before. An interesting concept though.

Alas, I still have no Gentoo, since I cannot boot into it. Blergh. Maybe I'll just go and install Debian. I'd really like to try out Gentoo, but if I can't boot . . . .

Egad, I hate being stuck using 'doze.

[de4d]