<BR>

</UL></UL>

<UL>

<UL>

<P>alias /dev/ttyS0, alias /dev/ttys1, alias /dev/ttys2, alias /dev/ttys3. All four ports can be used (if present).

<BR>

</UL></UL>

<UL>

<UL>

<P>&lt;bps&gt;. The baud rate of the serial port. The following baud rates are supported: 110, 150, 300, 600, 1200, 2400, 4800, and 9600 bps. Default is 2400 bps.

<BR>

</UL></UL>

<UL>

<UL>

<P>&lt;parity&gt;. The parity used on the serial line. LILO ignores input parity and strips the eighth bit. The following (upper- or lowercase) characters are used to describe the parity: n for no parity, e for even parity, and o for odd parity.

<BR>

</UL></UL>

<UL>

<UL>

<P>&lt;bits&gt;. The number of bits in a character. Only 7 and 8 bits are supported. Default is 8 if parity is none, 7 if parity is even or odd.

<BR>

</UL></UL>

<UL>

<LI>If serial is set, the value of delay is automatically raised to 20. Example: serial=0,2400n8 initializes COM1 with the default parameters.

<BR>

<BR>

<LI>ignore-table. Tells LILO to ignore corrupt partition tables.

<BR>

<BR>

<LI>fix-table. Allows LILO to adjust 3-D addresses in partition tables. Each partition entry contains a 3-D (sector/head/cylinder) and a linear address of the first and the last sector of the partition. If a partition is not track-aligned and if certain 
other operating systems (such as PC/MS-DOS or OS/2) are using the same disk, the operating system may change the 3-D address. LILO can store its boot sector only on partitions where both address types correspond. LILO readjusts incorrect 3-D start 
addresses if fix-table is set.

<BR>

<BR>

</UL>

<BLOCKQUOTE>

<BLOCKQUOTE>

<HR ALIGN=CENTER>

<BR>

<NOTE>fix-table does not guarantee that other operating systems might not attempt to reset the address later. It is also possible that this change has other, unexpected side effects. The correct fix is to repartition the drive with a program that does 
align partitions to tracks.</NOTE>

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<UL>

<LI>password=&lt;password&gt;. Sets a password for all images.

<BR>

<BR>

<LI>unsafe. This keyword is placed after a definition for a partition. The keyword tells LILO not to attempt to read the MBR or that disk's partition table entry. You can declare all the partitions in your system as a log of all exisiting partitions, then 
place the unsafe keyword entry to prevent LILO from reading it.

<BR>

<BR>

</UL>

<P>The kernel configuration parameters append, ramdisk, read-only, read-write, root, and vga can be set in the options section. They are used as defaults if they aren't specified in the configuration sections of the respective kernel images.

<BR>

<P>If the option -q is specified on the command line, the currently mapped files are listed. Otherwise, a new map is created for the images described in the configuration file /etc/lilo/config and they are written to in the boot sector.

<BR>

<BR>

<A NAME="E69E31"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>The boot Prompt</B></FONT></CENTER></H4>

<BR>

<P>When the system boots up, after the keyboard test, press and hold down one of any one of these keys: Alt, Shift, or Ctrl (or you can set the Caps Lock or Scroll Lock key). If any of these keys are pressed, LILO displays the boot: prompt and waits for 
the name of a boot image. Pressing the Tab key or typing ? gives you a list of names recognized by LILO. If you do not press any of these keys, LILO will boot up the first it finds in the lilo.conf file kernel (in this case, vmlinuz.cd) if there is no 
timeout specified in the /etc/lilo.conf file.

<BR>

<P>LILO can also pass command-line options to the kernel. Command-line options are words that follow the name of the boot image and are separated by spaces. Currently, the kernel recognizes the options root=&lt;device&gt;, ro, and rw, and all current init 
programs also recognize the option single, which boots the system in single-user mode. This bypasses all system-initialization procedures and directly starts a root shell on the console. Multiuser mode can be entered by exiting the single-user shell or by 
rebooting.

