<div dir="ltr">Hi<br><div class="gmail_extra"><br><br><div class="gmail_quote">On 3 October 2012 23:15, Neil Salstrom <span dir="ltr"><<a href="mailto:salstrom@gmail.com" target="_blank">salstrom@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
</div></div>The 3XX.XX series of Nvidia drivers handles modelines totally<br>
differently. I've not been able to get it working well myself so I'm<br>
on 295.75. I either lose modes or HD-audio (long story there).<br>
<br>
Here is a quote from an email chain I've had going on with an Nvidia developer:<br>
<br>
"There was a significant change to the mode validation process in the<br>
302.* driver series: previously, a "mode" consisted of a set of<br>
"back-end timings," i.e. the timings the GPU actually sent to the<br>
monitor, and "front-end timings," which were reported to the X server.<br>
The front-end timings were basically only used for their height and<br>
width, with the rest of the parameters ignored. That lead to all<br>
kinds of confusion when, for example, programs would calculate and<br>
report the "refresh rate" of the front-end timings, even when that was<br>
a lie and the back-end timings were completely different.<br></blockquote><div><br><br></div><div>Well, I had a deeper look into it, and the above is certainly not what I'm seeing at all.<br><br></div><div>The judder free wiki page works just fine, however there seems to be a bug with NVCtrl X extension, in that the first entry of the available modelines gets overidden from time to time. In which case you can't switch to it.<br>
<br></div><div>I have amended the judder free wiki page with a work-around. I've reported the issue to nvidia, will see what they say.<br></div><div><br></div><div>in the mean time, it works perfectly for me with the modeline workaround..<br>
</div></div></div></div>