|Summary:||x11-drivers/xf86-video-savage - EXA acceleration problems|
|Product:||Gentoo Linux||Reporter:||Riccardo <multix>|
|Component:||Current packages||Assignee:||Gentoo X packagers <x11>|
|Package list:||Runtime testing required:||---|
Description Riccardo 2012-10-27 10:25:59 UTC
Comment 1 Matt Turner 2012-10-27 17:35:46 UTC
It's outside of our scope to solve this. It's better to report this upstream (bugs.freedesktop.org) instead.
Comment 2 Chí-Thanh Christopher Nguyễn 2012-10-27 20:46:47 UTC
xorg-server-1.13 no longer supports XAA. The garbage you were seeing are probably bugs in shadowfb which is the default fallback. If framebuffer console is messed up, try a different fb driver (vesafb, uvesafb, savagefb, vga16fb) or vga text mode. Regarding the EXA slowness, try to play with the EXA options in xorg.conf (see "man exa"). Other than that you will need to wait until upstream fixes this and stay with xorg-server-1.12 in the meantime.
Comment 3 Riccardo 2012-11-04 09:43:29 UTC
I tried switching back to xorg 12.4 (and rebuilding all dirvers/modules again due to ABI downgrade) and noticed two things: 1) still with EXA enabled, I experience 2D slowness, however at xserver termination, my framebuffer is fine again 2) with XAA enabled everything works smooth again, both 2D performance and console after exit point 1 proves that the console mess-up problem is not EXA/XAA related, but xorg related
Comment 4 Chí-Thanh Christopher Nguyễn 2012-11-04 09:44:15 UTC
The EXA slowness can still be due to your fb driver.
Comment 5 Riccardo 2012-11-04 09:50:33 UTC
What/where do you suggest a change? are you sepaking about xorg settings? currently I have Identifier "Card0" Driver "savage" VendorName "S3 Inc." BoardName "SuperSavage IX/C SDR" BusID "PCI:1:0:0" #Option "AccelMethod" "XAA" Option "AccelMethod" "EXA" at a forum suggestion I had added Option "MigrationHeuristic" "greedy" without success. It is interesting to read: The EXA architecture is designed to make accelerating the Render exten- sion simple and efficient, and results in various performance tradeoffs compared to XAA. if it is efficient, it shouldn't have a performance tradeoff .)
Comment 6 Chí-Thanh Christopher Nguyễn 2012-11-04 09:55:04 UTC
The first change I suggest is to lose that fb driver (or replace it with one of the others). The other changes are the four EXA options, which you can try in multiple combinations to see if there is one combination that makes things work faster. Also don't forget to report this issue at bugs.freedesktop.org, because we are just packaging what upstream releases.
Comment 7 Chí-Thanh Christopher Nguyễn 2013-09-25 16:34:19 UTC
Please test 2.3.7 and if the issue still exists, reopen with a link to the upstream bug report.