[pups] Hardware config for 2.11BSD Installation on PDP-11/73]

Chuck Dickman chd at nktelco.net
Mon Feb 5 11:49:50 AEST 2001


"Steven M. Schultz" wrote:
>
> Hi -
>
<snip>
What you described here makes sense and was my first impression of
what should happen, but my experience is different.
>
>         In my /etc/dtab file I have:
>
> ra      ? 172154 154    5       raintr          # uda50, rqdx1/2/3
> ra      ? 172150 0      5       raintr          # 2nd uda50/uc08

My /etc/dtab is:

ra      ? 172150 154    5       raintr          # uda50, rqdx1/2/3
ra      ? 160334 160    5       raintr          # secondary mscp

The CQD220 is at 172150 and the RXDX3 is at 160334. Is 172154 a valid
MSCP address? It must be, cause it works for you. The docs I have
show 160334.

On booting the 11/73 and starting 2.11 BSD the following occurs:

DU8 and DU9 at boot are the RX50 drives on the second controller. The
floppy in DU8 contains the installation standalone utilities that were
part of the installation tape, including icheck.

------------
Testing in progress - Please wait
Memory Size is 1024 K Bytes
9 Step memory test
  Step 1 2 3 4 5 6 7 8 9

Message 04      Entering Dialog mode

Commands are Help, Boot, List, Setup, Map and Test.
Type a command then press the RETURN key: B DU8

Trying DU8

Starting system from DU8

.83Boot from ra(1,0,0) at 0160334
.: ra(1,0,0)/icheck
.ra(1,0,0) err op=89 sts=3
.ra(1,0,0) !online
.: ra(0,0,0)/unix
.Boot: bootdev=02400 bootcsr=0172150
.
2.11 BSD UNIX #10: Fri Nov 24 16:52:18 PST 2000
    root at mars.chd-net:/usr/src/sys/MARS

ra0: Ver 6 mod 13
ra0: RA82  size=1295849
attaching qe0 csr 174440
qe0: DEC DELQA addr 08:00:2b:0e:24:7c
attaching lo0

phys mem  = 1048576
avail mem = 725696
user mem  = 307200

February  1 23:38:41 init: configure system

hk ? csr 177440 vector 210 skipped:  No autoconfig routines.
ht ? csr 172440 vector 224 skipped:  No autoconfig routines.
ra 0 csr 172150 vector 154 vectorset attached
ra 1 csr 160334 vector 160 vectorset attached
rl ? csr 174400 vector 160 skipped:  No autoconfig routines.
tm ? csr 172520 vector 224 skipped:  No autoconfig routines.
ts 0 csr 172520 vector 224 attached
xp ? csr 176700 vector 254 skipped:  No autoconfig routines.
erase, kill ^U, intr ^C
#
# mount /dev/ra8a /mnt/rx0
ra1: Ver 4 mod 3
ra8 st=3 sb=0 fl=0 en=9
/dev/ra8a on /mnt/rx0: Input/output error
: not found
: not found
# mount /dev/ra9a /mnt/rx0
ra9 st=3 sb=0 fl=0 en=9
/dev/ra9a on /mnt/rx0: Input/output error
#
>
>         It's pretty simple and regular once one knows what is going on ;)
>
I agree that it is pretty simple as you describe it and it is what I
expected,
but it does not seem to be as I see it here. Could the problem be that I
am
booting from the second controller? Should all the controllers be
jumpered for
unit 0? Now that I think about it, it may be the boot firmware that is
uncooperative. If I set the RQDX3 for unit 0, I cannot boot from the
second
controller's first disk, but I can from the second. So, I should set all
the
controller unit numbers to 0. The restriction is that the boot device
must
be visible to the firmware. Make sense?

...

OK, I moved the RQDX3 to unit 0, and the boot floppy to the second
drive.
The boot is then:

--------------
Testing in progress - Please wait
Memory Size is 1024 K Bytes
9 Step memory test
  Step 1 2 3 4 5 6 7 8 9

Message 04      Entering Dialog mode

Commands are Help, Boot, List, Setup, Map and Test.
Type a command then press the RETURN key: B DU1

Trying DU1

Starting system from DU1

.83Boot from ra(1,1,0) at 0160334
.: ra(0,0,0)/unix
.Boot: bootdev=02400 bootcsr=0172150
.
2.11 BSD UNIX #10: Fri Nov 24 16:52:18 PST 2000
    root at mars.chd-net:/usr/src/sys/MARS

ra0: Ver 6 mod 13
ra0: RA82  size=1295849
attaching qe0 csr 174440
qe0: DEC DELQA addr 08:00:2b:0e:24:7c
attaching lo0

phys mem  = 1048576
avail mem = 725696
user mem  = 307200

February  1 23:38:41 init: configure system

hk ? csr 177440 vector 210 skipped:  No autoconfig routines.
ht ? csr 172440 vector 224 skipped:  No autoconfig routines.
ra 0 csr 172150 vector 154 vectorset attached
ra 1 csr 160334 vector 160 vectorset attached
rl ? csr 174400 vector 160 skipped:  No autoconfig routines.
tm ? csr 172520 vector 224 skipped:  No autoconfig routines.
ts 0 csr 172520 vector 224 attached
xp ? csr 176700 vector 254 skipped:  No autoconfig routines.
erase, kill ^U, intr ^C
# mount /dev/ra9a /mnt/rx0
ra1: Ver 4 mod 3
ra9: RX50  size=800
# ls /mnt/rx0
boot        icheck      restor      unix
disklabel   mkfs        rx50toroot
#
>         Steven Schultz
>         sms at to.gd-es.com
Thanks for helping me work through this. It looks like the boot device
must be
within the first 8 devices that the firmware can see, but 2.11 BSD wants
all
the unit number jumpers set to 0.

Chuck Dickman
chd at nktelco.net
-------------- next part --------------
An embedded message was scrubbed...
From: Chuck Dickman <chd at nktelco.net>
Subject: Re: [pups] Hardware config for 2.11BSD Installation on PDP-11/73
Date: Sun, 04 Feb 2001 20:43:06 -0500
Size: 5237
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20010204/67cb34c9/attachment.mht>


More information about the TUHS mailing list