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

suspend on BeeLink SER9 (and new Framework 13 AMD Ryzen AI 9 HX 370)

Reported by marcinczenko · filed Jul 29, 2025Closed upstream on 2026-02-21 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

suspend on BeeLink SER9 (and new Framework 13 AMD Ryzen AI 9 HX 370)revision 1 · captured 2026-10-04 11:27 UTC via poll

When using the "Suspend" on BeeLink SER9, after issuing "suspend" Beelink device fans spin up and what I see immediately is a lock screen (so looks like it is not suspending). After unlocking, WLAN0 interface is gone. Running lspci -knnd ::0280 shows:

c3:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
	Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
	Kernel modules: iwlwifi

you can see that Kernel driver in use: iwlwifi is not there.

Problem persists after rebooting. After booting into Windows (I have dual boot - systemd-boot), in Windows, Windows manages to power the interface up. Then, after booting back to Arch, the interface is back as well.

In the past I often had problems with Suspend on Linux, I am wondering if it works for you on other machines.

View raw text
When using the "Suspend" on BeeLink SER9, after issuing "suspend" Beelink device fans spin up and what I see immediately is a lock screen (so looks like it is not suspending). After unlocking, `WLAN0` interface is gone. Running `lspci -knnd ::0280` shows:

```bash
c3:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
	Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
	Kernel modules: iwlwifi
```

you can see that `Kernel driver in use: iwlwifi` is not there.

Problem persists after rebooting. After booting into Windows (I have dual boot - systemd-boot), in Windows, Windows manages to power the interface up. Then, after booting back to Arch, the interface is back as well.

In the past I often had problems with Suspend on Linux, I am wondering if it works for you on other machines.

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.