public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Jeff Garzik <jgarzik@redhat.com>
Subject: Re: libata testing on new machine with ICH5 and PDC20318
Date: Sat, 08 Nov 2003 12:49:42 -0500	[thread overview]
Message-ID: <3FAD2CB6.5070508@pobox.com> (raw)
In-Reply-To: <3FACC17C.7070901@backtobasicsmgmt.com>

Kevin P. Fleming wrote:
> I'm building a new server to go into a colo facility in about six weeks; 
> the machine will have an Intel motherboard with an ICH5R (although I 
> won't use the RAID features) and a Promise SATA150 TX4 (no RAID 
> support). All six SATA ports will have Seagate 160GB Barracuda drives 
> attached, and I plan on using software RAID-5 and LVM2 on top of the array.
> 
> I will be building the system using 2.6.0-test9, so will be using libata 
> to drive the disks. If there's anything I can help with 
> debugging/testing the ICH and/or Promise SATA drivers let me know... I 
> see that recently Jeff posted a small patch for some SATA reset issues 
> against -test9, so I'll certainly start out with that included.


The ICH5 should be fine.  You may need to twiddle BIOS setup options, 
some users have reported that both drivers/ide and libata fail in 
certain BIOS modes.  "Enhanced - SATA only" is usually the preferred 
mode, where feasible.

You need to make sure you get the Promise SATA fixes I just pushed to 
Linus.  Presumably they will be available in the next 2.6.0-testX BK 
snapshot on ftp.kernel.org, tonight or the next night.

	Jeff




  reply	other threads:[~2003-11-08 17:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08 10:12 libata testing on new machine with ICH5 and PDC20318 Kevin P. Fleming
2003-11-08 17:49 ` Jeff Garzik [this message]
2003-11-08 18:12   ` Kevin P. Fleming

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=3FAD2CB6.5070508@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=jgarzik@redhat.com \
    --cc=kpfleming@backtobasicsmgmt.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