LILO (boot loader)

From Wikipedia, the free encyclopedia - View original article

LILO
Lilo.png
Standard LILO menu display.
Developer(s)Werner Almesberger (1992–1998), John Coffman (1999–2007), Joachim Wiedorn (since 2010)
Stable release24.0 (7 June 2013)
Development statusmaintained
TypeBootloader
LicenseBSD license
Websitehttp://lilo.alioth.debian.org/
 
Jump to: navigation, search
LILO
Lilo.png
Standard LILO menu display.
Developer(s)Werner Almesberger (1992–1998), John Coffman (1999–2007), Joachim Wiedorn (since 2010)
Stable release24.0 (7 June 2013)
Development statusmaintained
TypeBootloader
LicenseBSD license
Websitehttp://lilo.alioth.debian.org/

LILO (LInux LOader) is a boot loader for Linux and was the default boot loader for most Linux distributions in the years after the popularity of loadlin. Today, most distributions use GRUB as the default boot loader.

Overview[edit]

LILO does not depend on a specific file system, and can boot an operating system (e.g., Linux kernel images) from floppy disks and hard disks. One of up to sixteen different images can be selected at boot time. Various parameters, such as the root device, can be set independently for each kernel. LILO can be placed in the master boot record (MBR) or the boot sector of a partition. In the latter case, the MBR must contain code to load LILO.

At system start, only the BIOS drivers are available for LILO to access hard disks. For this reason, a very old BIOS access area is limited to cylinders 0 to 1023 of the first two hard disks. For a later BIOS, LILO can use 32-bit "logical block addressing" (LBA) to access the entire capacity of the hard disks the BIOS has access to.

LILO files[edit]

lilo.conf[edit]

The lilo.conf file is typically located at /etc/lilo.conf. Within lilo.conf there are typically two section types. The first section, which defines the global options, contains parameters which specify boot location attributes. The second section(s) contain parameters associated with the operating system images to be loaded. The section type can be repeated for up to 16 different boot selections.

Remember to run the /sbin/lilo command after editing the /etc/lilo.conf file so that your changes take effect.

Definition information can be found in the LILO Manpage.

An example for /etc/lilo.conf:

 large-memory lba32 boot=/dev/hda install=menu map=/boot/map prompt   default=Linux image=/boot/vmlinuz-2.6.26 label="Linux" root=/dev/hda1 append="" read-only optional   other=/dev/hda3 label="FreeBSD" 

Note: Here LILO offers after correct installation a menu with Linux and FreeBSD.

/boot/[edit]

LILO stores a number of files in the /boot/ – see /boot/: LILO.

Master boot record[edit]

Main article: Master boot record

LILO can write a Master Boot Record on a device:

 /sbin/lilo -M 

Output[edit]

When LILO loads itself it displays the word “LILO”. Each letter is printed before or after some specific action. If LILO fails at some point, the letters printed so far can be used to identify the problem.

(nothing)
No part of LILO has been loaded. LILO either isn't installed or the partition on which its boot sector is located isn't active. The boot media is incorrect or faulty.
L
The first stage boot loader has been loaded and started, but it can't load the second stage boot loader. The two-digit error codes indicate the type of problem. This condition usually indicates a media failure or bad disk parameters in the BIOS.
LI
The first stage boot loader was able to load the second stage boot loader, but has failed to execute it. This can be caused by bad disk parameters in the BIOS.
LIL
The second stage boot loader has been started, but it can't load the descriptor table from the map file. This is typically caused by a media failure or by bad disk parameters in the BIOS.
LIL?
The second stage boot loader has been loaded at an incorrect address. This is typically caused by bad disk parameters in the BIOS.
LIL-
The descriptor table is corrupt. This can be caused by bad disk parameters in the BIOS.
LILO
All parts of LILO have been successfully loaded.

Error codes[edit]

e.g.: L 01 01 01, L 07 07 07 etc..

Error codeNameDescription
0x00Internal ErrorThis code is generated by the sector read routine of the LILO boot loader whenever an internal inconsistency is detected. This might be caused by corrupt files. Try re-building the map file. Another possible cause for this error are attempts to access cylinders beyond 1024 while using the LINEAR option.
0x01Illegal CommandThis shouldn't happen, but if it does, it may indicate an attempt to access a disk which is not supported by the BIOS. Definitely check to see if the disk is seen by the BIOS first (and that the BIOS detail is complete).
0x02Address mark not foundThis usually indicates a media problem. Try again several times.
0x03Write-protected diskThis should only occur on write operations.
0x04Sector not foundThis typically indicates a geometry mismatch. If you're booting a raw-written disk image, verify whether it was created for disks with the same geometry as the one you're using. If you're booting from a SCSI disk or a large IDE disk, you should check, whether LILO has obtained correct geometry data from the kernel or whether the geometry definition corresponds to the real disk geometry. Removing COMPACT may help too. So may adding LBA32 or LINEAR.
0x06Change line activeThis should be a transient error. Try booting a second time.
0x07Invalid initializationThe BIOS failed to properly initialize the disk controller. You should control the BIOS setup parameters. A warm boot might help too. (Boot a rescue disc and rerun LILO.)
0x08DMA overrunThis shouldn't happen. Try booting again.
0x09DMA attempt across 64k boundaryThis shouldn't happen, but may indicate a disk geometry mis-match. Try omitting the COMPACT option. You may need to specify the disk geometry yourself.
0x0CInvalid mediaThis shouldn't happen and might be caused by a media error. Try booting again.
0x10CRC errorA media error has been detected. Try booting several times, running the map installer a second time (to put the map file at some other physical location or to write "good data" over the bad spot), mapping out the bad sectors/tracks and, if all else fails, replacing the media.
0x11ECC correction successfulA read error occurred, but was corrected. LILO does not recognize this condition and aborts the load process anyway. A second load attempt should succeed.
0x20Controller errorThis shouldn't happen, then again, none of these errors should happen eh?
0x40Seek failureThis might be a media problem. Try booting again.
0x80Disk timeoutThe disk or the drive isn't ready. Either the media is bad or the disk isn't spinning. If you're booting from a floppy, you might not have closed the drive door. Otherwise, trying to boot again might help.
0x99Invalid Second StageMismatch between drive and BIOS geometry, or a bad map file. Some evidence that LINEAR needs to be set on the disk (see LiloNotes)
0x9ACan't Find Second StageCheck to see if you have the correct device for boot, e.g. boot=/dev/hda1 when it should be in the MBR i.e. boot=/dev/hda.
0xBBBIOS errorThis shouldn't happen. Try booting again. If the problem persists, removing the COMPACT option or adding/removing LINEAR or LBA32 might help.

elilo[edit]

elilo
Developer(s)HP
Stable release3.16 / March 29, 2013
TypeBootloader
LicenseGPL
Websiteelilo.sf.net

For EFI-based PC hardware the elilo boot loader was developed,[1] originally by Hewlett Packard for IA-64 systems made, but later also for standard Intel IA-32 and x86-64 hardware with EFI support.

On any version of Linux running on Intel-based Apple Macintosh hardware, elilo is one of the available bootloaders.[2]

It supports network booting using TFTP/DHCP.

See also[edit]

Notes[edit]

References[edit]

External links[edit]