[Nouveau] [Bug 74903] [NV34] TV Load not detected in X

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=74903

--- Comment #3 from Alexandre <alexandre.nunes at gmail.com> ---
(In reply to comment #2)
> 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?

It's off forever. But I can't even reproduce this anymore, please keep reading.
> 
> 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.

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140212/eff4c466/attachment.html>