From owner-freebsd-scsi Sun May 7 18:18:46 1995 Return-Path: freebsd-scsi-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA13849 for freebsd-scsi-outgoing; Sun, 7 May 1995 18:18:46 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA13831 for ; Sun, 7 May 1995 18:18:43 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <17739-0@bunyip.cc.uq.oz.au>; Mon, 8 May 1995 11:18:15 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id LAA10945; Mon, 8 May 1995 11:21:42 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id BAA10175; Mon, 8 May 1995 01:20:44 GMT Message-Id: <199505080120.BAA10175@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6 4/21/95 To: Dominic Gregoire cc: freebsd-scsi@FreeBSD.org Subject: Re: tmc8xx driver from 2.0 In-reply-to: Your message of "Sun, 07 May 1995 20:46:17 -0400." <199505080046.UAA18933@biko.llc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 May 1995 11:20:43 +1000 From: Stephen Hocking Sender: freebsd-scsi-owner@FreeBSD.org Precedence: bulk > I think i'll hit the right place with this. > > I've been trying for a few days to make freebsd2-0 works with a TMC-830 > 8bit scsi adaptor, using i386/isa/seagate.c. So far i've been able to > make autodetect works, it also detects all the present devices, and i'm > able to read/write to them. All i had to do was to add a signature to > seagate.c and recompile (The bios version on it is 4.0L, 5.0C was the > oldest in the sources). > > The problem is, it timeouts ALOT, and eventually panics and crash. I > tried everything i could think of, like the fix for tmc840 adaptor > (flipping defs for STAT_MSG and STAT_CD and forcing seagate type), i > played around a lot with scsi terminators, and on and on. Try commenting out the #defines for SEA_BLINDTRANSFER and SEA_ASSEMBLER. That worked for me on a Future Domain TMC-885, which experienced the exact symptoms you've described. I'm trying to put these options in the current version of the driver, so that I can submit the changes back and use it. I'm still trying to figure out (in between all the other stuff I have to do) where it would all go. > > Maybe someone here had the same level of troubles with a tmc-830, and > could help me. Maybe someone with scsi experience can tell me "It could > work if you do xxx", or "Just ditch it", whatever. > > Just any enlightement will do :) > > -- > Dominic_Gregoire@LLC.org : I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that!