From: Bradley Tate <btate@objectmastery.com>
To: jgarzik@pobox.com
Cc: linux-ide@vger.kernel.org
Subject: sil 3114 seagate problem
Date: Thu, 08 Jul 2004 23:56:28 +1000 [thread overview]
Message-ID: <40ED528C.1090803@objectmastery.com> (raw)
<http://www.seagate.com/cda/products/discsales/marketing/detail/0,1081,586,00.html>Hi,
I'm having problems with a group of ST3120026AS drives (not currently in
the list) which unfortunately are mated with a 3114 controller on a Tyan
motherboard. Trying to resolve a problem installing Fedora Core2 or Suse
9.1 eventually led me to the kernel mailing list which has indicated
that a) there is a problem and b) the fix degrades performance.
Can you tell me if the problems with the 3114 are restricted to Seagate
drives, and everything will be rosy if I get (for example) 4 x Western
Digital 120G drives instead? I'm a little confused about the nature of
the issue/bug but I'll be happy just to get a working server at this stage.
Sorry if this is the wrong place to ask but references to this problem
are rare.
Thanks,
Bradley.
next reply other threads:[~2004-07-08 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 13:56 Bradley Tate [this message]
2004-07-08 17:53 ` sil 3114 seagate problem Jeff Garzik
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=40ED528C.1090803@objectmastery.com \
--to=btate@objectmastery.com \
--cc=jgarzik@pobox.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.