From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 31957] Video Noise on HDMI output
Date: Mon, 29 Nov 2010 04:44:30 -0800 (PST) [thread overview]
Message-ID: <20101129124430.CB73F13004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-31957-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=31957
--- Comment #1 from Francisco Jerez <currojerez-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org> 2010-11-29 04:44:30 PST ---
(In reply to comment #0)
> When the nouveau driver is used, bright whites have noise in them.
> The picture is steady for all other colours.
> Replacing the driver with the nvidia closed source one, the HDMI works fine. So
> all cables must be OK, it must be a driver bug.
> I suspect a HDCP problem. How do I tell if HDCP has negotiated correctly or not
> with the nouveau driver?
> If I use the nouveau driver, but instead with the DVI connector, and connect it
> to an analogue VGA adapter to the same TV display unit, the output is fine with
> no noise.
Can you reboot with "drm.debug=4" in your kernel command line and attach the
full output from "dmesg"?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-11-29 12:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 10:56 [Bug 31957] New: Video Noise on HDMI output bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-31957-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-11-29 12:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2010-11-29 19:28 ` [Bug 31957] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-29 19:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-29 19:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-02 14:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-03 10:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-03 21:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-03 22:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-04 13:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-05 11:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-09 19:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-09 19:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-09 19:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-09 20:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-09 21:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-10 12:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-10 12:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-12 17:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-12 20:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-14 12:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` 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=20101129124430.CB73F13004F@annarchy.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.