Subject: Re: CMD qbus scsi issues
To: None <port-vax@netbsd.org>
From: Tom Ponsford <tponsford@theriver.com>
List: port-vax
Date: 01/31/2003 14:15:21
I picked up a MV 3600 a few months ago at the UA auction that had a CMD
CQD 220/223 mscp scsi adapter. After ;putting 1.6 on it. I compiled
several programs for over
36 hours without a hiccup. I did have problems with a NFS mount when
ximit died.
An interesting item is in the CMD Users manual which I noted:
"The CQD-223 consists of the CQD-220 and a microvax III adapter kit.
A shielded SCSI cable (with shielded connectors) is required to
connect the
CQD-223 to scsi devices."
As I recall I once had another CMD scsi->mscp controller and disk that
acted
flacky until I replaced the SCSI cable with a newer one and the problem
went away.
Tom
Lord Isildur wrote:
> ok, so we have had this thread before, but not for a while...
> has anybody in the meantime ever figured out why the CMD qbus scsi-mscp
> adaptors stopped working somewhere around 1.4? also, does anyone
> know if it worked right in 1.3.3? it does in 1.3.2 (which i remember from
> a long time ago was when bob tested a whole bunch of different versions
> on a uvax-II, as well as from still running two 1.3.2 machines), but
> 1.3.2 has other stability issues.
>
> for a brief refresher, while the cmd cards will configure just fine, and
> one can do a bit of io to disks through them, theyre extremely prone to
> causing panics. From what ive guessed trying to figure out the problem,
> they dont die immediately but leave something messed up which causes
> a problem shortly afterward..
>
> Isildur
>