As the email message says, this is due to a bug in the Asahi M1N1 hypervisor/bootloader (from the Asahi Linux project) which OpenBSD piggybacks on.
https://social.treehouse.systems/@AsahiLinux/112454079096607...
https://social.treehouse.systems/@AsahiLinux/112454079096607...
Asahi Linux already depends on a stable firmware interface provided by a fixed version of macOS, so macOS updates generally do not affect it. However, macOS updates can update system-wide firmware in ways that are backwards-compatible. In this case, one such update triggered a bug in our code.
This is no different from updating firmware on any other machine. It is always possible that a benign, backwards-compatible firmware update will trigger a latent bug by chance. This has only happened twice so far, since the project started, and both times we quickly fixed it.
Apple's platform/system design requires that they maintain backwards compatibility, in order to be able to run older versions of macOS. Therefore, they cannot break Asahi Linux with updates on purpose, only due to bugs.
... If you don't want to trust Apple software and their updates and just want to use Linux, then nobody forces you to. macOS is only used for installation and certain update/recovery scenarios, it's not part of the Linux boot process in any way and It's not going to magically update itself.https://asahilinux.org/about/#who-is-working-on-asahi-linux
Booting OpenBSD on a Apple silicon Mac requires:
• macOS + m1n1 stage 1 (from the Asahi Linux project)
• m1n1 stage 2 + u-boot (from OpenBSD)
• OpenBSD's EFI bootloader (BOOTAA64.EFI).
A recent macOS update exposed a bug in m1n1 which has been fixed and pushed out by both the Asahi Linux team, and now also OpenBSD.