So I just compiled and installed the fairydust kernel because I was missing the bigger screen aspect ratio of my external monitor and it worked flawlessly on first attempt.

I tried to set up the brightness syncing of both my external and built-in macbook display but for some reason sudo ddcutil detect can't detect my external display, is there any other workaround?

So I’ve decided to try Linux on my m1 MacBook and I’m pleasantly surprised. It’s decently faster than macOS and it’s smoother. But I’ve got some minor issues which I’m wondering if they could be fixed. First and most important is the audio. It’s noticeably worse than in macOS and I’ve tried different eqs and that doesn’t seem to help. Second is the trackpad. It’s a lot less precise and scrolling on the web feels less smoother. Everything else is awesome and if there’s a way to resolve these issues I might even main it.

I'm more familiar with web stacks, especially for building fancy and smooth UIs, so I got Claude to figure out how to get a Wayland compositor to sit on it, and then run a kiosked Firefox inside that.

Needs a kernel patch rn due to some sort of bug/feature/something in the ADP driver, where the touchbar has 64 byte wide buffers but only shows 60 bytes of it, but ADP only allocates 60 bytes, causing some of the content to spill over to the next line and screw it all up.

But hopefully this means we can get fancier touchbars running on Asahi Linux!

Hey everyone!

I've been working on pw-airplay, a project that brings AirPlay 2 audio output to PipeWire.

The idea is simple: your AirPlay 2 speakers, including HomePods, show up as regular audio outputs in Linux's sound settings, just like your built-in speakers or headphones.

What it supports

• Native PipeWire outputs: select your AirPlay speakers from your desktop's audio settings.
• Multi-room audio: define speaker groups and stream to them in sync.
• A/V sync: reports AirPlay's latency to PipeWire so compatible video players and browsers can compensate.
• Volume and media integration: control speaker volume and send now-playing metadata through MPRIS.
• Systemd integration: user services handle the streaming daemon and engine.

Under the hood, it uses PipeWire sinks and OwnTone's AirPlay 2 implementation, with some patches to support live audio streaming and integration with PipeWire.

I've tested it on Fedora 44 (aarch64) with a HomePod mini, and I'd love to see how it behaves on other Linux setups.

Since this is r/AsahiLinux, I'm particularly interested in whether anyone would be willing to try it on an Asahi Linux installation running on Apple Silicon. I haven't verified it on Asahi yet, so feedback on compatibility, dependencies, and potential issues would be really helpful.

Project & installation instructions: https://github.com/superlemon57/pw-airplay

It's still a work in progress, so bug reports, suggestions, and contributions are very welcome!

Curious to hear what you think.

Has anyone got photoshop working on ALARM if you did plz tell me how you did it. Thx :)

will a 1080p240hz monitor work on my m1 pro macbook pro via the hdmi port? it does work on macOS but I want to make sure if such a high refresh rate will work on asahi before installing it, as it is not specified, thank u!

Can anyone offer any help please?

The install script is failing at:
newfs_msdos -F 32 -v 'EFI - Fedor' -I 0x264e2b13 /dev/rdisk0s7

It's pretty much a normal mac. One OS, no extra installs. Nothing weird...

Stub OS installation complete.

Adding partition EFI (524.29 MB)...

  Formatting as FAT...

newfs_msdos: /dev/rdisk0s7: Resource busy

Failed to run process: newfs_msdos -F 32 -v 'EFI - Fedor' -I 0x264e2b13 /dev/rdisk0s7

Output: b''

root        : ERROR    Process execution failed

Traceback (most recent call last):

  File "/private/tmp/asahi-install/main.py", line 1216, in <module>

InstallerMain(installer_version).main()

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^

  File "/private/tmp/asahi-install/main.py", line 1000, in main

while self.main_loop():

~~~~~~~~~~~~~~^^

  File "/private/tmp/asahi-install/main.py", line 1175, in main_loop

return self.action_install_into_free(parts_free)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^

  File "/private/tmp/asahi-install/main.py", line 364, in action_install_into_free

self.do_install(os_size)

~~~~~~~~~~~~~~~^^^^^^^^^

  File "/private/tmp/asahi-install/main.py", line 569, in do_install

self.osins.partition_disk(self.part.name, total_size)

~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/private/tmp/asahi-install/osinstall.py", line 106, in partition_disk

subprocess.run(args, check=True, stdout=subprocess.PIPE)

~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/private/tmp/asahi-install/Frameworks/Python.framework/Versions/3.13/lib/python3.13/subprocess.py", line 577, in run

raise CalledProcessError(retcode, process.args,

output=stdout, stderr=stderr)

Any clues please?

I have an M2 MacBook Air with 16GB RAM and 256GB storage, but I don't have enough free space to install Asahi Linux.

I have a 1TB portable M.2 SSD and was wondering if it's possible to install Asahi Linux on it and boot from the external drive.

As far as I know, the installer doesn't officially support this, but I'm not entirely sure. I currently have around 35-40GB of free space on my internal drive.

Is there any workaround to install it on the external SSD? Would I run into any issues, and is it worth trying?

If it's possible, are there any tutorials, guides, wiki pages, or videos explaining how to do it?

https://github.com/idrode/barux

Hi again, I've adapted it to how I use it. It can definitely be improved a lot, and if anyone wants to customize it to their own taste, go ahead. For now I'm leaving it as it is. The guide is available in both English and Spanish.

