Repository navigation
Add generic Snapdragon X support on aarch64 - #8672
Conversation
|
@JimmayVV — thank you for the Snapdragon work. Your three snapdragon branches are what made the Yoga Slim 7x installation possible. I have opened the generic work for upstream review with your original commit authorship preserved: this PR, omacom/omarchy-iso#129, and omacom/omarchy-pkgs#221. The drafts are intentionally still gated on a fresh encrypted-install test. Please review or correct the split; I am happy to restructure it around how you want the work presented. |
|
@birkskyum, thank you. This is what I was hoping would happen. I only did this to get the ball moving, and seeing it boot a second machine with audio working is more than I managed on my own. I'm happy for these PRs to be the upstream path with you driving. I'll review, test on the G1q, and otherwise stay out of the way. The split looks right to me, and the provenance is accurate on all five PRs. One thing I think needs a look, which I've left on omacom/omarchy-pkgs#222 since it lives there. The pkgbase shim also wrote Testing on an HP EliteBook Ultra G1q with the X1E-78-100 and linux-aarch64 7.2-2, from these same commits. It installs and boots via Limine. Display at native resolution with GPU acceleration, Wi-Fi, Bluetooth, keyboard, touchpad and touchscreen all work. Audio doesn't yet. The card needs a topology and UCM name that upstream hasn't given the G1q, and I have a small follow-up for that. The encrypted path is also open. On the G1q the LUKS prompt comes up with the panel dark and no keyboard driver in the initramfs, so it looks hung. That's JimmayVV/omarchy-iso#25, and it may be useful for your encrypted-install gate. Anything new from me, audio, USB-C root disks, encrypted installs, will be small follow-ups after these land rather than additions to this stack. |
|
Correction to the Yoga validation above: microphone input works, but the internal speakers currently produce no sound during playback. I have corrected the PR descriptions; Yoga audio output remains an open hardware item. |
There was a problem hiding this comment.
Pull request overview
Adds aarch64 and Qualcomm Snapdragon X installation support, including boot configuration, firmware, graphics, and Arch Linux ARM package sources.
Changes:
- Adds ARM-safe Node, mkinitcpio, and pacman handling.
- Configures Qualcomm DTBs, firmware, kernel parameters, and Freedreno.
- Integrates Qualcomm detection and hardware setup.
Tip
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.
Reviewed changes
Copilot reviewed 11 out of 12 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
install/user/mise-work.sh |
Selects architecture-specific Node bundles. |
install/post-install/pacman.sh |
Restores ARM repositories and key trust. |
install/omarchy-other.packages |
Stages the Qualcomm extractor package. |
install/hardware/vulkan.sh |
Installs Freedreno on Qualcomm systems. |
install/hardware/qualcomm/kernel-params.sh |
Adds Snapdragon boot parameters. |
install/hardware/qualcomm/firmware.sh |
Installs firmware and DSP safeguards. |
install/hardware/qualcomm/dtb-uki.sh |
Embeds Qualcomm DTBs in UKIs. |
install/hardware/all.sh |
Runs Qualcomm setup leaves. |
etc/mkinitcpio.conf.d/thunderbolt_module.conf |
Restricts Thunderbolt to x86_64. |
default/pacman/pacman-aarch64.conf |
Defines Arch Linux ARM repositories. |
default/pacman/mirrorlist-aarch64 |
Adds the ARM package mirror. |
bin/omarchy-hw-qualcomm-soc |
Detects Qualcomm device-tree systems. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
I think I found why the speakers are silent on both machines. Arch Linux ARM's |
|
Thanks, Jimmy. I independently checked the current official ALARM config and upstream Yoga DTS. ALARM has |
|
The speaker fix is now physically validated on the Yoga and submitted upstream as archlinuxarm/PKGBUILDs#2217. With |
Each of these is an unconditional assumption that only holds on x86_64. None
is x86-specific in spirit, and each one blocks or breaks an ARM64 install.
1. etc/mkinitcpio.conf.d/thunderbolt_module.conf
MODULES+=(thunderbolt) is unconditional, but Thunderbolt is x86-oriented
hardware and the module is not built for every architecture -- Arch Linux
ARM's aarch64 kernel has no `thunderbolt`. mkinitcpio treats an unresolvable
MODULES entry as a hard error, so *every* initramfs build fails:
==> ERROR: module not found: `thunderbolt'
That means no UKI, no boot entry, and an install that completes and then
cannot boot.
2. install/post-install/pacman.sh
This overwrites /etc/pacman.conf unconditionally. That config points
[core]/[extra]/[multilib] at Omarchy's mirror of Arch, which is x86_64-only,
and [omarchy] at pkgs.omarchy.org/stable/$arch, which 404s for aarch64.
([multilib] is 32-bit x86 libraries and exists on no ARM mirror at all.)
Applying it on ARM leaves the installed system unable to update anything.
3. install/user/mise-work.sh
Node publishes its builds as linux-x64 / linux-arm64, which does not match
uname -m. The bundled-tarball lookup hardcodes linux-x64, so on ARM it finds
nothing and the install aborts with "no bundled Node tarball". The sed that
parses the version back out of the filename needs the same treatment.
All three were found by installing Omarchy on aarch64 (Arch Linux ARM) and are
fixed here the same way: derive from uname -m rather than assuming.
The previous guard skipped the pacman.conf restore on aarch64 on the grounds that Omarchy's config points at x86-only repositories. But at that point the target still carries the live ISO's pacman.conf, which knows only the offline mirror, and that directory does not exist on the installed system. Skipping therefore left every aarch64 install unable to run pacman at all, which is the outcome the guard claimed to prevent. Derive the config from Omarchy's template instead: drop [multilib], keep [omarchy] (its $arch placeholder resolves correctly), add Arch Linux ARM's [alarm] and [aur] repositories, and leave the mirrorlist the distribution installed rather than replacing it with Omarchy's x86_64 mirror of Arch. The x86_64 path is unchanged.
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.
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.
Adreno GPUs are platform devices, so the lspci vendor scan in vulkan.sh never sees them; ask the SoC probe instead.
…s 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).
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.
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.
The final pacman restore is skipped entirely on ARM, which leaves the installed system pointed at the live ISO's offline config -- a file:// repo under a bind mount that only exists during the install. The first thing a new aarch64 desktop does is fail: $ sudo pacman -Sy evtest failed retrieving file 'offline.db' from disk: Could not open file /var/cache/omarchy/mirror/offline/offline.db No pacman -S, no omarchy-update. The skip was right that Omarchy's channel configs cannot be applied on ARM -- [core]/[extra] come from Omarchy's mirror of Arch, which builds x86_64 only, [multilib] is 32-bit x86, and the Omarchy package repository serves no aarch64 tree -- but the configuration it keeps instead is the offline one, so it trades a broken config for no config. Restore Arch Linux ARM's repositories there instead: [core] [extra] [alarm] [aur], its stock set, through a mirrorlist of its own because ALARM serves $arch/$repo where Arch serves $repo/os/$arch. [options] is kept byte-identical to the x86_64 channel configs. [omarchy] is left out until that tree exists; including it would 404 on every sync, and Omarchy's own packages simply hold at the versions the ISO installed. Three further things the restore has to do that the x86_64 path does not: - Take archlinuxarm-keyring while the offline mirror is still the active source. Arch's `base` pulls in archlinux-keyring and nothing pulls in this one, and the repositories being written are unreachable during an offline install. - Write the mirrorlist unconditionally. The target's mirrorlist carries Omarchy's and Arch's x86_64 mirrors ahead of ALARM's, so a sync logs 404s from mirror.omarchy.org, mirror.rackspace.com and geo.mirror.pkgbuild.com before it finds anything. - Populate the keyring. The install leaves ALARM's build key untrusted on the target, so the first signed install fails with "Arch Linux ARM Build System <builder@archlinuxarm.org> is unknown trust". x86_64 keeps running the same two lines it ran before, and every other architecture keeps the behaviour it had before the skip was introduced.
b394e2d to
c1379b8
Compare
|
@JimmayVV, thanks again for your work on this. Since your G1q report, the shared speaker-reset fix has merged in archlinuxarm/PKGBUILDs#2217, and we've got speakers and graphical disk unlock working on the Yoga. Some of these fixes may help the G1q too, including JimmayVV/omarchy-iso#25. Would you be interested in testing a G1q-specific update when you have time? If you've already tried a newer kernel with your HP topology/UCM fixes, I'd also be interested to hear how it went. I'd adapt the Yoga-specific unlock changes and provide rollback instructions first, keeping the USB-root DSP safeguard if you're still using an external disk. No reinstall or Lenovo firmware needed. |
|
@birkskyum thanks for carrying this forward. One part of the PR I'd like to raise The template approach writes a fixed ALARM config and appends
An alternative that avoids all four: on aarch64, leave the existing config Limitations, to be upfront: it can't reset a broken ARM config the way the x86 Happy to fold this into your branch instead of a separate PR if you'd prefer. |
|
Thanks, Jim. Looks like you’re right about the refresh losing the repository ordering and mirror choices set by the installer. I’ll fold your change into this branch, preserving your authorship. |
(cherry picked from commit 6276d6b)
|
Confirmed the fold, thanks. The ARM refresh test, the aarch64 pacman test, and |
Summary
Dependencies and provenance
Carries Sean's ARM runtime prerequisites from #8039 and Jimmy Van Veen's generic Snapdragon work from
JimmayVV/omarchy@snapdragon, with original authorship preserved. The #8039 code is already in this branch; if that PR lands first, rebase this branch to leave only the Snapdragon changes.qcom-firmware-extractfrom Add safe Windows firmware extraction for Snapdragon laptops omarchy-pkgs#221 before distributing it. The package handles firmware inspection and board-selected GPU initramfs inclusion even when no files need extracting. This does not make Windows extraction a requirement for every Snapdragon laptop; device-tree discovery and ACPI/X2 limits are described in that package PR.Jim Martin's repository-preserving ARM refresh is included with his authorship preserved. The stable/RC safeguard remains while those ARM repositories are unpublished and #8781's rollback is unmerged. That rollback is not required for this guarded refresh change, and it is not included here.
The systemd shutdown fix and camera stack described below are separate follow-ups, not merge prerequisites.
Validation
5c3bce42d65b4443e619568dadd7a0b263107d8d. A September 7 ASUS follow-up reached the installer welcome screen and connected to Wi-Fi using the pinned September 6 integration image. That is live-session validation, not a fresh installation or confirmation of every current PR change. Board-specific display and audio coverage differs.The installed Yoga hardware report confirms Limine without the hash warning, graphical disk unlock, polished shutdown/reboot, Wi-Fi, Bluetooth, speakers and microphone. The shutdown result used a separate systemd v261.2 backport of systemd/systemd#43671, not a change included in this PR. The hardware report also covers the fast, denoised camera preview and subsequent Chromium live-video test on an experimental setup. Camera enablement remains separate from this PR.
Before the September 9 refresh revision, repository regression tests also passed on the physical Yoga using temporary files and stubbed upgrades. Enabling only the ARM edge repository on the installed Yoga made ChatGPT and VS Code discoverable through pacman, with no package upgrade or ALARM database/mirror change. The repository-preserving revision has only been tested in isolated containers so far. Neither result is a fresh-install or full-upgrade validation. The separate speaker-reset kernel fix, archlinuxarm/PKGBUILDs#2217, has merged.