From owner-freebsd-current Mon May 8 0:44:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B9DDA37B8BA for ; Mon, 8 May 2000 00:44:11 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA52151; Mon, 8 May 2000 09:44:07 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200005080744.JAA52151@freebsd.dk> Subject: Re: Abit BP6 - UDMA66 and non IBM disks In-Reply-To: <20000508001820.A308@sharmas.dhs.org> from Arun Sharma at "May 8, 2000 00:18:20 am" To: adsharma@sharmas.dhs.org (Arun Sharma) Date: Mon, 8 May 2000 09:44:07 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG (FreeBSD Current) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Arun Sharma wrote: > I have the following disk: > ad4: 9787MB [19885/16/63] at ata2-master using UDMA33 > and am experiencing hangs when I run it with UDMA66. That exact disk model cant do UDMA66 reliably, even Linux has it on the blacklist in the driver.... > I read the threads from Feb, where it was said that non IBM disks > had problems with the UDMA66 code in FreeBSD. Some of you said that > the disks worked just fine with other OSes. Not all non IBM disks has problems, that was not the message back then, at least not from me. What I said, and still says, is that Maxtor and WDC has a bad reputation on making drives that can't work reliably with UDMA66, quantum has its share too but not so bad. IBM's on the other hand works as expected... > I'd like to know if there has been a change in status of the UDMA66 > code. Not really, and it wont solve your particular problem, you should just run that disk as UDMA33 and it should work... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message