Commit ec7bcad8 authored by Joachim Wiedorn's avatar Joachim Wiedorn

Update of README.Debian file

parent 8114b945
--[ Distribution upgrade
README for lilo in Debian
-------------------------
** Distribution upgrade **
If you are upgrading or dist-upgrading, it is recommended to run
/sbin/lilo after that.
--[ Large initrd files and lilo
By default, LILO loads the initrd file into the first 15MB of memory
to avoid a BIOS limitation with older systems (earlier than 2001).
** Large initrd files **
Usually LILO loads the initrd file into the first 15MB of memory to
avoid a BIOS limitation with older systems (earlier than 2001 and
few systems until 2004).
However, with newer kernels the combination of kernel and initrd
may not fit into the first 15MB of memory and so the system will not
boot properly. It seems that the boot issues appear when the
kernel+initrd combination is larger than 8MB.
With newer kernels the combination of kernel and initrd may not fit
into the first 15MB of memory. LILO compute the needed size of memory
and will automatically use the memory above 15MB, too, if there is
enough physical memory. Then lilo give you information about this
while running lilo.
If this machine has a recent BIOS without the 15MB limitation, you can
add the 'large-memory' option to /etc/lilo.conf to instruct LILO to use
more memory for passing the initrd to the kernel. You will need to
re-run the 'lilo' command to make this option take effect.
If this machine has a recent BIOS without a 15MB limitation and you
want to use memory above 15MB for all kernels, set the 'large-memory'
option. You will need to re-run the 'lilo' command to make this
option take effect.
If this machine has an older BIOS, you may need to reduce the size of
the initrd *before* rebooting.
** Solve the 15MB problem **
If the machine has an older BIOS which don't can use any memory above
15MB you should use the newer option 'small-memory' in /etc/lilo.conf
to instruct LILO to use only the memory below the 15MB line. You may
need to reduce the size of the initrd *before* rebooting.
If you are using initramfs-tools, you should replace MODULES=most with
MODULES=dep in your configuration and regenerate your initrd file:
sed -i -e s/MODULES=most/MODULES=dep/ /etc/initramfs-tools/initramfs.conf
update-initramfs -u
sed -i -e s/MODULES=most/MODULES=dep/ /etc/initramfs-tools/initramfs.conf
update-initramfs -u
** Inaccessible devices **
The old patch for better support for inaccessible disks based on
problems with usb sticks. But this option 'inaccessible' is only
usable, if hard disks can not be accessed by the BIOS, but can always
be accessed by linux. This option is not sensible for usb sticks,
which will always bring failures if they are named in the lilo.conf.
So please don't use the option 'inaccessible' not for usb sticks and
other removable devices.
** Inactive disks of MD RAID-1 array **
RAID-1 devices are supported as boot device. If not all RAID-1 disks
are activated use '-H' to install only to active disks. This option
override fatal halt while found an inactive disk of an RAID-1 array.
Warning: Booting with partial RAID-1 installation only on active disks
is not failsafe!
If you are using yaird or any other initrd generator, please consult
the documentation for your initrd generator.
......@@ -43,6 +43,7 @@ lilo (1:23.1-1) unstable; urgency=low
* Move debian/Makefile.floppy into debian/floppy directory.
* Add debian/lilo.install file.
* Add lintian-overrides for package lilo.
* Update debian/README.Debian file.
-- Joachim Wiedorn <ad_debian@joonet.de> Thu, 18 Nov 2010 23:52:02 +0100
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment