[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Can't boot from hard disk



Well since you are "grasping at straws"...

1.  You did _run_ lilo after changing /etc/lilo.conf, yes?
2.  What does rdev /boot/vmlinuz-2.0.36 give you?
    (although your "root=/dev/hda1" should over-ride)
3.  Should you have the argument "compact" in your lilo.conf?
4.  You don't have one of those BIOSes with a "hole" in the memory do you?

While I have had this sort of thing happen before, rather than try to find
out what was wrong I...
Tried other "resc" disks for the installation (this has worked).
I have also compiled (on another machine) and installed a new kernel
and that worked.

The "thing" that bothers me about this whole problem (yours and the ones 
that I have experienced) is that I thought that the kernel that gets
installed in /boot is the exact same kernel that IS on the resc disk which
suggests to me that the problem "can not be" the kernel itself but must be
related to lilo and associated files (experience NOT withstanding).

On Sat, Aug 07, 1999 at 01:52:33PM -0500, Mark Lawrence wrote:
> Just installed 2.1 (slink) from cdrom. Boots from floppy OK, but hangs
> after "Loading Linux................." The machine is a Pentium 200 with
> 96 MB of RAM. The master EIDE hd has 6.4 GB and is partitioned like this:
> 
>   device       start        stop    mount point
> /dev/hda1         1           65     /
> /dev/hda2        66           81     swap
> /dev/hda3        82          337     /usr
> /dev/hda5       338          465     /usr/local
> /dev/hda6       466          784     /home
> 
> The /etc/lilo.conf looks like this:
> 
> boot=/dev/hda1
> root=/dev/hda1
> install=/boot/boot.b
> map=/boot/map
> vga=normal
> delay=20
> image=/vmlinuz
>     label=Linux
>     read-only
> 
> /vmlinuz is a link to /boot/vmlinuz-2.0.36, which is as it should be.
> 
> The frustrating thing is I've done this installation on another machine
> and it's worked just fine.
> 
> Any ideas would be appreciated.
> -- 
> Mark Lawrence
> lawrence@unified-eng.com


Reply to: