Am Donnerstag, den 28.01.2010, 10:13 +0100 schrieb Michel Dänzer: > On Tue, 2010-01-26 at 13:41 +0100, Bruno Kleinert wrote: > > Before I executed xgamma -gamma 1.0 I queried the X server by calling > > xgamma about the current settings and the output of xgamma was, that the > > values for RGB were already all set to 1.0! So it looks as if the state > > of the X server and the graphics hardware aren't the same after > > resuming. > > Maybe the X server or driver doesn't (properly) restore the hardware > CLUT on resume. > > Does this workaround also help on the other machine with an Intel GPU? Yes, the workaround also works on my notebook with the Intel GPU! Hm, looks as if it's a bug in the X server itself. I browsed the bug reports against xserver-xorg-core but didn't find something that could be the same or a similar bug as I'm experiencing it. A further experiment to collect information: On the Intel notebook I tried blindly to restore gamma values from the KMS framebuffer text console with DISPLAY=:0.0 xgamma -gamma 1.0 but that didn't bring back neither the framebuffer console nor the X session when I tried to switch to it. Only Blindly unlocking the GNOME screensaver and issuing the xgamma command restores the gamma values for the X session and also the KMS framebuffer text. Btw.: Also at the framebuffer console when I issued the xgamma command before, xgamma claimed that the gamma settings already were all set to 1.0 for R, G and B. I didn't yet try to get back gamma values on the ATI/AMD GPU from the text console (no KMS!) on my desktop machine. > > Is there a possibility to query the graphics hardware about gamma > > settings directly? > > Not sure there's anything better than looking at the monitor. :) Hehe, then I'll keep on looking at it ;)
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil