From: David Knierim <david_knierim@earthlink.net>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.6.7 Vitesse 7174 issues
Date: Wed, 23 Jun 2004 11:12:50 -0400 (GMT-04:00) [thread overview]
Message-ID: <8782538.1088003570736.JavaMail.root@dewey.psp.pas.earthlink.net> (raw)
We have been trying to use the use the libata Vitesse 7174 driver in the 2.6.7 kernel. We have seen two different issues.
The first issue:
In all cases, the attached SATA drives are not recognized the first time the driver is loaded. After removing the driver using rmmod, loading the driver for the second time will consistently recognize all SATA hard drives attached.
The second issue:
A Silicon Image 3611 SATA-to-IDE bridge card (vendor evaluation design) does not work when attached to the Vitesse 71714.
When an IDE drive is attached to this card, the following errors are printed the second time the kernel driver is loaded (X was 9 or 17):
ataX slow to respond, please be patient
ataX failed to respond
When an ATAPI cdrom is attached on this card, modprobe gave no response 5 times (out of 5 tries). The system simply returned another command line.
The Silicon Image 3611 bridge has been tested using Windows XP. It was attached to a Silicon Image controller for that test.
Our hardware:
- custom server based on Intel E7501 server chipsed and single Xeon 2.4Ghz processor
- onboard Vitesse 7174 controller
- pci reference card from Vitesse with 7174 controller.
The software:
- Fedora core 2 updated with 2.6.7 kernel.
Any clues as to how to get resolution on these issues would be most appreciated. We have dedicated equipment and manpower to test anything that may help get the Vitesse 7174 driver stable.
Please CC: me on any responses, since I am not subscribed to this mailing list.
Many thanks,
David Knierim
reply other threads:[~2004-06-23 15:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8782538.1088003570736.JavaMail.root@dewey.psp.pas.earthlink.net \
--to=david_knierim@earthlink.net \
--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®