<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c22">Comment # 22</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 <span class="vcard"><a class="email" href="mailto:ossi@kde.org" title="Oswald Buddenhagen <ossi@kde.org>"> <span class="fn">Oswald Buddenhagen</span></a>
</span></b>
<pre>many reboots later:
- yes, setting the resolution via the kernel command line clearly sets a mode
the kernel considers non-existent in another place
- i'm pretty sure it was using the digital channel of the dvi connector - i
think sysfs said DVI-D, the monitor said it (dunno what it would say if it got
analog on the dvi port), and it didn't do the usual geometry adjustment when
analog input is used
- yes, hacking away the duallink check fixes it
- i have no clue how to compile the kernel / which switch to set to get the
vbios.rom to pop up in the tree
unrelated to the picked resolution, nouveau often locks up the gpu. but that's
for another report ...</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>