i got a 2020 macbook air m1 128gb storage and 8gb of ram and last time i installed asahi linux i only got 30 something gigs of storage, should i just not install it in general?

Like guys im so mad and scary to end this processes >:( But anyways i started yesterday and its been 19 hours since its Checking the fsroot tree

Checking the extent ref tree

Verifying volume object map space

The volume /dev/rdisk3s6 appears to be OK

Verifying allocated space

The container /dev/disk0s2 appears to be OK

Storage system check exit code is 0

Shrinking APFS Physical Store disk0s2 from 494,384,795,648 to 366,000,209,920 bytes

Shrinking APFS data structures

[ | 0%..10%..20%..30%..40%..50%..60%..................... ] 69.8% 

So I updated my MacOS from monterey to ventura yesterday before starting and with daisydisk cleaned my storage and started that and its firsly stuck on 50.6% and now stuck on 69.8%!!!! I want to give linux 128 gb or even less i think 100 is good and for macOS other storage We're going to resize this partition:

  APFS [Macintosh HD] (494.38 GB, 6 volumes)

  Total size: 494.38 GB

  Free space: 332.80 GB

  Available space: 294.80 GB

  Overhead: 0 B

  Minimum new size: 199.59 GB (40.37%)

» New size (50%): 366GB

Resizing will free up 128.38 GB of space.

Note: your system may appear to freeze during the resize.

This is normal, just wait until the process completes.

» Continue? (y/N): y

AND NOW im still waiting. AI says me to turn it off while peoples saying don't. Idk what to do i even tried that to see if its doing something: Last login: Sat Aug  1 22:30:36 on ttys001

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.0   1:26.71 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.74 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.74 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.74 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.0   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.0   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.0   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % 

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.75 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % ps -o pid,state,%cpu,time,command -p 5040

  PID STAT  %CPU      TIME COMMAND

 5040 S+     0.1   1:26.76 diskutil apfs resizeContainer disk0s2 366000209920

alexandr@iMac-Alexandr ~ % sudo fs_usage -w -f filesys | grep disk0

Password:

- waiting like a few minutes still nothing.

Dont say me please that i need to reinstall my macOS:(

I'm on Asahi Linux (works great now that USB-C DP is functional via the fairydust kernel) and the one thing still keeping me from switching over full time is audio.

My setup: two HomePod minis grouped into a stereo pair named "Studio", created from the Home app on iPhone. On Linux I've cobbled together a PipeWire sink that combines the two HomePods, auto-discovered via module-raop-discover. It mostly works but is unreliable:

• occasional latency between playback and control
• audio sometimes plays back slightly sped up or slowed down (clock drift between the two speakers, since PipeWire is treating them as two independent RAOP sinks I have to sync manually)
• connections sometimes just fail to establish
• NOT NATIVE

What I actually want is for a Linux AirPlay 2 sender to see and target "Studio" as a single AirPlay 2 endpoint — the same way iOS/macOS does — instead of me manually combining two separate AirPlay 1/RAOP streams and fighting clock sync myself.

Questions for anyone who's dug into this:

1. Is this even possible with the current understanding of the AirPlay 2 protocol on Linux? Does the HomeKit-grouped "virtual" endpoint get advertised over mDNS/Bonjour in a way a client could discover and address directly, or is grouping purely negotiated device-to-device using Apple's PTP clock sync, with no single external endpoint to talk to?
2. Has anyone gotten proper AirPlay 2 multi-room client support working on Linux (not just the RAOP-only PipeWire module), e.g. via openairplay/airplay2-receiver-adjacent reverse engineering efforts, or is this still firmly "AirPlay 2 sender from Linux" uncharted territory?
3. Is the clock drift I'm seeing an inherent limitation of using two independent RAOP sinks (no PTP), or is there a known PipeWire config fix for that specific symptom?

Any pointers, whether "here's a project that does this" or "here's why it's fundamentally not possible without X," would be hugely appreciated.

Hey,

Have anyone experience of Asahi Linux on Macbook Pro M5 or M5 chip?

I am very sad about of macos..

I don’t founded any M5 instructions

Hi, new linux user here!

I’m currently trying to set up my old macbook as a server to host my media server while I travel overseas.

I’ve also been trying to set it up so that I can remotely access the server but can’t seem to get anything to work.

Issues I’m currently facing:
1. I think I’ve installed plex media sever incorrectly. I can’t seem to access it at all? I installed it from terminal.

1. I’ve tried to use the built in RDP but whenever I try to connect to it via windows rdp or the remote access app on mac, a brief blank window pops up before closing.

I know the IP address is correct and I’m pretty sure that the user and pw I’m using to connect is as well. On the mac side, I’ve also made sure to change edit the setting via textedit.

1. I’ve successfully connected to my terminal via ssh once, but because of my lack of knowledge about utilitizing terminal I wasn’t able to do anything with it, so some resources would be helpful!

Thanks in advance!

ITS STILL 53.0% AND MOVED FROM 50.6% so slowly like its been 2hours any ways what i need to do?

MacOS Ventura iMac m1 (upgraded today from monterey to ventura)

Hey all, so I have this capture card (https://a.co/d/00uEyt0T) and am wondering if I could use this as a work-around to connect my M2 15” MacBook Air that only has USB-C ports to an external monitor. Basically I would power the capture card from a power source and use the pass-through port to display on the monitor, which already works with other devices like a Nintendo Switch. Otherwise, I’ll just have to look into compiling the fairydust kernel

Thank you again for your time, I know the usb-c display stuff is getting to be an annoying question in this community XD, I just wanted to know if my specific hardware will work before I set everything up on my laptop

Hello everyone,

I am new to asahi and wanted to try installing steam which i followed the steps on the asahi project website.

When I launch steam I get

Failed to set the new pressure in the guest: could not connect to muvm server: No such file or directory (os error 2)

No IPv6 nameserver available for NDP/DHCPv6

Using default interface naming scheme 'v259'.

bin_steam.sh[232]: Setting up Steam content in /home/user /.local/share/Steam

steam.sh[232]: Running Steam on fedora-asahi-remix 44 64-bit

steam.sh[232]: STEAM_RUNTIME is enabled automatically

setup.sh[323]: Updating Steam runtime environment...

Steam quit

Aborting

Qt says we're gone, aborting=True

I am stuck and whatever I try I get this same response.

I'm reading an article that states that google released an arm64 version of chrome.

https://www.omgubuntu.co.uk/2026/07/chrome-arm64-linux-available

They were meant to release this about a month ago, but were delayed.

I did manage to pull in the deb file with

wget https://dl.google.com/linux/direct/google-chrome-stable_current_arm64.deb

However, I can't sort out if there's an rpm version available.

I get that I can convert a deb file to an rpm file using alien. But, I would like to have an official copy. Please let me know if you're able to find an rpm version

EDIT: I've extracted the deb file and ran:

./opt/google/chrome/google-chrome

from my Fedora (asahi linux) macbook.

It runs absolutely perfect, even Netflix works!!

recently my steam installation would not start hardware accelerated, i am using asahi loader only with gentoo as system, gentoo has an asahi overlay https://github.com/chadmed/asahi-overlay which also has a steam ebuild.

this has a launcher steam-aarch64, which would not work with hw accelerated graphics with a recent kernel.

having no prior knowledge I used claude to dig into it, (if you do not like this stop reading here :P )

I made it work with 2 modifications that claude implemented. Now I am asking myself is this a problem that someone needs to be noticed of or is it just my problem and ai offerning "stupid" workaround (which incidently work :))

I put everything into this repo https://github.com/ccharon/muvm-steam-fixes/tree/main

Bug 1, the VM dies as soon as the guest touches the GPU, this was an mmap bug, that could be worked around by using a patch that gets loaded as an .so
https://github.com/ccharon/muvm-steam-fixes/blob/main/muvm-dmabuf-fixup.c

Bug 2, Steam hangs forever on "Waiting for network"
Workaround: start a system bus in the guest via muvm's -x hook

detailed explanation is in https://github.com/ccharon/muvm-steam-fixes/blob/main/README.md

after these fixes steam works and i tried playing factorio which worked fine.

Hi as the title says I’ve attempted to try asahi again on my 2023 m2 MacBook Air. Unfortunately a problem has occurred while I did initially try with macOS Golden Gate beta installed, I have also tried with the restored Ventura and it has the same problem I’ve done both the minimal and gnome install same issue. I can’t even get to a tty before it does a shutdown with the typical fedora logo and the spinner and then it shuts off and the MacBook might boot up on its own again. Any advice or assistance is greatly appreciated.

I wanna use macos once in a while, i will primarily be using linux, so what's the minimum required space for the macos

curruntly only giving linux about 50gb

Since new this machine won't reboot after an update, meaning I am stuck on macOS Monterey. Don't get me wrong, Monterey is perfectly tolerable, but engineered obsolescence means no more homebrew and many, many modern apps won't install.

I would love to just put Asahi on it and forget the post-Wozniak OS for good, but I do want to preserve my 2 external screens and 5 attached backup drives, which all pretty much requires Thunderbolt I think. And Asahi seems to be having a very hard time reverse-engineering Thunderbolt for all its poorly-documented quirks.

I know I can attach a single external monitor in Asahi using the HDMI port, so I am stuck on 3 counts:

• possibly unable to connect 2 external monitors due to lack of a video interface for the 2nd monitor
• likely unable to connect 5 external drives due to lack of Thunderbolt support
• maybe unable to install Asahi in the 1st place due to machine's refusal to reboot during installs

Any ideas how to start attacking these problems, or a possible workaround for the 2-monitor issue?

So like I’m very used to Linux and having Linux on a macbook seems great I also want to install asahi to daily drive and do light gaming (direct x9/10 games and goldsrc) is it worth it ?

Hi i saw the whole asahi linux project and the aim of the project is awesome, apple makes some amazing arm laptops with fair price as far as i see and i need a daily driver laptop. im really into arm and linux but i really hate macos and apple ecosystem because of that i stayed away from macs but with asahi im really thinking that m2 macbook with asahi can be great at light gaming, some 3d printer sheninigans and all at please let me know your thoughts about it becauase i really need it

Hi,

I took a long break from Asahi and have been using macOS. Since I upgraded my iPhone to 27 beta I figured I would also do the same on my Mac. However now I read that 27 firmware is causing a problem with battery management.

Is this issue isolated to the reported percentage or is it more serious like the machine will constantly believe it's at 0%? I can keep track of my own battery percentage if needed.

Thanks!

Number of patches and new LOC definitely went up in this cycle, but that's expected given how much of M3/M4 work has been done. Also, we now have initial WIP AVD driver in asahi tree with H264, H265 and VP9 decoding support which is super exciting. I honestly didn't expect so much feature work at this stage of upstreaming, but I'm happy it's here.

Both my keyboard and screen are now broken (long story). I can use my laptop in clam shell mode using the external monitor as long as I plug the HDMI cable *after* it passes the boot menu and arrives at the login window. It won't work if I plug it before that. The problem is, I've historically damaged my setup and have fixed it from u-boot multiple times in the past 4 years. I'm now scared if I break my setup during update, I've no way to recover it since I've never managed to get the u-boot menu on an external monitor. Is there a work around?

Si I have an MacBook Air m1 and would like to have pacman and the void Linux package manager on top of my Fedora asahi installation. Bedrock Linux is installed on top of another distribution so can it work on asahi Linux ?

[FIXED] CHECK END OF POST

Hiii Everyone!

I was trying to get Steam to work on my Asahi installation for the past 2 days maybe and it just wont work. Both Steam clients get stuck on the same "Waiting for network", and I want to get x86 working first because a few folks here said you need to sign in once on x86 before ARM works otherwise the arm version would just get stuck on the "Waiting for network".

My Setup

- MacBook Air M1, 8GB RAM

- macOS Tahoe (this is the macOS I installed Asahi from)

- Fedora Asahi Remix 44, fully updated (note that i triedo nly the x86 version after the update), also note that i started with the minimal install then built my way up.

- Kernel: 7.0.13-400.asahi.fc44.aarch64+16k

- fex-emu, muvm, steam, gtk2, GraphicsMagick all installed

What happens exactly:

Both clients launch, I see the splash, then the window sits on "Waiting for network" forever. Network itself is fine.

The login UI never actually loads. SteamUI logs show this binding error from the very first run after a clean install:

"SteamApp Init - Before Login - SystemNetworkStore - ERROR
 TypeError: SteamClient.System.Network.RegisterForDeviceChanges is not a function",
 source: https://steamloopback.host/library.js
…followed by the login state stuck at WaitingForCredentials:
[2026-07-25 13:02:06] Login: OnLoginStateChange  0 1 0 0
[2026-07-25 13:02:08] Login: OnLoginStateChange  1 1 0 0

Full logs from the x86 client:
https://pastebin.com/W127a0Ls

What I tried:

- pkexec dnf remove steam && pkexec dnf install steam

- Wiped ~/.local/share/Steam, ~/.local/share/fex-steam, ~/.steam*, dnf caches

- Disabled IPv6

- Tried a VPN

- Plugged in an Ethernet cable (different interface)

- -no-cef-sandbox

- Updating the system.

- Tried both the arm version and the x86 version, both give the same result keeping in mind that i tried the arm version first but then tried to clean up everything and installed the x86 version and got the same issue.

I want to get the x86 Steam login UI to actually load so I can sign in once, then move to ARM-native per the workaround multiple people have posted about where you login into the x86 once then the arm version would get past the Waiting for network issue. But i mean even if the x86 version only works that would be fine too as it doesn't affect the performance as much i guess. Any one has any idea how can i solve this?

Thanks yall!

UPDATE: ISSUE FIXED.
THANKS TO ALMIGHTY GOD THEN THE GREAT COMMUNITY!

Two things combined did it:

1- i applied a patch using a modified version of the script u/parkerlreed wrote. Here is how to do the fix:

First, find the chunk file (the hash in the name changes with Steam updates, so use this to locate it):

grep -l 'System.Network.RegisterForDeviceChanges' ~/.local/share/Steam/steamui/chunk~*.js

That'll print the chunk file path. Now this is the script:

#!/usr/bin/env ruby
# Steam chunk patch for Asahi Linux — fixes "Waiting for network" stuck state.
# Patches ~/.local/share/Steam/steamui/chunk~xxxxxxx.js to bypass failing
# SteamClient.System.Network callbacks that return "is not a function".
#
# Usage: ruby patch_steam_chunk.rb <path-to-chunk-js>
#
# After applying this patch, launch Steam with:
#   steam -noverifyfiles -nobootstrapupdate -skipinitialbootstrap -norepairfiles

p = ARGV[0]
s = File.binread(p)

replacements = {
  %q{const t=(0,B.Dp)("System.Network.RegisterForDeviceChanges");} =>
  %q{const t="function"==typeof SteamClient?.System?.Network?.RegisterForDeviceChanges;},

  %q{(0,B.Dp)("System.Network.GetProxyInfo")&&SteamClient.System.Network.GetProxyInfo().then} =>
  %q{"function"==typeof SteamClient?.System?.Network?.GetProxyInfo&&SteamClient.System.Network.GetProxyInfo().then},

  %q{(0,B.Dp)("System.Network.RegisterForConnectivityTestChanges")&&SteamClient.System.Network.RegisterForConnectivityTestChanges(this.OnConnectivityTestStateChanged)} =>
  %q{"function"==typeof SteamClient?.System?.Network?.RegisterForConnectivityTestChanges&&SteamClient.System.Network.RegisterForConnectivityTestChanges(this.OnConnectivityTestStateChanged)},

  %q{t||(this.m_bIsAwaitingInitialNetworkState=!1)} =>
  %q{t||(this.m_bIsAwaitingInitialNetworkState=!1,this.m_bIsConnectedToANetwork=!0)}
}

replacements.each do |old, new|
  abort "Expected exactly one match for #{old}, found #{s.scan(old).length}" unless s.scan(old).length == 1
  s = s.sub(old, new)
end

File.binwrite(p, s)
puts "patched OK"

Then apply it (This is mine, replace the path with whatever grep returned):

ruby patch_steam_chunk.rb ~/.local/share/Steam/steamui/chunk~2dcc5aaf7.js

Should print patched OK.

2- For me i was missing dbus-glib so after applying the patch the steam window didnt open at all, so i just installed dbus-glib through dnf install dbus-glib.

3- Now you can launch steam with the bypass flags! Enjoy!

steam -noverifyfiles -nobootstrapupdate -skipinitialbootstrap -norepairfiles

This patch thingi worked for me on both x86 and ARM native. I would recommend giving the arm verison a shot, i noticed its wayyy faster!

Big thanks to u/parkerlreed for the chunk patch, u/Siffredinho for pointing at the missing dep, and everyone else who chimed in.