<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 17 April 2013 00:59, Mike Perkins <span dir="ltr"><<a href="mailto:mikep@randomtraveller.org.uk" target="_blank">mikep@randomtraveller.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I thought that with the latest versions of the nvidia drivers you had to use funky artificial refresh rates to get the ones you wanted, not to specify them as you have above? (ie an integer starting, IIRC, at 50, 51...)<span class="HOEnZb"><font color="#888888"><br>
</font></span><span class="HOEnZb"></span><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><br></blockquote></blockquote><div><br></div><div>The refresh rates still appears as some fancy number in xrandr.<br>
</div><div>But as I wrote earlier, myth uses the NVCtrl interface to determine the actual refresh rate from the modeline.<br></div><div>so it doesn't matter what xrandr returns, myth doesn't use that info when possible. <br>
</div></div></div></div>