<BR>

<P>The option vga is processed by the boot loader itself. The option vga=&lt;mode&gt; alters the VGA mode that was set at startup. The legal values for mode are NORMAL, EXTENDED, ASK, or a decimal number for the BIOS mode command. You can get a list of 
available modes by typing vga=ask and pressing Enter.

<BR>

<P>The root=&lt;device&gt; option changes the root device. This overrides settings that may have been made in the boot image and on the LILO command line.

<BR>

<UL>

<UL>

<P>&lt;device&gt; is either a hexadecimal device number or the full pathname of the device, such as /dev/hda3. (The device names are hard-coded in the kernel.)

<BR>

</UL></UL>

<UL>

<UL>

<P>ro instructs the kernel to mount the root file system as read-only. rw mounts it as read-write. If neither ro nor rw is specified, the setting from the boot image is used.

<BR>

</UL></UL>

<UL>

<UL>

<P>The no387 option disables using the hardware FPU.

<BR>

</UL></UL>

<P>Depending on the kernel configuration, some special configuration options for nonstandard hardware might be recognized as well. Some of these boot prompts include the following :

<BR>

<UL>

<LI>For a Panasonic CD-ROM with SoundBlaster support, use sbpcd=0x340,SoundBlaster.

<BR>

<BR>

<LI>For a bus mouse, use bmouse=irq.

<BR>

<BR>

<LI>For reserving ports from being autoprobed by device drivers in special hardware device-conflict situations, you can use reserve=port,size. For example, reserve=0x200,8 will reserve 8 ports starting at 0x200 from being probed by device drivers.

<BR>

<BR>

<LI>Ethernet cards usually take parameter from the ether=x,x,x,... command. The actual parameters sent depend on the type of card.

<BR>

<BR>

<LI>For Mitsumi CD-ROM, use mcd=port,irq&#151;for example, mcd=0x340,11.

<BR>

<BR>

<LI>If your Ethernet card is not recognized, try ether=10,0x340 to probe for it at port 0x340 using interrupt 10. Note that the interrupt number here is given before the port number is given for the Mitsumi CD-ROM driver.

<BR>

<BR>

</UL>

<P>The parameters for each type of device will come with their documentation, so do not assume anything. Use only specified values. If you do follow instructions, you may wind up causing irrecoverable errors, which may lead to a corrupt file system.

<BR>

<BR>

<A NAME="E69E32"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Uninstalling LILO</B></FONT></CENTER></H4>

<BR>

<P>In order to keep LILO from being invoked when the system boots, its boot sector has to be either removed or disabled. All other files belonging to LILO can be deleted after removing the boot sector, if desired.

<BR>

<P>LILO 0.14 (and newer) can be uninstalled with the lilo -u command.

<BR>

<P>If LILO's boot sector has been installed on a primary partition and is booted by the standard MBR or some partition-switching program, it can be disabled by making a different partition active. MS-DOS's FDISK, Linux's fdisk, or LILO's activate can do 
that.

<BR>

<P>If LILO's boot sector is the Master Boot Record (MBR) of a disk, it has to be replaced with a different MBR, typically MS-DOS's standard MBR. When using MS-DOS 5.0 or above, the MS-DOS MBR can be restored with FDISK /MBR. This alters only the boot 
loader code, not the partition table. LILO automatically makes backup copies when it overwrites boot sectors. They are named /etc/lilo/boot.&lt;nnnn&gt;, with &lt;nnnn&gt; corresponding to the device number&#151;that is, 0300 is /dev/hda, 0800 is /dev/sda, 
and so on. Those backups can be used to restore the old MBR if no easier method is available.

<BR>

<P>The commands are

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">dd if=/etc/lilo/boot.0300 of=/dev/hda bs=446 count=1</FONT></PRE>

<P>or

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">dd if=/etc/lilo/boot.0800 of=/dev/sda bs=446 count=1</FONT></PRE>

