So, let's start with the most obvious, the performance cores; they make the most sense for a CPU-intensive task; on my systems those are CPU 4-7. We can see here that the promise of the Trifecta Foundation holds, as the rust implementation is about 4% faster. 4/N
I'll do benchmarks using my own bzcat and comparing that with bzip2's original bzcat. All running on an M1 laptop running Linux. The M1 CPU has both performance and efficiency cores. We'll run the benchmark on both, using hyperfine to do the comparisons. 3/N
SMC made it just in time for the merge window! Now it's finally possible to reboot M1/M2 with an upstream kernel ;)
This also allows to enable the power gpios for e.g. wifi and allows us to upstream drivers for the power button, hardware sensors, battery status and RTC next.
https://lore.kernel.org/asahi/175334693659.1935861.13683239351116261977.b4-ty@kernel.org/
Regular reminder for anyone who might have an Apple Silicon based Mac that Asahi Linux is a thing and a good thing. It's not just Intel Macs that can play nice with Linux.
I love my little M1 Macbook Air. It's great hardware and never gets overheated. But sometimes I need to play with Linux instead of MacOS.
Asahi installation was able to hive off a small partition during setup to dual-boot. It's very smooth and makes for a great desktop. I've got Firefox and LibreOffice and even Proton VPN running nice. It's ready for prime time.
Am sending this toot from Asahi Linux right now :)
MacBook & Linux Ramblings
So today I bought a 9070 XT and reassembled my amd64 PC, which I retired a couple of years ago, because I really, _really_ want to play video games again without worrying about FEX or Rosetta.
So far, I have had 3 kernel oopses of various provenance. Haven't had one kernel oops on any of my Macs unless I was hacking on stuff.
The graphics card by itself sucks down over 30 W just sitting at the desktop. My entire Mac Studio idles at less than 5 W.
The fans will not shut the fuck up no matter what I do. The Mac Studio fans are never audible, even at full system utilisation.
The motherboard's DMI information is straight up just wrong, and the SuperIO chip has no hwmon driver. The Mac Studio's Devicetree is (obviously) correct, and the SMC hwmon driver works well.
The CPU pulls about 50% more power than my Mac Studio while being noticeably slower.
The motherboard's builtin audio interface is unusably bad compared even to my MacBook Air's headphone jack.
The only parts of this experience that are objectively better than using a Mac with Asahi are gaming performance (no shit, there's no emulation of history's worst instruction set involved), monitor support, which is something we're actively working on anyway, and boot time although it's close.
The whole PC ecosystem is, unbelievably, even more totally ratfucked than it was when I last abandoned it. For the money I've spent today to get back into the PC, I could've bought two whole Mac minis with change left over, or a new audio interface and calibration mic to retune some of Mac speakers that need it.
while #Gnome isn't working on my laptop, I decided to downgrade for now 
Hey #Linux / #Mesa / #gallium folks,
I'm having a problem where I can't start any graphical user interface, whether it's wayland or x11 because the driver files given by mesa don't have the __driDriverExtensions symbol
Anyone know how to deal with this? I'm on #AlpineLinux / #AsahiLinux. If you have a lot of linux friends, feel free to boost!
Now that 6.16-rc1 is out I've just submitted SMC v7 which is likely the one that will be merged: https://lore.kernel.org/asahi/20250610-smc-6-15-v7-0-556cafd771d3@kernel.org/
I've also sent a small cleanup for our device tree files: https://lore.kernel.org/asahi/20250610-nvmem-bit-pattern-v1-0-55ed5c1b369c@kernel.org/
Next up: Getting USB3 and atcphy into shape and send that out as a RFC to see if anyone can come up with a better way to handle that mess.
Asahi Linux uses DNF. It's essentially Fedora with the extra trimmings to make it Apple Silicon friendly.
Managed to install ProtonVPN after translating their cryptic instructions. Their CLI example didn't work for Asahi but pretending you have Fedora gets it over the hurdle.
Now just need to convince UpNote that Linux also runs on non-Intel hardware.
Asahi Linux is working very nicely on my little M1 MacBook Air. I wanted a clean environment that I could trust as secure.
Maybe I'll be inspired to spend a little more time writing code, updating the website, and tinkering with some FOSS.
It's very fast. Very clean. Mastodon looks peachy in my Firefox browser too :)
I just installed #AsahiLinux and it just… worked. What? How is the m* port of Linux the easiest to just… use?
Our #asahilinux i2c fixes were merged 
https://lore.kernel.org/asahi/enap4curtpjaiazxpcsw3sk64aq2i7wqi3iwm6l2pfph5qduwj@gkagpeazcumg/T/#t
4 commits less in our downstream tree, just a few hundred more to go 
Next up: SMC
I just sponsored #AsahiLinux. Go sponsor your open source dependencies!
As I depend on them in my day-to-day while daily driving an M1 device running Gentoo, I have begun supporting @AsahiLinux monthy via OpenCollective.
If you also make use of the Asahi kernel, or are interested in seeing the project succeed, consider donating as well:
https://opencollective.com/asahilinux
Looks like M4 support for #asahilinux is going be rather painful. We’re still focusing on upstreaming M1/M2 support but other people have been trying to bring up m1n1 on M4 and it looks like a few things changed:
When configuring a macho boot object we now get dropped into an environment where Apple’s SPTM is running in GL2 and we are supposed to talk to it from EL2 with MMU already enabled to setup pagetables. This neither works for Linux nor for running XNU under our hypervisor to reverse engineer the new hardware.
When configuring a raw boot object we’re dropped into EL2 with GL2 and most (all?) Apple specific extensions disabled. This is totally fine for Linux but we can’t run XNU under our hypervisor that we use to reverse engineer the hardware in this state. This also seems to be broken for >=15.2 right now because it probably isn’t very well tested 
Success!!! I've migrated Immich from an x86 Debian system to Asahi Fedora on an M1 Mac Mini.
Installing Fedora was easy
Installing Docker was easy.
Installing Tailscale was super simple.
Installing and setting up CSF was easy, but only because I had notes from last time on how to make Docker and Tailscale cooperate.
Migrating the Immich database was a nightmare!! I think because my old system was a mishmash of legacy settings from 100+ releases ago... Also, my old system wasn't on the very newest release, which in itself made migration fail initially.
oh shit! one of my main issues with #AsahiLinux (which let me be clear, definitely wasn't big enough an issue to prevent me from daily driving the thing) - the lack of built-in mic support - is no more! the mic works loud and clear on my machine!
thanks @AsahiLinux !
Al final #LinusTorvalds se va a tener que conformar con el Dell XPS 13. Es lo que tiene convertir #Linux en una gerontocracia con claras fobias hacia los jóvenes. https://www.phoronix.com/news/Asahi-Lina-Steps-Down-Linux-GPU
I cannot find any prebuilt aarch64 versions of #OrcaSlicer out there for #AsahiLinux but it will build.
You'll need to create an asahi-fedora-remix file in linux.d that looks like [https://github.com/amdavidson/OrcaSlicer/blob/asahi/linux.d/fedora-asahi-remix](this one).
Then you can run the recommended sudo ./BuildLinux.sh -u && ./BuildLinux.sh -dsi
I didn't have enough memory on my system to satisfy (>10gb free) it so I had to build single threaded ( -1 ) and edit BuildLinux.sh to look for less memory.
My Bambu Network Plugin doesn't work for my P1S, but it seems to work fine otherwise.
Good luck!
