mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kozkir-8 <kozkir-8@student.luth.se>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re[4]: VIA686A chipset crash under 2.4.2-ac20
Date: Fri, 16 Mar 2001 01:33:50 +0100	[thread overview]
Message-ID: <671081119.20010316013350@student.luth.se> (raw)
In-Reply-To: <Pine.LNX.4.10.10103151157400.28602-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10103151157400.28602-100000@coffee.psychology.mcmaster.ca>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5



>> >> kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>>
>> MH> this can only be caused by bad cable/config.  is it 18", with both ends
>> MH> plugged in?
>>
>>
>> Do you mean 40-pin E-IDE cable?

MH> 40-conductor cables are only valid to use up to udma33, but 80c cables
MH> will *always* help, and can be used in any mode.  but equally important
MH> is that the cable must never be longer than 18", with both ends plugged in
MH> (no stub).

I measured the cable and it is aprox. 45cm (18") and it is 80c.
It has also 3 connectors, two of them are in use (on the ends), and
one is free (in the middle). I also checked the connections on
motherboard and on disk, they are both ok.

-----BEGIN PGP SIGNATURE-----
Version: 2.6

iQCVAwUAOrFfcT5SQymVx3NvAQEmwQP/bMQYXekwlUDKPdQ80khqfkv45TCY8lVd
r6lXb82s60vvbEpCTyF16E4TwQkwirsPf5virJ0jZO+EBFRVwOhDFitbaF9PdHhG
MdSFtST6JrhwozsoU3LgkdMZb3Mnnw7YsV9ctOZij+4WN5SDd5IO5YNXgeWgrdLb
c+jZzBpmLK8=
=PvVG
-----END PGP SIGNATURE-----



       reply	other threads:[~2001-03-16  0:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10103151157400.28602-100000@coffee.psychology.mcmaster.ca>
2001-03-16  0:33 ` kozkir-8 [this message]
2001-03-16  0:38 ` kozkir-8

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=671081119.20010316013350@student.luth.se \
    --to=kozkir-8@student.luth.se \
    --cc=hahn@coffee.psychology.mcmaster.ca \
    --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®