Hello,
I had the same pb that machine hanged after showing
LI. This is because I had not installed LILO in
/dev/hda1 it was installed in /dev/hda3 where I had
Linux.
Reinstalling Linux and selecting appropriately
should solve the pb.
Paresh.
--- "Ravikant K.Rao" <[EMAIL PROTECTED]> wrote:
> >>>>> "Sekar" == S Sekar <[EMAIL PROTECTED]>
> writes:
>
> Sekar> Hello, After installing RedHat 6.0 as the
> only OS on a
> Sekar> Celeron PC, I find that during boot, the
> display stops
> Sekar> after displaying "LI".( lilo in MBR).
> LILO prompt is not
>
> <rant>
>
> All LILO users, please RTFM, someday.
>
> </rant>
>
> [pts/0] (13:30:10) ravi@rockford [/usr/doc/lilo]$
> zless Manual.txt.gz
>
> <snip>
>
> LILO start message
> - - - - - - - - -
>
> When LILO loads itself, it displays the word "LILO".
> Each letter is printed
> before or after performing some specific action. If
> LILO fails at some
> point, the letters printed so far can be used to
> identify the problem. This
> is described in more detail in the technical
> overview.
>
> Note that some hex digits may be inserted after the
> first "L" if a
> transient disk problem occurs. Unless LILO stops at
> that point, generating
> an endless stream of error codes, such hex digits do
> not indicate a severe
> problem.
>
> (<nothing>) No part of LILO has been loaded. LILO
> either isn't installed
> or the partition on which its boot sector is
> located isn't active.
> L <error> ... The first stage boot loader has
> been loaded and started,
> but it can't load the second stage boot loader.
> The two-digit error
> codes indicate the type of problem. (See also
> section "Disk error
> codes".) This condition usually indicates a
> media failure or a geometry
> mismatch (e.g. bad disk parameters, see section
> "Disk geometry").
> LI The first stage boot loader was able to load
> the second stage boot
> loader, but has failed to execute it. This can
> either be caused by a
> geometry mismatch or by moving /boot/boot.b
> without running the map
> installer.
> LIL The second stage boot loader has been
> started, but it can't load
> the descriptor table from the map file. This is
> typically caused by a
> media failure or by a geometry mismatch.
> LIL? The second stage boot loader has been
> loaded at an incorrect
> address. This is typically caused by a subtle
> geometry mismatch or by
> moving /boot/boot.b without running the map
> installer.
> LIL- The descriptor table is corrupt. This can
> either be caused by a
> geometry mismatch or by moving /boot/map without
> running the map
> installer.
> LILO All parts of LILO have been successfully
> loaded.
>
> <snip>
>
> HtH
>
> --ravi
> --
> Ravikant K.Rao : http://www.symonds.net/~ravi/
> Primary Email : <[EMAIL PROTECTED]> | PGP: 9544A4A1
> GPG: 1024D/C2FC752D
>
>
-----------------------------------------------------------------------
> The LIH mailing list archives are available at:
>
http://lists.linux-india.org/cgi-bin/wilma/linux-india-help
=====
regards,
Paresh.
__________________________________________________
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com
-----------------------------------------------------------------------
For more information on the LIH mailing list see:
http://lists.linux-india.org/lists/LIH
