mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Ellingsworth" <david@identd.dyndns.org>
To: "Mikael Pettersson" <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Promise PDC20376
Date: Mon, 1 Dec 2008 20:43:38 -0500	[thread overview]
Message-ID: <30353c3d0812011743we0bdddk2c9c37dd0191cf2a@mail.gmail.com> (raw)
In-Reply-To: <18732.3809.720247.329641@harpo.it.uu.se>

>  > Since I put this out there, I felt it was important to follow-up on so
>  > others could benefit from my experiences. After extensive testing, the
>  > cause of the problems I've experienced are a result of a bug in the
>  > Fasttrak bios for the Promise 376 controller. Specifically speaking,
>  > bios interrupt 13h, AH=42 fails to read the requested sector from the
>  > drive despite the fact that bios interrupt 13h, AH=41, BX=0x55AA
>  > indicates the drive supports LBA extensions. The only known
>  > work-around at this time is to limit the size of the primary boot
>  > partition to 8GB or less and place it below the 8GB boundary where LBA
>  > extensions are not required to read the drive. I have contacted
>  > Promise concerning this issue and will provide more updates if
>  > anything metabolizes. Until then any users experiencing similar issues
>  > should use the work-around I've described above to boot the operating
>  > system of their choice.
>
> For booting with grub only /boot needs to be accessible by the BIOS,
> so it's common to make /boot a separate partition early on the disk
> with / and other partitions higher up.
>
> This is the first I've heard of any Promise SATA controller having
> such lame limitations.
>

A small update to this. It seems the above mentioned interrupt fails
somewhere around the 128GB boundary. Interrupt 13h, AH=42 uses a 64
bit sector address and should be capable of addressing the entire
drive. For a SATA controller, this limitation seems relatively
arbitrary. For IDE controllers, a limitation such as this is
apparently common.

Regards,

David Ellingsworth

  reply	other threads:[~2008-12-02  1:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <30353c3d0810240704n7476cc50y28b3eb8a5f326626@mail.gmail.com>
2008-11-25 14:16 ` David Ellingsworth
2008-11-25 14:42   ` Mikael Pettersson
2008-12-02  1:43     ` David Ellingsworth [this message]
2008-12-02 10:50       ` Alan Cox
2008-12-02 13:36         ` David Ellingsworth

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=30353c3d0812011743we0bdddk2c9c37dd0191cf2a@mail.gmail.com \
    --to=david@identd.dyndns.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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®