From: Jasmeet Sidhu <jsidhu@arraycomm.com>
To: linux-kernel@vger.kernel.org (Linux Kernel)
Subject: Re: ide / usb problem
Date: Mon, 26 Feb 2001 11:53:07 -0800 [thread overview]
Message-ID: <5.0.2.1.2.20010226115140.0265f4f8@pop.arraycomm.com> (raw)
In-Reply-To: <E14X1f7-00033Q-00@the-village.bc.nu>
In-Reply-To: <20010225060326.K127@pervalidus>
At 01:56 PM 2/25/2001 +0000, Alan Cox wrote:
> > hda: dma_intr: status=3D0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=3D0x84 { DriveStatusError BadCRC }
> > ide0: reset: success
> >
> > Again, if it's really a cable problem, then ASUS is selling
> > cables that don't work with UDMA66 (but they sell it as
> > UDMA66).
>
>To get ATA66 working well you need the right cables, you also need a machine
>that is to spec on interference and the like. You cant just point at the
>cables
>althoigh they are first guess.
>
I have a similar setup and had the same problems. Dump your cables and get
ATA/100 Certified cables and you should not have this problem. Also keep
the cable length in mind. Anybody out there know if there's a max cable
length for the ATA/100 spec??
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
- - -
Jasmeet Sidhu
Unix Systems Administrator
ArrayComm, Inc.
jsidhu@arraycomm.com
www.arraycomm.com
next prev parent reply other threads:[~2001-02-26 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 9:03 ide / usb problem Frédéric L. W. Meunier
2001-02-25 10:31 ` Bernd Eckenfels
2001-02-25 13:56 ` Alan Cox
2001-02-25 19:22 ` jerry
2001-02-26 19:53 ` Jasmeet Sidhu [this message]
2001-02-26 20:23 ` Mark Hahn
2001-02-27 8:02 ` Vojtech Pavlik
2001-02-27 13:10 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2001-02-26 19:18 David Balazic
2001-02-26 20:06 ` jerry
2001-02-24 12:30 jerry
2001-02-24 16:55 ` Alan Cox
2001-02-25 21:06 ` Tim Moore
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=5.0.2.1.2.20010226115140.0265f4f8@pop.arraycomm.com \
--to=jsidhu@arraycomm.com \
--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 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.