Omarchy Hardware

Apple

MacBook 12-inch (Early 2015)

Twenty-two exact-model owner accounts include 13 people running Omarchy and a long Linux record of Apple SPI input failures, workarounds and current owner-confirmed progress.

22exact-model reportsReport mix: 13 Omarchy · one Arch Linux · one Arch-based · seven other Linux

Bottom line

Omarchy can run on this MacBook, but it is not yet a clean installation. The current installer still needs external input. After installation, five exact-model owners confirm that forcing the SPI controller into PIO mode restores the built-in keyboard and trackpad; three of them also establish the s2idle path through lid-close tests, and one verifies the keyboard at encrypted boot. The Omarchy change that would automate the core workaround remains open and unmerged. Speakers, Bluetooth and the camera require separate support paths and do not have equivalent current Omarchy confirmation.

An existing owner can turn the machine into a light-duty Omarchy computer if they are comfortable installing with a USB keyboard and applying a manual kernel configuration. As a used purchase, its 8GB memory ceiling, passive dual-core processor, single shared USB-C port, old battery and component-specific fixes make it a niche choice rather than a general recommendation. Buy it for extreme portability and reuse, not for local virtual machines, heavy compilation, modern games or a trouble-free Linux laptop.

What is reported

10 findings with cited evidence

  • Install and boot

    Owners can complete an Omarchy installation with external USB input, but the built-in keyboard and trackpad still do not work in the live installer. The pending exact-model change explicitly preserves that limitation.

    Have a USB keyboard ready before starting. Do not assume that a post-install input workaround will also make the installer or encrypted preboot prompt usable.

    Problems reportedSource 1, Source 2, Source 3

  • Desktop and graphics

    Omarchy owners reach a working desktop, and exact Linux inventories show the Intel HD Graphics 5300 using i915 and Mesa hardware acceleration at the panel's native resolution. No retained source is a controlled Omarchy graphics benchmark.

    The graphics path is sufficient for the desktop and ordinary 2D use. Treat the old integrated GPU as a capacity limit, not as an unresolved installation blocker.

    Working reportsSource 1, Source 2, Source 3

  • Internal display and brightness

    Exact Linux reports drive the 2304-by-1440 internal panel at 60 Hz, and Omarchy owners reach the desktop. The retained Omarchy reports do not separately establish brightness hotkeys or automatic brightness.

    The panel has a positive working baseline. Test brightness controls separately rather than reading the display result as proof that every key and sensor works.

    Working reportsSource 1, Source 2, Source 3

  • Keyboard, hotkeys and backlight

    Apple SPI input failed across years of exact-model Linux and Omarchy reports, often with repeated -110 timeouts. Five current Omarchy owners now confirm the PIO direction: three establish boot, login and lid-close behavior with s2idle, while another independent report verifies the keyboard at encrypted boot. The project has not shipped that change, and keyboard backlighting is not established.

    After installation, apply the current PIO and s2idle workaround and verify ordinary keys, LUKS input, hotkeys and backlighting as separate checks. Keep external input available until the Omarchy change ships and is retested.

    Mixed resultsSource 1, Source 2, Source 3, Source 4, Source 5, Source 6, Source 7, Source 8, Source 9, Source 10

  • Touchpad and pointing

    The Force Touch trackpad shares the Apple SPI failure with the keyboard. Current PIO reports restore pointing after installation, including a new independent exact-model confirmation; the s2idle reports preserve it across lid-close tests. The installer still needs external input, and deep sleep can strand the device.

    Treat keyboard and trackpad recovery as the same controller problem, while testing gestures and the haptic click separately after the devices appear.

    Mixed resultsSource 1, Source 2, Source 3, Source 4, Source 5, Source 6

  • Wi-Fi and Bluetooth

    Exact Linux inventories show Broadcom Wi-Fi working. An Omarchy owner reported Bluetooth missing in 2025, and an exact-model support project now offers a DSDT override plus an additional driver, but there is no retained current Omarchy confirmation.

    Wi-Fi has the stronger evidence. Bluetooth is a separate repair involving boot-time ACPI changes and disabled Secure Boot or lockdown, so do not assume that working Wi-Fi means the whole radio works.

    Mixed resultsSource 1, Source 2, Source 3, Source 4

  • Speakers, microphone and audio

    Multiple exact Linux owners report silent internal speakers while the 3.5 mm headphone path works. One exact-model support project gets the speakers working through a custom DKMS and PipeWire stack, with additional handling needed after deep sleep and for headphone switching.

    Expect headphones to be the simpler path. Internal speakers are not a stock Omarchy success and should be treated as an advanced, separately maintained modification.

    Problems reportedSource 1, Source 2, Source 3, Source 4

  • Camera

    An exact Linux owner loaded the FaceTime driver and saw the camera light without receiving video. A later exact-model change for the smaller sensor was merged into the out-of-tree facetimehd project, but there is no retained Omarchy owner retest.

    The project path has improved, but the camera is not a confirmed Omarchy feature. It still depends on an out-of-tree driver and proprietary firmware extraction.

    Problems reportedSource 1, Source 2, Source 3

  • Suspend and resume

    Deep sleep repeatedly killed the keyboard and trackpad in exact-model reports. Current Omarchy owners confirm that s2idle plus the PIO input configuration survives lid close; hibernation can also work, but it needs additional hooks and disk-backed swap that are outside the pending Omarchy change.

    Use s2idle and test a long lid-close cycle, not just a quick wake. Treat hibernation as a separate manual project, and expect higher standby draw than a fully working deep-sleep path.

    Mixed resultsSource 1, Source 2, Source 3, Source 4, Source 5

  • Battery, power and thermals

    The fanless Core M chassis is silent but loses sustained performance under combined or repeated load. Historical new-machine testing reached 7 hours, 36 minutes in one controlled macOS Wi-Fi test; that is not an Omarchy runtime prediction, and current s2idle guidance trades reliable wake for higher standby use.

    Judge a used unit by battery health and sustained work, not by Apple's original runtime claim or short boost speed. The machine is better suited to bursty light work than continuous CPU or graphics load.

    Mixed resultsSource 1, Source 2, Source 3, Source 4

