[Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

Also see askubuntu question: https://askubuntu.com/questions/944735/silent-hdmi-sound-with-nuc6cayh-16-04?noredirect=1#comment1505598_944735

I was slightly surprised to see the word "Broxton" since Intel canceled that product line before it was ever released. However that just seems to be an incorrect label arising from multiple Intel product lines sharing chipsets... The system is really a J3455 (Apollo Lake) and shares some silicon with the Broxton line.

Still, since you have a very new system you might find success in using a newer kernel. So try installing package 'linux-image-generic-hwe-16.04-edge'. If that does not solve the problem then please try the very latest from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12.8/

I have the same exact issue!

I don't know if this will help, but as long as the HDMI audio isn't working, my TV will display the Dolby symbol, followed by a capital D when pressing the OK button (It is an LG 47LH7020). Once I get it to work by restarting the TV, or switching input modes, the symbol is gone and the audio works until a restart.

It also happens in Zesty and Artful, by the way.

Status changed to 'Confirmed' because the bug affects multiple users.

Dear Community,

I can confirm that the same thing happens for ASRock ITX motherboard with Intel's J4205 CPU connected to Samsung TV.

Since I want to give Linux a go and not buy another OS from M$ - it is a bit disappointing that we have to use tricks to get a pretty basic thing to work.

Does anyone knows if this issue will be fixed in 17.10?

Is there an information I could provide to make it easier to fix the issue?

BR
Adam

Ironically, the first information we would ask for is for someone to test 17.10:

  http://cdimages.ubuntu.com/daily-live/current/

and tell us if it fixes the issue :)

Also we would ask someone who experiences the problem to test a different brand of TV other than Samsung.

Hi All,

Daniel, I have made a clean install of 17.10 from the link you have provided.
Problem is present in the newest version too.
As Oliver wrote before - it is also an issue with LG's.

Thanks.

Come to think of it, this is quite possibly a kernel issue. So adding a kernel task.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1709708

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

I was close to submit missing log file.
The command returned that I am not the owner of this bug (translated from Polish :)

How I can contribute?
I would be really happy to get the HDMI working properly on my ASRock J4205-ITX.
I know it is not a major issue nor the hardware popular - but Win10 works out-of-the-box.

Hi,

