At 10:51 PM 3/14/00 -0600, "J. Buck Caldwell" <buckaroo@igps.org> wrote:
>I'm working, as you know, on getting a 4000/200 co-located at a local ISP. 
>On it,
>I'm planning on putting up a NetBSD mirror. I was also toying with the idea of
>setting it up to build a regular snapshot of -current, say once per week or so
>(depending upon buildability, build time, &ct).

Ok, caveat the issue that you currently have to have -current (the unstable 
build) running to rebuild -current. (sorry couldn't resist :-)

>I hope to have the box installed
>at the ISP this weekend (cross fingers), but I'll still need to get a usable
>system up on it. What is the current state of support for the 4000/200? I know
>someone had put out a KA660 kernel, I think I have a link to it stored 
>somewhere
>(say, are those changes committed yet?), but what exactly is supported? On 
>board
>ethernet? The DSSI isn't needed, as I've got two Q-BUS SCSI controllers 
>(CMD-443)
>and a butload of drives to hook into it. But I will need support for the 
>ethernet
>(well, I suppose I can use a DESQA, but wouldn't the onboard be faster?).

Michael Kukat put up the kernel. DSSI is not supported. I know DESQA is but 
don't know about the on board SCSI.

>By the way - this for anybody familiar with CMD-443 controllers. The 
>device has
>two SCSI connectors on it - is it a dual-channel controller?

Its a very nice controller. I just got my hands on one as well. It is a 
dual channel controller (think dual 220's). Comes in /M and /TM flavors. 
Plug a VT420 into the MMJ and start programming it. There are docs for it 
on the CMD web site.

>The docs I can find
>say 7 devices, but they have a few noticeable errors in them anyway. And 
>it's got
>twice as much logic on the board as the 423 (or 223, for that matter). On 
>another
>note - anybody know how to test out a seemingly dead CMD223? It shows up 
>on SHOW
>QBUS, but with no devices, and the built-in utilities don't respond as at all.

No devices usually means you've not configured the NVRAM and the disks are 
labelled. There is a jumper on the board that can disable the console.

--Chuck