From owner-freebsd-hardware Wed Jun 12 11:34:52 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from skink.ru.ac.za (skink.ru.ac.za [146.231.128.4]) by hub.freebsd.org (Postfix) with ESMTP id 7DB5237B400 for ; Wed, 12 Jun 2002 11:34:45 -0700 (PDT) Received: from bashir.dsl.ru.ac.za ([146.231.113.19] helo=rucus.ru.ac.za) by skink.ru.ac.za with esmtp (Exim 3.36 #1) id 17I5P1-0001dM-00; Wed, 12 Jun 2002 12:30:59 +0200 Message-ID: <3D0722E1.4090601@rucus.ru.ac.za> Date: Wed, 12 Jun 2002 12:30:57 +0200 From: =?ISO-8859-1?Q?David_Sieb=F6rger?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc1) Gecko/20020506 X-Accept-Language: en-za, en-gb, en-us, en MIME-Version: 1.0 To: will@highveldcs.com Cc: hardware@freebsd.org Subject: Re: Per-drive ATA configuration? (fwd) References: <20020612104259.H252-100000@phoenix.vh.laserfence.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-added-header: added by skink.ru.ac.za Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Willie Viljoen wrote: > I've recently set my system up in a rather perculiar way, the mainboard= > (an Asus P3V133) has an onboard ATA-66 controller of some VIA flavour. = I > have a CMD-469 ATA-100 controller lying around, which was needed to run= my > 40GB drive on an older motherboard. [snip] > I checked the ata(4) manpage, and they mentioned a sysctl called > hw.atamodes. This sysctl (aparently) allows for individual tuning of AT= A > parameters. However, to my great dismay, I discovered that this sysctl > does not exist on my system (FreeBSD 4.6-RC) It was removed when the new ATA RAID code was MFC'ed during 4.5-STABLE. > I've tried having sysctl display all its opaque variables, and this sys= ctl > still simply isn't there. I tried setting it from loader.conf asif it w= ere > a kernel tunable, again, to no avail. >=20 > Has this controle been removed from the ata driver? Or has it simply no= t > yet been implimented... On a recent system, you'll need to use atacontrol(8). I guess you'll=20 need to do something like 'atacontrol mode 0 pio4 pio4'. Though, personally, I would want to get rid of the old drive and I'd=20 run the newer drive on the UDMA66 controller. I doubt the performance=20 difference between UDMA66 and UDMA100 is significant, particularly=20 with a single drive on the channel. --=20 David Sieb=F6rger drs@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message