I've just had two VAXen land on me.  The front panel of the one I have
right next to me now says it's a "MicroVAX 3100-80".  The POST messages
and the lettering on the board say it's a KA47.  (Specifically, I see
"KA47-A V1.4-38D-V4.2".)

And NetBSD mostly works, provided I use the 20010509-1.5.1_BETA2
snapshot kernel.  (The 1.4.2 kernel hiccups badly with the serial line,
doesn't find the SCSI interface at all, and panics as soon as I try to
"Enter pathname of shell or RETURN for sh: "; I haven't tried my 1.4T
source tree's GENERIC kernel yet.)

However, there is an oddity.  Despiet working, the kernel misidentifies
the machine; it says

VAXstation 4000/60
cpu: KA46

and the machine is a 3100-80, a KA47.  (And it's not just a 4000/60 in
a 3100-80 case; the silk-screening on the board also says it's a KA47.)

Is this misidentification anything to be concerned about?  There are
three other things of note:

	1) The kernel doesn't like the bootblocks:

asc0 at vsbus0 csr 0x200c0080 vec 774 ipl 15 maskbit 0
asc0: NCR53C94, 25MHz, SCSI ID 7
scsibus0 at asc0: 8 targets, 8 luns per target

WARNING: you must update your boot blocks.

scsibus0: waiting 2 seconds for devices to settle...

	2) The booter doesn't know how to do timeouts; I see

>>> boot esa0

 
-ESA0
>> NetBSD/vax boot [Mar  7 2000 04:32:44] <<
>> Press any key to abort autoboot 5

	and it hangs there until I press a key.

	3) When I do press a key and get the "> " prompt from the
	booter, there is something very peculiar: it smashes everything
	to lower case!  This strikes me as totally bizarre; I've been
	unable to postulate any even vaguely plausible explanation.

I'm going to be playing with it a bit, but wanted to see what was up
with the above points, if anyone knows.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B