From owner-freebsd-questions Thu Feb 27 0:43:34 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3FAD37B489 for ; Thu, 27 Feb 2003 00:43:31 -0800 (PST) Received: from apollo.laserfence.net (apollo.laserfence.net [196.44.69.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id B029743F85 for ; Thu, 27 Feb 2003 00:43:29 -0800 (PST) (envelope-from will@unfoldings.net) Received: from localhost ([127.0.0.1]) by apollo.laserfence.net with esmtp (Exim 4.10) id 18oJdW-0007kt-00; Thu, 27 Feb 2003 10:43:26 +0200 Received: from prometheus-p0.datel.laserfence.net ([192.168.255.1] helo=prometheus.home.laserfence.net) by apollo.laserfence.net with esmtp (Exim 4.10) id 18oJdH-0007km-00; Thu, 27 Feb 2003 10:43:12 +0200 Received: from phoenix.home.laserfence.net ([192.168.0.2]) by prometheus.home.laserfence.net with esmtp (Exim 4.10) id 18oJdD-0009uL-00; Thu, 27 Feb 2003 10:43:07 +0200 Received: from will by phoenix.home.laserfence.net with local (Exim 4.10) id 18oJdC-0006Ln-00; Thu, 27 Feb 2003 10:43:06 +0200 From: Willie Viljoen To: Len Conrad , freebsd-questions@freebsd.org Subject: Re: can't get to ATA133 Date: Thu, 27 Feb 2003 10:43:05 +0200 User-Agent: KMail/1.5 References: <5.2.0.9.0.20030226165710.028ad2f0@mail.go2france.com> <5.2.0.9.0.20030227022946.07db1e40@mail.go2france.com> In-Reply-To: <5.2.0.9.0.20030227022946.07db1e40@mail.go2france.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200302271043.05919.will@unfoldings.net> X-Spam-Score: (/) X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *18oJdH-0007km-00*WGCNfyRgMDQ* X-Virus-Scanned: by AMaViS snapshot-20020422 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday 27 February 2003 10:31, someone, possibly Len Conrad, typed: > >The ata driver is quite strict on standards implementation. It could be > > that the promise cables may not comply as strictly with the standard as > > it would prefer. Try getting 80-conductor cables from a third party. > > Generally speaking, buying your own cables is better than using the > > ones that came with the controller anyway, as those are usually > > el-cheapos, even with the most expensive controllers. > > One unreported point we later verified was in the TX2000 on-board setup > util, "Show Drive Status" shows both drives as mode "U6" (is ATA133). Won't matter to ata(4), if it doesn't like your cables, it will force your drives down to UDMA2 at boot time. It could be that the cables still have abit more noise than the driver is willing to tolerate. A new set of cables won't cost you more than $5 each, try replacing the cables first. The 80-conductor cables that came with my sister's motherboard and with my offboard ATA controller (CMD 649 variant) were both 80-conductor cables by the manufacturors' claims, but ata(4) was not interested. Will -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) will@unfoldings.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message