From: Frank Cusack <fcusack@fcusack.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Luis Miguel Garcia <ktech@wanadoo.es>, linux-kernel@vger.kernel.org
Subject: Re: Kernel & BIOS return differing head/sector geometries
Date: Mon, 23 Jun 2003 17:31:24 -0700 [thread overview]
Message-ID: <20030623173124.A2025@google.com> (raw)
In-Reply-To: <20030624013908.B1133@pclin040.win.tue.nl>; from aebr@win.tue.nl on Tue, Jun 24, 2003 at 01:39:08AM +0200
On Tue, Jun 24, 2003 at 01:39:08AM +0200, Andries Brouwer wrote:
> Linux does not use the BIOS, and does not use CHS either, so geometry is
> totally and completely irrelevant to Linux.
Is that also true for 2.2? I've had problems where large drives (60+G)
do these geometry tricks, and if I don't force the geometry to what I
want, fdisk (actually, sfdisk, dunno about fdisk) doesn't see the
entire drive.
Sometimes the BIOS doesn't report the specific geometry that the kernel
detects means "LBA" (I think this depends partly on drive firmware) and
then the kernel writes out some goofy geometry to the partition table
(I assume kernel geometry info is kept there?) and again I have problems
accessing the entire drive.
Also, if I later change the geometry, the previous partition table seems
to become incorrect. This one really confuses me, shouldn't the partition
table be indexed by sectors?
Anyway, it's been a very long time since I've worked directly on this
problem, so lots of my characterizations may be wrong. But I do know
that we force the geometry to specific values in our install, to combat
specific problems we've encountered.
/fc
next prev parent reply other threads:[~2003-06-24 0:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 23:09 Kernel & BIOS return differing head/sector geometries Luis Miguel Garcia
2003-06-23 23:39 ` Andries Brouwer
2003-06-24 0:31 ` Frank Cusack [this message]
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=20030623173124.A2025@google.com \
--to=fcusack@fcusack.com \
--cc=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