From owner-freebsd-hardware Mon Aug 7 22:44:38 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id 4785C37B624 for ; Mon, 7 Aug 2000 22:44:30 -0700 (PDT) (envelope-from simon@optinet.com) Received: from sharky (adsl-151-202-97-90.bellatlantic.net [151.202.97.90]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id HAA51041 for ; Tue, 8 Aug 2000 07:13:26 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200008081313.HAA51041@mail.fpsn.net> From: "Simon" To: "freebsd-hardware@FreeBSD.ORG" Date: Tue, 08 Aug 2000 01:47:25 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: <200008081306.HAA51017@mail.fpsn.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: What happened? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oh, i see, it changes 1/0 bit to turn on/off write cache. changing it to 0, turns off write cache I suspect. But, Mike said there are issues with the firmware, why not just update it if latest one doesn't have the problem? won't that be better? -Simon On Tue, 08 Aug 2000 01:40:12 -0400, Simon wrote: >Alrighty, now, i'm totally confused. What will/should this do? as far as i can tell, it'll replace 1 with 0 on all lines that start >with WCE, but that doesn't mean anything to me. Also, what do you mean by a bad firmware? > >Thanks, >Simon > >On Mon, 7 Aug 2000 22:30:28 -0700, Paul Saab wrote: > >>Run this: >> >>EDITOR="/usr/bin/perl -i -pe 's/1/0/g if /^WCE/'" \ >>camcontrol modepage da0 -P 3 -m 8 >> >>do this for all your drives which have bad firmware. >> >>-- >>Paul Saab >>Technical Yahoo >>paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org >>Do You .. uhh .. Yahoo!? >> >>Simon (simon@optinet.com) wrote: >>> Great to here there is a fix :-) I have another seagate drive in the same box: >>> >>> da1 at ahc0 bus 0 target 1 lun 0 >>> da1: Fixed Direct Access SCSI-3 device >>> da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled >>> da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) >>> >>> Same problem I suspect. The drive is just bigger in size. What would you suggest as the best fix for this? can I just >>> update the firmware? or going with a different controller is better? I doubt i have write cache turned on as the drive >>> seems to work much slower creating empty files than 5.4k 40 gig IDE maxtor drive (creates 10,000 empty files 10x >faster >>> than the SCSI i got). Still not exactly sure why. >>> >>> Thanks again, >>> Simon >>> >>> On Mon, 07 Aug 2000 22:23:56 -0700, Mike Smith wrote: >>> >>> >> Here it is: >>> >> >>> >> da0 at ahc0 bus 0 target 0 lun 0 >>> >> da0: Fixed Direct Access SCSI-3 device >>> > ^^^^ >>> >This firmware is known to interact badly with the ahc driver. You have >>> >three options: >>> > >>> > - Use the Adaptec setup utility to disable write caching. >>> > - Use a different SCSI controller. >>> > - Get the firmware update from Seagate and fix the drive. >>> > >>> >-- >>> >... every activity meets with opposition, everyone who acts has his >>> >rivals and unfortunately opponents also. But not because people want >>> >to be opponents, rather because the tasks and relationships force >>> >people to take different points of view. [Dr. Fritz Todt] >>> > >>> > >>> > >>> >>> >>> >>> >>> >>> To Unsubscribe: send mail to majordomo@FreeBSD.org >>> with "unsubscribe freebsd-hardware" in the body of the message >> > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message