On Fri, 11 Feb 2000, NetBSD Bob wrote:

> OK, I guess I am bit by the 5000/200 glitch on the asc_intr thing, finally.
> I was starting a compile last night and loading up some fresh sources, and
> it died with a gross error on 1.4P.  Reloaded 1.4.2A and it worked fine.
> Maybe it is a 5000/200 thing.  Drat!  I was rather getting used to 1/4
> inch high characters in rcons on the PMAG-C card under 1.4P.  The tiny
> print on the PMAG-BA card on the VR297 is.... small.  Anyway.  Is there
> any kind of workaround or fix for the 5000/200 machines or should I just
> wait until a recent snapshot gets posted and try that?  Any insights into
> what is going on and possible fixes are appreciated.

  The "gross" error is not good - I don't remember at the moment what it
indicates, other than some invalid sequence seen by the 53c94 chip.

  I'd guess that someone has made some kind of change in the ASC driver
that broke on the 5000/200.  I haven't seen any problems on a 5000/25
recently, but that would not have been a very recent kernel.  I've also
not seen this on a 5000/150 or 5000/260, but then I haven't been using the
ASC driver on them very much, and also haven't kept up on the latest
kernel on those systems either.

  The 5000/200 is still sitting on the floor in the closet behind me
waiting a place to get connected back up.  If I can ever get my pmax
development going again, and get the 5000/200 connected up, I can probably
figure out what the problem is.

> p.s.  I picked up a couple of 5 gig HP 2490A drives, today in surplus.
>       Anyone know of any problems using them on DS5000/200 hardware?

  The should work, but I can't make any guarentees.  I've been using a
Seagate 4BG Barracuda on a 5000/25 without any problems (of course, it's
been using the MI ncr53c9x driver most of the time).

--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA