Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
ACPI and AMD fTPM memory sections overlap on HP ENVY x360 m (Model 15m-bq121dx), causing hang at boot due to systemd failing to initialize TPM device
Reported by sonicbhoc · filed Dec 9, 2025Closed upstream on 2025-12-11. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
System details
AMD Ryzen 5 2500U, Omarchy 3.2.2
What's wrong?
I am running into the issue described in this github issue in the systemd project: Issue 33412
The consequence of this issue is a minimum addition of 1 minute and 30 seconds to my boot time waiting for the fTPM initialization to fail.
The solution is to modify the kernel command line options to add a kernel command line to remove the TPM CRBs from the ACPI NVS region so the TPM can get exclusive access to it:
memmap=0x1000%0xcd575000-4 memmap=0x1000%cd579000-4
View raw text
### System details AMD Ryzen 5 2500U, Omarchy 3.2.2 ### What's wrong? I am running into the issue described in this github issue in the systemd project: [Issue 33412](https://github.com/systemd/systemd/issues/33412#issuecomment-2557737935) The consequence of this issue is a minimum addition of 1 minute and 30 seconds to my boot time waiting for the fTPM initialization to fail. The solution is to modify the kernel command line options to add a kernel command line to remove the TPM CRBs from the ACPI NVS region so the TPM can get exclusive access to it: `memmap=0x1000%0xcd575000-4 memmap=0x1000%cd579000-4`
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.