From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99041] HDMI Audio not working after fixing HDMI.
Date: Thu, 16 Jul 2015 09:32:17 +0000 [thread overview]
Message-ID: <bug-99041-2300-kvSEXTP7EH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-99041-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=99041
--- Comment #1 from Florent Le Coz <louiz@louiz.org> ---
The issue is still present on kernel 4.0.7.
Little precision, that may be useful to diagnose the problem:
- If I boot with that HDMI-connected screen turned off and then I turn it on
with my X session already fully started, it is not automatically detected (the
screen says “no signal”), but this used to work on older versions of linux
(can’t remember which one introduced this “regression”).
Next, if I manually configure it with that command:
xrandr --output DVI-0 --mode 1920x1080 --output DVI-1 --right-of DVI-0 --mode
1920x1080 --output HDMI-0 --right-of DVI-1 --mode 1920x1080
the image on the screen works, but not the sound.
- However, if I boot while that screen is already turned on (or if I turn it on
while still on the gdm login screen), it is automatically detected and both the
image AND the sound BOTH work immediately.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-07-16 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 15:25 [Bug 99041] New: HDMI Audio not working after fixing HDMI bugzilla-daemon
2015-07-16 9:32 ` bugzilla-daemon [this message]
2015-10-08 10:54 ` [Bug 99041] " bugzilla-daemon
2015-10-30 20:05 ` bugzilla-daemon
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-99041-2300-kvSEXTP7EH@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).