|
Bugzilla – Full Text Bug Listing |
| Summary: | intel: Fonts sometimes get corrupted on VT switch with EXA ( 965GM) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Andrew Jorgensen <ajorgensen> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <xorg-maintainer-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | font corruption | ||
|
Description
Andrew Jorgensen
2008-04-26 00:18:39 UTC
Created attachment 210633 [details]
font corruption
This happened on first boot as well. Thanks for the reminder. Can you still reproduce this issue when adding Option "AccelMethod" "XAA" to Section "Device" of your /etc/X11/xorg.conf? (In reply to comment #3 from Stefan Dirsch) > Option "AccelMethod" "XAA" This certainly helps for my after-suspend rendering problems. Thanks. It would be interesting wich EXA acceleration breaks it. Could you test the available "EXANo*" options to figure this out? See "man exa" for details. Yes, the option given does avert the issue. I have not tried the EXANo options yet. Thanks for the promise to test with these options. ;-) Due to performance reasons I decided to make XAA the default for intel driver again. Therefore I'm closing this one now as fixed. Still it would be interesting to know, which EXANo* can workaround this issue. It's EXANoComposite=Yes that works around the issue. Thanks for the update. This is also the option, which is always mentioned, when it comes to bad performance with EXA and how to workaround it. I noticed that Ubuntu uses the "greedy" EXA MigrationHeuristic (from their X logs, they must have it hard-coded in the intel driver) so I tried that in oS 11.0 and it also works around this issue. It may also work around the performance issues. Please give it a try by setting Option "MigrationHeuristic" "greedy" This is what also the nv driver manual page recommends. But I'm afraid there is a reason, why "greedy" is *not* the default. |