Skip to content

Add omarchy-hw-match-device-tree for models that share a DMI name - #15064

Merged
birkskyum merged 4 commits into
omacom:n1xfrom
birkskyum:hw-dt-match
Oct 11, 2026
Merged

birkskyum merged 4 commits into
omacom:n1xfrom
birkskyum:hw-dt-match

Conversation

@birkskyum

@birkskyum birkskyum commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

A helper for telling apart laptop models that report the same DMI name, by the top-level compatible strings of the device tree. omarchy-hw-match cannot do that, so the Surface Pro 11 script in #14390 and the Zenbook A16 script in #13820 each read the device tree themselves, which n1x asks feature code not to do.

omarchy-hw-match-device-tree <compatibles...> is true when one of the strings is an entry of that list. It compares whole strings and ignores case, as the kernel does. It takes several strings, since the Zenbook goes by two names.

It reads the same fixture roots as omarchy-hw-platform, so a test can fake a device tree without each script carrying a path override of its own. As root it reads only the live one.

With it the two checks become

omarchy-hw-aarch64-qualcomm && omarchy-hw-match-device-tree microsoft,denali-oled
omarchy-hw-match-device-tree asus,zenbook-a16-ux3607oa asus,ux3607oa

Tested

  • The new test, the CLI metadata test and the platform and Snapdragon tests pass in an Arch Linux ARM container.
  • On a Yoga Slim 7x it matches lenovo,yoga-slim7x and qcom,x1e80100, in any case, and none of the partial or foreign strings we tried. As root it ignores a fixture root in its environment and still answers for the real board.

The Surface Pro 11 models report one DMI name and differ in the device tree's compatible strings, so omarchy-hw-match cannot tell them apart. This helper matches a whole compatible string, ignoring case as the kernel does, and takes several strings for a model that goes by more than one.
@greptile-apps

greptile-apps Bot commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 5/5

[Medium impact] The PR appears safe to merge; no blocking issues remain.

Summary

Adds omarchy-hw-match-device-tree to tell apart models that share a DMI name.

  • Feature checks can now tell apart models that share a DMI name.

No new issues found. Both earlier findings are addressed: sysfs fallback is present, and LC_ALL=C prevents locale-dependent case matching.

Reviews (3) · Last reviewed commit: "Rename omarchy-hw-dt-match to omarchy-hw..." · Reviewed by Greptile

Comment thread bin/omarchy-hw-dt-match Resolved
Comment thread bin/omarchy-hw-match-device-tree Resolved
A root without /proc/device-tree but with /sys/firmware/devicetree/base went unmatched, and naming both fixture roots ignored sysfs. Read the first of the two that is there, as omarchy-hw-platform reads both.
Bash folds case by the session's locale. In a Turkish one I becomes a dotless i, so MICROSOFT,DENALI-OLED no longer matched microsoft,denali-oled.
Spelled out, so the name needs no decoding, and starting with omarchy-hw-match, so the two list side by side as omarchy hw match and omarchy hw match device tree.
@birkskyum birkskyum changed the title Add omarchy-hw-dt-match for models that share a DMI name Add omarchy-hw-match-device-tree for models that share a DMI name Oct 11, 2026
@birkskyum
birkskyum merged commit fc79fff into omacom:n1x Oct 11, 2026
1 check passed
turbineBMW added a commit to turbineBMW/omarchy that referenced this pull request Oct 11, 2026
The OLED, LCD and X Plus models share a DMI name, so the script read the
device tree itself. omarchy-hw-match-device-tree (omacom#15064) does that for any
such model, and the test fakes the tree through OMARCHY_PROC_ROOT like the
other platform tests, skipping as root where fixtures are ignored.

Validated with test/shell.d/surface-pro-11-hardware-test.sh,
hw-match-device-tree-test.sh, snapdragon-hardware-test.sh and
surface-hardware-test.sh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
birkskyum added a commit to turbineBMW/omarchy that referenced this pull request Oct 11, 2026
omarchy-hw-dt-match became omarchy-hw-match-device-tree before omacom#15064 went in, so the old name is not on n1x and the model check was always false.
ryanrhughes pushed a commit that referenced this pull request Oct 12, 2026
…5064)

* Add omarchy-hw-dt-match for models that share a DMI name

The Surface Pro 11 models report one DMI name and differ in the device tree's compatible strings, so omarchy-hw-match cannot tell them apart. This helper matches a whole compatible string, ignoring case as the kernel does, and takes several strings for a model that goes by more than one.

* Fall back to the sysfs device tree in omarchy-hw-dt-match

A root without /proc/device-tree but with /sys/firmware/devicetree/base went unmatched, and naming both fixture roots ignored sysfs. Read the first of the two that is there, as omarchy-hw-platform reads both.

* Compare compatible strings in the C locale in omarchy-hw-dt-match

Bash folds case by the session's locale. In a Turkish one I becomes a dotless i, so MICROSOFT,DENALI-OLED no longer matched microsoft,denali-oled.

* Rename omarchy-hw-dt-match to omarchy-hw-match-device-tree

