Results 1 to 10 of 12
I installed Slackware 10.1 on my Maxtor 40gb harddrive, and when I boot, lilo just gives me L 99 99 99 99 99 99 99 (many 99:s)
Searched google and ...
- 04-25-2005 #1Just Joined!
- Join Date
- Jan 2005
- Posts
- 70
Lilo error, L 99
I installed Slackware 10.1 on my Maxtor 40gb harddrive, and when I boot, lilo just gives me L 99 99 99 99 99 99 99 (many 99:s)
Searched google and everything but didn't get it fixed..
Help me I'm lost / thrustrated (dunno did I write it correctly, English isn't my mother tonque)
- 04-25-2005 #2Linux Engineer
- Join Date
- Mar 2005
- Location
- Where my hat is
- Posts
- 765
Post the output of fdisk -l and the contents of your lilo.conf file.
Registered Linux user #384279
Vector Linux SOHO 6 / Vector Linux 7 RC 3.4
- 04-25-2005 #3Just Joined!
- Join Date
- Jan 2005
- Posts
- 70
hdd1
Originally Posted by retired1af
/dev/hdd1 /
/dev/hdd2 home
/dev/hdd3 swap
lilo.conf relevant parts:
#append hdX=ide-scsi
timeout 1
prompt
boot = /dev/hdd1
standard row / col
jadajadajada
label = Linux
root = /dev/hdd1
image = /boot/vmlinuz
-- simple lilo configuration, could do it myself but it was more stable to use that and mobify it myself afterwards
- 04-25-2005 #4
According to this site, installing Lilo to the MBR will solve this.
http://wiki.linuxquestions.org/wiki/LILO_Error_Codes
I looked for more documentation, but couldn't find any.
Hope this helps.
P.S doeas anybody happen to know where the Lilo documentation is.
I have read it is very good, but i couldn't find it.How to know if you are a geek.
when you respond to "get a life!" with "what's the URL?"
- Birger
New users read The FAQ
- 04-25-2005 #5
http://tldp.org is always a good place to start looking for docs.
In this case http://www.ibiblio.org/pub/Linux/doc...ngle/LILO.html
might help. Also man lilo and man lilo.conf could be usefull.
I\'m so tired .....
#200472
- 04-25-2005 #6Linux Engineer
- Join Date
- Mar 2005
- Location
- Where my hat is
- Posts
- 765
Without the actual contents of lilo.conf AND the actual output of fdisk -l there's not much we can do for you. Need the entire output of each please.
Originally Posted by Scourge Registered Linux user #384279
Vector Linux SOHO 6 / Vector Linux 7 RC 3.4
- 04-25-2005 #7I actually saw that page when I was searching and didn't realize that was it
Originally Posted by puntmuts
I didn't see any error codes on that page, I figured the Lilo doc page would have error codes.How to know if you are a geek.
when you respond to "get a life!" with "what's the URL?"
- Birger
New users read The FAQ
- 04-25-2005 #8
man lilo has a partial list of errors and their meaning. Since that page is unavailable when people getting this error here they come:
TS: try to change your boot= option in your lilo.conf. If you want to boot from your /dev/hdd then remove the 1 in your line and rerun lilo.Code:When the first stage loader gets control, it types the letter "L"; when it is ready to transfer control to the second stage loader it types the letter "I". If any error occurs, like a disk read error, it will put out a hexadecimil error code, and then it will re-try the operation. All hex error codes are BIOS return values, except for the lilo-generated 40, 99 and 9A. A partial list of error codes follows: 00 no error 01 invalid disk command 02 address mark not found 03 disk write-protected 04 sector not found 06 floppy disk removed 08 DMA overrun 0A bad sector flag 0B bad track flag 20 controller failure 40 seek failure (BIOS) 40 cylinder>1023 (LILO) 99 invalid second stage index sector (LILO) 9A no second stage loader signature (LILO)I\'m so tired .....
#200472
- 04-26-2005 #9Just Joined!
- Join Date
- Apr 2005
- Location
- Indiana
- Posts
- 22
The same thing happened to me.
When I installed Mandrake recently, I had the same error. I went searching through Google and eventually realized that the 99 99 99 error means something is corrupted. What I did was reinstall Mandrake with LILO and all and it started working again. I don't know why this happens, but reinstalling worked for me.
- 04-26-2005 #10Just Joined!
- Join Date
- Jan 2005
- Posts
- 70
Re: The same thing happened to me.
Re-installed.
Originally Posted by Zardokk
Didn't work.
That's why I asked help.
--
Retided1af
If you really really want to know what there says...
I will have to _write it down by hand.
I checked fdisk and so ong, I'm not first timer with linux.
I just run out of ideas.
Besides, I gave you information what should be enough to solve the problem.
There is another HD on my computer but it's irrelevant, lilo.conf is really really simple.
That's why I wroted those lines what really matters.
(Everything yelse is commented [ # ] )
Though, my other hd is hda, and lilo is littlebit cranky about it..
AND I noticed that my Slackware cd2 is broken / something.
It's the slackware rescuedisk, when I try to boot from it cames the same error.
Maybe I should try Grub?


Reply With Quote