looks like Catalyst 9.2beta leaked.

[legume]

It is enabled...

Strange - does the framerate if you run glxgears = your refresh rate?

I guess running out of CPU or double rate deinterlacing so framerate = refresh rate could also mess it up.

[legume]

Speaking of Vsync. Do any of the options work for you guys (on any driver version)? For me, the controls either force vsync on globally or force it off globally. The in between options (off/on unless specified) don't work as intended.

That's what I see as well

[legume]

Actually I seem to get a similarly good result with xine witn opengl - or maybe my eyes are starting to fail me from staring at the screen too close for too long.

Cool - I haven't tried xine, so I don't know what it's gl is like WRT CPU usage (eg it may do color space conversion in software, whereas the yuv=4 option uses GPU).

It doesn't really matter for SD mpeg2, but if you want to play HD h264 and have an older CPU like mine then it can make a difference. If you are scaling small res file to a large res display with mplayer you can also try bicubic rather than bilinear with lscale=1.

[nstamoul0]

One kinda off-topic question.

I have a debian/sid setup running the latest 2.6.26 kernel.The only way I can get new drivers to run (outside my repo) is to compile a new kernel (because of the flush tlb page bug).

Anybody know a way around this (besides compiling a new kernel ?).

[Vighy]

One kinda off-topic question.

I have a debian/sid setup running the latest 2.6.26 kernel.The only way I can get new drivers to run (outside my repo) is to compile a new kernel (because of the flush tlb page bug).

Anybody know a way around this (besides compiling a new kernel ?).

change distro.

[the-me]

One kinda off-topic question.

I have a debian/sid setup running the latest 2.6.26 kernel.The only way I can get new drivers to run (outside my repo) is to compile a new kernel (because of the flush tlb page bug).

Anybody know a way around this (besides compiling a new kernel ?).

8-12-4 is in Debian Sid now, which does not have this issue.

[nstamoul0]

change distro.

When hell frezes over

I'm already back to 8.12

[Vighy]

When hell frezes over

I'm already back to 8.12

so unstable to be not worth-trying? I will peacefully wait for 9-01 then...

...when it will ever arrive

[Boerkel]

Strange - does the framerate if you run glxgears = your refresh rate?

I guess running out of CPU or double rate deinterlacing so framerate = refresh rate could also mess it up.

Yes glxgears = refresh rate :
301 frames in 5.0 seconds = 60.195 FPS
301 frames in 5.0 seconds = 60.066 FPS

I don't think CPU is a problem. I've got a 2x2.0 GHz Turion and CPU-usage is far below 100%. So there must be another reason for this strange "tearing-line". I really don't know why this happens...

[biasquez]

(EE) Failed to load module "fglrx" (module requirement mismatch, 0)

error with jaunty (doesn't detect xorg 7.4)

driver support jaunty (infact Ubuntu/Jaunty is present in --listpkg and --buildpkg Ubuntu/Jaunty compile without error)