LinuxQuestions.org
Review your favorite Linux distribution.
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 01-26-2009, 07:34 PM   #1
posix_memalign
Member
 
Registered: Aug 2008
Posts: 81

Rep: Reputation: 15
L 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99


While compiling a new custom kernel (patched with the UnionFS) for my Slackware 12.0 install on a standard Pentium 4 I suddenly got the message:

"L 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99"

when LILO was trying to load. I've come to understand that this error means LILO stage 1 has loaded but stage 2 has failed to load.

I've read around a little and found a few solutions, such as using lilo -M to update the MBR (which supposedly could be broken). The HDD is fine, I've tested it with MHDD and it can also be booted from CD-ROM by passing the root= option to LILO.

My question is: What could cause this to happen, and how can I fix it? Why would this happen out of the blue? I compiled and rebooted the computer with my new kernel perhaps eight times, but then finally on the ninth reboot I suddenly get this error from LILO? I didn't do anything different, I simply do a "make; make modules; make modules_install", I then copy the bzImage kernel into /boot (and at the same time rename it to the proper name corresponding to the entry in lilo.conf).

I've also tried to simply reboot and add the kernel again, I've also tried to recompile, but according to the error the fault isn't with the kernel, but with lilo, like I wrote above i.e. that the second stage fails to load. Since I didn't touch lilo (in any other sense than executing the commanad "lilo") how could this happen?
 
Old 01-27-2009, 12:39 PM   #2
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Virginia, USA
Distribution: Debian 12
Posts: 8,349

Rep: Reputation: 552Reputation: 552Reputation: 552Reputation: 552Reputation: 552Reputation: 552
lilo places the absolute address of the kernel in the MBR and uses that absolute address to find the kernel. You have moved the kernel to a new location within /boot and the absolute address no longer points to the kernel image.

Run lilo to create a new MBR and all should be well.

-------------------
Steve Stites

P.S. Grub does not rely on absolute disk address so renaming the kernel would work in grub.

Last edited by jailbait; 01-27-2009 at 12:41 PM.
 
Old 01-27-2009, 12:53 PM   #3
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Linux 11 (Bullseye)
Posts: 3,407

Rep: Reputation: 141Reputation: 141
Quote:
Originally Posted by jailbait View Post
lilo places the absolute address of the kernel in the MBR and uses that absolute address to find the kernel.
It can't possibly be that, or we wouldn't be able to select from multiple kernels during the boot process. Looking in /boot/grub, which must be similar to lilo, I see stage1, stage1_5 for the various FS types, then stage2. From this, one must deduce that the MBR for grub has a hard pointer to at least the stage1 file. From there, grub loads some or all of its stage1_5 files, then loads stage2 and finally boots the kernel you've selected.
 
Old 01-27-2009, 01:23 PM   #4
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Virginia, USA
Distribution: Debian 12
Posts: 8,349

Rep: Reputation: 552Reputation: 552Reputation: 552Reputation: 552Reputation: 552Reputation: 552
Quote:
Originally Posted by Quakeboy02 View Post
It can't possibly be that, or we wouldn't be able to select from multiple kernels during the boot process. Looking in /boot/grub, which must be similar to lilo, I see stage1, stage1_5 for the various FS types, then stage2. From this, one must deduce that the MBR for grub has a hard pointer to at least the stage1 file. From there, grub loads some or all of its stage1_5 files, then loads stage2 and finally boots the kernel you've selected.
Yes, you are probably right. The problem is likely to be that posix_memalign has moved whatever the MBR has an absolute address for. I remember it as being for the kernel image but maybe it is for the map image that lilo creates when you issue the lilo command.

---------------------
Steve Stites

Last edited by jailbait; 01-27-2009 at 01:26 PM.
 
  


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



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

All times are GMT -5. The time now is 03:57 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