You are not logged in.

#1 2022-04-19 00:57:12

jmrushing
Member
Registered: 2022-04-19
Posts: 4

No audio from HDMI - "Monitor plugged-in, Failed to power up codec"

Looking for some help getting audio working from the HDMI port of this Gen 10 Intel i3 NUC. This is a fresh Arch install per the official install guide. This is a very minimal install, no GUI, pulseaudio, etc. I'm using the stock Arch kernel 5.17.3-arch1-1

On boot I get the error:

 
[    3.090708] snd_hda_codec_hdmi hdaudioC0D2: Monitor plugged-in, Failed to power up codec ret=[-13]

Trying speaker-test yields:

speaker-test 1.2.6

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
Playback open error: -2,No such file or directory

dmesg | grep snd_hda:

[    3.033019] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[    3.033366] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    3.090708] snd_hda_codec_hdmi hdaudioC0D2: Monitor plugged-in, Failed to power up codec ret=[-13]

lspci | grep Audio:

00:1f.3 Audio device: Intel Corporation Comet Lake PCH-LP cAVS

Here's a link to the output of my alsa-info.txt

Perhaps coincidentally, I had a very similar experience with this NUC last year while testing with Clear Linux. You can read about that outcome here. I tried my earlier solution that worked in Clear (i.e. manually assigning pins in a firmware patch for the snd-hda-intel module) but that didn't work on this fresh Arch install. So maybe the solution lies elsewhere?

Let me know if any additional information is needed. Any help would be greatly appreciated.

Offline

#2 2022-04-19 06:48:27

seth
Member
Registered: 2012-09-03
Posts: 29,957

Offline

#3 2022-04-19 23:12:24

jmrushing
Member
Registered: 2022-04-19
Posts: 4

Re: No audio from HDMI - "Monitor plugged-in, Failed to power up codec"

@seth

An attempt with the

snd_hda_intel.enable_silent_stream=0

kernel parameter isn't recognized by snd_hda_intel, as reflected in the dmesg:

[    0.000000] Command line: root=UUID=eba125f7-0d6d-4114-bd32-85e996abf7fe rw initrd=intel-ucode.img initrd=initramfs-linux.img snd_hda_intel.enable_silent_stream=0
[    0.042651] Kernel command line: root=UUID=eba125f7-0d6d-4114-bd32-85e996abf7fe rw initrd=intel-ucode.img initrd=initramfs-linux.img snd_hda_intel.enable_silent_stream=0
[    3.005963] snd_hda_intel: unknown parameter 'enable_silent_stream' ignored
[    3.006076] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[    3.006306] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    3.055908] snd_hda_codec_hdmi hdaudioC0D2: Monitor plugged-in, Failed to power up codec ret=[-13]

And an attempt with

snd_hda_codec_hdmi.enable_silent_stream=0

seems to have cleared the "Failed to power up codec error", but audio is still not working.

dmesg:

[    0.000000] Command line: root=UUID=eba125f7-0d6d-4114-bd32-85e996abf7fe rw initrd=intel-ucode.img initrd=initramfs-linux.img snd_hda_codec_hdmi.enable_silent_stream=0
[    0.042774] Kernel command line: root=UUID=eba125f7-0d6d-4114-bd32-85e996abf7fe rw initrd=intel-ucode.img initrd=initramfs-linux.img snd_hda_codec_hdmi.enable_silent_stream=0
[    2.903483] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[    2.903817] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

speaker-test gives same error as before:

speaker-test 1.2.6

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
Playback open error: -2,No such file or directory

Where should I look next?

Offline

#4 2022-04-21 13:12:07

seth
Member
Registered: 2012-09-03
Posts: 29,957

Re: No audio from HDMI - "Monitor plugged-in, Failed to power up codec"

That error doesn't necessarily imply an issue w/ the HDMI output

aplay -l
aplay -L

Offline

#5 2022-04-25 23:38:35

jmrushing
Member
Registered: 2022-04-19
Posts: 4

Re: No audio from HDMI - "Monitor plugged-in, Failed to power up codec"

Sorry for the late response.

Here's aplay -l:

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

and aplay -L:

null
Discard all samples (playback) or generate zero samples (capture)
hdmi:CARD=PCH,DEV=0
HDA Intel PCH, HDMI 0
HDMI Audio Output
hdmi:CARD=PCH,DEV=1
HDA Intel PCH, HDMI 1
HDMI Audio Output
hdmi:CARD=PCH,DEV=2
HDA Intel PCH, HDMI 2
HDMI Audio Output
hdmi:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 3
HDMI Audio Output
hdmi:CARD=PCH,DEV=4
HDA Intel PCH, HDMI 4
HDMI Audio Output

Also, did some googling and managed to get speaker test working with

speaker-test -D hw:0,3 -c2

.
However, I tested this both with and without the

snd_hda_codec_hdmi.enable_silent_stream=0

kernel parameter, and it works in both cases. So, even though the silent stream parameter clears the dmesg error, I'm not sure what it's actually doing beyond that. Is the kernel parameter even necessary?

Offline

#6 2022-04-26 06:38:45

seth
Member
Registered: 2012-09-03
Posts: 29,957

Re: No audio from HDMI - "Monitor plugged-in, Failed to power up codec"

Is the kernel parameter even necessary?

No, it's just to keep the output permanently used. If there's no functional failure, the error doesn't matter.

~/.asoundrc

pcm.!default {
    type hw
    card 0
    device 3
}

Or do you have a bogus (systemwide?) asoundrc that results in the wrong device being selected?

Offline

#7 2022-04-26 07:27:25

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 16,513

Re: No audio from HDMI - "Monitor plugged-in, Failed to power up codec"

ALSA/dmix defaults to hw:0,0 which is why an unconfigured speaker-test fails

The above config would fix speaker-test but lead to not showing the default node in aplay -L which can trip some applications (firefox being a notorious example) and will disable dmix which means you'd only have one application playing sound at a time. The minimal config you can do while keeping these things intact is  a

defaults.pcm.device 3

Note that if you ever intend to setup pulseaudio or pipewire you should remove any of these configs and opt for pulseaudio-alsa/pipewire-alsa respectively.

Offline

#8 2022-04-26 20:53:07

jmrushing
Member
Registered: 2022-04-19
Posts: 4

Re: No audio from HDMI - "Monitor plugged-in, Failed to power up codec"

Thanks for the clarification. I did not already have an .asoundrc or /etc/asound.conf in place for just that reason that V1del pointed out - I will (eventually) be installing pulseaudio. But wanted to pause before moving forward with that in case this "Failed to power up codec" issue was stopping audio from functioning through the HDMI port. Obviously, I misinterpreted the speaker-test error as being related to the codec error. It seems it was simply a case of ALSA defaulting to hw:0,0 (which doesn't match any available card/device mapping from the aplay -l results).

The ALSA page on the official Arch wiki is a little misleading in this respect. It assumes that ALSA will work "out-of-the-box":

udev will automatically detect your hardware and select needed drivers at boot time, therefore, your sound should already be working.

In my experience, the statement "your sound should already be working" is almost never true when using ALSA.

But my personal gripes aside, I think I will move forward with installing pulseaudio & pulseaudio-alsa and testing my application's sound from there. Assuming that the error in my original post is safe to ignore, I'll leave out the silent stream kernel param and see what happens.

Offline

Board footer

Powered by FluxBB