From owner-freebsd-questions Thu Feb 27 1:36:45 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 C2A2E37B401 for ; Thu, 27 Feb 2003 01:36:43 -0800 (PST) Received: from apollo.laserfence.net (apollo.laserfence.net [196.44.69.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id C802543FB1 for ; Thu, 27 Feb 2003 01:36:41 -0800 (PST) (envelope-from will@unfoldings.net) Received: from localhost ([127.0.0.1]) by apollo.laserfence.net with esmtp (Exim 4.10) id 18oKSr-00084t-00; Thu, 27 Feb 2003 11:36:29 +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 18oKSb-00084m-00; Thu, 27 Feb 2003 11:36:14 +0200 Received: from phoenix.home.laserfence.net ([192.168.0.2]) by prometheus.home.laserfence.net with esmtp (Exim 4.10) id 18oKSX-000A3x-00; Thu, 27 Feb 2003 11:36:09 +0200 Received: from will by phoenix.home.laserfence.net with local (Exim 4.10) id 18oKSW-0006Rl-00; Thu, 27 Feb 2003 11:36:08 +0200 From: Willie Viljoen To: Soeren Schmidt Subject: Re: can't get to ATA133 (Addendum to previous post) Date: Thu, 27 Feb 2003 11:36:08 +0200 User-Agent: KMail/1.5 Cc: Len Conrad , freebsd-questions@freebsd.org References: <200302270930.h1R9UqOc087155@spider.deepcore.dk> In-Reply-To: <200302270930.h1R9UqOc087155@spider.deepcore.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200302271136.08077.will@unfoldings.net> X-Spam-Score: (/) X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *18oKSb-00084m-00*W6BHVtKZGPg* 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 11:30, someone, possibly Soeren Schmidt, typed: > > Strange, I was told 30cm emphatically by our local techie, but S=F8ren > > did write the driver, so he's probably more correct than my techie. My > > mistake > > > > :) > > Well, point him at the ATA specs :) It seems he was reading some manufacturor's "own version" of the specs, we= =20 just checked the official specs and you are right :) > > S=F8ren, what else could be causing this? On bootup, Len's system=20 complains: > > > ad4: DMA limited to UDMA33, non-ATA66 cable or device > > > ad6: DMA limited to UDMA33, non-ATA66 cable or device > > This is because the cblid bit in the disks indicate that the disk doesn't > see the right cable (or rather the right signals it tests for). > Since I dont have a dmesg from the system I dont know if there are other > devices on the cable than the disks, as the most usual culprit here is > an ATAPI device that doesn't like UDMA. Len, post dmesg? :) =2D-=20 Willie Viljoen =46reelance 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