AMD Catalyst 9.10 Released

[dgrafenhofer]

I just have had kernel-source, I installed the two other but its still the same.

Option 1: Trace down the missing dependency - check the respective log files (sorry I do not have time to do this)

Option 2 (aka brute force): Install all "relevant" development schemes (base, c/c++, kernel)

[Kano]

You need kernel headers only.

[shinigami]

Did you install all kernel dev packages? I have the following kernel packages installed:

kernel-desktop
kernel-desktop-devel
kernel-source

I just have had kernel-source, I installed the two other but its still the same.

[wzzrd]

Mmh. Does not work in Rawhide (or at least, not easily, and that is as far as I went to try it out):

$ glxinfo 
name of display: :0.0
X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  135 (GLX)
  Minor opcode of failed request:  19 (X_GLXQueryServerString)
  Serial number of failed request:  16
  Current serial number in output stream:  16

And this suggests someone will have to take Secure Programming 101 again:

$ glxinfo 
glxinfo: error while loading shared libraries: libGL.so.1: cannot enable executable stack as shared object requires: Permission denied

Hardware acceleration will apparently only work if the stack can be marked executable. That probably is the way it has always been and maybe SELinux has become a bit less tolerant about this, but still, this being 2009, an executable stack seems a bit, well, let's call it 'odd'. Anyway, I am not a kernel programer of course: maybe there are a kazillion good reasons to mark your stack executable, in which case I'll happily take back this lil' ol' rant.

[Kano]

You must enable vsync for opengl globally to get tearfree opengl playback. xv ist crap as usual.

[dgrafenhofer]

Of course if you don't have vsync enabled in the first place, you won't see any difference; it will tear just like always.

On my hardware the tearing is nearly not noticable (or I am too blind to properly recognize it), so I prefer working fullscreen flash and tearing over non-fullscreen flash.

[RealNC]

I still have to check mplayer in depth. A first look did not expose any difference compared to not setting the option.

It's impossible for mplayer (or any other app) to do vsync with this option for the same reason it's impossible in windowed mode.

Of course if you don't have vsync enabled in the first place, you won't see any difference; it will tear just like always.

[Kano]

@legume

Maybe they did not use the "right" testfiles, i would consider it as joke.

[dgrafenhofer]

Btw, I'm not sure how fullscreen flash doesn't or isn't supposed to work. What's the problem? If there is one, I'm not seeing it on my HD4870 on Gentoo AMD64 (with 64-bit Flash) :P

The problem is that running full screen flash without this option nearly crashes my hp elitebook 8530p (low framerate, 100% cpu usage, choppy playback, graphics card heating up,...)... in one word: completely unusable (and potentially dangerous to the hardware)

I still have to check mplayer in depth. A first look did not expose any difference compared to not setting the option.

[legume]

Hmm, interesting line in the resolved issues of the release notes -

Playback with UVD acceleration no longer causes Mplayer to terminate abruptly or
display blank video