From: "John W. Linville" <linville@tuxdriver.com>
To: sean <seandarcy2@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: ahci or ata-piix for ich6?
Date: Sat, 30 Apr 2005 13:18:28 -0400 [thread overview]
Message-ID: <20050430171827.GA14203@tuxdriver.com> (raw)
In-Reply-To: <d502d3$sl8$1@sea.gmane.org>
On Sat, Apr 30, 2005 at 09:55:17AM -0400, sean wrote:
> I have a mobo with the 915G, 82801FB/FBW (ICH6/ICH6W) SATA
> controller. Which SATA driver in 2.6.12-rc3?
If you configured AHCI in the BIOS, then ahci should work. Otherwise
ata_piix is the choice. In fact, for ICH6 ata_piix is smart enough
to disable AHCI on its own, if it gets loaded. So, ata_piix is the
safe choice (ignoring any issues favoring AHCI).
For those observing, the reason this is an issue is because Intel
used the same PCI ID for ICH6 in either IDE or AHCI mode. So, there
is no obvious choice for kudzu and the like to make.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2005-04-30 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 13:55 ahci or ata-piix for ich6? sean
2005-04-30 17:18 ` John W. Linville [this message]
2005-05-01 1:12 ` sean
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=20050430171827.GA14203@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-ide@vger.kernel.org \
--cc=seandarcy2@gmail.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;
as well as URLs for NNTP newsgroup(s).