[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Slow XVideo



Hi Michel
Direct hit! Thank you very much for spotting this out. When having the option 
"vga=785" in the kernel boot parameter, /proc/mtrr looked like:

reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
reg01: base=0x1e000000 ( 480MB), size=  32MB: uncachable, count=1
reg02: base=0xe0000000 (3584MB), size=   1MB: write-combining, count=1
reg03: base=0xe8000000 (3712MB), size=  64MB: write-combining, count=1

after removing "vga=785" from the kernel parameter list:

walser:~# cat /proc/mtrr 
reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
reg01: base=0x1e000000 ( 480MB), size=  32MB: uncachable, count=1
reg03: base=0xe8000000 (3712MB), size=  64MB: write-combining, count=1

In the XFree log the warning was gone and the CPU usage of the XServer dropped
massively that watching DVD works now :-)
Thank you very much for this invaluable hint,

Best regards, Markus


Am Freitag, 1. April 2005 17.42 schrieb Michel Dänzer:
> On Fri, 2005-04-01 at 00:56 +0200, Markus Walser wrote:
> > 
> > The problem I´m faced to is that the XFree server uses quite a lot of CPU time to
> > play a DVD even with XVideo. With this configuration the Xserver uses more than 
> > mplayer/xine itself to play a DVD. And in fullscreen it´s way to slow to play on
> > the 1GHz Efficeon CPU .
> 
> [...]
> 
> > (WW) RADEON(0): Failed to set up write-combining range (0xe0000000,0x1000000)
> 
> This is likely the problem because the X server copies the XVideo data
> to the framebuffer with the CPU. You're probably running vesafb or
> radeonfb in console, and it's setting up a conflicting partial MTRR
> region for the framebuffer? (A workaround for this was committed to
> X.org CVS HEAD recently)
> 
> 



Reply to: