Multiple SCSI controller cards

Multiple SCSI controller cards

Post by Scott M. Navarr » Sun, 26 Nov 2000 08:38:49



Hello,

  (Before continuing, it may be important to know that my motherbaord has an
onboard adaptec AIC7xxx controller which controls my primary hardrive, tape,
and CD drive - everything there works fine)

  I am trying to add two Adaptec AHA1740 SCSI EISA controller cards to my
system.  I have set the cards through the EISA setup (bootable configuration
disk that came with system) as follows:

EISA slot #3:
    Interface Mode: Enhanced Mode
    I/O Port Definition: Disabled (Enhanced Mode)
    DMA Channel Definition: Disabled (Enhanced Mode)

    SCSI Device Configuration: Enhanced mode configuration

EISA slot #4:
    Interface Mode: Enhanced Mode
    I/O Port Definition: Disabled (Enhanced Mode)
    DMA Channel Definition: Disabled (Enhanced Mode)

    SCSI Device Configuration: Enhanced mode configuration

  I can only use the above addresses for the host adapter BIOSes since I
also have a Specialix RIO card in the system which apparently uses all of
the DXXXH address space - the configuration program will not let me use any
other addresses for my SCSI controllers other than the ones shown above.

  When the machine boots up, I see both controller's BIOSes and the drives
connected to them come up (I have 6 identical drives - 3 on each
controller):

.Adaptec AHA-1740 BIOS v1.40
.Copyright 1992 Adaptec, Inc.
.[Enhanced Mode]
.
.Target 0 - QUANTUM FIREBALL540S          - Drive D: (81h)
.Target 1 - QUANTUM FIREBALL540S
.Target 2 - QUANTUM FIREBALL540S
.
.Adaptec AHA-1740 BIOS v1.40
.Copyright 1992 Adaptec, Inc.
.[Enhanced Mode]
.
.Target 0 - QUANTUM FIREBALL540S
.Target 1 - QUANTUM FIREBALL540S
.Target 2 - QUANTUM FIREBALL540S

  Then (on a * RH7.0 install) I invoke the command:
'insmod /lib/modules/2.2.16-22/scsi/aha1740.o'
and get the following messages:

.Configuring aha174x at IO:3c80, IRQ 11
.aha174x: Extended translation disabled.
.Configuring aha174x at IO:4c80, IRQ 11
.aha174x: Extended translation disabled.
.Unable to allocate IRQ for adaptec controller.
.scsi1 : Adaptec 174x (EISA)
.scsi : 2 hosts.
.    Vendor: QUANTUM    Model: FIREBALL540S    Rev: 1Q04
.    Type: Direct-Access                            ANSI SCSI revision: 02
.Detected scsi disk sdb at scsi1, channel 0, id 0, lun 0
.    Vendor: QUANTUM    Model: FIREBALL540S    Rev: 1Q04
.    Type: Direct-Access                            ANSI SCSI revision: 02
.Detected scsi disk sdc at scsi1, channel 0, id 1, lun 0
.    Vendor: QUANTUM    Model: FIREBALL540S    Rev: 1Q04
.    Type: Direct-Access                            ANSI SCSI revision: 02
.Detected scsi disk sdd at scsi1, channel 0, id 2, lun 0
.SCSI device sdb: hdwr sector=512 bytes. Sectors= 1065235 [520 MB] [0.5 GB]
. sdb: unknown partition table
.SCSI device sdc: hdwr sector=512 bytes. Sectors= 1065235 [520 MB] [0.5 GB]
. sdc: unknown partition table
.SCSI device sdd: hdwr sector=512 bytes. Sectors= 1065235 [520 MB] [0.5 GB]
. sdd: unknown partition table

  I was then able to 'fdisk' these three devices and setup the partition
tables on these drives.  So, now the above "unknown partition table" lines
read:

. sdb: sdb1
. sdc: sdc1
. sdd: sdd1

  So, now my questions are these:
