Re: Dvd,dvd,dvd...

[Mark Cullen <mark.r.cullen@xxxxxxxxx>]

Petr Janda wrote:
> Hi,
> I totally forgot about loader.conf, now the drive gets set to UDMA4 on 
> boot. Its strange, but mplayer still fails on UDMA4, although I can 
> mount the dvd no problem. So added the atacontrol command to rc.local.
>
> Im sure the drive can handle UDMA4 since I remember that in Linux this 
> drive worked perfect in UDMA66 + the manufacturer lists UDMA4 as a 
> supported mode as well.

You're right. I have the same drive and it works perfectly in Windows at 
UDMA4 / UDMA66. I don't actually have anything else to add but that, so 
I hope you get your problem solved.

> I havent been able to replicate the crash yet after a reboot, but if it 
> happens I'll let you know.
>
> Cheers
> Petr
>
>
> Joerg Sonnenberger wrote:
> > On Wed, Jul 19, 2006 at 01:09:21AM +1000, Petr Janda wrote:
> >  
> > > Mine is set to 0. SO I did sysctl hw.ata.atapi_dma=1 and it says:
> > >
> > > sysctl: oid 'hw.ata.atapi_dma' is read only
> > >
> > > Why is that?
> > >     
> >
> > It is a tunable as well, so set it in /boot/loader.conf.
> >
> >  
> > > atacontrol has shown me that the device was in PIO4, so I set it to 
> > > UDMA4 instead(which is what my drive should be using as it supports 
> > > it), but then my dvds couldnt be read so I tried UDMA2 and it 
> > > improved it heaps though not perfect, and it seems that mplayer seems 
> > > to crash more :S.
> > >     
> >
> > This is strange... Well, that the drive can't handle UDMA4 is not really
> > surprising, but you shouldn't see much issues with UDMA2.
> >
> > *How* does mplayer crash?
> >
> > Joerg
> >
> >
> >