<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [NV44] dual-link tmds no longer allowed" href="https://bugs.freedesktop.org/show_bug.cgi?id=40747#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [NV44] dual-link tmds no longer allowed" href="https://bugs.freedesktop.org/show_bug.cgi?id=40747">bug 40747</a> from <a class="email" href="mailto:ossi@kde.org" title="Oswald Buddenhagen <ossi@kde.org>"> Oswald Buddenhagen</a> <pre>huh? i said that it is *easy* to convince the kernel to pick the right mode. it's picking a wrong one only automatically. there is no hardware limitation at all here. X appears more tenacious, apparently because it filters out the good mode earlier in the process. it's beyond me why it does that - it makes no sense at all, and the log doesn't indicate anything afaics. this also puts a weird twist on the meaning of _K_MS ... also note that i'm a different person than the OP. i just happen to have pretty much the same configuration (card and monitor) and consequently the same problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>