AMD Catalyst 8.9 Gets WINE Fix, RandR 1.2 Support

[Vighy]

And what about a bad regression that segfaults my Xorg on start-up?

It already happened with Catalyst 8.7...

[...snip...]
(II) fglrx(0): Direct rendering enabled
(II) fglrx(0): Interrupt handler installed at IRQ 16.
(II) fglrx(0): Exposed events to the /proc interface
(II) fglrx(0): Finished Initialize PPLIB!
(II) fglrx(1): === [atiddxPreInit] === begin
(EE) fglrx(1): Quitting secondary screen -- no monitor specified.
(EE) fglrx(1): PreInit failed
(II) fglrx(1): === [atiddxPreInit] === end

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x49263a]
1: /lib/libc.so.6 [0x7f9e61f5dda0]
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxFreeScreen+0x2f4) [0x7f9e5fcfa434]
3: /usr/bin/X(xf86DeleteScreen+0x7e) [0x4a5ade]
4: /usr/bin/X(InitOutput+0xa1f) [0x46c0bf]
5: /usr/bin/X(main+0x2c6) [0x437256]
6: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f9e61f491d6]
7: /usr/bin/X(FontFileCompleteXLFD+0x289) [0x4366f9]

Fatal server error:
Caught signal 11.  Server aborting

exactly the same backtrace!! (info about my architecture are in that thread, too)

http://www.phoronix.com/forums/showthread.php?t=11570

and other people experienced it too:

http://www.phoronix.com/forums/showthread.php?t=11794

with other chipsets...


Catalyst 8.8 and 8.6 didn't suffer for the hang. While 8.9 and 8.7 do hang in the same way.
There may be a workaround?

Bridgman, you could know an answer, or just tell your friends in AMD that this happens on this specific platform:

BIOS_CREATION_DATE="01/28/08,15:12:26"
BIOS_MSG="ASUS_F3Sa A12 M76 BIOS GDDR2 400m/500e ASID:A15201.011$                     "
BIOS_KIT_VERSION="BK-ATI VER010.054.000.000"

Thanks

[mirak63]

is video tearing fixed ???

[wfeltmate]

Fixed, no. They are still working to implement and complete the missing features that is causing the tearing. However, I noticed a lot less tearing in this release than the previous. For me, I only notice the tearing during really fast action scenes.

[Aostrich]

And what about a bad regression that segfaults my Xorg on start-up?

I had the same problem, I couldn't run X.
Uninstalling fgrlx with purging /etc/ati/ and restoring default xorg.conf and then installing Catalyst 8.9 helped me.
Try this, may be it's your case as well...

[Vighy]

I had the same problem, I couldn't run X.
Uninstalling fgrlx with purging /etc/ati/ and restoring default xorg.conf and then installing Catalyst 8.9 helped me.
Try this, may be it's your case as well...

no way.... sorry but it didn't help

[mirak63]

Fixed, no. They are still working to implement and complete the missing features that is causing the tearing. However, I noticed a lot less tearing in this release than the previous. For me, I only notice the tearing during really fast action scenes.

what is your xorg.conf ?

[Aostrich]

@Vighy,

which version of xorg-server do you use?
I succeeded only after upgrading from 1.4.0.99 (which is default for Slackware 12.1 and Slamd64 12.1) to 1.4.2...

[Vighy]

@Vighy,

which version of xorg-server do you use?
I succeeded only after upgrading from 1.4.0.99 (which is default for Slackware 12.1 and Slamd64 12.1) to 1.4.2...

xorg-server-1.4.2
and tried with 1.3.0.0 with the same result..

but I also tried on a livecd of ubuntu, a supported distro, and Xorg hung again...

with 8.7 bridgman said it could be related to my platform.. I don't know...

[wfeltmate]

what is your xorg.conf ?

Pretty well just the default setup really.

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
# Screen "aticonfig-Screen[0]-1" LeftOf "aticonfig-Screen[0]-0"
InputDevice "Synaptics Touchpad"
EndSection

Section "Files"
EndSection

Section "Module"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]-1"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:5:0"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]-1"
Driver "fglrx"
BusID "PCI:1:5:0"
Screen 1
EndSection

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

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

[C-MoH]

Come on ATi, support my 3870x2 already... the thing's price has already halved from when I bought it in April so put that profit to good use!

There is a thread here on how to hack the driver to get it working. However, this is not enough. I'm with you.