Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-603GitHub issuePublicDecided· Out of scope

ASUS ExpertBook PX4466CHA: built-in speakers silent (ALC256, subsystem 1043:3541)

Reported by DemonKissme · filed Sep 13, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

ASUS ExpertBook PX4466CHA: built-in speakers silent (ALC256, subsystem 1043:3541)revision 1 · captured 2026-09-28 21:23 UTC via poll

Hardware

  • Laptop: ASUS ExpertBook PX4466CHA
  • Codec: Realtek ALC256
  • HDA subsystem ID: 1043:3541
  • Audio controller: AMD Ryzen HD Audio Controller
  • Distribution: Omarchy 4.0.3-1 (Arch Linux)

Problem

The built-in speakers produce no audio at all.

This is not an application, PipeWire routing, or volume issue:

  • PipeWire routes Chrome audio to Ryzen HD Audio Controller Speaker
  • Chrome playback streams are active
  • Speaker volume is 100% and unmuted in ALSA
  • Auto-Mute Mode is disabled
  • HDMI and Bluetooth are separate devices, but the internal speakers remain silent

Kernel codec probing shows:

ALC256: picked fixup (pin match)
autoconfig for ALC256: line_outs=1 (0x14) type:speaker
speaker_outs=0
hp_outs=1 (0x21)

The absence of speaker_outs strongly suggests that this ASUS subsystem has no supported Realtek HDA quirk or amplifier-initialization path in Linux.

Expected behavior

Built-in speakers should work through the normal ALSA / PipeWire audio stack.

Actual behavior

Audio meters move and streams are active, but the built-in speakers are completely silent.

Could Omarchy maintainers please point this report to the appropriate upstream ALSA / Realtek maintainers, or document a known workaround if one exists?

View raw text
## Hardware

- Laptop: ASUS ExpertBook PX4466CHA
- Codec: Realtek ALC256
- HDA subsystem ID: `1043:3541`
- Audio controller: AMD Ryzen HD Audio Controller
- Distribution: Omarchy 4.0.3-1 (Arch Linux)

## Problem

The built-in speakers produce no audio at all.

This is not an application, PipeWire routing, or volume issue:

- PipeWire routes Chrome audio to `Ryzen HD Audio Controller Speaker`
- Chrome playback streams are active
- Speaker volume is 100% and unmuted in ALSA
- Auto-Mute Mode is disabled
- HDMI and Bluetooth are separate devices, but the internal speakers remain silent

Kernel codec probing shows:

```text
ALC256: picked fixup (pin match)
autoconfig for ALC256: line_outs=1 (0x14) type:speaker
speaker_outs=0
hp_outs=1 (0x21)
```

The absence of `speaker_outs` strongly suggests that this ASUS subsystem has no supported Realtek HDA quirk or amplifier-initialization path in Linux.

## Expected behavior

Built-in speakers should work through the normal ALSA / PipeWire audio stack.

## Actual behavior

Audio meters move and streams are active, but the built-in speakers are completely silent.

Could Omarchy maintainers please point this report to the appropriate upstream ALSA / Realtek maintainers, or document a known workaround if one exists?

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 12:38 UTC