Cannot set refresh rate other than 60 Hz, xrandr reports false frequency

[Ansus]

After automatic Xorg reconfiguring I cannot set refresh rate other than 60 Hz.

Before reconfiguring I had had 60 Hz after boot but could start nvidia-settings and set the rate to 76Hz. gnome-diasplay-settings did not allow setting any refresh rate than 53 Hz.

Now I cannot do even this. With empty xorg gnome-diasplay-settings suggest setting any rate up to 100 Hz but nothing happens: the refresh rate still 60 Hz. nvidia-settings does not start at all. When using my old xorg.conf nvidia-settings can be started, and I can select 76 Hz, but nothing happens again: the rate still remains 60 Hz. xrandr does nbot help either: it says "Rate x Hz not available for this size" for any rate higher than 53 Hz.

If to set this option
    Option "DynamicTwinView" "False"

Then xrandr reports the following:
   1280x1024 76.0* 75.0 60.0 72.0
   1280x960 60.0
   1152x864 75.0 70.0 60.0
   1024x768 75.0 70.0 60.0
   960x600 60.0
   960x540 60.0
   896x672 60.0
   840x525 75.0 70.0 60.0
   832x624 75.0
   800x600 75.0 72.0 60.0 56.0 65.0
   800x512 60.0
   720x450 60.0
   700x525 75.0 70.0 60.0
   680x384 60.0
   640x512 75.0 60.0
   640x480 75.0 73.0 60.0
   640x350 70.0
   576x432 75.0 70.0 60.0
   512x384 75.0 70.0 60.0
   416x312 75.0
   400x300 75.0 72.0 60.0 56.0
   320x240 75.0 73.0 60.0

But real refresh rate as reported by monitor still remains 60 Hz.

This is under Ubuntu Intrepid

See screencast:
http://verger1.narod.ru/refresh.ogv

[Bryce Harrington (bryce)]

Hi neptunia,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

[Bryce Harrington (bryce)]

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[mirak (mirak-mirak)]

I have this bug in Ubuntu 13.04 while i don't have this problem in ubuntu 12.04 and 12.10.

[mirak (mirak-mirak)]

With nvidia gpu and no mater wich driver I choose

[mirak (mirak-mirak)]

closing a bug report is certainly not a way to resolv the bugs ...