<P>respectively.

<BR>

<BLOCKQUOTE>

<BLOCKQUOTE>

<HR ALIGN=CENTER>

<BR>

<NOTE>Some other operating systems (such as MS-DOS 6.0) appear to modify the MBR in their install procedures. It is therefore possible that LILO will cease to work after such an installation and Linux has to be booted from floppy disk. The original state 
can be restored by either rerunning /etc/lilo/lilo (if LILO is installed as the MBR) or by making LILO's partition active (if it's installed on a primary partition).

<BR>Typically, the new operating system then has to be added to LILO's configuration (and /etc/lilo/lilo has to be rerun) in order to boot it.</NOTE>

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<BR>

<A NAME="E69E33"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Map Installer Errors</B></FONT></CENTER></H4>

<BR>

<P>Some messages that indicate common errors when installing the maps are as follows:

<BR>

<UL>

<LI>Can't put the boot sector on logical partition &lt;number&gt;

<BR>You attempted to put LILO's boot sector on the current root file system partition, which is on a logical partition. This usually doesn't have the desired effect, because common MBRs can boot only primary partitions. This check can be bypassed by 
explicitly specifying the boot partition with the -b option or by setting the configuration variable boot.

<BR>

<BR>

<LI>Device 0x&lt;number&gt;: Got bad geometry &lt;sec&gt;//&lt;cyl&gt;

<BR>The device driver for your SCSI controller does not support geometry detection. You have to use an /etc/lilo/disktab file.

<BR>

<BR>

<LI>Device 0x&lt;number&gt;: Invalid partition table, entry &lt;number&gt;

<BR>The 3-D and linear addresses of the first sector of the specified partition don't correspond. LILO can attempt to correct the problem; see variable FIX-TABLE.

<BR>

<BR>

<LI>First sector of &lt;device&gt; doesn't have a valid boot signature

<BR>The first sector of the specified device does not appear to be a valid boot sector. Check the device name.

<BR>

<BR>

<LI>geo_comp_addr: Cylinder number is too big (&lt;number&gt; &gt; 1023)

<BR>A file is located beyond the 1024th cylinder of a hard disk. LILO can't access such files, because the BIOS limits cylinder numbers to the range 0-1023. Try moving the file to a different place, preferably a partition that is entirely within the first 
1024 cylinders of the disk.

<BR>

<BR>

<LI>&lt;item&gt; doesn't have a valid LILO signature

<BR>The specified item has been located, but it is not part of LILO. If &lt;item&gt; is the first boot sector, you've probably forgotten to specify the -i option or the install variable to install the LILO boot sector.

<BR>

<BR>

<LI>&lt;item&gt; has an invalid stage code (&lt;number&gt;)

<BR>The specified item has probably been corrupted. Rebuild LILO.

<BR>

<BR>

<LI>&lt;item&gt; is version &lt;number&gt;. Expecting version &lt;number&gt;

<BR>The specified entity is either too old or too new. Make sure all parts of LILO (map installer, boot loaders, and chain loaders) are from the same distribution.

<BR>

<BR>

<LI>Kernel &lt;name&gt; is too big

<BR>The kernel image (without the setup code) is bigger than 512KB. LILO would overwrite itself when trying to load such a kernel. Try removing some unused drivers and compiling the kernel again.

<BR>

<BR>

<LI>Partition entry not found

<BR>The partition from which another operating system should be booted isn't listed in the specified partition table. This means either that an incorrect partition table has been specified or that you're trying to boot from a logical partition. The latter 
usually doesn't work. You can bypass this check by omitting the partition table specification (that is, omitting the variable table).

<BR>

<BR>

<LI>Sorry, don't know how to handle device &lt;number&gt;

<BR>LILO uses files that are located on a device for which there is no easy way to determine the disk geometry. Such devices have to be described in the file /etc/lilo/disktab.

<BR>

<BR>