Repository navigation
Description
Summary
On a MacBook Pro 13-inch (M1, 2020), J293/T8103, the SEP key store opens and the sensor binds in SPI mode 2 at 8 MHz, but initial sensor authentication fails at SESSION_COMMIT with status 0xfffffffe. Subsequent registration retries fail with 0x16, apart from one serial-read timeout. Omarchy's activation service ends with sensor_attach not-ready. No fingerprints are enrolled.
Non-default configuration: this machine already has xart_guard=0. Omarchy's installed eligibility script explicitly returns unsupported:m1-family; this is not presented as a stock supported setup. The origin of the existing override and initial provisioning history are unknown. No new guard bypass, enrollment, keybag reset, driver reload, or firmware change was performed during this investigation.
Hardware and software
| Item | Observed value |
|---|---|
| Model | Apple MacBook Pro (13-inch, M1, 2020) |
| Device-tree compatible | apple,j293 apple,t8103 apple,arm-platform |
| Distribution | Arch Linux ARM, Omarchy 4.5.0-3 |
| Kernel | 7.2.11-14-1-ARCH, SMP PREEMPT_DYNAMIC, built 2026-11-01 |
| Kernel package | linux-aurora 7.2.11.aurora14-1 |
| m1n1 package | m1n1-aurora 1.6.1.aurora22-1 |
| U-Boot package | uboot-aurora 2026.07.aurora6-1 |
| Platform integration | omarchy-mac 0.2.3-2 |
| libfprint | libfprint-git 1:1.94.100.r10.g6f9479c-5 |
| fprintd | 1.94.5-2 |
| SEP driver | In-tree apple-sep.ko, vermagic 7.2.11-14-1-ARCH SMP preempt mod_unload aarch64 |
| Driver diagnostic ABI | 2 |
The exact source commit of the installed kernel was not independently established from its package metadata. pacman -Qkk reports no altered package files for omarchy-mac, libfprint-git, and m1n1-aurora; this does not validate the separately deployed boot image.
Firmware and bootloader versions from the running device tree
asahi,os-fw-version: 13.5
asahi,system-fw-version: 26.5.2
asahi,iboot1-version: mBoot-18000.121.3
asahi,iboot2-version: iBoot-8422.141.2
asahi,m1n1-stage1-version: v1.6.1-dirty
asahi,m1n1-stage2-version: bc79acc4-dirty
These are reported boot firmware properties, not an independently checked macOS installation version. The dirty suffixes are included verbatim; their origin is unknown.
The driver logs that it uses /chosen/apfs-preboot-uuid; the identifier itself is omitted. The kernel command line contains user4k=on, with no explicit apple_sep.* options. Root/partition UUIDs are omitted.
Existing module configuration and sensor description
options apple_sep xart_writes=1 provision_keybag=1 xart_guard=0
- Sensor node:
/soc/spi@235108000/fingerprint@0 - Compatible:
apple,mesa-fingerprint - Status:
okay - Firmware name:
apple/mesacal-j293.bin - File exists at
/usr/lib/firmware/updates/apple/mesacal-j293.bin, 64574 bytes; calibration contents were not independently validated. - Kernel reports 20 ns CS timing, SPI mode 2, 8 MHz.
- An existing keybag is present. The diagnostic interface reports
keybag: present, and fprintd lists no enrolled fingerprints.
Observed failure sequence
This was inspected on one running boot, whose activation failure is recorded on 2026-11-05. Frequency across boots and recovery by reboot have not been tested. The driver reports boot: cold; the preceding physical power/reboot sequence is unknown.
The boot-time platform units load the driver and attempt activation. Read-only inspection used journalctl, the driver's diagnostic attributes, systemctl status, and fprintd-list. The diagnosis does not rely on a new enrollment or verification attempt.
Expected: the sensor completes authenticated initialization and becomes available for enrollment.
Actual: session commit fails, both the initial and late retry ladders fail, and activation remains not-ready.
Kernel log excerpts
Exact message text with monotonic timestamps retained; hostname and repetitive endpoint-discovery lines omitted.
[ 17.720851] apple-mesa spi2.0: sep sensor: CS timing 20 ns programmed in hardware
[ 17.721196] apple-mesa spi2.0: sep sensor: power line from the device node, driven low
[ 17.721408] apple-mesa spi2.0: sep sensor: bound, 8000000 Hz, mode 2 (CPOL=1 CPHA=0)
[ 17.724977] apple_sep 242400000.sep: sbio: communication initialization accepted
[ 17.750036] apple_sep 242400000.sep: sks: LOAD_KEYBAG reply mailbox status 0, response size 92, copied 92 bytes
[ 17.807112] apple_sep 242400000.sep: sbio: identity count 0 before the cold-match preparation
[ 18.522075] apple_sep 242400000.sep: scrd: cold-match credential established true
[ 18.522227] apple_sep 242400000.sep: sbio: pre-restore special unlock true, SCRD match context true
[ 18.523006] apple_sep 242400000.sep: sbio: restore master catacomb state Some(1) outcome NoStoredFile
[ 18.523106] apple_sep 242400000.sep: sbio: restore owner catacomb state None outcome Failed
[ 18.523176] apple_sep 242400000.sep: sbio: restore user catacomb state None outcome Failed
[ 18.523243] apple_sep 242400000.sep: sbio: restore lockout outcome NoStoredFile
[ 18.523384] apple_sep 242400000.sep: sbio: cold-match preparation true, component restore false
[ 18.523455] apple_sep 242400000.sep: sbio: identity count 0 after Catacomb restore with sensor registered
[ 18.523520] apple_sep 242400000.sep: matching unavailable this boot: cold-match preparation, SCRD credential, Catacomb restore, or identity proof did not complete; template state is unproven
[ 18.543045] apple_sep 242400000.sep: sbio: registering sensor at bring-up stage 0
[ 18.543219] apple_sep 242400000.sep: sbio: identity count 0 after sensor serial registration
[ 18.551011] apple_sep 242400000.sep: sensor: SESSION_COMMIT refused with status 0xfffffffe
[ 18.551166] apple_sep 242400000.sep: sensor: re-read 0 frame(s) the sensor still offered after a garbled read, discarded 1 stale frame(s)
[ 18.551242] apple_sep 242400000.sep: sensor: SESSION_COMMIT failed 27 ms after power-on; sensor now state 0 ack 0x60 identifier true holding 0 bytes
[ 18.551316] apple_sep 242400000.sep: sequence counter: session setup failed
[ 18.551383] apple_sep 242400000.sep: sensor patch: sequence counter init failed before the patch fetch
[ 18.551451] apple_sep 242400000.sep: sbio: the sensor did not wake at attach
[ 18.551517] apple_sep 242400000.sep: sensor: attach-time bring-up attempt 1 of 5 failed; starting again in 500 ms
[ 19.092051] apple_sep 242400000.sep: sbio: registering sensor at bring-up stage 2
[ 19.092220] apple_sep 242400000.sep: sbio: identity count 0 before CLEAR_STATE for sensor re-registration
[ 19.092295] apple_sep 242400000.sep: sbio: identity count 0 after CLEAR_STATE for sensor re-registration
[ 19.100019] apple_sep 242400000.sep: sensor: REGISTER_SERIAL refused with status 0x16
[ 19.100180] apple_sep 242400000.sep: sensor: REGISTER_SERIAL failed 28 ms after power-on; sensor now state 0 ack 0x60 identifier true holding 0 bytes
[ 20.167045] apple_sep 242400000.sep: sbio: registering sensor at bring-up stage 0
[ 21.411058] apple_sep 242400000.sep: sensor: serial read failed: ETIMEDOUT
[ 21.411913] apple_sep 242400000.sep: sensor: serial read failed 1266 ms after power-on; sensor now state 0 ack 0x60 identifier true holding 0 bytes
[ 23.508059] apple_sep 242400000.sep: sbio: registering sensor at bring-up stage 1
[ 23.508932] apple_sep 242400000.sep: sensor: REGISTER_SERIAL refused with status 0x16
[ 27.691053] apple_sep 242400000.sep: sbio: registering sensor at bring-up stage 0
[ 27.841048] apple_sep 242400000.sep: sensor: REGISTER_SERIAL refused with status 0x16
[ 27.843020] apple_sep 242400000.sep: sbio: attach-time sensor bring-up did not complete; matching unavailable; retrying in 10 s
[ 37.856060] apple_sep 242400000.sep: sensor: retrying the attach-time bring-up after the ready phase
[ 37.879027] apple_sep 242400000.sep: sensor: REGISTER_SERIAL refused with status 0x16
[ 38.423029] apple_sep 242400000.sep: sensor: REGISTER_SERIAL refused with status 0x16
[ 39.487032] apple_sep 242400000.sep: sensor: REGISTER_SERIAL refused with status 0x16
[ 41.594025] apple_sep 242400000.sep: sensor: REGISTER_SERIAL refused with status 0x16
[ 45.783006] apple_sep 242400000.sep: sensor: REGISTER_SERIAL refused with status 0x16
[ 45.783322] apple_sep 242400000.sep: sensor: authenticated attach incomplete after the late retry; capture unavailable until an enrol or verify brings the sensor up
The garbled-read message is reported alongside session commit; that alone does not establish which transport step caused the rejection.
Driver diagnostics after activation fails
Read from /sys/bus/platform/drivers/apple_sep/242400000.sep/diag/:
abi: 2
attach: attached
boot: cold
endpoints: 12
keybag: present
keystore: open
matching: usable
profile: T8103/J313
protocol: sepos13
restore: unknown
sensor: failed
sensor_attach: not-ready
touchid: not-ready
xart: enabled
xart_guard: 0
xart_guard_list: none
xart_guard_refusals: 0
matching: usable does not indicate a working reader here: the sensor and overall Touch ID attributes remain failed/not-ready.
Activation service:
[ 46.132324] Touch ID is not ready to enrol and match: the sensor did not come online (sensor_attach not-ready)
[ 46.133392] omarchy-mac-touchid-activate.service: Main process exited, code=exited, status=1/FAILURE
Related reports and requested guidance
- M1 Pro SEP: retain unresolved attach and post-resume session failures #42 documents the same
SESSION_COMMIT 0xfffffffefollowed byREGISTER_SERIAL 0x16sequence on J316s. This report adds J293 evidence; a common root cause is not established. - soc: apple: sep: Touch ID after reboot on M2 Max, M1 Pro and M1 (supersedes all open SEP PRs) aurora-silicon/linux#69 reports successful J293 enrollment and matching after reboot, including SPI mode 2. This system already uses mode 2.
- soc: apple: sep: add biometric application key operations aurora-silicon/linux#1004 reports recent successful J293 verification on the separate
feat/sepbranch, but does not provide firmware versions or claim to fix this session failure.
Is this J293 session-authentication failure covered by an existing fix or tracked under #42? Which exact driver revision and firmware combination should be used for a controlled test? Please advise on diagnostics that preserve existing secure state and do not require deleting/reprovisioning keybags or further weakening the xART guard.
No secret key material, calibration contents, partition UUIDs, OS identity UUID, or fingerprint data is included.
Activity
nkabbara commentedon Nov 6, 2026
Follow-up: a normal restart with the same kernel and existing module configuration cleared the initialization failure. After restarting, diagnostics reported sensor=online, sensor_attach=attached, touchid=ready, restore=empty, and activation completed successfully. The earlier SESSION_COMMIT / REGISTER_SERIAL failures did not appear on that boot.
The owner then completed Omarchy fingerprint setup and confirmed enrollment and verification succeeded. fprintd-list now shows right-index-finger; fingerprint PAM configuration is present for sudo, polkit, and the lock screen.
No driver update, firmware change, keybag reset, or guard change was needed for this recovery. The existing xart_guard=0 override remains unchanged. Persistence of this newly enrolled finger across another reboot and long-term reliability have not yet been tested, so this establishes recovery by restart, not a permanent driver fix. Closing at the owner’s request; we can reopen if it recurs.