mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Luis Miguel Garcia <ktech@wanadoo.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel & BIOS return differing head/sector geometries
Date: Tue, 24 Jun 2003 01:39:08 +0200	[thread overview]
Message-ID: <20030624013908.B1133@pclin040.win.tue.nl> (raw)
In-Reply-To: <20030624010906.08ad32f3.ktech@wanadoo.es>; from ktech@wanadoo.es on Tue, Jun 24, 2003 at 01:09:06AM +0200

On Tue, Jun 24, 2003 at 01:09:06AM +0200, Luis Miguel Garcia wrote:

> I'm getting this while running lilo from kernel 2.5.72mm2. What does it means?
> bash-2.05b# lilo
> Warning: Kernel & BIOS return differing head/sector geometries for device 0x80
>     Kernel: 13424 cylinders, 15 heads, 63 sectors
>       BIOS: 788 cylinders, 255 heads, 63 sectors

It means that Kernel and BIOS each invent a fake geometry for your disk,
and they did not invent the same fake geometry.

> Could it be dangerous?

No.

Linux does not use the BIOS, and does not use CHS either, so geometry is
totally and completely irrelevant to Linux.

Depending on the precise LILO version, and on whether you give options
like "linear" and "lba32", LILO might or might not be confused.
Test whether you can boot. If booting works all is well. If not
make sure you set at least one of "linear" and "lba32".

If you also have DOS on the same disk the story is more complicated.
All systems on a disk must agree as to where the partitions are,
or corruption will be the result.


  reply	other threads:[~2003-06-23 23:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 23:09 Luis Miguel Garcia
2003-06-23 23:39 ` Andries Brouwer [this message]
2003-06-24  0:31   ` Frank Cusack
2003-06-24  8:14     ` Andries Brouwer
2003-06-24  3:45   ` H. Peter Anvin
2003-06-24  4:22     ` Werner Almesberger
2003-06-24  4:27       ` H. Peter Anvin
2003-06-24 11:13         ` Werner Almesberger
2003-06-24 15:29           ` H. Peter Anvin
2003-06-24 15:42             ` John Coffman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030624013908.B1133@pclin040.win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=ktech@wanadoo.es \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®