=?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.deReceived on Sun Jul 11 2004 - 09:52:33 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:01 UTC