no luck with Adaptec SCSI controller in 2.4.X

Kevin B. Hendricks khendricks at
Sat Oct 13 04:13:58 EST 2001


> The old driver never issued more than 8 tags.  The new driver will
> attempt to dynamically determine the capabilities of the drive and can
> issue as much as 253 tags.  The algorithm used depends on the drive
> actually adhering to the SCSI spec and might fail on a buggy drive.  If
> you set the tag depth to 8 you may see similar behavior to the old
> driver.

> >> Perhaps the drive
> >> will function correctly if tagged queing is disabled for it.  You
> >> can do this only for target 1 with the "tag_info" option.  There may
> >> also be firmware updates for this drive.

Okay I used tag_info as you directed and set the Quantum Fireball drive to
use a maximum tag depth of 8 (like the old driver used) and everything
seems to work fine.

So can you point me to where in your driver code the depth of the tagged
queueing is dynamically determined?  I would like to play around a bit
with the driver code to see if I can tell if the Quantum Fireball is
simply spitting back bogus info or and if so what?



> It is like the verbose option.  A sample modules.conf line might look
> like (assuming you are using a loadable module):
> options aic7xxx aic7xxx='"verbose.tag_info:{{}}"'
> This sets the tag depth to 253, 8, 16, 92, and "don't do tags" for the
> targets 0, 1, 2, 3, and all others on adapter 0, respectively.  There is
> a comment section in the driver (I may have only updated it in 6.2.2 or
> 6.2.3) that discusses all of the driver options in detail.  The latest
> driver is 6.2.4.

** Sent via the linuxppc-dev mail list. See

More information about the Linuxppc-dev mailing list