I want to help my friend get Linux on his Mac Mini M1. How much disc space should he allocate for Asahi? I know he will want to play with a variety of software apps to see the potential Linux has to offer, especially the ArtCraft apps that recently came out, even though they are super early buggy alpha. And DaVinci Resolve for video editing. And the usual (Libreoffice, GIMP, browsers, simple text editor, Signal messenger)

I want to help a friend install a debian Linux distro on his M1 Mac Mini. I'm not a Mac/Apple user. Any help advice on how I can help him? It would be a dual boot system (or should he put Linux on an external ssd?) Debian based distro if possible as I am knowledgeable on deb distros.

Is it possible to run Asahi in a vm or container on macos? I wanted to use the m2 mac mini I got as an airmessage server while also utilizing linux.

Hi,

This series adds initial device trees and dt-bindings for the Apple
Silicon devices using the M4 Pro/Max (t6040/t6041) SoCs.

This series covers only a minimal amount of hardware, which is useful
as a basis for future developments. The hardware added here has remained
largely unchanged between the M3 and M4 generations.

The dt-bindings changes should be mostly boring (in a good way!). The
device trees themselves are roughly organized into the MacBook Pro
models on one side (t604x-j614-j616) and the Mac mini and Mac Studio on
the other side (t604x-j575-j773). I'm hoping to re-use these dtsi files
for the M5 Pro/Max versions of these machines in the future.
I applied some version of dt-check-style formatting to all new files
with the exception of the generated pmgr nodes.

Merge strategy:
Since there are no actual driver changes, we'd prefer to merge the
dt-bindings changes through the apple-soc tree once Acked by the
respective maintainers.

Thanks,

Yureka

Signed-off-by: Yureka Lilian <yureka@cyberchaos.dev>Hi,

This series adds initial device trees and dt-bindings for the Apple
Silicon devices using the M4 Pro/Max (t6040/t6041) SoCs.

This series covers only a minimal amount of hardware, which is useful
as a basis for future developments. The hardware added here has remained
largely unchanged between the M3 and M4 generations.

The dt-bindings changes should be mostly boring (in a good way!). The
device trees themselves are roughly organized into the MacBook Pro
models on one side (t604x-j614-j616) and the Mac mini and Mac Studio on
the other side (t604x-j575-j773). I'm hoping to re-use these dtsi files
for the M5 Pro/Max versions of these machines in the future.
I applied some version of dt-check-style formatting to all new files
with the exception of the generated pmgr nodes.

Merge strategy:
Since there are no actual driver changes, we'd prefer to merge the
dt-bindings changes through the apple-soc tree once Acked by the
respective maintainers.

Thanks,

Yureka

Signed-off-by: Yureka Lilian <yureka@cyberchaos.dev>

Given Tails OS can’t run on M1 and Asahi needs MacOS even after installated, maybe Asahi can run from pen drive ?

Hi everyone,

I know there have been similar questions on the forum, but I was wondering if there are any updates or any timelines regarding LLM inference and GPU acceleration in general, e.g. when it comes to gaming.

Last time I checked, LLM inference, using I believe vulkan as a backend, lagged significantly behind Metal in terms of performance; something like half t/s on decode (and maybe prefill as well, but I don't remember). Is this still the case and is anyone even working on it? Not trying to be derogatory; I know how hard it is. Just wondering if it is expected to get better or if it is somewhat abandoned.

Related to this, is the current backend exposing only the GPU or does it also expose the ANE and the AMX?

I always loved the build quality and the hardware. But honestly never really liked the apple logo. Glad that is dead now buried alive.

I have 256gb space for my laptop. Thought it'd be easy to remove macOS but some redditors said i should keep macOS. Should i keep it? Then i have no reason to keep using Asahi.

Got Fedora Asahi Remix 44 booting in a VM I've been building (MX Studio), with an arm64e guest on an M4 Max host. It reaches GNOME and works-ish. Still some rough edges.

Mostly posting as a fun data point on how far my VM has come. If anyone wants to try it or has ideas on what to test next, I'm happy to hear them.

When the macOS 27 developer beta came out, issues arose with the SMC and other components, i.e. battery readings were all over the place and I had Wi-Fi issues. But now that macOS 27 is stable and a couple months have passed since that developer beta, can I update my macOS 15 install next to Asahi to 27?

Apple logo cover up https://www.reddit.com/r/AsahiLinux/s/4Kn81x6YV4

Hello,

As you already know, OpenCore Legacy Patcher allowed running macOS versions up to Tahoe on macs as old as 2008 thanks to hardworking of the development team. However, with macOS 27 fully dropping Intel, it won’t be possible to install any newer macOS version on Intel macs, which also means that the project is now coming to an end.

However, this brings me to another concern. Despite macOS 27 Golden Gate still supporting all Apple Silicon Macs without any issues, it is likely that Apple will start dropping support for older Apple Silicon Macs in macOS 28 or 29 starting with M1. So I wonder once Apple starts dropping OS support for Apple Silicon Macs, would it be possible to make a similar patcher using m1n1 bootloader to allow installing newer macOS versions on older Apple Silicon Macs. I would be sad to see my M1 MacBook Air losing macOS support despite Linux being a good alternative.