From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 32406] nouveau fails to send hotplug event to ALSA hda hdmi audio
Date: Fri, 27 Feb 2015 00:51:30 +0000 [thread overview]
Message-ID: <bug-32406-8800-cmtP4tlSP3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-32406-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=32406
--- Comment #9 from Kip Warner <Kip-pQI53ePfAtSt/hvpvFFPbQ@public.gmane.org> ---
Hey Ilia,
I can confirm that this is still an issue. In fact, I noticed it not just with
the Nouveau driver (Ubuntu, amd64, 1:1.0.11+git1411032101.3fb97d~gd~u), but
also with the non-free nVidia 346 driver.
In both cases the hotplug notification was not being reported by udevadm (and
presumably the kernel hotplug system either via netlink or script driven). The
card in question was an nVidia GeForce GTX 960.
This may be a hardware issue because plugging in the same HDMI sink (Onkyo
TX-NR535) to my integrated Intel HDMI port emits several hotplug events no
problem on both connect and disconnect.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1627 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2015-02-27 0:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 10:53 [Bug 32406] New: nouveau fails to send hotplug event to ALSA hda hdmi audio bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-32406-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-12-15 11:22 ` [Bug 32406] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-15 11:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-16 0:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-16 11:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-17 23:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-12-18 17:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-01 11:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-27 0:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
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-32406-8800-cmtP4tlSP3@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.