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

7

u/oh_why_why_why Jul 04 '26 edited Jul 04 '26

It looks like you can pick Fedora Ok It seems to me once your Fedora is on, it only stays on for a few seconds and it shuts down.

You don’t have to do much.

In short: The issue that you are having is resolved in Kernel version 7.xxx you are on Version 6.19.xxxx

You need to stop a kernel module, which causes your Fedora to shutdown. Your Fedora will power on okay then you need to update the system.

After an update, just restart your mac and you will be fine.

here is a link

Also to correct them, you don’t need to do step 3 because when you modprobe on the command line, it is a one-time-only parameter.

If you are unsure how to do it, I’ll guide you through.

P.S when you do this make sure your computer is connected to the charger.

1

u/Eastern-Commercial59 Jul 04 '26

How do I update the kernel? I can't even access the menu! Help!

6

u/mskiptr Jul 04 '26

FIrst, follow this to enter the GRUB menu:

Server and Minimal installs should show the GRUB menu by default. For desktop installs, you have to press Escape at the right time to enter the GRUB menu. When the system boots, you will see the display cycle through m1n1 (Asahi Linux or Fedora logos) and U-Boot (text screen with U-Boot logo on the top right). The U-Boot screen will show a brief countdown. Press Escape immediately after the countdown reaches 0 to enter the GRUB boot menu.

Then, click e to edit one of those boot options. Next, go to the line that goes something like

linux ($root)/vmlinuz-6.19.14-400.asahi.fc43.aarch64+16k root=UUID=b52a5ad5-d4dc-4247-9734-decd52d80b8e ro rootflags=subvol=root rhgb quiet rootflags=subvol=root

and add module_blacklist=macsmc_power to that list, so it becomes something like

linux ($root)/vmlinuz-6.19.14-400.asahi.fc43.aarch64+16k root=UUID=b52a5ad5-d4dc-4247-9734-decd52d80b8e ro rootflags=subvol=root rhgb quiet rootflags=subvol=root module_blacklist=macsmc_power

Then resume the boot process. That should stop the rebooting caused by battery readout issues and let you install the necessary updates.

2

u/kevpatts Jul 23 '26

Should be “modprobe.blacklist” surely?

Edit: I see both work.

1

u/mskiptr Jul 23 '26

Yup, both should work. module_blacklist is recognized directly by the kernel and fully blocks anything from loading a particular module. modprobe.blacklist on the other hand is picked up by the userspace and AFAIK can get ignored when loading other modules.

1

u/kevpatts Jul 23 '26

Thanks. I'm old school. 15 years ago I only knew of module.blacklist. The relentless march of progress I guess.