Asahi Linux / is on Nostr

Linux for Apple Silicon macs

Website: https://asahilinux.org
GitHub: https://github.com/AsahiLinux
GitHub Sponsors: https://github.com/sponsors/marcan
Patreon: https://patreon.com/marcan

Last Notes

2024-08-05 14:31:51

PSA: **Hold off on distro updates for a few days if you use WiFi.**
An upstream wpa_supplicant update broke WPA2/3 on all Broadcom chips (not just Macs). We are in the process of releasing a fix for Fedora. For other distros, please check with the relevant maintainers.
Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2302577

2024-07-15 12:41:09

GPU acceleration support for Flatpak is finally coming to Fedora Asahi Remix! Try it out today:<code>sudo dnf copr enable @asahi/flatpak<br>sudo dnf install mesa-asahi-23.08-flatpak mesa-asahi-22.08-flatpak<br></code>
Log out and back in for the changes to take effect, then launch any Flatpak that uses the GPU.
(Note: supported on the FDO 22.08 and 23.08 runtimes only, which covers the vast majority of Flatpaks)

2024-06-02 05:57:14

Hey everyone,
We have seen a deluge of posts (on Reddit etc.) about x86 emulation on Asahi Linux in the past few weeks. While it is of course OK to be excited about recent developments, we want to remind everyone of a few things:<li>This stuff is bleeding edge. ABIs are changing all the time. Things may break with any random package upgrade. There is a reason we are not shipping this for end users yet. You are entirely on your own if you choose to try it.</li><li>The state of things today should in no way be taken to be representative of what x86 gaming on Asahi Linux can achieve. Put another way: It's okay to be excited about the things that <em>do</em> work, but the bugs, limitations, and brokenness you might experience are not where we expect to be.</li><li>In particular, if you experience issues or bugs, chances are that as a user you have absolutely no idea what the root cause is or how easy it is to fix. We've been through issues as dumb as "all GPU memory is leaked forever" and "microVMs only have a hardcoded 4GB of RAM", never mind the obvious "without TSO everything is slow". Obviously these issues are not acceptable, nor are they hard to fix, but if you experience the effects you might wrongly conclude that stuff is very broken in much deeper or hard to fix ways than it actually is, and therefore leave disappointed and very misled thinking it's going to take months or years to fix these dumb issues.</li><li>We don't talk about timelines for a reason. Anyone claiming "X will be here next quarter" or "X won't be here for a year" is making things up, either way. Stuff will be done when it's done. Until then, any speculation about when things will be ready from random people is pure speculation, and not based on any objective reality.</li>
We're excited about what there is to come, and we do intend to package and make this all available to users - once it's ready. In the meantime, our recommendation is always to wait until then. You are free to experiment of course, but please be mindful that you don't imply anyone or everyone should try this, and avoid writing "easy-to-follow" guides or scripts that present themselves as being suitable for end users. We don't want news coverage to happen before things are ready, as that will only hurt the project. If you are a journalist watching the progress, we would appreciate it if you wait until things are officially released before publishing any articles about this.