|
|
#1 | |
|
Registered User
Join Date: Dec 2005
Posts: 4
|
Hello,
Basically, running /usr/bin/nvidia-settings --load-config-only --config=~/.nvidia-settings-rc doesn't restore the monitor brightness settings (even though they're there under the monitor controls). However, just running /usr/bin/nvidia-settings restores them! Also, note that this problem is present only if RANDR is enabled. If it's disabled (by enabling Xinerama), the controls appear in a different place, under "X Server Color Correction", and then the command works correctly. I think this is a regression, since the problem appeared after I upgraded from 295.59 to 304.43 (now I'm on 304.60). Thanks! ----------------------------------------- ~/.nvidia-settings-rc contents: # # Configuration file for nvidia-settings - the NVIDIA X Server Settings utility # Generated on Sun Oct 21 00:06:58 2012 # # ConfigProperties: RcFileLocale = C ToolTips = Yes DisplayStatusBar = Yes SliderTextEntries = Yes IncludeDisplayNameInConfigFile = No ShowQuitDialog = No Timer = Thermal_Monitor_(GPU_0),Yes,1000 Timer = PowerMizer_Monitor_(GPU_0),Yes,1000 Timer = Graphics_Card_(GPU_0),Yes,1000 Timer = Memory_Used_(GPU_0),Yes,3000 # Attributes: 0/CursorShadow=1 0/CursorShadowAlpha=50 0/CursorShadowRed=0 0/CursorShadowGreen=0 0/CursorShadowBlue=0 0/CursorShadowXOffset=5 0/CursorShadowYOffset=0 0/SyncToVBlank=1 0/LogAniso=0 0/FSAA=0 0/TextureSharpen=0 0/TextureClamping=1 0/FXAA=0 0/AllowFlipping=1 0/FSAAAppControlled=1 0/LogAnisoAppControlled=1 0/OpenGLImageSettings=1 0/FSAAAppEnhanced=0 0/DigitalVibrance[CRT-1]=0 0/XVideoSyncToDisplay=2 linux:0[dpy:1]/RedBrightness=-0.813953 linux:0[dpy:1]/GreenBrightness=-0.813953 linux:0[dpy:1]/BlueBrightness=-0.813953 linux:0[dpy:1]/RedContrast=0.000000 linux:0[dpy:1]/GreenContrast=0.000000 linux:0[dpy:1]/BlueContrast=0.000000 linux:0[dpy:1]/RedGamma=1.000000 linux:0[dpy:1]/GreenGamma=1.000000 linux:0[dpy:1]/BlueGamma=1.000000 |
|
|
|
|
|
|
#2 | |
|
Registered User
Join Date: Jul 2007
Posts: 74
|
In addition, 304.60 conflicts with the power management of KDE.
For example, Power Management is unable to automatically adjust the brightness when you switch to battery. Another problem I found is that the window of the nVidia panel takes more than a minute to appear on the screen. |
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: May 2008
Posts: 113
|
Try deleting your current nvidia-settings.rc file and then run the GUI tool and have it make a new one.
|
|
|
|
|
|
#4 | |
|
Registered User
Join Date: Jul 2007
Posts: 74
|
As soon as the file nvidia-settings.rc is recreated, the same problems occur.
|
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Jan 2011
Posts: 4
|
Solved:
Code:
--- .nvidia-settings-rc-313-18 2013-01-31 14:56:52.252842411 +0100 +++ .nvidia-settings-rc 2013-01-31 16:01:42.964688769 +0100 @@ -62,21 +62,21 @@ 1/ColorSpace[DFP-1]=0 1/ColorRange[DFP-1]=0 1/XVideoSyncToDisplay=131072 -debian64:0[dpy:0]/RedBrightness=0.000000 -debian64:0[dpy:0]/GreenBrightness=0.000000 -debian64:0[dpy:0]/BlueBrightness=0.000000 -debian64:0[dpy:0]/RedContrast=0.000000 -debian64:0[dpy:0]/GreenContrast=0.000000 -debian64:0[dpy:0]/BlueContrast=0.000000 -debian64:0[dpy:0]/RedGamma=1.000000 -debian64:0[dpy:0]/GreenGamma=1.000000 -debian64:0[dpy:0]/BlueGamma=1.000000 -debian64:0[dpy:3]/RedBrightness=-0.161290 -debian64:0[dpy:3]/GreenBrightness=-0.161290 -debian64:0[dpy:3]/BlueBrightness=-0.161290 -debian64:0[dpy:3]/RedContrast=-0.424731 -debian64:0[dpy:3]/GreenContrast=-0.424731 -debian64:0[dpy:3]/BlueContrast=-0.424731 -debian64:0[dpy:3]/RedGamma=1.000000 -debian64:0[dpy:3]/GreenGamma=1.000000 -debian64:0[dpy:3]/BlueGamma=1.000000 +:0[dpy:0]/RedBrightness=0.000000 +:0[dpy:0]/GreenBrightness=0.000000 +:0[dpy:0]/BlueBrightness=0.000000 +:0[dpy:0]/RedContrast=0.000000 +:0[dpy:0]/GreenContrast=0.000000 +:0[dpy:0]/BlueContrast=0.000000 +:0[dpy:0]/RedGamma=1.000000 +:0[dpy:0]/GreenGamma=1.000000 +:0[dpy:0]/BlueGamma=1.000000 +:0[dpy:3]/RedBrightness=-0.161290 +:0[dpy:3]/GreenBrightness=-0.161290 +:0[dpy:3]/BlueBrightness=-0.161290 +:0[dpy:3]/RedContrast=-0.424731 +:0[dpy:3]/GreenContrast=-0.424731 +:0[dpy:3]/BlueContrast=-0.424731 +:0[dpy:3]/RedGamma=1.000000 +:0[dpy:3]/GreenGamma=1.000000 +:0[dpy:3]/BlueGamma=1.000000 |
|
|
|
|
|
#6 | |
|
Registered User
Join Date: Dec 2002
Location: Rio de Janeiro, Brazil
Posts: 88
|
Well, it is still broken for me (304.64 driver on a x86_64 Fedora 18). The .rc file is saved when I quit nvidia-settings (the timestamp on the header is updated), but some settings reset to their defaults. I can't save neither brightness nor contrast or gamma for any of my two monitors, changes are simply ignored. The same applies to cursor shadow. Weird thing is that some other settings are saved as expected (at least "sync to vblank" and "flipping").
Also, the tool is reading settings from the file, but isn't applying them: if I change let's say contrast and quit the tool, settings are not saved but the changes are effective. When I run the tool again it shows the (default) values read from the file, but doesn't reset the monitor configuration -- unless I make any other change on the settings or reset to hardware defaults. This is very annoying :-( I hope it gets fixed soon. Regards, Andre |
|
|
|
|
|
|
#7 |
|
Registered User
Join Date: Dec 2002
Location: Rio de Janeiro, Brazil
Posts: 88
|
Is there anywhere I could file a bug report? This is really annoying since the only way to load custom settings is to open nvidia-settings dialog during desktop session startup...
|
|
|
|
|
|
#9 |
|
Registered User
Join Date: Dec 2002
Location: Rio de Janeiro, Brazil
Posts: 88
|
Thks for the pointer, didn't know about it (it was about time BTW ;-)). Will post there.
|
|
|
|
![]() |
| Thread Tools | |
|
|