Setup
The project provides an official Python installer. The steps are very clear and easy to follow without any partitionning knowledge. This is a very neat experience, even easier than booting from a USB stick for Linux installations on Intel.
curl https://alx.sh | sh
Want to see more details about it ? We saved the installer's output below.
I'm very curious...
The big text is separated into smaller chunk at each user interaction.
user@macm2 ~ % curl https://alx.sh | sh
Bootstrapping installer:
Checking version...
Version: v0.8.3
Downloading...
Extracting...
Initializing...
The installer needs to run as root.
Please enter your sudo password if prompted.
Password:
Welcome to the Asahi Linux installer!
This installer will guide you through the process of setting up
Asahi Linux on your Mac.
Please make sure you are familiar with our documentation at:
https://alx.sh/w
Press enter to continue.
Collecting system information...
Product name: MacBook Air (M2, 2022)
SoC: Apple M2
Device class: j413ap
Product type: Mac14,2
Board ID: 0x28
Chip ID: 0x8112
System firmware: mBoot-18000.120.36
Boot UUID: 2B2A9BD4-C332-4ABA-9BCC-642B21D15F60
Boot VGID: 2B2A9BD4-C332-4ABA-9BCC-642B21D15F60
Default boot VGID: 2B2A9BD4-C332-4ABA-9BCC-642B21D15F60
Boot mode: macOS
OS version: 15.7.7 (24G720)
OS restore version: 24.7.720.0.0,0
Main firmware version: 26.5 (25F71)
No Fallback System Firmware / rOS
SFR version: 25.6.71.0.0,0
SystemRecovery version: 25.4.125.0.0,0 (26.3 25D125)
Login user: user
Collecting partition information...
System disk: disk0
Collecting OS information...
Partitions in system disk (disk0):
1: APFS [Macintosh HD] (245.11 GB, 6 volumes)
OS: [B*] [Macintosh HD] macOS v15.7.7 [disk3s1s1, 2B2A9BD4-C332-4ABA-9BCC-642B21D15F60]
2: APFS (System Recovery) (5.37 GB, 2 volumes)
OS: [ ] recoveryOS v26.5 [Primary recoveryOS]
[B ] = Booted OS, [R ] = Booted recovery, [? ] = Unknown
[ *] = Default boot volume
Using OS 'Macintosh HD' (disk3s1s1) for machine authentication.
Choose what to do:
r: Resize an existing partition to make space for a new OS
q: Quit without doing anything
» Action (r): r
We're going to resize this partition:
APFS [Macintosh HD] (245.11 GB, 6 volumes)
Total size: 245.11 GB
Free space: 218.94 GB
Available space: 180.94 GB
Overhead: 0 B
Minimum new size: 64.17 GB (26.18%)
Enter the new size for your existing partition:
You can enter a size such as '1GB', a fraction such as '50%',
or the word 'min' for the smallest allowable size.
Examples:
30% - 30% to macOS, 70% to the new OS
80GB - 80GB to macOS, the rest to your new OS
min - Shrink macOS as much as (safely) possible
» New size (50%): 50%
Resizing will free up 122.55 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
Started APFS operation
Aligning shrink delta to 122,552,778,752 bytes and targeting a new container size of 122,554,417,152 bytes
Determined the minimum size for the APFS Container to be 27,111,981,056 bytes
Resizing APFS Container designated by APFS Container Reference disk3
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l /dev/disk0s2
Checking the container superblock
Checking the checkpoint with transaction ID 7909068
warning: container has been mounted by APFS version 2811.120.14.0.1, which is newer than 2332.140.13.700.1
warning: disabling overallocation repairs by default; use -o to override
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the encryption key structures
Checking volume /dev/rdisk3s1
Checking the APFS volume superblock
The volume Macintosh HD was formatted by newfs_apfs (1677.41.3.101.1) and last modified by apfs_kext (2332.140.13.700.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking snapshot 1 of 1 (com.apple.os.update-2A1B3A6887F49B150BBDBEB3FADA453426E5218B3A174DF9C1942AB06AF6BA72, transaction ID 7693880)
Checking the fsroot tree
Checking the file extent tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s1 with UUID 0049C376-D980-46F3-BF29-189D92CEF470 appears to be OK
Checking volume /dev/rdisk3s2
Checking the APFS volume superblock
The volume Preboot was formatted by newfs_apfs (2142.140.9) and last modified by apfs_kext (2632.80.1.0.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s2 with UUID 833BCEAE-E574-4C1F-BC82-5F7CE8E2BE85 appears to be OK
Checking volume /dev/rdisk3s3
Checking the APFS volume superblock
The volume Recovery was formatted by newfs_apfs (2142.140.9) and last modified by apfs_kext (2332.140.13.700.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s3 with UUID BA3FA29F-6A2D-4F88-949E-A77F26E42F72 appears to be OK
Checking volume /dev/rdisk3s4
Checking the APFS volume superblock
The volume Update was formatted by newfs_apfs (2142.140.9) and last modified by apfs_kext (2632.80.1.0.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s4 with UUID FB127040-2965-4A34-8111-DF02729CCD29 appears to be OK
Checking volume /dev/rdisk3s5
Checking the APFS volume superblock
The volume Macintosh HD - Data was formatted by mobile_obli (2332.140.13.700.1) and last modified by apfs_kext (2632.80.1.0.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Checking the file key rolling tree
Verifying volume object map space
The volume /dev/rdisk3s5 with UUID 241A3679-64A0-4B76-BC7B-24EDE3BEFBC3 appears to be OK
Checking volume /dev/rdisk3s6
Checking the APFS volume superblock
The volume VM was formatted by apfs_boot_util (2142.140.9) and last modified by apfs_kext (2332.140.13.700.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s6 with UUID C2596BB5-900B-4180-B4BE-B0BF504310F8 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 245,107,195,904 to 122,554,417,152 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
Finished APFS operation
Resize complete. Press enter to continue.
Collecting partition information...
System disk: disk0
Collecting OS information...
Partitions in system disk (disk0):
1: APFS [Macintosh HD] (122.55 GB, 6 volumes)
OS: [B*] [Macintosh HD] macOS v15.7.7 [disk3s1s1, 2B2A9BD4-C332-4ABA-9BCC-642B21D15F60]
2: (free space: 122.55 GB)
3: APFS (System Recovery) (5.37 GB, 2 volumes)
OS: [ ] recoveryOS v26.5 [Primary recoveryOS]
[B ] = Booted OS, [R ] = Booted recovery, [? ] = Unknown
[ *] = Default boot volume
Using OS 'Macintosh HD' (disk3s1s1) for machine authentication.
Choose what to do:
f: Install an OS into free space
r: Resize an existing partition to make space for a new OS
q: Quit without doing anything
» Action (f): f
Choose an OS to install:
1: Fedora Asahi Remix 44 with KDE Plasma
2: Fedora Asahi Remix 44 with GNOME
3: Fedora Asahi Remix 44 Server
4: Fedora Asahi Remix 44 Minimal
5: UEFI environment only (m1n1 + U-Boot + ESP)
» OS: 1
Downloading OS package info...
Minimum required space for this OS: 33.93 GB
Available free space: 122.55 GB
How much space should be allocated to the new OS?
You can enter a size such as '1GB', a fraction such as '50%',
the word 'min' for the smallest allowable size, or
the word 'max' to use all available space.
» New OS size (max): max
The new OS will be allocated 122.55 GB of space,
leaving 458.75 KB of free space.
Enter a name for your OS
» OS name (Fedora Linux with KDE Plasma):
Using macOS 13.5 for OS firmware
Downloading macOS OS package info...
Creating new stub macOS named Fedora Linux with KDE Plasma
Installing stub macOS into disk0s5 (Fedora Linux with KDE Plasma)
Preparing target volumes...
Checking volumes...
Beginning stub OS install...
\
| Setting up System volume...
100.00% (0.00 B/s)
Setting up Data volume...
Setting up Preboot volume...
/ 100.00% (0.00 B/s)s)
Setting up Recovery volume...
\ 100.00% (21.17 MB/s)
Wrapping up...
Stub OS installation complete.
Adding partition EFI (524.29 MB)...
Formatting as FAT...
Adding partition Boot (1.07 GB)...
Adding partition Root (118.45 GB)...
Collecting firmware...
100.00% Installing OS...
\ 100.00% (0.00 B/s)
Copying from esp into disk0s4 partition...
| 100.00% (0.00 B/s)
Copying firmware into disk0s4 partition...
Extracting boot.img into disk0s7 partition...
/ 100.00% (29.04 MB/s)
Extracting root.img into disk0s6 partition...
| 100.00% (36.59 MB/s)
Downloading extra files...
Downloading mozilla-openh264-2.6.0-3.fc44.aarch64.rpm (1/2)...
Downloading openh264-2.6.0-3.fc44.aarch64.rpm (2/2)...
Preparing to finish installation...
Collecting installer data...
To continue the installation, you will need to enter your macOS
admin credentials.
Password for user: ****
Setting the new OS as the default boot volume...
Installation successful!
Install information:
APFS VGID: 638303D5-4738-42D8-888E-1455EBDF82CE
EFI PARTUUID: 9597e084-bcda-4c66-a96a-7a14a2df9099
Help us improve Asahi Linux!
We'd love to know how many people are installing Asahi and on what
kind of hardware. Would you mind sending a one-time installation
report to us?
This will only report what kind of machine you have, the OS you're
installing, basic version info, and the rough install size.
No personally identifiable information (such as serial numbers,
specific partition sizes, etc.) is included. You can view the
exact data that will be sent.
Report your install?
y: Yes
n: No
d: View the data that will be sent
» Choice (y/n/d): d
This is the data that will be sent:
{
# The model code of your device. For example, j274ap means
# 'Mac mini (M1, 2020)'.
"device_class": "j413ap",
# The kind of chip your device has. For example, 0x8103 means Apple M1.
# This is redundant (it is the same for any given device_class), but it
# makes grouping reports by chips instead of devices a bit easier.
"chip_id": "0x8112",
# The macOS version you are installing from. This helps us know how up
# to date people are, so we can decide when to start requiring a newer
# version. The text in parentheses is the build ID, which is the same
# for any given release version of macOS (but varies for betas).
"macos_ver": "15.7.7 (24G720)",
# Your System Firmware version. This is usually the same as the macOS
# version, unless you have multiple macOS installs.
"sfr_ver": "26.5 (25F71)",
# Whether you are installing from macOS or recoveryOS.
"boot_mode": "macOS",
# The OS you selected to install. This lets us know what the most
# popular OS choices are.
"os_name": "Fedora Asahi Remix 44 with KDE Plasma",
# The OS package filename. This tells us the particular OS version that
# was installed.
"os_package": "https://asahilinux-fedora.b-cdn.net/os/fedora-44-kde-202604271600.zip",
# The firmware version used for this specific OS install. This is
# one of a few specific options, since our kernels must support all
# firmware versions used in the wild.
"os_firmware": "13.5",
# The SSD size of your machine, in gigabytes. This helps us gauge how
# painful having to keep a macOS install around is for our users.
"disk_size": 251,
# The fraction of your disk you allocated to your install, rounded to
# 5%. This helps us understand how many people are using Asahi as
# their primary OS, secondary OS, or just trying it out.
"disk_fraction": 0.5,
# Version and configuration information for the installer. This lets us
# know whether you used the official installer or something else.
# The information is the same for everyone who installs using the same
# command line.
"installer": {
"tag": "alx-prod",
"version": "v0.8.3",
"env": {
"INSTALLER_BASE": "https://cdn.asahilinux.org/installer",
"INSTALLER_DATA": "https://github.com/AsahiLinux/asahi-installer-data/raw/prod/data/installer_data.json",
"REPO_BASE": "https://cdn.asahilinux.org"
}
}
}
Report your install?
y: Yes
n: No
d: View the data that will be sent
» Choice (y/n/d): y
Your install has been counted. Thank you! ❤
To be able to boot your new OS, you will need to complete one more step.
Please read the following instructions carefully. Failure to do so
will leave your new installation in an unbootable state.
Press enter to continue.
When the system shuts down, follow these steps:
1. Wait 25 seconds for the system to fully shut down.
2. Press and hold down the power button to power on the system.
* It is important that the system be fully powered off before this step,
and that you press and hold down the button once, not multiple times.
This is required to put the machine into the right mode.
3. Release it once you see 'Loading startup options...' or a spinner.
4. Wait for the volume list to appear.
5. Choose 'Fedora Linux with KDE Plasma'.
6. You will briefly see a 'macOS Recovery' dialog.
* If you are asked to 'Select a volume to recover',
then choose your normal macOS volume and click Next.
You may need to authenticate yourself with your macOS credentials.
7. Once the 'Asahi Linux installer' screen appears, follow the prompts.
If you end up in a bootloop or get a message telling you that macOS needs to
be reinstalled, that means you didn't follow the steps above properly.
Fully shut down your system without doing anything, and try again.
If in trouble, hold down the power button to boot, select macOS, run
this installer again, and choose the 'p' option to retry the process.
Press enter to shut down the system.
Bluetooth disconnect
As of 2026-07-26, I experienced some Bluetooth disconnections happening after the computer would wake up from sleep. My Bluetooth keyboard and mouse would just not be able to connect again...
The solution found on this Reddit post is to remove KDE Connect (if you don't use it):
sudo dnf remove kde-connect
Multimedia codecs
Like for standard Fedora on Intel, you will miss some video codecs. As always, there are available from
TODO continue this