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

[PATCH] selftest/alsa: correct grammar in conf_get_bool error string
by Zhang Chujun 03 Nov '25

03 Nov '25

The phrase "an bool" is grammatically incorrect; it should be "a bool". Signed-off-by: Zhang Chujun <zhangchujun(a)cmss.chinamobile.com> diff --git a/tools/testing/selftests/alsa/conf.c b/tools/testing/selftests/alsa/conf.c index 5b7c83fe87b3..317212078e36 100644 --- a/tools/testing/selftests/alsa/conf.c +++ b/tools/testing/selftests/alsa/conf.c @@ -448,7 +448,7 @@ int conf_get_bool(snd_config_t *root, const char *key1, const char *key2, int de ksft_exit_fail_msg("key '%s'.'%s' search error: %s\n", key1, key2, snd_strerror(ret)); ret = snd_config_get_bool(cfg); if (ret < 0) - ksft_exit_fail_msg("key '%s'.'%s' is not an bool\n", key1, key2); + ksft_exit_fail_msg("key '%s'.'%s' is not a bool\n", key1, key2); return !!ret; } -- 2.50.1.windows.1

2 1

bug in snd_seq_query_subscribe_get_time_real
by Erwin P 02 Nov '25

02 Nov '25

Hello, I think there is a bug in snd_seq_query_subscribe_get_time_real(). This function returns (info->flags & SNDRV_SEQ_PORT_SUBS_TIMESTAMP), but it should be (info->flags & SNDRV_SEQ_PORT_SUBS_TIME_REAL), as it is in snd_seq_port_subscribe_get_time_real(). Regards, Erwin.

1 0

Reg: Internal Microphone Broken on ASUS X509UA (ALC3251, SSID 1043:1961) Starting AFTER Kernel 6.8.0-31
by jo 02 Nov '25

02 Nov '25

*System/Hardware Details:* Parameter Value *Laptop Model* *ASUS VivoBook X509UA* *CPU Generation* Intel Core i3-7020U (Kaby Lake / Sunrise Point-LP) *Audio Codec* Realtek ALC3251 (Variant of ALC256) *Subsystem ID (SSID)* *1043:1961* (ASUSTeK Computer Inc.) *PCI Device ID* Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] *Working Kernel Version* *Linux Kernel 6.8.0-31* and previous versions. *Broken Kernel Version* *Starts AFTER 6.8.0-31* (e.g., 6.8.0-32, 6.8.0-35, etc.). Description of the Issue The internal microphone on the ASUS X509UA is *no longer functional* on Linux kernels newer than version 6.8.0-31. The input device is detected by ALSA/PulseAudio, but the capture level remains at zero (no sound is recorded). The issue is a *clear regression*, as the microphone worked correctly on kernel 6.8.0-31 and all previous versions (e.g., in Ubuntu 22.04 LTS). It also works correctly under Chrome OS Flex, which uses a custom-patched kernel. Diagnostic Steps Performed All standard user-level and common developer workarounds have failed on the affected kernel versions: 1. *ALSA Mixer Levels:* Confirmed that the "Capture," "Mic," and "Internal Mic Boost" levels are correctly set (not muted—"OO" instead of "MM") and boosted (to 80-100%). 2. *hdajackretask (Pin Remapping):* All available pins, including 0x19, 0x1b, and "Not Connected" pins (0x12, 0x13, 0x18, 0x1a), were tested with the *"Internal mic"* function. None of these overrides corrected the issue. 3. *hda-verb Commands:* Standard GPIO-based *quirks* commonly used to fix Realtek mic issues (e.g., hda-verb 0x01/0x02/0x04) were executed and failed to activate the microphone. 4. *ALSA Model Quirk Options:* The following common and targeted model= options were added to /etc/modprobe.d/test-audio.conf (one at a time, followed by sudo alsa force-reload) and did not resolve the issue: - options snd-hda-intel model=alc256-asus-mic1 - options snd-hda-intel model=laptop-amic - options snd-hda-intel model=dell-headset-multi (This caused the microphone to disappear entirely.) 5. *Old Configuration Files:* Reverting to or applying the exact configuration files (hda.conf) that *worked* on the pre-6.8 kernels failed to activate the microphone on the post-6.8.0-31 kernels, suggesting a deeper structural change in the driver code. Request The failure of all standard workarounds indicates that the regression is due to a *missing or incorrect pin-mapping configuration* for the *1043:1961 SSID* within the snd-hda-intel driver, likely introduced in a patch after *6.8.0-31*. A patch is needed to re-introduce the correct microphone *quirk* for the *ASUS X509UA (1043:1961)* to restore functionality on the latest Linux kernel series.

1 0

[PATCH REQUEST] ASUS ROG Zephyrus G14 GA403W - CS35L56 volume controls not exposed correctly
by John DelTorchio 02 Nov '25

02 Nov '25

