would using a different X server be an option?
If so, you can ask X to use an individual XF86Config, and you can add the
desired "Gamma" parameter to the "Monitor" section in that
new
"XF86Config_gamma" file
here's a bite of my XF86Config file to deal with an LCD monitor
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Sony GDM-17SE2T"
DisplaySize 337 270
HorizSync 30.0 - 85.0
VertRefresh 48.0 - 150.0
Gamma 0.6
Option "dpms"
EndSection
This guy here sort of puts it all in a script:
http://koti.mbnet.fi/hoppq/sc-howto.html
On Thu, 24 Jun 2004 16:12:29 -0700 (PDT), Randall Walls
<slightcrazed@linuxquestions.net> wrote:
> Hello List,
>
> I'm hoping someone else might have a solution for a particularly
strange
> problem that I have been having. I am running wine 20040615, on a
> slackware 9.1 install running dropline gnome and the 2.6.6 kernel.
> Whenever I run a game that requires OpenGL, I often have to adjust the
> brightness of my monitor so that I can see what is on screen. It is an
> old monitor, and has seen better days. This was always just a mild
> inconvenience, as I would write the gamma change into a script to launch
> the app anyway. Recent versions of wine seem to be ignoring the current
> gamma (xgamma -gamma 4.6) and are running extrememly dark. Deus Ex is a
> good example. I can manually adjust the brightness to 4.6, start the
> application, and right before the full screen mode starts the gamma
> switches back to 1.0 and I can hardly see anything on the screen. No
> error messages pertaining to gamma settings are present. My assumption
> is that because the game has an internal brightness adjustor that
> somehow wine i!
> s feeding the game a gamma setting of 1.0, and then the game is using
> that as a base and adjusting up or down from 1.0, as opposed to
> adjusting up or down from 4.6, which it should be. Does this make any
> sense? Is there a setting or a line of code that I can tweak to get Wine
> to recognize the current gamma setting? Any ideas?
>