1)  What does "Extended translation disabled" mean above, and is it a
problem?
2)  Does the "unable to allocate IRQ for adaptec controller" refer to the
second controller that I am not able to access?  (which is shown above as
using the same IRQ as the first one - IRQ 11).  But, the EISA setup program
does not give IRQ choices for 'Enhanced Mode'...

  As a note, these were working in the same box while running the SCO
Openserver O/S.  However, I had these cards set to 'Standard Mode' (instead
of 'Enhanced' - I read that Linux supports the AHA1740 in Enhanced Mode).
Therefore, on the SCO setup I had the IRQs set to 9 and 10, the I/O Port set
to 130H and 230H, the DMAs set to 7 and 6, and the adapter BIOSes disabled
(there was disk array software controlling these cards).  So, there were
enough IRQs before, and I have not added any other cards to the box since
switching to Linux... actually, I removed an AHA1740 card that used to
control the boot drive for SCO (the onboard AIC7xxx controller wasn't used
under the SCO configuration).

  Any help or direction on this would be highly appreciated.

Thanks in advance!

Scott Navarre

 
 
 

Multiple SCSI controller cards

Post by Scott M. Navarr » Sun, 26 Nov 2000 09:23:11


  Please disregard question 1), the message must refer to the "Extended BIOS
translation" that I set to 'Disabled' through the EISA setup for the cards -
and shouldn't matter... all the drives on the controller are less than 1GB
(they are all 0.5GB drives).

 
 
 

Multiple SCSI controller cards

Post by Scott M. Navarr » Sun, 26 Nov 2000 12:04:44


But, I still need the answer to question 2) please!
 
 
 

Multiple SCSI controller cards

Post by Robert Helle » Sun, 31 Dec 1899 09:00:00



  In a message on Fri, 24 Nov 2000 23:38:49 GMT, wrote :

"MN> Hello,
"MN>
"MN>   (Before continuing, it may be important to know that my motherbaord has an
"MN> onboard adaptec AIC7xxx controller which controls my primary hardrive, tape,
"MN> and CD drive - everything there works fine)
"MN>
"MN>   I am trying to add two Adaptec AHA1740 SCSI EISA controller cards to my
"MN> system.  I have set the cards through the EISA setup (bootable configuration
"MN> disk that came with system) as follows:
"MN>
"MN> EISA slot #3:
"MN>     Interface Mode: Enhanced Mode
"MN>     I/O Port Definition: Disabled (Enhanced Mode)
"MN>     DMA Channel Definition: Disabled (Enhanced Mode)

"MN>     SCSI Device Configuration: Enhanced mode configuration
"MN>
"MN> EISA slot #4:
"MN>     Interface Mode: Enhanced Mode
"MN>     I/O Port Definition: Disabled (Enhanced Mode)
"MN>     DMA Channel Definition: Disabled (Enhanced Mode)

