Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!mit-eddie!genrad!decvax!ucbvax!ucbarpa.Berkeley.EDU!haynes
From: haynes@ucbarpa.Berkeley.EDU.UUCP
Newsgroups: comp.bugs.4bsd
Subject: 4.3 won't autoconfigure _certain_ DEC RM03 drives properly
Message-ID: <17204@ucbvax.BERKELEY.EDU>
Date: Wed, 4-Feb-87 22:07:08 EST
Article-I.D.: ucbvax.17204
Posted: Wed Feb  4 22:07:08 1987
Date-Received: Sat, 7-Feb-87 10:00:22 EST
Sender: usenet@ucbvax.BERKELEY.EDU
Distribution: world
Organization: University of California at Berkeley
Lines: 30

Synopsis:   VAX11/780 with DEC RM03 on mba0

config file:	controller mba0 at nexus ?
		disk hp0 at mba? drive 0

		/sys/vaxmba/hp.c  7.1 (Berkeley) 6/5/86

We had to replace a defective RM03 - after DEC worked on for weeks and it
again caught fire they gave up and shipped out a new (refurbished) one.
The new one during autoconfiguration reports the drive type as 9775 (!)
and so is unusable.

I did a lot of poking around in code I don't understand and found that
hpmaptype() piddles with the drive serial number hpsn.  This seems to be
some kludge necessitated by S.I. controllers.  At any rate, the serial number
of the new drive is 8758.  We jumpered a couple of the bits to change it to
8458 or something like that, and then it worked OK.

I hope someone wiser than I will figure out whether the driver really is
weird, or do we have something else wrong in the hardware that causes the
real drive type to be overlooked and activates the S.I. kludge?

Jim Haynes
...ucbvax!ucscc!haynes
haynes@ucscc.bitnet
haynes@ucbarpa.berkeley.edu

"When the going gets weird, the weird turn pro."
	Hunter S. Thompson
*********************************************************