From: Phil Howard <phil-linux-kernel@ipal.net>
To: linux-kernel@vger.kernel.org
Subject: Re: IDE: 2.2.19+IDE patches works fine; 2.4.x fails miserably; please help me figure out why!
Date: Sun, 25 Nov 2001 07:23:26 -0600 [thread overview]
Message-ID: <20011125072326.A26870@vega.ipal.net> (raw)
In-Reply-To: <200111250457.fAP4vIt03205@jik.kamens.brookline.ma.us>
In-Reply-To: <200111250457.fAP4vIt03205@jik.kamens.brookline.ma.us>
On Sat, Nov 24, 2001 at 11:57:18PM -0500, Jonathan Kamens wrote:
| I've seen people mention in comp.os.linux.development.system that the
| BadCRC error may indicate a cable problem. However, (a) I'm pretty
| certain that I'm using Ultra66 cables for both hde and hdg, and (b) if
| that's the problem, why don't I get the same errors with 2.2.19?
|
| As for (a), I believe I've got the right cables because I checked when
| I installed them and because the controller (Promise Ultra66)
| recognizes both hde and hdg as Ultra-capable drives when it starts up
| (which it wouldn't do if I didn't have the correct cables -- I know
| this because it wasn't doing it when I didn't have the correct cables
| ;-).
I've had drive problems simply as a result of bad _instances_ of cables,
even though it was the right kind of cable. I've also had drive problems
as a result of looseness of connections. Some connector _instances_
seem to be more prone to this, and some headers on some motherboards
also seem to be more prone to this.
<paranoid>
Pull the cable and clean all the connections on the cable, board, and
drive. High pressure air is good enough in most cases, but liquid
cleaner might be needed in some. Check the cable for dings, nicks,
and sharp bends. These have more impact on ATA66 cables. If it has
any, get a new cable and cut the old one in half. If you have a
single ATA66 drive, be sure it is on the _end_ connector. While you
can cut off the end of older IDE cables to make short ones, not so
with ATA66 cables. Leave the middle connector dangling or get a cable
with just 2 connectors. Also, don't "round" an ATA66 cable.
</paranoid>
And finally, I actually have a couple drives that exhibit these problems
no matter what I do. The drives _can_ simply be bad.
--
-----------------------------------------------------------------
| Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ |
| phil-nospam@ipal.net | Texas, USA | http://phil.ipal.org/ |
-----------------------------------------------------------------
next prev parent reply other threads:[~2001-11-25 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 4:57 Jonathan Kamens
2001-11-25 13:23 ` Phil Howard [this message]
2001-11-27 0:35 ` IDE: 2.2.19+IDE patches works fine; 2.4.x fails miserably;please " nakai
2001-11-27 8:12 ` Jonathan Kamens
[not found] <fa.fdgrtcv.qh4d14@ifi.uio.no>
2001-11-25 20:55 ` IDE: 2.2.19+IDE patches works fine; 2.4.x fails miserably; please " Jonathan Kamens
[not found] <Pine.LNX.4.10.10111251617280.7477-100000@coffee.psychology.mcmaster.ca>
2001-11-25 21:32 ` Jonathan Kamens
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=20011125072326.A26870@vega.ipal.net \
--to=phil-linux-kernel@ipal.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®