Received: (from major@localhost)
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) id KAA02262
	for pups-liszt; Tue, 21 Apr 1998 10:44:10 +1000 (EST)
X-Authentication-Warning: minnie.cs.adfa.oz.au: major set sender to owner-pups@minnie.cs.adfa.oz.au using -f
Received: from moe.2bsd.com (0@MOE.2BSD.COM [206.139.202.200])
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) with ESMTP id KAA02257
	for <pups@minnie.cs.adfa.oz.au>; Tue, 21 Apr 1998 10:44:03 +1000 (EST)
Received: (from sms@localhost)
	by moe.2bsd.com (8.8.5/8.8.5) id RAA27285;
	Mon, 20 Apr 1998 17:43:12 -0700 (PDT)
Date: Mon, 20 Apr 1998 17:43:12 -0700 (PDT)
From: "Steven M. Schultz" <sms@moe.2bsd.com>
Message-Id: <199804210043.RAA27285@moe.2bsd.com>
To: jp@spektr.ludvika.se, shoppa@alph02.triumf.ca
Subject: Re: Some QBus questions.
Cc: pups@minnie.cs.adfa.oz.au
Sender: owner-pups@minnie.cs.adfa.oz.au
Precedence: bulk

Tim, Jorgen -

	Hello again.  

> Tim Shoppa <shoppa@alph02.triumf.ca>
> > jp@spektr.ludvika.se

> RI?  I don't find that in my ASCII tables.  Can you give me the
> octal value?

> Have you tried going into the setup menu on the terminal and switching
> it between 7 and 8 bits?

	That as my suggestion also.  I have a feeling there's some terminal
	setup parameter (parity is a likely choice) that's not quite right.

> I'm a bit confused - where is this 2.11 kernel from?  Isn't the standard

	It's from the standard GENERIC kernel kit that I put in the archive.

> generic kernel built for just a single ra controller?  Isn't 174400

	Nope - it's built for two.  Let me quick check...

	Yes, NRAC is 2 and NRAD is 3 in the GENERIC config file.  So you can
	have 2 controllers and 3 drives in the generic kernel.

> the standard DEQNA/DELQA ('qe0') address?  Is it possible that

	Oh - I missed that.  That number did not look right for a MSCP device
	and now I know why - it's the DEQNA address ;-)

> In any event, 2.11BSD can be readily convinced - if it's been built
> for two MSCP controllers - to find your second controller at 160334.
> Just go in and modify /etc/dtab.

	That was my suggestion - just need to add

	ra      ? 160334 0    5       raintr          # uda50, rqdx1/2/3

	to the /etc/dtab file (after the first "ra ? 172150" line).  The '0'
	in the vector field tells autoconfig and the kernel to dynamically
	allocate a vector.

> But I'm tending to believe that this won't help your immediate
> situation, because your kernel doesn't have support for a second
> MSCP controller.  If this is the case, then you can just choose

	The kernel has support for a 2nd MSCP controler but...

> to install at your controller at an address of 160334 by telling
> the standalone utilities to install at 'ra(1,0,0)'.  It'll ask
> you which CSR should be used, at which point you'd tell it 160334.

	'boot' does not.  WHen you specify "ra(1,0,0)" to boot it will
	prompt you for the CSR.

	IF later you boot from that second controller the CSR of the booting
	controller is passed thru to the kernel and he will automatically
	attach that as 'ra0' (in which case you need to immediately edit
	/etc/dtab and change the first 'ra' line to come after the one you
	are booting from.

	An example might be useful.  If you have two MSCP controllers at
	172150 and 160334 and are booting/running from the one at 172150
	the two lines in /etc/dtab should be:

ra      ? 172150 154    5       raintr          # uda50, rqdx1/2/3
ra      ? 160334 0      5       raintr          # uda50, rqdx1/2/3

	in that order.

	If you are running/booting from the controller at 160334 the kernel
	will load ok and you need to edit the dtab file so that the lines
	read:

ra      ? 160334 154    5       raintr          # uda50, rqdx1/2/3
ra      ? 172150 0      5       raintr          # uda50, rqdx1/2/3

	The problem is that 'autoconfig' isn't quite as smart as he probably
	should be.  The KERNEL knows it booted and is running from an alternate
	controller but 'autoconfig' doesn't.  Things get confused if you 
	don't order 'dtab' correctly as soon as you have a chance at the first
	'#' prompt.

	ALSO remember that /etc/fstab and /dev/swap will likely need to
	be adjusted as well.

> Once you've done the install, I'm not sure off the top of my head
> how you convince your 11/83 to boot from a nonstandard CSR.  But

	Fill in the 'ADDRESS' field in the menu I believe.

> you will be able to boot from tape, and then tell it to load
> from 'ra(1,0,0)unix', and again you'll be prompted for the CSR.

	'boot' is built for 2 controllers of all device types but only has
	the primary CSR compiled in.  Specifying '1' will cause boot to 
	prompt for a CSR - whatever number you type is treated as octal so
	don't enter '8' or '9' ;-)

	Steven


