- Alsa-devel - mailman.alsa-project.org

Lenovo Yoga Pro 7 built-in speakers volume not controlled by GNOME/PipeWire
by GitHub issues - edited 18 Nov '25

18 Nov '25

alsa-project/alsa-ucm-conf issue #642 was edited from 2O77: Device: Lenovo Yoga Pro 14 14IMH9 Sound card: sof-hda-dsp Problem: ALSA Post-Mixer / Pre-Mixer controls work via alsamixer, but GNOME volume slider or PipeWire sink volume does not affect hardware output. Likely an issue in the UCM profile for this device. Steps to reproduce: 1. Boot any Linux distribution. 2. Attempt to change volume via GNOME/KDE slider or `pactl` / PipeWire controls. 3. Observe that output volume of laptop speakers does not change. 4. Testing with headphones (AirPods, Beats) or external speakers works correctly. Notes: - This issue is specific to the built-in laptop speakers. - Different desktop environments (GNOME, KDE) and distributions (Fedora GNOME, Fedora KDE, openSUSE Tumbleweed) were tested and exhibit the same problem. - ALSA `Post-Mixer` / `Pre-Mixer` controls work correctly when adjusted via `alsamixer`. Expected behavior: - GNOME / PipeWire slider should affect the actual hardware output volume of the laptop speakers. Suggested area: - UCM profile for sof-hda-dsp on this Lenovo model may need adjustment. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/642 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Lenovo Yoga Pro 14 built-in speakers volume not controlled by GNOME/PipeWire
by GitHub issues - edited 17 Nov '25

17 Nov '25

alsa-project/alsa-ucm-conf issue #642 was edited from 2O77: Device: Lenovo Yoga Pro 14 14IMH9 Sound card: sof-hda-dsp Problem: ALSA Post-Mixer / Pre-Mixer controls work via alsamixer, but GNOME volume slider or PipeWire sink volume does not affect hardware output. Likely an issue in the UCM profile for this device. Steps to reproduce: 1. Boot any Linux distribution. 2. Attempt to change volume via GNOME/KDE slider or `pactl` / PipeWire controls. 3. Observe that output volume of laptop speakers does not change. 4. Testing with headphones (AirPods, Beats) or external speakers works correctly. Notes: - This issue is specific to the built-in laptop speakers. - Different desktop environments (GNOME, KDE) and distributions (Fedora GNOME, Fedora KDE, openSUSE Tumbleweed) were tested and exhibit the same problem. - ALSA `Post-Mixer` / `Pre-Mixer` controls work correctly when adjusted via `alsamixer`. Expected behavior: - GNOME / PipeWire slider should affect the actual hardware output volume of the laptop speakers. Suggested area: - UCM profile for sof-hda-dsp on this Lenovo model may need adjustment. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/642 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Lenovo Yoga Pro 14 built-in speakers volume not controlled by GNOME/PipeWire
by GitHub issues - edited 17 Nov '25

17 Nov '25

alsa-project/alsa-ucm-conf issue #642 was edited from 2O77: Device: Lenovo Yoga Pro 14 14IMH9 Sound card: sof-hda-dsp Problem: ALSA Post-Mixer / Pre-Mixer controls work via alsamixer, but GNOME volume slider or PipeWire sink volume does not affect hardware output. Likely an issue in the UCM profile for this device. Steps to reproduce: 1. Boot any Linux distribution. 2. Attempt to change volume via GNOME slider or `pactl` / PipeWire controls. 3. Observe that output volume of laptop speakers does not change. 4. Testing with headphones (AirPods, Beats) or external speakers works correctly. Notes: - This issue is specific to the built-in laptop speakers. - Different desktop environments (GNOME, KDE) and distributions (Fedora GNOME, Fedora KDE, openSUSE Tumbleweed) were tested and exhibit the same problem. - ALSA `Post-Mixer` / `Pre-Mixer` controls work correctly when adjusted via `alsamixer`. Expected behavior: - GNOME / PipeWire slider should affect the actual hardware output volume of the laptop speakers. Suggested area: - UCM profile for sof-hda-dsp on this Lenovo model may need adjustment. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/642 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Lenovo Yoga Pro 14 built-in speakers volume not controlled by GNOME/PipeWire
by GitHub issues - edited 17 Nov '25

17 Nov '25

