Hello. I have a GeForce GT 610 on a computer running openSUSE Leap 15. It’s working very well, but I need to set the underscan by 50 pixels. No problem doing that through the NVIDIA X Server Settings utility, but, when I click on “Save to X Configuration File” to try to save the new setting, I get the “Save X Configuration” window with a “Browse…” button next to a window to put in… What? Where is the configuration file kept? Or, where does this configuration file need to be saved? “Merge with existing file” and the check box next to it is grayed out.
THANKS!
You need to run nvidia-settings as root to be able to write to the system config:
sudo nvidia-settings
the location to enter is
/etc/X11/xorg.conf
It’s probably empty and the merge button grayed out because there’s no config currently existing.
1 Like
Thanks, that helped, though I still needed to generate an initial xorg.conf file by:
sudo nvidia-xconfig
to get the ball rolling. I saved my configuration file in my “Downloads” folder, then sudo mv’ed it into the /etc/X11/ folder.
I couldn’t just save it using the NVIDIA Utility because I don’t have root privileges outside of terminal.
Thanks again!
Wow Huge thanks! finally someone that knows what they’re talking about with a simple solution. coming over from Windows, just running nvidia-settings as root didn’t occur to me. lesson learned. sudo nvidia-settings make changes apply save configuration file. thank you so much…
When I had this problem (on a completely vanilla installation of Ubuntu 24.04) it had exactly the same behaviour even as root. While making the attempts as root, however, I noticed an extra error message in the terminal where I had executed sudo nvidia-settings: Error executing /usr/share/screen-resolution-extra/nvidia-polkit: Permission denied.
From there I was able to solve the issue by running sudo chmod +x /usr/share/screen-resolution-extra/nvidia-polkit. Once that binary was made executable, the Save to X Configuration File button began working even when not running NVIDIA Settings as root, as it happily provided a popup for its own sudo permissions.
I couldn’t say why that file was not executable already.