Comment 3 for bug 1049630

Revision history for this message
In , Brian Ealdwine (eode) wrote :

This is a severe issue, that prevents me (and a decent number of others) from using accelerated graphics.

This bug has the following behaviors:

* Corrupts the displayed graphics of every running program (as far as I can tell).
* Often corrupts the pointer graphics
* Corrupts fonts
* Corrupts the terminal display with noise from X, if you switch to a terminal
* Exists in accelerated and unaccelerated modes, but is marginal when not accelerated.
* Is made worse by KMS
* Is made worse by Compositing.
* Affects a rather large number of users (many with the rs690/x1200/x1250 cards, which are common in netbooks)

The previous workaround has been to disable KMS, which I believe somehow caused the radonhd driver to be used (uncertain about this). Either way, it brought the garbage to a usable level, and still allowed acceleration. However, that is not the case now. Using nomodeset results in a non-accelerated desktop.

Please let me know what pieces of information I should supply, and how I can be of assistance regarding this.

Note that glxinfo currently (with kms disabled) reports me to be using SGI and Mesa. Direct Rendering is "Yes", but it's actually using software, yes?. Even with this totally different driver set, I still sometimes get the corruptions (particularly after a long time running).

Is it possible that some fundamental thing (like a base memory address, or how much shared memory is to be used, or something) is being misreported and causing all these issues? This seems to be a very difficult bug to sort out, as it has been around a while.