Problem
I have an Adaptec 3940 Dual Channel SCSI PCI controller and want to use it for SCO OpenServer Release 5.
I have attempted to configure this adapter to use the "alad" driver. When SCO OpenServer 5 is booted up, these driver messages are seen on the hardware screen:
device address vector dma comment
--------------------------------------------------------------
...
%adapter 0xXXXX-0xXXXX 11 - type=alad ha=0 id=7 fts=st
%adapter 0xXXXX-0xXXXX 11 - type=alad ha=1 id=7 fts=st
...Although the devices on channel A work fine, I cannot access any of the devices on channel B.
I have tried three different alad drivers:
- the one supplied in the basic SCO OpenServer 5 product - the one from the Advanced Hardware Supplement 5.1 - the one supplied in the Adaptec package ("alad325")
The symptoms of this problem are, however, the same when using each of these drivers.
Cause
Although the Adaptec 3940 appears to be a dual channel card, it is actually two Adaptec 2940's on the same card, and therefore needs to be configured as two separate adapters with different Interrupt Request Queues (IRQs), rather than one adapter with two buses.
Solution
Modify the machine's BIOS configuration for this adapter in order
to configure it to use two different IRQs. For example, use IRQ 11
for the first PCI slot and IRQ 10 for the second (empty) PCI slot.After this change to the BIOS configuration, reboot the system, and these driver messages should now be displayed at the hardware screen:
device address vector dma comment
--------------------------------------------------------------
...
%adapter 0xXXXX-0xXXXX 11 - type=alad ha=0 id=7 fts=st
%adapter 0xXXXX-0xXXXX 10 - type=alad ha=1 id=7 fts=st
...It should now be possible to access all of the devices attached to channel B of this adapter, using any of the three alad drivers specified above.
NOTE: The following hardware requirements are necessary when using the
Adaptec 3940 Dual Channel SCSI PCI controller:- the system BIOS must support PCI-to-PCI bridging (PPB) - the machine's motherboard must be PCI v2.0-compliant