Linux aic7xxx driver doesn"t see my tape drive
Linux aic7xxx driver doesn"t see my tape drive
am 09.04.2004 07:35:23 von cummings
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.....)]
--
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 13.04.2004 02:36:36 von Keith Morse
On Fri, 9 Apr 2004, 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).
Please post the output of lspci.
>
> 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.....)]
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 15.04.2004 03:05:03 von cummings
Keith Morse wrote:
> On Fri, 9 Apr 2004, 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).
>
>
> Please post the output of lspci.
OK, here it is:
> 00:00.0 Host bridge: nVidia Corporation: Unknown device 01e0 (rev c1)
> 00:00.1 RAM memory: nVidia Corporation: Unknown device 01eb (rev c1)
> 00:00.2 RAM memory: nVidia Corporation: Unknown device 01ee (rev c1)
> 00:00.3 RAM memory: nVidia Corporation: Unknown device 01ed (rev c1)
> 00:00.4 RAM memory: nVidia Corporation: Unknown device 01ec (rev c1)
> 00:00.5 RAM memory: nVidia Corporation: Unknown device 01ef (rev c1)
> 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
> 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
> 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
> 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
> 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
> 00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
> 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
> 00:08.0 PCI bridge: nVidia Corporation: Unknown device 006c (rev a3)
> 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
> 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
> 01:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
> 01:0a.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U
> 02:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2)
>>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.....)]
--
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 15.04.2004 05:30:08 von cummings
Well,
Given that the tape drive is attached to the Adaptec 2940U SCSI=20
controller, doesn't st have to eventually send SCSI commands to the=20
aic7xxx driver????
Here are the relevent modules after I:
depmod -ae
modprobe st
> [root@kjc386 root]# lsmod
> st 29964 0 (unused)
> ide-scsi 11120 0
> sd_mod 13004 2
> sr_mod 16888 0 (autoclean)
> cdrom 31040 0 [sr_mod ide-cd]
> aic7xxx 130996 1
> scsi_mod 102968 6 [st sg sr_mod ide-scsi aic7xxx sd_m=
od]
But, there is still no mention of the tape drive in /proc/scsi/scsi, no=
r=20
when I:
cdrecord --scanbus
> Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schil=
ling
> Linux sg driver version: 3.1.24
> Using libscg version 'schily-0.7'
> scsibus0:
> 0,0,0 0) *
> 0,1,0 1) *
> 0,2,0 2) *
> 0,3,0 3) *
> 0,4,0 4) *
> 0,5,0 5) *
> 0,6,0 6) 'IBM ' 'DSAS-3360 !a' 'S47Q' Disk
> 0,7,0 7) *
> scsibus1:
> 1,0,0 100) 'CDWRITER' 'IDE5224 ' '001H' Removable C=
D-ROM
> 1,1,0 101) *
> 1,2,0 102) *
> 1,3,0 103) *
> 1,4,0 104) *
> 1,5,0 105) *
> 1,6,0 106) *
> 1,7,0 107) *
mt -f /dev/st0 status
> /dev/st0: No such device
Bruce Ferrell wrote:
> st shouldn't be aliased to your aic7xxx. That causes modprobe to try=
to=20
> load the aic driver when you try to load st.
>=20
> Remove the alias, run depmod -ae, then modprobe st
>=20
> this is the output of lsmod on my system:
>=20
> [root@baywinds root]# lsmod
> Module Size Used by Not tainted
> sr_mod 16248 0 (autoclean)
> ixj 120992 0 (autoclean)
> phonedev 4000 1 (autoclean) [ixj]
> vfat 12220 0 (autoclean)
> fat 40696 0 (autoclean) [vfat]
> ipt_MASQUERADE 2848 1 (autoclean)
> ipt_LOG 4576 0 (autoclean)
> ipt_state 1216 1 (autoclean)
> iptable_filter 2464 1 (autoclean)
> ip_nat_irc 3840 0 (unused)
> ip_nat_ftp 4768 0 (unused)
> iptable_nat 28308 3 [ipt_MASQUERADE ip_nat_irc ip_nat_f=
tp]
> ip_conntrack_irc 4608 1 [ip_nat_irc]
> ip_conntrack_ftp 5568 1 [ip_nat_ftp]
> ip_conntrack 41076 2 [ipt_MASQUERADE ipt_state ip_nat_ir=
c=20
> ip_nat_ftp iptable_nat ip_conntrack_irc ip_conntrack_ftp]
> ip_tables 17792 7 [ipt_MASQUERADE ipt_LOG ipt_state=20
> iptable_filter iptable_nat]
> cipcb 31648 1
> sb 9184 0 (autoclean)
> sb_lib 44736 0 (autoclean) [sb]
> uart401 8160 0 (autoclean) [sb_lib]
> sound 76044 0 (autoclean) [sb_lib uart401]
> hostap_pci 51692 1
> hostap 98760 0 [hostap_pci]
> eepro100 22604 1
> mii 4060 0 [eepro100]
> tulip 52128 1
> crc32 3948 0 [tulip]
> ide-floppy 15552 0 (autoclean)
> st 30352 0 (unused)
> loop 11632 3 (autoclean)
> md 64384 0 (unused)
>=20
>=20
> And from the below, you can see st.o is a module that stands apart fr=
om=20
> the scsi drivers. That's what recognizes your tape drive and activat=
es=20
> /dev/st0
>=20
>=20
> locate /st.o
> /lib/modules/2.4.18-3smp/kernel/drivers/scsi/st.o
> /lib/modules/2.4.18-3/kernel/drivers/scsi/st.o
> /lib/modules/2.4.18-3debug/kernel/drivers/scsi/st.o
> /lib/modules/2.4.20-28.7/kernel/drivers/scsi/st.o
> /lib/modules/2.4.18-27.7.xdebug/kernel/drivers/scsi/st.o
> /lib/modules/2.4.20-28.7smp/kernel/drivers/scsi/st.o
> /lib/modules/2.4.25/kernel/drivers/scsi/st.o
> /usr/src/linux-2.4.25/drivers/scsi/st.o
>=20
>=20
> Kevin J. Cummings wrote:
>=20
>> I have the following in my modules.conf:
>>
>> alias st0 aic7xxx
>>
>> (it used to be:
>> alias st0 BusLogic
>> )
>>
>> Even so, when I "modprobe st", "mt -f /dev/st0 status" still tells m=
e:
>>
>> /dev/st0: No such device
>>
>>
>> Bruce Ferrell wrote:
>>
>>> have you loaded the st module? (modprobe st)
>>>
>>> Kevin J. Cummings wrote:
>>>
>>>> Can someone please explain why my Adaptec 2940U Ultra Wide SCSI=20
>>>> controller (AutoSCSI in the controller BIOS) shows me that my=20
>>>> Archive Python DAT tape drive is on Channel 0, id 3, but when I bo=
ot=20
>>>> RedHat's linux-2.4.20-28.9, the aic7xxx module only sees my disk=20
>>>> drive on channel 0, id 6? Yes, both devices are plugged into the=20
>>>> narrow bus, and auto termination is configured on the controller,=20
>>>> 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 h=
ad=20
>>>> to stop using on my new motherboard (because the ABIT AF7=20
>>>> motherboard won't finish POST with the BusLogic BT-948 controller=20
>>>> plugged into a PCI slot.....)]
>>>>
>>>
>>
>=20
--=20
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 18.04.2004 19:55:58 von Keith Morse
On Wed, 14 Apr 2004, Kevin J. Cummings wrote:
> Well,
> Given that the tape drive is attached to the Adaptec 2940U SCSI=20
> controller, doesn't st have to eventually send SCSI commands to the=20
> aic7xxx driver????
>=20
> Here are the relevent modules after I:
>=20
> depmod -ae
> modprobe st
>=20
> > [root@kjc386 root]# lsmod
> > st 29964 0 (unused)
> > ide-scsi 11120 0
> > sd_mod 13004 2
> > sr_mod 16888 0 (autoclean)
> > cdrom 31040 0 [sr_mod ide-cd]
> > aic7xxx 130996 1
> > scsi_mod 102968 6 [st sg sr_mod ide-scsi aic7xxx sd=
_mod]
>=20
> But, there is still no mention of the tape drive in /proc/scsi/scsi, =
nor=20
> when I:
>=20
> cdrecord --scanbus
>=20
> > Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Sch=
illing
> > Linux sg driver version: 3.1.24
> > Using libscg version 'schily-0.7'
> > scsibus0:
> > 0,0,0 0) *
> > 0,1,0 1) *
> > 0,2,0 2) *
> > 0,3,0 3) *
> > 0,4,0 4) *
> > 0,5,0 5) *
> > 0,6,0 6) 'IBM ' 'DSAS-3360 !a' 'S47Q' Disk
> > 0,7,0 7) *
> > scsibus1:
> > 1,0,0 100) 'CDWRITER' 'IDE5224 ' '001H' Removable=
CD-ROM
> > 1,1,0 101) *
> > 1,2,0 102) *
> > 1,3,0 103) *
> > 1,4,0 104) *
> > 1,5,0 105) *
> > 1,6,0 106) *
> > 1,7,0 107) *
>=20
> mt -f /dev/st0 status
>=20
> > /dev/st0: No such device
Is this also reflected on the bios output during post on the scsci=20
controller? Sorry if you already mentioned in a previous, but errantly=
=20
deleted them.
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 19.04.2004 00:23:47 von Bruce Ferrell
Well that's not good! Mine does show up:
cdrecord -scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schill=
ing
Linux sg driver version: 3.1.25
Using libscg version 'schily-0.5'
scsibus0:
0,0,0 0) 'IBM ' 'DNES-318350W ' 'SAH0' Disk
0,1,0 1) 'IBM ' 'DNES-318350W ' 'SAH0' Disk
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) 'IMATION ' 'CD-R IMR080020 ' '1.07' Removable CD=
-ROM
0,6,0 6) *
0,7,0 7) *
scsibus1:
1,0,0 100) 'SEAGATE ' 'SX910800N ' '8514' Disk
1,1,0 101) *
1,2,0 102) 'SEAGATE ' 'SX910800N ' '8514' Disk
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) 'HP ' 'C1533A ' 'A907' Removable Ta=
pe
1,7,0 107) *
When you boot the system, during the Adaptec startup, there can be, if=20
it's turned on, a Control-A prompt. Does the tape drive show up in the=
=20
bios setup screens?
Keith Morse wrote:
> On Wed, 14 Apr 2004, Kevin J. Cummings wrote:
>=20
>=20
>>Well,
>> Given that the tape drive is attached to the Adaptec 2940U SCSI=20
>>controller, doesn't st have to eventually send SCSI commands to the=20
>>aic7xxx driver????
>>
>> Here are the relevent modules after I:
>>
>>depmod -ae
>>modprobe st
>>
>>
>>>[root@kjc386 root]# lsmod
>>>st 29964 0 (unused)
>>>ide-scsi 11120 0
>>>sd_mod 13004 2
>>>sr_mod 16888 0 (autoclean)
>>>cdrom 31040 0 [sr_mod ide-cd]
>>>aic7xxx 130996 1
>>>scsi_mod 102968 6 [st sg sr_mod ide-scsi aic7xxx sd_=
mod]
>>
>>But, there is still no mention of the tape drive in /proc/scsi/scsi, =
nor=20
>>when I:
>>
>>cdrecord --scanbus
>>
>>
>>>Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schi=
lling
>>>Linux sg driver version: 3.1.24
>>>Using libscg version 'schily-0.7'
>>>scsibus0:
>>> 0,0,0 0) *
>>> 0,1,0 1) *
>>> 0,2,0 2) *
>>> 0,3,0 3) *
>>> 0,4,0 4) *
>>> 0,5,0 5) *
>>> 0,6,0 6) 'IBM ' 'DSAS-3360 !a' 'S47Q' Disk
>>> 0,7,0 7) *
>>>scsibus1:
>>> 1,0,0 100) 'CDWRITER' 'IDE5224 ' '001H' Removable =
CD-ROM
>>> 1,1,0 101) *
>>> 1,2,0 102) *
>>> 1,3,0 103) *
>>> 1,4,0 104) *
>>> 1,5,0 105) *
>>> 1,6,0 106) *
>>> 1,7,0 107) *
>>
>>mt -f /dev/st0 status
>>
>>
>>>/dev/st0: No such device
>=20
>=20
>=20
>=20
> Is this also reflected on the bios output during post on the scsci=20
> controller? Sorry if you already mentioned in a previous, but errant=
ly=20
> deleted them.
>=20
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin=
" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>=20
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 20.04.2004 11:18:02 von Matt Howard
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
Superior Insurance - Technical Services
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 21.04.2004 23:54:22 von cummings
Keith Morse wrote:
> On Wed, 14 Apr 2004, Kevin J. Cummings wrote:
>=20
>=20
>>Well,
>> Given that the tape drive is attached to the Adaptec 2940U SCSI=20
>>controller, doesn't st have to eventually send SCSI commands to the=20
>>aic7xxx driver????
>>
>> Here are the relevent modules after I:
>>
>>depmod -ae
>>modprobe st
>>
>>
>>>[root@kjc386 root]# lsmod
>>>st 29964 0 (unused)
>>>ide-scsi 11120 0
>>>sd_mod 13004 2
>>>sr_mod 16888 0 (autoclean)
>>>cdrom 31040 0 [sr_mod ide-cd]
>>>aic7xxx 130996 1
>>>scsi_mod 102968 6 [st sg sr_mod ide-scsi aic7xxx sd_=
mod]
>>
>>But, there is still no mention of the tape drive in /proc/scsi/scsi, =
nor=20
>>when I:
>>
>>cdrecord --scanbus
>>
>>
>>>Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schi=
lling
>>>Linux sg driver version: 3.1.24
>>>Using libscg version 'schily-0.7'
>>>scsibus0:
>>> 0,0,0 0) *
>>> 0,1,0 1) *
>>> 0,2,0 2) *
>>> 0,3,0 3) *
>>> 0,4,0 4) *
>>> 0,5,0 5) *
>>> 0,6,0 6) 'IBM ' 'DSAS-3360 !a' 'S47Q' Disk
>>> 0,7,0 7) *
>>>scsibus1:
>>> 1,0,0 100) 'CDWRITER' 'IDE5224 ' '001H' Removable =
CD-ROM
>>> 1,1,0 101) *
>>> 1,2,0 102) *
>>> 1,3,0 103) *
>>> 1,4,0 104) *
>>> 1,5,0 105) *
>>> 1,6,0 106) *
>>> 1,7,0 107) *
>>
>>mt -f /dev/st0 status
>>
>>
>>>/dev/st0: No such device
>=20
>=20
>=20
>=20
> Is this also reflected on the bios output during post on the scsci=20
> controller? Sorry if you already mentioned in a previous, but errant=
ly=20
> deleted them.
No, during POST, I can see both devices as id 3 (tape drive) and id 6=20
(disk drive) before linux boots. I can see both devices using the=20
Auto-SCSI in the SCSI BIOS if I invoke it (it even tells me that the=20
tape drive is not a disk drive!)....
--=20
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 21.04.2004 23:56:15 von cummings
Bruce Ferrell wrote:
> Well that's not good! Mine does show up:
>=20
> cdrecord -scanbus
> Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schi=
lling
> Linux sg driver version: 3.1.25
> Using libscg version 'schily-0.5'
> scsibus0:
> 0,0,0 0) 'IBM ' 'DNES-318350W ' 'SAH0' Disk
> 0,1,0 1) 'IBM ' 'DNES-318350W ' 'SAH0' Disk
> 0,2,0 2) *
> 0,3,0 3) *
> 0,4,0 4) *
> 0,5,0 5) 'IMATION ' 'CD-R IMR080020 ' '1.07' Removable C=
D-ROM
> 0,6,0 6) *
> 0,7,0 7) *
> scsibus1:
> 1,0,0 100) 'SEAGATE ' 'SX910800N ' '8514' Disk
> 1,1,0 101) *
> 1,2,0 102) 'SEAGATE ' 'SX910800N ' '8514' Disk
> 1,3,0 103) *
> 1,4,0 104) *
> 1,5,0 105) *
> 1,6,0 106) 'HP ' 'C1533A ' 'A907' Removable T=
ape
> 1,7,0 107) *
>=20
> When you boot the system, during the Adaptec startup, there can be, i=
f=20
> it's turned on, a Control-A prompt. Does the tape drive show up in t=
he=20
> bios setup screens?
Yes, it does. Tape drive is id 3, disk drive is id 6....
--=20
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 22.04.2004 00:21:22 von cummings
Matt Howard wrote:
> 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.
But that's where my disk drive is. B^) Besides. This setup worked
just fine when the SCSI controller was a BusLogic BT-948.... That's
what makes me think its an aic7xxx driver problem....
> 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)/*'
The tape drive isn't found anyplace there.
> 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!
I suppose I could swap the Tape and Disk drive IDs, when I get the
chance to....
--
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 22.04.2004 07:55:47 von Keith Morse
On Wed, 21 Apr 2004, Kevin J. Cummings wrote:
> The tape drive isn't found anyplace there.
>
> > 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!
>
> I suppose I could swap the Tape and Disk drive IDs, when I get the
> chance to....
>
Very odd indeed. And I would suggest putting the devices on the chain one
at a time if possible and see what happens when you boot.
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux aic7xxx driver doesn"t see my tape drive
am 20.05.2004 03:02:17 von cummings
Well, I finally upgraded to Fedora Core 2 yesterday. Surprise! I can
now see my tape drive again.... Nothing has changed as far as I can
tell hardware-wise, in fact, I haven't even powered the system off....
Oh well. Chaulk another one up to development software....
Thanks to everyone who offered help!
--
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html