| Title: | SABLE SYSTEM PUBLIC DISCUSSION |
| Moderator: | COSMIC::PETERSON |
| Created: | Mon Jan 11 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2614 |
| Total number of notes: | 10244 |
Hi,
How does it work to connect an adaptec1742-eisa-scsi-adapter manually?
Is it supported anyway to connect it by hand?
I am suffering on the following problem (openvms6.2, dec2100 a500 mp)
(patch alpscsi02_070 doesn`t help):
Connecting an adaptec1742-eisa-scsi-adapter manually does not work,
while doing the same thing with an kzpsa-pci-scsi-adapter works fine.
In dcl:
$ mc sysman
sysman> io sh bus
%SYSMAN-I-OUTPUT, command execution on node DZDMZC
_Bus__________Node_TR#__Name____________Base CSR__________
KA0902 0 1 CPU FFFFFFFFACDBC000
KA0902 1 1 CPU FFFFFFFFACDBE000
KA0902 2 1 CPU FFFFFFFFACDC0000
KA0902 3 1 CPU FFFFFFFFACDC2000
KA0902 7 1 MEM FFFFFFFFACDC4000
KA0902 8 1 IO Port FFFFFFFFACDC6000
PCI 0 2 PCI/NI FFFFFFFFACDC8000
PCI 8 2 PCI/SCSI FFFFFFFFACDCA000
XBUS 0 4 System Board FFFFFFFFACDCE000
XBUS 1 4 Floppy FFFFFFFFACDCE000
XBUS 2 4 Parallel Port FFFFFFFFACDCE000
XBUS 3 4 Serial Port FFFFFFFFACDCE000
EISA 2 3 VGA Adapter FFFFFFFFACE0E000
EISA 3 3 FDDI Adapter FFFFFFFFACE2E000
EISA 4 3 DSSI Adapter FFFFFFFFACE4E000
EISA 6 3 SCSI Adapter FFFFFFFFACE8E000
PCI 48 2 PCI/fwdSCSI FFFFFFFFAD00A000
PCI 56 2 PCI/fwdSCSI FFFFFFFFAD00C000
PCI 64 2 PCI/fwdSCSI FFFFFFFFAD00E000
sysman> io sho exclude
%SYSMAN-I-OUTPUT, command execution on node xxxxxx
%SYSMAN-I-IOEXCLUDE, the current permanent exclusion list is: PKE*
sysman> io autoconf /sel=pke0
sysman> exit
$ sh dev pk
Device Device Error
Name Status Count
PKA0: Online 0
PKE0: Online 0
works fine. Doing the same thing manually leads in a crash (/csr=0) or in
an infinite loop on at least the primary processor (/csr=%XFFFFFFFFACE8E000)
$ mc sysman
sysman> io sho exclude
%SYSMAN-I-OUTPUT, command execution on node xxxxxx
%SYSMAN-I-IOEXCLUDE, the current permanent exclusion list is: PKE*
sysman> io connect pke0/node=6/adapter=3/csr=0/vector=18/driver=sys$pkjdriver
(now a crash "invalid exception while above astdel" occurs)
Motivation:
I have this problem when trying to do an SCSI-Connection between a DEC8400
and a DEC2100 a500 mp in an openvmscluster. The KZPSAs in the DEC8400 connect as
pke0 and pkf0, so I have to move the adapterletters on the DEC2100 from b and c
to e and f.
The adaptec1742-eisa-scsi-adapter won't be used for clustering.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2531.1 | CLOUD::SHIRRON | Stephen F. Shirron, 223-3198 | Mon Feb 24 1997 09:09 | 21 | |
Several problems here... First off, I don't think what you are doing will ever work. The problem is that to be in a SCSI cluster, you have to run the clustering software, which loads drivers very early in the boot process; there is no way to load them later, in a .COM file, like you are trying to do. You might be able to get it to work if you can always boot the Sable first and get the drivers loaded before you boot the TurboLaser. Anyway, to the next part: How are you determining the value to use in /VECTOR? If you don't get the vector right, the system won't work correctly (but at least it probably won't crash). PCI drivers ignore the value passed for /CSR, but EISA drivers do not. This is because PCI drivers can read the appropriate CSR value from PCI configuration space, but no such corresponding capability exists for EISA. So using /CSR=0 will work for PCI, but not for EISA. The value you should use is provided in the IO SHOW BUS display. The "loop" you see may be a result of having the vector wrong, and may have nothing to do with your CSR value. stephen | |||||