From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: pjones@redhat.com
Cc: "ATARAID (eg, Promise Fasttrak,
Highpoint 370) related discussions" <ataraid-list@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: IDE HPA
Date: Fri, 02 Sep 2005 21:22:58 +0100 [thread overview]
Message-ID: <1125692578.30867.33.camel@localhost.localdomain> (raw)
In-Reply-To: <1125688483.31292.20.camel@localhost.localdomain>
On Gwe, 2005-09-02 at 15:14 -0400, Peter Jones wrote:
> Ugh. So some BIOSes use it for legitimate reasons (like thinkpads), and
> some use it to work around BIOS bugs. Great.
All are legitimate uses. The partition table tells you which.
> Mine didn't, but it does have an HPA. Thankfully we weren't disabling
> it yet when I installed my laptop -- I know others who weren't so lucky.
> So this partitioning scheme hasn't always been the case...
You installed it on Red Hat 7 ? I think 7, may have been 6.x or earlier.
This behaviour goes back pretty much to the creation of the ATA spec for
HPA. In fact if it was that long ago IBM shipped it with Windows so it
did have a partition table!
> It really sounds better (to my naive mind, at least) to whitelist the
> known-broken BIOSes.
Not really practical. You'd have to list most older PC systems.
> Well, installers probably should be aware, yes -- that's why I mentioned
> userland interfaces to enabling/disabling. But to me it still seems
> like we want to disable the HPA during installation and bootup, but only
> if your BIOS is doing things wrong.
"Wrong" is a poor term here.
If the system has a partition table that doesn't cover the post HPA area
and its about the right size we can be fairly sure the right choice is
to honour the HPA, if its a randomly different size its a fair bet the
disk got moved
If the partition table exceeds the no HPA area of disk but not the full
disk then its almost certainly right the HPA should be disabled post
boot. If it exceeds both its a raid 0 volume of some form...
next prev parent reply other threads:[~2005-09-02 20:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87941b4c05082913101e15ddda@mail.gmail.com>
[not found] ` <200508300859.19701.tennert@science-computing.de>
2005-08-30 15:52 ` Greg Felix
2005-08-30 16:16 ` Bartlomiej Zolnierkiewicz
2005-08-30 17:05 ` Alan Cox
2005-08-31 0:30 ` Bartlomiej Zolnierkiewicz
2005-08-30 16:38 ` Alan Cox
[not found] ` <87941b4c050830095111bf484e@mail.gmail.com>
2005-09-02 7:27 ` Molle Bestefich
2005-09-02 13:05 ` Alan Cox
2005-09-02 13:33 ` Molle Bestefich
2005-09-02 14:35 ` Matthew Garrett
2005-09-02 16:24 ` Molle Bestefich
2005-09-02 17:05 ` Alan Cox
2005-09-02 17:44 ` Molle Bestefich
2005-09-02 18:04 ` Matthew Garrett
2005-09-02 18:09 ` Peter Jones
2005-09-02 18:59 ` Alan Cox
2005-09-02 19:14 ` Peter Jones
2005-09-02 20:22 ` Alan Cox [this message]
2005-09-02 21:14 ` Peter Jones
2005-09-03 0:05 ` Alan Cox
2005-09-03 23:31 ` Jeff Garzik
2005-09-07 14:52 ` Bill Davidsen
2005-09-03 0:03 ` Pekka Pietikainen
2005-09-02 18:57 ` Alan Cox
2005-09-02 17:57 ` Vojtech Pavlik
2005-09-02 14:50 ` Alan Cox
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=1125692578.30867.33.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ataraid-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
/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
Powered by JetHome