/dev/[*]st* does not work with EXBAYTE 8505 with 2.6 kernels

From: John Damm Sørensen
Date: Wed Aug 25 2004 - 01:29:50 EST


I have just upgraded from RH9 Linux 2.4 to FC2 Linux 2.6 and now my
EXABYTE 8505 no longer works.

If I try to access it with mt (using any device like nst0) I get no such
device error message. Same thing with stinit.

The tape drive is found during boot, as this snippet from dmesg shows:
qla1280: QLA12160 found on PCI bus 1, dev 8
ACPI: PCI interrupt 0000:01:08.0[A] -> GSI 11 (level, low) -> IRQ 11
scsi(1): Reading NVRAM
qla1280_isr(): index 1 asynchronous BUS_RESET
qla1280_isr(): index 0 asynchronous BUS_RESET
scsi(1:0): Resetting SCSI BUS
scsi(1:1): Resetting SCSI BUS
scsi1 : QLogic QLA12160 PCI to SCSI Host Adapter
Firmware version: 10.04.32, Driver version 3.24.3
Vendor: EXABYTE Model: EXB-85058SQANXR0 Rev: 0808
Type: Sequential-Access ANSI SCSI revision: 02
scsi(1:0:4:0): Sync: period 50, offset 14

cat of /proc/scsi/scsi also shows the tape device:
Attached devices:
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: COMPAQ Model: ST34371W Rev: 0682
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 04 Lun: 00
Vendor: SEAGATE Model: ST39103LW Rev: 0002
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 04 Lun: 00
Vendor: EXABYTE Model: EXB-85058SQANXR0 Rev: 0808
Type: Sequential-Access ANSI SCSI revision: 02

lsmod seems to contain the necessary driver modules as well:

Module Size Used by
st 30429 0
qlogicfas408 6473 0
parport_pc 21249 1
lp 9133 0
parport 35977 2 parport_pc,lp
md5 3905 1
ipv6 217349 16
autofs4 20677 0
sunrpc 141861 1
iptable_filter 2369 0
ip_tables 13889 1 iptable_filter
3c59x 33385 0
dm_mod 47317 0
button 4825 0
battery 7117 0
asus_acpi 9177 0
ac 3533 0
ext3 96937 4
jbd 66521 1 ext3
qla1280 81997 0
sd_mod 17473 5
scsi_mod 105360 3 st,qla1280,sd_mod

Any hints?
Please don't tell me that the 8505 is no longer supported.

Cheers
John



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/