From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: No output or input exists after upgrading alsa-ucm-conf to 1.2.16
Date: Thu, 4 Jun 2026 14:34:52 +0200 (CEST) [thread overview]
Message-ID: <18b5e0e232dda300-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18b5e0e232b41800-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #774 was opened from EricLin0509:
## Summary
After upgrading the `alsa-ucm-conf` to `1.2.16`, the builtin speaker and microphone in MSI Prestige 16 Flip AI+ C3MTG has gone, and these devices previously worked fine. To make them work again I have to downgrade `alsa-ucm-conf` to `1.2.15.3` (keep `alsa-lib 1.2.16` is fine).
Similar issue #773
## Environment
- OS: Arch Linux
- Device: MSI Prestige 16 Flip AI+ C3MTG
- `alsa-ucm-conf` broken: 1.2.16-1
- `alsa-ucm-conf` working: 1.2.15.3-2
- Kernel: 7.0.11-1-cachyos
- Audio server: PipeWire 1.6.6 / WirePlumber 0.5.14
## Root cause
The configuration can't be loaded in version `1.2.16` on a board matching `rt713-sdca`
Here are the outputs of `alsaucm -c hw:0 dump text` in these two versions.
- 1.2.15.3
```
Verb.HiFi {
Comment "Play HiFi quality Music"
Device.Headphones {
Comment Headphones
Values {
CaptureCTL "_ucm0001.hw:sofsoundwire"
JackControl "Headphone Jack"
PlaybackCTL "_ucm0001.hw:sofsoundwire"
PlaybackPCM "_ucm0001.hw:sofsoundwire"
PlaybackPriority 200
TQ HiFi
}
}
Device.Headset {
Comment "Headset Microphone"
Values {
CaptureCTL "_ucm0001.hw:sofsoundwire"
CaptureMixerElem "rt713 FU0F"
CapturePCM "_ucm0001.hw:sofsoundwire,1"
CapturePriority 200
CaptureSwitch "rt713 FU0F Capture Switch"
CaptureVolume "rt713 FU0F Capture Volume"
JackControl "Headset Mic Jack"
PlaybackCTL "_ucm0001.hw:sofsoundwire"
TQ HiFi
}
}
Device.Mic {
Comment "SoundWire Microphones"
Values {
CaptureCTL "_ucm0001.hw:sofsoundwire"
CaptureMixerElem "rt713 FU1E"
CapturePCM "_ucm0001.hw:sofsoundwire,4"
CapturePriority 100
CaptureSwitch "rt713 FU1E Capture Switch"
CaptureVolume "rt713 FU1E Capture Volume"
PlaybackCTL "_ucm0001.hw:sofsoundwire"
TQ HiFi
}
}
Device.Speaker {
Comment Speaker
Values {
CaptureCTL "_ucm0001.hw:sofsoundwire"
PlaybackCTL "_ucm0001.hw:sofsoundwire"
PlaybackPCM "_ucm0001.hw:sofsoundwire,2"
PlaybackPriority 100
TQ HiFi
}
}
Device.HDMI1 {
Comment "HDMI / DisplayPort 1 Output"
Values {
CaptureCTL "_ucm0001.hw:sofsoundwire"
JackControl "HDMI/DP,pcm=5 Jack"
PlaybackCTL "_ucm0001.hw:sofsoundwire"
PlaybackPCM "_ucm0001.hw:sofsoundwire,5"
PlaybackPriority 500
TQ HiFi
}
}
Device.HDMI2 {
Comment "HDMI / DisplayPort 2 Output"
Values {
CaptureCTL "_ucm0001.hw:sofsoundwire"
JackControl "HDMI/DP,pcm=6 Jack"
PlaybackCTL "_ucm0001.hw:sofsoundwire"
PlaybackPCM "_ucm0001.hw:sofsoundwire,6"
PlaybackPriority 600
TQ HiFi
}
}
Device.HDMI3 {
Comment "HDMI / DisplayPort 3 Output"
Values {
CaptureCTL "_ucm0001.hw:sofsoundwire"
JackControl "HDMI/DP,pcm=7 Jack"
PlaybackCTL "_ucm0001.hw:sofsoundwire"
PlaybackPCM "_ucm0001.hw:sofsoundwire,7"
PlaybackPriority 700
TQ HiFi
}
}
}
```
- 1.2.16
```
ALSA lib utils.c:372:(uc_mgr_config_load_into) [error.ucm] could not open configuration file /usr/share/alsa/ucm2/codecs/rt713-sdca/init.conf
ALSA lib parser.c:79:(uc_mgr_config_load_file) [error.ucm] failed to open file /usr/share/alsa/ucm2/codecs/rt713-sdca/init.conf: -2
ALSA lib main.c:1805:(snd_use_case_mgr_open) [error.ucm] failed to import hw:0 use case configuration -2
alsaucm: error failed to open sound card hw:0: No such file or directory
```
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/774
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2026-06-04 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18b5e0e232b41800-webhooks-bot@alsa-project.org>
2026-06-04 12:34 ` GitHub issues - opened [this message]
[not found] <18b5e14bb5346700-webhooks-bot@alsa-project.org>
2026-06-04 12:42 ` No output or input exists after upgrading alsa-ucm-conf to 1.2.16 GitHub issues - edited
[not found] <18b5e171f815fb00-webhooks-bot@alsa-project.org>
2026-06-04 12:45 ` GitHub issues - edited
[not found] <18b5e1a1fe8ea700-webhooks-bot@alsa-project.org>
2026-06-04 12:48 ` GitHub issues - edited
[not found] <18b5e1c8293ed400-webhooks-bot@alsa-project.org>
2026-06-04 12:51 ` GitHub issues - edited
[not found] <18b63a9967efa700-webhooks-bot@alsa-project.org>
2026-06-05 15:58 ` GitHub issues - reopened
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=18b5e0e232dda300-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox