|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
You eat, breathe and sleep innovation. Build your mobile intelligence with BlackBerry® experts this July. Register Today! |
|
#1
|
||||
|
||||
|
LILO Error Code - L?L?
So, what the heck is error code L?L? anyway? The closest thing I can find is LIL? which means:
Quote:
I can't find anything about error L?L?, so what is it? Any help in resolving this error would be much appreciated. |
|
#2
|
||||
|
||||
|
Hopefully you have a boot disk handy, because you're going to have to boot from it and play with the configuration of /etc/lilo.conf.
I can't give you a whole lot of help, because the configuration is VERY system dependent. Remember to run "/sbin/lilo" after you tweak lilo.conf to write the changes to your boot sector. . . What did you do that could've messed up lilo? Kernel upgrade? Fix your boot sector with a windows virus program (if you dual-boot)? |
|
#3
|
||||
|
||||
|
oops, sorry... should have been specific. I have my lilo.conf set up with 2 linux kernels and a dos partition on a different disk. The linux kernels launch ok, but when I try to launch dos I get L?L? and it locks.
My dos partition should, in theory, be on hdb1 which is where I have lilo.conf pointed. I ran /sbin/lilo each time I made a conf change, so that's not it. |
|
#4
|
||||
|
||||
|
Well, here's my working lilo.conf, don't know if the "other" section will be much help. . .
Please post your lilo.conf, and the output of df, maybe we can suss something out. Code:
prompt
timeout=50
default=linux
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
lba32
image=/boot/vmlinuz-2.4.18-3
label=linux
initrd=/boot/initrd-2.4.18-3.img
read-only
root=/dev/hda6
other=/dev/hda1
optional
label=DOS
|
|
#5
|
||||
|
||||
|
Code:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=2.4.16-xx
image=/boot/vmlinuz-2.2.16-22
label=2.2.16-22
read-only
root=/dev/hda1
image=/boot/vmlinuz-2.4.18
label=2.4.18-xx
read-only
root=/dev/hda1
other=/dev/hdb1
label=dos
I'm curious about the linear setting. I'm going to change it to lba32 and see if that helps. Nope... wait.. I'm thinking maybe hdb1 isn't getting mounted.. I just noticed I have no /mnt/dos even though it's in fstab.. wonder where it went... Last edited by Ctb : September 11th, 2002 at 09:56 PM. |
|
#6
|
||||
|
||||
|
Well, one thing off the bat is that your "default" doesn't match any valid labels in your entries.
Code:
default=2.4.16-xx . . . label=2.2.16-22 . . . label=2.4.18-xx I guess it's possible it's getting screwed up from this, but I doubt it. Chances are your drive uses lba32 addressing, that may very well fix it. Let us know! |
|
#7
|
||||
|
||||
|
Whoops.. typo (default matches the 2.4.18-xx entry in the real file).
lba32 didn't work. I noticed that my /mnt/dos directory was gone so I put it back. Now I don't get L?L? when I try to launch dos, I just get nothing... [edit] Whoops, forgot to run /sbin/lilo... [/edit] No, still no good.... Last edited by Ctb : September 11th, 2002 at 10:25 PM. |
|
#8
|
||||
|
||||
|
OK, I knew this was bad news from the start but I did it anyway:
I changed boot= to boot=/dev/hdb which, of course, fragged my Windows disk's boot sector. This caused 3 separate mount problems under Linux and of course did not solve the problem, so, I stuck in my windows boot disk and "sys"ed the drive back to "life" as it were. However, I am now stuck with this problem. LILO has taken over the MBR on the other disk, so unless I can figure out why I get L? when I try to boot Windows, I'll never get back into it. Perhaps, part of my problem was that my /mnt/dos directory was gone? I put it back so now fstab's entry is valid and the FAT mount succeeds when I boot up, but I can't boot to it with LILO.... ugh... windows is giving me headaches even when I'm NOT using it.... Now I'm going to have to go fdsk /mbr my other disk. Has anyone done this before? I don't trust fdsk in the least.... [speculation] It would seem to me that if I say "linear" mode in lilo.conf for a 40GB disk... that doesn't make geometric sense. It would almost HAVE to be lba32.... yet, that fails as well... [/speculation] |
|
#9
|
||||
|
||||
|
Just idle speculation, but in Hero's lilo.conf there was the line "optional" for the dos entry, and not in Ctb's.... I seem to remember having that line when I used to dual boot, so maybe that's something? (it probably does nothing now I saw it lol
) |
|
#10
|
||||
|
||||
|
Well, here's the thing I think I need to sort out first... if I have two drives, where does LILO/Linux get it's assignments from, BIOS? That is, say I set up my BIOS to try booting from Disk 2 first, which is the disk that contains Linux. Now, does that BIOS setup make my Linux disk hda1 and my Windoze disk hdb1? If that's the case then if I install LILO over the MBR on the first disk and change BIOS to boot from disk 1 first, doesn't Windoze then become hda1 and Linux hdb1? If that's the case, how the heck would I set my lilo.conf file up for that...? googling as I speak.
|
|
#11
|
||||
|
||||
|
I believe it works like this-
Whatever drive that's set as the master is /dev/hda, the slave is /dev/hdb. Lilo is usually installed on MBR of /dev/hda, and you can then boot from whatever partition you wish. |
![]() |
| Viewing: Dev Shed Forums > Operating Systems > Linux Help > LILO Error Code - L?L? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|