All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Howard <mhoward@sigins.com>
To: linux-admin@vger.kernel.org
Subject: Re: Linux aic7xxx driver doesn't see my tape drive
Date: Tue, 20 Apr 2004 04:18:02 -0500	[thread overview]
Message-ID: <c62psb$ro9$1@sea.gmane.org> (raw)
In-Reply-To: 4076361B.90107@kjchome.homeip.net

Kevin J. Cummings wrote:

> Can someone please explain why my Adaptec 2940U Ultra Wide SCSI
> controller (AutoSCSI in the controller BIOS) shows me that my Archive
> Python DAT tape drive is on Channel 0, id 3, but when I boot RedHat's
> linux-2.4.20-28.9, the aic7xxx module only sees my disk drive on channel
> 0, id 6?  Yes, both devices are plugged into the narrow bus, and auto
> termination is configured on the controller, and the devices are in the
> same order as before (see below).
> 
> This used to work fine on my BusLogic BT-948 controller [which I had to
> stop using on my new motherboard (because the ABIT AF7 motherboard won't
> finish POST with the BusLogic BT-948 controller plugged into a PCI
> slot.....)]
> 

I don't know if the st driver actually requires this, but the standard is
for your first tape to be on ID 6.  I'm, in fact, using a 2940U with a
Python DAT on ID 6 with 2.4.25 on a PC next to me right now.

Since you're working with a tape drive, I'll take this chance to advertise
for bacula:  http://www.bacula.org
A free network backup solution. ;)

Other investigatory things you should look at are 'dmesg'
'cat /proc/scsi/scsi' and 'cat /proc/scsi/(modulename)/*'

Digging around in st.c and scsi_scan.c don't indicate anything strange, but,
hey, try out ID 6 anyway -- this is the first time I've looked at either of
those files!

HTH
Matt Howard
-- 
Matt Howard <mhoward@sigins.com>
Superior Insurance - Technical Services


  parent reply	other threads:[~2004-04-20  9:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-09  5:35 Linux aic7xxx driver doesn't see my tape drive Kevin J. Cummings
2004-04-13  0:36 ` Keith Morse
2004-04-15  1:05   ` Kevin J. Cummings
     [not found] ` <407644D0.5050105@baywinds.org>
     [not found]   ` <40770A14.10102@kjchome.homeip.net>
     [not found]     ` <4078BDD9.5030904@baywinds.org>
2004-04-15  3:30       ` Kevin J. Cummings
2004-04-18 17:55         ` Keith Morse
2004-04-18 22:23           ` Bruce Ferrell
2004-04-21 21:56             ` Kevin J. Cummings
2004-04-21 21:54           ` Kevin J. Cummings
2004-04-20  9:18 ` Matt Howard [this message]
2004-04-21 22:21   ` Kevin J. Cummings
2004-04-22  5:55     ` Keith Morse
2004-05-20  1:02       ` Kevin J. Cummings

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='c62psb$ro9$1@sea.gmane.org' \
    --to=mhoward@sigins.com \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.