Date: Tue, 21 Apr 1998 09:02:42 -0700 (PDT)
From: "Steven M. Schultz" <sms@moe.2bsd.com>
Message-Id: <199804211602.JAA14980@moe.2bsd.com>
To: jp@spektr.ludvika.se, sms@moe.2bsd.com
Subject: Re: Some QBus questions.
Cc: pups@minnie.cs.adfa.oz.au, shoppa@alph02.triumf.ca
Sender: owner-pups@minnie.cs.adfa.oz.au
Precedence: bulk

Jorgen -

> > 	Oh - I missed that.  That number did not look right for a MSCP device
> > 	and now I know why ...
> 
> Just went home for lunch and checked again. You're right and I were wrong
> (of course.. :)

	Well, I was a bit wrong too ;)

> The conf output didn't say "ra 1 .." but it said "rl ..". My only excuse
> is that I fiddled with this late last night and wasn't quite awake... :)
> 
> But isn't "rl" the rl in RL02? And the rl entry in /etc/dtab says
> rl	? 174400 ...

	174400 is indeed the first RL controller.

	174440 is the first DEQNA address.  Note the extra '4' ;)

> > ra      ? 172150 154    5       raintr          # uda50, rqdx1/2/3
> > ra      ? 160334 0      5       raintr          # uda50, rqdx1/2/3
> 
> I've added that line to my /etc/dtab and now the kernel finds the Emulex

	Hurrah!

> board. But when I do a "disklabel -r ra1" it complains about I/O error.

	Does the kernel log/print an error message?  Or, is the error
	being printed by the 'disklabel' program?  Do you have the /dev/ra1*
	entries (cd /dev; ./MAKEDEV ra1)?

	Ah, I know what your problem is... (I think).  If this drive is the
	first drive on the SECOND controller the name you need to use is 'ra8'.

	'ra0' is the first drive on the 172150 controller, ra1 is the second
	drive on the 172150 controller, etc.  

	Under 2.11BSD drives are numbered 0 thru 7 on the first controller,
	then 8 thru 15 on the second controller and so on up to a maximum
	of 4 controllers.

	If the drive is the first unit on the second controller it is 'ra8', if
	it is the second drive on the second controller it would be 'ra9' and
	so on.

	You will need 'ra8' devices in /dev:  cd /dev; ./MAKEDEV ra8

	You may find the 'standalone' disklabel program easier to use than the
	one in /bin.  The system's disklabel program will want 'vi' to use when
	editing labels so if you do not have /usr/ucb loaded the disklabel
	program will be very hard to use.  The 'standalone' disklabel program
	("tms(0,1)" from the boot tape) handles unlabeled drives in a more
	friendly manner.

> And a red LED is lit on the controller. Guess that means something is
> wrong?
	
	It might just mean that the board is 'alive' and running.

> I've checked what type of Emulex controller it was and this is what it
> 
> QD3210201 -00D
	
	That would be a QD32.

	Steven