Spelled out, so the name needs no decoding, and starting with omarchy-hw-match, so the two list side by side as omarchy hw match and omarchy hw match device tree.
birkskyum pushed a commit to turbineBMW/omarchy that referenced this pull request Oct 12, 2026
The OLED, LCD and X Plus models share a DMI name, so the script read the
device tree itself. omarchy-hw-match-device-tree (omacom#15064) does that for any
such model, and the test fakes the tree through OMARCHY_PROC_ROOT like the
other platform tests, skipping as root where fixtures are ignored.

Validated with test/shell.d/surface-pro-11-hardware-test.sh,
hw-match-device-tree-test.sh, snapdragon-hardware-test.sh and
surface-hardware-test.sh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
birkskyum added a commit to turbineBMW/omarchy that referenced this pull request Oct 12, 2026
omarchy-hw-dt-match became omarchy-hw-match-device-tree before omacom#15064 went in, so the old name is not on n1x and the model check was always false.
@ryanrhughes ryanrhughes mentioned this pull request Oct 15, 2026
4 tasks done
ryanrhughes added a commit that referenced this pull request Oct 15, 2026
* Add NVIDIA N1x (aarch64) platform support to the runtime

Port of the N1x bring-up onto quattro. Everything is gated on the new
omarchy-hw-n1x detector (ACPI NVDA0200 MediaTek I2C controllers or the
10de:2e06 GB20B GPU, aarch64 only), so x86_64 behaviour is unchanged.

- install/hardware/n1x.sh (runs before nvidia.sh): ensures linux-n1x and
  headers, drops the stock kernel, pins console=tty0 acpi=nospcr and a
  verbose boot through an alphabetically-first Limine drop-in (the entry
  tool prepends += fragments, so that drop-in's fragment lands last and
  wins over omarchy-defaults.conf's quiet loglevel=0), adds a
  linux-n1x-rescue entry with its own KERNEL_CMDLINE key and UKI (Limine
  hands the entry cmdline to systemd-stub as load options, overriding the
  embedded one), keeps the NVIDIA stack unloaded with blacklist plus
  install-to-/bin/false lines because 610.57.04 cannot boot this GPU's GSP
  and its dead render node aborts Hyprland, and sets up key-only SSH for
  the install user plus a per-boot hardware probe.
- install/hardware/nvidia.sh defers to n1x.sh on this platform instead of
  configuring early KMS.
- etc/mkinitcpio.conf.d/omarchy_hooks.conf drops plymouth (crashes in the
  AArch64 initramfs) and microcode on aarch64 and adds the I2C-HID input
  modules the internal keyboard and touchpad need before root is mounted.
- Arch Linux ARM pacman config for installed aarch64 systems; the bundled
  Node.js tarball lookup follows the machine architecture.
- test/shell.d/hw-n1x-test.sh covers the detector and the script contract.

* Drive the N1x panel from the GPU on firmware 1.0 and later

BIOS 1.0.4 lets the 610.57.04 open driver boot the GPU's GSP, so the
NVIDIA blacklist is now limited to pre-release 0.x firmware. On 1.0+ the
script installs the driver, enables nvidia_drm modeset with fbdev, loads
the modules in the initramfs for early KMS, and blacklists the firmware
framebuffer driver on the kernel command line, as NVIDIA does on the
Spark, so Hyprland sees a single DRM device. Verified on the dev unit:
eDP-1 at 1920x1200@120 after an unattended reboot.

* Keep N1x bootable when the NVIDIA DKMS build fails, and track Omarchy's aarch64 repo

- hardware/n1x.sh only enables early KMS when DKMS produced nvidia_drm for the
  N1x kernel; otherwise the NVIDIA stack stays unloaded and Hyprland renders on
  the firmware framebuffer instead of every UKI build failing.
- Remote access moves out of the runtime: the N1x development ISO owns its
  own, separately removable SSH setup.
- Installed aarch64 systems gain pkgs.omarchy.org's edge aarch64 repository,
  ahead of Arch Linux ARM, and omarchy-refresh-pacman no longer copies an
  x86_64 channel config onto them.

* Check every early-loaded NVIDIA module, and report sshd state from the N1x probe

The DKMS check now requires all four modules the initramfs lists, not just
nvidia_drm. The probe reported a recovery key by name on every boot whether or
not sshd was set up; it now prints what systemd says about sshd.

* Name the N1x rescue entry for what it is

It is a text console with the GPU off; SSH comes only from a --dev-ssh image.

* Make the ASUS ProArt P14 (N1x) touchpad register touches

Its PixArt haptic pad reports force on a 0-65535 pressure axis, so
libinput's default touch threshold is never reached. Mark it a pressure
pad in /etc/libinput/local-overrides.quirks, the only file libinput reads
from /etc, and add a migration for existing installs.

* Route ASUS ProArt P14 (N1x) speakers, headphones and microphones

The MediaTek MT8901 SoundWire card (cs42l43 + 2x cs35l56) exposes only
front-end PCMs; without a UCM profile nothing routes them to the codecs
and PipeWire offers a dummy output. Add a profile for this model that
sets the AFE interconnect and reuses alsa-ucm-conf's cs42l43/cs35l56
controls. It lives under its own Omarchy UCM directory, selected through
a conf.d link for the card's long name, for omarchy-settings to install
under /usr/share/alsa/ucm2. A migration restarts PipeWire to pick it up.

* List Omarchy's aarch64 repository first on existing N1x installs

pacman-aarch64.conf puts [omarchy] ahead of Arch Linux ARM so Omarchy's
builds, the NVIDIA driver among them, win. Installs from earlier N1x
images list it last. Move the section in place, leaving the rest of the
file as it is.

* Boot N1x laptops quietly so Plymouth stays up through unlock and shutdown

The N1x console drop-in added loglevel=7, systemd.show_status=1 and
friends for bring-up, after Omarchy's quiet splash so they would win.
Kernel and systemd messages then printed over Plymouth once the disk
was unlocked and again during shutdown. Keep only console=tty0 and
acpi=nospcr on the normal entry; the rescue entry stays verbose.

* Light the N1x panel for Plymouth's LUKS prompt

The panel stays at its dim power-on backlight until the NVIDIA backlight
is first written: its DPCD brightness registers read zero while nvidia_0
reports 100. systemd-backlight is the first to write it, after the disk
is unlocked, so the LUKS prompt was nearly black. An initramfs hook right
after plymouth sets 60%; the saved level still returns after unlock.

* Give the ASUS ProArt P14 the RAM its firmware reserves for Windows' GPU

The 128 GB ProArt P14's firmware reserves 62.5 GiB as the N1x GPU's
dedicated memory under Windows. Linux's NVIDIA driver runs the GPU from
system memory, so the reservation sits idle and the laptop boots with
61 GiB, and the BIOS has no setting to shrink it.

linux-omarchy-n1x's efi_reclaim_reserved= hands the idle 61.9 GiB to
the kernel, leaving reserved the firmware's DRAM training buffer and
the top 512 MiB, where the GPU's firmware runs. Only add it when the
firmware still reserves exactly the block it was measured on.

* Add a speaker tuning for the ASUS ProArt P14 (N1x)

On Windows, ASUS's Dolby Atmos layer voices this laptop's speakers on
top of the Cirrus amplifier tuning; on Linux they sounded muffled. Start
from the static speaker voicing in ASUS's Dolby tuning for this model
(its 600 Hz speaker PEQ and 20-band optimizer curve, fitted to 0.06 dB),
then voice the low mids by ear in place of Dolby's adaptive dialog
enhancement: a 300 Hz mud cut, a softer 600 Hz bump and a broad 2.5 kHz
vocal lift. Above 4 kHz it is Dolby's curve.

It applies only once the amplifiers have ASUS's tuning for this laptop,
which the curve assumes.

* Install ASUS's speaker amplifier tuning on the ProArt P14 (N1x)

The amplifiers ran their ROM defaults, quiet and unvoiced, without
ASUS's tuning for this laptop. Install asus-proart-p14-speaker-firmware
on the H7407BA, ahead of the speaker tuning that builds on it, and add
both to existing installs.

* Let omarchy-pkg-drop run as root like omarchy-pkg-add

* Ship N1x laptops on linux-omarchy-n1x without the bring-up scaffolding

- Install linux-omarchy-n1x, which carries the N1x platform, USB4 and ASUS
  ProArt P14 patches, and drop the stock and linux-n1x kernels.
- Let limine-mkinitcpio-hook build the rescue entry as the kernel's fallback
  UKI, so it follows kernel updates, instead of a one-off copied UKI.
- Keep Plymouth in the initramfs on aarch64 again; only the N1x gets the
  I2C keyboard modules for the LUKS prompt.
- Suspend to idle, as the firmware's deep sleep returns at once.
- Keep the USB4 host routers powered and leave PCI room for docks on the
  ProArt P14, where USB4 is validated.
- Hold the GPU stack back only on Dell's pre-release firmware; the version
  sort let ASUS firmware through by accident.
- Run omarchy-n1x-probe on demand instead of on every boot.

* Move existing N1x installs to linux-omarchy-n1x

Installs the kernel, writes the same keyboard, sleep, USB4 and rescue-entry
drop-ins as a fresh install, removes the one-off rescue UKI and the
every-boot probe, and drops linux-n1x once the machine no longer runs it.
The boot order only changes once DKMS has built the NVIDIA modules for the
new kernel.

* Leave the N1x console setting to the ISO installer

The installer now gives every aarch64 install console=tty0 acpi=nospcr,
the setting the N1x's serial console table needs, so n1x.sh no longer
writes its own copy of it.

* Keep Arch Linux ARM's signing key trusted on aarch64

Arch Linux ARM signs every package in its repositories, archlinux-keyring
included, with its build key 68B3537F39A313B3E574D06777193F152BDBE6A6, and
only archlinuxarm-keyring carries it. pacman's "Import PGP key?" prompt adds
the key without trusting it, after which every update stopped at "unknown
trust" with nothing to repair it.

Before the keyring refresh, an aarch64 machine whose key is not valid
populates it from the installed archlinuxarm-keyring, or fetches it by
fingerprint, signs it locally and installs the package when that is missing,
the way the Omarchy key is bootstrapped. keys.openpgp.org does not carry it,
so it comes from keyserver.ubuntu.com. After the refresh, a key that is still
untrusted fails the update instead of reporting the keys correct.

* Keep the N1x USB4 tunnel root ports awake so docks' PCIe devices appear

The ProArt P14's USB4 tunnel root ports (10de:22cf) cannot signal a hotplug
while runtime-suspended, in D3hot or D3cold alike. They suspend about 100 ms
after going idle, so by the time a dock is plugged in and bolt authorizes it,
the PCIe tunnel comes up behind a sleeping port and nothing is enumerated: the
dock shows as authorized, its USB and display work, and its Ethernet never
appears until something happens to read the port's config space. On a fresh
install from the n1x ISO, two of three physical replugs of a CalDigit TS4
left it without its NIC, one of them for 97 minutes. Holding the ports in D0
brought the NIC up 16 ms after authorization on every try, and a deauthorize
and authorize cycle went from no NIC after 30 s to the NIC in 1 s.

Keep the three ports in D0 with a udev rule, written alongside the USB4
command line on the ProArt, and add it to existing ProArt installs with a
migration that also applies it to the running system. linux-omarchy-n1x
should eventually resume the root port when it activates a PCIe tunnel
instead; this costs the idle power of three root ports until then.

* Answer ARP only for each interface's own address

With the kernel's default ARP behaviour every interface answers for every
local address. Plug a dock's Ethernet into the same network the laptop's
Wi-Fi is on, and the Wi-Fi answers NetworkManager's address-conflict probe
for the new wired address: the probe reaches the Wi-Fi a few hundred
milliseconds late over the air, after the address is already up. NetworkManager
then sees "conflict detected ... with host <the laptop's own Wi-Fi MAC>" and
withdraws the wired routes while still reporting the connection as connected,
so all traffic quietly stays on Wi-Fi. It is a race, so it only happens on
some activations. LAN hosts also learn the Wi-Fi address on the wired MAC
and the other way round. A fresh N1x install docked to a CalDigit TS4 lost
its wired routes on two of its first three activations this way.

Set arp_ignore=1 and arp_announce=2 for all and default interfaces: answer
only for the interface's own address and announce from it. With that, the
late probes still reach the Wi-Fi but go unanswered, and three further
activations and a replug saw no conflict. The settings go in their own file
because an older source's aarch64 omarchy-settings-dev replaces
99-omarchy-sysctl.conf with a single line. A migration applies them to the
running system.

* Start the N1x rescue entry with initramfs_async=0

The rescue entry carries its own command line and missed the
initramfs_async=0 every other entry gets.

[Ryan: cherry-picked from 3b93764 onto n1x. Its other half, removing only
the stray kernels that are installed, is already how n1x removes them
(omarchy-pkg-drop skips what isn't installed). The migration that moves
existing N1x installs writes the same rescue line, so it gets the flag too.]

* Route the Dell XPS 16 N1x speakers, headphones and microphones through a UCM profile

* Stop systemd 262's NvPCR setup from failing three units on every boot

* Give the Dell XPS 16 N1x the RAM its firmware reserves for Windows' GPU, as on the ProArt P14

* Give the N1x swap on zram, the memory tuning and realtime audio scheduling

omarchy-settings ships the x86_64 memory stack on aarch64 now (swap on zram,
zswap off, the reclaim sysctls, systemd-oomd's slice policy), but installs
from the earlier N1x images ran with no swap at all. They also lacked rtkit,
which nothing pulls in on aarch64, so PipeWire got no realtime scheduling.

rtkit joins the aarch64 package list, and a migration gives existing N1x
installs rtkit and zram-generator and starts the zram swap without a reboot.

* Turn on USB4 and Thunderbolt on the N1x: keep the USB4 resources powered and set aside bus numbers for docks

[Ryan: cherry-picked onto n1x, which already sets the ASUS ProArt P14 up with
the larger windows and root-port rule validated on it (Spencer: "take
yours"). This setting becomes the one for every other N1x, the XPS 16 among
them, and its migration leaves the ProArt to 1791077437.]

* Keep the N1x GPU firmware's room below its memory out of the reclaimed RAM, since a large external display reaches into it

* Drop the N1x rescue hook and entry that the fallback entry replaces

The n1x-xps16 branch built the N1x rescue entry as its own UKI and rebuilt it
from a pacman hook running omarchy-refresh-n1x-rescue. On n1x the
limine-mkinitcpio-hook fallback entry does that job and the command does not
exist, so an install that ran that branch would fail the hook on every kernel
update and keep a rescue entry for an old kernel. Remove both there.

* Skip lib32 graphics drivers on aarch64, where Steam runs its native arm64 client and multilib does not exist

omarchy-install-gaming-gpu-lib32 asked for lib32-nvidia-utils on the N1x, which no aarch64 repository has, so omarchy-install-gaming-steam (and the Heroic, Lutris and Battle.net installers) stopped before installing anything. omarchy-pkgs now builds steam for aarch64 on Valve's native arm64 client (omacom/omarchy-pkgs#842), which needs no lib32 drivers, so the same installer works on both architectures.

* Boot the ASUS ProArt P14 keyboard with media keys on the top row, as the laptop ships, and keep F1-F12 on Fn+Esc

* Give Snapdragon and the NVIDIA N1x platform names of their own

Both families need code of their own: Snapdragon its linux-firmware-qcom,
the N1x its own kernel and NVIDIA stack. Both were plain aarch64 to
omarchy-hw-platform, so omarchy-pkg-defaults left those packages out, and an
image build, which defers hardware setup to first boot and may be offline
then, had nothing to install them from.

omarchy-hw-platform now prints aarch64-qualcomm for a "qcom," device tree
and aarch64-n1x for an ACPI machine with the N1x's MediaTek I2C controllers
(NVDA0200) or its GPU (PCI 10de:2e06), and refuses an N1x signature
alongside an Apple or Qualcomm device tree. Image manifests accept both
names, and an older builder's "qualcomm" reads as aarch64-qualcomm. Each
family adds install/omarchy-aarch64-<family>.packages to its default set,
shares the aarch64 pacman templates and the edge channel, and registers no
lifecycle package. omarchy-hw-aarch64-qualcomm and omarchy-hw-aarch64-n1x
are the family predicates; omarchy-hw-n1x stays as a hidden alias for older
N1x images. A single model's quirks (the ProArt P14's, the XPS 16's) stay
behind omarchy-hw-match on its DMI name.

* Install Gliff on aarch64 too, now that Omarchy's edge repository builds it there

* Restore Snapdragon X and Yoga Slim 7x support on n1x (#14834)

* Add Snapdragon X and Yoga Slim 7x support to n1x (#14759)

* Carry the Windows-on-ARM device trees in every UKI on Qualcomm SoCs

Snapdragon laptops boot with the device tree for their exact model and the
firmware provides none. The live ISO already boots them with a systemd-stub
UKI that carries every candidate tree as .dtbauto sections and picks one by
SMBIOS hardware id; the installed system built its UKIs with no tree at all,
so the first reboot after the install had nothing to boot.

Add the omarchy-hw-qualcomm-soc probe (root device-tree compatible starts
with qcom,) and a hardware leaf that lists the trees in /etc/kernel/uki.conf,
which mkinitcpio hands to ukify for every UKI limine-mkinitcpio-hook builds.
The list is a snapshot of /boot/dtbs/qcom taken when the leaf runs; the file
header says so, and the enumeration retires when ukify accepts globs.

* Kernel parameters Snapdragon laptops need under Windows-on-ARM firmware

The same set Fedora's Snapdragon images and the live ISO carry, as a
limine-entry-tool drop-in so limine-update folds it into every entry, with
each parameter's reason and retirement condition in the file.

* Install the Adreno Vulkan driver on Qualcomm SoCs

Adreno GPUs are platform devices, so the lspci vendor scan in vulkan.sh
never sees them; ask the SoC probe instead.

* Qualcomm firmware package, and blacklist the audio DSP until its blobs exist

Arch Linux ARM keeps the redistributable Qualcomm blobs in
linux-firmware-qcom; the installed system had none of them. The vendor-signed
DSP firmware comes later from the owner's Windows partition; until it is
there the DSP driver's failing probe resets the USB-C mux, which drops a
USB-C root disk and hangs the boot (seen on the HP EliteBook Ultra G1q).

* Copy the vendor-signed Qualcomm firmware from Windows during install

install/hardware/qualcomm/firmware.sh installs qcom-firmware-extract next to
linux-firmware-qcom and runs it in the target: the files the device tree
names (GPU zap shader, audio and compute DSP images) are taken from the stage
the ISO saved before the disk was written, or from a Windows partition still
on disk, into /usr/lib/firmware/updates. The audio-DSP blacklist now follows
what is actually missing (qcom-firmware-extract --list-missing) instead of a
path glob, so it clears itself once the firmware is present.

install/omarchy-other.packages lists qcom-firmware-extract (arch=any) so the
offline mirror carries it.

* Keep the Qualcomm DSPs off when the root disk is on USB

With real DSP firmware the Type-C port controller takes over the ports once
the ADSP is up and resets them, which drops a root disk behind a USB-C port
(G1q, external NVMe: cdsp up at 10.8 s, I/O errors and a read-only root at
22 s). Installs whose root disk reports TRAN=usb keep qcom_q6v5_pas
blacklisted (no audio or battery reporting) until the kernel stops resetting
connected ports; internal-disk installs are unchanged.

* Address Snapdragon setup review feedback

* Trim Snapdragon implementation comments

* Keep missing Qualcomm firmware from aborting setup

* Preserve safe Snapdragon setup on failed firmware inspection

* Syntax-check each Snapdragon setup script

* Add Lenovo Yoga Slim 7x board support (#8673)

* Add Yoga Slim 7x board support

* Trim Yoga board setup comments

* Skip Yoga DSP startup when disabled

* Initialize Yoga display before disk unlock

* Include compressed and extracted Yoga display firmware

* Use the laptop console for Yoga disk unlock

* Reuse board-matched zap firmware and exercise Yoga failure paths

* List every package Snapdragon setup installs for the ISO mirror

* Say how to rebuild the UKI and why firmware is searched by suffix

---------

Co-authored-by: Jimmy Van Veen <jimmy.van.veen@gmail.com>

* Move Snapdragon setup onto the aarch64-qualcomm platform

n1x now names Snapdragon laptops aarch64-qualcomm and gives them a package
list of their own. The setup leaves ask omarchy-hw-aarch64-qualcomm, so the
separate device tree probe goes, and the packages they install sit in
install/omarchy-aarch64-qualcomm.packages instead of omarchy-other.packages,
so only Snapdragon images carry them.

The Yoga Slim 7x is matched by its DMI product name (83ED) through
omarchy-hw-match, like every other single model, instead of by its device
tree.

* Ask an image's first boot to rebuild when the device tree list changes

The UKI carries the device trees only once it is rebuilt. An image's first
boot rebuilds after its last step when a step changed the files it watches,
and /etc/kernel/uki.conf is not one of them, so the device tree step now asks
for the rebuild through OMARCHY_IMAGE_BOOT_REBUILD. An unchanged list is left
alone and asks for nothing.

An install from the ISO needs nothing here: the installer's final
limine-update builds the UKIs after hardware setup.

* Keep trying for the Yoga's compute DSP after the audio DSP is up

The starter stopped at the first pass in which the audio DSP was running, so
a compute DSP that appeared later or failed its first start was never tried
again. Both are now tried until both are up or the attempts run out. The
audio DSP still decides the result, since battery, audio and USB-C hang off
it.

* Say beside the Snapdragon leaves who builds the boot image

They write boot settings and build nothing, like every hardware leaf. The
installer's final limine-update builds the UKIs after hardware setup, and an
image's first boot rebuilds once after its last step.

* Run the Snapdragon setup tests under the real platform detector

* Name n1x.sh as the leaf the Snapdragon ones follow on boot images

---------

Co-authored-by: Jimmy Van Veen <jimmy.van.veen@gmail.com>

* Install NVIDIA's 32-bit packages only on x86_64 (#10752)

The 32-bit libraries come from multilib, which only x86_64 has. On an aarch64
machine with an NVIDIA GPU, such as the DGX Spark, asking for
lib32-nvidia-utils stops the hardware setup and with it the installation. The
N1x does not reach this path; it has its own driver setup.

* Keep Intel Surface fixes off Snapdragon Surfaces (#14389)

* Keep Intel Surface fixes off Snapdragon Surfaces

omarchy-hw-surface matches any Microsoft Surface, so on a Surface Pro 11
(Snapdragon X Elite) the installer added Marvell Wi-Fi firmware and wrote an
initramfs module list naming Intel LPSS modules that do not exist on ARM.
Limit both fixes to x86_64 and leave the detector unchanged, so ARM Surface
setup can still use it.

Validated with test/shell.d/surface-hardware-test.sh, which fails on the
previous scripts, and the Snapdragon hardware test.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* Test that the Surface keyboard fix still runs on Intel Surfaces

The shell test only covered the keyboard fix on aarch64, so it would still pass if the guard skipped every architecture. Add an x86_64 case that checks the lsmod probe runs; the mock prints no module names, so nothing is written to /etc.

The keyboard script also reads the DMI product name from sysfs, which ARM machines and containers may not have, and under set -e that failed read would abort the test before the probe check. Mock that read as an Intel Surface so the test does not depend on the host's firmware tables.

Validated with test/shell.d/surface-hardware-test.sh, which now fails when the guard skips x86_64, and passes with cat shimmed to fail on /sys/class/dmi/id/product_name.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* Let the Surface keyboard test check the module list it writes

The keyboard script wrote its initramfs module list to a hard-coded /etc path, so the test could only check that lsmod ran and had to keep its lsmod mock silent to stay clear of the host. Read the directory from OMARCHY_SURFACE_MKINITCPIO_DIR with the same default, as the Yoga and Qualcomm scripts do, and point the test at a scratch directory.

The test now feeds the mock a pinctrl line and checks the exact MODULES list on x86_64, checks that an Intel Surface without a pinctrl module writes nothing, and checks that a Surface Pro 11's pinctrl_sm8550_lpass_lpi writes nothing on aarch64.

Validated with test/shell.d/surface-hardware-test.sh, which fails when the module list drops surface_kbd or when the path is hard-coded again, and with ./test/shell.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* Ask omarchy-hw-x86 in the Intel Surface checks

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: Birk Skyum <74932975+birkskyum@users.noreply.github.com>

* Give the NVIDIA GB10 a platform name of its own (#14895)

The GB10 desktops (the DGX Spark, the ASUS Ascent GX10) need packages of
their own: the NVIDIA driver, the container toolkit for GPU containers,
rdma-core for the ConnectX-7 network and NVIDIA's profilers, as DGX OS ships
them. They were plain aarch64 to omarchy-hw-platform, so no default set
carried those packages and an image had nothing to install them from.

omarchy-hw-platform now prints aarch64-gb10 for an ACPI machine with the
GB10's GPU (PCI 10de:2e12), and refuses it alongside an Apple or Qualcomm
device tree or the N1x's signatures. Image manifests accept the name. The
family adds install/omarchy-aarch64-gb10.packages to its default set, shares
the aarch64 pacman templates and the edge channel, and registers no
lifecycle package. omarchy-hw-aarch64-gb10 is its predicate.

* Disable system sleep on GB10 machines (#13260)

* Give the NVIDIA GB10 a platform name of its own

The GB10 desktops (the DGX Spark, the ASUS Ascent GX10) need packages of
their own: the NVIDIA driver, the container toolkit for GPU containers,
rdma-core for the ConnectX-7 network and NVIDIA's profilers, as DGX OS ships
them. They were plain aarch64 to omarchy-hw-platform, so no default set
carried those packages and an image had nothing to install them from.

omarchy-hw-platform now prints aarch64-gb10 for an ACPI machine with the
GB10's GPU (PCI 10de:2e12), and refuses it alongside an Apple or Qualcomm
device tree or the N1x's signatures. Image manifests accept the name. The
family adds install/omarchy-aarch64-gb10.packages to its default set, shares
the aarch64 pacman templates and the edge channel, and registers no
lifecycle package. omarchy-hw-aarch64-gb10 is its predicate.

* Disable system sleep on the DGX Spark, as DGX OS does

* Follow the DGX Spark sleep setting in the menu, suspend toggle and hibernation setup

* Check the DGX Spark sleep setting before hibernation support

* Turn sleep off on every GB10, under a general setting name

The ASUS Ascent GX10 and the other GB10 machines share the DGX Spark's chip
and DGX OS, so the setting follows the GB10 platform instead of the Spark's DMI
name. It moves to install/hardware/gb10/, and its drop-in is now
omarchy-sleep-disabled.conf, so another machine could reuse the menu, toggle
and hibernation checks.

* Give the working command that restores the GB10 sleep setting

omarchy apply hardware needs root and --install-user, so the manual's command
to put the drop-in back stopped before doing anything.

* Let a Snapdragon laptop boot a kernel that builds its platform drivers as modules (#14952)

Arch Linux ARM's kernel builds the X1 pin control, interconnect, PMIC and bus
drivers in, and translates device memory access by default. Omarchy's own
aarch64 kernel builds those drivers as modules and defaults to IOMMU
passthrough, so on it a Snapdragon laptop got an initramfs without them, and
on the Yoga Slim 7x the keyboard, touchpad and touchscreen read back empty
descriptors and never appeared.

The Snapdragon setup now names those drivers for the initramfs, each one
optional, and boots with iommu.passthrough=0. Neither changes anything on Arch
Linux ARM's kernel. The device tree list takes the trees of Omarchy's own
kernel first, where that kernel keeps them under its package name.

Tested on a Yoga Slim 7x running linux-omarchy-n1x 7.2.8.

* Boot the DGX Spark without a UKI until Limine is fixed (#13426)

* Boot the DGX Spark without a UKI until Limine stops returning all memory

* Preserve Spark Direct Boot and test failed boot rebuilds

* Rebuild a Spark whose Omarchy EFI entry is inactive

* Point out an inactive Omarchy EFI entry left without its UKI

* Name the command that removes an inactive Omarchy EFI entry

* Keep a Direct Boot Spark's UKI when hardware setup runs

* Verify the Spark boot setting before rebuilding

* Match the DGX Spark by its DMI name for the boot setting

The firmware delay has only been seen on the DGX Spark, so the setting stays
with that model: a GB10 whose DMI product name is NVIDIA_DGX_Spark, checked with
omarchy-hw-match as other single models are. It moves to
install/hardware/nvidia/, and a GX10 keeps its UKI.

* Check the kernel and initramfs hashes when factory reset runs without UKIs

The reset only checked the hashes of UKIs under /EFI/Linux, so on a DGX Spark,
which boots the kernel and initramfs directly, the check found nothing to
compare and passed. It now checks every hashed file limine.conf loads, leaving
snapshot copies under limine_history, which the rebuild does not touch.

* Hide Direct Boot on a Spark that boots without a UKI

Direct Boot points the firmware at the Omarchy UKI, and a DGX Spark with the
boot setting has none, so the menu offered an entry that could only fail with
"No Omarchy UKI found". The menu now hides it while that setting is in place.

* Find the Omarchy EFI entry with the Direct Boot helper in Setup

omarchy-setup-direct-boot kept its own pattern for the Omarchy EFI entry, which
missed an inactive entry and matched any label that starts with Omarchy.
omarchy-boot-direct --number now prints the boot number of every Omarchy entry,
active or not, and Setup > Direct Boot uses it.

* Add omarchy-hw-match-device-tree for models that share a DMI name (#15064)

* Add omarchy-hw-dt-match for models that share a DMI name

The Surface Pro 11 models report one DMI name and differ in the device tree's compatible strings, so omarchy-hw-match cannot tell them apart. This helper matches a whole compatible string, ignoring case as the kernel does, and takes several strings for a model that goes by more than one.

* Fall back to the sysfs device tree in omarchy-hw-dt-match

A root without /proc/device-tree but with /sys/firmware/devicetree/base went unmatched, and naming both fixture roots ignored sysfs. Read the first of the two that is there, as omarchy-hw-platform reads both.

* Compare compatible strings in the C locale in omarchy-hw-dt-match

Bash folds case by the session's locale. In a Turkish one I becomes a dotless i, so MICROSOFT,DENALI-OLED no longer matched microsoft,denali-oled.

* Rename omarchy-hw-dt-match to omarchy-hw-match-device-tree

Spelled out, so the name needs no decoding, and starting with omarchy-hw-match, so the two list side by side as omarchy hw match and omarchy hw match device tree.

* Keep the lid from suspending a laptop on a display whose connector type is Unknown

* Have the N1x firmware reserve 4 GiB for the GPU instead of reclaiming its 62.5 GiB in the kernel

* Install the N1x's kernel under its new name, linux-omarchy

omarchy-pkgs renames linux-omarchy-n1x to linux-omarchy (omarchy-pkgs
#1038): the aarch64 kernel takes the name the x86_64 one has.

The N1x package list and its hardware setup ask for it by that name
now: the packages to install, the fallback image and boot order Limine
is given, and the check that one such kernel is installed.

The migrations that moved N1x laptops onto linux-omarchy-n1x are left
as they were. The laptops that ran them are being reinstalled, and a
fresh install runs none of them.

* N1x setup: leave the kernel to the installer and the package list

The hardware setup installed linux-omarchy and its headers itself, and
kept NVIDIA's older linux-n1x in place until the machine had booted the
new kernel. Both were for laptops moving over from linux-n1x, and those
are being reinstalled.

On an install from the ISO neither does anything: the installer puts the
kernel and its headers on the machine and checks they match, and the
N1x package list names them. The list is now the one place in this
repository that names the N1x's kernel.

Other kernels are still dropped, so Limine shows one.

* Turn on CPPC autonomous selection on the N1x, so power profiles take effect

cppc_cpufreq leaves autonomous selection off, so the CPUs follow the
kernel governor and the energy performance preference power-profiles-
daemon sets per profile changes nothing. NVIDIA's RTX Spark driver for the
daemon relies on it being on, as their images set it. The firmware hands
over each core with its CPPC floor raised to its ceiling for a faster
boot, which autonomous selection would keep, so the cores would never
slow down.

As NVIDIA's power-knobs package does, a udev rule restores each policy's
full range when cppc_cpufreq loads and when a CPU comes online, then turns
autonomous selection on, which programs the floor and ceiling from that
range. The setup writes it on new installs and a migration on existing
N1x machines; it takes effect at the next boot.

* Use NVIDIA's MT8901 UCM profiles in place of Omarchy's

These are NVIDIA's profiles from alsa-ucm-conf#862 (822569010c),
unchanged. They pick a profile per SoundWire codec topology instead of
per machine, and cover the ProArt P14 and the Dell XPS 16 along with
NVIDIA's other RTX Spark boards. The Dell loses the headset microphone,
which NVIDIA does not declare on that board.

The files move again when alsa-ucm-conf merges #862 under the card's
upstream name, mt8901-sdw.

* Translate the notice that suspend is turned off on this machine

* Install Gliff on existing aarch64 machines in a migration of its own

* Retry the N1x boot rebuild until the reclaim option is gone

---------

Co-authored-by: Spencer Bull <spencerbull2554@gmail.com>
Co-authored-by: Spencer Bull <spencer@omarchy.org>
Co-authored-by: Birk Skyum <74932975+birkskyum@users.noreply.github.com>
Co-authored-by: Jimmy Van Veen <jimmy.van.veen@gmail.com>
Co-authored-by: Jim Martin <jimmartin@gmail.com>
Co-authored-by: Brandon W <103607286+turbineBMW@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: Emir Beganovic <beganovic.emir@gmail.com>
birkskyum pushed a commit to turbineBMW/omarchy that referenced this pull request Oct 17, 2026
The OLED, LCD and X Plus models share a DMI name, so the script read the
device tree itself. omarchy-hw-match-device-tree (omacom#15064) does that for any
such model, and the test fakes the tree through OMARCHY_PROC_ROOT like the
other platform tests, skipping as root where fixtures are ignored.

Validated with test/shell.d/surface-pro-11-hardware-test.sh,
hw-match-device-tree-test.sh, snapdragon-hardware-test.sh and
surface-hardware-test.sh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
birkskyum added a commit to turbineBMW/omarchy that referenced this pull request Oct 17, 2026
omarchy-hw-dt-match became omarchy-hw-match-device-tree before omacom#15064 went in, so the old name is not on n1x and the model check was always false.
birkskyum pushed a commit to turbineBMW/omarchy that referenced this pull request Oct 17, 2026
The OLED, LCD and X Plus models share a DMI name, so the script read the
device tree itself. omarchy-hw-match-device-tree (omacom#15064) does that for any
such model, and the test fakes the tree through OMARCHY_PROC_ROOT like the
other platform tests, skipping as root where fixtures are ignored.

Validated with test/shell.d/surface-pro-11-hardware-test.sh,
hw-match-device-tree-test.sh, snapdragon-hardware-test.sh and
surface-hardware-test.sh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
birkskyum added a commit to turbineBMW/omarchy that referenced this pull request Oct 17, 2026
omarchy-hw-dt-match became omarchy-hw-match-device-tree before omacom#15064 went in, so the old name is not on n1x and the model check was always false.
turbineBMW added a commit to turbineBMW/omarchy that referenced this pull request Oct 21, 2026
The OLED, LCD and X Plus models share a DMI name, so the script read the
device tree itself. omarchy-hw-match-device-tree (omacom#15064) does that for any
such model, and the test fakes the tree through OMARCHY_PROC_ROOT like the
other platform tests, skipping as root where fixtures are ignored.

Validated with test/shell.d/surface-pro-11-hardware-test.sh,
hw-match-device-tree-test.sh, snapdragon-hardware-test.sh and
surface-hardware-test.sh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
turbineBMW pushed a commit to turbineBMW/omarchy that referenced this pull request Oct 21, 2026
omarchy-hw-dt-match became omarchy-hw-match-device-tree before omacom#15064 went in, so the old name is not on n1x and the model check was always false.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant