From owner-freebsd-questions Wed Mar 14 11:30:10 2001 Delivered-To: freebsd-questions@freebsd.org Received: from funkthat.com (mg128-084.ricochet.net [204.179.128.84]) by hub.freebsd.org (Postfix) with ESMTP id 2C9D237B718; Wed, 14 Mar 2001 11:30:03 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by funkthat.com (8.11.1/8.8.7) id f2EJTaZ20293; Wed, 14 Mar 2001 11:29:36 -0800 (PST) Message-ID: <20010314112930.36100@hydrogen.funkthat.com> Date: Wed, 14 Mar 2001 11:29:30 -0800 From: John-Mark Gurney To: kstewart@urx.com Cc: freebsd-questions@freebsd.org Subject: Re: 4.2-R installer bombs because I can't turn UDMA off... References: <20010313233604.59613@hydrogen.funkthat.com> <3AAF3125.6153EA6B@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <3AAF3125.6153EA6B@urx.com>; from Kent Stewart on Wed, Mar 14, 2001 at 12:51:49AM -0800 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart scribbled this message on Mar 14: > John-Mark Gurney wrote: > > > > Well, I'm looking for a way to turn off UDMA under 4.2-R. I have a > > PA-2007 motherboard, and if I have UDMA enabled on the IDE controler, FICA ^ (it's using a VIA VT82C586A south brige chip) > > the system has problems. With pre-4.x systems, this wasn't a problem, > > but I do not see any documentation on how to turn off UDMA in 4.2-R. > > What kind of HD's do you have. Both Western Digital and Maxtor have > programs that will setup their HD's up to only work at lower rates. It's a seagate.. > Once you get 4.2 installed, you can add a sysctl for hw.atamodes and > set them to pio mode in /etc/sysctl.con. The Promise Ultra 66 > controller pci card also works on my system with a similar problem. but how do I know that when booting (between the time the kernel starts init and /etc/sysctl.con gets read) that I won't get corrupted data?? This needs to be done at the kernel initalization time, and NO later... you can't risk having a boot fail.. what happens if the machine drops to shell because of a bad reading durning fsck?? -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "Thank God I'm an atheist, that'd just be confusing." -- cmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message