[Pkg-alsa-devel] Bug#1138532: alsa-ucm-conf: Realtek ALC1220 sometimes starts with wrong or missing output profile

[Marek]

Package: alsa-ucm-conf
Version: 1.2.14-1
Severity: normal
X-Debbugs-Cc: vadovates at gmail.com

Dear Maintainer,

After recent updates on Debian 13 Trixie, the integrated Realtek ALC1220
audio device sometimes starts with an incorrect or unusable
PipeWire/WirePlumber output profile.

Hardware:

Motherboard:
Gigabyte B450 AORUS PRO-CF

Affected audio device:
09:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD]
Starship/Matisse HD Audio Controller [1022:1487]
Subsystem: Gigabyte Technology Co., Ltd Device [1458:a0c3]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

Codec:
Realtek ALC1220
alsa.components = HDA:10ec1220,1458a0c3,00100101

Other audio device present, not affected:
07:00.1 Audio device [0403]: NVIDIA Corporation GA102 High Definition Audio
Controller [10de:1aef]
Subsystem: Gigabyte Technology Co., Ltd Device [1458:403e]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

Symptoms observed:

   1.

   The card may start as:
   Starship/Matisse HD Audio Controller Analogowe przestrzenne 4.1

   with the default sink:
   alsa_output.pci-0000_09_00.4.analog-surround-41

   This is incorrect for my setup, which is stereo / 2.1.
   2.

   On another boot, GNOME / PipeWire showed only:
   Głuche wyjście

   while wpctl still showed the configured default sink as:
   alsa_output.pci-0000_09_00.4.analog-stereo

   In that state, the Realtek source was visible, but no usable Realtek
   playback sink was created.
   3.

   Headphone and speaker routing becomes inconsistent. Front panel
   headphone detection does not behave correctly when the wrong profile is
   selected.

Workarounds observed:

In the analog-surround-41 case, this fixed the problem:

wpctl set-profile pro-audio
systemctl --user restart wireplumber pipewire pipewire-pulse

After this, the card returned to:

Starship/Matisse HD Audio Controller Analogowe stereo

and the default sink became:

alsa_output.pci-0000_09_00.4.analog-stereo

In the "Dummy Output" case, restarting PipeWire and WirePlumber alone was
enough:

systemctl --user restart wireplumber pipewire pipewire-pulse

No profile change was needed in that case.

Relevant observations:

api.alsa.use-acp = "true"
api.acp.auto-profile = "false"
api.acp.auto-port = "false"

This looks like a regression or race condition in ACP/UCM profile handling
for this ALC1220 device. The hardware works after PipeWire/WirePlumber is
restarted or after forcing a profile transition through pro-audio.

Expected result:

The device should consistently start with a usable analog stereo output
profile:

alsa_output.pci-0000_09_00.4.analog-stereo

Actual result:

The device sometimes starts as analog-surround-41 or with only Dummy Output
available.

-- System Information:
Debian Release: 13.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.90+deb13-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages alsa-ucm-conf depends on:
ii libasound2t64 1.2.14-1

alsa-ucm-conf recommends no packages.

alsa-ucm-conf suggests no packages.

-- no debconf information
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-alsa-devel/attachments/20260531/47e9b6a9/attachment.htm>