Are we ARM yet?
Omarchy on ARM PCs, model by model.
Every ARM laptop needs a device tree, hardware IDs and firmware. Omarchy ships them in its own packages, often before Linux, systemd and linux-firmware have them. The Omarchy view shows what its channels ship today, and the Upstream view what every distro gets. Boots means an owner reached the desktop on Omarchy RC, with linux-omarchy 7.3-3 and systemd 262.1-1. Booting is the first goal; features like suspend and USB4 come next.
Own an ARM laptop that isn't green yet? Help get it there, whatever distro you run. It only takes a few minutes.
How to helpSnapdragon X and X2 83
ShowHide
Snapdragon X and X2 83
ShowHide1 works out of the box on Omarchy today, 23 more once open pull requests land and 11 once Omarchy carries pieces that exist elsewhere. The others still need a device tree (32), hardware IDs (8) or firmware from outside Windows (8).
11 models are ready to test on Omarchy RC, and owners have confirmed 2 boot to the desktop and reported problems on 6. A machine for the team would help most for the 32 models nobody we know has, the 3 with problems the team can't reproduce and the 2 whose tree nobody has booted. Every other device tree was written or booted by someone with the machine. To help a model along, send a hardware report from Windows, the device tree you boot with on Linux, or a boot test, as Help a model get there explains.
How far ahead Omarchy is
Models with each piece in Omarchy, on any channel, against the releases of Linux, systemd and linux-firmware. On Omarchy's bar the striped part comes from upstream, the green part is what Omarchy adds, the amber part is in an open pull request on omarchy-pkgs, and the grey part exists elsewhere but Omarchy doesn't carry it yet.
- Device tree
- 7 ahead
- Hardware IDs
- 2 ahead
- Firmware
- even
- All three
- even
What the labels meandoneon its waymissinganother way or not neededShowHide
Out of the box
Whether a fresh Omarchy install has everything it needs, and if not, what it still lacks.
- On stable
- A fresh install from Omarchy's stable channel has its device tree, hardware IDs and firmware.
- On RC
- A fresh install from Omarchy's RC channel has its device tree, hardware IDs and firmware.
- On edge
- A fresh install from Omarchy's edge channel, the nightly image, has its device tree, hardware IDs and firmware.
- After PRs
- Every piece Omarchy still lacks is in an open pull request on omarchy-pkgs.
- Needs carrying
- Every piece exists, but Omarchy doesn't carry all of them yet.
- Needs a tree
- Nobody has written its device tree yet.
- Needs IDs
- Nobody has sent its hardware IDs yet, so an install image can't pick its device tree.
- Needs firmware
- Its firmware has only turned up in Windows so far, so the installer copies it from the laptop's own Windows.
ACPI dump
The laptop's own hardware tables, which a device tree is written from.
- Collected
- Its ACPI tables are in the aarch64-laptops collection, an owner's hardware report or this board's copy of a dump not merged there yet.
- Not needed
- It already has a device tree.
- Wanted
- The first thing to send for a model without a device tree.
Device tree
The description of the hardware that Linux needs for each model, in Omarchy's kernel.
- Stable
- Omarchy's stable kernel ships it (linux-omarchy 7.2.8-13).
- RC
- Omarchy's RC kernel ships it (linux-omarchy 7.3-3), the one the current install image has.
- Edge
- Omarchy's edge kernel ships it (linux-omarchy 7.3-12), the one the nightly image has.
- Open PR
- An open pull request on omarchy-pkgs adds it to Omarchy's kernel.
- Not carried
- One exists, in a newer Linux, a posted patch or out of tree, but Omarchy's kernel doesn't carry it yet. Whoever wrote it had the machine, unless the Machine column says the tree is untested.
- Wanted
- Doesn't exist yet. An ACPI dump is what one gets written from.
Hardware IDs
How Omarchy's install image recognises the model and picks its device tree.
- Stable
- Omarchy's stable channel recognises it and picks its device tree, through systemd's list or the IDs Omarchy's kernel adds.
- RC
- Omarchy's RC channel recognises it and picks its device tree, through systemd's list or the IDs Omarchy's kernel adds.
- Edge
- Omarchy's edge channel recognises it and picks its device tree, through systemd's list or the IDs Omarchy's kernel adds.
- Open PR
- An open pull request on omarchy-pkgs adds its hardware IDs to Omarchy's kernel.
- Not carried
- Its hardware IDs exist, in a newer systemd, Ubuntu's stubble or sent in here, but Omarchy doesn't carry them yet.
- Mismatch
- systemd's entry names a different device tree than the kernel's, so it never matches.
- Wanted
- Nobody has sent its hardware IDs yet.
Firmware
Signed files for its audio, sensor and graphics chips, in Omarchy's packages. Booting doesn't need them, but without them there's no sound, battery status, USB-C display, sensors or graphics acceleration.
- Stable
- Every file its device tree loads is in Omarchy's stable packages, from linux-firmware or the maker's own package.
- RC
- Every file its device tree loads is in Omarchy's RC packages, from linux-firmware or the maker's own package.
- Edge
- Every file its device tree loads is in Omarchy's edge packages, from linux-firmware or the maker's own package.
- Open PR
- An open pull request on omarchy-pkgs packages the maker's files.
- Partly
- Omarchy's packages have some of the files its device tree loads. The installer copies the rest from Windows.
- Not packaged
- The maker's driver download has it, but Omarchy doesn't package it yet. Until then the installer copies it from Windows.
- From Windows
- Omarchy's installer copies it from the laptop's own Windows. Nobody has found it in a maker's download yet.
Boots
Has an owner reached the desktop on it? Tested on Omarchy so far, and reports from any distro are welcome. Booting is the first goal for every model; features like suspend and USB4 come next.
- Boots
- An owner booted into the Omarchy desktop on the current release. Not every feature has to work yet.
- Ready to test
- Omarchy's kernel has its device tree and the install image picks it by itself, but no owner has confirmed it boots yet.
- Problems
- An owner couldn't get to the Omarchy desktop on the current release without a workaround.
- Not recognised
- Omarchy's kernel has its device tree, but the install image doesn't recognise this model, because systemd has no hardware IDs for it. Its hardware IDs would fix that.
- Newer kernel
- Its device tree is in Omarchy's edge kernel or a newer Linux, but not in the RC kernel (7.3-3) yet. It's ready to test once the RC gets it.
- No device tree
- Nobody has written a device tree for it yet, so Linux can't start on it.
Machine
Where getting the machine to the Omarchy team would help most.
- Nobody has one
- No device tree, no ACPI dump and no owner report, so nobody we know has one. The machine itself would give its tables, tree, hardware IDs, firmware and the boot test.
- Tree untested
- Its device tree was written from an owner's ACPI tables, without the machine, and nobody has booted it yet. An owner booting it, or the machine, confirms it.
- Would help
- Owners report problems and nobody on the team has one, so each fix waits on a round trip with an owner.
- Linux community
- Someone in the wider Linux community has one: its tree is in Linux or a posted patch, an owner keeps one in their own repository, or its tables are in aarch64-laptops. They can test it, but it takes reaching them first.
- Omarchy community
- Someone in Omarchy's community has one: they reported on an Omarchy release, sent a hardware report from its installer tool or its hardware IDs, or work on it in an Omarchy discussion. We can ask them to test.
- Team has one
- Someone on the Omarchy team has one.
Colours and badges
Every label also explains itself when you point at it.
- Green
- Done.
- Amber
- On its way, or partly there.
- Red
- Missing or failing, and where help counts most.
- Grey
- Works another way today, or not needed.
- Announced
- Announced by the vendor, but not confirmed in shops yet.
What the labels meandoneon its waymissinganother way or not neededShowHide
Linux
Its device tree in Linux itself.
- Linux 6.x
- In Linux since that release.
- linux-next
- Accepted, and coming in the next Linux release.
- Kernel patch
- Sent to the Linux kernel mailing list as a patch, not accepted yet.
- Out of tree
- One exists outside Linux, in Omarchy's kernel, Ubuntu's kernel or a community repository, but it hasn't been sent there yet.
- Wanted
- Doesn't exist yet.
systemd
Its hardware IDs in systemd's list, which boot images pick the device tree from.
- systemd 2xx
- In systemd's list since that release, so an install image recognises the model.
- In Ubuntu
- In the list of Ubuntu's stubble, which systemd copies its list from in batches. Not in systemd yet.
- Stubble PR
- A pull request adding its hardware IDs is open on Ubuntu's stubble, which systemd copies its list from in batches.
- Collected
- Its hardware IDs have been sent in, and still have to go to Ubuntu's stubble, which systemd copies its list from.
- Mismatch
- systemd's entry names a different device tree than the kernel's, so it never matches.
- Wanted
- Not in systemd's list yet.
linux-firmware
Its firmware files in linux-firmware.
- Released
- Every file its device tree loads is in linux-firmware's newest release (20261019).
- Next release
- Merged into linux-firmware, and coming with its next release.
- MR open
- A merge request with its files is open on linux-firmware, not merged yet.
- Partly
- linux-firmware has some of the files its device tree loads.
- Missing
- linux-firmware doesn't have its files. It takes them only when the maker submits or signs them off.
Colours and badges
Every label also explains itself when you point at it.
- Green
- Done.
- Amber
- On its way, or partly there.
- Red
- Missing or failing, and where help counts most.
- Grey
- Works another way today, or not needed.
- Announced
- Announced by the vendor, but not confirmed in shops yet.
Where's my model number?
It's on the sticker underneath. In Windows, open System Information and look at System Model and System SKU. On Linux, run
cat /sys/class/dmi/id/product_name cat /sys/class/dmi/id/product_sku
A full number like 83ED0049US or 14-fe0013dx finds its series.
Show only | Show only | Show only | Show only | Show only | Show only | Show only | Show only | Show only |
|---|---|---|---|---|---|---|---|---|
| Acer | Snapdragon X · 2025 · X1-26-100 · A14-11M, A14-11MT A draft device tree, written from owners' hardware reports. It shares almost everything with the Aspire 16's, which an owner booted on Ubuntu's live USB, but nobody has tried it on an Aspire 14 yet. | After PRs | Collected | Edge | Edge | Open PR | Newer kernel | Tree untested |
| Acer | Snapdragon X · 2025 · X1-26-100 · A16-11M, A16-11MT A draft device tree, written from owners' hardware reports. An owner booted it on Ubuntu's live USB in November 2026, with the screen, keyboard, disk, USB, battery and Bluetooth working. Wi-Fi needs a board file copied from Windows, since linux-firmware has none for its card. | After PRs | Collected | Edge | Edge | Open PR | Newer kernel | Omarchy community |
| Acer | Snapdragon X · 2026 · X1-26-101 · AL14-11M | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Acer | Snapdragon X · 2024 · X1E-78-100, X1P-64-100 · SF14-11, SF14-11T | After PRs | Not needed | Edge | Stable | Open PR | Newer kernel | Linux community |
| Acer | Snapdragon X · 2024 · X1E-78-100 · SFA14-11 | After PRs | Collected | Open PR | Open PR | Open PR | No device tree | Linux community |
| Acer | Snapdragon X · 2024 · X1P-42-100 · SFG14-01 | After PRs | Not needed | Edge | Stable | Open PR | Newer kernel | Linux community |
| Acer | Snapdragon X2 · 2026 · X2E-78-100 · SFSP14-Q51T | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| ASUS | Snapdragon X2 · 2026 · X2E-88-100 · QN10, 90MS03E2-M000B0 A draft device tree, written from its ACPI tables on the Zenbook A16's, whose firmware describes the same power, USB and PCIe wiring. Nobody has booted it yet. Ethernet and HDMI are the likeliest gaps. | Needs IDs | Collected | Not carried | Wanted | From Windows | No device tree | Tree untested |
| ASUS | Snapdragon X · 2024 · X1P-42-100 · HT5306QA | Needs carrying | Not needed | Not carried | Not carried | Open PR | No device tree | Omarchy community |
| ASUS | Snapdragon X2 · 2026 · X2E-88-100 · HT7407NA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| ASUS | Snapdragon X · 2026 · X1-26-100 · VM441QA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| ASUS | Snapdragon X · 2026 · X1-26-100 · VM471QA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| ASUS | Snapdragon X · 2025 · X1-26-100 · X1407QA, A1407QA Owners boot it with the X Plus Vivobook S 15's device tree or a patched Zenbook A14 one. | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| ASUS | Snapdragon X · 2025 · X1-26-100 · X1607QA, F1607QA, A1607QA | Needs firmware | Not needed | Not carried | Not carried | From Windows | No device tree | Omarchy community |
| ASUS | Snapdragon X · 2024 · X1E-78-100, X1P-64-100, X1P-42-100 · S5507QA, S5507QAD, Q5507QA
The maker download on the firmware page has the X Elite model's files only. ASUS sells both chips as S5507QA, so which package carries the X Plus model's signed files isn't clear yet. | After PRs | Collected | Stable | Stable | Open PR | Problems | Would help |
| ASUS | Snapdragon X · 2025 · X1-26-100 · S3407QA | Needs IDs | Not needed | Not carried | Wanted | Open PR | No device tree | Linux community |
| ASUS | Snapdragon X · 2026 · X1-26-101 · S5408QA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| ASUS | Snapdragon X · 2026 · X1-26-100 · TP5408QA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| ASUS | Snapdragon X2 · 2026 · X2E-88-100 · S3607NA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| ASUS | Snapdragon X · 2025 · X1-26-100 · S3607QA
A draft device tree, written from two owners' hardware reports, in an OLED and an LCD version. An owner booted the OLED version on Ubuntu's live USB in November 2026, with the screen, keyboard, touchpad, Bluetooth, USB, HDMI and disk working. Wi-Fi needs board data that linux-firmware doesn't have yet. | Needs carrying | Collected | Not carried | Not carried | Open PR | No device tree | Omarchy community |
| ASUS | Snapdragon X · 2026 · X1-26-101 · S5608QA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| ASUS | Snapdragon X · 2026 · X1-26-100 · TP5608QA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| ASUS | Snapdragon X · 2026 · X1-26-100 · UX3480QA The device tree builds on the Zenbook A14 UX3407QA's and isn't posted to the kernel lists yet. The hardware IDs are proposed in ubuntu/stubble#96 and the ACPI tables in aarch64-laptops/build#178. | Needs carrying | Not needed | Open PR | Open PR | Not packaged | Problems | Team has one |
| ASUS | Snapdragon X · 2025 · X1E-78-100, X1P-42-100, X1-26-100 · UX3407RA, UX3407QA
| After PRs | Collected | Stable | Stable | Open PR | Ready to test | Linux community |
| ASUS | Snapdragon X2 · 2026 · X2E-88-100 · UX3407NA | Needs carrying | Not needed | Not carried | Stable | Open PR | Newer kernel | Linux community |
| ASUS | Snapdragon X2 · 2026 · X2E-96-100, X2E-94-100 · UX3607OA | Needs carrying | Collected | RC | Stable | Partly | Ready to test | Linux community |
| Dell | Snapdragon X · 2024 · X1P-64-100, X1P-42-100, X1-26-100 · 5441, P190G, P190G001
| Needs IDs | Collected | Open PR | Wanted | Open PR | No device tree | Linux community |
| Dell | Snapdragon X · 2024 · X1E-80-100, X1P-64-100 · 7441, P190G, P190G001 | After PRs | Collected | Stable | Stable | Open PR | Problems | Team has one |
| Dell | Snapdragon X · 2024 · X1P-64-100, X1P-42-100, X1-26-100 · 5455, P190G | After PRs | Collected | Edge | Stable | Open PR | Newer kernel | Linux community |
| Dell | Snapdragon X · 2024 · X1E-80-100, X1P-64-100 · 7455, P190G, P190G001 | After PRs | Collected | Stable | Stable | Open PR | Ready to test | Linux community |
| Dell | Snapdragon X · 2024 · X1E-80-100, X1P-64-100 · 9345, P189G, P189G001 | After PRs | Collected | Stable | Stable | Open PR | Ready to test | Linux community |
| Dynabook | Snapdragon X · 2025 · X1P-42-100 · P1D5APBL, W6XDZA5BAM-K | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Fujitsu | Snapdragon X · 2026 · X1-26-100 · WU6-L1, UQ-L1, FMVUQSL1WA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Honor | Snapdragon X · 2024 · X1E-80-100 · MRO-521 Honor's driver download has no compute DSP firmware, so those two files still come from the laptop's own Windows. | Needs firmware | Collected | RC | Stable | From Windows | Ready to test | Linux community |
| HP | Snapdragon X · 2025 · X1E-78-100, X1P-42-100, X1-26-100 · HSN-Q42C, 8E06 | After PRs | Collected | Edge | Stable | Open PR | Newer kernel | Linux community |
| HP | Snapdragon X2 · 2026 · X2E-84-100, X2P-64-100 · HSN-I68C | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| HP | Snapdragon X · 2024 · X1E-78-100, X1P-42-100 · EliteBook Ultra G1q, EliteBook Ultra G1q8, 8CBE | After PRs | Collected | Stable | Stable | Open PR | Ready to test | Linux community |
| HP | Snapdragon X2 · 2026 · X2E-90-100, X2E-88-100, X2E-84-100, X2E-80-100, X2P-42-100 · HSN-I66C-4, 8E91 | Needs carrying | Not needed | Open PR | Stable | Not packaged | Newer kernel | Linux community |
| HP | Snapdragon X · 2026 · X1-26-100 · 14-hz0xxx | Needs IDs | Not needed | Not carried | Wanted | Open PR | No device tree | Linux community |
| HP | Snapdragon X · 2026 · X1-26-100 · 16-bz0xxx | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| HP | Snapdragon X · 2026 · X1-26-100 · 16-ct0xxx | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| HP | Snapdragon X · 2025 · X1P-42-100, X1-26-100 · 14-he0xxx, 14-he0 | Needs carrying | Collected | Not carried | Not carried | Open PR | No device tree | Omarchy community |
| HP | Snapdragon X2 · 2026 · X2P-42-100 · 14-he1xxx | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| HP | Snapdragon X · 2025 · X1P-42-100, X1-26-100 · 16-bf0xxx, 16-fb0xxx Owners run the OmniBook 5 14's out-of-tree device tree on it. | Needs a tree | Wanted | Wanted | Not carried | Not packaged | No device tree | Nobody has one |
| HP | Snapdragon X2 · 2026 · X2P-64-100 · 16-bf1xxx | Needs carrying | Not needed | Not carried | Not carried | Open PR | No device tree | Omarchy community |
| HP | Snapdragon X2 · 2026 · X2E-90-100, X2E-84-100, X2P-64-100 · 14-kg0xxx | Needs IDs | Not needed | Not carried | Wanted | Open PR | No device tree | Linux community |
| HP | Snapdragon X · 2024 · X1E-78-100, X1P-42-100 · 14-fe0xxx, 14-fe1xxx, 8CBE
| After PRs | Collected | Stable | Stable | Open PR | Ready to test | Linux community |
| HP | Snapdragon X2 · 2026 · X2P-42-100, X2P-64-100, X2E-80-100 · 14-kr0xxx, 14-kr1xxx | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| HP | Snapdragon X2 · 2026 · X2E-84-100, X2P-42-100 · 16-cp0xxx, 16-cp1xxx | After PRs | Not needed | Open PR | Open PR | Open PR | No device tree | Omarchy community |
| HP | Snapdragon X · 2025 · X1-26-100, X1P-42-100 · HSN-Q42C Owners report Ubuntu booting on it with the X Plus OmniBook X 14's device tree. | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| HUMAIN | Snapdragon X2 · 2026 · X2E-80-100, X2E-88-100 · Horizon, Horizon Ultra Its out-of-tree device tree is the Glymur reference board's with fixes for this machine, and keeps the reference board's compatible. | Needs IDs | Not needed | Not carried | Wanted | Partly | No device tree | Linux community |
| Lenovo | Snapdragon X · 2025 · X1P-64-100, X1-26-100 · 01Q8X10, 91B6
| After PRs | Collected | Stable | Stable | Open PR | Not recognised | Linux community |
| Lenovo | Snapdragon X · 2024 · X1P-42-100, X1-26-100 · 14Q8X9, 83GH | Needs firmware | Collected | Not carried | Stable | From Windows | No device tree | Linux community |
| Lenovo | Snapdragon X2 · 2026 · X2P-42-100 · 14Q8Y11, 83UK | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Lenovo | Snapdragon X · 2025 · X1-26-100 · 15Q8X10, 83N3, 83TW | Needs firmware | Collected | Not carried | Stable | From Windows | No device tree | Linux community |
| Lenovo | Snapdragon X · 2024 · X1P-42-100, X1-26-100 · 14Q8X9, 83HL
| Needs firmware | Collected | Open PR | Stable | From Windows | No device tree | Linux community |
| Lenovo | Snapdragon X2 · 2026 · X2P-42-100 · 13Q8Y11, 83RK | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Lenovo | Snapdragon X2 · 2026 · X2P-42-100 · 15Q8Y11, 83RL | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Lenovo | Snapdragon X · 2026 · X1-26-100 · 14Q8X12, 84A9 | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Lenovo | Snapdragon X2 · 2026 · X2P-42-100 · 22BB | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Lenovo | Snapdragon X · 2024 · X1P-42-100, X1-26-100 · 21NH | Needs firmware | Collected | Stable | Stable | From Windows | Ready to test | Linux community |
| Lenovo | Snapdragon X · 2025 · X1-26-100 · 13C8, 13C9, 13CA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Lenovo | Snapdragon X · 2024 · X1E-78-100, X1P-42-100 · 21N1, 21N2
| On stable | Collected | Stable | Stable | Stable | Ready to test | Linux community |
| Lenovo | Snapdragon X2 · 2026 · X2E-80-100, X2P-42-100 · 22A7, 22A8 | After PRs | Not needed | Open PR | Open PR | Open PR | Newer kernel | Linux community |
| Lenovo | Snapdragon X · 2024 · X1E-78-100, X1P-64-100 · 14Q8X9, 83ED | Needs carrying | Collected | Stable | Stable | Partly | Boots | Team has one |
| Lenovo | Snapdragon X2 · 2026 · X2E-88-100, X2E-80-100, X2P-42-100 · 14Q8Y11, 83QR | Needs firmware | Collected | Open PR | Stable | From Windows | Newer kernel | Linux community |
| Medion | Snapdragon X · 2024 · X1E-78-100, X1P-42-100 · MD62636, MD62637, MD62695 | After PRs | Collected | Stable | Stable | Open PR | Ready to test | Linux community |
| Microsoft | Snapdragon X · 2025 · X1P-42-100 · 2095 | Needs carrying | Not needed | Not carried | Not carried | Open PR | No device tree | Omarchy community |
| Microsoft | Snapdragon X2 · 2026 · X2P-42-100 · 2145 | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Microsoft | Snapdragon X · 2024 · X1P-64-100, X1E-80-100 · 2036 | After PRs | Collected | Stable | Stable | Open PR | Problems | Would help |
| Microsoft | Snapdragon X · 2024 · X1E-80-100 · 2037 | After PRs | Collected | Stable | Stable | Open PR | Problems | Would help |
| Microsoft | Snapdragon X2 · 2026 · X2P-64-100, X2E-78-100 · 2036, 2138
Two device trees describe this laptop, both on the Mahua chip. Omarchy's kernel carries Jim Martin's, and Qualcomm posted its own to Linux under another name. | Needs carrying | Not needed | Edge | Not carried | Open PR | Newer kernel | Team has one |
| Microsoft | Snapdragon X2 · 2026 · X2E-78-100, X2P-64-100 · 2037, 2139 | Needs a tree | Wanted | Wanted | Wanted | Not packaged | No device tree | Nobody has one |
| Microsoft | Snapdragon X · 2024 · X1P-64-100, X1E-80-100 · 2076, 2085, 2077
| After PRs | Collected | Stable | Stable | Open PR | Boots | Team has one |
| Microsoft | Snapdragon X · 2025 · X1P-42-100 · 2110, 2109 | After PRs | Collected | RC | Open PR | Open PR | Not recognised | Linux community |
| Microsoft | Snapdragon X2 · 2026 · X2P-42-100 · 2148, 2149 | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Microsoft | Snapdragon X2 · 2026 · X2P-64-100, X2E-78-100 · 2076, 2140, 2085 | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Qualcomm | Snapdragon X · 2024 · X1E-00-1DE · X1E001DE Devkit | Needs firmware | Collected | Stable | Stable | From Windows | Ready to test | Linux community |
| Samsung | Snapdragon X · 2024 · X1E-80-100 · NP940XMA, NP944XMA, NT940XMA The speaker amps are WSA883x, not the WSA884x the v8 device tree names. | After PRs | Collected | Open PR | Open PR | Open PR | Problems | Team has one |
| Samsung | Snapdragon X · 2024 · X1P-42-100, X1-26-100 · NP750XQA, NT750XQA, NP750XQB | Needs IDs | Not needed | Not carried | Wanted | From Windows | No device tree | Linux community |
| Samsung | Snapdragon X · 2024 · X1E-80-100, X1E-84-100 · NP960XMA, NP960XMB, NP964XMA | Needs IDs | Not needed | Open PR | Wanted | Open PR | No device tree | Linux community |
| Samsung | Snapdragon X · 2025 · X1-26-100 · NP755XRA | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
| Samsung | Snapdragon X2 · 2026 · X2E-88-100 · NP960XRD, NT960XRD | Needs a tree | Wanted | Wanted | Wanted | From Windows | No device tree | Nobody has one |
Snapdragon 8cx Gen 3 4
ShowHide
Snapdragon 8cx Gen 3 4
ShowHideThe generation before Snapdragon X. They need the same pieces and use the same views and labels as the models above.
Where's my model number?
It's on the sticker underneath. In Windows, open System Information and look at System Model and System SKU. On Linux, run
cat /sys/class/dmi/id/product_name cat /sys/class/dmi/id/product_sku
A full number like 83ED0049US or 14-fe0013dx finds its series.
Show only | Show only | Show only | Show only | Show only | Show only | Show only | Show only | |
|---|---|---|---|---|---|---|---|---|
| Huawei | Snapdragon 8cx Gen 3 · 2022 · SC8280XP · GK-W7X | Needs firmware | Collected | Stable | Stable | From Windows | Ready to test | Linux community |
| Lenovo | Snapdragon 8cx Gen 3 · 2022 · SC8280XP · 21BX, 21BY | On stable | Collected | Stable | Stable | Stable | Ready to test | Linux community |
| Microsoft | Snapdragon 8cx Gen 3 · 2022 · Microsoft SQ3 · 1996, 1997 | Needs firmware | Collected | Stable | Stable | From Windows | Ready to test | Linux community |
| Microsoft | Snapdragon 8cx Gen 3 · 2022 · SC8280XP · 2043 | Needs firmware | Collected | Stable | Stable | From Windows | Ready to test | Linux community |
Googlebooks with Snapdragon 2
ShowHideBoots 1Not yet 11 of 2 boot to the desktop
Googlebooks with Snapdragon 2
ShowHideThey use the same Snapdragon X Elite as the laptops above, but start like a Pixel, through Android's bootloader instead of UEFI. So they need no ACPI tables or hardware IDs, and Omarchy's ARM image doesn't start on them; they need a device tree and a Linux image built for that bootloader.
To help, read the device tree Googlebook OS starts with, following the owner guide. It changes nothing on the laptop.
What the labels meandoneon its waymissinganother way or not neededShowHide
Bootloader
Whether its Android-style bootloader lets owners start another system.
- Unlockable
- Google lets owners unlock the bootloader to try another system. Unlocking wipes the laptop.
- Locked
- The bootloader only starts the system it shipped with.
Device tree
The description of the hardware that Linux needs, the same work as for the other Snapdragon laptops.
- Linux 6.x
- In Linux since that release.
- linux-next
- Accepted, and coming in the next Linux release.
- Kernel patch
- Sent to the Linux kernel mailing list as a patch, not accepted yet.
- Out of tree
- One exists outside Linux, in Omarchy's kernel, Ubuntu's kernel or a community repository, but it hasn't been sent there yet.
- Wanted
- Doesn't exist yet.
Linux image
Whether a Linux image starts on it, the step before Omarchy can.
- Starts
- A Linux image starts on it.
- None yet
- Nobody has built a Linux image that starts on it yet.
Boots
Has an owner reached the desktop on it? Tested on Omarchy so far.
- Boots
- An owner booted into Omarchy on it. Not every feature has to work yet.
- Problems
- An owner tried it and couldn't get to the Omarchy desktop.
- Not tested
- A Linux image starts on it, but nobody has tried Omarchy on it yet.
- Not yet
- Nothing starts on it yet. It needs a device tree and a Linux image for its Android-style bootloader.
Where's my model number?
It's on the sticker underneath. In Windows, open System Information and look at System Model and System SKU. On Linux, run
cat /sys/class/dmi/id/product_name cat /sys/class/dmi/id/product_sku
A full number like 83ED0049US or 14-fe0013dx finds its series.
Show only | Show only | Show only | Show only | Show only | Show only |
|---|---|---|---|---|---|
| Dell | Snapdragon X · 2026 · X1E-80-100 · DX13267, P212G Its Android device name is mica. The community tree is adapted from the HP Googlebook 14's, with the Dell wiring taken from the stock tree in Google's recovery image. It leaves the internal drive off, so it only runs from USB for now. Owner guide | Unlockable | Out of tree | Starts | Boots |
| HP | Snapdragon X · 2026 · X1E-80-100 · 14c-cf0xxx A community tree runs mainline Linux from the second boot slot and leaves Googlebook OS on the first. Nearly everything works, with kernel patches for the keyboard, the audio DSP and suspend. The internal mics click now and then, and battery time estimates come out about 8 times too short. Owner guide | Unlockable | Out of tree | Starts | Not tested |
NVIDIA N1x and GB10 17
ShowHideBoots 2Ready to test 7Not tested 82 of 17 boot to the desktop
NVIDIA N1x and GB10 17
ShowHideNVIDIA's ARM laptops and desktops start through ACPI, so they need no device tree or hardware IDs. What counts here is whether someone has booted into Omarchy on them.
To help, install Omarchy's ARM image or another distro and report whether it boots, through Add your model.
What the labels meandoneon its waymissinganother way or not neededShowHide
Linux
Whether plain Linux runs it, or it needs patches Linux doesn't have yet.
- Not in Linux yet
- Needs patches Linux doesn't have yet. Omarchy's kernel carries them.
- Mainline
- Plain Linux supports it.
Boots
Has someone reached the desktop on it? Tested on Omarchy so far, and reports from any distro are welcome.
- Boots
- Someone booted into Omarchy on it. Not every feature has to work yet.
- Ready to test
- Same platform as a model that boots, but nobody has tried this one yet.
- Problems
- Someone tried it and couldn't get to the Omarchy desktop.
- Not tested
- Nobody has tried Omarchy on it yet.
Where's my model number?
It's on the sticker underneath. In Windows, open System Information and look at System Model and System SKU. On Linux, run
cat /sys/class/dmi/id/product_name cat /sys/class/dmi/id/product_sku
A full number like 83ED0049US or 14-fe0013dx finds its series.
Show only | Show only | Show only | Show only | |
|---|---|---|---|---|
| Acer | NVIDIA GB10 · 2025 | Not in Linux yet | Ready to test | Same GB10 platform as the DGX Spark. |
| ASUS | NVIDIA GB10 · 2025 | Not in Linux yet | Ready to test | Same GB10 platform as the DGX Spark. |
| Dell | NVIDIA GB10 · 2025 | Not in Linux yet | Ready to test | Same GB10 platform as the DGX Spark. |
| Gigabyte | NVIDIA GB10 · 2025 | Not in Linux yet | Ready to test | Same GB10 platform as the DGX Spark. |
| HP | NVIDIA GB10 · 2025 | Not in Linux yet | Ready to test | Same GB10 platform as the DGX Spark. |
| Lenovo | NVIDIA GB10 · 2025 | Not in Linux yet | Ready to test | Same GB10 platform as the DGX Spark. |
| MSI | NVIDIA GB10 · 2025 | Not in Linux yet | Ready to test | Same GB10 platform as the DGX Spark. |
| NVIDIA | NVIDIA GB10 · 2025 | Not in Linux yet | Boots | Sleep is off on every GB10 for now. |
| ASUS | NVIDIA N1x · 2026 | Not in Linux yet | Boots | Boots through ACPI with Omarchy's kernel. |
| ASUS | NVIDIA N1x · 2026 | Not in Linux yet | Not tested | |
| Dell | XPS 16 Creator EditionAnnounced NVIDIA N1x · 2026 | Not in Linux yet | Not tested | |
| HP | NVIDIA N1x · 2026 | Not in Linux yet | Not tested | |
| HP | NVIDIA N1x · 2026 | Not in Linux yet | Not tested | |
| Lenovo | Yoga Pro 9nAnnounced NVIDIA N1x · 2026 | Not in Linux yet | Not tested | |
| Microsoft | NVIDIA N1x · 2026 | Not in Linux yet | Not tested | |
| Microsoft | Surface RTX Spark Dev BoxAnnounced NVIDIA N1x · 2026 | Not in Linux yet | Not tested | |
| MSI | Prestige N16 Flip AI+Announced NVIDIA N1x · 2026 | Not in Linux yet | Not tested |
Apple Silicon Macs run Linux through Asahi Linux, which Omarchy builds on. Asahi's feature support pages track which models and features work.
What a model needs
ARM laptops don't describe their hardware to Linux the way PCs do, so each model needs a device tree, written from its ACPI tables. Its hardware IDs in systemd let a boot image pick that device tree by itself, and its firmware files for the DSPs, GPU and Wi-Fi have to come from linux-firmware, from Windows, or from the maker's own download.
Where the data comes from
Collected 2026-11-03 from Linux and linux-next 20261103, systemd's hardware IDs, linux-firmware, aarch64-laptops, owners' hardware reports and Omarchy's packages.