From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: HP OmniBook Ultra Flip (Lunar Lake, 103C:8CDE) — ALSA headphone jack state changes but audio does not route to headphones
Date: Fri, 8 May 2026 14:55:04 +0200 (CEST) [thread overview]
Message-ID: <18ad985148d8a700-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18ad985148d44c00-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #758 was edited from pavlo0909:
### Description
On the HP OmniBook Ultra Flip (Intel Lunar Lake), headphone plug/unplug is correctly detected by ALSA, but audio does not route to the headphone output automatically.
When headphones are inserted, the `Headphone Jack` control changes state correctly. However, the active output does not switch to headphones in KDE / PipeWire, and audio continues through the internal speakers. The internal speakers and internal DMIC both work normally.
### Environment
- **Manufacturer / Model:** HP OmniBook Ultra Flip Laptop 14-fh0xxx
- **Platform:** Intel Lunar Lake (LNL)
- **Codec:** Realtek ALC245
- **PCI SSID:** 103C:8CDE
- **Distribution:** Fedora 44 (KDE Plasma Desktop Edition)
- **Kernel:** 6.19.14-300.fc44.x86_64
- **Audio stack:** SOF + PipeWire + WirePlumber
### Diagnostic Results
I verified headphone jack detection at the ALSA level using:
`watch "amixer -c0 contents | grep -A2 Jack"`
The control `numid=19,iface=CARD,name='Headphone Jack'` changes state correctly:
- **Unplugged:** `values=off`
- **Plugged:** `values=on`
### Observed Behavior
- ALSA detects headphone insertion correctly, but the desktop environment (PipeWire/WirePlumber) does not automatically switch the routing or expose the port correctly.
- Audio continues through internal speakers.
- **Key Observation:** Manual routing is successful when performing the following sequence:
1. `amixer -c0 set 'Headphone' on`
2. `amixer -c0 set 'Speaker' off`
3. `amixer -c0 set 'Auto-Mute Mode' Enabled`
4. wpctl set-mute @DEFAULT_AUDIO_SINK@ 0
### Technical Details (from alsa-info)
- **Headphone node:** `Node 0x21 [Pin Complex]`
- **Pin default:** `0x03211020: [Jack] HP Out at Ext Left`
- **Topology:** `intel/sof-ipc4-tplg/sof-hda-generic-2ch.tplg`
---
**Note to Maintainers:** I have attached the full `alsa-info.txt` to this issue. This hardware was previously discussed in the SOF project https://github.com/thesofproject/linux/issues/5757where it was confirmed that HDA jack detection is functional at the driver level.
[alsa-info.txt](https://github.com/user-attachments/files/27514810/alsa-info.txt)
**Output of alsaucm dump text and spa-acp-tool lv for both the legacy and SOF case**
[sof_spa_acp.txt](https://github.com/user-attachments/files/27518858/sof_spa_acp.txt)
[sof_ucm_dump.txt](https://github.com/user-attachments/files/27518859/sof_ucm_dump.txt)
[legacy_spa_acp.txt](https://github.com/user-attachments/files/27518860/legacy_spa_acp.txt)
alsaucm dump text is only available for the SOF case; for the Legacy driver, it returns 'UCM is not supported'
```
alsaucm dump text > legacy_ucm_dump.txt
ALSA lib parser.c:305:(error_node) [error.ucm] UCM is not supported for this HDA model (HDA Intel PCH at 0x3013200000 irq 218)
ALSA lib main.c:1804:(snd_use_case_mgr_open) [error.ucm] failed to import hw:0 use case configuration -6
alsaucm: error failed to open sound card hw:0: No such device or address
```
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/758
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2026-05-08 12:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18ad985148d44c00-webhooks-bot@alsa-project.org>
2026-05-08 12:55 ` GitHub issues - edited [this message]
[not found] <18ad9857ce4d9d00-webhooks-bot@alsa-project.org>
2026-05-08 12:55 ` HP OmniBook Ultra Flip (Lunar Lake, 103C:8CDE) — ALSA headphone jack state changes but audio does not route to headphones GitHub issues - edited
[not found] <18ad984970874900-webhooks-bot@alsa-project.org>
2026-05-08 12:54 ` GitHub issues - edited
[not found] <18ad9840aa8c2100-webhooks-bot@alsa-project.org>
2026-05-08 12:53 ` GitHub issues - edited
[not found] <18ad966e63c9f700-webhooks-bot@alsa-project.org>
2026-05-08 12:20 ` GitHub issues - edited
[not found] <18ad960b8155cf00-webhooks-bot@alsa-project.org>
2026-05-08 12:13 ` GitHub issues - edited
[not found] <18ad95fefb7a4a00-webhooks-bot@alsa-project.org>
2026-05-08 12:12 ` GitHub issues - edited
[not found] <18ad95f5bf40dc00-webhooks-bot@alsa-project.org>
2026-05-08 12:11 ` GitHub issues - edited
[not found] <18ad95cc252ef900-webhooks-bot@alsa-project.org>
2026-05-08 12:08 ` GitHub issues - edited
[not found] <18ad94d174d7ff00-webhooks-bot@alsa-project.org>
2026-05-08 11:50 ` GitHub issues - edited
[not found] <18ad90c9277b4d00-webhooks-bot@alsa-project.org>
2026-05-08 10:37 ` GitHub issues - edited
[not found] <18ad8ec0a3edaf00-webhooks-bot@alsa-project.org>
2026-05-08 9:59 ` GitHub issues - opened
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=18ad985148d8a700-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.