Repository navigation
Hand the M3 Air GPU to Linux on install and on update - #68
Conversation
The M3 Air leaf now appends the GPU start, chosen.asahi,t8122-gpu=1, and its power handoff, chosen.asahi,t8122-gpu-power-standin=1 and chosen.asahi,t8122-gpu-fuse-leakage=1, beside the display line on both Air sizes. These are the switches aurora-sep's persistent J613 profile boots. The GPU lines go in only while the display line is 1 and the owner has no t8122-gpu* or j61x-25g83* line, so an owner's choice or the native 25G83 experiment profile is never changed. 96-omarchy-mac-m3-air.hook runs the leaf again after an install or upgrade of omarchy-mac-boot or m1n1-aurora, after 95-m1n1-install.hook, so Airs installed before this, or with an older m1n1-aurora, get the lines on update. Its script never fails the transaction, and the leaf's own gates still leave other Macs, older m1n1 and chroots alone.
[Medium impact] The reviewed changes appear safe to merge, with no outstanding findings. SummaryAdds M3 Air GPU defaults during setup and package updates while keeping the owner's settings.
|
arch-chroot bind-mounts the host's /run, so /run/systemd/system alone let the new update hook edit m1n1.conf and run update-m1n1 inside an Air's chroot; systemd-detect-virt --chroot now stops it. An owner's display line with an empty or padded value read as absent, so the leaf added the display and GPU anyway; any owner line now stays, and the GPU goes in only beside display lines that are all exactly 1.
sed printed nothing for a final chosen.asahi,t8122-dcp= without its newline, so the leaf took the file as having no display line and added the display and GPU. Each value now carries a marker, so that line counts as the owner's and keeps the GPU out.
chriskearney
left a comment
There was a problem hiding this comment.
The install and upgrade wiring checks out at c85c97dab6437bb7dd9c7b573e4b4e46be32da34. The focused m1n1-display-test.sh fixture passes for J613/J615 defaults, display-only upgrades, idempotence, explicit GPU/display/profile choices, minimum-version refusal, the bound-/run chroot case and config restoration on failure. The latest no-final-newline display-value fix is included. I found no source blocker in that scope.
This is source and host-fixture validation, not a device boot or full local package-suite pass. The documented boot.bin/config rollback limitation remains unchanged. J615’s final profile still needs actual device qualification, as already noted in the PR.
For the coordinated cutover, the matching kernel-default and normal system-Mesa handoff slices are draft linux-aurora #230 and #231, alongside package PR omacom/omarchy-pkgs#1591. Those drafts still need full native build/package/device qualification; this boot setup change alone does not establish an accelerated default desktop. Pro boot defaults remain a separate slice.
Picks up omacom/omarchy-mac-pkgs#68. An M3 MacBook Air (J613 or J615) gets m1n1's GPU start and power handoff in /etc/m1n1.conf beside the display line, at install and, through a new pacman hook, at the update that brings this package or a new m1n1-aurora. An owner's own lines, chroots and older m1n1 stay untouched.
Summary
Item 3 of the M3 Air GPU plan, alongside Mesa omarchy-pkgs#1591, the kernel omarchy-pkgs#1622 plus Chris's default-start change, and the login hook in linux-aurora. The kernel's T8122 runtime starts only after m1n1 has handed the GPU over, and m1n1 does that only on
chosen.asahi,t8122-gpu=1. Until now this package wrote only the display line, and only at install.These four lines are what aurora-sep's persistent J613 profile boots (
m3_air_switch_set). m1n1 checks the 14.8.3 GPU firmware before touching the GPU and leaves the node disabled on any other firmware.The owner's lines win:
t8122-dcpline of the owner's, for either value, is kept.chosen.asahi,t8122-gpu*orchosen.asahi,j61[35]-25g83*line, sogpu=0and the native 25G83 experiment profile stay as the owner set them.No kernel command-line flag is added: automatic startup belongs to the kernel default.
Evidence
chosen.asahi,t8122-dcp=1only. An Air installed earlier got nothing on update.After:
m1n1-display-test.shchecks the following:update-m1n1;gpu=0,gpu=1,gpu-handoff-diag=1andj615-25g83-experimental=1leave the file andboot.binuntouched;dcp=0adds nothing;95-m1n1-install.hook, and its script runs the staged leaf and exits 0 when the leaf fails.omarchy-mac-boot/test/all: 247 ok in an Arch Linux ARM container. One case skips withoutOMARCHY_TEST_RUNTIME, which CI sets.Merge Danger
Door: two-way
The hook changes
/etc/m1n1.confandboot.binon M3 Airs at their next update. Reverting the package stops new writes but doesn't remove lines already written. An owner, or a follow-up, sets them to 0.Blast Radius: M3 Airs
Publish this together with, or after, a kernel that starts the T8122 runtime by default and the RC Mesa. With an older kernel, m1n1 hands over a GPU that nothing starts. The 15-inch J615 has no hardware evidence on this profile yet; aurora-sep enables it on the J613 only.