An experimental, Omarchy-inspired desktop for Apple A-series devices. Built on Arch Linux ARM, with Omarchy's look and feel reworked for touch.
You need a Mac or Linux computer, a USB cable, and a compatible device (iPad Air 2, iPad 5–7, iPhone 7–X) on iOS or iPadOS 15 or later.
- Back up your device.
- Make room for Linux (at least 9 GB):
- Install palera1n 3.0 beta 3. On a Mac, run
export RA1N_CLI=1 PALERA1N=/Applications/palera1n.app/Contents/MacOS/palera1nbefore the next step. - Download and unzip Resize APFS, then run
./resize-apfs bootin its folder and follow the prompts. - When the device has started, open the Resize APFS app, choose Adjust size, and wait for Completed and verified.
- Install palera1n 3.0 beta 3. On a Mac, run
- Put the device in DFU mode; the screen stays black.
- Install:
curl -fsSL https://github.com/OrchardLinux/omarchy-a/releases/latest/download/install.sh | sh - After a restart, start it again from your computer: DFU mode, then
orchard launch.
Update from the device with Update > Omarchy in the menu. The Linux storage is not encrypted. For problems, see Troubleshooting.
An iPad cannot boot a Linux installer like a PC boots an ISO. How Omarchy A gets from DFU to desktop explains the boot path, release format, device runtime, and installation lifecycle.
- Desktop: improve touch interaction, the shell, applications, and Omarchy integration here.
- Hardware and host tooling: contribute kernel patches, device trees, firmware recipes, runtime support, device adapters, boot transports and installation workflows to orchard.
- Create your own remix: customize the desktop, root filesystem, and image policy using the same release format; minimal-linux provides a smaller, Alpine-based example.
See CONTRIBUTING.md for bring-up guidance and BUILD.md for image assembly and validation.
This repository is the distribution: desktop, root filesystem and release. The
hardware support and the orchard tool live in
orchard; put its launcher on your PATH
once (see its README). Here,
orchard runs orchard's newest nightly, whose kernels, m1n1, Pongo and tools this
build then takes as they are. To work against your own orchard checkout, e.g. a
branch with a driver you need, run that checkout's launcher instead
(../orchard-installer/bin/orchard build). To test package changes (Labwc,
wlroots, Mesa, …) before they are published, keep a checkout of
OrchardLinux/packages beside this one
(../packages): orchard build then builds every package of the image whose
recipe there differs from the published one, caches it by recipe, installs it in
place of [orchard]'s, and prints which packages it built. A checkout elsewhere
is --packages DIR. A gitignored orchard.local.toml may hold your board and
that choice:
device = "j71b"
# packages = "../somewhere/packages" # another checkout; false: published packages onlyorchard.toml (its [release] table) makes this checkout an orchard distribution:
orchard build # every component that changed, then a release in out/releases/dev-DATE-TIME
orchard run # build, then start that release's recovery on the attached iPad, from RAM
orchard install # install the last build
orchard python -m unittest discover -s testsorchard build runs tools/build.py, which keeps each component (desktop,
base, artwork, …) in out/components/ and rebuilds it only when its files
change; orchard brings Pongo, the recovery tools and the kernels.
BUILD.md describes the steps one by one.
RAM experiments and device bring-up happen in orchard itself, with its examples and bring-up guide.
Hardware work before and after installation (recovery boot, device-tree capture, firmware preparation, RAM experiments, bringing up a new device) happens with orchard from a checkout; see its device bring-up guide.
See Troubleshooting for USB connectivity, diagnostics, and failed installations.