Mailinglist Archive: opensuse (2234 mails)

[tomas@xxxxxxxxxxxx (S.Toms)]

On Wed, 1 Sep 1999, Chris wrote:

c> I remember seeing the explanation for this somewhere but for the life of me
c> can't find it again.  I searched through the list archive but couldn't
c> locate anything.
c> 
c> I have (or want) SuSE and Windows 98 on the same machine using LILO to boot
c> both.  I did a fresh install of 6.2 and thought I setup LILO the same as I
c> had it in 6.1.  Now, when the computer boots, all I get is "LI" and then it
c> locks.  If I remember right this has something to do the 1024 cylinder
c> limit.  Is this correct and could someone please expand on this further?
c> 

  see pages 112-113 section 4.8.1 Diagnosis of errors: LILO start messages

  For those of you without 6.2 books, here it is :)

none: No part of LILO has been loaded. Either LILO is not installed at all
or the partition with LILO's boot sector has not been started.

`L' error ...: The first step has been loaded and started but the second
step (/boot/boot.b) could not be laoded. This normally points to a
physical error on the boot device or a faulty disk geometry.

`LI': The second step of LILO has been invoked but could not be started.
This can be due to a faulty disk geometry or to moving /boot/boot.b
without reinstalling LILO.

`LIL': The second step of LILO has been started but could not allocate
needed data from its map file. This typically is due to a physical error
of the boot device or a faulty disk geometry.

`LIL?': The second step has been loaded at a wrong memory address. This 
can be due to a faulty disk geometry or to moving /boot/boot.b without
reinstalling LILO.

`LIL-': Data in the map file is invalid. This can be due to a faulty disk
geometry or to moving /boot/boot.b without reinstalling LILO.

`LILO': Every part of LILO has been loaded successfully.


-- 
     S.Toms - tomas@xxxxxxxxxxxx - http://www.primenet.com/~tomas
                S.u.S.E. Linux v6.1+ - Kernel 2.2.11

As Zeus said to Narcissus, "Watch yourself."

--    
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx             
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/