After extensive debugging, the issue has been isolated to incorrect ALSA mixer control mapping. Technical Details Hardware Configuration: - Laptop Model: ASUS ROG Zephyrus G14 (GA403W) - Audio Codec: Realtek ALC285 (Subsystem ID: 0x10431024) - Amplifiers: Dual Cirrus Logic CS35L56 smart amplifiers - ALSA Card: Card 2 (HD-Audio Generic) - Driver: snd_hda_intel with cs35l56-hda module Amplifier Status: The CS35L56 amplifiers are being detected and initialized correctly: cs35l56-hda i2c-CSC3556:00-cs35l56-hda.0: DSP1: Firmware: 1a00d6 vendor: 0x2 v3.11.16 cs35l56-hda i2c-CSC3556:00-cs35l56-hda.1: DSP1: Firmware: 1a00d6 vendor: 0x2 v3.11.16 Firmware files loaded: - cirrus/cs35l56-b0-dsp1-misc-10431024-spkid1.wmfw - cirrus/cs35l56-b0-dsp1-misc-10431024-spkid1-amp1.bin - cirrus/cs35l56-b0-dsp1-misc-10431024-spkid1-amp2.bin The Actual Problem Current (broken) behavior: - The volume slider controls Master Playback Volume (numid=24) on the ALC285 codec - This control only affects the analog signal level going into the CS35L56 amplifiers - Lowering this control degrades signal quality (adds muffling/distortion) without actually reducing speaker output volume - The CS35L56 amplifiers remain at a fixed gain, so perceived loudness doesn't change significantly Correct behavior should be: - The volume slider should control AMP1 Speaker Playback Volume (numid=6) and AMP2 Speaker Playback Volume (numid=12) - The codec's Master and Speaker controls should remain at 100% for optimal signal-to-noise ratio Verified working configuration: bash # Codec output (should be fixed at these values) amixer -c2 sset 'Master' 100 % amixer -c2 sset 'Speaker' 100 % # Amplifier controls (should be user-adjustable via volume slider) amixer -c2 sset 'AMP1 Speaker' 85 % amixer -c2 sset 'AMP2 Speaker' 85 % `` ` Manual testing confirms: - ✅ ` AMP1 Speaker ` and ` AMP2 Speaker ` controls properly adjust speaker loudness - ✅ Volume range 0 -100% works without distortion when codec is at 100 % - ❌ PipeWire/desktop environment uses the wrong mixer controls ### PipeWire Configuration Current sink properties show it's using ACP ( ALSA Card Profiles ) : ` ` ` api.alsa.use-acp = "true" api.alsa.path = "front:2" ` ` ` The automatically selected mixer path is choosing ` Master ` as the primary volume control instead of the CS35L56 amp controls. ### Required Fix This needs one of the following solutions: 1 . **ALSA UCM ( Use Case Manager ) profile** for device ID ` 10431024 ` : - Lock codec controls at 100 % - Expose AMP1/AMP2 Speaker controls as primary volume 2 . **Custom ALSA mixer path** at ` /usr/share/alsa/mixer/paths/ ` : - Define AMP1/AMP2 Speaker as volume elements - Set Master/Speaker to ` volume = ignore ` or ` volume-limit = 0.0 ` 3 . **Kernel quirk** in ` sound/pci/hda/patch_realtek.c ` : - Add model-specific configuration for GA403W - Similar to how other ASUS models with CS35L41/CS35L56 are handled 4 . **PipeWire/WirePlumber profile update**: - Device-specific configuration to use correct mixer elements ### Relevant Files **ALSA Controls Output:** ` `` numid = 6 ,iface = MIXER,name = 'AMP1 Speaker Playback Volume' : values = 400 | dBscale-min = -100.00dB,step = 0 .25dB,mute = 0 | Range: 0 -448 numid = 12 ,iface = MIXER,name = 'AMP2 Speaker Playback Volume' : values = 400 | dBscale-min = -100.00dB,step = 0 .25dB,mute = 0 | Range: 0 -448 numid = 24 ,iface = MIXER,name = 'Master Playback Volume' : values = 39 | dBscale-min = -65.25dB,step = 0 .75dB,mute = 0 | Range: 0 -87 Codec Information: - See full codec dump at: https://paste.centos.org/view/6c3a3640 - Full diagnostics at: https://paste.centos.org/view/c0d20bf3 Temporary Workaround Users can manually set correct levels on boot with this autostart script: ~/.config/autostart/audio-fix.desktop: desktop [Desktop Entry] Type=Application Name=Audio Fix Exec=/usr/bin/bash -c "sleep 5 && amixer -c2 sset 'Master' 100%% && amixer -c2 sset 'Speaker' 100%% && amixer -c2 sset 'AMP1 Speaker' 85%% && amixer -c2 sset 'AMP2 Speaker' 85%%" Hidden=false NoDisplay=false However, the volume slider will still not function correctly. Sent with [Proton Mail](https://proton.me/mail/home) secure email.

1 0

doxygen: fix for doxygen 1.10.0 and later
by GitHub pull_request - opened 01 Nov '25

01 Nov '25

alsa-project/alsa-lib pull request #480 was opened from borine: doygen 1.10.0 changed the paths that include files are searched, with the consequence for alsa-lib that the "Topics" tab is no longer fully populated. See for example the [alsa project online docs](https://www.alsa-project.org/alsa-doc/alsa-lib/topics.html) To fix this we need to prevent circular #include references when doygen scans its input files, and also to re-order some macros. Request URL : https://github.com/alsa-project/alsa-lib/pull/480 Patch URL : https://github.com/alsa-project/alsa-lib/pull/480.patch Repository URL: https://github.com/alsa-project/alsa-lib

1 0