You are not logged in.

#1 2021-10-16 22:20:07

Markon101
Member
Registered: 2021-10-16
Posts: 3

Nvidia Driver 470.74 sets refresh rate to 24hz every reboot SOLVED

Hi everyone. I have run into quite the annoying issue with my new Arch install. My Nvidia driver keeps setting my refresh rate to 24hz every time I reboot or login to Gnome! I have tried a variety of fixes including trying this command I figured out reading the Man page for nvidia-settings.

 nvidia-settings -a [gpu:0]/RefreshRate[SCREEN-0]=60 

But this has no effect on my refresh rate. I also tried RefreshRate3 but that didn't work either. I can manually change the setting each time I boot in the nvidia-settings GUI without issue. However, because I was trying to write a script to get around this issue I was attempting to change the settings from the terminal and use a custom Systemd service on boot to load a script that runs that command.

Here is my xorg.conf

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 470.74

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 470.74

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "SONY TV  *02"
    HorizSync       14.0 - 70.0
    VertRefresh     48.0 - 62.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVIDIA GeForce GTX 1080 Ti"
    BusID          "PCI:1:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "3840x2160_60 +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Thank you all for looking over my issue. I hope it can help others with similar issues. Maybe it is just a bug in the driver. Please let me know if you are experiencing something like this with version 470.74 of the NVIDIA drivers!

Last edited by Markon101 (2021-10-17 17:57:04)

Offline

#2 2021-10-16 22:53:19

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,656

Re: Nvidia Driver 470.74 sets refresh rate to 24hz every reboot SOLVED

Remove that xorg conf as it doesn't do anything of use and maybe enable early KMS: https://wiki.archlinux.org/title/NVIDIA#Early_loading

Offline

#3 2021-10-17 06:36:08

seth
Member
Registered: 2012-09-03
Posts: 50,983

Re: Nvidia Driver 470.74 sets refresh rate to 24hz every reboot SOLVED

Also, how do you determine the refresh rate? What's the output of "xrandr -q"?

Offline

#4 2021-10-17 16:13:46

Markon101
Member
Registered: 2021-10-16
Posts: 3

Re: Nvidia Driver 470.74 sets refresh rate to 24hz every reboot SOLVED

xrandr -q gives me the following (after manually setting the 60hz in Nvidia settings GUI)

Screen 0: minimum 8 x 8, current 3840 x 2160, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 950mm x 540mm
   1920x1080     60.00 +  59.94    50.00    29.97    23.98    60.05    60.00    50.04  
   4096x2160     59.94    50.00    24.00    23.98  
   3840x2160     59.94*   50.00    29.97    25.00    23.98  
   1680x1050     59.95  
   1600x900      60.00  
   1280x1024     60.02  
   1280x720      60.00    59.94    50.00    29.97    23.98  
   1152x864      75.00  
   1024x768      60.00  
   800x600       60.32  
   720x576       50.00  
   720x480       59.94  
   640x480       59.94    59.93  
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)
DVI-D-1-0 disconnected (normal left inverted right x axis y axis)
HDMI-1-0 disconnected (normal left inverted right x axis y axis)
DP-1-0 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-2 disconnected (normal left inverted right x axis y axis)
DP-1-3 disconnected (normal left inverted right x axis y axis)
DP-1-4 disconnected (normal left inverted right x axis y axis)
DP-1-5 disconnected (normal left inverted right x axis y axis)

I also found this on Nvidia's website. Nvidia Documentation

The display settings I configured in nvidia-settings do not persist.
	

Depending on the type of configuration being performed, nvidia-settings will save configuration changes to one of several places:

    Static X server configuration changes are saved to the X configuration file (e.g. /etc/X11/xorg.conf). These settings are loaded by the X server when it starts, and cannot be changed without restarting X.

    Dynamic, user-specific configuration changes are saved to ~/.nvidia-settings-rc. nvidia-settings loads this file and applies any settings contained within. These settings can be changed without restarting the X server, and can typically be configured through the nvidia-settings command line interface as well, or via the RandR and/or NV-CONTROL APIs.

    User-specific application profiles edited in nvidia-settings are saved to ~/.nv/nvidia-application-profiles-rc. This file is loaded along with the other files in the application profile search path by the NVIDIA OpenGL driver when it is loaded by an OpenGL application. The driver evaluates the application profiles to determine which settings apply to the application. Changes made to this configuration file while an application is already running will be applied when the application is next restarted. See Appendix J, Application Profiles for more information about application profiles.

Settings in ~/.nvidia-settings-rc only take effect when processed by nvidia-settings, and therefore will not be loaded by default when starting a new X session. To load settings from ~/.nvidia-settings-rc without actually opening the nvidia-settings control panel, use the --load-config-only option on the nvidia-settings command line. nvidia-settings --load-config-only can be added to your login scripts to ensure that your settings are restored when starting a new desktop session.

Even after nvidia-settings has been run to restore any settings set in ~/.nvidia-settings-rc, some desktop environments (e.g. GNOME, KDE, Unity, Xfce) include advanced display configuration tools that may override settings that were configured via nvidia-settings. These tools may attempt to restore their own display configuration when starting a new desktop session, or when events such as display hotplugs, resolution changes, or VT switches occur.

