View Full Version : dpms standby forces gamma to 1.0
I just downloaded the 1.0-4363 drivers. I am excited to see that SMP + DVI is working great.
DPMS works too. But when I set DPMS to standby using the comand "xset dpms force standby", my gamma, which was initialized to 2.0 by my XF86Config, is reset to 1.0, despite the fact that xgamma reports the gamma as still being 2.0.
It is easy to reset the gamma to 2.0 using the command "xgamma -gamma 2.0". It's just a minor inconvenience.
Some information about my system:
linux kernel 2.4.20
XFree86 Version 4.2.1.1
nullpointer
04-24-03, 07:32 PM
I have noticed the same problem but I wasn't sure if it was the NVidia drivers or X.
As a hack to work around the problem I wrote this small program:
/*
compile:
g++ -O3 xgamma_fix.C -o xgamma_fix -L/usr/X11R6/lib -lXext -lXxf86vm -lX11
*/
#include <X11/Xlib.h>
#include <X11/extensions/xf86vmode.h>
extern "C" {
#include <X11/extensions/dpms.h>
}
#include <unistd.h>
static void set_gamma( Display* dpy )
{
XF86VidModeGamma gamma;
gamma.red = 0.7;
gamma.green = 0.7;
gamma.blue = 0.7;
XF86VidModeSetGamma( dpy, DefaultScreen(dpy), &gamma );
}
int main()
{
int dummy;
BOOL onoff;
CARD16 state;
Display* dpy = XOpenDisplay( 0 );
bool on = true;
while( 1 )
{
DPMSInfo( dpy, &state, &onoff );
if( onoff )
{
if( state == DPMSModeOn )
{
if( ! on ) set_gamma( dpy );
on = true;
}
else
{
on = false;
}
}
sleep( 1 );
}
return 0;
}
I have noticed the same problem but I wasn't sure if it was the NVidia drivers or X.
Well I don't have this problem on my other computer. Here is more information about the computer on which the problem does occur:
linux kernel 2.4.20
XFree86 Version 4.2.1.1
nvidia drivers 1.0.4363
card: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a2)
monitor: DVI LCD
And here's more information about the computer on which the problem doesn't occur:
linux kernel 2.4.19
XFree86 Version 4.2.1.1
nvidia drivers 1.0.3123
card: nVidia Corporation NV25 [GeForce4 Ti 4600] (rev a3)
monitor: SVGA CRT
nullpointer
04-24-03, 09:11 PM
I think it is because the monitor is connected via DVI, I have had the problem since I got my flatpannel about a year ago with the last few revs of drivers.
vBulletin® v3.7.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.