27 Jul
2012
27 Jul
'12
9:17 a.m.
I'm curious if anyone here has tried to boot rsts v10.1 with an emulex
UC07 qbus scsi controller.
I'll go ask on the google forums, but I thought I'd ask here also.
I made an ra81 disk image with simh and it boots fine, but when I
transfer the image to a scsi disk and and boot it on an 11/83 with a
UC07 scsi controller it fails (claims something about the cluster size
being wrong).
I'm just trying to get a rsts v10.1 image which will boot on a qbus
11/23 with an UC07. I'm wondering if the UC07's MSCP emulation is at
odds with rsts's MSCP driver.
-brad
27 Jul
27 Jul
9:52 a.m.
On 07/27/2012 12:17 PM, Brad Parker wrote:
I'm curious if anyone here has tried to boot rsts
v10.1 with an emulex
UC07 qbus scsi controller.
I'll go ask on the google forums, but I thought I'd ask here also.
I made an ra81 disk image with simh and it boots fine, but when I
transfer the image to a scsi disk and and boot it on an 11/83 with a
UC07 scsi controller it fails (claims something about the cluster size
being wrong).
I'm just trying to get a rsts v10.1 image which will boot on a qbus
11/23 with an UC07. I'm wondering if the UC07's MSCP emulation is at
odds with rsts's MSCP driver.
It's possible, but I doubt it. I fought and fought with exactly this
until I figured out what was going on.
What I'd bet is happening here is that the UC07's firmware is querying
the SCSI drive for its size, and reporting that back to the MSCP layer
as the size for that unit. If this is not the EXACT number of blocks as
the simh-generated image you transferred to the disk, you will get
exactly this result.
What I do in this case is boot something else on the system, from a
different drive if necessary, and (via an MSCP driver) get the number of
blocks for that specific drive. Here, I usually do this by readdressing
the controller and sticking it into a PDP-11 running 2.11BSD, as its
kernel device probe messages will give you the unit sizes as the drives
are brought online.
Then go back to simh, and use the "rauser" facility to create an MSCP
device of arbitrary size:
sim> set rq0 rauser=<number_of_blocks>
...then do your OS install and transfer your image, and it should boot.
Doing something like "set rq0 ra81" will set the unit size to that of
an RA81, and your SCSI drive is very unlikely to have exactly that
number of blocks.
Give that a shot.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
2:24 p.m.
On Jul 27, 2012 9:55 AM, "Dave McGuire" <mcguire at neurotica.com> wrote:
What I do in this case is boot something else on the system, from a
different drive if necessary, and (via an MSCP driver) get the number of
blocks for that specific drive. Here, I usually do this by readdressing
the controller and sticking it into a PDP-11 running 2.11BSD, as its
kernel device probe messages will give you the unit sizes as the drives
are brought online.
Or boot the the 2.11BSD install tape and run the disklabel program from the
install tape. That displays the full geometry of the disks as reported by
the MSCP controller. I've found that to be useful.
2:37 p.m.
On 07/27/2012 05:24 PM, Glen Slick wrote:
That's a good idea! I guess whichever is more convenient; if you have
a running 2.11BSD system already, or a bootable tape if not.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
What I do in
this case is boot something else on the system, from a
different drive if necessary, and (via an MSCP driver) get the number of
blocks for that specific drive. Here, I usually do this by readdressing
the controller and sticking it into a PDP-11 running 2.11BSD, as its
kernel device probe messages will give you the unit sizes as the drives
are brought online.
Or boot the the 2.11BSD install tape and run the disklabel program from the
install tape. That displays the full geometry of the disks as reported by
the MSCP controller. I've found that to be useful.
4531
days inactive
4531
days old
3 comments
3 participants
participants (3)
-
brad＠heeltoe.com -
glen.slick＠gmail.com -
mcguire＠neurotica.com