jan-jaap wrote:
Changing the SCSI host ID this way is a bit of a hack: it changes the host ID of all controllers in the system
This is wrong. Or at least it is incomplete.
Changing the scsihostid variable in PROM changes the hostid of the
standard onboard scsi controllers.
I added an LSI dual Ultra320 controller to improve the transfer rates of my PowerVault, and it was completely unaffected by the scsihostid variable.
But /var/sysgen/system/irix.sm lists a variety of tunables for the LSI driver ('ls'). One of them is:
Code:
ls_scsi_hostid (valid for controller only)
(valid range 0-15, default is 0)
The syntax is a little involved, but you can (no, you
must) set it per controller, like this
Code:
* Set the SCSI ID to 7 for the LSI dual U320 card to make the PowerVault 220S work
DEVICE_ADMIN: /hw/module/001c01/IXbrick/xtalk/11/pci-x/1/1a/scsi_ctlr/0 ls_scsi_hostid=7
DEVICE_ADMIN: /hw/module/001c01/IXbrick/xtalk/11/pci-x/1/1b/scsi_ctlr/0 ls_scsi_hostid=7
The dual U320 scsi controller shows up in 'hinv' like this:
Code:
Integral SCSI controller 5: Version LS1030, low voltage differential
Integral SCSI controller 6: Version LS1030, low voltage differential
The full device path for controllers 5 & 6 can then be found like this:
Code:
tezro 12# ls -l /hw/scsi_ctlr/
total 0
lrw------- 1 root sys 57 Feb 28 14:43 0 -> /hw/module/001c01/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/0
lrw------- 1 root sys 57 Feb 28 14:43 1 -> /hw/module/001c01/IXbrick/xtalk/15/pci-x/0/3/scsi_ctlr/1
lrw------- 1 root sys 57 Feb 28 14:43 2 -> /hw/module/001c01/IXbrick/xtalk/15/pci-x/0/1/scsi_ctlr/0
lrw------- 1 root sys 58 Feb 28 14:43 3 -> /hw/module/001c01/IXbrick/xtalk/11/pci-x/0/1a/scsi_ctlr/0
lrw------- 1 root sys 58 Feb 28 14:43 4 -> /hw/module/001c01/IXbrick/xtalk/11/pci-x/0/1b/scsi_ctlr/0
lrw------- 1 root sys 58 Feb 28 14:43 5 -> /hw/module/001c01/IXbrick/xtalk/11/pci-x/1/1a/scsi_ctlr/0
lrw------- 1 root sys 58 Feb 28 14:43 6 -> /hw/module/001c01/IXbrick/xtalk/11/pci-x/1/1b/scsi_ctlr/0
lrw------- 1 root sys 58 Feb 28 14:43 7 -> /hw/module/001c01/IXbrick/xtalk/11/pci-x/1/2a/scsi_ctlr/0
lrw------- 1 root sys 58 Feb 28 14:43 8 -> /hw/module/001c01/IXbrick/xtalk/11/pci-x/1/2b/scsi_ctlr/0
After a quick '/etc/autoconfig -fv' & reboot, the PowerVault 220S shows up:
Code:
Integral SCSI controller 5: Version LS1030, low voltage differential
Disk drive: unit 0 on SCSI controller 5 (unit 0)
Disk drive: unit 1 on SCSI controller 5 (unit 1)
Disk drive: unit 2 on SCSI controller 5 (unit 2)
Disk drive: unit 3 on SCSI controller 5 (unit 3)
Disk drive: unit 4 on SCSI controller 5 (unit 4)
Disk drive: unit 5 on SCSI controller 5 (unit 5)
Scanner: unit 6 on SCSI controller 5
Disk drive: unit 8 on SCSI controller 5 (unit 8)
Integral SCSI controller 6: Version LS1030, low voltage differential
Scanner: unit 6 on SCSI controller 6
Disk drive: unit 9 on SCSI controller 6 (unit 9)
Disk drive: unit 10 on SCSI controller 6 (unit 10)
Disk drive: unit 11 on SCSI controller 6 (unit 11)
Disk drive: unit 12 on SCSI controller 6 (unit 12)
Disk drive: unit 13 on SCSI controller 6 (unit 13)
Disk drive: unit 14 on SCSI controller 6 (unit 14)
Disk drive: unit 15 on SCSI controller 6 (unit 15)
Notice the disk at SCSI ID 0 on controller 5
Each channel of the Powervault contains a management module which shows up as a scanner in IRIX

_________________
Now this is a deep dark secret, so everybody keep it quiet 
It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgiCurrently in commercial service:

(2x)

In the
museum: almost every MIPS/IRIX system.
Wanted: GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)