Announcement

Collapse
No announcement yet.

AMD Catalyst 8.9 Gets WINE Fix, RandR 1.2 Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Vighy
    replied
    Originally posted by Aostrich View Post
    @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...

    Leave a comment:


  • Aostrich
    replied
    @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...

    Leave a comment:


  • mirak63
    replied
    Originally posted by wfeltmate View Post
    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 ?

    Leave a comment:


  • Vighy
    replied
    Originally posted by Aostrich View Post
    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

    Leave a comment:


  • Aostrich
    replied
    Originally posted by Vighy View Post
    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...

    Leave a comment:


  • wfeltmate
    replied
    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.

    Leave a comment:


  • mirak63
    replied
    is video tearing fixed ???

    Leave a comment:


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

    It already happened with Catalyst 8.7...

    Code:
    [...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:
    Code:
    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

    Leave a comment:


  • Kano
    replied
    Well you can not directly remove only, but when you install another driver the old one is uninstalled.

    Leave a comment:


  • aniruddha
    replied
    Originally posted by Kano View Post
    Well you can remove it with the script as it has the hotfix integrated. If you want to do that manually do:

    sed -i 'sX> /dev/nullX||trueX' /var/lib/dpkg/info/xorg-driver-fglrx.postrm

    My script downloads dkms (updated url yesterday, before it might be broken for Debian) then the Ubuntu debs can be used. Latest script can use -v8-9 on 64 bit already. Working on the rest. dkms is nice when you switch kernels, then you always get the correct fglrx module - also you can trigger patches based on kernel version.
    How do I use your script to remove drivers? (the help function doesn't show this).

    Leave a comment:

Working...
X