<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [NV34] TV Load not detected in X"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74903#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [NV34] TV Load not detected in X"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74903">bug 74903</a>
from <span class="vcard"><a class="email" href="mailto:alexandre.nunes@gmail.com" title="Alexandre <alexandre.nunes@gmail.com>"> <span class="fn">Alexandre</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=74903#c2">comment #2</a>)
<span class="quote">> What happens if you're in X (with the image off) and then try to switch back
> to the console? Does it come on, or is it off forever?</span >
It's off forever. But I can't even reproduce this anymore, please keep reading.
<span class="quote">>
> I don't see any relevant changes between 3.11.2 and 3.11.6... would be very
> interesitng to know what causes the additional regression -- it should be a
> pretty fast bisect, if you're up for it.</span >
In fact, it's worse: It seems intermitent. I can only get there about 1 in 3
attempts if I cold boot (w kernel 3.11.2, I suspect newer kernels could be the
same thing) (i.e. turn the power off and on again), but never if I just reboot
after getting the "blue screen" from tv.
But here is the strange thing: I tested on another tv and it's ok. Since this
problematic tv only hits this bug on KMS (intermitent)/xserver w/
nouveau(always happens as far as I've observed), but not on console or vesa fb,
I suspect it could be related to load detection.
I tried booting with param video=TV1:e as (poorly) documented way to force tv
on. dmesg log and X log now plays nice as if the tv was indeed connected,
however, I can't see anything past kms trigger.
Is there a way to truly override load detection? As I said, the other tv is
just fine, the dmesg shows tv connected.</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>