Re: [PLUG] lilo question

[Serguei Ostrovskii <sostrovs@kns.com>]

Yes, I think I see you problem. From your lilo.out :
<-----
Added linux *
    <dev=0xc0,hd=0,cyl=57,sct=138>
    "ro root=305"
Boot image: /boot/vmlinuz-2.2.14-5.0
Device 0x0301: BIOS drive 0x80, 255 heads, 4982 cylinders,
               63 sectors. Partition offset: 63 sectors.
Setup length is 7 sectors.
Mapped 1218 sectors.
Mapping RAM disk /boot/initrd-2.2.14-5.0.img
Device 0x0301: BIOS drive 0x80, 255 heads, 4982 cylinders,
               63 sectors. Partition offset: 63 sectors.
RAM disk: 848 sectors.
Added linux-up
    <dev=0xc0,hd=0,cyl=57,sct=164>
    "ro root=305"
<-----
These     <dev=0xc0, ... blah ...> mean LILO thinks it should build bootloader
which will try to access your hda through INT13 as 0xC0 device at _boot_time_.
This might be because you set in the BIOS boot device floppy, or SCSI ( just to
boot
somehow ). LILO isn't aware about your plans to change boot device in the future,
so you have to explicitely tell that your root=/dev/hda? for yor images will be on
BIOS 0x80
device in the next boot.
1) For every image=    section append parameter     disk(or disc ? can't remember
now, LILO errore'd
once because of that )=0x80.
2) Run LILO
3) Reboot, and while rebooting change your primary boot device to C:.
4) If it boots successfully ( I wish you so ) you can remove these root=0x80 and
rerun LILO.

Sergey Ostrovsky.



______________________________________________________________________
Philadelphia Linux Users Group       -      http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion  -  http://lists.phillylinux.org/mail/listinfo/plug