AMD Catalyst 8.3 Linux Driver

[linzerd]

bridgman, Xv is almost fixed, but still when there are fast movements tearing is noticed even with TexturedVideoSync activated, but i think that you're in the right way... please keep on with the work on Xvideo issues, and in AMDCCCLE functionality... Keep on with the good work guys! BTW, what are the better options for video playback with a Radeon X1300 ? I mean options for xorg.conf file... Thx in advance

[bridgman]

For an X1300, I would go with :

TexturedVideo on
VideoOverlay off
OpenGLOverlay off (doesn't really matter, but...)

Check in amdpcsdb to make sure that you don't have competing settings in there. In the event of a conflict, I believe amdpcsdb wins. Also note that the syntax is a bit different -- "Son" and "Soff" (meaning "string : on" etc... IIRC).

[Extreme Coder]

I will repeat my question, since you guys didn't seem to notice it:
How do you stop the stuttering of video and 3D when Compiz is on? (not necessarily fullscreen)
Thanks!

[xeros]

As I still experienced freeze at logout with this release when atieventsd is active I take a few time today to search for the reason.

What I found is authatieventsd.sh do not search the xauthority file at the location my system put it : /var/run/xauth/
It look like this is the default location for xorg7 and kdm do not override it.
Change that in authatieventsd.sh and all work fine!

I add a comment in the bugzilla with this change:
http://ati.cchtml.com/show_bug.cgi?id=992#c26

But atieventsd must be made more robust to not freeze the screen in the case authatieventsd.sh return an error because it is likely that many other error condition are possible.

Thank you very much pchev. This /etc/ati/authatieventsd.sh modification helped me - now Xorg doesn't freeze on KDM restart/kill/shutdown. I've changed:
XDM_AUTH_MASK=/var/lib/xdm/authdir/authfiles/A$1*
to
#XDM_AUTH_MASK=/var/lib/xdm/authdir/authfiles/A$1*
XDM_AUTH_MASK=/var/run/xauth/A$1*
and now KDM works fine.

[hobbes]

For an X1300, I would go with :

TexturedVideo on
VideoOverlay off
OpenGLOverlay off (doesn't really matter, but...)

Check in amdpcsdb to make sure that you don't have competing settings in there. In the event of a conflict, I believe amdpcsdb wins. Also note that the syntax is a bit different -- "Son" and "Soff" (meaning "string : on" etc... IIRC).

I did exactly that:

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
Option "TexturedVideo" "on"
Option "VideoOverlay" "off"
Option "OpenGLOverlay" "off"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "0"
# Option "RENDER" "0"
EndSection
_ _ _ _ _ _

[AMDPCSROOT/SYSTEM/DDX]
TexturedVideo=Son
VideoOverlay=Soff
OpenGLOverlay=Soff

_ _ _ _ _

But when I run Totem it gets segfaulted.

totem La.Grande.Illusion.\(1937\).FS.B\&amp\;W.CRiTERiON .DVDRip.DivX5-Wolfman.avi
sh: jackd: not found
No accelerated IMDCT transform found
sh: jackd: not found
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 78 error_code 2 request_code 140 minor_code 19)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
_ _ _ _ _ _ _

Mplayer no video playback, only an empty window and this output:

Starting playback...
VDec: vo config request - 672 x 512 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.31:1 - prescaling to correct movie aspect.
VO: [xv] 672x512 => 672x512 Planar YV12
[mpeg4 @ 0xe5eba0]frame skip 8ct: 0.000 1/ 1 ??% ??% ??,?% 0 0
X11 error: BadValue (integer parameter out of range for operation)
X11 error: BadValue (integer parameter out of range for operation)
X11 error: BadValue (integer parameter out of range for operation)
X11 error: BadValue (integer parameter out of range for operation)
X11 error: BadValue (integer parameter out of range for operation)
X11 error: BadValue (integer parameter out of range for operation)
X11 error: BadValue (integer parameter out of range for operation)
_ _ _ __ _ _ _ _ _

There is a message on Xorg.O.log.

glesx exec program failed
glesx exec program failed
glesx exec program failed
glesx exec program failed
_ _ _ _ _ _ _ _

Do you have any idea what this is happening?

Gutsy 64 bits + X1600 pro AGP 512MB + Catalyst 8.3

Thanks for reading.

[fransschreuder]

Well, i also have Mobility Radeon X2300, running Ubuntu Gutsy on Asus F3Jr laptop and I did and upgrade from 8.1 fglrx using the automatic installation.
So far tested:
xv - finaly works, no blocks or diagonal tearing, even HD demos run fine, it also uses noticably less CPU
3D - tested glxgears and fgl_glxgears, all works, score +- the same
suspend - tried a few times, seems to work
hibernate - not tested yet, worked on 8.1 but with dead sound
compiz - no luck but it has never worked in the past,so its perhaps some configuration mess on my side

So do you have 8.3 running? (you didn't mention the version) And which automated installer did you use? just ./ati-driver-installer-8-3-x86.x86_64.run or did you use --buildpkg Ubuntu/Gutsy.

Are you sure that it actually loads? (have you blacklisted the old fglrx driver) or are you maybe just running the old driver from the repository. I find it suspicious that you don't have aiglx and no flicker. sounds like the old driver...

[linzerd]

sorry, but where is located this amdpcsdb? i need to check settings there too?

[Melcar]

sorry, but where is located this amdpcsdb? i need to check settings there too?

It's in /etc/ati
Usually what you change in xorg.conf relating to the driver also affects amdpcsdb, but as far as I know, it doesn't work the other way (changes in amdpcsdb do not affect xorg.conf). All your multiple display settings, as well as post processing settings (AA, AF, Vsync) are also stored in amdpcsdb.

[linzerd]

thx melcar, guys this indeed is a forum... thx to all of you... it would be interesting to make a document with all xorg.conf options for the fgrlx driver and their effects... and the way amdpcsdb works...

[Slegge]

it would be interesting to make a document with all xorg.conf options for the fgrlx driver and their effects... and the way amdpcsdb works...

mhm, good idea. I went looking earlier for doc's regarding the xorg.conf options for fglrx, amdpcsdb, etc. What i found was a man page for fglrx that seems to be somewhat old and probably outdated. Is there any recent doc's lying around anywhere? other than forum posts