See also following documents:
See the documentation of Lilo on your Linux system :
# Use the kghostview, ghostview or gv command
kghostview /usr/share/doc/lilo-21.4.4/doc/user.ps
# To read in HTML format do this -
mkdir $HOME/lilodocs
cd $HOME/lilodocs
cp /usr/share/doc/lilo-21.4.4/doc/user.tex .
latex2html user
# This creates the html files in user directory
Section 17, “ Appendix C - GRUB Details And A Sample grub.conf ” GRUB Conf file.
"http://www.linuxdoc.org/HOWTO/LILO-crash-rescue-HOWTO.html" .
The beeper error codes :
Table 1. Beeper Error Codes Table
| Code | Description |
|---|---|
| 0 | PC-Speaker Defect |
| 1 | Refresh of DRAM defect |
| 2 | Paritykring defect |
| 3 | Error in the 64 basis RAM |
| 4 | Systeemtimer defect |
| 5 | Processor defect |
| 6 | Keyboard controller error |
| 7 | Virtuele modus error |
| 8 | Test from videomemory failed |
| 9 | ROM-BIOS checksumm error |
2 short beeps : POST not correct. Error in a Harware test. 1 short & 2 long beeps : video error. 1) Video ROM BIOS, parity error. 2) Problem with the horizontal retour from the video adapter. 1 long & 3 short beeps: video error. 1) videocard defect. 2) wrong detection from used monitor. 3) Video RAM error. 1 long beep : POST was correct If there is a posterror, there is a hardwareproblem. Check the extentioncards for a bad contact
See also http://www.preggers.easynet.be/lilo.html
If you get problems in LILO, refer to following tips. During boot if you get error "L0101010101010101 ....", then do this
Use your favorite text editor to open /etc/lilo.conf
# Find the line that reads
linear
# Comment it out. Change it to read
# linear
Save and rerun lilo.
You need to have your booting partion below the 8 gb mark. If you have a program like parition magic or Mandrake's DiskDrake utility you can easily fix this.
01 is dram refresh error. When you get the L 01 simply reboot again with CTRL+ATL+DEL (but you should not power off just do ctrl+alt+del). This may correct the problem.
Always give a date extension to the filename, because it tells you when you built the kernel, as shown below:
bash# man lilo
bash# man lilo.conf
And edit /etc/lilo.conf file and put these lines -
image=/boot/bzImage.myker.26mar2001
label=myker
root=/dev/hda1
read-only
You can check device name for 'root=' with the command -
bash# df /
Now give -
bash# lilo
bash# lilo -q
You must re-run lilo even if the entry 'myker' exists, everytime you create a new bzImage.
Given below is a sample /etc/lilo.conf file. You should follow the naming conventions like ker2217 (for kernel 2.2.17), ker2214 (for kernel 2.2.14). You can have many kernel images on the same /boot system. On my machine I have something like:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=firewall
image=/boot/vmlinuz-2.2.14-5.0
label=ker2214
read-only
root=/dev/hda9
image=/boot/vmlinuz-2.2.17-14
label=ker2217
read-only
root=/dev/hda9
#image=/usr/src/linux/arch/i386/boot/bzImage
# label=myker
# root=/dev/hda7
# read-only
image=/boot/bzImage.myker.11feb2001
label=myker11feb
root=/dev/hda9
read-only
image=/boot/bzImage.myker.01jan2001
label=myker01jan
root=/dev/hda9
read-only
image=/boot/bzImage.myker-firewall.16mar2001
label=firewall
root=/dev/hda9
read-only