From: Nicholas Wourms <nwourms@netscape.net>
To: linux-kernel@vger.kernel.org
Subject: Incorrect 80 wire detection with amd 760mpx & 2.4.21-pre4-ac7
Date: Sat, 01 Mar 2003 19:54:29 -0500 [thread overview]
Message-ID: <3E615645.4010206@netscape.net> (raw)
FYI:
I suspect that:
http://marc.theaimsgroup.com/?l=linux-kernel&m=104619727013220&w=2
is related to my problem.
Anyhow, I'm using a UDMA5 WesternDigital drive on a ASUS
K7M266-D motherboard. With a plain, stock 2.4.20 kernel,
the viper driver properly recognizes which channel has the
80 wire cable (in my case ide0). The hard disk is the
primary master, a cd-r drive is the primary slave, and a zip
drive is the secondary slave. I can successfully set UDMA5
with hdparm without any problems. However, after upgrading
to 2.4.21-pre4-ac7, I noticed that the drive was stuck at
UDMA2. Checking /proc/ide/amd74XX yeilds some unexpected
results:
----------AMD BusMastering IDE Configuration----------------
Driver Version: 2.9
South Bridge: Advanced Micro Devices
[AMD] AMD-768 [Opus] IDE
Revision: IDE 0x4
Highest DMA rate: UDMA100
BM-DMA base: 0xd800
PCI clock: 33.3MHz
-----------------------Primary IDE-------Secondary IDE------
Prefetch Buffer: yes yes
Post Write Buffer: yes yes
Enabled: yes yes
Simplex only: no no
Cable Type: 40w 80w
-------------------drive0----drive1----drive2----drive3-----
Transfer Mode: UDMA UDMA UDMA PIO
Address Setup: 30ns 30ns 30ns 120ns
Cmd Active: 90ns 90ns 90ns 90ns
Cmd Recovery: 90ns 90ns 30ns 30ns
Data Active: 90ns 90ns 90ns 330ns
Data Recovery: 30ns 90ns 30ns 270ns
Cycle Time: 60ns 60ns 60ns 600ns
Transfer Rate: 33.3MB/s 33.3MB/s 33.3MB/s 3.3MB/s
It appears that the driver has got it backwards, identifying
my 80 wire cable as a 40 wire cable and visa-versa. As I
mentioned, this is completely opposite to the behavior of
2.4.20. I've poked around the source, but I can't come up
with anything new to what the other person discovered.
Trying to pass ide0=ata66 doesn't seem to have any effect on
the situation. I can provide further information upon
request, but I don't think it will be necessary at this point.
Cheers,
Nicholas
next reply other threads:[~2003-03-02 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 0:54 Nicholas Wourms [this message]
2003-03-02 2:16 ` Incorrect 80 wire detection with amd 760mpx & 2.4.21-pre4-ac7 Alan Cox
2003-03-03 15:44 ` Vojtech Pavlik
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=3E615645.4010206@netscape.net \
--to=nwourms@netscape.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