On Mon, 03 Apr 2000, Chuck Collins wrote:
> > On Mon, 3 Apr 2000, Chuck Collins wrote:
> > 
> > > I've installed RedHat 6.1 on a Prostar laptop. Most everything
> > > works OK except it will not boot from the hard disk. It will boot
> > > fine from floppy.
> > > 
> > > I've run LILO directly, LILO thought everything went OK. I took a
> > > look at the first sector of /dev/hda, and it matched boot/boot.b .
[snip]
> > > Who has a silver bullet for this problem?
[snip]
> Disk /dev/hda: 128 heads, 63 sectors, 525 cylinders
> Units = cylinders of 8064 * 512 bytes
> 
>    Device Boot    Start       End    Blocks   Id  System
> /dev/hda1   *         1         5     20128+  83  Linux
> /dev/hda2             6       525   2096640    5  Extended
> /dev/hda5             6        38    133024+  82  Linux swap
> /dev/hda6            39       525   1963552+  83  Linux
[snip]
> /dev/hda6 on / type ext2 (rw)
> /dev/hda1 on /boot type ext2 (rw)

This is starting to sound like another ugly, long thread I was involved with a
short time ago. Lets get some facts straight:
1) Your using a small /boot partition which is definatly below 1024 cylinders.
2) You tried with lilo in both /dev/hda and /dev/hda1 with no luck.\
3) Lilo runs and doesn't think anything went wrong.
This sounds just like the other thread. Basicly, it came down to a conclusion
that the BIOS didn't like the looks of LILO and therefor refused to load it
instead giving back a :"missing operating system" or something simillar. One
question, what type of boot disk is this? A kernel on the floppy or Lilo? I'm
betting if you put Lilo on a floppy (change the boot line to boot=/dev/fd0 in
/etc/lilo.conf) by itself, it will boot the system. This was the same in the
other thread, but Lilo would not work from the hard drive. The final conclusion
was Lilo won't work but another boot loader "Chos" did.

Adrian

-- 
- I just tried this on my old Packard Bell 486/66 w/4MB (Hey ...
- shut-up! I was young, ignorant, and didn't know anything about
- hardware or quality manufacturers.).

Reply via email to