I've got a TD Systems Viking "VIK/QDA"
QBUS SCSI controller, which I'm
trying to use. Does anyone have documentation for this thing? It's
properly configured to be at the primary (disk) MSCP controller address,
and looks OK from the QBUS side, but I can't talk to any SCSI disks that
I connect to it.
This is what "show qbus" gives me on my VAX 4000/300:
>>show qbus
Scan of Qbus I/O Space
-20001468 (772150) = B440 RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK
-2000146A (772152) = 0B40
-20001600 (773000) = 0A0F
-20001602 (773002) = 01FF
-20001920 (774440) = FF08 DELQA/DEQNA/DESQA
-20001922 (774442) = FF00
-20001924 (774444) = FF2B
-20001926 (774446) = FF32
-20001928 (774450) = FFA6
-2000192A (774452) = FF9E
-2000192C (774454) = 8400
-2000192E (774456) = 1030
-20001F40 (777500) = 0020 IPCR
And, this is what "show uqssp" gives me:
>>show uqssp
UQSSP Disk Controller 0
(772150)
-DUA0 (@0)
-DUA1 (@0)
-DUA2 (@0)
-DUA3 (@0)
-DUA4 (@0)
-DUA5 (@0)
-DUA6 (@0)
So, it's there, and responding to the CPU (and yes, it's the only MSCP
device in the system, so it's not conflicting with anything else).
I've tried setting the SCSI drive to several different SCSI IDs, and I've
used drives from 540MB to 6GB in size, with no luck. When I try a "show
uqssp" or a "boot dua0", the controller blinks its red LED, but the
activity light on the drive doesn't light up at all (the SCSI ID on the
drive was set to "0" when I tried booting from it).
Any ideas?
Pat
--
Purdue University ITAP/RCAC ---
http://www.rcac.purdue.edu/
The Computer Refuge ---
http://computer-refuge.org
Well, I know its not you. I tried using a Viking controller in a BA215
backplane with a 11/53 and it didn't work, although other controllers would
work ( UC07, DQ696 ). I thought it might be the termination on the qbus in
the 215, but never found out.
Doug Taylor