LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 07-23-2003, 07:21 PM   #1
somnium
LQ Newbie
 
Registered: Jul 2003
Location: Suburbia
Distribution: Slackware
Posts: 26

Rep: Reputation: 15
Lilo errors after compiling kernel


Hello, I've been having the famed L99 error. After checking all the prev posts here, doing some checking in Google and man pages, I have an idea of what's wrong but don't know how to fix it.

Specifically, the problem I've been having is after recompiling the kernel and copying the System.map file to /boot, I get the L99 error. From the man pages I figured out error #99 is Lilo generated. Fine. Also, it defines it further by saying "99 - invalid second stage index sector (LILO)". Alright. It goes on to say the map file is probably corrupt (even though I rerun /sbin/lilo to update the map file and install it).

I believe the problem is not configuration wise (since lilo worked just fine before the compilation of the new kernel). The only thing I can think of is that the System.map file didn't get copied correctly or something of that sort.

So I restored my old System.map file (I saved it since I got this problem before...) and figured out it's a link. Fine. So I copied the new System.map to /boot/System.map.new and changed the System.map s link to the System.map.new. Didn't work either. I know it was a long shot but hey I'll try anything at this point.

Any ideas? I can't figure out how compiling the kernel has anything to do with it. And if you exclude that, the only thing difference from a previously working lilo configuration is the new System.map file... and I ran out of ideas to fix it. Any ideas would be appreciated.

Also, I didn't include lilo.conf (etc) cause I really doubt it's anything to do with that, or my partitioning scheme (simple setup, lilo boots from /dev/hda2 (/boot)).

Anyways... thanks for any ideas again
 
Old 07-23-2003, 11:03 PM   #2
somnium
LQ Newbie
 
Registered: Jul 2003
Location: Suburbia
Distribution: Slackware
Posts: 26

Original Poster
Rep: Reputation: 15
Lightbulb

Still doing some error checking and the like. Lilo seems to be finding the right geometry for my HDDs. I've double checked this now. This means (according to it's man page) that it's got to be the map file, which throws me against a brick wall.. if calling lilo to remap the map file doesn't work, what can I do? Apparently the map file is corrupted or is somehow unreadable. Everything else seems to work fine... again, any ideas?
 
Old 07-24-2003, 02:43 AM   #3
ppuru
Senior Member
 
Registered: Mar 2003
Location: Beautiful BC
Distribution: RedHat & clones, Slackware, SuSE, OpenBSD
Posts: 1,791

Rep: Reputation: 50
Q: do you have LBA32 in lilo.conf
 
Old 07-24-2003, 03:26 AM   #4
somnium
LQ Newbie
 
Registered: Jul 2003
Location: Suburbia
Distribution: Slackware
Posts: 26

Original Poster
Rep: Reputation: 15
Yep. Here - so I have it posted:

# lilo.conf (07.24.03)

# GLOBALS
boot = /dev/hda2
install = /boot/boot.b
map = /boot/map
lba32
vga = ask

# Stanza for linux
image = /boot/vmlinuz
append = "hdc=ide-scsi hdd=ide-scsi"
label = Linux
root = /dev/hda3

# Stanza for new linux kernel
image = /boot/bzImage.current
append = "hdc=ide-scsi hdd=ide-scsi"
label = Linux_test
root = /dev/hda3

As I said, pretty simplistic setup. Also, I used the compact and linear options (one at a time) and that ended with the same results: L99...

Thanks for looking into it though, I'm running out of options to fix it other than post in newsgroups or other forums...

Last edited by somnium; 07-24-2003 at 03:36 AM.
 
Old 07-24-2003, 03:39 AM   #5
somnium
LQ Newbie
 
Registered: Jul 2003
Location: Suburbia
Distribution: Slackware
Posts: 26

Original Poster
Rep: Reputation: 15
Success

I have, finally, resolved this problem. I had to rip the bootsector from the partition again. I wasn't aware that a map file was part of the bootsector or, probably better worded, the map file was a dependency in the bootsector. Either way, I've never heard of this particular error happening and hopefully someone can put what I learned to good use instead of reading page after page of information no applicable to the problem (but quite informative!)

EDIT: Apparently, I have to re-rip the bootsector every time I change lilo.conf. I thought the whole idea was to have a lilo load the files it needed at boot time, instead of them residing in the bootsector for them to be used (so the bootsector size stayed under 512).

Last edited by somnium; 07-24-2003 at 04:07 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Errors when compiling kernel bornhj Slackware 18 04-14-2005 12:50 AM
Errors Compiling 2.6.10 Kernel! Please Help! Jonescity Slackware 12 02-26-2005 06:01 PM
Errors compiling kernel linuxgamer09483 Linux - Software 9 02-16-2004 09:58 AM
Kernel compiling errors krackerroot Slackware 4 10-27-2003 12:33 AM
Errors when compiling kernel, what do they mean? DiBosco Linux - Software 6 01-24-2002 03:13 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 03:19 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration