<html><br />On Tuesday, March 8, 2016 09:45 CET, Jean-Yves Avenard <jyavenard@gmail.com> wrote:<br /> <blockquote type="cite" cite="CANpj82L3YVea4ZgnG7t9GHBN8sSJHEgYXseiMBj_7f=bwizaFg@mail.gmail.com">Hi<br />...<br />...<div>That's what your problem is then, 50Hz is the closest to 23.93. So myth is doing the right thing as far as its concerned. </div><div> </div><div>Which version of Xrandr do you have installed?</div><div> </div><div>Myth only supports 1.2 or the nvidia X extension(libnvctrl) , but this needs to be installed and present. </div><div>Normally the nvidia installer would install it automatically. </div><div> </div></blockquote>I see this on the nvidia release notes for driver 358.16:<br />Problems that Will Not Be Fixed<br /><br />NV-CONTROL versions 1.8 and 1.9<br />Version 1.8 of the NV-CONTROL X Extension introduced target types for setting and querying attributes as well as receiving event notification on targets. Targets are objects like X Screens, GPUs and Quadro Sync devices. Previously, all attributes were described relative to an X Screen. These new bits of information (target type and target id) were packed in a non-compatible way in the protocol stream such that addressing X Screen 1 or higher would generate an X protocol error when mixing NV-CONTROL client and server versions.<br /><br />This packing problem has been fixed in the NV-CONTROL 1.10 protocol, making it possible for the older (1.7 and prior) clients to communicate with NV-CONTROL 1.10 servers. Furthermore, the NV-CONTROL 1.10 client library has been updated to accommodate the target protocol packing bug when communicating with a 1.8 or 1.9 NV-CONTROL server. This means that the NV-CONTROL 1.10 client library should be able to communicate with any version of the NV-CONTROL server.<br /><br />NVIDIA recommends that NV-CONTROL client applications relink with version 1.10 or later of the NV-CONTROL client library (libXNVCtrl.a, in the nvidia-settings-358.16.tar.bz2 tarball). The version of the client library can be determined by checking the NV_CONTROL_MAJOR and NV_CONTROL_MINOR definitions in the accompanying nv_control.h.<br /><br />The only web released NVIDIA Linux driver that is affected by this problem (i.e., the only driver to use either version 1.8 or 1.9 of the NV-CONTROL X extension) is 1.0-8756.<br /><br />Is that relevant?<br /><br /><br />BR.<br /><br />Marius<br /><br /><br /><br /> </html>