I have a KDA50 qbus controller card set and an RA81 disk drive. I am having
trouble getting them to work in my MicroVAX II.

The netbsd kernel seems to detect the KDA50 as uda0, however I cannot get
it to detect the disk drive. From the chevron prompt I cannot get the vax to
try and boot from the RA81 either, I get error 41 DEVASSIGN, which
according to hamster at http://www.telnet.hu/hamster/dr/ka630.html means
"Device is not present." I am using the b duxy command where x is a or b and y
is 0-4, all with the same result, except b dua0 and b dua1 which gave dev
offline messages, I think they refer to the RX50 floopy drive.

Netbsd reports the following:

Feb  3 19:36:19 bigvax /netbsd: NetBSD 1.5 (GENERIC) #1: Sun Nov 19 15:44:10
PST 2000
Feb  3 19:36:19 bigvax /netbsd:     matt@cheetah.local:/u1/kobj/GENERIC
Feb  3 19:36:19 bigvax /netbsd:
Feb  3 19:36:19 bigvax /netbsd: MicroVAX II
Feb  3 19:36:19 bigvax /netbsd: total memory = 16372 KB
Feb  3 19:36:19 bigvax /netbsd: avail memory = 12448 KB
Feb  3 19:36:19 bigvax /netbsd: using 230 buffers containing 920 KB of memory
Feb  3 19:36:20 bigvax /netbsd: mainbus0 (root)
Feb  3 19:36:20 bigvax /netbsd: ibus0 at mainbus0
Feb  3 19:36:20 bigvax /netbsd: uba0 at ibus0: Q22
Feb  3 19:36:20 bigvax /netbsd: uda0 at uba0 csr 172150 vec 774 ipl 17
Feb  3 19:36:20 bigvax /netbsd: mscpbus0 at uda0: version 2 model 3
Feb  3 19:36:20 bigvax /netbsd: mscpbus0: DMA burst size set to 4
Feb  3 19:36:20 bigvax /netbsd: rx0 at mscpbus0 drive 0: RX50
Feb  3 19:36:20 bigvax /netbsd: rx1 at mscpbus0 drive 1: RX50
Feb  3 19:36:20 bigvax /netbsd: rx0: attempt to get status failed:  unit
offline (not mounted) (code 3, subcode 1)
Feb  3 19:36:20 bigvax /netbsd: qe0 at uba0 csr 174440 vec 770 ipl 17
Feb  3 19:36:20 bigvax /netbsd: qe0: delqa, hardware address 08:00:2b:02:0a:88
Feb  3 19:36:21 bigvax /netbsd: boot device: qe0
Feb  3 19:36:21 bigvax /netbsd: root on qe0
Feb  3 19:36:21 bigvax /netbsd: nfs_boot: trying DHCP/BOOTP
Feb  3 19:36:21 bigvax /netbsd: nfs_boot: timeout...
Feb  3 19:36:21 bigvax last message repeated 2 times
Feb  3 19:36:21 bigvax /netbsd: nfs_boot: trying RARP (and RPC/bootparam)
Feb  3 19:36:21 bigvax /netbsd: nfs_boot: client_addr=192.168.1.3 (RARP from
192.168.1.1)
Feb  3 19:36:21 bigvax /netbsd: nfs_boot: server_addr=192.168.1.1
Feb  3 19:36:21 bigvax /netbsd: nfs_boot: hostname=bigvax
Feb  3 19:36:21 bigvax /netbsd: nfs_boot: gateway=192.168.1.1
Feb  3 19:36:22 bigvax /netbsd: nfs_boot: my_mask=255.255.255.0
Feb  3 19:36:22 bigvax /netbsd: stray interrupt: vector 0x200, ipl 23
Feb  3 19:36:22 bigvax /netbsd: root on amislave:/home/vax/root
Feb  3 19:36:22 bigvax /netbsd: root file system type: nfs

Looking at the detection messages I see the RX50 has appeared on mscpbus0
which appeard on uda0, which would suggest that uda0 is my RQDX3.

Can anyone interpret what is going on for me? I see that both the kda50 cards
have 4 leds on them, and they all stobe on, one after the other in very quick
succession about every 5 seconds.

The RA81 has two black strap cables comming out of the back, labeled A & B.
These cables are screwed to the case but seem to be permanently wired to the
unit, as if you unscrew them there is no plug to pull, just more wires that
are connected inside somewhere.

Do i have to connect both cables to the kda50 card? The RA81 has buttons
labeled A and B, should these be pushed in? Both of them? Does the drive have
to be spun up and the ready light lit when the microvax is turned on? When
netbsd boots? Will the drive be detected even if it is not spinning?

The order of the cards has changed from that displayed on my website, it now
goes:

cpu
ram
ethernet | ram
kda50
kda50
rqdx3


--
Tom Parker - tom@carrott.org
           - http://www.carrott.org