Skip to content

linux-aurora: pin aurora9 (J516C display/GPU, G15 fixes) with mesa#17 - #1736

Merged
ryanrhughes merged 1 commit into
masterfrom
pin-linux-aurora9-mesa17
Oct 28, 2026
Merged

ryanrhughes merged 1 commit into
masterfrom
pin-linux-aurora9-mesa17

Conversation

@maralcbr

@maralcbr maralcbr commented Oct 28, 2026 •

Copy link
Copy Markdown
Member

Pins linux-aurora to integration/aurora at 30a65186 (aurora9) and mesa-aurora to integration/aurora at 7f0206e7, so the kernel and Mesa reach edge together.

Kernel (aurora8 → aurora9, 937b727e → 30a65186)

  • linux-aurora#249: the J516C GPU board data comes from the ADT export and fixed reference words, with no board file.
  • linux-aurora#246: the J516C native display is on by default, the T6031 GPU waits for the display, and asahi autoloads.
  • linux-aurora#253: Eryk's G15 submission fixes (stamp wrap, slot binding at publication, one mapping lock per submit) and the T6030 PMP power vote.
  • linux-aurora#240: DCP panel dimensions.

Mesa (7c86130d → 7f0206e7)

Landing order

  1. This PR first. With the current m1n1 (aurora21), a J516C gets no display handoff, so it keeps the boot framebuffer and the GPU stays off, the same as today.
  2. Then #1707 (m1n1 aurora22, bc79acc4), once this is on edge, so edge never pairs the new stage 2 with the old kernel.

Evidence and limits

For the release notes

Existing aurora-sep Max installs (dcp=1,gpu=0) get the native display on this kernel, and their GPU stays off. Recovery steps: linux-aurora#189.

@ryanrhughes
ryanrhughes enabled auto-merge (squash) October 28, 2026 05:05
@greptile-apps

greptile-apps Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] No actionable issue was found that blocks merging these package pin updates.

Summary

Updates the kernel and Mesa pins together.

  • The Aurora kernel package moves to aurora9.
  • Mesa packages use the newer M3 Pro Vulkan profile.

Acknowledged by maralcbr in the PR description: the exact combined kernel still needs J516C and M3 Pro boot and graphics checks. The later m1n1 update is intentional to avoid pairing the new stage 2 with the old kernel. Neither is reported as a new finding.

Reviews (1) · Last reviewed commit: "linux-aurora: pin aurora9 with J516C dis..." · Reviewed by Greptile

@github-actions

Copy link
Copy Markdown
Contributor

Publish succeeded → live

Packages: linux-aurora (aarch64, PR artifact); mesa-aurora (aarch64, PR artifact)

  • edge/aarch64: linux-aurora-7.2.11.aurora9-1-aarch64, linux-aurora-headers-7.2.11.aurora9-1-aarch64, mesa-aurora-1:26.3.0_devel.20261028.231099.7f0206e79f9-1-aarch64, vulkan-aurora-1:26.3.0_devel.20261028.231099.7f0206e79f9-1-aarch64

Some planned slots did not run because an earlier slot failed.

Commit b3a318d · run

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.

2 participants