On Mon, Mar 31, 2014 at 5:43 PM, Jani Nikula
wrote:
> On Sun, 30 Mar 2014, Kenneth de Mello wrote:
>> What about dual-link DVI? I though the additional link addressed the
>> pixel clock limitation. Has it only been using a single link this entire
>> time, and it's only worked by ignoring the
Jani,
Thank you for explaining further. After checking the manual for my
motherboard, I am mistaken. It specifies DVI-I and states the maximum
resolution over DVI is 1920x1200@60Hz, so it appears all is well. The
fact it worked before is a happy accident.
I have since switched to use displa
On Sun, 30 Mar 2014, Kenneth de Mello wrote:
> What about dual-link DVI? I though the additional link addressed the
> pixel clock limitation. Has it only been using a single link this entire
> time, and it's only worked by ignoring the maximum dotclock, so in other
> words, the fact it works a
Hi Kenneth,
On Sun, 30 March 2014 Kenneth de Mello wrote:
> What about dual-link DVI? I though the additional link addressed the
> pixel clock limitation. Has it only been using a single link this entire
> time, and it's only worked by ignoring the maximum dotclock, so in other
> words, the fa
Bruno,
Thank you for your reply.
What about dual-link DVI? I though the additional link addressed the
pixel clock limitation. Has it only been using a single link this entire
time, and it's only worked by ignoring the maximum dotclock, so in other
words, the fact it works at all is the bug?
Hi Kenneth,
On Fri, 28 March 2014 Kenneth de Mello wrote:
> On my system, the maximum resolution of my monitor, 2560x1440, is no longer
> automatically detected properly with kernel 3.13.7. This worked with
> 3.13.6, and 5 with this hardware and identical kernel configs.Now the
> autodetect