"MN>     SCSI Device Configuration: Enhanced mode configuration
"MN>
"MN>   I can only use the above addresses for the host adapter BIOSes since I
"MN> also have a Specialix RIO card in the system which apparently uses all of
"MN> the DXXXH address space - the configuration program will not let me use any
"MN> other addresses for my SCSI controllers other than the ones shown above.
"MN>
"MN>   When the machine boots up, I see both controller's BIOSes and the drives
"MN> connected to them come up (I have 6 identical drives - 3 on each
"MN> controller):
"MN>
"MN> .Adaptec AHA-1740 BIOS v1.40
"MN> .Copyright 1992 Adaptec, Inc.
"MN> .[Enhanced Mode]
"MN> .
"MN> .Target 0 - QUANTUM FIREBALL540S          - Drive D: (81h)
"MN> .Target 1 - QUANTUM FIREBALL540S
"MN> .Target 2 - QUANTUM FIREBALL540S
"MN> .
"MN> .Adaptec AHA-1740 BIOS v1.40
"MN> .Copyright 1992 Adaptec, Inc.
"MN> .[Enhanced Mode]
"MN> .
"MN> .Target 0 - QUANTUM FIREBALL540S
"MN> .Target 1 - QUANTUM FIREBALL540S
"MN> .Target 2 - QUANTUM FIREBALL540S
"MN>
"MN>   Then (on a * RH7.0 install) I invoke the command:
"MN> 'insmod /lib/modules/2.2.16-22/scsi/aha1740.o'
"MN> and get the following messages:
"MN>
"MN> .Configuring aha174x at IO:3c80, IRQ 11
"MN> .aha174x: Extended translation disabled.
"MN> .Configuring aha174x at IO:4c80, IRQ 11
"MN> .aha174x: Extended translation disabled.
"MN> .Unable to allocate IRQ for adaptec controller.
"MN> .scsi1 : Adaptec 174x (EISA)
"MN> .scsi : 2 hosts.
"MN> .    Vendor: QUANTUM    Model: FIREBALL540S    Rev: 1Q04
"MN> .    Type: Direct-Access                            ANSI SCSI revision: 02
"MN> .Detected scsi disk sdb at scsi1, channel 0, id 0, lun 0
"MN> .    Vendor: QUANTUM    Model: FIREBALL540S    Rev: 1Q04
"MN> .    Type: Direct-Access                            ANSI SCSI revision: 02
"MN> .Detected scsi disk sdc at scsi1, channel 0, id 1, lun 0
"MN> .    Vendor: QUANTUM    Model: FIREBALL540S    Rev: 1Q04
"MN> .    Type: Direct-Access                            ANSI SCSI revision: 02
"MN> .Detected scsi disk sdd at scsi1, channel 0, id 2, lun 0
"MN> .SCSI device sdb: hdwr sector=512 bytes. Sectors= 1065235 [520 MB] [0.5 GB]
"MN> . sdb: unknown partition table
"MN> .SCSI device sdc: hdwr sector=512 bytes. Sectors= 1065235 [520 MB] [0.5 GB]
"MN> . sdc: unknown partition table
"MN> .SCSI device sdd: hdwr sector=512 bytes. Sectors= 1065235 [520 MB] [0.5 GB]
"MN> . sdd: unknown partition table
"MN>
"MN>   I was then able to 'fdisk' these three devices and setup the partition
"MN> tables on these drives.  So, now the above "unknown partition table" lines
"MN> read:
"MN>
"MN> . sdb: sdb1
"MN> . sdc: sdc1
"MN> . sdd: sdd1
"MN>
"MN>   So, now my questions are these:
"MN> 1)  What does "Extended translation disabled" mean above, and is it a
"MN> problem?

This is not a problem for *Linux*.  If you were booting from these disks
and they were large enough to have more than 1024 cylinders, LILO would
be unhappy (unless they were partitioned to have a /boot or / partition
whole under the 1024 cylinder limit).  MS-DOS would be unhappy if the
disks were large.  Since none of this applies, this is no big deal.

"MN> 2)  Does the "unable to allocate IRQ for adaptec controller" refer to the
"MN> second controller that I am not able to access?  (which is shown above as
"MN> using the same IRQ as the first one - IRQ 11).  But, the EISA setup program
"MN> does not give IRQ choices for 'Enhanced Mode'...
"MN>
"MN>   As a note, these were working in the same box while running the SCO
"MN> Openserver O/S.  However, I had these cards set to 'Standard Mode' (instead
"MN> of 'Enhanced' - I read that Linux supports the AHA1740 in Enhanced Mode).
"MN> Therefore, on the SCO setup I had the IRQs set to 9 and 10, the I/O Port set
"MN> to 130H and 230H, the DMAs set to 7 and 6, and the adapter BIOSes disabled
"MN> (there was disk array software controlling these cards).  So, there were
"MN> enough IRQs before, and I have not added any other cards to the box since
"MN> switching to Linux... actually, I removed an AHA1740 card that used to
"MN> control the boot drive for SCO (the onboard AIC7xxx controller wasn't used
"MN> under the SCO configuration).

