Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] No sound after hibernation
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Multimedia
View previous topic :: View next topic  
Author Message
Princess Nell
l33t
l33t


Joined: 15 Apr 2005
Posts: 916

PostPosted: Mon Jan 24, 2022 8:39 pm    Post subject: [SOLVED] No sound after hibernation Reply with quote

Kernel 5.15.16, but this may have happened on 5.10.x as well. Installed alsa packages are at version 1.2.4. The card is
Quote:

0 [PCH ]: HDA-Intel - HDA Intel PCH

The system has no sound after coming out of hibernation. The sound card exists and all snd modules are loaded. In this state, after a reboot, there is no sound device at all (lspci |grep -i audio). It only reappears after a shutdown with power off.

Not really sure where to start. After both reboot and hibernation,
Quote:

# alsactl init
alsa-lib /var/tmp/portage/media-libs/alsa-lib-1.2.4/work/alsa-lib-1.2.4/src/ucm/parser.c:260:(error_node) UCM is not supported for this HDA model (HDA Intel PCH at 0xf1240000 irq 127)
alsa-lib /var/tmp/portage/media-libs/alsa-lib-1.2.4/work/alsa-lib-1.2.4/src/ucm/main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
Found hardware: "HDA-Intel" "Realtek ALC293" "HDA:10ec0293,17aa2231,00100003 HDA:80862809,80860101,00100000" "0x17aa" "0x2231"
#

So I looked at UCM, not knowing what it is.
Quote:

# alsaucm list 0
ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.2.4/work/alsa-lib-1.2.4/src/ucm/parser.c:260:(error_node) UCM is not supported for this HDA model (HDA Intel PCH at 0xf1240000 irq 127)
ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.2.4/work/alsa-lib-1.2.4/src/ucm/main.c:1014:(snd_use_case_mgr_open) error: failed to impI don;ort hw:0 use case configuration -6
alsaucm: error failed to open sound card hw:0: No such device or address

I don't think UCM is the problem, but I also think UCM is not set up right. alsa-ucm-conf is installed and I found no usable documentation how to configure it.

As far as I'm aware, powersave is not configured for this device.
Quote:

# cat /sys/module/snd_hda_intel/parameters/power_save
0
# cat /sys/module/snd_hda_intel/parameters/power_save_controller
N
#

Any ideas?


Last edited by Princess Nell on Mon Feb 07, 2022 9:46 pm; edited 1 time in total
Back to top
View user's profile Send private message
Princess Nell
l33t
l33t


Joined: 15 Apr 2005
Posts: 916

PostPosted: Tue Jan 25, 2022 11:51 pm    Post subject: Reply with quote

It looks like I have a workaround, but I don't quite understand it, nor do I know what consequences it may have for using sound on this machine.
Upon inspecting /var/log/messages, I found
Quote:
kernel: snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x20270503
kernel: snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x20270503
kernel: snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to single_cmd mode: last cmd=0x20270503
kernel: snd_hda_codec_generic hdaudioC0D2: Unable to sync register 0x2f0d00. -5
kernel: snd_hda_codec_generic hdaudioC0D2: Unable to sync register 0x2f0d00. -5
kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5
kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

The "azx_get_response timeout" part led me to the kernel docs, alsa-configuration.rst and hd-audio/notes.rst. Both files explain how to use the probe_mask module option.
Normally, /var/log/messages will show this,
Quote:
kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC293: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
kernel: snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
kernel: snd_hda_codec_realtek hdaudioC0D0: hp_outs=2 (0x16/0x15/0x0/0x0/0x0)
kernel: snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
kernel: snd_hda_codec_realtek hdaudioC0D0: inputs:
kernel: snd_hda_codec_realtek hdaudioC0D0: Dock Mic=0x19
kernel: snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a
kernel: snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
kernel: snd_hda_codec_generic hdaudioC0D2: autoconfig for Generic: line_outs=0 (0x0/0x0/0x0/0x0/0x0) type:line
kernel: snd_hda_codec_generic hdaudioC0D2: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
kernel: snd_hda_codec_generic hdaudioC0D2: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
kernel: snd_hda_codec_generic hdaudioC0D2: mono: mono_out=0x0
kernel: snd_hda_codec_generic hdaudioC0D2: dig-out=0x3/0x0
kernel: snd_hda_codec_generic hdaudioC0D2: inputs:

i.e. initializaton of the two codecs,
Quote:
# grep Codec /proc/asound/card0/codec#*
/proc/asound/card0/codec#0:Codec: Realtek ALC293
/proc/asound/card0/codec#2:Codec: Intel Generic
#

What fixes my problem now is
Quote:
# grep mask /etc/modprobe.d/alsa.conf
options snd-hda-intel probe_mask=1
#

This leads to the Generic codec no longer being autoconfigured, i.e. the "snd_hda_codec_generic" lines in the second log excerpt above no longer appear.
Sound keeps working through hibernation now, user is happy. But what is the impact of no longer having the Generic codec available? What does "type:line" mean/control?
I also found that for some reason, enabling CONFIG_SND_DEBUG and CONFIG_SND_DEBUG_VERBOSE has not created any additional output in /var/log/messages or dmesg.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Multimedia All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum