Date: Sun, 27 Feb 2000 10:50:48 +1030 From: Greg Lehey <grog@lemis.com> To: "Kenneth D. Merry" <ken@kdm.org> Cc: "Walter A. Roberts" <wroberts@med.wayne.edu>, freebsd-scsi@FreeBSD.ORG Subject: Re: Fw: Adaptec 1542c and Exabyte 8200/tar: Device not config Message-ID: <20000227105047.C39462@freebie.lemis.com> In-Reply-To: <20000225125543.A48858@panzer.kdm.org> References: <004301bf7f15$5a0e7180$986f4acf@walt> <20000225125543.A48858@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 25 February 2000 at 12:55:43 -0700, Kenneth D. Merry wrote: > On Thu, Feb 24, 2000 at 17:20:19 -0500, Walter A. Roberts wrote: >> Dear folks: >> >> I was referred to this list for possible help on the problems with a recent >> installation of 3.2 BSD related to a need for SCSI. I swapped out my >> adaptec 1502 cheapie for a 1542c since the CAM drivers don't support the >> 1502 and I had the 1542c on the shelf, thinking this would be easy. Sigh. >> >> I would be willing to write a driver for the 1502, but I've never written >> UNIX drivers, just VMS drivers so I'm not sure how steep the learning curve >> would be, but if any of you'd be willing to coach a little I could give it a >> whack. > > FreeBSD 3.4 and FreeBSD-current have a driver for the AIC-6260 and 6360 > chips that are on the 1502, so you don't need to write a driver. :) > >> I mainly (actually only) need the scsi on the UNIX side to read a tar file >> off an EXABYTE EXB-8200 scsi drive. If there's no hope for the present >> situation, if anyone knew of a way to get the stuff on the MS side onto >> other media (via the 1502/EXB), without a lot of contortions that would work >> too, although I know this part is way off the track of this list. >> >> Thanks for any help you can be. Technical details follow. > > It should be possible to use an Exabyte 8200. They're known to be rather > cantankerous, though. I have a couple of 8200s which don't work on current versions of FreeBSD. They have a marginally different command set which doesn't understand certain basic SCSI commands; they probe like this: sa1 at sym0 bus 0 target 5 lun 0 sa1: <EXABYTE EXB-8200 254A> Removable Sequential Access SCSI-CCS device sa1: 3.300MB/s transfers The microcode revision (254A) is the key here. They don't understand mode sense correctly, so just about any attempt to access them gives the messages: Feb 27 10:46:48 panic /kernel: (sa1:sym0:0:5:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 Feb 27 10:46:48 panic /kernel: (sa1:sym0:0:5:0): ILLEGAL REQUEST info?:1fff Don't worry about the "panic": that's the name of my test machine :-) >>>> Problem: Swapped ADAPTEC 1502 out to use ADAPTEC 1542C after installing >>>> 3.3.x and can't get tar (or mount or mt) to access the EXABYTE 8200 >>>> (scsi device 4) to read the device. >>>> >>>> History: Since no device drivers appeared to be available for the 1502 >>>> and I have tarred stuff on 8 mm (DEC ULTRIX tarred files), I tried to >>>> install the AHA-1542C board and an EXABYE-8200 (taken from the VAX) to >>>> read the files. >>>> >>>> The AHA installed and appeared to be properly identified by FreeBSD at >>>> all the right spots. During boot it tickled the exabyte numerous times >>>> (slowly), and came up fine. That's the Exabyte that's being slow. They take forever to load and get started. >>>> Camcontrol dev will show the aha1542 device on scbus0 but no devices. >>>> Camcontrol periph will show the aha1542 likewise. >>>> Camcontrol scan will then show the exabyte-8200 and hangs at this >>>> point. Kill -9 won't make this process go away. Only reboot does. > > Does camcontrol rescan hang the whole system, or is it just that process > that is hung, or what? I haven't seen this on any combination I've tried. >> scbus0 on aha0 bus 0: >> <EXABYTE EXB-8200 425A> at scbus0 target 0 lun 0 (probe0) >> < > at scbus0 target -1 lun -1 () It's possible that this microcode version will be OK. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000227105047.C39462>