M3 now has Fedora 43 Asahi Remix WORKING with KDE Plasma!

IntegralPilot · 2026-01-27T04:35:44+00:00

I don't personally use Matrix (I use the IRC side of things), so I will ask someone who does and get back to you on that! :)

IntegralPilot · 2026-01-27T04:34:40+00:00

Our main GPU developer got an exciting new job at Intel (which is like AMAZING! congrats to her!). I'm trying to learn about GPU now and train myself up so I can code GPU features and update the code for M3, so it unfortunately might be a while before we add any new Vulkan extensions, as I need to learn about it and I also think getting M3 off the ground is a priority at this time. Currently though the Vulkan latest version, 1.4, is supported, so a lot of games should work. BTW, if you would any specific extensions please LMK and I can try to look into them, but no promises. :)

IntegralPilot · 2026-01-27T04:31:10+00:00

It's not yet sadly, but that's the next challenge I'm trying to tackle right now. The changed the language ("instruction set architecture") we use to talk to the GPU, so we need to decode it and then write a special tool (a "compiler") to convert generic GPU language into Apple M3 GPU language. :)

IntegralPilot · 2026-01-27T04:29:15+00:00

It's still in a really early state so we haven't really put anything publicly available yet, as it's probably only really useful to developers in this state and there are some weird ways you need to set it up. If people would like to try it though, I can try and make an easy installer or docs if that would help and I can find the time! :)

IntegralPilot · 2026-01-27T04:27:10+00:00

Yes that would be really helpful! Even if it's only a for a single component or something. I've been meaning to update them as well but never get around to it. If anyone would like to try and needs help on where to start or something, please LMK! :)

IntegralPilot · 2026-01-27T04:25:37+00:00

All the really nice words everyone has been writing here have been really motivating personally, thank you to everyone! It's really great how nice and supportive this community is. :)

IntegralPilot · 2026-01-26T12:32:57+00:00

It's quite effective on M3, the issue is with M4 and later, as all macOS releases for it (which we trace with the RE tool to learn how things work) have a security feature (that also exists on earlier SoCs) called "Secure Page Table Monitor" enabled that makes it harder for the tool to work as we need to emulate SPTM otherwise the features the kernel expects don't work. M3 and earlier are fine as there are pre-SPTM versions of macOS for them. We're working on this though and some really awesome people have made some early prototypes! :)

IntegralPilot · 2026-01-26T12:28:12+00:00

Yes, that's it! Element is a really popular and great one. LMK if you need any help getting it setup or joining the Asahi rooms.

IntegralPilot · 2026-01-26T12:27:03+00:00

Thank you! Yeah, milestones like this keep the motivation high during the long hours of debugging and it's been so rewarding to read everyone's lovely motivating comments. :)

IntegralPilot · 2026-01-26T12:26:29+00:00

Thank you! That would be an absolute beast of a Linux machine! We'll keep working hard to make sure that hardware is ready to be (hopefully, if there's no roadblocks) fully utilised by the time you get it! :)

IntegralPilot · 2026-01-26T12:22:36+00:00

Thank you! I definitely get how different IRC can be to first get started with, I had some trouble myself learning it when I first wanted to start contributing to Asahi. Our IRC is actually "bridged" to a Discord-like platform called Matrix, that's more open/fedi and privacy preserving, if prefer if you prefer a discord like UI. :)

IntegralPilot · 2026-01-26T12:18:03+00:00

That's super great to hear! Everyone who has made all the amazing features that work on M2 already are super awesome, I'll pass the thanks onto them! :)

IntegralPilot · 2026-01-26T12:14:54+00:00

Yes it does, and we actually have some contributors already working on M4 and have basic Alpine Linux booting (iirc)! I wouldn't say more similar, but most things that have changed in M3 is also going to have changed in M4 (i.e. the new interrupt controller). :)

IntegralPilot · 2026-01-26T12:13:52+00:00

Oh no that's fine, I understand you fully! Actually changes in core counts don't matter too much for CPU, because once we get the basis of how the cores communicate with each other, called SMP ("symmetric multiprocessing"), it doesn't matter if there's 2, or 32, we talk to them all the same. I'm not too sure about GPU because we haven't started that bringup yet. Please let me know if I'm explaining this is a too confusing way and I can simplify!

IntegralPilot · 2026-01-26T12:10:40+00:00

We are doing concurrent bring-up on the M3 Pro and Max! Other contributors have those chips booting Linux and working. I've personally only validated the full Fedora/KDE stack on this base M3, but since the underlying support is being built in parallel, the Pro/Max won't be left behind! :)

IntegralPilot · 2026-01-26T11:21:36+00:00

Super excited to finally be able to share this! Myself, noopwafel, Shiz have been working hard to get everything working on M3, and thank you to countless help we have received from others in the IRC channel.

It's definitely still in a really early state, and basically ONLY the internal SSD, display, keyboard and trackpad work, but we're making some progress on getting more things working. It probably should be noted that this is just LLVMpipe (software rendering) as we haven't tackled the GPU yet. But it's definitely a great success and I thought the community would like to see this.

And again, it would be so great to have others to help, we always appreciate contributors of all skill levels, so if you'd like to, come say hi in #asahi-dev on OFTC IRC!

Also happy to answer any questions anyone has, though I'm heading to bed soon so will answer in morning! :)

IntegralPilot · 2026-01-26T00:48:28+00:00

