public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Neil Conway <nconway.list@ukaea.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: IDE corruption, 2.2, VIA chipset in PIO mode
Date: Tue, 05 Jun 2001 09:29:31 +0100	[thread overview]
Message-ID: <3B1C986B.BA6522CC@ukaea.org.uk> (raw)
In-Reply-To: <E156y8B-0005eg-00@the-village.bc.nu>

Alan Cox wrote:
> > Sigh.  Ah, I think I see a nice brown bag, in a nice deep hole.
> 
> Its only a pointer. PIO speed cable errors tend to  imply a bad cable problem
> (eg not properly connected ribbon). So it could still be that the problem is
> elsewhere

Ah OK.  Though a cable fault does seem consistent with the evidence...
(I swear I read the FAQ before posting!)

In practice, does a BadCRC error EVER imply a crap/buggy chipset?

On the flip side, the cable isn't too long, isn't damaged, and was very
definitely seated properly (I did it personally and took some care over
that).  On the third hand, I don't know where it came from, and somebody
had spilled coffee on it in a previous life :-) (not the connectors!).

To approach the question from a different angle completely: DARE I use
the VIA 686A in UDMA-33/66[/100 if capable?] mode, or is it not really
up to the job?  I've seen so many posts on a search for "linux via ide
corruption" that I'm uneasy about repeating the experiments on what is a
production box...

thanks,
Neil
PS: 80pin cables on the way :-)

       reply	other threads:[~2001-06-05  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E156y8B-0005eg-00@the-village.bc.nu>
2001-06-05  8:29 ` Neil Conway [this message]
2001-06-04 14:43 IDE corruption, 2.2, VIA chipset in PIO mode Neil Conway
2001-06-04 17:02 ` Alan Cox
2001-06-04 17:29   ` Neil Conway

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=3B1C986B.BA6522CC@ukaea.org.uk \
    --to=nconway.list@ukaea.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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