Boot loop after upgrade but also after fresh install AsahiFedora 44

Our Neighbors Asahi Linux Ask Asahi
1

Dear experts,
I have been happily using Asahi linux since its start, alongside MacOs (currently Tahoe) on my 2020 M1 MacBook Air. When I upgraded to AsahiFedora 43, I ended up in a boot loop: apple logo → asahi logi → fedora logo → countdown menu (fedora 43, 42, UEFI) → black screen with ‘Fedora’ in lower part, and white circle, which freezes after some seconds, nothing happens. After approx. 20 secs there is a spontaneous reboot: apple logo, asahi logo, etcetera. Fortunately I could fall back to AsahiFedora 42 in the countdown menu.
Not to be left behind, I decided to remove all linux partitions from my MacBook, very carefully following the asahi partitioning cheatsheet; and do a fresh install of AsahiFedora 44 (KDE). Everything went smoothly. But to my surprise, after the final reboot, the old problem is back!
apple logo → asahi logo → Fedora logo → countdown menu (offering fedora 44 and UEFI) → white circle that freezes, and spontaneous reboot aftyer which everything repeats. (And no longer can I revert to Fedora 42 from the countdown menu).

Could it be that AsahiFedora 43 and 44 are not compatible with first generation M1 macbooks?
Thank you in advance!

2

additional info:
Yesterday I suddenly succesfully booted into AsahiFedora-44. The interactive setup proces of KDEplasma started succesfully. However, this was a one time incident: after rebooting, the boot-cycle, including the freezing of the spinning white circle, was back. But now there is an new error message during the rebooting:

error: ../../grub-core/commands/loadenv.h:read_envblk_file:51:invalid environment block.

I hope this may help in diagnosing my problem with AsahiLinux on macbook M1 (2020) .
Thanks for any suggestions!

3

I had a boot issue as well. I upgraded my M1 mac mini to Fedora Server 44 Linux 7.1.13-402.asahi.fc44.aarch64+16k today. It reboots fine now.

I am not sure if you have the same problem that I had. Might be worth a try.

4

Dear John-Mark,

Thank you for your advice.
I removed all linux partitions from my M1 airbook (2020) and did a fresh install of the asahi-fedora 44 server. Alas: just like the GUI version the infinite boot-loop occurred again.

During the boot process, again I noticed a /grub-core/commands error: badenv.h.;read_envblk_file:51:invalid environment block.

And just like the bootlooping GUI 43 and 44 versions: suddenly, at the Nth loop, the boot process went ahead and I could setup the server environment. But at the next reboot, the boot-loop was back again.

On other fora I find several people reporting that fresh Asahi-Fedora-linux installs boot-loop on M1 machines. Could it be that the Asahi experts consider M1 too old to support?

Again, thank you for your message.
Hans.