M-Systems Flash Disk Pioneers 91-SR-005-10-7L Benutzerhandbuch
Using the DiskOnChip with Linux OS
91-SR-005-10-7L REV. 2.0
22
Appendix II: Booting from a HDD when the DiskOnChip Firmware
is Active
is Active
Since Lilo and the DiskOnChip firmware (i.e. doc121.exb) share the same area in RAM, the system
will hang during boot when using an unpatched Lilo. Updating Lilo solves this problem. The existing boot
loader needs to be updated as follows:
will hang during boot when using an unpatched Lilo. Updating Lilo solves this problem. The existing boot
loader needs to be updated as follows:
# /tmp/doc-driver/plilo -i /tmp/doc-driver/boot.b
This command uses the patched Lilo supplied by the TrueFFS driver and patched boot.b, and your
default /etc/lilo.conf. Make sure that you run this command in the Linux that booted from the
HDD.
default /etc/lilo.conf. Make sure that you run this command in the Linux that booted from the
HDD.
pLilo is actually forcing you to use smaller kernels because it allocates part of the physical memory to the
driver. Therefore, big kernels (around 470 KB) will have a problem with pLilo (pLilo will stop with an error
‘Kernel xxx is too big’). There are two solutions to this problem:
driver. Therefore, big kernels (around 470 KB) will have a problem with pLilo (pLilo will stop with an error
‘Kernel xxx is too big’). There are two solutions to this problem:
1. Compile the kernel with the bzImage option (‘make bzImage’). Refer to
/usr/doc/HOWTO/Kernel-HOWTO.gz
for more information.
2. Comment out all big kernels from lilo.conf (only during the installation procedure).
M-Systems provides a patch file to Lilo sources to make pLilo. To activate the patch, you must have the
Lilo sources available on your system. After you verify that the sources are available, type the following
command:
Lilo sources available on your system. After you verify that the sources are available, type the following
command:
# patch -p0 < lilo-patch
You now have pLilo sources.