*BSD News Article 78042


Return to BSD News archive

Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!garlic.com!news.scruz.net!kithrup.com!news.Stanford.EDU!bloom-beacon.mit.edu!news.mathworks.com!news4.ner.bbnplanet.net!cpk-news-feed2.bbnplanet.com!cam-news-hub1.bbnplanet.com!howland.erols.net!netcom.com!rll
From: rll@netcom.com (Richard L. Lamb)
Subject: Re: SCSI Tape not working
Message-ID: <rllDxJ9KA.94B@netcom.com>
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
References: <5116q9$90d@uriah.heep.sax.de> <3234a838.44844395@news.insync.net> <rllDxHp4L.DK8@netcom.com>
Date: Tue, 10 Sep 1996 20:14:34 GMT
Lines: 59
Sender: rll@netcom20.netcom.com

I fixed it.  In my haste to reconfigure the Adaptec card to IRQ 10, I
didn't notice that _two_ different jumpers needed to be changed.
The tape works fine now.

In article <rllDxHp4L.DK8@netcom.com> rll@netcom.com (Richard L. Lamb) writes:
>I have a working 2.1 system that I'm trying to add a SCSI controller and
>tape to.  The system was previously all IDE.  I've installed an Adaptec
>1542B and a Tandberg 525MB QIC tape drive.  I've recompiled the kernel
>to include SCSI support, and both the adapter and tape drive are recognized
>at boot:
>
>aha0 at 0x330-0x333 irq 10 drq 5 on isa
>aha0 waiting for scsi devices to settle
>(aha0:4:0): "TANDBERG  TDC 3800 G03B" type 1 removable SCSI 1
>st0(aha0:4:0): Sequential-Access density code 0x0, 512-byte blocks, write-protected
>
>I've also run MAKEDEV st0:
>
>rlamb: {5} ls -l /dev/*st0*
>crw-r-----  2 root  operator   14,   2 Sep  9 15:30 /dev/erst0
>crw-r-----  2 root  operator   14,   2 Sep  9 15:30 /dev/erst0.0
>crw-r-----  1 root  operator   14,   6 Sep  9 15:30 /dev/erst0.1
>crw-r-----  1 root  operator   14,  10 Sep  9 15:30 /dev/erst0.2
>crw-r-----  1 root  operator   14,  14 Sep  9 15:30 /dev/erst0.3
>crw-r-----  2 root  operator   14,   1 Sep  9 15:30 /dev/nrst0
>crw-r-----  2 root  operator   14,   1 Sep  9 15:30 /dev/nrst0.0
>crw-r-----  1 root  operator   14,   5 Sep  9 15:30 /dev/nrst0.1
>crw-r-----  1 root  operator   14,   9 Sep  9 15:30 /dev/nrst0.2
>crw-r-----  1 root  operator   14,  13 Sep  9 15:30 /dev/nrst0.3
>crw-r-----  2 root  operator   14,   0 Sep  9 15:30 /dev/rst0
>crw-r-----  2 root  operator   14,   0 Sep  9 15:30 /dev/rst0.0
>crw-r-----  1 root  operator   14,   4 Sep  9 15:30 /dev/rst0.1
>crw-r-----  1 root  operator   14,   8 Sep  9 15:30 /dev/rst0.2
>crw-r-----  1 root  operator   14,  12 Sep  9 15:30 /dev/rst0.3
>crw-------  1 root  wheel      14, 536870912 Sep  9 15:30 /dev/rst0.ctl
>crw-rw----  1 root  operator   14,   3 Sep  9 15:30 /dev/st0ctl.0
>crw-rw----  1 root  operator   14,   7 Sep  9 15:30 /dev/st0ctl.1
>crw-rw----  1 root  operator   14,  11 Sep  9 15:30 /dev/st0ctl.2
>crw-rw----  1 root  operator   14,  15 Sep  9 15:30 /dev/st0ctl.3
>
>But any attempt to access the tape via tar or mt just hangs, and after
>a minute or so I get these messages:
>
>Sep  9 15:52:25 rlamb /kernel: st0(aha0:4:0): timed out 
>Sep  9 15:52:29 rlamb /kernel: st0(aha0:4:0): timed out  AGAIN
>Sep  9 15:54:09 rlamb /kernel: st0(aha0:4:0): timed out 
>Sep  9 15:54:13 rlamb /kernel: st0(aha0:4:0): timed out  AGAIN
>
>The tape drive does an automatic retension when a tape is inserted, so I
>don't think the drive is dead.  I've also substituted a Tandberg 150MB
>drive with the same result.  The Adaptec is SCSI ID 7, the tape is
>SCSI ID 4.  The bus is terminated properly.
>
>Any clues?
>
>Richard Lamb
>rll@netcom.com