FedoraForum.org - Fedora Support Forums and Community
Results 1 to 10 of 10
  1. #1
    gy.schmitt Guest

    [F10] ATI Radeon XAA vs EXA [SOLVED]

    Hello,

    I just installed Fedora 10, 32 bits. I'm running an ATI Radeon 9600 M10 R350 with the "radeon" x.org driver. However, I have been very unpleased with the performance of EXA:

    - frequent font corruption (garbled) with EXA
    - huge performance decrease: glxgears went from 1400+ fps with XAA to 550+ with EXA !

    Is there any explanation for this, or is this just the state of the EXA in the radeon?

    Also, I had to switch to another kernel, because adding the XAA option in xorg.conf would systematically crash everything, to the point of non responsiveness (computer hard shutdown). The stock Fedora kernel would never be able to start x.org.

  2. #2
    Join Date
    Sep 2006
    Location
    Connellsville, PA, USA
    Posts
    11,306
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    EXA = "Experimental Acceleration Architecture". Does that explain ?

    I'm disappointed that XAA would fail. There are numerous options to try, however - see: man radeon and consider trying driconf to play with DRI options.

    V
    Last edited by Hlingler; 29th November 2008 at 05:56 AM.

  3. #3
    gy.schmitt Guest
    It wans't my intent to start a flamewar, but from what I've heard, EXA support for ATI R300 (yes, it's ATI, not intel...) was almost complete. Still, that doesn't explain why XAA fails. I guess I have more options to explore.

  4. #4
    Join Date
    Sep 2006
    Location
    Connellsville, PA, USA
    Posts
    11,306
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    OOPS! Must have been day-dreaming. I meant: man radeon. Fixed the above post.

    If you really want to find out why XAA fails, you would have to deliberately reproduce the error conditions, and then review the Xorg.0.log to find out why. It is possible (but not certain) that the problem could be corrected.

    V

  5. #5
    gy.schmitt Guest
    I tried to attach the log, but didn't work. Here's the link: http://pastebin.com/m73cb0f8f

    I had a look at the log, no (WW) or even (EE) line.

    However, I saw:

    Code:
    (II) RADEON(0): XAA Render acceleration unsupported on Radeon 9500/9700 and newer. Please use EXA instead.
    So it looks like I should use EXA anyway, despite its terrible performance and countless graphic bugs. Interesting...
    Last edited by gy.schmitt; 29th November 2008 at 04:48 PM.

  6. #6
    Join Date
    Sep 2006
    Location
    Connellsville, PA, USA
    Posts
    11,306
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by gy.schmitt
    I tried to attach the log, but didn't work. Here's the link: http://pastebin.com/m73cb0f8f
    Unfortunately, our vBulletin attachments feature is currently busted, which is why I mentioned pastebin.com.
    Quote Originally Posted by gy.schmitt
    I had a look at the log, no (WW) or even (EE) line.
    I see:
    Code:
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    Such warnings, while perhaps not fatal, cannot help. I suggest that you fix it:
    Code:
    su -
    yum install acpi acpid
    [...]
    chkconfig --level 2345 acpid on
    service acpid start
    Then re-start X.

    Also:
    Code:
    (II) RADEON(0): Cannot access BIOS or it is not valid.
    BIOS update? The ACPID might also fix this.
    Quote Originally Posted by gy.schmitt
    However, I saw:
    Code:
    (II) RADEON(0): XAA Render acceleration unsupported on Radeon 9500/9700 and newer. Please use EXA instead.
    Not sure - I see conflicting info:
    Code:
    (II) RADEON(0): XAA Render acceleration unsupported on Radeon 9500/9700 and newer. Please use EXA instead.
    (II) RADEON(0): Render acceleration disabled
    (II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
            Screen to screen bit blits
            Solid filled rectangles
            8x8 mono pattern filled rectangles
            Indirect CPU to Screen color expansion
            Solid Lines
            Scanline Image Writes
    (II) RADEON(0): Acceleration enabled
    What does glxinfo|grep render say?
    Quote Originally Posted by gy.schmitt
    So it looks like I should use EXA anyway, despite its terrible performance and countless graphic bugs. Interesting...
    It is of also possible that the decrease in performance has nothing at all to do with the driver. It might be due to increased resource demands of the newer desktop and other apps, or problems in same. Example: F8=>F9, my (very ancient) ATI Rage Pro (A) crashed KDE4 with xorg.conf option "BackingStore" on (still does, and so does any chipset with same option, bug open...), and (B) performed horribly under new "plasma" desktop until 2.6.27+ series kernels and/or KDE4.1.3, but (C) now works fine with Plasma but FPS dropped from ~250 to ~200 (20% decrease). Oh, well: creeping giantism of software means that each new release demands more from hardware, leaving older chipsets further behind. In such cases, a better measure of performance is a real benchmark program like hardinfo - I suggest that you install it, then run ("System Profiler and BenchMark") the FBENCH test (FPU RayTracing). Sync with on-line database for best comparison with other similar hardware.

    Finally, you can install package driconf and play with DRI settings to attempt to maximize performance. There are many xorg.conf options specific to radeon driver that might also help; see: man xorg.conf and man radeon.

    V

  7. #7
    gy.schmitt Guest
    My answers:

    - I don't see the need for acpid anymore. It used to be nice when I was not running gnome-power-manager, but I got rid of it and didn't see a difference, as everything works fine (power buttons, cpufreq...) without it.

    - bios not valid: it always was like this, didn't trouble anything (maybe due to the fact I'm on a laptop?)

    - XAA was actually enabled.

    Huge information however: I found the culprit, and it turned out not to be EXA, but KMS itself.

    Booting with the nomodeset option on the kernel line, started X as usual and ran glxgears gave me a nice 1400+ fps. I should have thought about it, because my cpu is under heavy load when plymouth starts up with the graphic effects (the fan turns on and is loud). More info to come later, but so far, KMS is out of my computer.

    Btw:

    Code:
    glxinfo | grep "render"
    OpenGL renderer string: Mesa DRI R300 20060815 AGP 8x x86/MMX+/3DNow!+/SSE2 TCL
    Funny, I thought this had been updated when the ATI driver went from 6.8 (Fedora 9) to 6.9 (Fedora 10).

  8. #8
    gy.schmitt Guest
    Alright, final nail in the KMS coffin. Using nomodeset as a kernel parameter, I get:

    - Decent 2D/3D acceleration
    - EXA as well as XAA are possible and won't crash the computer
    - No more graphic glitches (usually seen in fonts being rendered uncorrectly - some characters were just misinterpreted).
    - Flash in Firefox doesn't glitch anymore (i.e some flash objects don't disappear when out of the visible area)

  9. #9
    Join Date
    May 2008
    Posts
    12
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I have the same problem with radeon 9600 and reverted back to F9.
    Can you please let me know if you are running compiz and what is the performance ?
    what is KMS ? what does nomodeset do ?
    There is a bug filed against radeon driver as well.
    https://bugzilla.redhat.com/show_bug.cgi?id=473115

  10. #10
    gy.schmitt Guest
    - Not running compiz.
    - KMS : look in Fedora 10 release notes (do your search!)
    - radeon driver bug : I'm not sure the driver is at fault, the KMS code is.

Similar Threads

  1. Replies: 0
    Last Post: 24th November 2006, 02:22 AM
  2. nother dual head: Radeon 9200 + Radeon 7500
    By ZeuS572 in forum Hardware
    Replies: 2
    Last Post: 15th June 2005, 05:03 PM
  3. Replies: 1
    Last Post: 12th September 2004, 08:31 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •