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-5033GitHub issuePublicReceived

Dell XPS 13 DX13260 (0E54): silent speakers due to missing Cirrus firmware links

Reported by zspetersen · filed Sep 11, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #9687 (R-1081). GitHub close reason: completed.

Received and recorded verbatim. Nothing has been checked yet.

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?
Not yet mapped to any requirement or component.
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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Dell XPS 13 DX13260 (0E54): silent speakers due to missing Cirrus firmware linksrevision 1 · captured 2026-10-04 12:10 UTC via poll

System details

  • Dell XPS 13 DX13260, SKU 0E54, audio subsystem 1028:0e54
  • Intel Core Ultra 7 355; integrated Intel Panther Lake graphics
  • Omarchy 4.0.3-1
  • Kernel 7.2.3-arch1-1-ptl
  • linux-firmware-cirrus 20260810-2
  • sof-firmware 2025.12.2-1
  • alsa-ucm-conf 1.2.16.1-1
  • PipeWire 1.6.8, WirePlumber 0.5.17
  • CS42L43 codec with two CS35L56 Rev B2 speaker amplifiers

What's wrong?

The internal speakers were silent. PipeWire and WirePlumber were running, with the Speaker output selected, unmuted, and set to 35%. Both amplifier switches were enabled.

The boot log showed these errors for both amplifiers:

FIRMWARE_MISSING
Calibration disabled due to missing firmware controls
Can't read tuning IDs

The installed Cirrus firmware package had no firmware links for 10280e54. Its package integrity check reported no missing packaged files.

Reproduction

On this hardware with the versions above, before adding the missing links:

  1. Boot Omarchy and select the internal Speaker output.
  2. Unmute and attempt audio playback.
  3. Check journalctl -b -k for the amplifier firmware errors above.

Expected: audio plays through the internal speakers.

Observed: silent speakers despite normal output settings.

Local remediation and verification

Added the nine 10280e54 firmware links defined in the upstream linux-firmware manifest, covering speaker IDs 1–3. These point to the existing CS35L56 4.5.9 firmware and corresponding 10280e53 tuning files.

After reboot, both amplifiers loaded the 10280e54-spkid1 firmware and their respective tuning files. Both logged:

Calibration applied

The Speaker output is present again. Firmware loading and calibration are verified, and I confirmed that audio playback through the internal speakers works after reboot.

Related report and scope

Related to #9687, but this machine is 1028:0e54 with speaker ID 1. That report concerns 1028:0e53 with speaker ID 0.

This appears to be a gap in the installed firmware package. Reporting here to document the affected Omarchy configuration and the official upstream remediation; it may belong with the firmware package maintainers.

View raw text
### System details

- Dell XPS 13 DX13260, SKU `0E54`, audio subsystem `1028:0e54`
- Intel Core Ultra 7 355; integrated Intel Panther Lake graphics
- Omarchy `4.0.3-1`
- Kernel `7.2.3-arch1-1-ptl`
- `linux-firmware-cirrus 20260810-2`
- `sof-firmware 2025.12.2-1`
- `alsa-ucm-conf 1.2.16.1-1`
- PipeWire `1.6.8`, WirePlumber `0.5.17`
- CS42L43 codec with two CS35L56 Rev B2 speaker amplifiers

### What's wrong?

The internal speakers were silent. PipeWire and WirePlumber were running, with the Speaker output selected, unmuted, and set to 35%. Both amplifier switches were enabled.

The boot log showed these errors for both amplifiers:

```text
FIRMWARE_MISSING
Calibration disabled due to missing firmware controls
Can't read tuning IDs
```

The installed Cirrus firmware package had no firmware links for `10280e54`. Its package integrity check reported no missing packaged files.

### Reproduction

On this hardware with the versions above, before adding the missing links:

1. Boot Omarchy and select the internal Speaker output.
2. Unmute and attempt audio playback.
3. Check `journalctl -b -k` for the amplifier firmware errors above.

Expected: audio plays through the internal speakers.

Observed: silent speakers despite normal output settings.

### Local remediation and verification

Added the nine `10280e54` firmware links defined in the [upstream linux-firmware manifest](https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware/+/refs/heads/main/WHENCE), covering speaker IDs 1–3. These point to the existing CS35L56 4.5.9 firmware and corresponding `10280e53` tuning files.

After reboot, both amplifiers loaded the `10280e54-spkid1` firmware and their respective tuning files. Both logged:

```text
Calibration applied
```

The Speaker output is present again. Firmware loading and calibration are verified, and I confirmed that audio playback through the internal speakers works after reboot.

### Related report and scope

Related to #9687, but this machine is `1028:0e54` with speaker ID 1. That report concerns `1028:0e53` with speaker ID 0.

This appears to be a gap in the installed firmware package. Reporting here to document the affected Omarchy configuration and the official upstream remediation; it may belong with the firmware package maintainers.

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.

No decision has been recorded yet.