Just installed Asahi linux, and its amazing. Turned the animation speed to instant and it feels so much snappier than Golden Gate.

For some reason I can't uninstall some packages (k-mail, etc) using the discover app.

At first, I installed Fedora Minimal and manually set up KDE on it. But I grew tired of KDE’s look, and I was already bored with GNOME, so I continued using macOS most of the time. That’s why I decided I could experiment a bit and try installing my favorite desktop environment, Pantheon, as a second option.

Overall, it’s working fine so far. I’ve encountered a couple of bugs, but they aren’t critical, and I’ve managed to fix some of them.

Hey everyone!

I'm thinking about switching to Fedora Asahi Remix and would love some advice from people who are already using it, especially on similar hardware.

My MacBook:

• MacBook Pro 13-inch (2022)
• Apple M2 chip
• 8GB unified memory
• 512GB SSD (443GB used, around 51GB free)
• macOS Golden Gate 27.2

I'm mainly interested in Linux because I'm getting a bit bored with macOS and really enjoy customizing my desktop. I'm also hoping for a smoother, more responsive experience.

My main activities are web browsing, watching videos, listening to music, and software development. I have another Mac for iOS development, so losing Xcode isn't a concern.

A few questions:

1. Performance: Does Fedora Asahi feel faster or smoother than macOS, especially on the base M2 with 8GB RAM?
2. Hyprland vs KDE: I'm really interested in Hyprland (or maybe Niri). How well do they work on Asahi? Any GPU or stability issues?
3. Battery: How does battery life compare to macOS? What about battery drain during sleep?
4. Storage: My SSD is almost full. How much space would you recommend freeing up and allocating to Linux for comfortable daily use?
5. Compatibility: Any issues with browsers, video playback, Spotify, hardware acceleration, or other daily applications?
6. Installation: Is installing Fedora Asahi alongside macOS 27.2 currently safe and reliable? Anything specific I should watch out for?

I'd love to hear from anyone daily-driving Asahi on an M2 MacBook, particularly with 8GB RAM.

Would you recommend making the switch, or is macOS still the better experience overall?

Thanks!

I am on 7.1.13-402.asahi.fc45.aarch64+16k, running FC45. The system updated to the latest version, but the kernel did not.

I would like to update to kernel 7.2, if it is available for the M2 Air Mac.

I'm on an m1 air running macos 27.

Is it okay for me to lets say, downgrade to macos BigSur, which is the oldest macos version available to download, and then install Asahi using the command?

I saw the download size for the macos 27.2 and decided I was finally done with apple.

I know that Hoolock Linux does support A7 but I am not sure where to start, I know I need checkra1n and pongoOS but I'm not sure where to go from there, any advice?

Is Ashai linux going to have support for the macbook neo soon?

I did this using Hoolock Linux (kernel + m1n1) with an Arch userspace. The phone goes into DFU, palera1n (checkm8) pwns it, and a laptop boots m1n1 plus the Linux kernel over USB

What works:

All 6 CPU cores

Multitouch touchscreen, with a driver

In progress: the GPU. Its firmware already boots and accepts jobs, but nothing is GPU-accelerated yet

Thanks to Hoolock Linux, Asahi Linux and palera1n

so i've been trying out spotatui, ncspot and spotify_player for terminal. however, all of them seems to be stuck every time i tried to play a track. with a second thought, i installed spotifyd and somehow it doesn't work either, or i'm just too noob to install correctly.

question is: has anyone succeeded using terminal spotify on asahi linux at all? any advice or tips?

Well so i'm totally new to linux in general, and i've just discovered that spotify and discord are only available through pwa. I'm currently on dms hyprland, and i kinda want to try adjust spotify pwa preferences to my liking. I've seen people using spicetify (?) but since i don't have the app like everyone, i was left clueless.

Is there a full disc encryption built-in in the plan into the installation process? I'd love to have a completely separared spaces.

Similar to what it is, for example, on the Pop_Os when you can only click on check box and it's done.

The amount of work that has been put into this release is simply astonishing. The fairydust branch was also updated today. I've also improved my own scripts that track the Asahi upstreaming efforts and this time there is a bit more data represented with the infographics I'm proud to present in this post, because I think they better reflect on how much effort the Asahi team has put into this, because the numbers of patches and lines on top of mainline is not enough to tell the whole story and why they are increasing.

It also wouldn't be fair because Asahi team is actually upstreaming quite a lot, while also delivering the new features now. I've made a lot of fixes e.g. visual style, excluded rust-for-linux/rust-next/drm-rust-next etc. from the main counts, the line counts were slightly off as well and many other things.

The tag is available at https://github.com/AsahiLinux/linux/releases/tag/asahi-7.2.11-1 with the following changes:

- initial thunderbolt support, only xdomain (usb4net/usb4stream) and usb3
  tunneling, no PCIe/DisplayPort tunneling
- support for compressed / interchange framebuffers for sharing between
  video decoder, GPU and display. Only display support implemented
- DCP 14.8.3 firmware support as basis for M3* support
- display mode selection and backlight locking fixes
- workarounds for M4+/A18 WFI*/WFE* brokenness
- AVD fixes
- Rust io rework from 7.3 and refactored all rust drivers
- GPU driver rework onto upstream DRM abstraction (DRM GPUVM, device
  lifetime, scatterlist)
- dropped crashdump/dev-coredump support in GPU driver
- use shared GPIO for speaker amp shutdown pin
- DART aperture DT changes

Update: since the 7.2.11 tag, the 7.2.12 has also been tagged with minor asahi config fragment and t8103 dts fixesminor asahi config fragment and t8103 dts fixes.

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!

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?

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 :)

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?

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!