Proof Portal

Sign in
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-225GitHub issuePublicDecided· Out of scope

power-profiles-daemon fails on amd_pstate desktop APU (Ryzen 5 5600G) — same root cause as #6898, no platform_profile fallback available

Reported by theswampdawg · filed Sep 21, 2026 · open at source

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

power-profiles-daemon fails on amd_pstate desktop APU (Ryzen 5 5600G) — same root cause as #6898, no platform_profile fallback availablerevision 1 · captured 2026-09-28 21:23 UTC via poll

Summary

Hitting the same power-profiles-daemon / amd_pstate incompatibility reported in #6898, on different hardware — a desktop AM4 board with a Ryzen 5 5600G (Cezanne APU, 6c/12t). Adding this as a separate data point since the proposed fix in #6898 (falling back to /sys/firmware/acpi/platform_profile) does not apply to this class of hardware.

Environment

  • CPU: AMD Ryzen 5 5600G with Radeon Graphics (Cezanne)
  • Board: desktop AM4 (ASUS)
  • Kernel: linux-omarchy 7.2.5-3
  • power-profiles-daemon: 0.30-1
  • scaling_driver: amd-pstate-epp

Steps to reproduce

  1. sudo systemctl unmask power-profiles-daemon
  2. sudo systemctl enable --now power-profiles-daemon
  3. Observe journal output

Error

power-profiles-daemon[...]: Core           Failed to activate initial profile: Failed to activate CPU driver 'amd_pstate': Error writing '/sys/devices/system/cpu/cpufreq/policy11/boost': Invalid argument

This reproduces on every boot the daemon is enabled — confirmed via journalctl history going back roughly 6 months across many separate boots, always failing on the same policy11 (the 12th logical CPU / last SMT sibling in the loop). CPU topology and ACPI CPPC perf values (highest_perf/nominal_perf/lowest_perf) for policy11 look identical in shape to its sibling cores — no evidence of a disabled/binned core, so this looks like a PPD/kernel interaction bug (likely PPD writing boost to all 12 per-CPU policies in a tight loop and the driver/SMU rejecting one of the writes) rather than anything specific to this core.

platform_profile fallback does not apply here

The workaround proposed in #6898 (falling back to /sys/firmware/acpi/platform_profile) is not available on this system:

$ cat /sys/firmware/acpi/platform_profile
cat: /sys/firmware/acpi/platform_profile: No such file or directory

This ACPI interface is generally only exposed on laptops with vendor EC/WMI support for platform power profiles. Desktop AM4 boards typically don't implement it, so any fallback logic in Omarchy needs to also handle the case where neither PPD nor platform_profile work — e.g., surfacing a clear "power profile switching unavailable on this hardware" state, or falling back to directly writing scaling_governor / energy_performance_preference via cpufreq sysfs instead.

Current workaround

Masking power-profiles-daemon avoids the boot-time error entirely, at the cost of losing profile-switching UI. This is presumably why it was masked by default in some existing installs — worth confirming whether Omarchy intentionally masks it in certain scenarios already.

Happy to provide any further sysfs dumps or test patches if useful.

View raw text
## Summary

Hitting the same `power-profiles-daemon` / `amd_pstate` incompatibility reported in #6898, on different hardware — a desktop AM4 board with a Ryzen 5 5600G (Cezanne APU, 6c/12t). Adding this as a separate data point since the proposed fix in #6898 (falling back to `/sys/firmware/acpi/platform_profile`) does not apply to this class of hardware.

## Environment

- CPU: AMD Ryzen 5 5600G with Radeon Graphics (Cezanne)
- Board: desktop AM4 (ASUS)
- Kernel: `linux-omarchy` 7.2.5-3
- `power-profiles-daemon`: 0.30-1
- `scaling_driver`: `amd-pstate-epp`

## Steps to reproduce

1. `sudo systemctl unmask power-profiles-daemon`
2. `sudo systemctl enable --now power-profiles-daemon`
3. Observe journal output

## Error

```
power-profiles-daemon[...]: Core           Failed to activate initial profile: Failed to activate CPU driver 'amd_pstate': Error writing '/sys/devices/system/cpu/cpufreq/policy11/boost': Invalid argument
```

This reproduces on **every boot** the daemon is enabled — confirmed via `journalctl` history going back roughly 6 months across many separate boots, always failing on the same `policy11` (the 12th logical CPU / last SMT sibling in the loop). CPU topology and ACPI CPPC perf values (`highest_perf`/`nominal_perf`/`lowest_perf`) for policy11 look identical in shape to its sibling cores — no evidence of a disabled/binned core, so this looks like a PPD/kernel interaction bug (likely PPD writing `boost` to all 12 per-CPU policies in a tight loop and the driver/SMU rejecting one of the writes) rather than anything specific to this core.

## platform_profile fallback does not apply here

The workaround proposed in #6898 (falling back to `/sys/firmware/acpi/platform_profile`) is not available on this system:

```
$ cat /sys/firmware/acpi/platform_profile
cat: /sys/firmware/acpi/platform_profile: No such file or directory
```

This ACPI interface is generally only exposed on laptops with vendor EC/WMI support for platform power profiles. Desktop AM4 boards typically don't implement it, so any fallback logic in Omarchy needs to also handle the case where neither PPD nor `platform_profile` work — e.g., surfacing a clear "power profile switching unavailable on this hardware" state, or falling back to directly writing `scaling_governor` / `energy_performance_preference` via cpufreq sysfs instead.

## Current workaround

Masking `power-profiles-daemon` avoids the boot-time error entirely, at the cost of losing profile-switching UI. This is presumably why it was masked by default in some existing installs — worth confirming whether Omarchy intentionally masks it in certain scenarios already.

Happy to provide any further sysfs dumps or test patches if useful.

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 19:23 UTC