These tools may also override some types of settings that are stored in and loaded from the X configuration file, such as any MetaMode strings that may specify the initial display layouts of NVIDIA X screens. Although the configuration of the initial MetaMode is static, it is possible to dynamically switch to a different MetaMode after X has started. This can have the effect of making the set of active displays, their resolutions, and layout positions as configured in the nvidia-settings control panel appear to be ineffective, when in reality, this configuration was active when starting X and then overridden later by the desktop environment.

If you believe that your desktop environment is overriding settings that you configured in nvidia-settings, some possible solutions are:

    Use the display configuration tools provided as part of the desktop environment (e.g. gnome-control-center display, gnome-display-properties, kcmshell4 display, unity-control-center display, xfce4-display-settings) to configure your displays, instead of the nvidia-settings control panel or the xrandr command line tool. Setting your desired configuration using the desktop environment's tools should cause that configuration to be the one which is restored when the desktop environment overrides the existing configuration from nvidia-settings. If you are not sure which tools your desktop environment uses for display configuration, you may be able to discover them by navigating any available system menus for "Display" or "Monitor" control panels.

    For settings loaded from ~/.nvidia-settings-rc which have been overridden, run nvidia-settings --load-config-only as needed to reload the settings from ~/.nvidia-settings-rc.

    Disable any features your desktop environment may have for managing displays. (Note: this may disable other features, such as display configuration tools that are integrated into the desktop.)

    Use a different desktop environment which does not actively manage display configuration, or do not use any desktop environment at all.

Some systems may have multiple different display configuration utilities, each with its own way of managing settings. In addition to conflicting with nvidia-settings, such tools may conflict with each other. If your system uses more than one tool for configuring displays, make sure to check the configuration of each tool when attempting to determine the source of any unexpected display settings.

And here is my .nvidia-settings-rc file.

#
# /home/anon/.nvidia-settings-rc
#
# Configuration file for nvidia-settings - the NVIDIA X Server Settings utility
# Generated on Sun Oct 17 12:08:27 2021
#

# ConfigProperties:

RcFileLocale = C
DisplayStatusBar = Yes
SliderTextEntries = Yes
IncludeDisplayNameInConfigFile = No
ShowQuitDialog = Yes
UpdateRulesOnProfileNameChange = Yes
Timer = PowerMizer_Monitor_(GPU_1),Yes,1000
Timer = Thermal_Monitor_(GPU_1),Yes,1000
Timer = Memory_Used_(GPU_1),Yes,3000
Timer = PowerMizer_Monitor_(GPU_0),Yes,1000
Timer = Thermal_Monitor_(GPU_0),Yes,1000
Timer = Memory_Used_(GPU_0),Yes,3000

# Attributes:

