[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: WD 93c33 trouble - resolved.
-----BEGIN PGP SIGNED MESSAGE-----
On Feb 18, 2009, at 1:47 PM, jscottkasten%yahoo.com@localhost wrote:
--- On Wed, 2/18/09, Michael <macallan%netbsd.org@localhost> wrote:
I was more thinking about a external ID switch box -
like the ones
on the back of drive cases connected upside-down.
combinations. But Michael explicitely said
It's jumpered to ID1, ARCS reports it there. If I
change it to ID2 and leave it alone ARCS reports it as ID2
as does NetBSD. It's some other craziness.
This makes me wonder if it's really some firmware issue in the drive
More weirdness. With the external ZIP actually powered up the NetBSD
kernel finds it as sd1 without any trouble. If I power up the 2nd
harddisk we hang again after attaching sd0.
Now ZIPs aren't exactly known for being good SCSI citizens.
Also, apparently my earlier theory about Target Initiated Sync
Negotiations seems to be right - I found a jumper sitting in a
'reserved' position, removed it and all of sudden the kernel detects
So, for future reference, on IBM DORS-32160 drives the jumper between
'Unit Attention Disable' and 'Auto Start Delay' which is labeled as
'Reserved', being the JP8 counted from the right ( don't ask me why
they did that ) in the datasheet enables Target Initiated Sync
Negotiation or something else that hopelessly confuses the wd33c93
driver. No idea why it was set in the first place.
The drive in question is an SGI-badged IBM ( and ironically, the other
one is a Compaq-badged Seagate )
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
-----END PGP SIGNATURE-----
Main Index |
Thread Index |