Bugzilla – Bug 103963
switching screens on Matrox G400 corrupts colors of the X desktop
Last modified: 2005-08-15 14:07:30 UTC
After switching between console and graphic screen (Ctrl-Alt-F{1,7}), the colors of the X desktop are corrupted. I remember a related problem in the early days of the MGA driver some years ago, and from the early days of MGA G550 support (not so long ago).. Also, I had one occurence of https://bugzilla.novell.com/show_bug.cgi?id=71981 on this system with B1 (from about 15 login attempts). I don't remember that on a G400 any time before.
Please provide more informations: http://www.opensuse.org/index.php/Bugs:X
Created attachment 45631 [details] xorg.conf
Created attachment 45632 [details] Xorg.0.log
Created attachment 45633 [details] hwinfo --gfx
Let me know, what else you need..
There has been *zero* changes in mga driver since SuSE 9.3 ...
Hmm, than the culprit must be somewhere else. Surely the kernel is involved in console switching, and X. Both would lead to others suffering from it, too, don't it?
Created attachment 45940 [details] screenshot of the damage
BTW, you use a dualhead setup with different color depths on both screens. Please test whether it helps to use either 16 or 24 bit color depth for both screens.
It wasn't me, who setup dualhead. Blame sax2.. Either adjusting the second port to 24 bit or deactivating it comletely fixed it! The typical color corruption is visible for half a second in the upper half of the screen after switching back to X. Looks like the screen content is copied first, and the color tables(?!) are adjusted later (after vbi?). A question remains: could this be prevented without user intervention? BTW: while I got https://bugzilla.novell.com/show_bug.cgi?id=71981 a few times before the fix, it never happened thereafter (restarted X about 20 times, switched screens back and forth many times).
Please describe in detail, what you did during installation and configuration of X11.
Well, that's easy: as I happily noticed the new buttons to adjust the resolution in YaST, I just reduced the screen resolution from 1280x1024 to 1152x864, since the default is a bit to much for this poor 17'' CRT. Nothing else. I can kick another install on this system to support this claim, if you like. In real installations with Matrox graphic cards, which I happen to have quite a bunch of (about 30 in all flavors from early G200 with 2MB up to the G550), I tend to deactivate the second screen, reduce the max. vert. refresh to 85Hz (if CRT), and activate 3D acceleration.
Stefan I'm fed up with that matrox graphics driver it's really a piece of broken code. I would suggest to remove every profile entry within the CDB using the Matrox_* profile files. In that case only single head is supported which means there is a small chance for the driver to work correctly Thanks
I agree. We should finally do this step.
Matrox_* profile entries are now removed in CDB. Fixed for Beta2.