Re: lilo and L 01 01 01 01 on older pc with 30GB hard disk

On Sat, 25 Mar 2006 09:45:29 -0500, psantoro <psantoro@xxxxxxxxxxxx> wrote:

<snip>

Any ideas on how to make this hardware combo work without using the boot
floppy is appreciated. Is the answer that I need to create a small
(less than 8GB, within the 1024 cylinder limit) /boot partition? If so,
I was under the impression that the version of lilo (22.5.9) in
slackware 10.2 gets around this bios limitation - but I could be wrong.

LILO can try to use LBA addressing since version 21.4-4. However, if the BIOS
does not support LBA (lba32) addressing, then the LILO support for it is moot.

By removing EZ-BIOS, you have defeated LBA addressing. 2.4 kernels recognize
EZ-BIOS and respect the boot sector mapping. 2.6 kernels remove this
recognition for some [unknown] reason.

You can:

1. Re-install EZ-BIOS (if you use a 2.4 kernel).
2. Create a /boot partition below the 1024 cylinder limit. With LILO version
22.5.9 and later, you will then place the kernel, initrd, and /boot/map files
within this partition. These are the three files needed by LILO at boot time;
they MUST be BIOS-accessible.

Version 2 kernels access the IDE controller directly; the old BIOS will not
matter. The only trouble will occur if you use a very old kernel which is
limited to 28-bit IDE (lba) addresses. Newer kernels use the 48-bit IDE (lba)
addressing scheme. The disk size is above about 137GB where the newer kernels
will be needed.

--John



.

Relevant Pages

  • Problem: running lilo corrupts filesystem on first partition
    ... Problem kernels: vanilla 2.6.14-rc5 and Ubuntu kernel 2.6.12-9-686 ... I am using a script that executes a sequence of commands similar to the ... The problem is that running lilo causes the first few sectors of the ... this script will wipe out the disk! ...
    (Linux-Kernel)
  • Re: lilo and L 01 01 01 01 on older pc with 30GB hard disk
    ... By removing EZ-BIOS, ... EZ-BIOS and respect the boot sector mapping. ... kernels remove this ... So my first mistake was assuming that my original lilo errors were due to ez-bios, when in fact they were due to bios-inaccessible files needed by lilo. ...
    (comp.os.linux.setup)
  • Re: kernel version modules
    ... Not sure why it says i686, since the kernels say i386 (Although I've ... Both options will uninstall the packages. ... Unless you used the optional flag in lilo, you nay need to re-run lilo. ... Unless you used the optional flag in lilo, you nay need to re-run lilo." ...
    (Ubuntu)
  • Re: two distros on one hd?
    ... I've had 4 booting off the same hard drive. ... The way I did it was, install the first, let it configure lilo so it's ... Then install the second, third and fourth, selecting the same /home and swap ... Then, boot into the first, mount the other 3, copy their kernels to the ...
    (comp.os.linux.misc)
  • Re: Getting rid of old, obsolete kernels
    ... > and configuring new hardware and if anything else breaks to get ... a few kernels around such as the OS's original default can ... >> If lilo is your boot manager, then it will change the config of lilo, ... kernel for one boot only, then reboot to have the new kernel boot the next ...
    (comp.os.linux.setup)