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

No microphone USB audio Behringer UMC204HD ALSA update
by GitHub issues - opened 02 Dec '24

02 Dec '24

alsa-project/alsa-ucm-conf issue #479 was opened from emiltoacs: No input on my Behringer UMC204HD because of an update in the following packages on Arch Linux alsa-card-profiles,alsa-lib,alsa-ucm-conf,alsa-utils,lib32-alsa-lib alsa-card-profiles 1:1.2.6-1 -> 1:1.2.7-1 alsa-lib 1.2.12-1 -> 1.2.13-1 alsa-ucm-conf 1.2.12-1 -> 1.2.13-2 alsa-utils 1.2.12-1 -> 1.2.13-2 lib32-alsa-lib 1.2.12-1 -> 1.2.13-1 The error messages related by pipewire : pw.node: (alsa_output.pci-0000_00_1f.3.stereo-fallback-57) graph xrun not-triggered (0 suppressed) pw.node: (alsa_output.pci-0000_00_1f.3.stereo-fallback-57) xrun state:0x7ba2cfaed008 pending:6/6 s:0 a:0 f:0 waiting:0 process:0 status:triggered pw.node: (alsa_output.pci-0000_00_1f.3.stereo-fallback-57) graph xrun not-triggered (4 suppressed) pw.node: (alsa_output.pci-0000_00_1f.3.stereo-fallback-57) xrun state:0x7ba2cfaed008 pending:1/1 s:2663559587040 a:2663559606728 f:2663559630434 waiting:19688 process:23706 status:triggered pw.node: (alsa_output.pci-0000_00_1f.3.stereo-fallback-57) graph xrun not-triggered (0 suppressed) pw.node: (alsa_output.pci-0000_00_1f.3.stereo-fallback-57) xrun state:0x7ba2cfaed008 pending:1/1 s:5553029600968 a:5553029610813 f:5553029623757 waiting:9845 process:12944 status:triggered If I revert package the package to these version it works again : alsa-card-profiles-1:1.2.6-1-x86_64.pkg.tar.zst alsa-lib-1.2.12-1-x86_64.pkg.tar.zst lib32-alsa-lib-1.2.12-1-x86_64.pkg.tar.zst alsa-utils-1.2.12-1-x86_64.pkg.tar.zst alsa-ucm-conf-1.2.12-1-any.pkg.tar.zst In the meantime I add : --ignore alsa-card-profiles,alsa-lib,alsa-ucm-conf,alsa-utils,lib32-alsa-lib to my pacman update. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/479 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

[PATCH] ALSA: hda/realtek: Enable mute and micmute LED on HP ProBook 430 G8
by Nazar Bilinskyi 01 Dec '24

01 Dec '24

HP ProBook 430 G8 has a mute and micmute LEDs that can be made to work using quirk ALC236_FIXUP_HP_GPIO_LED. Enable already existing quirk. Signed-off-by: Nazar Bilinskyi <nbilinskyi(a)gmail.com> --- sound/pci/hda/patch_realtek.c | 1 + 1 file changed, 1 insertion(+) diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c index 2bf5c512e..877c5d20a 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -10340,6 +10340,7 @@ static const struct hda_quirk alc269_fixup_tbl[] = { SND_PCI_QUIRK(0x103c, 0x87b7, "HP Laptop 14-fq0xxx", ALC236_FIXUP_HP_MUTE_LED_COEFBIT2), SND_PCI_QUIRK(0x103c, 0x87c8, "HP", ALC287_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87d3, "HP Laptop 15-gw0xxx", ALC236_FIXUP_HP_MUTE_LED_COEFBIT2), + SND_PCI_QUIRK(0x103c, 0x87df, "HP ProBook 430 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87e5, "HP ProBook 440 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87e7, "HP ProBook 450 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87f1, "HP ProBook 630 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), -- 2.47.1

1 0

snd_seq_open and pulse audio??
by Mark Lentczner 01 Dec '24

01 Dec '24

My ALSA Seq port manager runs as a service. The service is installed under its own service user, which has the home directory set to some place non-existent and non-writable. When my service starts I see this surprising log message: *amidiminder[136345]: Failed to create secure directory (/var/lib/misc/.config/pulse): No such file or directory* A little investigation reveals that this error is generated by this call, opening the ALSA Seq: serr = snd_seq_open(&seq, "default", SND_SEQ_OPEN_DUPLEX, 0); It's a little surprising that opening ALSA Seq would somehow invoke something in pulse audio, and further that pulse audio would then be trying to create its user directory (.configure/pulse is where pulse audio sticks things under each user's home directory). This seems to be a reprise of this Debian bug from 2013 involving alsa-utils and pulse audio: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712980 Which was close via this patch to alsa-utils: alsactl: Make homedir configurable <https://mailman.alsa-project.org/hyperkitty/list/alsa-devel@alsa-project.or…> The fix there seems to be adding some mechanism to change the $HOME environment variable to point at /var/run/alsa. I agree with Takashi's reply to that fix: Overriding $HOME sounds scary to me, too! Is there any insight into this... and did that fix stick or was some other method found to deal with this. In my case, I don't understand why just opening the ALSA Seq is causing any pulse audio code to run... but perhaps things are more entwined at a lower level of ALSA lib than I understand. - Mark

1 0