All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: [Regression] No sound / Deferred binding [RR] on MSI Prestige 16 AI+ C3MG (Panther Lake SoundWire) after UCM update
Date: Fri, 12 Jun 2026 00:26:04 +0200 (CEST)	[thread overview]
Message-ID: <18b827352445d300-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18b82735241e5800-webhooks-bot@alsa-project.org>

alsa-project/alsa-ucm-conf issue #784 was opened from tarabelo:

Hello,

A recent update to the `alsa-ucm-conf` package has introduced a regression on the MSI Prestige 16 AI+ C3MG laptop. The audio subsystem falls back to a deferred state, muting all physical outputs (Speakers and Headphone jack). 

The hardware uses an Intel Panther Lake DSP routing audio over a SoundWire bus (4SDCA topology) to Realtek codecs. The SOF firmware loads correctly and the kernel modules are probed, but ALSA fails to map the endpoints with the latest UCM profiles, leaving the controls locked in a `[RR]` (deferred) state in alsamixer.

Downgrading `alsa-ucm-conf` to the previous version completely restores all audio functionality.

### Hardware / System Information:
* **Vendor:** Micro-Star International Co., Ltd.
* **Product:** Prestige 16 AI+ C3MG
* **Board:** MS-2622
* **OS:** Ubuntu 26.04
* **Kernel:** 7.0.0-22-generic
* **DSP:** Intel Panther Lake Smart Sound Technology (SST)
* **Codecs (via SoundWire):** * Realtek ALC1320 (Amps) - mfg_id 0x025d part_id 0x1320
  * Realtek ALC713 (Jack) - mfg_id 0x025d part_id 0x0713

### Symptoms & Logs:
1. `dmesg` shows SOF loading the topology but ALSA defers the binding:
   `sof_sdw sof_sdw: ASoC: Parent card not yet available, widget card binding deferred`
2. `lsmod` confirms `snd_soc_rt1320_sdw` and `snd_soc_rt712_sdca` are loaded.
3. `alsamixer` shows the `sof-soundwire` card, but `Speaker` and `Headphone` elements are locked in `[RR]`.

### Steps to Reproduce:
1. Boot with the latest `alsa-ucm-conf` package on this specific hardware.
2. Check `aplay -l` (only HDMI/DP nodes are visible).
3. Check `alsamixer` (controls deferred).

### Workaround / Proof of Regression:
Reverting `alsa-ucm-conf` from version  1.2.15.3-1ubuntu1.2 to 1.2.15.3-1ubuntu1 and clearing the WirePlumber state (`rm -rf ~/.local/state/wireplumber/`) immediately restores the hardware mapping and functionality.

I can provide the unified diff of the `usr/share/alsa/ucm2` directory between the working and broken versions if needed, or test any proposed patches.

Issue URL     : https://github.com/alsa-project/alsa-ucm-conf/issues/784
Repository URL: https://github.com/alsa-project/alsa-ucm-conf

           reply	other threads:[~2026-06-11 22:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <18b82735241e5800-webhooks-bot@alsa-project.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18b827352445d300-webhooks-bot@alsa-project.org \
    --to=github@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.