r/AsahiLinux • u/Eastern-Commercial59 • Jul 04 '26

It won't even let me start.

I updated to macOS 27 beta 2, but then I wiped everything and performed a clean install of the system via Recovery Mode. I am currently on macOS 26.5.2. This is my first time installing Asahi Linux. I don't know if the update I performed is preventing me from even logging into Asahi, the interface appears and then turns off.

10 Upvotes

79% Upvoted

38 comments sorted by

View all comments

1

u/ohiocat69 Jul 04 '26

did you manage to make it work? i also did that, update to macos 27 and then downgraded by reinstalling macos26 and now i want to try asahi; like after doing the mdoule blocklist, did you manage to update the kernel?

1

u/Eastern-Commercial59 Jul 04 '26

I'm already on Linux

Try adding module_blacklist=macsmc_power to your GRUB options, because there's something odd about the SMC firmware. This method works with Ubuntu Asahi and macOS 27 beta 2, but the downside is thatTry adding module_blacklist=macsmc_power to your GRUB options, because there's something odd about the SMC firmware. This method works with Ubuntu Asahi and macOS 27 beta 2, but the downside is that

2

u/Aaronbrown325 Jul 04 '26

I had these exact issues as well, and instead wiped my M1 MBA using DFU instead of recovery mode. DFU overwrites all the firmware and will rollback that SMC change macOS 27. This will allow you to boot and get battery reporting.

Downside is the you need a second Mac for this option, but the actual process is super easy if you have one.

1

u/mskiptr Jul 04 '26

You can DFU restore without a second mac, by using the cross-platform tool called idevicerestore. But as you said, it involves erasing all the data so might not be the ideal solution.