Date: Thu, 27 Feb 2003 11:36:08 +0200 From: Willie Viljoen <will@unfoldings.net> To: Soeren Schmidt <sos@spider.deepcore.dk> Cc: Len Conrad <LConrad@Go2France.com>, freebsd-questions@freebsd.org Subject: Re: can't get to ATA133 (Addendum to previous post) Message-ID: <200302271136.08077.will@unfoldings.net> In-Reply-To: <200302270930.h1R9UqOc087155@spider.deepcore.dk> References: <200302270930.h1R9UqOc087155@spider.deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200302271136.08077.will>