From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 11:52:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90DA216A4CE for ; Sun, 11 Jul 2004 11:52:33 +0000 (GMT) Received: from mout2.freenet.de (mout2.freenet.de [194.97.50.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6014D43D31 for ; Sun, 11 Jul 2004 11:52:33 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from [194.97.55.190] (helo=mx6.freenet.de) by mout2.freenet.de with asmtp (Exim 4.390) id 1Bjcsg-0003Nw-4h; Sun, 11 Jul 2004 13:52:30 +0200 Received: from dff3b.d.pppool.de ([80.184.255.59] helo=peedub.jennejohn.org) by mx6.freenet.de with esmtp (TLSv1:AES256-SHA:256) (Exim 4.34 #3) id 1Bjcsf-0001yk-JR; Sun, 11 Jul 2004 13:52:30 +0200 Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.11/8.11.6) with ESMTP id i6BBqRdd015659; Sun, 11 Jul 2004 13:52:27 +0200 (CEST) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200407111152.i6BBqRdd015659@peedub.jennejohn.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: sos@DeepCore.dk In-Reply-To: Message from =?ISO-8859-1?Q?S=F8ren_Schmidt?= of "Sat, 10 Jul 2004 12:05:39 +0200." <40EFBF73.9080904@DeepCore.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Jul 2004 13:52:27 +0200 From: Gary Jennejohn X-Mailman-Approved-At: Sun, 11 Jul 2004 12:33:06 +0000 cc: Ion-Mihai Tetcu cc: Divacky Roman cc: current@FreeBSD.org Subject: Re: via 8237 and above-udma33 problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 11:52:33 -0000 =?ISO-8859-1?Q?S=F8ren_Schmidt?= writes: > Divacky Roman wrote: > >>>2) if not - how may I tell fbsd to initialize this drive (resp. the > >>>channel the drive is attached to) to udma33 instead of the default mode. > >>>I want to boot from that drive so I cannot use atacontrol or whatever > >>>since it would have hanged before I'd enter user-space system > >>>initialization > >> > >>Put hw.ata.ata_dma=0 > >>/boot/loader.conf > > > > > > I WANT dma! just not udma100 but udma33... so this is not what I want > > I think there should be some > > device.hints:dev.ata.adX.mode=blah > > You can just specify no dma in loader.conf and then use atacontrol to > set the wanted mode on each device later on in rc.local or whatever you > prefer... > Just a data point: On my amd64 system in 64-bit mode I had to define a bash alias to turn on DMA. Doing it in rc.local often resulted in so many DMA errors that the system hung. Probably due to the intense disk activity which happens during startup. Strangely enough, the same disk exhibits absolutely no DMA errors when I boot a 32-bit FreeBSD system. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de