Wolfgang Bornath wrote:
> 
> Tom Berger wrote:
> >
> > Hm, maybe I missed something but why don't you configure the master LiLo
> > using M5.3? Another possibility would be using loadlin from your
> > win-partition. As for the error messages: you commented the hdparm
> > optimizations, did you? If they are still there LiLo will be confused by
> > the 'wrong' parameters of your hd.
> >
> 
> OK, a little bit more info:
> 
> Win is on hda1, M5.3 on hda2 and M6 on hda3. (Master)LILO is in
> MBR of hda.
> 
> In my lilo.conf in M5.3 I have:
> 
> boot = /dev/hda
> timeout = 50
> prompt
>   vga = normal
>   read-only
> map=/boot/map
> install=/boot/boot.b
> 
> image = /boot/bzImage
>   label = m  # for M5.3
>   root = /dev/hda2
> 
> other = /dev/hda1
>   label = w  # for Win
>   table=/dev/hda
> 
> other = /dev/hda3
>   label = m6 # this would be the entry for M6
>   table=/dev/hda
 

Guess you left the 'image' and 'root' entry in the third section out by
accident? 'other' is a keyword suggesting a non-Linux OS.


> So during installation of M6 I tried to install lilo (of M6) in
> bootrecord of hda3.
> That failed.


Dumb guess: you are below the 1024 cylinders area, aren't you?

 
> If in M5.3 I try to put a line like
> 
> image = /boot/vmlinuz
> label = m6
> root = /dev/hda3
> 
> and start /sbin/lilo I get an error message because it can't find
> /boot/vmlinuz. Sure, because hda3 is not mounted. If I mount it
> on /mnt then lilo can't find it either because it is on /mnt/boot
> not in /boot.


Hm, another dumb guess: put vmlinuz in a newly created directory
/mnt/boot. Or try the 'optional' switch. Maybe that'll help.


 
> As for the hdparm entry: During installation the optimization is
> not active because I boot with the RH boot.img. I even switched
> to tty2 and deleted the entry in /mnt/etc/rc.sysinit.
> 
> I did the whole thing again today. Called fdisk in M5.3 and
> deleted the hda3 partition. Disks were synced. Then the complete
> installation procedure again with the same result. I even tried
> several *empty* floppies. No chance. Problem is that the system
> doesn't tell why there is an error in creating a bootdisk and why
> there is an error in implementing LILO.


Duh, and I thought I had problems... :-(

 
> Wolfgang


tom


> --
> Linux Mandrake's Home: http://www.linux-mandrake.com
> Linux-Mandrake NewsGroup: news:alt.os.linux.mandrake
> a.o.l.m.-FAQ(English):  http://home.knUUt.de/tom.be/faq.html
> a.o.l.m.-FAQ(German): http://people.frankfurt.netsurf.de/wobo

Reply via email to