From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 60680] New: HDMI is connected and has mode, TV says "no signal"
Date: Mon, 11 Feb 2013 18:20:18 +0000 [thread overview]
Message-ID: <bug-60680-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2157 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=60680
Priority: medium
Bug ID: 60680
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: HDMI is connected and has mode, TV says "no signal"
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: ppaalanen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: Driver/nouveau
Product: xorg
Created attachment 74633
--> https://bugs.freedesktop.org/attachment.cgi?id=74633&action=edit
kernel log with nouveau.debug=trace, v3.8-rc5-51-g4f84a11
TV does not receive signal when connected via HDMI to my Asus G50V laptop.
Laptop is single-GPU, NV96. xrandr shows HDMI as connected, having a mode, and
it should just work but doesn't. TV does not detect a signal.
LVDS works just fine.
I have tried:
- switching HDMI on and off via xrandr
- setting different video modes with xrandr for the HDMI
- booting with and without HDMI cable connected
- hotplugging HDMI
DDX 1.0.6.
Kernel is the nouveau kernel based on 3.8.0-rc5, v3.8-rc5-51-g4f84a11
commit 4f84a118d8872f21e1d5b78241e0e6f31b79e46b
Author: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date: Tue Feb 5 20:44:19 2013 +0100
drm/nouveau/therm: reduce stack usage of nouveau_therm_ic_ctor
The nvidia proprietary drivers can run the TV via HDMI fine.
This is the first time I am trying to run nouveau with HDMI on this machine.
In the kernel log at timestamp 93, I was in X and ran:
$ xrandr --output LVDS-1 --auto --output HDMI-1 --auto --right-of LVDS-1
Before that X had seemed to set up a clone mode at the laptop panels resolution
also on TV.
Similar bugs:
#37085 - I do not know if my case is a regression, different chips.
#43939 - I am using a real TV, not a DVI monitor.
#56601 - I have not even attempted audio yet, video only.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3705 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2013-02-11 18:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 18:20 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-60680-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-02-11 18:23 ` [Bug 60680] HDMI is connected and has mode, TV says "no signal" 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
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@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.