1 Dec
2003
1 Dec
'03
8:12 a.m.
Hi all,
I could use some help on setting up a KDA50-Controller in a VAX 4000/200 as I'm
interested in connecting a RA-92 to it (the VAX has no drives installed so far!) so that
NetBSD or VMS can run on it.
The backplane contains the KA-660 Board with extra Memory (MS650), a KLESI- and a
KFQSA-Controller (DSSI), respectively.
Typing "config" in the Console-Mode gives out the adress fopr the
SDI-Controller, if I type in KLESI, KFQSA and KDA50.
I installed the controller directly behind the KFQSA-Board with the address given by
config.
When I type "show qbus" after powering on the Vax, the KDA50 isn't diplayed.
Doing the same routine described above without the KLESI- and KFQSA-Controller brings no
result.
Can the KDA50 be noticed by the "show qbus" command ?
The cycling pattern described in the user guide appears every 4 seconds, that's why I
think that the boards work properly.
How do I know that the VAX found the KDA50 ?
Any hints or ideas?
Thanks alot for your help in advance
Pierre
______________________________________________________________________________
WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und
nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130
1 Dec
1 Dec
9:37 a.m.
VMS can run on it. The backplane contains the KA-660
Board
with extra Memory (MS650), a KLESI- and a KFQSA-Controller
(DSSI), respectively. Typing "config" in the Console-Mode
gives out the adress fopr the SDI-Controller, if I type in
KLESI, KFQSA and KDA50. I installed the controller directly
behind the KFQSA-Board with the address given by config.
It's been a while now but I'm pretty sure that the KFQSA
pretends to be an MSCP device for each disk it has been
configured to recognise. So if you have configured your
KFQSA for two disks, it behaves as two KDA50s. The
exact addresses of these depend on how the KFQSA was
configured.
With your KLESI and KFQSA in the box, try a SHOW QBUS
command. I *think* the KLESI "lives" somewhere else in
the address space so it won't interfere. So you should
see your KFQSA appear once per configured disk. It's
quite likely (if things were working in this config) that
it will be occupying the first two MSCP disk device
addresses. In which case you set the switches on your
KDA50 to be the third such device.
Can the KDA50 be noticed by the "show qbus"
command ?
Yes, definitely. With the post-MicroVAX II systems, it's
one of the quick ways to see if the KDA50 works at all.
It's probably being masked by the KFQSA.
The cycling pattern described in the user guide
appears every
4 seconds, that's why I think that the boards work properly.
How do I know that the VAX found the KDA50 ?
Head over to http://vt100.net/manx and search for KFQSA and
then KDA50. You should be able to pick up scanned installation
manuals for both the KDA50 and the KFQSA.
Antonio
--
---------------
Antonio Carlini arcarlini(a)iee.org
10:10 a.m.
On Mon, 1 Dec 2003, Antonio Carlini wrote:
Yes, a KFQSA controller creates up to three MSCP controllers;
one for each device connected (in my VAX 4705A, which only HAS
three drives.. it may support the full 7 drives..)
So, if you have a KDA50 as well, that could create up to 4
of em. Make sure the one you want to *boot* from is the one
at the MSCP default (17772150 comes to mind?) address.
gives out the
adress fopr the SDI-Controller, if I type in
KLESI, KFQSA and KDA50. I installed the controller directly
behind the KFQSA-Board with the address given by config.
It's been a while now but I'm pretty sure that the KFQSA
pretends to be an MSCP device for each disk it has been
configured to recognise. So if you have configured your
KFQSA for two disks, it behaves as two KDA50s. The
exact addresses of these depend on how the KFQSA was
configured. Yes, definitely. With the post-MicroVAX II systems,
it's
one of the quick ways to see if the KDA50 works at all.
It's probably being masked by the KFQSA.
The KDA probably sits at the default
address, with the KFQSA
also using that address, indeed. Most KFQSA's are configured
to allocate as many controllers as needed, with the first one
sitting at the MSCP-default address, soo..
Fred
--
Fred N. van Kempen, DEC (Digital Equipment Corporation) Collector/Archivist
Visit the VAXlab Project at http://www.pdp11.nl/VAXlab/
Visit the Archives at http://www.pdp11.nl/
Email: waltje(a)pdp11.nl BUSSUM, THE NETHERLANDS / Sunnyvale, CA, USA
7692
days inactive
7692
days old
2 comments
3 participants
participants (3)
-
arcarlini＠iee.org -
cheri-post＠web.de -
waltje＠pdp11.nl