Intel DHA no audio on HDMI: works only after display sleep
I have an Intel NUC (NUC7i3BNH, i.e., using Intel High Definition Audio) running Ubuntu 16.04.3. Its intended use is for a media center. I'm unable to get HDMI audio working unless I allow the system to sit idle (5 minutes by default) long enough for the display to sleep. When the display is woken back up, HDMI audio works perfectly.
Pavucontrol has no effect on the issue. Full system suspend does not fix HDMI audio. I've tried multiple displays, same behavior with each.
Any ideas? Thanks!
sound pulseaudio hdmi intel-nuc
add a comment |
I have an Intel NUC (NUC7i3BNH, i.e., using Intel High Definition Audio) running Ubuntu 16.04.3. Its intended use is for a media center. I'm unable to get HDMI audio working unless I allow the system to sit idle (5 minutes by default) long enough for the display to sleep. When the display is woken back up, HDMI audio works perfectly.
Pavucontrol has no effect on the issue. Full system suspend does not fix HDMI audio. I've tried multiple displays, same behavior with each.
Any ideas? Thanks!
sound pulseaudio hdmi intel-nuc
That's weird. It seems HDMI was not projected 'to sleep'. Look this unsolved 2010-issue. Even on Windows we see complains about it!
– Redbob
Sep 21 '17 at 3:45
Same issue with Zotac CI549.
– Jofre
Oct 8 '17 at 9:56
Not an elegant solution but forcing a screen resolution as explained here askubuntu.com/questions/906266/… worked for me without having to wait for the go to Sleep. I hope I could automate it
– Jofre
Oct 8 '17 at 15:28
Maybe it's just a matter of selecting the right output? Check if my answer here fixes your problem: askubuntu.com/a/1024739/204815
– Lucio Paiva
Apr 13 '18 at 17:30
add a comment |
I have an Intel NUC (NUC7i3BNH, i.e., using Intel High Definition Audio) running Ubuntu 16.04.3. Its intended use is for a media center. I'm unable to get HDMI audio working unless I allow the system to sit idle (5 minutes by default) long enough for the display to sleep. When the display is woken back up, HDMI audio works perfectly.
Pavucontrol has no effect on the issue. Full system suspend does not fix HDMI audio. I've tried multiple displays, same behavior with each.
Any ideas? Thanks!
sound pulseaudio hdmi intel-nuc
I have an Intel NUC (NUC7i3BNH, i.e., using Intel High Definition Audio) running Ubuntu 16.04.3. Its intended use is for a media center. I'm unable to get HDMI audio working unless I allow the system to sit idle (5 minutes by default) long enough for the display to sleep. When the display is woken back up, HDMI audio works perfectly.
Pavucontrol has no effect on the issue. Full system suspend does not fix HDMI audio. I've tried multiple displays, same behavior with each.
Any ideas? Thanks!
sound pulseaudio hdmi intel-nuc
sound pulseaudio hdmi intel-nuc
edited Oct 28 '17 at 10:22
Rael Gugelmin Cunha
3,84512028
3,84512028
asked Aug 14 '17 at 20:34
Alex RawlingsAlex Rawlings
113
113
That's weird. It seems HDMI was not projected 'to sleep'. Look this unsolved 2010-issue. Even on Windows we see complains about it!
– Redbob
Sep 21 '17 at 3:45
Same issue with Zotac CI549.
– Jofre
Oct 8 '17 at 9:56
Not an elegant solution but forcing a screen resolution as explained here askubuntu.com/questions/906266/… worked for me without having to wait for the go to Sleep. I hope I could automate it
– Jofre
Oct 8 '17 at 15:28
Maybe it's just a matter of selecting the right output? Check if my answer here fixes your problem: askubuntu.com/a/1024739/204815
– Lucio Paiva
Apr 13 '18 at 17:30
add a comment |
That's weird. It seems HDMI was not projected 'to sleep'. Look this unsolved 2010-issue. Even on Windows we see complains about it!
– Redbob
Sep 21 '17 at 3:45
Same issue with Zotac CI549.
– Jofre
Oct 8 '17 at 9:56
Not an elegant solution but forcing a screen resolution as explained here askubuntu.com/questions/906266/… worked for me without having to wait for the go to Sleep. I hope I could automate it
– Jofre
Oct 8 '17 at 15:28
Maybe it's just a matter of selecting the right output? Check if my answer here fixes your problem: askubuntu.com/a/1024739/204815
– Lucio Paiva
Apr 13 '18 at 17:30
That's weird. It seems HDMI was not projected 'to sleep'. Look this unsolved 2010-issue. Even on Windows we see complains about it!
– Redbob
Sep 21 '17 at 3:45
That's weird. It seems HDMI was not projected 'to sleep'. Look this unsolved 2010-issue. Even on Windows we see complains about it!
– Redbob
Sep 21 '17 at 3:45
Same issue with Zotac CI549.
– Jofre
Oct 8 '17 at 9:56
Same issue with Zotac CI549.
– Jofre
Oct 8 '17 at 9:56
Not an elegant solution but forcing a screen resolution as explained here askubuntu.com/questions/906266/… worked for me without having to wait for the go to Sleep. I hope I could automate it
– Jofre
Oct 8 '17 at 15:28
Not an elegant solution but forcing a screen resolution as explained here askubuntu.com/questions/906266/… worked for me without having to wait for the go to Sleep. I hope I could automate it
– Jofre
Oct 8 '17 at 15:28
Maybe it's just a matter of selecting the right output? Check if my answer here fixes your problem: askubuntu.com/a/1024739/204815
– Lucio Paiva
Apr 13 '18 at 17:30
Maybe it's just a matter of selecting the right output? Check if my answer here fixes your problem: askubuntu.com/a/1024739/204815
– Lucio Paiva
Apr 13 '18 at 17:30
add a comment |
1 Answer
1
active
oldest
votes
UPDATE: This is fixed in kernel 4.14 and higher.
I have a NUC too (NUC7i5BNK) and this has been a pain.
You can force the display to sleep with /usr/bin/xset dpms force off
command.
I included this line in the required startup script and fixed for my purposes (run as an emulation station, running RetroPie).
RetroPie usually launch stuff using a script called /opt/retropie/supplementary/runcommand/runcommand.sh
, so I've edited this script.
If you want to use Kodi, edit Kodi startup script and before launch it include these 2 lines:
xset dpms force off
xset dpms force on
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f946273%2fintel-dha-no-audio-on-hdmi-works-only-after-display-sleep%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
UPDATE: This is fixed in kernel 4.14 and higher.
I have a NUC too (NUC7i5BNK) and this has been a pain.
You can force the display to sleep with /usr/bin/xset dpms force off
command.
I included this line in the required startup script and fixed for my purposes (run as an emulation station, running RetroPie).
RetroPie usually launch stuff using a script called /opt/retropie/supplementary/runcommand/runcommand.sh
, so I've edited this script.
If you want to use Kodi, edit Kodi startup script and before launch it include these 2 lines:
xset dpms force off
xset dpms force on
add a comment |
UPDATE: This is fixed in kernel 4.14 and higher.
I have a NUC too (NUC7i5BNK) and this has been a pain.
You can force the display to sleep with /usr/bin/xset dpms force off
command.
I included this line in the required startup script and fixed for my purposes (run as an emulation station, running RetroPie).
RetroPie usually launch stuff using a script called /opt/retropie/supplementary/runcommand/runcommand.sh
, so I've edited this script.
If you want to use Kodi, edit Kodi startup script and before launch it include these 2 lines:
xset dpms force off
xset dpms force on
add a comment |
UPDATE: This is fixed in kernel 4.14 and higher.
I have a NUC too (NUC7i5BNK) and this has been a pain.
You can force the display to sleep with /usr/bin/xset dpms force off
command.
I included this line in the required startup script and fixed for my purposes (run as an emulation station, running RetroPie).
RetroPie usually launch stuff using a script called /opt/retropie/supplementary/runcommand/runcommand.sh
, so I've edited this script.
If you want to use Kodi, edit Kodi startup script and before launch it include these 2 lines:
xset dpms force off
xset dpms force on
UPDATE: This is fixed in kernel 4.14 and higher.
I have a NUC too (NUC7i5BNK) and this has been a pain.
You can force the display to sleep with /usr/bin/xset dpms force off
command.
I included this line in the required startup script and fixed for my purposes (run as an emulation station, running RetroPie).
RetroPie usually launch stuff using a script called /opt/retropie/supplementary/runcommand/runcommand.sh
, so I've edited this script.
If you want to use Kodi, edit Kodi startup script and before launch it include these 2 lines:
xset dpms force off
xset dpms force on
edited Jan 2 at 18:16
answered Oct 27 '17 at 16:06
Rael Gugelmin CunhaRael Gugelmin Cunha
3,84512028
3,84512028
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f946273%2fintel-dha-no-audio-on-hdmi-works-only-after-display-sleep%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
That's weird. It seems HDMI was not projected 'to sleep'. Look this unsolved 2010-issue. Even on Windows we see complains about it!
– Redbob
Sep 21 '17 at 3:45
Same issue with Zotac CI549.
– Jofre
Oct 8 '17 at 9:56
Not an elegant solution but forcing a screen resolution as explained here askubuntu.com/questions/906266/… worked for me without having to wait for the go to Sleep. I hope I could automate it
– Jofre
Oct 8 '17 at 15:28
Maybe it's just a matter of selecting the right output? Check if my answer here fixes your problem: askubuntu.com/a/1024739/204815
– Lucio Paiva
Apr 13 '18 at 17:30