> What am I doing wrong?
Davide
by dav.. » Mon, 23 Dec 2002 02:54:06
Davide
by Paul Lutu » Mon, 23 Dec 2002 02:54:06
--
Paul Lutus
http://www.arachnoid.com
by Davi » Mon, 23 Dec 2002 03:50:44
> lba32
> boot=/dev/hda
> root=/dev/hda2
> install=/boot/boot-menu.b
> map=/boot/map
> delay=50
> vga=normal
> default=Linux
> linear
> image=/vmlinuz
> label=Linux
> read-only
> initrd=/initrd.img
> image=/vmlinuz.old
> label=LinuxOLD
> read-only
> optional
> The files /vmlinuz and /vmlinuz.old are symbolic links to
> /boot/vmlinuz-2.4.18-k7 and /boot/vmlinuz-2.2.20-idepci, respectively,
> so according to lilo.conf, the default kernel should be 2.4.18,
> but instead my machine boots to 2.2.20-idepci.
> What am I doing wrong?
> Here are some more details. The file /initrd.img is a symbolic
> link to /boot/initrd.img-2.4.18-k7. The full contents of /boot
> are:
> $ ls -F /boot
> System.map-2.2.20-idepci boot.0300 map
> boot-bmp.b chain.b vmlinuz-2.2.20-idepci
> boot-compat.b config-2.2.20-idepci vmlinuz-2.4.18-k7
> boot-menu.b config-2.4.18-k7
> boot-text.b initrd.img-2.4.18-k7
ls -F /boot/
boot.0200 boot-text.b map System.map-2.4.20tbls
So I would say either you need to create the proper symlinks or
configure lilo.conf to use something more in line with the
following. This is from a redhat system and may cause problems if
you cut and paste into your lilo.conf file.
!!! YOU HAVE BEEN WARNED !!!
image=/boot/vmlinuz-2.4.20tbls
label=linux
initrd=/boot/initrd-2.4.20tbls.img
read-only
root=/dev/hda1
#image=/boot/vmlinuz-2.4.20-1
# label=linux-old
# initrd=/boot/initrd-2.4.20-1.img
# read-only
# root=/dev/hda1
--
Confucius: He who play in root, eventually kill tree.
Registered with the Linux Counter. http://counter.li.org
by johninsd at san dot rr dot co » Tue, 24 Dec 2002 17:12:42
>Did you run lilo -v after modifying the lilo.conf ?
>Davide
LILO only reads 'lilo.conf' at INSTALL time, never at BOOT time.
/sbin/lilo is the boot installer. (boot.b, or similar, is the actual boot
loader). The function of the boot installer is to create /boot/map, the
sector map of kernel sectors to load (& initrd & other=...).
--John
by RonB » Fri, 27 Dec 2002 14:06:18
>>What am I doing wrong?
> Did you run lilo -v after modifying the lilo.conf ?
--
RonB
(stuck using my Windows 98se until AT&T gets my cable modem back up)
...10 days and counting...
Hi,
I wonder if anyone knows what's going on. I've upgraded my kernel to a
newer one, and I went to change my /etc/lilo.conf file to get it to boot
into it correctly. So far so good, the online documentation was fine.
So now I had Windows, the older kernel and the newer kernel as options. So
far so good.
Then I decided to delete the older kernel. I deleted any of the files that
had anything related to the older kernel from /boot. I then changed
lilo.conf to remove the entry for the older kernel aswell.
I restart my computer and I get the exact same boot options - Windows,
Older kernel and new kernel.
After a bit of digging, I found there was a different file called
/etc/lilo.conf~ which had my old settings to boot. So this file was
probably the one it was using to choose my boot options. Why is that?
Also, it's weird because this old lilo.conf~ file which has the old kernel
still as an option runs fine.
image="/boot/vmlinuz-2.4.2-2"
label="linux"
read-only
root="/dev/hda4"
When I select "linux" from Lilo, it boots into Linux fine, even there is no
"/boot/vmlinuz-2.4.2-1", (not even a hidden file of that name).
Here's a copy of linux.conf~ file in all its entirity:
boot="/dev/hda"
map=/boot/map
install=/boot/boot.b
prompt
timeout="50"
message=/boot/message
lba32
default=Windows
image="/boot/vmlinuz-2.4.2-2"
label="linux"
read-only
root="/dev/hda4"
other=/dev/hda1
optional
label=Windows
image="/boot/vmlinuz-2.4.3-12"
label="LinuxNew"
root="/dev/hda4"
read-only
(the linux.conf file is the same, just without the /boot/vmlinuz-2.4.2-2
image).
Any help appreciated,
Michael
3. Help: Lilo ignored at boot time.
4. Linux & 21 color sync apple Studio screen
5. LILO shows "010101010101010..." instead of "LILO" at boot time...
6. Help with Orinoco + 2.4.17 + RH7.1
7. kernel panic at boot time (related to mem=384M in lilo.conf)
8. Trying to connect a "legacy" system
9. lilo can't find /etc/lilo.conf, even though it's there
10. Does LILO use any other configuration file besides lilo.conf?
12. LILO - Can I add a command line argument to /etc/lilo.conf?
13. LILO not reading LILO.CONF