alsa-project/alsa-ucm-conf issue #642 was edited from 2O77: Device: Lenovo Yoga Pro 14 14IMH9 Sound card: sof-hda-dsp Problem: ALSA Post-Mixer / Pre-Mixer controls work via alsamixer, but GNOME volume slider or PipeWire sink volume does not affect hardware output. Likely an issue in the UCM profile for this device. Steps to reproduce: 1. Boot any Linux distribution. I tested on Fedora (GNOME and KDE) and openSUSE Tumbleweed, but it will probably occur on other distros or desktop environments as well. 2. Attempt to change volume via GNOME slider or `pactl` / PipeWire controls. 3. Observe that output volume of laptop speakers does not change. 4. Testing with headphones (AirPods, Beats) or external speakers works correctly. Notes: - This issue is specific to the built-in laptop speakers. - Different desktop environments (GNOME, KDE) and distributions (Fedora GNOME, Fedora KDE, openSUSE Tumbleweed) were tested and exhibit the same problem. - ALSA `Post-Mixer` / `Pre-Mixer` controls work correctly when adjusted via `alsamixer`. Expected behavior: - GNOME / PipeWire slider should affect the actual hardware output volume of the laptop speakers. Suggested area: - UCM profile for sof-hda-dsp on this Lenovo model may need adjustment. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/642 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Lenovo Yoga Pro 14 built-in speakers volume not controlled by GNOME/PipeWire
by GitHub issues - opened 17 Nov '25

17 Nov '25

alsa-project/alsa-ucm-conf issue #642 was opened from 2O77: Device: Lenovo Yoga Pro 14 14IMH9 Sound card: sof-hda-dsp Problem: ALSA Post-Mixer / Pre-Mixer controls work via alsamixer, but GNOME volume slider or PipeWire sink volume does not affect hardware output. Likely an issue in the UCM profile for this device. Steps to reproduce: 1. Boot Fedora (GNOME or KDE) or openSUSE Tumbleweed. 2. Attempt to change volume via GNOME slider or `pactl` / PipeWire controls. 3. Observe that output volume of laptop speakers does not change. 4. Testing with headphones (AirPods, Beats) or external speakers works correctly. Notes: - This issue is specific to the built-in laptop speakers. - Different desktop environments (GNOME, KDE) and distributions (Fedora GNOME, Fedora KDE, openSUSE Tumbleweed) were tested and exhibit the same problem. - ALSA `Post-Mixer` / `Pre-Mixer` controls work correctly when adjusted via `alsamixer`. Expected behavior: - GNOME / PipeWire slider should affect the actual hardware output volume of the laptop speakers. Suggested area: - UCM profile for sof-hda-dsp on this Lenovo model may need adjustment. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/642 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

[PATCH v2] ASoC: SDCA: bug fix while parsing mipi-sdca-control-cn-list
by Niranjan H Y 17 Nov '25

17 Nov '25

"struct sdca_control" declares "values" field as integer array. But the memory allocated to it is of char array. This causes crash for sdca_parse_function API. This patch addresses the issue by allocating correct data size. Signed-off-by: Niranjan H Y <niranjan.hy(a)ti.com> --- v2: - use kcalloc instead of kzalloc --- sound/soc/sdca/sdca_functions.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sound/soc/sdca/sdca_functions.c b/sound/soc/sdca/sdca_functions.c index b2e3fab9b..49b98fe2d 100644 --- a/sound/soc/sdca/sdca_functions.c +++ b/sound/soc/sdca/sdca_functions.c @@ -950,7 +950,8 @@ static int find_sdca_entity_control(struct device *dev, struct sdca_entity *enti return ret; } - control->values = devm_kzalloc(dev, hweight64(control->cn_list), GFP_KERNEL); + control->values = devm_kcalloc(dev, hweight64(control->cn_list), + sizeof(int), GFP_KERNEL); if (!control->values) return -ENOMEM; -- 2.25.1

4 3

[PATCH 5.10] ASoC: SOF: Intel: hda: Fix potential buffer overflow by snprintf()
by Alexandra Diupina 17 Nov '25

17 Nov '25

