From: "Jim B" <jim@jbsys.com>
To: jgarzik@pobox.com
Cc: linux-ide@vger.kernel.org
Subject: SATA Promise driver
Date: Wed, 2 Jun 2004 11:25:31 -0700 [thread overview]
Message-ID: <007101c448ce$fd2cc8d0$0a01a8c0@jbsys.com> (raw)
Jeff
I have a K8V SE Deluxe MoBo with a Promise FastTrack 378 controller. It can be
used as a RAID or extended IDE controller by sellecting the proper BIOS setting.
I have tried the RAID setting and used ft3xx.o driver (from Promise) in FC1 2.4
kernels to use the two 160 GB IDE disks. I currently have it set to extended
IDE. I use the pdc-ultra.o driver (from Promise) in FC1 2.4 kernels for this
mode. I installed FC2 x86_64 version to another partition on the standard IDE
disk. It boots and works, except it will not see the PATA drives on the Promise
controller. It says there are no drives present. Does the SATA_Promise module
support this controller in either of these modes? Am I doing something wrong?
Is it because I am using IDE drives instead of SATA drivers?
Jim
next reply other threads:[~2004-06-02 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 18:25 Jim B [this message]
2004-06-02 18:40 ` SATA Promise driver 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='007101c448ce$fd2cc8d0$0a01a8c0@jbsys.com' \
--to=jim@jbsys.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 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).