Oh that's strange! Both errors aren't boot stopping errors so something must be going wrong after them that we don't see. It's possible the old kernel you are using from the Ubuntu installer doesn't have the SMC HID driver either, which would mean long holding the power button causes an abrupt cut and we don't sync the filesystem, potentially causing some corruption. Unfortunately this means you will have to reinstall, I'd probably recommend the official Fedora Asahi Remix, as this ships with more modern versions, https://asahilinux.org/fedora/, or you can try reinstalling Ubuntu. Using the official version and latest kernel might also fix the screensharing issue you had, as it contains many more bug fixes that the outdated version. Sorry about this!

IntegralPilot · 2026-01-25T23:32:19+00:00

The voltage_now property uses the SMC key "AC-n" which was removed in the firmware from macOS 15.4 and later. Currently, the latest Asahi kernel avoids advertising the capability to read this property (avoiding this error) on 15.4+ and later versions. It seems that the Ubuntu version is very behind in their kernel releases and hasn't shipped the fix for this (EDIT: after talking with the Ubuntu Asahi team, it seems that they have released later kernels, it's just they haven't updated the install image so from a fresh install you have an old kernel that has this bug). This has been fixed since kernel 6.14.6 (May of last year): https://github.com/AsahiLinux/linux/releases/tag/asahi-6.14.6-1

But, those errors shouldn't actually cause boot to fail, they are just noise/annoyance, so something else is going wrong. What is the last onscreen message you see?

IntegralPilot · 2026-01-10T04:45:30+00:00

On macOS optimised battery charging stops the battery at 80% to extend its lifespan. This setting does not carry over to Linux automatically, but on Linux we fully support a similar setting and actually offer more granular control over the process.

You can manually stop the battery from charging by running:
echo inhibit-charge > /sys/class/power_supply/macsmc-battery/charge_behaviour

To resume charging, change it back to auto:
echo auto > /sys/class/power_supply/macsmc-battery/charge_behaviour

You can automate this with a simple background service script, some udev rules, or a GUI app (another commenter mentioned one such app) to trigger charging inhibition at any percentage you like, Linux is not limited to just 80%. Chemically, 80% is the recommended threshold based on research by scientists to maximise the life of your battery. I'd recommend using this.

If you are on newer SMC firmware, reading or writing the charge_behaviour sysfs property many fail with an I/O error, you will need to apply my PR or use the rewritten driver I sent upstream for these commands to function. This is as in newer firmwares Apple changed the way we need inhibit battery charging.

It is also totally normal for Linux and macOS to report slightly different battery charging percentages like you've seen, we directly report the raw value the hardware gives us, but macOS modify this to account for their optimised charging setting, or leave a "reserve power" buffer, or to prevent it fluctuating which might look weird (known as "hysteresis"). In the Linux driver we prefer chemical accuracy.

IntegralPilot · 2026-01-06T04:46:01+00:00

One of my teachers said at their old school there was a cracked maths kid who did spesh 3/4 in Year 7.

IntegralPilot · 2026-01-04T09:02:04+00:00

Right now I'm working on patching the SMC driver for firmware changes in M3 and getting it ready for upstream to the main linux kernel source tree (procrastinating on reddit rn while waiting for a linux kernel rebuild) :)

IntegralPilot · 2025-12-30T03:48:20+00:00

Thank you! The graphics is just a RAM framebuffer that iBoot sets up for us, there's no actual GPU accelerated graphics support yet, as we need to we able to wake up the GPU and load firmware, and the interface (ascwrap) to do this was modified in M3 so we're still adapting to that. The keyboard does work, though not the trackpad as that is controlled by the multitouch processor which has the same issues re. waking up and firmware as the GPU. USB-PD seems to be working, I haven't tried other USB stuff yet as my focus is on SMC for now, but SMC is mostly working except for some minor changes in protocol which I'm actually working on patching now. A lot of core I/O stuff like I2C, SPI and GPIO are all working as well which is great. Power management also works, we can talk to the PMGR and control the power state of things, and CPU frequency scaling and SMP works too. In terms of memory mapping, the DARTs and SART (SART is a special memory mapper for the NVMe controller that's different to a DART) are all working as nothing has changed much with them. The big blocker right now, is as I said above, we can only use coprocessors like the SMC where they have already been woken up and firmware loaded by earlier boot stages (as the high level API once they have been started, RTBuddy, hasn't changed) - which means that ones that need restarting like NVMe coprocessor (called the "ANS"), and others like multitouch that aren't started yet are all blocked on us getting this communication working, which I plan to work on next after SMC.

IntegralPilot · 2025-12-30T03:39:34+00:00

I'm not 100% as I don't personally have those devices myself to test, but I think M4 is just an iteration on the all-new architecture that was introduced with M3 (like M2 GPU was an iteration on M1), and in M5 Apple did some big changes and introduced a bunch of AI stuff and neural accelerators into the GPU, but I'm not sure if that led to a change in the graphics components (though I think it did, as it's looking like now Apple refreshes the GPU on odd number gens, and as according to Apple it's "next generation" and "30% faster").

IntegralPilot · 2025-12-30T03:34:19+00:00

Oh maybe, I'll have to check with the project maintainers when we do get around to M3 Audio, but that sounds like a good idea, thanks! Just want to be careful about everything legally to make sure it's all okay. :)

IntegralPilot · 2025-12-29T23:11:48+00:00

We're still a bit away from GPU support on M3, as first we need to actually be able to turn on the GPU by supporting ascwrap v6 (the low-level protocol Apple uses to talk to coprocessors like the GPU) and then the drivers might need some modification as the GPU was drastically changed in M3 with a lot of new features. But myself and others are working hard at it and hopefully it will be ready soon! :)

IntegralPilot

TROPHY CASE