0/SyncToVBlank=1
0/LogAniso=0
0/FSAA=0
0/TextureClamping=1
0/FXAA=0
0/AllowFlipping=1
0/FSAAAppControlled=1
0/LogAnisoAppControlled=1
0/OpenGLImageSettings=1
0/FSAAAppEnhanced=0
0/ShowGraphicsVisualIndicator=0
0/XVideoSyncToDisplayID=HDMI-0
[DPY:DVI-D-0]/Dithering=0
[DPY:DVI-D-0]/DitheringMode=0
[DPY:DVI-D-0]/DitheringDepth=0
[DPY:DVI-D-0]/ColorSpace=0
[DPY:DVI-D-0]/ColorRange=0
[DPY:DVI-D-0]/SynchronousPaletteUpdates=0
[DPY:HDMI-0]/RedBrightness=0.000000
[DPY:HDMI-0]/RefreshRate3=60
[DPY:HDMI-0]/GreenBrightness=0.000000
[DPY:HDMI-0]/BlueBrightness=0.000000
[DPY:HDMI-0]/RedContrast=0.000000
[DPY:HDMI-0]/GreenContrast=0.000000
[DPY:HDMI-0]/BlueContrast=0.000000
[DPY:HDMI-0]/RedGamma=1.000000
[DPY:HDMI-0]/GreenGamma=1.000000
[DPY:HDMI-0]/BlueGamma=1.000000
[DPY:HDMI-0]/Dithering=0
[DPY:HDMI-0]/DitheringMode=0
[DPY:HDMI-0]/DitheringDepth=0
[DPY:HDMI-0]/DigitalVibrance=0
[DPY:HDMI-0]/ColorSpace=0
[DPY:HDMI-0]/ColorRange=0
[DPY:HDMI-0]/SynchronousPaletteUpdates=0
[DPY:DP-0]/Dithering=0
[DPY:DP-0]/DitheringMode=0
[DPY:DP-0]/DitheringDepth=0
[DPY:DP-0]/ColorSpace=0
[DPY:DP-0]/ColorRange=0
[DPY:DP-0]/SynchronousPaletteUpdates=0
[DPY:DP-1]/Dithering=0
[DPY:DP-1]/DitheringMode=0
[DPY:DP-1]/DitheringDepth=0
[DPY:DP-1]/ColorSpace=0
[DPY:DP-1]/ColorRange=0
[DPY:DP-1]/SynchronousPaletteUpdates=0
[DPY:DP-2]/Dithering=0
[DPY:DP-2]/DitheringMode=0
[DPY:DP-2]/DitheringDepth=0
[DPY:DP-2]/ColorSpace=0
[DPY:DP-2]/ColorRange=0
[DPY:DP-2]/SynchronousPaletteUpdates=0
[DPY:DP-3]/Dithering=0
[DPY:DP-3]/DitheringMode=0
[DPY:DP-3]/DitheringDepth=0
[DPY:DP-3]/ColorSpace=0
[DPY:DP-3]/ColorRange=0
[DPY:DP-3]/SynchronousPaletteUpdates=0
[DPY:DP-4]/Dithering=0
[DPY:DP-4]/DitheringMode=0
[DPY:DP-4]/DitheringDepth=0
[DPY:DP-4]/ColorSpace=0
[DPY:DP-4]/ColorRange=0
[DPY:DP-4]/SynchronousPaletteUpdates=0
[DPY:DP-5]/Dithering=0
[DPY:DP-5]/DitheringMode=0
[DPY:DP-5]/DitheringDepth=0
[DPY:DP-5]/ColorSpace=0
[DPY:DP-5]/ColorRange=0
[DPY:DP-5]/SynchronousPaletteUpdates=0
[DPY:DVI-D-1-0]/Dithering=0
[DPY:DVI-D-1-0]/DitheringMode=0
[DPY:DVI-D-1-0]/DitheringDepth=0
[DPY:DVI-D-1-0]/ColorSpace=0
[DPY:DVI-D-1-0]/ColorRange=0
[DPY:DVI-D-1-0]/SynchronousPaletteUpdates=0
[DPY:HDMI-1-0]/Dithering=0
[DPY:HDMI-1-0]/DitheringMode=0
[DPY:HDMI-1-0]/DitheringDepth=0
[DPY:HDMI-1-0]/ColorSpace=0
[DPY:HDMI-1-0]/ColorRange=0
[DPY:HDMI-1-0]/SynchronousPaletteUpdates=0
[DPY:DP-1-0]/Dithering=0
[DPY:DP-1-0]/DitheringMode=0
[DPY:DP-1-0]/DitheringDepth=0
[DPY:DP-1-0]/ColorSpace=0
[DPY:DP-1-0]/ColorRange=0
[DPY:DP-1-0]/SynchronousPaletteUpdates=0
[DPY:DP-1-1]/Dithering=0
[DPY:DP-1-1]/DitheringMode=0
[DPY:DP-1-1]/DitheringDepth=0
[DPY:DP-1-1]/ColorSpace=0
[DPY:DP-1-1]/ColorRange=0
[DPY:DP-1-1]/SynchronousPaletteUpdates=0
[DPY:DP-1-2]/Dithering=0
[DPY:DP-1-2]/DitheringMode=0
[DPY:DP-1-2]/DitheringDepth=0
[DPY:DP-1-2]/ColorSpace=0
[DPY:DP-1-2]/ColorRange=0
[DPY:DP-1-2]/SynchronousPaletteUpdates=0
[DPY:DP-1-3]/Dithering=0
[DPY:DP-1-3]/DitheringMode=0
[DPY:DP-1-3]/DitheringDepth=0
[DPY:DP-1-3]/ColorSpace=0
[DPY:DP-1-3]/ColorRange=0
[DPY:DP-1-3]/SynchronousPaletteUpdates=0
[DPY:DP-1-4]/Dithering=0
[DPY:DP-1-4]/DitheringMode=0
[DPY:DP-1-4]/DitheringDepth=0
[DPY:DP-1-4]/ColorSpace=0
[DPY:DP-1-4]/ColorRange=0
[DPY:DP-1-4]/SynchronousPaletteUpdates=0
[DPY:DP-1-5]/Dithering=0
[DPY:DP-1-5]/DitheringMode=0
[DPY:DP-1-5]/DitheringDepth=0
[DPY:DP-1-5]/ColorSpace=0
[DPY:DP-1-5]/ColorRange=0
[DPY:DP-1-5]/SynchronousPaletteUpdates=0

EDIT: This thread can now be marked solved. The issue was solved by going into the Gnome display settings GUI and setting the refresh rate from there! I can't believe I didn't think of that sooner. So Gnome's display manager was overriding Nvidia's settings every time I logged in. I hope that helps if anyone else runs into this or a similar issue!

Last edited by Markon101 (2021-10-17 16:28:11)

Offline

#5 2021-10-17 16:50:21

seth
Member
Registered: 2012-09-03
Posts: 50,983

Re: Nvidia Driver 470.74 sets refresh rate to 24hz every reboot SOLVED

Ftr the default resolution announced by the EDID is 1920x1080 @60.00Hz.

To mark resolved threads, edit your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

Board footer

Powered by FluxBB