Subject: Re: VAX 4000 QBUS question
To: None <port-vax@netbsd.org>
From: George Harvey <fr30@dial.pipex.com>
List: port-vax
Date: 12/17/2004 01:05:11
On Thu, 16 Dec 2004 22:59:28 +0100 (CET)
Johnny Billquist <bqt@Update.UU.SE> wrote:

> On Thu, 16 Dec 2004, George Harvey wrote:
> 
> > On Thu, 16 Dec 2004 09:02:44 -0500 (EST)
> > Kirk Russell <kirk@ba23.org> wrote:
> >
> >> On Thu, 16 Dec 2004, George Harvey wrote:
> >>
> >>> With the CMD card installed, I get exactly the same output. If I
> >>> then remove the TK70 controller, I still get the same output! From
> >>> this I guess that my CMD card is configured with the same address
> >as>> the TK70 controller. I've had a hunt on the 'net but haven't
> >found>> any info on jumper settings for the CQD-223 so I'm looking
> >for help>> to re-jumper it to a non-overlapping address.
> >>
> >> http://www.bitsavers.org/pdf/cmd/CQD-220_CQD-223_Nov90.pdf
> >>
> >> I used address 772150.
> >
> > Yes! That had exactly the information I was looking for. I've
> > changed the CSR address and it now shows up as a disk controller.
> > Jumper W6 sets the CSR and I changed mine as follows:
> >
> >                           1   2   3   4   5   6   7
> > Was: 17774500 / 20001940  in out out out  in  in  in
> > Now: 17772150 / 20001468  in in  in  in  out out out
> 
> I think you have set the TAPE CSR to 17772150. That will be bad juju.
> It will "look" right when the "show device" command is done, because
> of the way that command works, but it will not make you happy when you
> try to find any disks.

It was a disk/tape confusion but I've RTFM, found the magic incantation
and it's now working :-)

The 223/TM can be either a tape controller, disk controller or both.
When I got it, it was configured as a tape controller and conflicted
with the controller already in my 4000. Changing the CSR address allowed
the system to recognise it as a disk controller but the on-board NVRAM
still had all the SCSI IDs marked as tape drives. I spotted this when I
re-configured the jumpers to enable both controller modes (using the
secondary tape address) and my disk drive showed up as a tape! The
solution was to attach a terminal directly to the CMD card and reset it
to factory defaults, the default setting is for IDs 0-3 to be disks and
4-6 to be tapes. I also changed the disk ID to 0. Once that was done, my
disk showed up as DUA0 and all was well.

It's getting late so I'll post the final jumper settings, QBUS display
and DEV display tomorrow to help anyone else who comes across one of
these cards.

Many thanks for all the replies,
George