You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i just installed asahi linux kde on my macbook air m1 8gb
the only problem is it randomly shuts down afther around 3 minutes
does someone know how to fix it
module_blacklist=macsmc_power in the kernel command line should work around this until a fixed kernel is available.
Where/how does one actually put this for those of us in the audience who aren't super-familiar with Linux? 😅 My Asahi Fedora doesn't even stay up long enough for me to log in so I'm hoping it doesn't require having the machine operational under Linux... (not that there's anything important on it, I guess worst case I can blow the whole partition away and start again once the fixed kernel is released).
You can edit the kernel command line from GRUB. You can get the GRUB menu to show after U-Boot has run by mashing one of the Shift keys. Once there, on-screen instructions will tell you how to edit the command line and boot the modified boot entry. Make sure your modification goes on the line starting with linux. It won't work on any other line.
Okay, so this was a massive pain but those instructions at least got me onto the right path, thanks! For posterity:
The default timeout for GRUB with Asahi is only one second, so as soon as it says "Hit any key to stop autoboot" and comes up with the next line, you need to press Escape rather than Shift (apparently Shift is for BIOS and Escape is UEFI).
Press e to start editing, but for some reason the cursor isn't actually visible so the only way to figure out where it is is to just type a letter and see where it appears.
The fastest way to get to the very end of the line that starts with linux is to press the down arrow a bunch of times so you're on the last line, then hit the left arrow a couple of times so goes to the end of the line above it, then type a letter to confirm you're in the right place, then put module_blacklist=macsmc_power (I also found that the keyboard doesn't reliably respond and it would miss key presses which made this whole process even more fun).
Press Ctrl-x to boot.
This managed to get me in and avoid the machine shutting down immediately, but it's only a one-time thing. I tried editing /etc/default/grub to add module_blacklist=macsmc_power onto the end of the GRUB_CMDLINE_LINUX_DEFAULT line, apparently either update-gruborgrub-mkconfig` are meant to be run once you've edited that file but neither of them actually exist on my system that I can see.
I've had enough frustration and yak-shaving for one day so I'll come back to this later, heh.
You're only supposed to do it once to update the system. The latest kernel has a fix for this and you do not need to blocklist macsmc_power permanently.
Activity
jannau commentedon Jun 14, 2026
Is on the device the macOS 27 developer beta installed?
Most likely yes, this is caused be change in SMC firmware in macOS 27. The issue is fixed in AsahiLinux/linux#517 but no fixed kernel is yet released.
module_blacklist=macsmc_powerin the kernel command line should work around this until a fixed kernel is available.See also https://social.treehouse.systems/@AsahiLinux/116719749555082847 and https://social.treehouse.systems/@AsahiLinux/116742414272710482
VirtualWolf commentedon Sep 2, 2026
Where/how does one actually put this for those of us in the audience who aren't super-familiar with Linux? 😅 My Asahi Fedora doesn't even stay up long enough for me to log in so I'm hoping it doesn't require having the machine operational under Linux... (not that there's anything important on it, I guess worst case I can blow the whole partition away and start again once the fixed kernel is released).
chadmed commentedon Sep 5, 2026
You can edit the kernel command line from GRUB. You can get the GRUB menu to show after U-Boot has run by mashing one of the Shift keys. Once there, on-screen instructions will tell you how to edit the command line and boot the modified boot entry. Make sure your modification goes on the line starting with
linux. It won't work on any other line.VirtualWolf commentedon Sep 12, 2026
Okay, so this was a massive pain but those instructions at least got me onto the right path, thanks! For posterity:
eto start editing, but for some reason the cursor isn't actually visible so the only way to figure out where it is is to just type a letter and see where it appears.linuxis to press the down arrow a bunch of times so you're on the last line, then hit the left arrow a couple of times so goes to the end of the line above it, then type a letter to confirm you're in the right place, then putmodule_blacklist=macsmc_power(I also found that the keyboard doesn't reliably respond and it would miss key presses which made this whole process even more fun).Ctrl-xto boot.This managed to get me in and avoid the machine shutting down immediately, but it's only a one-time thing. I tried editing
/etc/default/grubto addmodule_blacklist=macsmc_poweronto the end of theGRUB_CMDLINE_LINUX_DEFAULTline, apparentlyeitherupdate-gruborgrub-mkconfig` are meant to be run once you've edited that file but neither of them actually exist on my system that I can see.I've had enough frustration and yak-shaving for one day so I'll come back to this later, heh.
chadmed commentedon Sep 12, 2026
You're only supposed to do it once to update the system. The latest kernel has a fix for this and you do not need to blocklist macsmc_power permanently.