Changes over time

15 dated events
  1. Ubuntu owner records input loss after suspend

    An exact-model owner reproduces dead keyboard and trackpad after suspend on two kernel lines, establishing the long-running deep-sleep failure.

  2. Fedora logs show the recurring -110 timeout

    The Apple SPI devices enumerate, but transfers time out and the controller's interrupt fails on an exact MacBook8,1.

  3. One machine works on Ubuntu but not Arch, Manjaro or openSUSE

    The same exact-model owner reports working input on Ubuntu 20.04 and dead input after GRUB on three rolling distributions, including Arch.

  4. Avoiding sleep preserves input but drains more battery

    An exact owner uses display-off instead of sleep across distributions and desktop stacks, keeping input available at the cost of greater closed-lid energy use.

  5. Mint inventory separates working core hardware from weak components

    The display and accelerated Intel graphics work, but input needs repeated boots and audio, Bluetooth and the camera are absent.

  6. Omarchy installation requires external input

    An exact 2015 owner installs Omarchy 3.0.1 with a USB keyboard and mouse, then finds built-in input and Bluetooth still unavailable after boot.

  7. Omarchy 3.0.2 adds the MacBook8,1 identifier

    The merged change corrects model detection and includes Apple SPI modules in the initramfs path, but does not address the controller's DMA failure.

  8. Owners show that the 3.0.2 change did not fix input

    Two exact owners retest the advertised release and still need external installer input, with the built-in keyboard and trackpad dead afterward.

  9. A Pop kernel restores post-install input

    One Omarchy owner gets the built-in devices working on a Pop kernel while continuing to need external input for installation and initial setup.

  10. The kernel workaround fails after sleep

    Another exact owner loses input after suspending with the Pop kernel, then reports recovery after separate sleep and bootloader changes.

  11. CachyOS owner rules out the available configuration fixes

    An exact owner on Linux 7.0.12 still records zero controller interrupts and repeated -110 timeouts after trying the thread's module, power and boot-parameter suggestions.

  12. An upstream series proposes forcing this controller into PIO

    Linux developers post a MacBook8,1-specific PXA2xx SPI change after tracing the timeout to DMA. The retained series is under review rather than a released-kernel result.

  13. Current Omarchy owners confirm PIO and s2idle

    Three exact owners report working keyboard and trackpad through boot, login, lid close and hibernation tests on current stock Arch kernels; a fourth confirms the same PIO direction.

  14. The Omarchy integration is proposed but not shipped

    An exact-machine PR adds the PIO and s2idle parameters for installed systems. It remains open, unmerged and explicitly leaves live-installer input, speakers, camera and Bluetooth out of scope.

  15. Another owner confirms the PIO workaround

    A new exact-model owner independently confirms that disabling the broken DMA path restores the built-in keyboard and trackpad, including keyboard input at the encrypted boot prompt. The Omarchy integration remains open and unmerged.