From owner-freebsd-questions Mon Jun 12 15:13:17 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bart.callnet0800.com (bart.callnet0800.com [212.67.128.108]) by hub.freebsd.org (Postfix) with ESMTP id 1FBA637B5AF for ; Mon, 12 Jun 2000 15:13:10 -0700 (PDT) (envelope-from Ian@tirnanog.org) Received: from smtp.f1racing.co.uk [212.67.128.141] by bart.callnet0800.com with ESMTP (SMTPD32-5.05) id A09921E018E; Mon, 12 Jun 2000 23:13:45 +0100 Received: from unknown [212.67.148.179] by smtp.f1racing.co.uk (SMTPD32-5.05) id A06A32DD0050; Mon, 12 Jun 2000 23:12:58 +0100 From: Ian J Greely To: Adam Pendleton Cc: freebsd-questions@freebsd.org Subject: Re: Old DMA problems? Date: Mon, 12 Jun 2000 23:10:33 +0100 Message-ID: <4lnakso55vnkd4bjn5r3el0c8lbsg9lv2b@4ax.com> References: In-Reply-To: X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The ata device under 4 sometimes has this problem. (I have it on my main box and have gone back to 3.4). The only way to force the device to use pio is with the sysctl command. Unfortunately you can't do this before an install so, if the install itself is failing, there is nothing you can do about it unless the bios on your machine allows you to diable dma mode access to the device. If the problem is after install a sysctl atamodes.ht=3Dpio,pio,pio,pio (check the man pages) will force all devices on both IDE controllers to run in the PIO mode only. There will be a signifcant performance hit associated with this over normal DMA mode working. There are no flags accepted by this device. regards, Ian On Mon, 12 Jun 2000 11:53:53 -0400, you wrote: >I was looking through the archives, because I know this problem has come= up >before, but I couldn't find a solution in any of the articles. My = problem >is this. When performing the 4.0-RELEASE installation from the ISO = image, I >get through all the package selection, disk partitioning, etc. setup, = but >when it comes time to actually perform the disk formatting I get this = error >on the error console: > >ad0: WRITE command timeout - resetting >at0: [attempting?] resetting devices > >How can I correct this? Is it necessary to turn of DMA, and if so, how = do I >do that, and what is the penalty for doing that? This is an AMD K6, = with a >generic hard drive. > > > >Adam H. Pendleton >Security Engineer >VGS, Inc. >Fairfax, Virginia=20 > >Si hoc legere scis nimium eruditionis habes. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message