Subject: Minimum MicroVAX 3100/20 kernel config?
To: None <port-vax@netbsd.org>
From: NetBSD Bob <nbsdbob@weedcon1.cropsci.ncsu.edu>
List: port-vax
Date: 11/04/1999 09:42:40
I was trying to get VAXbaby to compiler her kernel last night (Yes, Ragge,
it does take overnight, or at least after I feel over asleep.....(:+{{).
but when I checked her this morning, the build had stopped at sbi.c,
in routine sbi_attach, with a def of VAX8600 not being recognized.
I am assuming I have something twiggled incorrectly, in the GENERIC
kernel, although I don't remember for sure if I commented anything out.

My reason for recompiling the kernel is that it is forcing me into a
floppy instead of sd2.  I am assuming it is configured for a VS3100
rather than a MV3100 (it is the SCSIDMA kernel 1.4L).  Dmesg shows
all 5 internal hard drives, but when I invoke sd2 for any reason, it
assumes a 1.2 meg floppy (e.g., in newfsing the thing).

Anyway, for the sake of discussion, anyone have a working minimum config
file for a MicroVAX 3100/20, that uses uba0 scsi1 and scsi2, no floppy,
and can hang at least 6 drives (2 on scsi1 and 4 on scsi2) plus tape and
cd?  Reading the 4.4BSD config does not help much on the later hardware.
And, my VAXspeak is rather primitive, currently.....(:+{{...

The CPU is a KA41-A, and all I saw was a KA410 and a KA42/43, etc.
I am assuming the KA41 is like one of the other CPU's?  The UBA0 
controller seems OK, with ncr1 and ncr2 scsi, and le0 seems to work
on ifconfig and shows up in dmesg.

Alternatively, if I can find copy of the DMASCSI config, and diff
that against the GENERIC, maybe I can pickup on the differences and
see if that explains my sd2 floppy instead of HD problem.

Other than being a little slow, and not letting me hang more drives on
her, VAXbaby is a fun little machine.

Thanks

Bob