AMD Catalyst 8.3 Linux Driver

[linzerd]

no... we must build it... the documentation fot fglrx available is clearly outdated... maybe brigdman and the amd developers team could help us...

[veysey]

Hip-hip!

While I would also enjoy seeing full documentation (for instance, does "Textured2D" matter? Do I need both TexturedVideo and VideoOverlay?) ...

I must first and foremost commend ATI for this release.

Everything is working on my x1250, and working pretty well.

Best release I've seen ... ever? Anticipating further fine tuning, I'm actually excited to own two ATI cards.

Many thanks, Bridgeman!

[Osado]

Even when this release is working pretty well for me (having the already mentioned flicker using xvideo on compiz), anyone noticed two X processes?
One seems to be running, the other not, but both of them are wasting the same amount of memory...

[[email protected] ~]$ ps aux | grep "X"
toni 7620 0.0 0.0 3112 1012 tty1 S+ Mar10 0:00 xinit /usr/lib/X11/xinit/xinitrc -- -auth /home/toni/.serverauth.7604 -deferglyphs 16
root 7621 5.7 6.4 148784 134428 tty7 Rs+ Mar10 4:36 /etc/X11/X :0 -auth /home/toni/.serverauth.7604 -deferglyphs 16
root 7644 0.0 6.4 148784 134428 tty7 S+ Mar10 0:00 /etc/X11/X :0 -auth /home/toni/.serverauth.7604 -deferglyphs 16

KSysGuard shows 311456 MB for both. Is some mirror effect?

Osado

[siggma]

Even when this release is working pretty well for me (having the already mentioned flicker using xvideo on compiz), anyone noticed two X processes?
One seems to be running, the other not, but both of them are wasting the same amount of memory...

[[email protected] ~]$ ps aux | grep "X"
toni 7620 0.0 0.0 3112 1012 tty1 S+ Mar10 0:00 xinit /usr/lib/X11/xinit/xinitrc -- -auth /home/toni/.serverauth.7604 -deferglyphs 16
root 7621 5.7 6.4 148784 134428 tty7 Rs+ Mar10 4:36 /etc/X11/X :0 -auth /home/toni/.serverauth.7604 -deferglyphs 16
root 7644 0.0 6.4 148784 134428 tty7 S+ Mar10 0:00 /etc/X11/X :0 -auth /home/toni/.serverauth.7604 -deferglyphs 16

KSysGuard shows 311456 MB for both. Is some mirror effect?

Osado

Same thing here:
root 3394 6.5 6.5 210232 134180 tty7 Ss+ 16:02 13:17 /usr/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
root 3403 0.0 6.5 210232 134180 tty7 S+ 16:02 0:00 /usr/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
tom 9668 0.0 0.0 5204 796 pts/0 S+ 19:24 0:00 grep X

I'm sure it's not a separate X session.
See the codes, from:# man ps

S    Interruptible sleep (waiting for an event to complete)
s    is a session leader

So the first occurrence is a session leader, the second is the event it's waiting for.
YOU... to log off.
Don't hurry, we have forever...

-Tom

[Vighy]

Even when this release is working pretty well for me (having the already mentioned flicker using xvideo on compiz), anyone noticed two X processes?
One seems to be running, the other not, but both of them are wasting the same amount of memory...

[[email protected] ~]$ ps aux | grep "X"
toni 7620 0.0 0.0 3112 1012 tty1 S+ Mar10 0:00 xinit /usr/lib/X11/xinit/xinitrc -- -auth /home/toni/.serverauth.7604 -deferglyphs 16
root 7621 5.7 6.4 148784 134428 tty7 Rs+ Mar10 4:36 /etc/X11/X :0 -auth /home/toni/.serverauth.7604 -deferglyphs 16
root 7644 0.0 6.4 148784 134428 tty7 S+ Mar10 0:00 /etc/X11/X :0 -auth /home/toni/.serverauth.7604 -deferglyphs 16

KSysGuard shows 311456 MB for both. Is some mirror effect?

Osado

under AMD64 it was already an issue of the previous releases.

don't know why they didn't fix it yet.

[Malek]

God dammit, still...

(EE) fglrx(1): [DRI] Locking deadlock.
        Already locked with context 137036428,
        trying to lock with context 2.
(EE) fglrx(1): [DRI] Unlocking inconsistency:
        Context 137036428 trying to unlock lock held by context 2
(EE) fglrx(1): [DRI] Locking deadlock.
        Already locked with context 137036428,
        trying to lock with context 2.
(EE) fglrx(1): [DRI] Unlocking inconsistency:
        Context 137036428 trying to unlock lock held by context 2

Repeated X infinity in my Xorg.0.log, and GLX works (sort of, it works once then hangs on any subsequent requests) on one screen only.

Anyone? Setup is 2 monitors in dtop=horizontal configuration.

[sloggerKhan]

I'm pretty sure every ati fglrx release I've ever used shows two xorg processes. I've always wondered about that.

[xeros]

God dammit, still...

(EE) fglrx(1): [DRI] Locking deadlock.
        Already locked with context 137036428,
        trying to lock with context 2.
(EE) fglrx(1): [DRI] Unlocking inconsistency:
        Context 137036428 trying to unlock lock held by context 2
(EE) fglrx(1): [DRI] Locking deadlock.
        Already locked with context 137036428,
        trying to lock with context 2.
(EE) fglrx(1): [DRI] Unlocking inconsistency:
        Context 137036428 trying to unlock lock held by context 2

Repeated X infinity in my Xorg.0.log, and GLX works (sort of, it works once then hangs on any subsequent requests) on one screen only.

Anyone? Setup is 2 monitors in dtop=horizontal configuration.

Any configuration with more than one monitor in fglrx is real pain. For example I haven't success with compiz+fglrx+dualhead (GL_texture_from_pixmap missing and Xorg crash with problem as you mentioned when using indirect rendering) and this problem occurs on every apllication which wants to use indirect rendering (even "glxinfo -i") - Xorg crash and infinite loop... With previous fglrx releases there were more problems (even with direct rendering crashes). I'd suggest you to use single head for now waiting for radeon or fglrx driver fixes or try dualhead setup with vertical arrangement of displays (there can be problems with 2048x2048 all displays resolution).

[NeoBrain]

By the way, has anyone tried to run Warcraft 3 under Wine using 8.3?
The graphics are quite broken for me, I hope this will get fixed in future fglrx versions... (though it could also be a wine regression, I am using 0.9.57)

[Cable]

Well, I installed the driver and it seems to be working fine with the exception of Compiz. I made a post about it on the Ubuntu forums here. If you could give me any advice on how to fix the problem, I will love you! Thanks!