With a Buslogic (Mylex) BT-958 scsi adapter, my Exabyte 8200 8mm tape drive fails. With an Adaptec 2940uw, that same 8mm tape drive works well. I merely switched scsi adapters on the same P2B motherboard of my computer, using the same kernel and modules. I want to use the Buslogic adapter with my Exabyte 8200 tape drive, so I WELCOME ANY SUGGESTIONS TO DO THIS.
Here are some more details. I run kernel version 2.0.34 with some of the following kernel parameters CONFIG_BLK_DEV_SD=y #scsi disk support CONFIG_CHR_DEV_ST=y #scsi tape support CONFIG_BLK_DEV_SR=y CONFIG_CHR_DEV_SG=y # CONFIG_SCSI_MULTI_LUN is not set CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_AIC7XXX=y #for Adaptec CONFIG_AIC7XXX_PROC_STATS=y #for Adaptec CONFIG_AIC7XXX_RESET_DELAY=15 #for Adaptec CONFIG_SCSI_BUSLOGIC=y #for Buslogic CONFIG_SCSI_OMIT_FLASHPOINT=y #for Buslogic Here is my Buslogic scsi bus diagram: Fujitsu wide-ultra-scsi disk drive (id 0) --> Buslogic BT-958 scsi adapter card (id 7) --> 68pin-50pin (terminating empty pins; from Granite Digital) --> Exabyte 8200 8mm tape drive (id 5) --> active terminator externally on the tape drive On the Buslogic card, at boot, I have NOT invoked ultra scsi; the Fujitsu is set to negotiate at 20MB, wide, scsi-id 0; the Exabyte is set to negotiate asynchronously, on disconnection, off wide-negotiation, off motor-spin-up, on Bios-scan, scsi-id 5. Other general Buslogic settings are on cd-rom-boot-support, 0 boot-hard-disk-scsi-id, on bios-support-for-1-GB+, on bios-support-for-2+ hdd, disable isa-compatible-port, on scsi-parity-detection, off scam-mode, auto termination, on enable-bios-scan. On booting, with the kernel option "BusLogic=TraceErrors" I see 8656 successive sets of the following three lines: Dec 13 23:47:17 rabbit kernel: scsi0: CCB #10069 Target 5: \ Result 8 Host Adapter Status 00 Target Status 08 Dec 13 23:47:17 rabbit kernel: scsi0: CDB 00 00 00 00 00 00 Dec 13 23:47:17 rabbit kernel: scsi0: \ Sense 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I suspect these are benign errors, reflecting the old age of my Exabyte drive's protocols, but I am largely ignorant about their meaning. When I try using "dump", I get the following response: rabbit# /sbin/dump 0uBf 2500000 /dev/nst0 /usr/lib/tripwire DUMP: Date of this level 0 dump: Sun Dec 13 23:45:16 1998 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/sda1 (/usr/lib/tripwire) to /dev/nst0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 23865 tape blocks on 0.01 tape(s). DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] ** DUMP: End of tape detected #The Adaptec would not do this. DUMP: Closing /dev/nst0 Simultaneously, in /var/log/syslog, I get the following messages: ** Dec 14 00:21:52 rabbit kernel: scsi : aborting command due to timeout\ : pid 14855, scsi0, channel 0, id 0, lun 0 Write (6) 02 34 d9 04 00 Dec 14 00:21:52 rabbit kernel: scsi0: Aborting CCB #17835 to Target 0 Dec 14 00:21:53 rabbit kernel: SCSI host 0 abort (pid 14855) timed out \ - resetting Dec 14 00:21:53 rabbit kernel: SCSI bus is being reset for host 0 channel 0. Dec 14 00:21:53 rabbit kernel: scsi0: Sending Bus Device Reset \ CCB #17837 to Target 0 Dec 14 00:21:54 rabbit kernel: SCSI host 0 channel 0 reset \ (pid 14855) timed out - trying harder Dec 14 00:21:54 rabbit kernel: SCSI bus is being reset for host 0 channel 0. Dec 14 00:21:54 rabbit kernel: scsi0: Resetting BusLogic BT-958 \ due to Target 0 Dec 14 00:21:54 rabbit kernel: scsi0: *** BusLogic BT-958 \ Initialized Successfully *** Dec 14 00:21:56 rabbit kernel: scsi0: CCB #17838 Target 5: \ Result 2 Host Adapter Status 00 Target Status 02 Dec 14 00:21:56 rabbit kernel: scsi0: CDB 0A 01 00 00 1E 00 Dec 14 00:21:56 rabbit kernel: scsi0: Sense 70 00 06 00 00 00 \ 00 12 00 00 00 00 00 00 00 00 . . . Dec 14 00:21:56 rabbit kernel: st0: Error with sense data: \ extra data not valid Current error st09:00: sense key Unit Attention . . . WATCHING MY EXTERNAL EXABYTE DRIVE, I SEE ITS YELLOW LIGHT STAY ON (NO FLASHING AS FOR WRITING) FOR 25 SECONDS. I PRESUME MY TAPE DRIVE HAS MOVED FORWARD, and might infer that it has somehow gotten the wrong signal. If I use tar (rather than dump) on my tape drive, I get a response like rabbit: tar -cvf /dev/nst0 /usr/lib/tripwire tar: Removing leading `/' from absolute path names in the archive usr/lib/tripwire/ usr/lib/tripwire/tripwire usr/lib/tripwire/databases/ usr/lib/tripwire/databases/tw.db_rabbit.burtnet ** tar: Cannot write to /dev/nst0: Input/output error tar: Error is not recoverable: exiting now -- Jim Burt, NJ9L, Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.mnsinc.com/jameson [EMAIL PROTECTED] (703) 235-5213 ext. 132 (work) "A poor man associating with a rich man will soon be too poor to buy even a pair of breeches." --Chinese Proverb