![](https://seccdn.libravatar.org/avatar/3d60551c4ad5942138d8ec54fd6d971e.jpg?s=120&d=mm&r=g)
Lilo likes the /boot partition to be inside the 1st 1024 cylinders (2Gb). Does your BIOS understand drives >2 gb - with older bioses this can cause the LI prompt - and is the /boot within the 1st 2 gig? On Wednesday, April 19, 2000 1:19 PM, Cliff Pankonien [SMTP:jackdaw@jackdaw.net] wrote:
Hello, all; I recently installed 6.4 on an AMD K62-450 with two ide drives, a 4 gig and a 1.5 gig. When I reboot I get the LI prompt, I can boot using the boot disk and booting from hda2 (hda1 being the swap partition). When I run /usr/sbin/lilo, I get the following error - Hole found in map file (alloc_page). I also got this same error when doing the initial installation. Any ideas?
Thanks,
Cliff Pankonien jackdaw@jackdaw.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"WorldSecure Server <lombard.co.uk>" made the following annotations on 04/19/00 13:40:14 ------------------------------------------------------------------------------ The opinions expressed within this email represent those of the individual and not necessarily those of Lombard. The contents of this Email may be privileged and are confidential. It may not be disclosed to or used by anyone other than the addressee(s), nor copied in any way. If received in error, please advise the sender, then delete from your system. Should you wish to use Email as a mode of communication, Lombard are unable to guarantee the security of Email content outside of our own computer systems. ============================================================================== -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
![](https://seccdn.libravatar.org/avatar/9fe7324b963d268ec9106ffd7bd24d4e.jpg?s=120&d=mm&r=g)
On Wed, 19 Apr 2000, Paul Sims wrote:
Lilo likes the /boot partition to be inside the 1st 1024 cylinders (2Gb).
Lilo doesn't care. But it's using the BIOS for its disk I/O, and the BIOS disk I/O routines in some (all?) BIOSes can't go beyond 1,024 cylinders. How much space is within 1,024 cylinders depends on drive geometry and whether you are using LBR. It can be as much as 8-point-something gigabytes.
Does your BIOS understand drives >2 gb - with older bioses this can cause the LI prompt - and is the /boot within the 1st 2 gig?
AFAIK there has never been a BIOS with a 2-gig limit. Pre-LBR BIOSes had a 512-meg limit on IDE drives, because of a conflict between how the BIOS wanted to address the disk and how the IDE spec addresses the disk. LBR moved that limit, initially to a bit over 8 gig (the limit that the BIOS could address, absent the conflict with IDE - meaning that the change *ought* to be completely transparent to software running on top of the BIOS.) At the same time, some sort of provision was made for "large" drives, which are subject to the IDE limits which allow a much higher maximum capacity than the BIOS limits. This implies that the change might not be completely transparent. The 2-gig limit came from the FAT16 file system, and is a per-partition limit. And it doesn't matter whether the disk is IDE, SCSI, or even Winchester (although I don't think anyone ever made a 2-gig Winchester drive).
On Wednesday, April 19, 2000 1:19 PM, Cliff Pankonien [SMTP:jackdaw@jackdaw.net] wrote:
Hello, all; I recently installed 6.4 on an AMD K62-450 with two ide drives, a 4 gig and a 1.5 gig. When I reboot I get the LI prompt, I can boot using the boot disk and booting from hda2 (hda1 being the swap partition). When I run /usr/sbin/lilo, I get the following error - Hole found in map file (alloc_page). I also got this same error when doing the initial installation. Any ideas?
This simply means that, for some reason, LILO couldn't read the kernel. I'm thinking about that error message from /usr/sbin/lilo, and what I *think* it means is that the map file is not contiguous. Make a new copy of the map file in the same directory, and rename both copies so that the new copy has the old name. See if that fixes the error that you get when running /usr/sbin/lilo. If so, it might (good chance but not certainty) also fix the booting problem. It could also mean that not all of the map file is accessible to the BIOS. In which case you absolutely must move the map file earlier on the disk. Don't move the kernel to make room, because both these files need to be ENTIRELY in cylinders 0 to 1,023 as percieved by the BIOS. One thing that is frequently recommended (including by me) is to have a small (8 meg is good unless you want to have 3 or more versions of the kernel available at one time) /boot partition early on the disk. The entire partition will be within the area the BIOS can reach, so no problem there. It will also be rarely used except at boot time - when it is only read, not written to - so it won't soon become fragmented. (If you ever become suspicious that it is fragmented: move the files to another partition, clean out the /boot partition, move the files back, and rerun lilo.) Another thing that could be causing your boot problem (but not the other error) is if linux sees the disk geometry differently than the BIOS. When you run /usr/sbin/lilo, you are using linux's perception; at boot time the BIOS's perception matters. If they don't agree, there's a good chance that the bootloader won't be able to find the kernel. However, there's a way around that disagreement. In lilo.conf, add (near the top) a line that just says linear This tells lilo to convert cylinder/head/sector locations on disk to just a sector number, as if all the sectors were spread out in a line and counted. Then at boot time the reverse conversion will be done, using the geometry as the BIOS sees it - so it will end up with the same sector even if the geometry is different. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (2)
-
psims@lombard.co.uk
-
warrl@blarg.net