It appears that Linux will support ONE AHA1740 in Enhanced Mode, but
not two...  You should either set one (or both) cards to 'Standard Mode'
and use different IRQ's for the two cards...

"MN>
"MN>   Any help or direction on this would be highly appreciated.
"MN>
"MN> Thanks in advance!
"MN>
"MN> Scott Navarre
"MN>
"MN>
"MN>                                                                                                                                

--
                                     \/


http://www.veryComputer.com/              /\FidoNet:    1:321/153

 
 
 

Multiple SCSI controller cards

Post by Scott M. Navarr » Mon, 27 Nov 2000 13:37:43


Quote:> It appears that Linux will support ONE AHA1740 in Enhanced Mode, but
> not two...  You should either set one (or both) cards to 'Standard Mode'
> and use different IRQ's for the two cards...

  Thank you very much for your suggestion.

  I recently tried setting both cards to Standard mode, using the same
settings as they were configured (and working) on the SCO system.

  However, I had read the source code 'aha1740.c' and apparently this driver
only works for these cards operating in Enhanced Mode.
  I also read the Adaptec manual for the 1740 cards which explains why.  It
said that "Standard Mode is an AHA-1540/1542 compatible interface that
allows the use of AHA-1540/1542 software drivers.  Enhanced Mode is a higher
performance interface that uses AHA-1740 software drivers".
  So, I tried setting both cards to Standard Mode and used the 'aha1542.o'
driver module invoked by the 'insmod' command and this is what I got:

scsi : 1 host.
/lib/modules/2.2.16-22/scsi/aha1542.o : init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters

  Any other suggestions?

Thanks again,
  Scott Navarre

 
 
 

Multiple SCSI controller cards

Post by Scott M. Navarr » Mon, 27 Nov 2000 13:42:24


  One other note:  The header comments at the top of 'aha1740.c' says
"Multiple adapter support"...
Quote:> It appears that Linux will support ONE AHA1740 in Enhanced Mode, but
> not two...  You should either set one (or both) cards to 'Standard Mode'
> and use different IRQ's for the two cards...

 
 
 

1. One SCSI controller is not recognized with another SCSI controller

Hello,

I have an ISA SCSI controller (AHA1522B) to which Iomega Jaz external
and Plextor SCSI CD-ROM internal are attached and a PCI SCSI (AHA2940UW)
with two wide hard drives attached (C:, D:).

When I tried to boot from Debian Linux (Debian GNU/Linux 1.2.2), the
first SCSI controller (AHA1522B) was not recognized, but AHA2940UW was.
I disabled the bios of AHA1522B in vain. I tried with Slackware Linux
with the same result.

I can connect the CD-ROM to AHA2940UW, but I have Jaz still on the
AHA1522B since AHA2940UW works that way.

Please let me know if there is any way I can use both of the controllers
or I can use all of the devices (Wide SCSI H/Ds, SCSI CD-ROM, SCSI Jaz)
on the AHA2940UW..

Sincerely,
DH.
--
Dong Hwan Nam
#18-1 2/6 Bu-Won Dong, Kim-Hae Si, Kyong-Nam, Seoul, Korea

Tel: 011-82-525-25-3563/33-8829, Fax: 011-82-525-25-3563

2. pptp vpn problem: can connect but no traffic

3. Multiple Adaptec SCSI controllers

4. permissions

5. Multiple 1742 Scsi Controllers (fwd)

6. Support for Mylex lnp101?

7. multiple scsi controllers?

8. Windows-like pointer acceleration

9. Multiple SCSI Controllers on 1.3.97

10. Multiple SCSI Controllers in One Machine

11. Multiple SCSI controller device nomenclature

12. Multiple SCSI controllers (Adaptec)

13. Multiple SCSI controllers