On 6 Dec 1999 09:09:28 GMT,
> >You can usually get around this by using the 'linear' option in
> >/etc/lilo.conf. This will use an alternative interface to the BIOS and
> >instead of asking for a given cylinder/head/sector, will ask for a
> >certain block number and let the BIOS figure out where that is. This is
> >effectively sneaking around any sort of remapping the BIOS does
> I guess that is wishful thinking. What happen with the linear option is
> that lilo makes a bios call to get the disk geometry, and with that
> information it convert all linear addresses to CHS format before calling
> the bios disk read function.
No, it doesn't. It asks the drive itself what the geometry is, and this can
differ from what the BIOS presents. Hence the problem.
You are deceived if you believe that the BIOS has anything to do with the
operation of Linux once it has booted.
Quote:> That means cyl1024 is still very much an issue.
Which of course has nothing to do with what I said, or what the users
LILO will notify you upon installation if the Cyl is >1024 and will refuse
to install it. In this case, though, the user said that LILO ran just fine,
installing itself into the boot record, and as per the subject of this
thread, upon booting it said "LI"
This situation is quite well documented in the LILO documentation:
| LI The first stage boot loader was able to load the second stage boot
| loader, but has failed to execute it. This can either be caused by a
| geometry mismatch or by moving /boot/boot.b without running the map
Again, the 'linear' option is to address this issue and it is your own
wishful thinking and misreading the articles that makes you believe that
this has anything to do with 1024 cylinders.
Specifically, again from the LILO documentation, note the description
of the 'linear' option and why you would use it:
| LINEAR Generate linear sector addresses instead of sector/head/cylinder
| addresses. Linear addresses are translated at run time and do not
| depend on disk geometry. Note that boot disks may not be portable if
| LINEAR is used, because the BIOS service to determine the disk geometry
| does not work reliably for floppy disks. When using LINEAR with large
| disks, /sbin/lilo may generate references to inaccessible disk areas
| (see section "BIOS restrictions"), because 3D sector addresses are not
| known before boot time. LINEAR may conflict with COMPACT, see section
| "Other problems".
'LI' as the boot message is typically a geometry mismatch, and 'linear' use
a method that doesn't depend on geometry.... hrrm, one would think that
could be related, no?
Please read the articles before you post your misdiagnosis.
Brian Moore | Of course vi is God's editor.
Sysadmin, C/Perl Hacker | If He used Emacs, He'd still be waiting
Usenet Vandal | for it to load on the seventh day.
Netscum, Bane of Elves.