slgvr01
December 23, 2024, 12:35am
1
After updating to kernel 6.12.5-200.fc41.x84_64 my audio stopped working, I have the “Dummy Output” as my output device in the sound settings. Here is some information that might be useful:
inxi -bAE output:
System:
Host: bender Kernel: 6.12.5-200.fc41.x86_64 arch: x86_64 bits: 64
Desktop: GNOME v: 47.2 Distro: Fedora Linux 41 (Workstation Edition)
Machine:
Type: Laptop System: Acer product: Swift SF314-54 v: V1.18
serial: <superuser required>
Mobo: KBL model: Strongbow_KL v: V1.18 serial: <superuser required>
UEFI: Insyde v: 1.18 date: 10/08/2021
Battery:
ID-1: BAT0 charge: 17.3 Wh (52.1%) condition: 33.2/50.8 Wh (65.3%)
volts: 15.1 min: 15.3
CPU:
Info: dual core Intel Core i3-8130U [MT MCP] speed (MHz): avg: 3400
min/max: 400/3400
Graphics:
Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
Device-2: Sunplus Innovation HD User Facing driver: uvcvideo type: USB
Display: wayland server: X.Org v: 24.1.4 with: Xwayland v: 24.1.4
compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: iris gpu: i915 resolution: 1920x1080~60Hz
API: OpenGL v: 4.6 vendor: intel mesa v: 24.2.8 renderer: Mesa Intel UHD
Graphics 620 (KBL GT2)
Audio:
Device-1: Intel Sunrise Point-LP HD Audio driver: snd_soc_avs
API: ALSA v: k6.12.5-200.fc41.x86_64 status: kernel-api
Server-1: PipeWire v: 1.2.7 status: active
Network:
Device-1: Intel Wireless 7265 driver: iwlwifi
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb type: USB
Report: btmgmt ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: 14:4F:8A:56:B6:6A bt-v: 4.2
Drives:
Local Storage: total: 238.47 GiB used: 133.42 GiB (55.9%)
Info:
Memory: total: 8 GiB available: 7.63 GiB used: 3.1 GiB (40.6%)
Processes: 282 Uptime: 48m Shell: Bash inxi: 3.3.36
wpctl status output:
PipeWire 'pipewire-0' [1.2.7, sasha@bender, cookie:824453487]
└─ Clients:
32. xdg-desktop-portal [1.2.7, sasha@bender, pid:2754]
33. WirePlumber [1.2.7, sasha@bender, pid:27739]
34. pipewire [1.2.7, sasha@bender, pid:27740]
35. Mutter [1.2.7, sasha@bender, pid:2163]
36. Firefox [1.2.7, sasha@bender, pid:2]
49. WirePlumber [export] [1.2.7, sasha@bender, pid:27739]
65. gnome-shell [1.2.7, sasha@bender, pid:2163]
66. GNOME Shell Volume Control [1.2.7, sasha@bender, pid:2163]
67. GNOME Volume Control Media Keys [1.2.7, sasha@bender, pid:2284]
68. GNOME Settings [1.2.7, sasha@bender, pid:49467]
76. wpctl [1.2.7, sasha@bender, pid:55903]
Audio
├─ Devices:
│ 50. Built-in Audio [alsa]
│ 51. Built-in Audio [alsa]
│ 52. Built-in Audio [alsa]
│ 53. Compress-Offload device (ALSA card 2) [alsa:compressed]
│
├─ Sinks:
│ * 62. Dummy Output [vol: 0.57]
│
├─ Sources:
│
├─ Filters:
│
└─ Streams:
70. GNOME Settings
69. monitor_FL
71. input_FR < Dummy Output:monitor_FR [active]
74. monitor_FR
75. input_FL < Dummy Output:monitor_FL [active]
Video
├─ Devices:
│ 47. HD User Facing [v4l2]
│ 57. HD User Facing [v4l2]
│ 61. HD User Facing: HD User Facing [libcamera]
│
├─ Sinks:
│
├─ Sources:
│ * 60. HD User Facing (V4L2)
│
├─ Filters:
│
└─ Streams:
Settings
└─ Default Configured Devices:
1. Audio/Source alsa_input.platform-skl_hda_dsp_generic.HiFi__hw_hdadsp_7__source
If possible I would prefer to not have to fall to an older version of the kernel, I’d like to know if there is an alternative solution to the problem. Thanks.
ilikelinux
December 23, 2024, 11:09pm
2
This would be important if you like to use your audio straight away and also if you not want to loose your working kernel. Because on a kernel update you will preserve the running kernel.
And using an older kernel is not a big risk if you not use it over month.
You can also set an other default boot kernel that you not have manually to change it.
There are a few steps to do, which you can replete after a failed new kernel upgrade.
ilikelinux
December 23, 2024, 11:14pm
3
To see if an older kernel works is also important to find out the culprit of your problem.
slgvr01
December 24, 2024, 10:05am
4
I just switched to the older 6.11.11-300.fc41.x86_64 kernel that works fine and checked the driver used for the audio.
Audio:
Device-1: Intel Sunrise Point-LP HD Audio driver: snd_soc_skl
API: ALSA v: k6.11.11-300.fc41.x86_64 status: kernel-api
Server-1: PipeWire v: 1.2.7 status: active
The driver used is different and the PipeWire version is the same.
1 Like
ilikelinux
December 24, 2024, 11:51am
5
I changed the Title of your request. This way is visible what has changed.
New:
I could find a few articles in internet but not found a workaround for the newest kernel.
Can you please test this:
Based on your dmesg logs, it seems that snd_soc_avs and snd_hda_intel try to control the same devices, probably causing some form of race condition. This would explain why your speakers work occasionally.
You may try disabling the snd_soc_avs module on boot.
Start by checking without persisting, by editing your Linux options on boot. When using systemd-boot, you can press e to edit the options. Add module_blacklist=snd_soc_avs to the kernel options line.
To persist the change, create /etc/modprobe.d/disable_snd_soc_avs.conf with the content:
# Prevent loading the `snd_soc_avs` module to fix speaker issue
# due to a race with `snd_hda_intel`.
# See <https://superuser.com/questions/1845508/dell-xps-9550-speakers-only-detected-some-of-the-time-when-booting-arch-linux>
blacklist snd_soc_avs
source: audio - Dell XPS 9550 speakers only detected some of the time when booting Arch Linux - Super User
slgvr01
December 24, 2024, 12:48pm
6
I have GRUB but the steps seem to be the same, so I did it. I added module_blacklist=snd_soc_avs to the kernel options line and after booting I checked the driver used for the audio:
Audio:
Device-1: Intel Sunrise Point-LP HD Audio driver: N/A
API: ALSA v: k6.12.5-200.fc41.x86_64 status: kernel-api
Server-1: PipeWire v: 1.2.7 status: active
I don’t think I did the steps wrong, but I can try again and show you a picture if you want.
1 Like
ilikelinux
December 24, 2024, 5:50pm
7
Let’s have a look what we do have installed/used:
dmesg | grep snd
Can you please post the output as pre formated text </>?
It looks like that the snd_soc_skl is missing.
slgvr01
December 25, 2024, 12:38am
8
Yeah sure, here’s the output (it’s a bit long):
[ 6.116854] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SST driver
[ 6.280950] snd_soc_avs 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 6.394772] snd_hda_codec_realtek hdaudioB0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 6.394780] snd_hda_codec_realtek hdaudioB0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 6.394784] snd_hda_codec_realtek hdaudioB0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 6.394787] snd_hda_codec_realtek hdaudioB0D0: mono: mono_out=0x0
[ 6.394789] snd_hda_codec_realtek hdaudioB0D0: inputs:
[ 6.394791] snd_hda_codec_realtek hdaudioB0D0: Internal Mic=0x1a
[ 6.394793] snd_hda_codec_realtek hdaudioB0D0: Headset Mic=0x19
[ 6.397922] snd_hda_codec_realtek hdaudioB0D0: creating for ALC256 Analog 0
[ 6.397930] snd_hda_codec_realtek hdaudioB0D0: creating for ALC256 Alt Analog 1
[ 6.397933] snd_hda_codec_realtek hdaudioB0D0: skipping playback dai for ALC256 Alt Analog
[ 6.604179] snd_soc_avs 0000:00:1f.3: Direct firmware load for intel/avs/hda-10ec0256-tplg.bin failed with error -2
[ 6.604186] snd_soc_avs 0000:00:1f.3: request topology "intel/avs/hda-10ec0256-tplg.bin" failed: -2
[ 6.682343] snd_hda_codec_hdmi hdaudioB0D2: creating for HDMI 0 0
[ 6.682350] snd_hda_codec_hdmi hdaudioB0D2: skipping capture dai for HDMI 0
[ 6.682352] snd_hda_codec_hdmi hdaudioB0D2: creating for HDMI 1 1
[ 6.682355] snd_hda_codec_hdmi hdaudioB0D2: skipping capture dai for HDMI 1
[ 6.682357] snd_hda_codec_hdmi hdaudioB0D2: creating for HDMI 2 2
[ 6.682360] snd_hda_codec_hdmi hdaudioB0D2: skipping capture dai for HDMI 2
[ 6.682543] snd_soc_avs 0000:00:1f.3: Direct firmware load for intel/avs/hda-8086280b-tplg.bin failed with error -2
[ 6.682547] snd_soc_avs 0000:00:1f.3: request topology "intel/avs/hda-8086280b-tplg.bin" failed: -2
[ 16.930084] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.930090] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.930093] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.930153] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.930156] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.930364] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.930367] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.930369] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.930422] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.930424] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.933490] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.933495] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.933498] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.933571] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.933574] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.933799] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.933801] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.933804] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.933856] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.933858] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.934558] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.934563] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.934565] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.934636] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.934639] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.936604] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.936610] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.936613] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.936680] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.936683] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.936884] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.936886] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.936888] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.936939] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.936942] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.937166] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.937168] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.937170] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.937221] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.937224] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.937403] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.937405] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.937407] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.937459] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.937462] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.938214] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.938220] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.938223] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.938278] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.938280] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.939018] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.939023] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.939026] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.939077] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.939080] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.939361] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.939364] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.939366] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.939407] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.939410] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.939721] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.939724] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.939726] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.940620] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.940625] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.940937] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.940941] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.940943] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.941000] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.941003] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.941832] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.941838] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.941842] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.941899] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.941901] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.942748] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.942753] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.942756] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.942816] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.942819] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.943120] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.943123] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.943125] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.943180] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.943182] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.943724] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.943728] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.943731] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.943789] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.943792] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.945615] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.945620] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.945622] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.945689] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.945692] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 16.946528] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 16.946534] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 16.946537] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 16.946618] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 16.946621] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.112272] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.112277] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.112279] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.112390] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.112393] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.112574] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.112576] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.112577] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.112631] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.112633] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.112834] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.112836] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.112837] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.112886] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.112888] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.113040] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.113042] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.113043] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.113101] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.113102] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.114008] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.114012] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.114014] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.114063] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.114064] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.114650] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.114652] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.114654] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.114703] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.114704] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.114864] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.114866] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.114867] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.114915] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.114916] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.115105] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.115106] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.115107] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.115152] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.115153] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.115297] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.115299] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.115300] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.115345] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.115346] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.116007] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.116010] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.116012] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.116062] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.116063] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.116651] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.116654] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.116655] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.116703] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.116704] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.116910] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.116912] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.116913] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.116963] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.116964] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.117196] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.117198] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.117199] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.117244] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.117245] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.117447] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.117449] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.117450] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.117497] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.117498] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.118194] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.118198] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.118199] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.118250] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.118252] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.118922] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.118925] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.118927] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.118975] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.118976] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.119199] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.119201] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.119202] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.119247] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.119248] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.119500] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.119502] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.119503] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.119549] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.119550] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.119767] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.119769] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.119770] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.119815] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.119816] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[ 33.120533] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[ 33.120536] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[ 33.120538] snd_soc_avs 0000:00:1f.3: error creating module -2
[ 33.120588] snd_soc_avs 0000:00:1f.3: create path failed: -2
[ 33.120590] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
ilikelinux
December 25, 2024, 1:55am
9
When you made
dmesg | grep snd
was the snd_soc_avs still blacklisted? If yes try to undo the blacklist entry and see if the errors in the dmesg are gone.
It is just that we do have enough information to file a bug. Have you done this already once? Otherwise I can help you to file one.
slgvr01
December 25, 2024, 3:16am
10
snd_soc_avs was not blacklisted. I had already performed a reboot before seeing your response, so the change to the kernel options was no longer in effect. Also, I just updated to the new 6.12.6-200.fc41.x86_64 kernel, and the issue persists.
No, I’ve never filed a bug.
lnegron
December 25, 2024, 4:00am
11
I found this today as I’ve been looking for a solution to the same problem since the weekend but I never had looked at the kernel. I booted from rescue and audio worked, then I tried the 6.11 kernel and it work but none of the two 6.12.x* kernel versions I have work. I tried blacklisting snd_soc_avs on boot using the e option but that didn’t work. For now I guess my best bet is to try future kernel updates as they come out? I’m running Fedora 41 on a chromebook lava which is not the best vehicle but I like challenges. I have installed the audio drivers for it from the WeirdTreeThing on github and they work but the kernel update simply doesn’t see my soundcard. I apologize I’m all over the place, I’ve never posted before.
ilikelinux
December 25, 2024, 9:49am
12
Welcome to Fedora @lnegron
Can you please also check if it is the snd_soc_skl where is missing in your case. If you follow the instructions above you will see what I mean.
Btw. there is a new kernel released 6.12.6 (I am still on F40 with the main system), I updated today. Do not forget to change in a working kernel before upgrade, otherwise you will loose the possibility of booting in to the working kernel.
Can you please also give the information of inxi -bAE to see if we talk more or less about the same setup.
slgvr01
December 25, 2024, 1:05pm
13
Yes, we have the exact same problem. I guess waiting for new kernel updates is the only option at this point.
ilikelinux
December 25, 2024, 2:42pm
14
If nobody makes a bug report you can wait long. As I understood was _skl for analogue audio while _avs is for digital. This means if you depend on the _skl module you will have to look for an alternative ton install this when it gets kicked from the kernel.
grumpey
December 25, 2024, 8:18pm
15
Do you have alsa or alsa-sof firmware installed?sudo dnf list alsa-\*firmware\*
It might be worth trying if it is not.
slgvr01
December 25, 2024, 10:18pm
16
I just checked and I do have alsa-sof-firmware.noarch installed, version 2024.09.2-2.fc41.
pavethem
January 11, 2025, 4:33pm
17
Same problem here on my Acer SF315-52 laptop ever since 6.12 dropped.link
I suppose this has something to do with the kernel removing legacy sound drivers and replacing them with avs, which doesn’t work for our kaby lake architecture however. (phoronix ).snd-intel-dspcfg dsp_driver to go back to the old way does not work either. Neither does blacklisting avs. The only thing that does get sound back is going back to the legacy legacy drivers with options snd-intel-dspcfg dsp_driver=1, but I was never able to get the microphone working with those.
I would gladly file a bug, alas I’m unsure against what. alsa-ucm? avs-topology? the kernel?cp /usr/share/alsa/ucm2/conf.d/avs_dmic/Acer-Lars-1.0.conf /usr/share/alsa/ucm2/conf.d/avs_dmic/avs_dmic.conf, I’m leaning towards a missing ucm file for the laptop speakers, but I would appreciate any pointers in the right direction.
1 Like
slgvr01
January 26, 2025, 8:00pm
18
Have you opened an issue? If not I could try
pavethem
January 27, 2025, 12:09pm
19
I have filed a bug against alsa-ucm, but haven’t gotten a response yet…bug report
There appears to be a pull request created recently however which might benefit us: link
1 Like
slgvr01
January 28, 2025, 4:50pm
20
Thank you, let’s hope for a solution soon!