From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: andyliebman@aol.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Changes in SATA, IDE and ATAPI configuration
Date: Sat, 07 Jan 2006 19:14:49 +0000 [thread overview]
Message-ID: <1136661289.3748.70.camel@localhost.localdomain> (raw)
In-Reply-To: <8C7E1BF63B9F5F4-AC8-506C@FWM-M45.sysops.aol.com>
On Sad, 2006-01-07 at 11:34 -0500, andyliebman@aol.com wrote:
> -- BIOS settings for the ICH5 SATA controller on my Xeon motherboard
> (Auto, SATA, PATA?)
> -- Whether the CD is connected to the Primary or Secondary IDE channel
Secondary slave is broken in 2.6.15 and all earlier SATA releases I've
seen for ICH5. ATAPI prefetch handling is incorrect on PIIX/ICH5. If the
CD is anywhere but the secondary slave it should be fine.
> -- Use (or NOT) of "options libata atapi_enabled=1" in modprobe.conf
If its modular. Otherwise it needs to be a boot time option for libata
> -- Order of loading modules
Shouldn't be
> -- Use (or NOT) of the AHCI module. When making fresh installs onto
> SATA drives, some distributions seem to load the AHCI module and some
> don't, on exactly the same hardware with the same kernel.
AHCI mode is an option for the ICH5-R and later controllers and BIOS
side.
Basically ICH5 supports
'Pretend we are one device' (Combined mode) which will see the PATA
ATAPI ports appear as non DMA IDE ports (old style) and in its full
functional mode where PATA and SATA ports are properly seperated out.
> Whatever it is, I haven't found the magic formula for making the
> transfer from IDE to SATA work.
Insert CD, install, sync over data. Actually for Fedora and anything
using initrd root device labels you should only need to make the right
initrd and set the options.
Alan
prev parent reply other threads:[~2006-01-07 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 16:34 andyliebman
2006-01-07 19:14 ` Alan Cox [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=1136661289.3748.70.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andyliebman@aol.com \
--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
all inboxes | Powered by JetHome®