It seems that newest kernel candidate (from http://kernel.ubuntu.com/) v4.14-rc5 mainline build fixes the sound issue. But on the other end it kills LAN :)

Regards
Adam

Interesting to see Intel released a firmware update specifically for HDMI on the NUC. If you can boot Windows to install it then it might be worth trying for NUC owners like Neilen...

https://downloadcenter.intel.com/download/26609/NUCs-HDMI-2-0-Firmware-Update-Tool-for-Intel-NUC-Kit-NUC7i3BN-NUC7i5BN-NUC7i7BN-NUC6CAY?product=95062

... but I mostly still expect this is a Linux kernel bug that applies to all manufacturers.

The firmware updates have no effect on this issue, Daniel! (It would've been nice though...)

The Intel firmware upgrade is intended only for HDMI 2.0 displays. And, interestingly, you can install it only if NUC is attached to a HDMI 2.0 device.

@Rael: I thought so too, but it upgraded just fine on a <2.0 HDMI cable and TV! (afaik)

@Olivier, I installed a Win10 yesterday with no activation key, and ran the upgrader tool in a old HDMI TV, and the upgrader said it cannot upgrade (according the PDF is because my TV is not HDMI 2).

Anyway, I ran a workaround: edited pulseaudio config to power off the display for 1 second and my sound is now working (at least for the applications I'm running).

@Rael That is odd. My TV and cable are way too old to be 2.0 (circa 2008-2009 I believe) and yet the firmware went through and the version number changed. Then again the 2.0 update doesn’t fix anything for this issue. I am also using the 1 second workaround for now!

Well, to be honest, it was your tip about the dpms that I followed! Thanks!

I just made a bit different: I've added a line to the xset call in the pulseaudio startup script (the sleep call was not required, just the xset one). Details here: https://askubuntu.com/a/969935/138621

And now sound is working on retroarch! Again, thanks!

Can you try which is the first version of v4.14-rc* that fixes the issue?

It is v4.14-rc4 which produced sound without playing with pulseaudio or restarting display.

This commit fixes the issue:

commit 2d8f63297b9f0b430c96329893667c0bfdcbd47e
Author: Jani Nikula <email address hidden>
Date: Tue Sep 19 18:38:13 2017 +0300

    drm/i915: always update ELD connector type after get modes

    drm_edid_to_eld() initializes the connector ELD to zero, overwriting the
    ELD connector type initialized in intel_audio_codec_enable(). If
    userspace does getconnector and thus get_modes after modeset, a
    subsequent audio component i915_audio_component_get_eld() call will
    receive an ELD without the connector type properly set. It's fine for
    HDMI, but screws up audio for DP.

    Always set the ELD connector type at intel_connector_update_modes()
    based on the connector type. We can drop the connector type update from
    intel_audio_codec_enable().

    Credits to Joseph Nuzman <email address hidden> for figuring this out.

    Cc: Ville Syrjälä <email address hidden>
    Cc: Joseph Nuzman <email address hidden>
    Reported-by: Joseph Nuzman <email address hidden>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101583
    Reviewed-by: Ville Syrjälä <email address hidden>
    Tested-by: Joseph Nuzman <email address hidden>
    Cc: <email address hidden> # v4.10+, maybe earlier
    Signed-off-by: Jani Nikula <email address hidden>
    Link: https://patchwork<email address hidden>
    (cherry picked from commit d81fb7fd9436e81fda67e5bc8ed0713aa28d3db2)
    Signed-off-by: Rodrigo Vivi <email address hidden>

It has "Cc: <email address hidden>" so it'll get pulled into Ubuntu's kernel.

I'm using the X-Swat PPA (https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates) with mesa 17.2.3-0ubuntu0~16.04.0. Should I purge it in order to receive the fix?

> On 4 Nov 2017, at 7:29 PM, Rael Gugelmin Cunha <email address hidden> wrote:
>
> I'm using the X-Swat PPA
> (https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates) with mesa
> 17.2.3-0ubuntu0~16.04.0. Should I purge it in order to receive the fix?

This fix comes from kernel side, so downgrade Mesa or not should not affect it.
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1709708
>
> Title:
> [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
> produces no sound on an HDMI TV until power cycled.
>
> Status in DRI:
> Fix Released
> Status in linux package in Ubuntu:
> Triaged
> Status in pulseaudio package in Ubuntu:
> Invalid
>
> Bug description:
> Upon bootup, the HDMI output connected to a Samsung TV shows up as an
> output. If this output is selected and a sound test run (either using
> the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
> sound is heard. Pavumeter does however show sound coming through.
>
> I found that sound can be fixed by allowing the display to sleep,
> waking it up, and then restarting pulseaudio (pulseaudio -k). After
> that sound output through HDMI to the TV will work until rebooted.
>
> The fix can be succesfully scripted as follows:
>
> xset dpms force off
> sleep 1
> pulseaudio -k
>
> The machine is an Intel NUC6CAYH, connected to a not particularly new
> Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
> 16.04.
>
> In earlier attempts at fixing the issue I set pulseaudio to never let
> the sound device sleep (commented out load-module module-suspend-on-
> idle in /etc/pulse/default.pa), and also set the default sampling rate
> to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
> sure if these settings contributed to the fix, but they are not
> sufficient on their own.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: pulseaudio 1:8.0-0ubuntu3.3
> ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
> Uname: Linux 4.10.0-30-generic x86_64
> ApportVersion: 2.20.1-0ubuntu2.10
> Architecture: amd64
> Date: Wed Aug 9 21:48:39 2017
> InstallationDate: Installed on 2017-08-06 (2 days ago)
> InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
> SourcePackage: pulseaudio
> Symptom: audio
> Symptom_Card: HDA-Intel - HDA Intel PCH
> Symptom_Jack: Digital Out, HDMI
> Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect card
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 11/24/2016
> dmi.bios.vendor: Intel Corp.
> dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
> dmi.board.name: NUC6CAYB
> dmi.board.vendor: Intel Corporation
> dmi.board.version: J23203-402
> dmi.chassis.type: 3
> dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
> modified.conffile..etc.pulse.daemon.conf: [modified]
> modified.conffile..etc.pulse.default.pa: [modified]
> mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22...