From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Headphone jack (3.5mm) silent on Alienware 18 with sof-arl-rt722 — speakers work
Date: Mon, 25 May 2026 19:12:23 +0200 (CEST) [thread overview]
Message-ID: <18b2de396de93300-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18b2de396db34900-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #766 was opened from d0mm392:
Hardware:
Alienware 18 (Area_51M AA18250-0M66RF)
Audio: Intel SOF + rt722 (headphone/mic) + rt1320 (speaker) via SoundWire
Kernel: 7.0.1 / 7.0.5 / 7.0.9 nobara.fc43 (all same behavior)
alsa-sof-firmware: 2025.12.2-1.fc43
Problem:
3.5mm headphone jack produces no audio. Laptop speakers work fine.
Findings:
Jack detection works correctly — evtest /dev/input/event26 confirms SW_HEADPHONE_INSERT events fire on plug/unplug
PipeWire routes to Headphones__sink (status: RUNNING), all mixer controls at 100%, nothing muted
Topology ABI mismatch at boot: Topology ABI 3:29:1 vs Kernel ABI 3:23:1
UCM profile bugs in /usr/share/alsa/ucm2/sof-soundwire/rt722.conf:
EnableSequence references 'Headphone Switch' — control doesn't exist (actual: 'Headphone')
JackControl "Headphone Jack" — doesn't exist (kernel registers it as "Headset Jack")
Tested: module reload, alsactl init, UCM patch — no change
dmesg:
sof-audio-pci-intel-mtl: loading topology: sof-arl-rt722-l0_rt1320-l2.tplg
Topology: ABI 3:29:1 Kernel ABI 3:23:1
sof_sdw: ASoC: Parent card not yet available, widget card binding deferred
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/766
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-05-25 17:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18b2de396db34900-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=18b2de396de93300-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.