Repository navigation
Conversation
cachebag
requested review from
chriskearney,
maralcbr and
scottjones
as code owners
November 5, 2026 02:07
The 14" M3 Pro (J514S) set up by the Asahi installer reports m1n1
stage 1 v1.6.1, not the Omarchy installer's v1.6.1-dirty, with the same
macOS 14.8.3 stub and iBoot. m3_stage1_problem refuses the handoff on
it even with --m3-handoff ("its m1n1 stage 1 is v1.6.1").
Let m3_clean_stage1_14_qualified admit j514s/t6030 on the same terms
the M3 Airs already have (OS firmware 14.7 or 14.8.3, 14.8.3 stub, no
oslog overlap), but only when the owner asked with --m3-handoff. A plain
run stays kernel-only; j516s and M3_STAGE1_VERSIONS are unchanged.
Booted on a J514S (os-fw 14.7, system-fw 26.6.2, stage 1 v1.6.1) with
aurora-2026.10.17.20: the handoff comes up with the native display and
G15S GPU, no oslog overlap node, three dcp-oslog nodes.
Signed-off-by: cachebag <alhakimiakrmj@gmail.com>
cachebag
force-pushed
the
j514s-stage1
branch
from
November 5, 2026 02:12
ab34cc0 to
af5dad1
Compare
This was referenced Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 14" M3 Pro (J514S) set up by the Asahi installer reports m1n1 stage 1 v1.6.1, not the Omarchy installer's v1.6.1-dirty, with the same macOS 14.8.3 stub and iBoot. m3_stage1_problem refuses the handoff on it even with --m3-handoff ("its m1n1 stage 1 is v1.6.1").
Let m3_clean_stage1_14_qualified admit j514s/t6030 on the same terms the M3 Airs already have (OS firmware 14.7 or 14.8.3, 14.8.3 stub, no oslog overlap), but only when the owner asked with --m3-handoff. A plain run stays kernel-only; j516s and M3_STAGE1_VERSIONS are unchanged.
Booted on a J514S (os-fw 14.7, system-fw 26.6.2, stage 1 v1.6.1) with aurora-2026.10.17.20: the handoff comes up with the native display and G15S GPU, no oslog overlap node, three dcp-oslog nodes.
Report: #360
AI Disclosure: I did not use AI for these (#358, #361, asahi-alarm/PKGBUILDs#100) patches, though the commit messages were all generated via Opus 5.5.