Omdat kabouters (gnomen) niet zo goed kunnen tellen
Van:
http://wiki.archlinux.org/index.php/How_to_install_NVIDIA_driver#Why_is_the_refresh_rate_not_reported_correctly_by_utilities_that_use_the_XRandR_X_extension_.28e.g..2C_the_GNOME_.22Screen_Resolution_Preferences.22_panel.2C_.60xrandr_-q.60.2C_etc.29.3FWhy is the refresh rate not reported correctly by utilities that use the XRandR X extension (e.g., the GNOME "Screen Resolution Preferences" panel, `xrandr -q`, etc)?
The XRandR X extension is not presently aware of multiple display devices on a single X screen; it only sees the MetaMode bounding box, which may contain one or more actual modes. This means that if multiple MetaModes have the same bounding box, XRandR will not be able to distinguish between them.
In order to support DynamicTwinView, the NVIDIA X driver must make each MetaMode appear to be unique to XRandR. Presently, the NVIDIA X driver accomplishes this by using the refresh rate as a unique identifier.
You can use `nvidia-settings -q RefreshRate` to query the actual refresh rate on each display device.
The XRandR extension is currently being redesigned by the X.Org community, so the refresh rate workaround may be removed at some point in the future.
This workaround can also be disabled by setting the "DynamicTwinView" X configuration option to FALSE, which will disable NV-CONTROL support for manipulating MetaModes, but will cause the XRandR and XF86VidMode visible refresh rate to be accurate.
