All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shane Hathaway <shane@hathawaymix.org>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Bug: Resume with Host Protected Area
Date: Tue, 19 Apr 2005 21:43:20 -0600	[thread overview]
Message-ID: <4265CFD8.4010408@hathawaymix.org> (raw)
In-Reply-To: <87f94c370504191420d2f5c32@mail.gmail.com>

Greg Freemyer wrote:
> IMHO, if you are going to put live data in the HPA, you really should
> just kill the HPA permanently not depend on Linux to do a volitile
> reset on every reboot/resume.
>
> See setmax at http://www.win.tue.nl/~aeb/linux/setmax.c 

Thanks for the pointer.

Still, I'm thinking of all the others who may have fallen into the same
trap.  I got into this situation purely by accident--I was never made
aware of HPA at installation time; Linux must have disabled it
automatically.  Then it took me a year to guess that the problems with
sleeping might be related to some peculiar messages I saw in the kernel
logs.

The HPA support needs to be all or nothing: either Linux disables HPA
automatically at boot *and* at resume, or it doesn't touch HPA at all.
Also, HPA shouldn't be disabled without user consent.  IBM put the
Windows installer in my laptop's HPA rather than provide installation
CDs.  There were no partition table entries indicating there was
anything stored at the end of the drive, so when I installed Linux, I
wiped out the Windows installer without knowing it.  IBM still hasn't
sent the replacement CDs.

Shane

      reply	other threads:[~2005-04-20  3:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 20:03 Bug: Resume with Host Protected Area Shane Hathaway
2005-04-19 21:20 ` Greg Freemyer
2005-04-20  3:43   ` Shane Hathaway [this message]

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=4265CFD8.4010408@hathawaymix.org \
    --to=shane@hathawaymix.org \
    --cc=greg.freemyer@gmail.com \
    --cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.