Omarchy on Mac: Intel, T2 and Apple Silicon explained
Identify the Mac generation, separate native installation from emulation, and understand boot security, hardware limitations and recovery planning.
Based on public documentation; not hardware-tested. Match the instructions to your version and hardware.
“Mac support” is not one compatibility answer. An Intel Mac, an Intel Mac with a T2 chip and an M-series Mac have different CPUs and boot arrangements. Identify the machine before preparing an installer; a model’s marketing name alone can span different generations.
Make the first decision from the processor
Section titled “Make the first decision from the processor”| Machine | Native route described by Omarchy | What to investigate next |
|---|---|---|
| Intel Mac without T2 | Official guide describes Intel installation, with model-dependent limitations | Boot media, exact model’s devices and recovery |
| Intel Mac with T2 | Official guide describes additional boot permission and T2 hardware handling | Apple Startup Security Utility and T2-specific device support |
| Apple Silicon, such as M1/M2/M3/M4 | Reviewed official guide does not directly support a native M-series installation | Asahi’s model matrix for Linux; a separate project, not an Omarchy ISO procedure |
The official Mac guide is the source for Omarchy’s support boundaries. Use About This Mac/System Information to record the processor and exact model identifier. Verify whether it has T2 using Apple’s information rather than guessing from the presence of a Touch Bar: Touch Bar and T2 are not interchangeable labels.
Intel installation: plan what happens to macOS
Section titled “Intel installation: plan what happens to macOS”The official Mac procedure describes replacing the system, including erasing macOS. It is not a documented promise that macOS/Omarchy dual boot works on every Intel model. If preserving macOS is mandatory, stop before the disk operation and establish a model-specific alternative; do not improvise partitions using a generic PC tutorial.
Before booting the USB:
- Make a recoverable copy of personal files, including files outside common Documents folders.
- Check that you can reach macOS Recovery and understand Apple’s recovery route for that machine.
- Record the exact model, T1/T2 status, Wi-Fi, audio and input requirements.
- Prepare a wired/receiver keyboard and a working network fallback where needed.
- Verify and write the official ISO; keep recovery media separate from the USB you are about to erase.
On Intel Macs, the official guide uses Option at startup to choose EFI boot media and Command + R for Recovery. Those instructions should not be transplanted onto Apple Silicon, whose startup-options procedure differs.
T2 startup security is its own control
Section titled “T2 startup security is its own control”For a T2 Intel Mac, Apple’s Startup Security Utility guide explains the Recovery utility, boot security level and external/removable boot permission. Omarchy’s Mac procedure calls for settings that allow its installation media to boot. Record the previous settings so you can deliberately restore the appropriate policy if returning to macOS.
Three things often confused here are:
| Control | Purpose | Does it solve the others? |
|---|---|---|
| Apple startup security | Which OS/boot media this Mac permits | Does not verify a downloaded ISO with GPG |
| External boot permission | Whether removable media may start | Does not select the disk to erase |
| Linux disk encryption | Protects installed data at rest | Does not authorize an external OS to boot |
Do not clear keys or reset every firmware option because a generic Linux guide mentions a different PC’s security setting. If USB media is absent from the picker, investigate media/permission first. If it appears but later loses graphics, you have passed a different boundary.
Device support requires a separate acceptance plan
Section titled “Device support requires a separate acceptance plan”Omarchy describes handling for Broadcom networking, SPI keyboards and some storage issues, with additional T2 kernel/firmware, audio and fan handling. It also reports T1-era limitations including audio/Touch Bar. This is a reason to check your exact model, not to assume every Intel Mac becomes fully compatible after the installer finishes. The manual’s model table should not replace Apple’s hardware identification.
After installation, test: internal keyboard/trackpad, Wi-Fi reconnect, speakers and microphone separately, headphone output, webcam, brightness, external displays, lid close/wake and fan behavior under a modest load. Keep these observations tied to the model and release. A keyboard that works at login can still differ at encrypted-disk unlock; an external display working says nothing about the internal microphone.
A useful fault report says “model identifier, Omarchy version, device, first failing stage, exact error.” Avoid general claims such as “Mac audio does not work.” Route ordinary device faults through hardware guides; retain the Mac-specific context.
Apple Silicon: why Asahi is not an Omarchy install recipe
Section titled “Apple Silicon: why Asahi is not an Omarchy install recipe”Apple Silicon uses ARM and a platform-specific boot/device stack. Asahi Linux works on this platform, and its feature matrix tracks models and capabilities. That work does not make the standard Intel Omarchy ISO an ARM installer, nor does it establish that an arbitrary Omarchy setup script supports an Asahi system.
If your immediate aim is Linux on an M-series Mac, choose a supported Asahi route for the exact model and accept that it is a different distribution/setup. If your aim is specifically learning Omarchy, use a compatible Intel/AMD machine or assess the VM choices. Fusion’s ARM guests are not Intel Omarchy guests; Parallels’ Intel emulator has explicit preview restrictions and should not be presented as normal support.
Decide before modifying the disk
Section titled “Decide before modifying the disk”Proceed only when you can explain: which architecture you have, which supported installation path you intend, what gets erased, how you return to a usable system, and which devices still need testing. Neither a benchmark from one Mac nor a successful screenshot proves your own model’s reliability. The valuable outcome of preparation is a clear boundary between an installation you can attempt and one the current documentation does not support.