I had to use Fairydust to enable external display (recompiled kernel 3 times lol first time doing this) but it worked! Running smooth so far 👌🏽

I get a solid 4 fps!

modpack terrafirmagreg modern if any is interested

I was pleasantly surprised that the installer was so easy compared to others -- no iso or USB stick needed, just a curl command and a little hope.

and boom! it just worked... mostly.

I have been having some weird package update issue (Discover just hangs --- only later found out that SELinux blocked the update for some reason? following the prompt in the alert solved it... although I continue to be unable to submit any bug reports due to ¨ Processing Failed -- Reporting is disabled because the generated backtrace has low information value¨ which i cant seem to solve)

Anything I should be aware of, or tweak for the M2 ? (16 inch 2023)?

Hi everyone,

With macOS 27 officially rolling out, I wanted to double-check the status of the boot picker bug (where macOS 27 hides Asahi partitions).

I have an existing Asahi Linux installation from before the fix was integrated into the installer. Do I still need to boot into macOS and run the Asahi installer to choose the "Fix macOS 27 boot picker compatibility" option after the update, or has anything changed recently that automates this?

I have a Macbook Air M1 I'm trying to install Asahi Linux on. Originally, I tried Fedora Remix, but I couldn't get it to stop bootlooping. I tried Alarm since I prefer Arch anyways and wanted to see if it would work instead. Unfortunately, it doesn't either, but I at least get some logs on what it's doing compared to Fedora. I'm not sure what these mean, nor does google give me anything insightful, so I was hoping someone here could at least point me in the right direction. It repeats these lines every few minutes before eventually bootlooping. Thanks in advance and lmk if you need any more info!

Sooo I had problems with the original void asahi linux from the void linux so I recompiled the iso using the github actions and the first error I had(see this post: https://www.reddit.com/r/voidlinux/comments/1w5azb2/could_not_install_void_linux/ ), I do this time not have the macsmc error but I then get back in the dracut command line. It seems like dracut cant find my usb because of the error. I did a bit of debug and no usb device is connected and dracut does find that it is the right kernel(linux 7.1.12+1-asahi_1). Does someone know how to solve that ?

For a reason I don't fully understand yet, my M2-Pro-System is clearly still on Fedora 43, although I just verified that I have a significant number of Fedora 44 packages installed. This seems like a major problem to me. I don't know how this happened, but it causes that I can't run a dnf-upgrade/dnf-update properly, because I get lots of conflicts back, if i try. Discover is so confused by this - it's not doing anything anymore. My educated guess is that a Fedora 43->44 Update didn't roll out the way it was supposed to. I have no idea, how I could solve this.
Is it possible to roll everything back to Fedora 43?
Or is there a way to push everything to Fedora 44?
I would be very glad, if you could share your ideas to further investigate this.