*BSD News Article 3913


Return to BSD News archive

Path: sserve!manuel!munnari.oz.au!mips!mips!swrinde!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!cis.ksu.edu!sxs
From: sxs@cis.ksu.edu (Spencer Smith)
Newsgroups: comp.unix.bsd
Subject: Re: Problems with SCSI tape 386BSD
Message-ID: <sxs.714260429@draconis.cis.ksu.edu.cis.ksu.edu>
Date: 19 Aug 92 21:29:39 GMT
References: <1992Aug19.073813.12145@NeoSoft.com>
Organization: Kansas State University
Lines: 27
NNTP-Posting-Host: draconis.cis.ksu.edu

karl@NeoSoft.com (Karl Lehenbauer) writes:

>When trying to write to an Exabyte EXB-8500 I get the following:

>as1a: controller error 0x12 writing fsbn 0-19
>scsi sense: 0 0 0 0 0 0 0 0 0 ...

the driver/or adapter is getting confused possibly by something
the exabyte is sending back. 
	
>Even with the tape as SCSI unit 1, it is not recognized in the boot probe.
>But on the first attempt to access it, it does probe it and announces
>an Exabyte 8500, etc.

Pace's device driver doesnt probe for the devices untill there
is an open call for them. Once it has it will remmber them. 

There is work on rewritting the SCSI decive driver, that should
help remove alot of the problems that people are having. Im getting
there but its taking a little work (theres some small differences
between mach and bsd).

So if anyone out there knows how to do phystov it might remove
a small hack in the new code (-:  vtophys isnt a problem (-:
 
Spencer
sxs@cis.ksu.edu