Skip to content

Add the aarch64-surface platform for the Surface Pro 11 - #15031

Closed
GeneralPawz wants to merge 1 commit into
omacom:quattrofrom
GeneralPawz:surface-pro-11-platform
Closed

GeneralPawz wants to merge 1 commit into
omacom:quattrofrom
GeneralPawz:surface-pro-11-platform

Conversation

@GeneralPawz

Copy link
Copy Markdown

Fixes #15030

The Surface Pro 11 (Snapdragon X, devicetree root microsoft,denali, LCD and OLED) runs Arch Linux Ports with the linux-sp11 kernel repository instead of Arch Linux ARM, and boots a UKI that its kernel package builds from mkinitcpio's output. As plain aarch64 it gets Arch Linux ARM's pacman template (dropping its kernel repository on omarchy refresh pacman), the ALARM keyring, and the generic initramfs hooks, whose build fails there (btrfs-overlayfs doesn't exist).

This adds aarch64-surface as a family of its own, following the Platforms section of AGENTS.md:

  • omarchy-hw-platform reports aarch64-surface for a microsoft,denali devicetree; omarchy-hw-aarch64-surface predicate
  • default/pacman/aarch64-surface/: edge template with the Ports repositories and the kernel repository. [omarchy] sits last: its aarch64 builds target Arch Linux ARM's libraries, which lag Ports (e.g. Qt 6.11 vs 6.12), so packages both publish come from Ports
  • install/post-install/pacman.sh: no archlinuxarm-keyring on this platform
  • 00-omarchy-hooks.conf: the platform keeps mkinitcpio.conf's own HOOKS line
  • omarchy-pkg-defaults, pacman helpers, image manifest: accept the name
  • hw-platform test: LCD and OLED fixtures

Validation: hw-platform, pacman-templates, image-target-platform, mkinitcpio-hooks, mkinitcpio-apple-drop-ins and platform-app-hooks tests pass. On the device (Surface Pro 11, LCD): the detector prints aarch64-surface, pacman-conf resolves the template to the same repositories and order as the working install, and the hooks drop-in leaves the original HOOKS line unchanged.

The Surface Pro 11 (devicetree root "microsoft,denali", LCD and OLED) runs
Arch Linux Ports with the linux-sp11 kernel repository, not Arch Linux
ARM, and boots a UKI that its kernel package builds. As plain aarch64 it
gets Arch Linux ARM's pacman template, which drops the kernel repository
on `omarchy refresh pacman`, the ALARM keyring, and the generic initramfs
hooks (plymouth, encrypt, btrfs-overlayfs), whose build fails there.

- omarchy-hw-platform: report aarch64-surface for "microsoft,denali", with
  an omarchy-hw-aarch64-surface predicate
- default/pacman/aarch64-surface: Arch Linux Ports + linux-sp11 template,
  [omarchy] last because its aarch64 builds target ALARM's libraries
- post-install pacman: no ALARM keyring on this platform
- 00-omarchy-hooks.conf: keep mkinitcpio.conf's own HOOKS line
- pkg-defaults, pacman helpers, image manifest: accept the new name
- hw-platform test: LCD and OLED fixtures
@greptile-apps

greptile-apps Bot commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 4/5

[Medium impact] Adds a new hardware platform variant for Surface Pro 11.

The PR appears safe to merge, with a non-blocking request to test the new Surface pacman and hook behavior.

Findings

  1. P2 Surface fixes lack regression tests ▶

Summary

Adds aarch64-surface for Surface Pro 11 machines running Arch Linux Ports.

  • Surface Pro 11 devices get their own aarch64-surface platform identity.
  • Surface installs use Ports repositories and the Surface kernel source.
  • Surface keeps its own mkinitcpio hook line for its unified kernel image.

GeneralPawz explicitly describes putting Ports packages ahead of Omarchy packages as intentional because Omarchy's ARM builds target older libraries.

Reviews (1) · Last reviewed commit: "Add the aarch64-surface platform for the..." · Reviewed by Greptile

# The Surface Pro 11 boots a unified kernel image built by its kernel package
# from mkinitcpio.conf's own line (no Limine, no btrfs-overlayfs, no plymouth
# splash on its command line), so its line stays as it is.
[[ $_omarchy_platform != "aarch64-surface" ]] || _omarchy_platform=platform-owned

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Surface fixes lack regression tests

pacman-templates-test.sh still excludes aarch64-surface, and mkinitcpio-hooks-test.sh never checks that it keeps its original HOOKS. Those suites can pass even if a refresh drops the Surface repositories or a rebuild restores the unwanted hooks.

Add Surface cases that check repository order, template copying, the ALARM keyring exclusion, and preservation of a custom HOOKS line.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@birkskyum

Copy link
Copy Markdown
Contributor

Thanks for the report and the detail in #15030. Some context that may save you work, since the ARM side is moving on the n1x branch right now.

On n1x the Snapdragon laptops are one family, aarch64-qualcomm, and a single model sits behind a check for its device tree string, omarchy-hw-match-device-tree from #15064. @turbineBMW's Surface Pro 11 setup is built that way in #14390, and omacom/omarchy-pkgs#975 moves it onto Omarchy's own aarch64 kernel in place of linux-sp11. So a microsoft,denali tree is aarch64-qualcomm there, and a second family for the same laptops would pull the two apart.

Your two findings stand apart from that. The hooks list failing where there is no btrfs-overlayfs hook, and the pacman template replacing a setup that is not Arch Linux ARM, are real on any machine that did not come from Omarchy's installer. It may be worth keeping #15030 for those.

It would be good to compare notes with @turbineBMW. You have the LCD model, and his work is tested on the OLED one.

@jandrusk

Copy link
Copy Markdown

Thanks for writing this up so thoroughly. A couple of questions:

  • [dwhinham] inherits SigLevel = Required DatabaseOptional, but nothing here installs or locally signs that repository's packager key, and archlinuxarm-keyring is now skipped. On a fresh image, or after omarchy refresh pacman on a machine without the key, how does the key get trusted? A keyring step or a short note in the template would help.
  • Shipping templates that point at a personal GitHub releases repo and a community Ports mirror (arch-linux-repo.drzee.net) as Omarchy defaults is probably a maintainer call, so flagging it for them.
  • Overlap: Add Microsoft Surface Pro 11 board support #14390 (base n1x) adds Surface Pro 11 board support by a different route (ALARM plus linux-sp11 replacing linux-aarch64, matching microsoft,denali-oled). It's worth reconciling the two so the platform name and detection don't diverge.

@omarchybot omarchybot added the enhancement New feature or request label Oct 17, 2026
@birkskyum

Copy link
Copy Markdown
Contributor

@GeneralPawz Since this was opened, Omarchy's ARM side moved to one kernel of its own. Every Snapdragon laptop runs linux-omarchy, which has the Surface Pro 11 patches since 7.2.8-19 (omacom/omarchy-pkgs#975), and @turbineBMW's board support in #14390 is built on that, tested with a fresh install on the OLED model. So the Surface Pro 11 won't get a platform of its own on Arch Linux Ports, and this PR can be closed in favour of #14390. #15030 stays useful for the two problems on installs that didn't come from Omarchy's installer.

What would help most is your LCD X Plus. #14390 leaves the LCD and X Plus models alone until someone tests them, so a run of the ARM image from #11823 on yours, posted on #14390 with what works and what doesn't, is what gets them covered.

@birkskyum

Copy link
Copy Markdown
Contributor

Closing this, since Omarchy's ARM side now runs one kernel of its own, linux-omarchy, which carries the Surface Pro 11 patches, and the Surface Pro 11's setup lives in install/hardware/microsoft/surface-pro-11.sh. Thanks for the groundwork here. If something on the Surface Pro 11 still only works with this platform, an issue or a PR against that setup is welcome.

@birkskyum birkskyum closed this Nov 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

aarch64: initramfs build fails on a UKI-booted Snapdragon install (btrfs-overlayfs hook); ALARM pacman template replaces non-ALARM repositories

4 participants