From owner-freebsd-questions Fri Nov 24 6:24:53 2000 Delivered-To: freebsd-questions@freebsd.org Received: from droid.nosc.mil (droid.nosc.mil [128.49.4.117]) by hub.freebsd.org (Postfix) with ESMTP id 6C8A837B479 for ; Fri, 24 Nov 2000 06:24:51 -0800 (PST) Received: from slartibartfast.nosc.mil (slartibartfast.nosc.mil [198.253.21.36]) by droid.nosc.mil (8.11.0/8.11.0) with ESMTP id eAOEP3p11495; Fri, 24 Nov 2000 06:25:03 -0800 (PST) Message-Id: <4.3.2.7.2.20001124091604.00ad7d60@localhost> X-Sender: huck@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 24 Nov 2000 09:24:38 -0500 To: "Aistis Zenkevicius" , From: Craig Huckabee Subject: Re: UDMA ICRC READ ERRORs In-Reply-To: <001001c0556d$e0326850$9b00a8c0@admin> References: <20001123163615.22055.qmail@web108.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:53 PM 11/23/00 +0100, Aistis Zenkevicius wrote: >hi all, > > > > I've got the same problem with 4.2-BETA and an AMD > > > K6/2 500Mhz box, built > > > with an ASUS P5A, and a Western Digital hard drive. > > > I searched the mailing > > > list archives and found this fix : > > > > > > /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio > >don't want to get onto someones nerves, but is it a "solution" ??? It is a work around for what appears to be a problem with a particular combination of specific brands or models of hard drives and specific brands of ATAPI controllers. It is not a solution. Possible solutions would be (IMHO) to fix the ata driver so that it works with this combination (if possible), or augment the driver so it recognizes this type of problem and backs off to pio mode on its own, or compile a list of broken hardware, add that list to a FAQ, and have the millions of users to complain to the manufacturers to fix their hardware (I am assuming it is fixable). >where's the normal support for udma-66 ? udma works fine with other combinations of hardware - as I stated in my reply I have two systems now running 4.2 (using different hard drives) that are working just fine. --Craig ------------------------------------------------------- Craig Huckabee huck@spawar.navy.mil Systems Engineer, Compliance Corporation (843) 218 6459 SPAWAR Systems Center - Charleston, Charleston, SC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message