Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 60680] [NV96] HDMI is connected and has mode, TV says "no signal"
Date: Wed, 15 Jan 2014 17:19:26 +0000	[thread overview]
Message-ID: <bug-60680-8800-exZ0aRCdqh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-60680-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 592 bytes --]

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

--- Comment #17 from Pekka Paalanen <ppaalanen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Created attachment 92168
  --> https://bugs.freedesktop.org/attachment.cgi?id=92168&action=edit
Kernel log 3.5.2, HDMI clone ok, drm.debug=0xe

As requested, here is the log from a kernel that lights up the HDMI output
properly.

Laptop booted with HDMI connected and TV on, nouveau module then loaded
manually after boot. Fbcon is cloned to both LVDS and HDMI correctly.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1559 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-01-15 17:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 18:20 [Bug 60680] New: HDMI is connected and has mode, TV says "no signal" bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-60680-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-02-11 18:23   ` [Bug 60680] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-11 18:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-11 18:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-12  8:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-13 20:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-03-27 13:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 23:12   ` [Bug 60680] [NV96] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21  5:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24  8:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-06 12:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-06 14:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-22  9:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-22 19:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-28  6:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-10 10:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 17:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 17:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-01-15 22:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-17  6:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-18  8:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-19 15:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-21 18:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-23  6:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-26 11:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-60680-8800-exZ0aRCdqh@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox