lilo auto boot

[$m0kE]

auto boot doesn't work...also after timeout!
this is my lilo.conf:

append="vga=0x0303"
boot=/dev/hde2
vga=normal
message=/boot/message
menu-scheme=Wg:kw:Wg:Wg
read-only
prompt
timeout=10

image = /boot/vmlinuz
root = /dev/hde2
label = linux

[acid_kewpie]

you've not got a

default = linux

line. add it and run 'lilo' as root

[X_console]

Actually the default tag will not matter. Your lilo.conf file seems to be correct. Did you rerun the lilo command after modifying it? You need to to update LILO.

[$m0kE]

mhm...i just executed it with and without the "default=linux" tag by typing:
lilo -C /etc/lilo.conf
but it doesn't boot automatically
=(
it's getting on my nerves because i always have to connect it to the keyboard, press enter, and then i have to reconnect it to my windows pc! *gna*

[bdg1983]

Try removing the 'prompt'.

[Slackmonster]

If I had a nickel for every time I forgot to run lilo after changing the conf file I could by a new computer game!! Anyone got any spare nickels? :D

[$m0kE]

mhm...i also forgot that in the beginning!
:)
but it doesn't work neither with nor without prompt.
is the tag default = linux at the right place? or does it have to stand at the end? or in the middle?
here's my actual conf again:

default=linux
append="vga=0x0303"
boot=/dev/hde2
vga=normal
message=/boot/message
menu-scheme=Wg:kw:Wg:Wg
read-only
timeout=1
# End LILO global Section
#
image = /boot/vmlinuz
root = /dev/hde2
label = linux

[DMR]

Originally posted by $m0kE:
mhm...i also forgot that in the beginning!
:)
but it doesn't work neither with nor without prompt.
is the tag default = linux at the right place? or does it have to stand at the end? or in the middle?
here's my actual conf again:

default=linux
append="vga=0x0303"
boot=/dev/hde2
vga=normal
message=/boot/message
menu-scheme=Wg:kw:Wg:Wg
read-only
timeout=1
# End LILO global Section
#
image = /boot/vmlinuz
root = /dev/hde2
label = linuxboot=/dev/hde2 That means that lilo is installed to the root partition of the secondary master drive, and not the MBR. In your case, I don't think that's the setup you want. What other drives and operating systems are on your box?

[ 06 November 2001: Message edited by: DMR ]

[$m0kE]

on this machine i have installed linux only....but because the partition is larger than 1024 cylinders 8or something like that) i must have an own partition for the boot sector...i don't need a boot manager, i just want suse to be started!
=)

[$m0kE]

and there is just one drive-->that is connected to the primary master (udma100)

[Silent Bob]

Originally posted by $m0kE:
<STRONG>on this machine i have installed linux only....but because the partition is larger than 1024 cylinders 8or something like that) i must have an own partition for the boot sector...i don't need a boot manager, i just want suse to be started!
=)</STRONG>

In that case you either have to set /dev/hde2 to be the active partition (I think this can be done with cfdisk) OR you should change where LILO is installed to /dev/hda. This changes the Master Boot Record (MBR) of your primary master harddisk to point to where the necessary code to boot GNU/Linux is. (IE the MBR points to /boot). It doesn't matter that /boot is on a different drive.

At least that's how I understand it, anyone who knows better can feel free to correct me :)

And don't forget to rerun /sbin/lilo

[ 06 November 2001: Message edited by: Silent Bob ]

[$m0kE]

mhm... i would prefer doing it with lilo, because then i at least have the possibility to boot other devices if i should need to...

[X_console]

As I said, you don't need the default tag to make it autoboot. I have one of my servers autoboot with the following:


boot = /dev/hda
prompt
timeout = 100
change-rules
reset
vga=791
image = /vmlinuz
root = /dev/hda1
label = Linux
read-only


And then run lilo as root for changes to take effect.

[Silent Bob]

Originally posted by $m0kE:
<STRONG>mhm... i would prefer doing it with lilo, because then i at least have the possibility to boot other devices if i should need to...</STRONG>

Sorry, I should have put it better

What I suggested is booting with LILO. All that is happening when you install it to /dev/hda is that you are installing LILO to a different place (the MBR). :)

Try it and see. If you want to restore your MBR afterwards (and uninstall LILO) just run lilo -u

[ 06 November 2001: Message edited by: Silent Bob ]

[$m0kE]

how can i install lilo to a different partition? can u please gimme the sorce code. the hard disk that should be booted is /dev/hde...
=)

[DMR]

Originally posted by $m0kE:
<STRONG>and there is just one drive--&gt;that is connected to the primary master (udma100)</STRONG> Ah, so is the ATA-100 onboard controller responsible for the "hde" designation? As primary master, it would usually be "hda".

In any event, lilo.conf would have something similar to the following lines when booting from the MBR: boot=/dev/hde
map=/boot/map
install=/boot/boot.bNotice that the location indicated in the "boot=" line points to a device, not a partition on that device.

I think that if you simply run /sbin/lilo with no arguments it installs to the MBR by default. Sorry, but I'm not near my Linux box or documentation right now, so I can't give specifics.

[ 06 November 2001: Message edited by: DMR ]

[Slackmonster]

Originally posted by $m0kE:
<STRONG>auto boot doesn't work...also after timeout!
this is my lilo.conf:

append="vga=0x0303"
boot=/dev/hde2
vga=normal
message=/boot/message
menu-scheme=Wg:kw:Wg:Wg
read-only
prompt
timeout=10

image = /boot/vmlinuz
root = /dev/hde2
label = linux</STRONG>


I may be blowing smoke but I just noticed something. The hard drive device he has listed is /dev/hde2. Could this be the problem?

[DMR]

Singlemalt,

No smoke perhaps, but re-read the entire thread. The "hde" issue has been brought up already (but no one has given a definitive answer yet).
:confused: