From owner-aic7xxx Thu May 18 16:13:56 2000 Delivered-To: aic7xxx@freebsd.org Received: from devserv.devel.redhat.com (devserv.devel.redhat.com [207.175.42.156]) by hub.freebsd.org (Postfix) with ESMTP id 47AA637B912 for ; Thu, 18 May 2000 16:13:54 -0700 (PDT) (envelope-from dledford@redhat.com) Received: from localhost (dledford@localhost) by devserv.devel.redhat.com (8.9.3/8.9.3) with ESMTP id TAA17852; Thu, 18 May 2000 19:12:35 -0400 X-Authentication-Warning: devserv.devel.redhat.com: dledford owned process doing -bs Date: Thu, 18 May 2000 19:12:35 -0400 (EDT) From: Doug Ledford X-Sender: dledford@devserv.devel.redhat.com To: pk@physicist.net Cc: aic7xxx@FreeBSD.ORG Subject: Re: Adaptec 29160N In-Reply-To: <000518175926CV.10768@weba3.iname.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 18 May 2000 pk@physicist.net wrote: > Please excuse me for having been offtopic. Just thought I should let > anyone interested know that my problem with the 29160N stems from the > cabling & the terminator, which I've stated below, but there actually > wasn't anything wrong with the cable or the active terminator; it just > was the wrong type of cable and terminator. Apparently an lvd cable & > active terminator isn't enough for ultra 160, you need special ultra > 160 lvd cable & active terminator... If anyone's interested. So my > problem with the card detecting the drive's capabilities at boot is > solved; now I've got another "problem": Why does the driver report > 80Mb/sec when the card reports 160Mb/sec at boot? Because there is a bug in the sequencer code, and I force Quantum Atlas IV and later drives that support 160 mode into 80 mode in order to get around the bug. The problem is that they will generate occasional bus resets under load. When I have a sequencer that fixes the problem, then the drives will run at 160 mode again. > > However there's still one questions remaining: What is the sequencer > code for (what does it do?)? It handles the low level protocol communications between the controller card and the devices and it also is responsible for the majority of the communications between the card and the kernel level driver. -- Doug Ledford Opinions expressed are my own, but they should be everybody's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message