From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ALC4080 0b05:1999 (ASUS ROG Strix Z590-A Gaming WiFi): front Headphones output works but is disabled by HeadphonesName ""
Date: Wed, 12 Aug 2026 20:35:58 +0200 (CEST) [thread overview]
Message-ID: <18cb22a1f01c4100-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18cb22a1efeab100-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #830 was opened from stephensedge:
### Summary
On the **ASUS ROG Strix Z590-A Gaming WiFi** (ALC4080-over-USB, `0b05:1999`) in a standard desktop case, the front-panel headphone output is fully functional — but the UCM profile deliberately hides it via `HeadphonesName ""` in the `If.asus-rog-strix` block of `ucm2/USB-Audio/Realtek/ALC4080-HiFi.conf`. Removing that line makes the front headphones work out of the box, with working jack detection.
### Environment
- Motherboard: ASUS ROG STRIX Z590-A GAMING WIFI (BIOS 1202), standard case with front-panel HD-audio header wired to a combo headset jack
- USB device: `0b05:1999 ASUSTek Computer, Inc. USB Audio` (ALC4080)
- alsa-lib / alsa-ucm-conf 1.2.16.1 (Fedora 44), PipeWire/WirePlumber
### Evidence the hardware works
The codec exposes a front-headphone playback path on PCM device 1 with a functional jack sensor:
```
$ amixer -c 2 controls | grep -i jack
numid=32,iface=CARD,name='Headphone - Output Jack'
...
```
With headphones plugged into the front jack, the sensor reports correctly:
```
$ amixer -c 2 cget numid=32
: values=on # off when unplugged — detection works
```
And audio plays out of the front jack:
```
$ amixer -c 2 cset "name='PCM Playback Switch',index=1" on
$ speaker-test -D plughw:2,1 -c 2 -t sine -f 440 -l 2 # audible on front headphones
```
After deleting the `HeadphonesName ""` line from the `If.asus-rog-strix` block, PipeWire exposes a "Front Headphones" sink alongside "Speakers"; both route correctly, and port availability follows the jack sensors as expected.
### Why the quirk exists (I think)
The block was added in d771df03 ("Add: 0b05:1999 ASUS ROG Strix Z590-A Gaming WiFi", from PR #247), whose commit message notes the board "is recognized as a thelio-mira-b1 by system76". The System76 Thelio chassis has no front-panel audio wired, which would explain why the original submitter blanked the Headphones device — on their machine the jack physically doesn't exist.
But that's a chassis property, not a board/codec property. On a Thelio, the `Headphone - Output Jack` control simply stays `off`, so with the Headphones device enabled the port would just show as unavailable — jack detection already handles the unwired case gracefully.
### Suggested fix
Remove `HeadphonesName ""` from the `If.asus-rog-strix` (`0b05:1999`) block:
```diff
If.asus-rog-strix {
Condition {
Type RegexMatch
String "${CardComponents}"
Regex "USB(0b05:1999)"
}
True.Define {
Line1PCM "3"
- HeadphonesName ""
}
}
```
I'm running with exactly this change locally and everything (front headphones, rear speakers, jack detection, profile switching) behaves correctly. Happy to provide `alsa-info` output or test patches.
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/830
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-08-12 18:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18cb22a1efeab100-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=18cb22a1f01c4100-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