From: Takashi Iwai <tiwai(a)suse.de> commit 94c1ceb043c1a002de9649bb630c8e8347645982 upstream. snprintf() returns the would-be-filled size when the string overflows the given buffer size, hence using this value may result in the buffer overflow (although it's unrealistic). This patch replaces with a safer version, scnprintf() for papering over such a potential issue. Fixes: 29c8e4398f02 ("ASoC: SOF: Intel: hda: add extended rom status dump to error log") Signed-off-by: Takashi Iwai <tiwai(a)suse.de> Link: https://lore.kernel.org/r/20220801165420.25978-4-tiwai@suse.de Signed-off-by: Mark Brown <broonie(a)kernel.org> Signed-off-by: Alexandra Diupina <adiupina(a)astralinux.ru> --- Backport fix for CVE-2022-50050 sound/soc/sof/intel/hda.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/soc/sof/intel/hda.c b/sound/soc/sof/intel/hda.c index b4cc72483137..1d879c2b81e1 100644 --- a/sound/soc/sof/intel/hda.c +++ b/sound/soc/sof/intel/hda.c @@ -437,7 +437,7 @@ static void hda_dsp_dump_ext_rom_status(struct snd_sof_dev *sdev) for (i = 0; i < HDA_EXT_ROM_STATUS_SIZE; i++) { value = snd_sof_dsp_read(sdev, HDA_DSP_BAR, HDA_DSP_SRAM_REG_ROM_STATUS + i * 0x4); - len += snprintf(msg + len, sizeof(msg) - len, " 0x%x", value); + len += scnprintf(msg + len, sizeof(msg) - len, " 0x%x", value); } sof_dev_dbg_or_err(sdev->dev, hda->boot_iteration == HDA_FW_BOOT_ATTEMPTS, -- 2.30.2

1 0

snd-loopback does not work
by GitHub issues - edited 17 Nov '25

17 Nov '25

alsa-project/alsa-lib issue #482 was edited from Sameguyy: ``` $pactl list short sources 80 alsa_output.platform-snd_aloop.0.analog-stereo.monitor PipeWire s32le 2ch 48000Hz RUNNING 81 alsa_input.platform-snd_aloop.0.analog-stereo PipeWire s32le 2ch 48000Hz RUNNING ``` These are two interfaces that Pipewire automatically pulled in, and the sound goes into 3.0 and doesn't leave from 3.1 That is, I play a sound on hw:3.0 and when I try to read something from hw:3.1 I get silence aplay\arecord records silence $ uname -r 6.17.8-arch1-1 Wayland PipeWire gnome ```$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: DACX6 [DAC-X6], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: DACX6 [DAC-X6], device 1: USB Audio [USB Audio #1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [SAMSUNG] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 3: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 3: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 ``` ``` $pacman -Q | grep alsa alsa-card-profiles 1:1.4.9-1 alsa-lib 1.2.14-2 alsa-plugins 1:1.2.12-5 alsa-topology-conf 1.2.5.1-4 alsa-ucm-conf 1.2.14-2 alsa-utils 1.2.14-1 lib32-alsa-lib 1.2.14-2 lib32-alsa-plugins 1.2.12-1 vlc-plugin-alsa 3.0.21-31 ``` Issue URL : https://github.com/alsa-project/alsa-lib/issues/482 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

snd-loopback does not work
by GitHub issues - edited 17 Nov '25

17 Nov '25

alsa-project/alsa-lib issue #482 was edited from Sameguyy: ``` $pactl list short sources 80 alsa_output.platform-snd_aloop.0.analog-stereo.monitor PipeWire s32le 2ch 48000Hz RUNNING 81 alsa_input.platform-snd_aloop.0.analog-stereo PipeWire s32le 2ch 48000Hz RUNNING ``` These are two interfaces that Pipewire automatically pulled in, and the sound goes into 3.0 and doesn't leave from 3.1 That is, I play a sound on hw:3.0 and when I try to read something from hw:3.1 I get silence aplay\arecord records silence $ uname -r 6.17.8-arch1-1 Wayland PipeWire gnome ```$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: DACX6 [DAC-X6], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: DACX6 [DAC-X6], device 1: USB Audio [USB Audio #1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [SAMSUNG] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 3: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 3: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 ``` Issue URL : https://github.com/alsa-project/alsa-lib/issues/482 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

snd-loopback does not work
by GitHub issues - edited 17 Nov '25

17 Nov '25

alsa-project/alsa-lib issue #482 was edited from Sameguyy: ``` $pactl list short sources 80 alsa_output.platform-snd_aloop.0.analog-stereo.monitor PipeWire s32le 2ch 48000Hz RUNNING 81 alsa_input.platform-snd_aloop.0.analog-stereo PipeWire s32le 2ch 48000Hz RUNNING ``` These are two interfaces that Pipewire automatically pulled in, and the sound goes into 3.0 and doesn't leave from 3.1 That is, I play a sound on hw:3.0 and when I try to read something from hw:3.1 I get silence aplay\arecord records silence $ uname -r 6.17.8-arch1-1 Wayland PipeWire gnome ```$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: DACX6 [DAC-X6], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: DACX6 [DAC-X6], device 1: USB Audio [USB Audio #1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [SAMSUNG] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 3: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 3: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 ``` I don't understand what I'm doing wrong can sm1 guess Issue URL : https://github.com/alsa-project/alsa-lib/issues/482 Repository URL: https://github.com/alsa-project/alsa-lib

1 0