Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!tfs.com!julian
From: julian@tfs.com (Julian Elischer)
Subject: Re: AHA1540A-PERTEC tape problem
Message-ID: <Cu4xp9.9yG@tfs.com>
Organization: TRW Financial Systems, Oakland, CA
References: <320bqg$8nf@pith.uoregon.edu> <Cu4ww4.9LL@tfs.com>
Distribution: na
Date: Sat, 6 Aug 1994 22:41:33 GMT
Lines: 77
Something went terribly wrong in my response to this mail..
I include the corrected response:
In article <320bqg$8nf@pith.uoregon.edu>,
mike hoffman <mike@lutefisk.uoregon.edu> wrote:
>I have have not been able to read and/or write to my 1/2 tapedrive
>using FreeBSD 1.1.5.1R. . The board, converter and tapedrive
>worked fine under 386BSD so I think the 'problem' lies in the
>new operating system (drivers?).
> Viper 60 Cart tape ( works OK)
> NCR ADP-53 SCSI to PERTEC tape controller --> CIPHER F880 1/2 tape
>It appears the scsi tape drivers were changed from 386bsd to FreeBSD.
Oh dear oh dear.. :-)
well yes they were massively rewritten.
if SCSI_DEBUG option is used in the kernel, then you can use the
scsi(1) command to turn on massive debugging on that device, and
get a exact dump of which command is failing...
then You might add a "quirk" entry in the tape driver to dissable the
issuing of that command if your particular drive is found.
The tape driver has the facility to tailor it's behaviour to a small extent
depending on the found device.
so look at /sys/scsi/st.c, and
check out the man pages for st(1) st(4) scsi(1) scsi(4).
>
>I have configured the kernel with st0 for cart, and st1 for 1/2 inch
>also sd0 for luck.
well, that shouldn't make any differnce.
>
>When booting the devices are found, both st0 and st1.
>aha0 targ 1 lun 0: <unknownunknown????>
>st1: such and old device is a known rogue
>st1: density code 0x2, 512-byte blocks, write-protected
>(The tape in the drive has no write ring in it so the 'write protected' is
>correct. 0x2 converts to 1600bpi , also correct)
ah well, you see there is already a quirk entry for old devices, and maybe
it should be extended to disable whatever configuration command is failing..
(much better idea than to make a new one? I don't know.. your call.)
>
>Aug 6 16:04:49 scrooge /386bsd: st1(aha0:1:0): timed out
>st1(aha0:1:0): not ready
>st1: Cannot set selected mode Present Mode: Density = 0x2, Blocksize = 512
looks like teh default mode will do just fine, so maybe we can
just disable the mode setting command....
>bytes
>
>Any other operation has the same results.
>It appears that the first command sent is not to the liking of the 1/2
>tape drive. (it used to like them!) After getting one it does not like
>nothing else gets thru.
>
>Any thoughts etc???
>
>
>Mail address mike@scrooge.uoregon.edu
julian
+----------------------------------+ ______ _ __
| __--_|\ Julian Elischer | \ U \/ / On assignment
| / \ julian@tfs.com +------>x USA \ in a very strange
| ( OZ ) 300 lakeside Dr. oakland CA. \___ ___ | country !
+- X_.---._/ USA+(510) 645-3137(wk) \_/ \\
v