In article <[EMAIL PROTECTED]>,
Kero van Gelder <[EMAIL PROTECTED]> wrote:
> [snip]
> > When the notebook wants to boot from the hard disc, I get:
> >
> > Insert Boot-Disk and press any key
> You ran lilo?
> (have to ask; I have one useful remark at the bottom)
Yes, I did. That's the point that is puzzling me! But as you can see as
well from my hex dump, LILO /is/ installed in the first few bytes of
sector 0 on my hard disc.
[snip]
> > pii233:~# cat /etc/lilo.conf
> > boot=/dev/hda
> > root=/dev/hda3
> > compact
> > install=/boot/boot.b
> > map=/boot/map
> > vga=normal
> > delay=20
> > linear
> >
> > image=/boot/vmlinuz
> > label=Linux-2.2.x
> > read-only
> You did have /boot mounted when you ran lilo (suppose it'd give an
> error, but anyway)?
Yes, I did. I even ran lilo with -v -v -v -v which gave me lots of
verbose output, all of which looked quite ok to me.
> > image=/boot/vmlinuz.old
> > label=Linux-Old
> > read-only
> >
> > image=/boot/vmlinuz-2.0.36
> > label=Linux-2.0.36
> > read-only
> [snip dd MBR dump]
> (Don't know what it all means, but first few bytes are same as on my
> HD).
Well, at least this means, that LILO /is/ installed into the MBR,
doesn't it?
[snip]
> > BTW: I don't have any options in the BIOS concerning the hard disc.
> > So I can't switch on/off special modes for the hard disc. (Just in
> > case you suggest something like this!)
> Your BIOS did not get screwed?
Why should it? No, Win runs (and boots) ok from it.
> As in, it does try to boot from HDD?
I don't get the question (perhaps my English?). Currently my boot
preferences in the BIOS are set as follows:
1st boot device: floppy
2nd boot device: CD-ROM
3rd boot device: hard disc
At least with Windows this works perfectly well.
And - before you ask - I have tried making the hard disc the 1st boot
device, it didn't make any difference.
> > If somebody could give me any kind of advice what might be wrong and
> > how I can get LILO to boot from my hard disc, I'd be very happy! :-)
> Diference with my lilo.conf is that you don't have the root=/dev/hda3
> _after_ the image line, like:
> image=/boot/vmlinuz-2.0.36
> label=Linux-2.0.36
> read-only
> root=/dev/hda3
Well, that's only necessary if the root option is not a global one. But
as my root partition is - for all of my three kernels - the same, I may
put it into the global section. I don't see why this should cause any
problem.
> And I have a line with
> initrd=/boot/initrd-2.0.36-20.img
> in the same block, but that seems unnecessary.
If LILO ran, and then crashed some time later (even after the kernel
has been started), then I'd consider this, but at present, I don't see
how this could cause my problems.
Sorry, didn't solve my problem yet, but thanks anyway for your help. :-)
Greetings,
Stefan.
--
Stefan Bellon * <mailto:[EMAIL PROTECTED]> * <http://www.sbellon.de/>
Data file? No thanks, I prefer to date people
