Date: Fri, 19 Nov 2004 09:41:13 -0600 From: Sean Welch <Sean_Welch@alum.wofford.org> To: Sean Farley <sean-freebsd@farley.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Strange DMA behavior under 5.3-RELEASE Message-ID: <20041119154113.GA3458@NitroPhys.welchsmnet.net> In-Reply-To: <20041118114008.H96597@thor.farley.org> References: <20041117160137.GA7243@NitroPhys.welchsmnet.net> <20041118114008.H96597@thor.farley.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 18, 2004 at 11:46:28AM -0600, Sean Farley wrote: > That is odd. I can see it happening on my old Dell PII. The sysctl > only enable DMA capability I believe. It is enabled by default. If you > disable it during boot, I would guess you would not be able to set WDMA2 > with atacontrol. At least I'm not the only one! You are correct about the sysctl (as far as I know). I tried removing it from the loader.conf file and after boot the value was still set correctly. The confusing bit is that we can set the speed using atacontrol but it doesn't get set at boot. > Also, I get from the Zip drive: > ata1-slave: FAILURE - SETFEATURES SET TRANSFER MODE status=1<ERROR> > error=4<ABORTED> I haven't seen this one. I think I'll turn on verbose booting and see if I see something similar from the DVD drive. I'll pop in the modular drive too to see if it gets set properly. Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041119154113.GA3458>