Omarchy now runs on Anduril’s BlueChip, and the Omarchy kernel gets its own device tree for it
Ten days after asking Palmer Luckey to make it happen, DHH has Omarchy booting on Anduril’s US-built laptop, with two kernel pull requests merged the same afternoon.
Image: DHH (X)
On October 27, DHH said he wanted Omarchy on Anduril’s BlueChip, and Palmer Luckey asked for his address. On November 6, 2026, the wish came true. “Omarchy is up and running on the @anduriltech BlueChip!!” DHH posted on X, adding: “All our work on @Snapdragon compatibility is paying off. This thing is awesome, @PalmerLuckey! We are going to make it a superb Omarchy machine.” The post came with two photos and had more than 100,000 views at the time of writing.
The paper trail on GitHub shows how fast it went. At 15:23 UTC that day, a hardware report from the Omarchy Arm installer was filed under DHH’s GitHub account. It lists the manufacturer as Anduril, the product as “Qualcomm Glymur”, and the processor as a Snapdragon X2 Elite X2E88100. The report also notes that Windows was still on the laptop.
Twenty minutes later, Birk Skyum, who joined Omarchy Core this week as the Dragon team delegate, opened a first pull request against the aarch64 Omarchy kernel. According to its description, the laptop is built on Qualcomm’s Glymur reference design: every device in its firmware tables carries the CRD’s subsystem ID, and the touchpad, keyboard, embedded controller, NVMe drive and Wi-Fi chip sit exactly where they do on the CRD. So the PR simply teaches systemd-stub to pick the Glymur CRD’s device tree on this machine, which systemd doesn’t list on its own. The one thing left out was the touchscreen, a Goodix part instead of the CRD’s FocalTech, which “stays off until the laptop gets its own tree.” Ryan Hughes merged it 30 minutes after it was opened.
That own tree followed within the hour. Birk’s second pull request adds a device tree for the Anduril BlueChip proper, through four kernel patches: an Anduril vendor prefix, the board’s binding, the tree itself and a QSEECOM allowlist entry, as the CRD has. The tree reuses the CRD’s and changes two things: it lists the Goodix touchscreen at both of the addresses it can sit at, depending on the panel, and keeps PCIe 6 off since the firmware reports no WWAN slot. The laptop’s hardware IDs move from qcom,glymur-crd to anduril,bluechip. Ryan Hughes merged it at 17:13 UTC, less than an hour before DHH’s post.
A caveat from the PR itself: when it was written, “the one machine with these IDs hasn’t installed Omarchy yet.” It also warns that an already installed system would need to run omarchy apply hardware before booting the new kernel, since kernel updates don’t refresh the device tree list baked into the UKI. Both changes are merged into omarchy-pkgs and are coming in the next Omarchy kernel build.
The PR is also candid about firmware. The CRD’s tree points to the Qualcomm-signed Glymur DSP and GPU firmware from linux-firmware, and whether this laptop accepts it “shows on its first install.” DHH’s “we are going to make it a superb Omarchy machine” suggests there’s polishing ahead.
The community wasted no time dressing it up either. Tom Ballard replied to DHH that it was a shame he didn’t use the theme, pointing to his BlueChip theme for Omarchy: dark navy, warm ivory text, steel-blue accents and ten 8K wallpapers mixing pressed metal and faded Americana. Its README is clear that it’s a “personal concept theme; not an official BlueChip, Omarchy or Anduril collaboration release.”
