AsahiLocker 2.0.2 — m1n1 stage 2 first; stage 1 only with care
This corrects 2.0.1. Nothing changes in how a volume is encrypted, in the
KDF, or in any volume an earlier release made.
What 2.0.1 left out
To get U-Boot to see a live USB on an M3 (#4), 2.0.1 suggested upgrading
m1n1 stage 1 with the Asahi installer's option m. It gave no warning.
That upgrade worked on the M3 Air in #4. On an M2 Max with system firmware
27 (macOS 27) it left the Asahi install unbootable. The installer's
recoveryOS approval step showed a blue screen saying it was not the correct
recoveryOS. It asked for a user name and password, rebooted, and showed the
same screen again. It failed four times in a row. The upgrade does not
delete the old stage 1; it writes the new one beside it, and pointing the
boot back at the old one made the install bootable again. The recovery
procedure is in docs/LIVE-USB.md, under If the stage 1 upgrade loops.
The advice now, safest first
- Stage 2:
sudo dnf upgrade m1n1, then reboot. It is an ordinary
package update; Fedora 44 has had 1.9.9 since October 2026. - Stage 1: only after reading the warning in
docs/LIVE-USB.md, and
with a way back. Check your system firmware first:tr -d '\0' < /proc/device-tree/chosen/asahi,system-fw-version; echo
- Or skip the USB: the second-install route (
docs/SECOND-INSTALL.md)
needs none.
luks-deploy.sh's M3 warning says the same and points to the docs before
anyone tries stage 1.