Are we ARM yet?
Docs menu

Help with your laptop

Every Snapdragon laptop needs a device tree that describes its hardware to Linux, its hardware IDs so a boot image picks that tree by itself, and its firmware. Writing a device tree takes a developer, but it's written from what's on your laptop, and it's finished by someone testing it on the real hardware.

If your laptop is marked Wanted on the board, says Should boot under Bootable, which nobody has confirmed yet, or isn't on it at all, pick the case that fits. Each takes a few minutes.

Your laptop still has Windows#

The Omarchy Arm Installer reads the laptop from its own Windows and writes a hardware report with the ACPI and SMBIOS tables Windows uses to describe the hardware, its hardware IDs, every device with its driver and resources, and a list of the firmware files in its drivers. A device tree is written from exactly that. Serial numbers and other personal details are taken out, and no firmware files go into the report.

  1. Download OmarchyArmInstaller.exe from the installer's latest release. It's a pre-release, so expect rough edges.
  2. Right-click it and choose Run as administrator, which it needs to read the firmware tables.
  3. Choose Share a hardware report. If Linux doesn't know the laptop yet, the installer offers it by itself.
  4. Choose Collect the report. The zip lands in Downloads, next to a list of what was taken out of it. Unless you clear the box above the button, the installer then sends the firmware files in the laptop's drivers to this site's private store. They are used to ask the maker to put them in linux-firmware, and are never published.
  5. Choose Open the form. The model and its hardware IDs are filled in already. Drag the zip in, add a link to the vendor's driver page if you know it, and submit. Reports are public in omarchy-hardware-reports.

If you can test boot images on the laptop later, say so in the report. An owner who can test is what gets a device tree finished.

You already run Linux on it#

If Linux boots on it, with another model's device tree or one you patched, the tree it boots with is the best start for its own. The kernel keeps a copy of it you can save.

  1. Install the device tree compiler and fwupd.
    sudo pacman -S dtc fwupd                     # Arch, Omarchy
    sudo apt install device-tree-compiler fwupd  # Debian, Ubuntu
    sudo dnf install dtc fwupd                   # Fedora
  2. Save the device tree the laptop booted with, without its serial number. Warnings from dtc are normal.
    dtc -I fs -O dts /sys/firmware/devicetree/base > tree.dts
    sed -i '/serial-number/d' tree.dts
  3. Save its hardware IDs.
    sudo fwupdtool hwids > hwids.txt
  4. Open Add your model, drag in both files, and say which device tree you started from and what you changed. A patch or a link to your branch is even better.

It's ready to test#

A model that says Should boot under Bootable has its device tree and hardware IDs in Omarchy, so the install image picks the tree by itself. Nobody has confirmed it on the real hardware yet.

  1. Make an Omarchy USB stick. With Windows still on the laptop, the Omarchy Arm Installer makes one and copies the laptop's firmware onto it from Windows' own drivers. Install Omarchy has every step.
  2. Turn off Secure Boot, boot from the stick, and install, or just see how far it gets.
  3. If it reached the desktop, run the hardware test. It measures what works and puts it on the model's page, so there's nothing to write up.
  4. If it didn't get that far, open Add your model and choose how far it got. If you run another distro on it, tell us how that does too.

Check what works once it boots#

On Omarchy, install the hardware test once and run it. It tests the screen, keyboard, sound, camera, Wi-Fi, sleep and the rest, some of it by itself and some of it with you, and puts the results on your model's page.

omarchy-mise-install github:birkskyum/arewearmyet hw-test
hw-test

The hardware test says what it tests, what it sends, and how to hand a part that doesn't work to your AI agent.

Please don't send#

  • Serial numbers, or the MSDM ACPI table, which holds the Windows product key. The installer leaves both out.

What happens next#

Reports and device trees go to the people writing trees for these laptops. The board shows each step as it lands, from a tree out of tree to one posted to the kernel list and then in a Linux release. When there's something to try on your laptop, we'll ask in your issue.

Add your model · Back to the board