You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
5 board configurations · one shared discussion · Aurora Linux assessment
Broad kernel integration is present: Aurora's working tree includes this product's core platform, NVMe, GPU, DCP display, USB, wireless and audio paths. Board-specific exceptions and Aurora's newer development work are listed below; this assessment is not a blanket pass for every port, firmware version or installation.
Refreshed October 16, 2026. Baseline: aurora-wip at f53454ba0da1. Open PR and feat/sep results are identified separately. These statuses use Aurora's public source and contributor reports with their actual tested kernels identified. The baseline source and every linked PR state were rechecked; no new physical test was performed for this update.
Configurations
Board
Silicon / SoC
Model / configuration
Year
Aurora assessment
J293
M1 · T8103
MacBook Pro 13-inch
2020
🔵 Broad kernel integration; board reports below
J314S
M1 Pro · T6000
MacBook Pro 14-inch
2021
🔵 Broad kernel integration; board reports below
J316S
M1 Pro · T6000
MacBook Pro 16-inch
2021
🔵 Broad kernel integration; board reports below
J314C
M1 Max · T6001
MacBook Pro 14-inch
2021
🔵 Broad kernel integration
J316C
M1 Max · T6001
MacBook Pro 16-inch
2021
🔵 Broad kernel integration; board reports below
Evidence key · Aurora source and Aurora hardware reports
Marker
Meaning
🔵 Integrated source
The relevant implementation or enabled board description exists in the pinned Aurora working tree. This is source evidence, not a new hardware test.
🟢 Hardware report
A linked public Aurora report names the board and tested feature. Read its revision and limits.
🟠 Development / partial
An open PR, feature branch, incomplete configuration or qualification remains.
🔴 Source gap
The required driver match or board path is absent or disabled in this snapshot.
⚪ Unverified
The evidence checked here does not establish this capability.
—
Not fitted to this product.
A report from another board is not a pass for this board. An open PR may work on hardware without being integrated into aurora-wip. A driver being enabled does not by itself establish firmware availability, userspace integration or a complete usable installation.
🧩 Core platform
Feature
Aurora status
Evidence / boundary
Board description / kernel build target
🔵 Integrated source
Every board above has a DTS and a Makefile target. Bootloader handoff and a repeatable installer run are separate checks.
NVMe / ANS storage
🔵 Integrated source
Enabled storage nodes in every board tree; CONFIG_NVME_APPLE=m.
CPU frequency / idle
🔵 Integrated source
Enabled cluster-frequency nodes; Apple cpufreq, CPU idle and PMU options configured. CPU idle is not whole-system suspend qualification.
Interrupts / IOMMU / platform buses
🔵 Integrated source
Apple AIC, DART, GPIO, I²C, SPI, SPMI and RTKit platform options are configured; board-specific nodes are in the linked DTS sources.
SMC / RTC / sensors
🔵 Integrated source
SMC paths present; MACSMC RTC, input, hwmon and power drivers configured.
Enabled AGX node and matching driver entry for the listed SoCs; CONFIG_DRM_ASAHI=m. On J316S, vkcube and prime-test (6 × 200) passed on a one-shot c679c8a7 kernel with merged linux #240. Mesa, firmware and application / conformance results must be recorded separately.
Display pipeline
🔵 DCP integrated; 🟢 J316S and J314S reports
Enabled DCP / DCPEXT paths and CONFIG_DRM_APPLE=m. Merged linux #224 (legacy reply records) and linux #225 (released register ranges) fix the pre-H17P DCP paths that M1/M2 firmware uses; on J316S (DCP firmware 13.5) both DCPs bind and the panel runs 3456x2160@120 with 5/5 swaps and working backlight (no external monitor attached). Merged linux #313 (external-display resume, DCP message hold in s2idle) was qualified on J700 only. J314S Type-C display routing work is open (reports below). Connector routing, refresh modes and hotplug remain board- and firmware-specific.
Speakers / headphone jack
🔵 Speaker + headphone links
MCA / Mac audio drivers and codecs are configured. Audio routing in source does not establish safe speaker tuning or a playback qualification.
Built-in microphones
🔵 AOP audio enabled; 🟢 J316S capture check
Board AOP audio state checked; CONFIG_SND_SOC_APPLE_AOP_AUDIO=m. J316S one-shot boots of merged linux #232 and linux #237 recorded five non-silent built-in microphone captures each. Record actual capture quality and channel behaviour per board.
Built-in camera
🔵 ISP integrated; 🟢 J316S report
Enabled ISP node with a matching driver family and CONFIG_VIDEO_APPLE_ISP=m. Merged linux #220 holds 30 fps in low light by default: on J316S, 3 × 150 frames at 29.99 fps in a dark room (15.00 fps on the stock kernel), and exposure_dynamic_framerate=1 restores the old behaviour. One-shots of merged linux #267 and linux #268 opened, streamed and reopened the J316S camera. Other boards need their own runs.
Hardware video decode
🔵 AVD source; 🟠 qualification
AVD nodes and decoder driver are present and CONFIG_VIDEO_APPLE_AVD=m. Decoder fixes in #45 are merged into aurora-wip; codec / stream coverage and application integration are not a general pass.
Video encode / ProRes
⚪ Unverified
This audit does not establish an integrated, hardware-qualified encode or ProRes pipeline.
Neural Engine
🔵 Driver + runtime PM; chip-specific enablement
linux #155 and buffer/lifetime fix linux #191 are merged. Runtime PM autosuspends after 1.5 s by default. The pinned DT enables T8103, T6000/T6001 and T6020/T6021; base M2/T8112 and M1/M2 Ultra remain disabled. Firmware and userspace are separate requirements. Since October 12, asahi.config selects CONFIG_DRM_ACCEL=y and CONFIG_DRM_ACCEL_ANE=m (direct merge 45da41c0cd1b); the arm64 defconfig alone does not, and a configured driver is not a per-board runtime test. J293 and J314S each completed 600/600 bit-exact add calls over 30 autosuspend/resume cycles, four concurrent 20-call runs and a device-test suspend cycle on contributor kernel 11.31/custom/sep@87e165cc (report). This is not a full-system suspend test or a direct power measurement. A report records passing in-tree smoke rows for M1, M1 Pro and M2 Pro; chip enablement does not qualify every product.
🔌 I/O and security
Feature
Aurora status
Evidence / boundary
USB2 / USB3 host
🔵 DWC3 integrated
Enabled Apple DWC3 board nodes and configured driver. Port combinations, hubs and role swaps need per-board tests.
linux #8, linux #50, linux #184, linux #193 and linux #195 are merged and their merge history reaches the pinned tree. asahi.config selects CONFIG_USB4=m and CONFIG_USB4_APPLE_SOC=m. linux #46 and linux #51 closed without merge on October 11; #8 had already carried their dual-stream and controller-teardown lock changes, as it carried linux #64. Merged linux #327 lets a CD321x port register without its USB4 router once that router fails to bind (builds without USB4_APPLE_SOC); it was tested on J316S and J413 only. J316S results for #327, T6000 reference-Mac results for open linux #332, and J314S two-display and HPD work in open linux #316, m1n1 #33 and linux #302, are in the reports below. A default-on T600x/T602x PCIe-C cold-init path (pcie_apple.tunnel_kernel_init) reached the pinned tree on October 12 through direct merge 45da41c0cd1b; no M1 Pro/Max tunnel device was retested on it. Display, PCIe tunnelling and resume remain board/build specific.
Wi-Fi / Bluetooth
🔵 Wi-Fi board path; 🔵 Bluetooth board path
Broadcom recovery linux #7, AWDL linux #24, J416C recovery linux #167, recovery teardown linux #186 and failed-reset handling linux #192 are merged. Firmware, userspace and named-board test limits remain; this does not qualify every wireless function.
Keyboard / touchpad
🔵 Built-in input path
SPI HID or dockchannel HID descriptions and Apple input drivers are present. Basic input and trackpad haptic feedback are distinct. On J316S, merged linux #210 binds the SPI trackpad's haptic actuator without the old workqueue-name warning (no motor playback was requested).
Ethernet / SD / PCIe expansion
⚪ Per-device qualification
PCIe host support is configured. Qualify fitted controllers, adapters and link speeds independently; do not copy support from a sibling board.
SEP / Touch ID
🔵 Integrated driver and board nodes; 🟠 board-specific acceptance
SEP integration is present through merged linux #42. The pinned tree has T8103 and T6000 SEP profiles (T6001 uses the T6000 one) and enables the Mesa sensor on all five boards; the J293, J314S, J314C and J316C nodes from the feat/sep line reached aurora-wip on October 12 through direct merge 45da41c0cd1b. linux #69 and linux #152 themselves are merged only into feat/sep. Merged linux #303, linux #325 and linux #326 are J700 SEP fixes (#325 and #326 state that M1/M2 are unaffected). Merged tools linux #329 and linux #330 label /dev/sep-bio for SELinux and record that cold-boot keybag creation on T600x rewrites one existing xART session record, so macOS Touch ID afterwards is unverified on these Macs. Named sensor, firmware and tested-kernel limits still apply; downstream iconidentify/aurora-linux fixes are separate from this snapshot.
🔋 Power and complete-system readiness
Feature
Aurora status
Evidence / boundary
Battery / charging / thermals
🔵 Driver foundation
MACSMC power and thermal / hwmon options are configured. Charge behaviour, runtime and battery-health reporting need a board test.
Suspend / resume
🟠 Board-specific qualification
CPU idle and shutdown drivers do not prove a complete suspend / resume cycle. Only the exact boards and development builds named below have cited runtime results. pm_test runs on J316S (#327) and on the T6000 reference Mac (open #332), 3/3 with no DART faults, stop short of a full s2idle cycle.
Installer / complete system
⚪ Release qualification unverified
This is a public kernel source and evidence audit, not a fresh installation or end-to-end hardware test. Record installer, boot chain, kernel, Mesa and firmware revisions together.
🧪 Aurora hardware reports and development branches
SPI mode 2 enrolment and matching after reboot are reported. This is development-branch evidence. The J293 Mesa node (SPI mode 2) is now in pinned aurora-wip; the result has not been repeated there.
October 2 report: stage-0 sensor refusal recovered on first verify; later boots matched both fingers, including after 22-second s2idle. Sequence-counter failure remains untested on that head; re-touch delay remains under investigation. A later report on contributor release 11.32 adds deletion persistence across reboot, re-enrolment and verification after s2idle; those firmware-selected keystore and deletion fixes are not assumed present in pinned aurora-wip. J316S does not inherit the result.
Final 7.1.12-tbpr8-usb2fix2 build: TS4 USB2 first-session attach 3/3, keyboard / mouse and 3840×2160 at 120 Hz. TS4 s2idle and Ethernet recovery reported; not every dock / role swap was requalified.
October 2 LG report: 3840×2160 at 60 Hz, replug and 22-second s2idle worked on Thunderbolt code matching 99a554596d0a, with local PCIe-C and DP-audio patches. A later report on custom/sep@0cde04307749 drove a Dell U4025QW at 5120×2160@60 with USB3 on all three ports; resume recovered by dropping and re-enumerating the router (5.8–7.3 s), not by preserved tunnels. LG UltraFine 5120×2880@60 worked with downstream iconidentify/aurora-linux#22. None of these is a clean-current-head or every-dock pass.
Keep the earlier J293 binding and J316C smoke/reboot observations tied to their original build. #155 now reports successful T6001 module inference and T6021 in-tree inference, without board IDs; the later J293 enabled-DT test is separate; it does not qualify the current candidate on every board. These are newer, distinct experiments.
J314C / J316C
M1 Max Touch ID wiring
🔵 Board nodes in pinned aurora-wip (from linux #69's line)
The T6001 profile and board sensor wiring added October 2 now reach pinned aurora-wip, but have not been run on either board; the J314C DT notes that its own platform device tree was not checked. Follow-up.
11.26-rc1 plus fixes, own enabled T8103 DT; no DKMS or overlays. 20 initial + 500 stability + 80 concurrent H13 add jobs were bit-exact; counters matched 600 jobs with no new kernel faults. Device remained runtime-active after work; idle-power/autosuspend is unresolved. Whole models and current-head regression are not established by this add test.
Reference 16-inch M1 Pro. PR heads on aurora-wip with the Mac's Fedora-Asahi-based configuration, each booted once before merge. Both DCPs and DCP audio bind; 3456x2160@120 with 5/5 swaps; camera at 29.99 fps; five non-silent microphone captures; vkcube, prime-test, Wi-Fi and Bluetooth work; 0 DART faults and 0 WARN. No suspend in these runs, and none is an installed-release test.
October 16 one-shot boots with the Aurora DTB. Without USB4_APPLE_SOC, all 4 tps6598x controllers bind, the Type-C ports continuing without their router after about 15 s, no devices stay deferred, and the charger partner, AC and PD source come online. With it, 3 routers and 3 switches probe and the ports bind at once. Both: pm_test ×3 with 0 DART faults; Wi-Fi, Bluetooth, NVMe, GPU and audio OK.
The PR names only the SoC; #327 identifies the same lab's M1 Pro as J316S. Merged into aurora-wipa837bd5 with USB4_APPLE_SOC=m: 10/10 Type-C cycles with partner, AC and PD back, a refused DR swap plus rebind without WARN, pm_test=platform 3/3, KUnit 78/78. No USB devices, external displays or cable orientations were attached.
NixOS 26.05, feat/sep120e030 (Linux 7.1.9), OS firmware 13.5, Asahi m1n1 1.6.0 with Aurora's UUID forwarding backported, libfprint 1.94.10 with Aurora's patch, fprintd 1.94.5. One finger: enrol, verify-match, verification without re-enrolment on 2 later boots, wrong-finger rejection, verify after one s2idle cycle, GDM unlock, and trusted-key seal/unseal across reboot. 2 boots failed SBIO communication init (EIO, fprintd NoSuchDevice) for an undetermined reason; J700-only #325 does not cover this path. Separately, merged linux #329's SELinux module let fprintd find the reference M1 Pro's sensor under Fedora's enforcing policy (kernel not stated). Not a pinned-aurora-wip result.
With m1n1 built from the m1n1-aurora base 06a4601 plus #33, all three routes were enabled and two USB-C displays came up together as dispext0,0 and dispext1,0; single and simultaneous replugs and monitor power cycles worked. With current m1n1-aurora 1.6.1.aurora1-3 (no #33) and the added drm/apple commit, dcpext0 binds with its routes disabled, the panel and HDMI work, and Type-C DP stays on dcpext1. The two PRs are to merge together; other M1 Pro/Max boards are untested.
With the crossbar driver in the initramfs, an empty or charger-only port could take the only Type-C pipeline and leave the monitor dark in about half of the author's boots. Running an earlier version since October 13, the takeover fired in 3 of the last 12 boots and the monitor came up; other boots were unchanged.
PR snapshot: October 16, 2026. Current states and destinations are recorded below. SEP is integrated through #42, while newer downstream Touch ID fixes retain their contributor-kernel scope.
Board attribution: some maintainer PRs name only "M1 Pro" or the SoC. Their results are listed under J316S because linux #327 identifies that test machine as J316S. Treat that attribution as inferred; sibling M1 Pro/Max boards do not inherit it.
What changed · October 16, 2026
J316S: maintainer one-shot boots of merged PRs report display, camera, microphones, GPU and haptics. Merged linux #327 was hardware-tested on J316S, and open linux #332 adds M1/M2 Type-C regression fixes tested on a T6000 reference Mac.
J316S Touch ID: a contributor report on feat/sep 120e030e (NixOS) passes enrolment, reboot, s2idle and GDM unlock, with intermittent SBIO initialization failures.
Board nodes: the J293, J314S, J314C and J316C Mesa/SEP nodes now reach pinned aurora-wip through direct merge 45da41c0cd1b; J314C and J316C remain untested. Merged tools linux #329 and linux #330 add the Fedora SELinux and PAM steps.
J314S: open linux #316 with m1n1 #33 runs two USB-C displays at once; open linux #302 recovers a dark Type-C monitor at boot.
Open and draft PRs are development work; a merged change alone does not qualify every configuration above.
🧪 Add a reproducible hardware report
Reply here with one feature or failure per report. Identify the exact row from the configurations table.
Board ID:
SoC ID and chip variant:
Model / screen size / configuration:
Feature or SoC block:
Kernel repository / branch / commit:
m1n1 / U-Boot / Mesa commits, where relevant:
Firmware version:
Steps to reproduce:
Expected result:
Observed result and repeat count:
Public log or artifact URL:
Artifact SHA-256 and command to repeat the check:
Known limits / recovery steps:
Repository admins can update this opening post through ⋯ → Edit. Record the tested board next to each result; keep implementation status separate from unverified hardware results on other boards.
Keep this product generation together. Discuss shared silicon changes here and link affected sibling products through the hardware directory. A result on one board does not change another board’s status.
Audit baseline:f53454ba0da1; public source and PR reports checked October 16, 2026. No new physical test was performed for this update. Working-tree integration does not imply an aurora-stable release.
Open development PR; hardware reports retain their tested revisions · 9b4dcc65874e
PR state, source integration and hardware qualification are separate. A closed PR is not necessarily merged. Public reports describe their original test kernels, including contributor branches. Repository administrators can edit this opening post.
hardwareBoard-specific hardware evidence and SoC indexessoc:T8103Hardware discussions for T8103 (M1)soc:T6000Hardware discussions for T6000 (M1 Pro)soc:T6001Hardware discussions for T6001 (M1 Max)
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
MacBook Pro · M1 family
🧭 Hardware directory › M1 category › MacBook Pro
5 board configurations · one shared discussion · Aurora Linux assessment
Broad kernel integration is present: Aurora's working tree includes this product's core platform, NVMe, GPU, DCP display, USB, wireless and audio paths. Board-specific exceptions and Aurora's newer development work are listed below; this assessment is not a blanket pass for every port, firmware version or installation.
Refreshed October 16, 2026. Baseline:
aurora-wipatf53454ba0da1. Open PR andfeat/sepresults are identified separately. These statuses use Aurora's public source and contributor reports with their actual tested kernels identified. The baseline source and every linked PR state were rechecked; no new physical test was performed for this update.Configurations
J293T8103J314ST6000J316ST6000J314CT6001J316CT6001Evidence key · Aurora source and Aurora hardware reports
A report from another board is not a pass for this board. An open PR may work on hardware without being integrated into
aurora-wip. A driver being enabled does not by itself establish firmware availability, userspace integration or a complete usable installation.🧩 Core platform
CONFIG_NVME_APPLE=m.🎨 Graphics, audio and media
CONFIG_DRM_ASAHI=m. On J316S,vkcubeandprime-test(6 × 200) passed on a one-shotc679c8a7kernel with merged linux #240. Mesa, firmware and application / conformance results must be recorded separately.CONFIG_DRM_APPLE=m. Merged linux #224 (legacy reply records) and linux #225 (released register ranges) fix the pre-H17P DCP paths that M1/M2 firmware uses; on J316S (DCP firmware 13.5) both DCPs bind and the panel runs 3456x2160@120 with 5/5 swaps and working backlight (no external monitor attached). Merged linux #313 (external-display resume, DCP message hold in s2idle) was qualified on J700 only. J314S Type-C display routing work is open (reports below). Connector routing, refresh modes and hotplug remain board- and firmware-specific.CONFIG_SND_SOC_APPLE_AOP_AUDIO=m. J316S one-shot boots of merged linux #232 and linux #237 recorded five non-silent built-in microphone captures each. Record actual capture quality and channel behaviour per board.CONFIG_VIDEO_APPLE_ISP=m. Merged linux #220 holds 30 fps in low light by default: on J316S, 3 × 150 frames at 29.99 fps in a dark room (15.00 fps on the stock kernel), andexposure_dynamic_framerate=1restores the old behaviour. One-shots of merged linux #267 and linux #268 opened, streamed and reopened the J316S camera. Other boards need their own runs.CONFIG_VIDEO_APPLE_AVD=m. Decoder fixes in #45 are merged intoaurora-wip; codec / stream coverage and application integration are not a general pass.asahi.configselectsCONFIG_DRM_ACCEL=yandCONFIG_DRM_ACCEL_ANE=m(direct merge45da41c0cd1b); the arm64 defconfig alone does not, and a configured driver is not a per-board runtime test. J293 and J314S each completed 600/600 bit-exact add calls over 30 autosuspend/resume cycles, four concurrent 20-call runs and a device-test suspend cycle on contributor kernel11.31/custom/sep@87e165cc(report). This is not a full-system suspend test or a direct power measurement. A report records passing in-tree smoke rows for M1, M1 Pro and M2 Pro; chip enablement does not qualify every product.🔌 I/O and security
asahi.configselectsCONFIG_USB4=mandCONFIG_USB4_APPLE_SOC=m. linux #46 and linux #51 closed without merge on October 11; #8 had already carried their dual-stream and controller-teardown lock changes, as it carried linux #64. Merged linux #327 lets a CD321x port register without its USB4 router once that router fails to bind (builds withoutUSB4_APPLE_SOC); it was tested on J316S and J413 only. J316S results for #327, T6000 reference-Mac results for open linux #332, and J314S two-display and HPD work in open linux #316, m1n1 #33 and linux #302, are in the reports below. A default-on T600x/T602x PCIe-C cold-init path (pcie_apple.tunnel_kernel_init) reached the pinned tree on October 12 through direct merge45da41c0cd1b; no M1 Pro/Max tunnel device was retested on it. Display, PCIe tunnelling and resume remain board/build specific.feat/sepline reachedaurora-wipon October 12 through direct merge45da41c0cd1b. linux #69 and linux #152 themselves are merged only intofeat/sep. Merged linux #303, linux #325 and linux #326 are J700 SEP fixes (#325 and #326 state that M1/M2 are unaffected). Merged tools linux #329 and linux #330 label/dev/sep-biofor SELinux and record that cold-boot keybag creation on T600x rewrites one existing xART session record, so macOS Touch ID afterwards is unverified on these Macs. Named sensor, firmware and tested-kernel limits still apply; downstreamiconidentify/aurora-linuxfixes are separate from this snapshot.🔋 Power and complete-system readiness
pm_testruns on J316S (#327) and on the T6000 reference Mac (open #332), 3/3 with no DART faults, stop short of a full s2idle cycle.🧪 Aurora hardware reports and development branches
feat/sepaurora-wip; the result has not been repeated there.aurora-wip. J316S does not inherit the result.aurora-wip99a554596d0a, with local PCIe-C and DP-audio patches. A later report oncustom/sep@0cde04307749drove a Dell U4025QW at 5120×2160@60 with USB3 on all three ports; resume recovered by dropping and re-enumerating the router (5.8–7.3 s), not by preserved tunnels. LG UltraFine 5120×2880@60 worked with downstreamiconidentify/aurora-linux#22. None of these is a clean-current-head or every-dock pass.aurora-wip(from linux #69's line)aurora-wip, but have not been run on either board; the J314C DT notes that its own platform device tree was not checked. Follow-up.11.26-rc1plus fixes, own enabled T8103 DT; no DKMS or overlays. 20 initial + 500 stability + 80 concurrent H13 add jobs were bit-exact; counters matched 600 jobs with no new kernel faults. Device remained runtime-active after work; idle-power/autosuspend is unresolved. Whole models and current-head regression are not established by this add test.aurora-wipwith the Mac's Fedora-Asahi-based configuration, each booted once before merge. Both DCPs and DCP audio bind; 3456x2160@120 with 5/5 swaps; camera at 29.99 fps; five non-silent microphone captures;vkcube,prime-test, Wi-Fi and Bluetooth work; 0 DART faults and 0 WARN. No suspend in these runs, and none is an installed-release test.USB4_APPLE_SOC, all 4 tps6598x controllers bind, the Type-C ports continuing without their router after about 15 s, no devices stay deferred, and the charger partner, AC and PD source come online. With it, 3 routers and 3 switches probe and the ports bind at once. Both:pm_test×3 with 0 DART faults; Wi-Fi, Bluetooth, NVMe, GPU and audio OK.aurora-wipa837bd5 withUSB4_APPLE_SOC=m: 10/10 Type-C cycles with partner, AC and PD back, a refused DR swap plus rebind without WARN,pm_test=platform3/3, KUnit 78/78. No USB devices, external displays or cable orientations were attached.feat/sepfeat/sep120e030 (Linux 7.1.9), OS firmware 13.5, Asahi m1n1 1.6.0 with Aurora's UUID forwarding backported, libfprint 1.94.10 with Aurora's patch, fprintd 1.94.5. One finger: enrol,verify-match, verification without re-enrolment on 2 later boots, wrong-finger rejection, verify after one s2idle cycle, GDM unlock, and trusted-key seal/unseal across reboot. 2 boots failed SBIO communication init (EIO, fprintdNoSuchDevice) for an undetermined reason; J700-only #325 does not cover this path. Separately, merged linux #329's SELinux module let fprintd find the reference M1 Pro's sensor under Fedora's enforcing policy (kernel not stated). Not a pinned-aurora-wipresult.dcpext0on Type-Cdispext0,0anddispext1,0; single and simultaneous replugs and monitor power cycles worked. With current m1n1-aurora 1.6.1.aurora1-3 (no #33) and the addeddrm/applecommit,dcpext0binds with its routes disabled, the panel and HDMI work, and Type-C DP stays ondcpext1. The two PRs are to merge together; other M1 Pro/Max boards are untested.PR snapshot: October 16, 2026. Current states and destinations are recorded below. SEP is integrated through #42, while newer downstream Touch ID fixes retain their contributor-kernel scope.
Board attribution: some maintainer PRs name only "M1 Pro" or the SoC. Their results are listed under J316S because linux #327 identifies that test machine as J316S. Treat that attribution as inferred; sibling M1 Pro/Max boards do not inherit it.
What changed · October 16, 2026
feat/sep120e030e (NixOS) passes enrolment, reboot, s2idle and GDM unlock, with intermittent SBIO initialization failures.aurora-wipthrough direct merge45da41c0cd1b; J314C and J316C remain untested. Merged tools linux #329 and linux #330 add the Fedora SELinux and PAM steps.asahi.confignow selects the ANE driver; a T600x/T602x PCIe-C cold-init path arrived in the same direct merge; legacy DCP fixes linux #224 and linux #225 merged; linux #46 and linux #51 closed after Thunderbolt: M1/M2 Pro display, M1 PCIe and resume recovery #8 carried their changes.Pinned Aurora evidence
Working-tree configuration · Arm64 base configuration · Board build targets · GPU device matches · DCP driver · ISP driver · AVD decoder · Thunderbolt driver · Thunderbolt configuration · SEP driver
Public references
aurora-wipatf53454ba0da1.Board-specific identity and device-tree references
J293: Device tree.J314S: Device tree.J316S: Device tree.J314C: Device tree.J316C: Device tree.Related board work
J293: #36 (merged into the PR's target branch; see branch-qualified evidence above) — arm64: dts: apple: t8103-j293: enable the Mesa fingerprint sensorJ314S: #62 (closed without merge; superseded by soc: apple: sep: Touch ID after reboot on M2 Max, M1 Pro and M1 (supersedes all open SEP PRs) #69) — soc: apple: sep + dts: Touch ID on the 14" M1 Pro (J314s)J314S: #316 with m1n1 #33 (open) — t600x: let dcpext0 drive Type-C displays; #302 (open) — Type-C port with HPD takes over a pipelineJ316S: #327 (merged intoaurora-wip) — tipd: don't leave M1/M2 Type-C ports deferred; #332 (open) — M1/M2 Type-C regression fixesOpen and draft PRs are development work; a merged change alone does not qualify every configuration above.
🧪 Add a reproducible hardware report
Reply here with one feature or failure per report. Identify the exact row from the configurations table.
Repository admins can update this opening post through ⋯ → Edit. Record the tested board next to each result; keep implementation status separate from unverified hardware results on other boards.
Keep this product generation together. Discuss shared silicon changes here and link affected sibling products through the hardware directory. A result on one board does not change another board’s status.
Audit baseline: f53454ba0da1; public source and PR reports checked October 16, 2026. No new physical test was performed for this update. Working-tree integration does not imply an
aurora-stablerelease.PR state and integration audit · October 16, 2026
aurora-wipaurora-wiphistory ·e6c5b30d0ac0aurora-wipaurora-wiphistory ·b37df4bdd552aurora-wipaurora-wiphistory ·6c00439340a7feat/sepaurora-wiphistory ·b5eae3734e40aurora-wipaurora-wiphistory ·c9a55efdff8faurora-wipaurora-wiphistory ·510ac224fe96review/pr14-base2530a2c3a694fix/j414s-dual-dock-dpaurora-wiphistory ·9dc79fb25c92fix/j414s-dual-dock-dp8153565e7166feat/sep34ddd3887bbdaurora-wip5d524a478c92aurora-wipaurora-wiphistory ·2e1656f93c27feat/sepfeat/sep; SEP integration also landed through #42. Later downstream fixes are not implied ·2cf2b0a22229feat/sepfeat/sep; SEP integration also landed through #42. Later downstream fixes are not implied ·120e030eac9faurora-wipaurora-wiphistory ·9e9e1b83b71eaurora-wipaurora-wiphistory ·883e58b33d57fix/j414s-dual-dock-dpaurora-wiphistory ·9e93cac3ac71aurora-wipaurora-wiphistory ·0fc050327e0caurora-wipaurora-wiphistory ·212a52e404dbaurora-wipaurora-wiphistory ·49d3482292fdaurora-wipaurora-wiphistory ·b1bd8bd99cf0fix/j414s-dual-dock-dpaurora-wiphistory ·2530a2c3a694aurora-wipaurora-wiphistory ·f9ee7e25bd2daurora-wipaurora-wiphistory ·86bfea0aea65aurora-wipaurora-wiphistory ·3fecb279810daurora-wipaurora-wiphistory ·0a0216f71a14aurora-wipaurora-wiphistory ·98818cea22eeaurora-wipaurora-wiphistory ·1702229de78faurora-wipaurora-wiphistory ·c679c8a75a89aurora-wipaurora-wiphistory ·fffde617a6b3aurora-wipaurora-wiphistory ·cff65c17da01aurora-wipaurora-wiphistory ·3b2bd35a8591aurora-wip53397b77038eaurora-wipaurora-wiphistory ·a490adab6fc3aurora-wipaurora-wiphistory ·5cf6579fa592aurora-wip2127f56e5b5caurora-wipaurora-wiphistory ·97075ac83279aurora-wipaurora-wiphistory ·99b5f912426eaurora-wipaurora-wiphistory ·a6cfa4dd59a5aurora-wipaurora-wiphistory ·8b66c7bc0ec6aurora-wipaurora-wiphistory ·a837bd5f9a21aurora-wip2757f43e143eaurora-wip9b4dcc65874ePR state, source integration and hardware qualification are separate. A closed PR is not necessarily merged. Public reports describe their original test kernels, including contributor branches. Repository administrators can edit this opening post.
All reactions