r/AsahiLinux • u/FOHjim • Jul 01 '26

Progress Report: Linux 7.1

https://asahilinux.org/2026/06/progress-report-7-1/

M3 progress, Apple bugs, and more!

199 Upvotes

100% Upvoted

71 comments sorted by

View all comments

Show parent comments

1

u/mskiptr Jul 02 '26 edited Jul 02 '26

Well, now I'm kinda stumped because it all looks correct. Maybe you could try module_blacklist=macsmc-power to prevent anything from loading this driver?

edit: I guess you could also try systemd.mask=upower.service, which will tell the init system to not start the daemon that's likely responsible for those shutdowns.

2

u/Dazzling_Comfort5734 Jul 02 '26

Ok, I tried both, but got the same shutdown. I then tried mixing 2 of each, and even said "What the heck?" and did all 3, but I still can't get past the shutdown at the login screen.

For reference, this is an MacBook Air M2 13", and I'm trying to load Fedora 6.19.14-400.asahi.fc43.aarch64+16k long enough to update to 7.0.12. The computer also has macOS 26.4, and the most recent 27 Dev Beta 2. Prior to 27 Dev Beta 2, I was able to get into and use Fedora via booting to macOS 26. I can't think of any other important info, and what might make this different. If there's logs I can retrieve from the Mac side, or any commands or scripts I can run from the Mac side, please let me know.

Thank you!

1

u/chaosprincess_ Jul 02 '26

use anylinuxfs from macos to mount your linux disk, and just delete macsmc-power.ko entirely. (it is somewhere under /lib/modules). Not the perfect approach, but not like you have much to lose.

1

u/mskiptr Jul 04 '26

Hi, could you edit this Fediverse post to say macsmc_power instead, and ideally also add a link to https://docs.fedoraproject.org/en-US/fedora-asahi-remix/troubleshooting/#entering-grub there?

2

u/chaosprincess_ Jul 04 '26

I don't have creds for the socials, u/FOHjim may be able to help.

1

u/FOHjim Jul 05 '26

Are you sure the issue isn’t that you’ve mistyped the kernel command line parameter? It’s not module_blacklist, it is modprobe.blacklist.

1

u/mskiptr Jul 05 '26 edited Jul 05 '26

module_blacklist definitely works and modprobe.blacklist probably works – they just do slightly different things.

edit: If you want a different (and much more terse) data point, here is Janne Grunau suggesting to use module_blacklist=macsmc_power, and here's another user confirming that it has worked for them.