All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 56601] New: 9600m GT HDMI output no video or audio.
Date: Wed, 31 Oct 2012 05:02:16 +0000	[thread overview]
Message-ID: <bug-56601-8800@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 56601
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: 9600m GT HDMI output no video or audio.
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: vekinn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/DRI/nouveau
           Product: Mesa

Created attachment 69340
  --> https://bugs.freedesktop.org/attachment.cgi?id=69340&action=edit
xorg log

Video output is blank and no audio on HDMI output after connecting tv and
running xrandr --auto

Works on nvidia blob.

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

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

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

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

             reply	other threads:[~2012-10-31  5:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31  5:02 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-56601-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-10-31  5:03   ` [Bug 56601] 9600m GT HDMI output no video or audio bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-01 19:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-01 23:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-01 23:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-01 23:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-01 23:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-01 23:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-12  7:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-24 23:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-26 23:19   ` 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-56601-8800@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.