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.
Omarchy 4.0.4 on 2019 T2 MacBook Pro: post-login black screen, full-speed fans and shutdown; hybrid graphics workaround succeeds
Reported by TheBuilderJR · filed Sep 20, 2026 · open at source
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
System details
- 2019 Intel MacBook Pro with T2; exact DMI model identifier, screen size and GPU SKU have not been captured.
- Installed from
omarchy-4.0.4.iso. - The ISO contains
linux-t2kernel7.2.4-arch1-Watanare-T2-3-t2; I have not separately recordeduname -rfrom the installed system.
What's wrong?
After installation, I could reach the login screen, but logging in caused the fans to blast, the screen to go black, and the laptop to shut off.
I initially used a modified ISO with a Safe Graphics entry adding nomodeset to the live installer's kernel command line. This helped get through installation, but did not resolve the installed system's post-login failure. That initial modification only changed the live ISO's GRUB configuration.
This appears to corroborate #9609 on Omarchy 4.0.4. I found the workaround through discussion #4917 and the T2 Linux hybrid graphics guide. The symptoms match the guide's hybrid-graphics freeze/shutdown description, but I do not have crash logs establishing CPU CATERR or the precise root cause on my machine.
What worked
A second custom ISO included a T2 Mac Intel Graphics boot entry using:
apple_gmux.force_igd=1This entry does not use nomodeset. The normal entry and a separate Safe Graphics (nomodeset) fallback remained available, with a visible 10-second boot menu.
The installer was also patched to write the following settings into the installed target, before its final limine-update/UKI build:
/etc/modprobe.d/99-omarchy-mbp-gmux.conf
options apple-gmux force_igd=y/etc/limine-entry-tool.d/99-omarchy-mbp-graphics.conf
KERNEL_CMDLINE[default]+=" apple_gmux.force_igd=1"/etc/mkinitcpio.conf.d/99-omarchy-mbp-graphics.conf
FILES+=(/etc/modprobe.d/99-omarchy-mbp-gmux.conf)/etc/udev/rules.d/30-omarchy-mbp-amdgpu-pm.rules
SUBSYSTEM=="drm", DRIVERS=="amdgpu", ATTR{device/power_dpm_force_performance_level}="low"The custom patch gates these installed settings by the machine's DMI product name: Intel preference plus AMD low power for MacBookPro16,1, MacBookPro16,4 and MacBookPro15,3; Intel preference only for MacBookPro15,1, following the guide's Polaris power-management exception. Other models receive no installed-system changes. These are the patch's supported branches, not models I have personally tested. The live environment also includes a model-gated AMD low-power rule.
No permanent nomodeset was added to the installed system. No display connector was disabled, no dGPU-off service was enabled, and no sleep, fan or thermal-protection settings were changed. AMD low-power mode may reduce graphics performance.
Result and limitations
The T2 Mac Intel Graphics entry showed a blank screen on the first attempt, but booted successfully on the second attempt. After proceeding with this modified image, my installation now works instead of failing after login.
This is a successful workaround on one machine, not a claim of long-term stability or proof that every setting above is necessary. Intel selection and the applicable power-management changes were bundled together, so I have not isolated their individual effects. External displays, suspend/resume and GPU-heavy applications have not been evaluated as part of this report. No omarchy-debug output or crash journal is attached yet.
Suggested improvement
Please consider a supported, hardware-aware T2 hybrid-graphics workaround during installation, applied before the first installed boot, and an Intel Graphics boot option for affected Macs. Keeping a separate Safe Graphics fallback would also help. Merely adding nomodeset to the live installer does not address this post-install failure.
Related: #9609 and discussion #4917. Posting this as an additional 4.0.4 reproduction and a record of the working installer changes; feel free to consolidate it into #9609 if that is the preferred tracking issue.
View raw text
### System details
- 2019 Intel MacBook Pro with T2; exact DMI model identifier, screen size and GPU SKU have not been captured.
- Installed from `omarchy-4.0.4.iso`.
- The ISO contains `linux-t2` kernel `7.2.4-arch1-Watanare-T2-3-t2`; I have not separately recorded `uname -r` from the installed system.
### What's wrong?
After installation, I could reach the login screen, but logging in caused the fans to blast, the screen to go black, and the laptop to shut off.
I initially used a modified ISO with a **Safe Graphics** entry adding `nomodeset` to the live installer's kernel command line. This helped get through installation, but did not resolve the installed system's post-login failure. That initial modification only changed the live ISO's GRUB configuration.
This appears to corroborate #9609 on Omarchy 4.0.4. I found the workaround through [discussion #4917](https://github.com/omacom/omarchy/discussions/4917) and the [T2 Linux hybrid graphics guide](https://wiki.t2linux.org/guides/hybrid-graphics/). The symptoms match the guide's hybrid-graphics freeze/shutdown description, but I do not have crash logs establishing CPU CATERR or the precise root cause on my machine.
### What worked
A second custom ISO included a **T2 Mac Intel Graphics** boot entry using:
```text
apple_gmux.force_igd=1
```
This entry does **not** use `nomodeset`. The normal entry and a separate Safe Graphics (`nomodeset`) fallback remained available, with a visible 10-second boot menu.
The installer was also patched to write the following settings into the **installed target**, before its final `limine-update`/UKI build:
`/etc/modprobe.d/99-omarchy-mbp-gmux.conf`
```conf
options apple-gmux force_igd=y
```
`/etc/limine-entry-tool.d/99-omarchy-mbp-graphics.conf`
```bash
KERNEL_CMDLINE[default]+=" apple_gmux.force_igd=1"
```
`/etc/mkinitcpio.conf.d/99-omarchy-mbp-graphics.conf`
```bash
FILES+=(/etc/modprobe.d/99-omarchy-mbp-gmux.conf)
```
`/etc/udev/rules.d/30-omarchy-mbp-amdgpu-pm.rules`
```udev
SUBSYSTEM=="drm", DRIVERS=="amdgpu", ATTR{device/power_dpm_force_performance_level}="low"
```
The custom patch gates these installed settings by the machine's DMI product name: Intel preference plus AMD low power for `MacBookPro16,1`, `MacBookPro16,4` and `MacBookPro15,3`; Intel preference only for `MacBookPro15,1`, following the guide's Polaris power-management exception. Other models receive no installed-system changes. These are the patch's supported branches, **not** models I have personally tested. The live environment also includes a model-gated AMD low-power rule.
No permanent `nomodeset` was added to the installed system. No display connector was disabled, no dGPU-off service was enabled, and no sleep, fan or thermal-protection settings were changed. AMD low-power mode may reduce graphics performance.
### Result and limitations
The T2 Mac Intel Graphics entry showed a blank screen on the first attempt, but booted successfully on the second attempt. After proceeding with this modified image, my installation now works instead of failing after login.
This is a successful workaround on one machine, not a claim of long-term stability or proof that every setting above is necessary. Intel selection and the applicable power-management changes were bundled together, so I have not isolated their individual effects. External displays, suspend/resume and GPU-heavy applications have not been evaluated as part of this report. No `omarchy-debug` output or crash journal is attached yet.
### Suggested improvement
Please consider a supported, hardware-aware T2 hybrid-graphics workaround during installation, applied before the first installed boot, and an Intel Graphics boot option for affected Macs. Keeping a separate Safe Graphics fallback would also help. Merely adding `nomodeset` to the live installer does not address this post-install failure.
Related: #9609 and discussion #4917. Posting this as an additional 4.0.4 reproduction and a record of the working installer changes; feel free to consolidate it into #9609 if that is the preferred tracking issue.
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 16:21 UTC