From: "Derek J Witt" <djw@flinthills.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Suspend support for IDE
Date: Sun, 10 Mar 2002 18:44:58 -0600 [thread overview]
Message-ID: <009501c1c895$f9008e10$d3c02740@flinthills.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0203101801150.30628-100000@coffee.psychology.mcmaster.ca>
yeah, these are 18" cables. I previously had my caviar setup as a secondary
master and not cable-select as far I could remember. I was using the end
connector due to space constraints in the case and the cable-length
restraints. I did attempt to have both hard drives on separate controllers.
I was trying to setup my swaps in a raid-like fashion. Once I moved my
drives around in the case, I moved the caviar back to primary slave using
the end connector. It was using the end connector on secondary master due
not being able to stretch the middle connector to the caviar.
I was having the cable twist some strange ways just to get the cable to fit
properly. This hard drive came out of an old gateway. It was setup as a
slave in that box too.
I suppose risking screwing up the IDE cable just to get it to reach or fit
properly in a mid-tower isn't worth losing data via CRC errors...
I now have this IDE setup:
Primary master: Quantum Fireball SE6.4A
Primary slave: Western Digital WDC AC36400L
Secondary master: Acer ATAPI CD-ROM 40x N0AP
Secondary slave: Acer ATAPI CD-RW 2x6x CRW6206A.
I got the CD-ROM in the middle 5 1/4" bay, the CD-RW in the bottom 5 1/4"
bay, the 3 1/2" floppy in the top 3 1/2" bay, the Caviar in the middle 3
1/2" bay, and the Quantum in the 3rd 3 1/2" bay below the floppy. I was
using an IDE cable from the old AT case I had. I think it was a faulty
cable in my situation. I have since replaced the cable and the cd drives are
working just fine even with dma enabled. I'm using an ATA66 cable for the
hard drives.
-- Derek Witt.
----- Original Message -----
From: "Mark Hahn" <hahn@physics.mcmaster.ca>
To: "Derek J Witt" <djw@flinthills.com>
Sent: Sunday, March 10, 2002 5:02 PM
Subject: Re: Suspend support for IDE
> > Does the IDE blacklist include those drives that malfunction if they're
not
> > using the correct connector on the IDE ribbon cable?
>
> no. there is no specificity for connector unless you're using
cable-select.
>
> > I found out a few weeks ago that my Caviar WD36400 is that particular.
> > Upon putting that drive back on the middle connector on secondary, my
box
> > was then able to suspend and resume without the drive disconnecting on
me.
>
> are your cables <=18", with both *ends* plugged in? the spec requires
that.
>
>
next parent reply other threads:[~2002-03-11 0:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0203101801150.30628-100000@coffee.psychology.mcmaster.ca>
2002-03-11 0:44 ` Derek J Witt [this message]
2002-03-11 1:01 ` Suspend support for IDE Mark Hahn
2002-03-08 18:02 Pavel Machek
2002-03-08 18:37 ` Alan Cox
2002-03-08 18:33 ` benh
2002-03-09 21:03 ` Pavel Machek
2002-03-09 22:05 ` Alan Cox
2002-03-10 0:52 ` Barry K. Nathan
2002-03-11 0:10 ` Reid Hekman
2002-03-11 5:47 ` Andre Hedrick
2002-03-10 8:23 ` Rogier Wolff
2002-03-10 22:16 ` Derek J Witt
2002-03-10 22:37 ` Alan Cox
2002-03-11 12:15 ` Pavel Machek
2002-03-09 22:08 ` Martin Dalecki
2002-03-09 13:02 ` Martin Dalecki
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='009501c1c895$f9008e10$d3c02740@flinthills.com' \
--to=djw@flinthills.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox