Hi, On Mon, 2 Feb 1998, Wayne Topa wrote:
From Page 123 of SuSE 5.1 book, Section 8.3.4
QUOTE
"ANY part of LILO has to be on the first 1024 cylinders on the hard disk."
From Yast.debug "/dev/hda3 * 977 977 1518 256095 83 Linux native"
Consider how LILO works: When you install LILO, it generates a map-file /boot/map which holds the CHS-position (cylinder/head/sector) of all the files needed for booting. This is the second stage loader /boot/boot.b and the kernel image /vmlinuz itself. Because LILO has to do all of its work by BIOS means it is restricted to cylinder numbers less than 1024. If you have a partition setup like above with the partition starting at 977 and ending at 1518, results are unpredictable. If all of /boot/map, /boot/boot.b and /vmlinuz happen to sit on cylinders below 1024, LILO will work without problems because every needed sector can be loaded with BIOS calls. If one single sector is on a cylinder >= 1024, LILO will fail.
Yes I could put the kernel on hda1. BUT I have the SuSE kernel where the BOOK says it should work. Lilo 19 DID work with the Debian kernel on hda3 (start cylinder 977), so is the problem with lilo 20?
No. You simply had luck when installing debian. Probably debian uses another installation order so all the relevant files for booting happened to sit on cylinders below 1024. If you had recompiled your kernel, there had been chances for LILO to fail afterwards.
Which statement is true: All of the kerner MUST be on cylinders < 1024, (BB) OR ANY part of the kernel has to be on the FIRST 1024 cylinders??? (Book)
I think this is a problem with a foreign/other/strange/alien/unknown language ;-) The book should probably read "EVERY part of the kernel...". And additionally: "This is true for the files /boot/boot.b and /boot/map also". Please note that /boot/map is generated when LILO is installed.
Thanks for your help. Chus (Is that spelled right ?)
Wayne
Hubert PS: If you are interested in how LILO and bootmanagers work, there is an excellent documentation in /usr/doc/packages/lilo. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e