You bought an M-series Mac and want Fedora
You just unboxed a MacBook with an M2 or M3 chip. You want to run Fedora Workstation, but the standard ISO refuses to boot. You find a project called Asahi Linux, assume it is a bootloader or a dual-boot manager, and try to install it alongside macOS. The installer wipes your drive instead. The confusion is understandable. Apple Silicon Macs do not run standard x86_64 Fedora images. They also do not support traditional dual-boot setups. Asahi Linux is not a tool you install on top of macOS. It is a hardware porting project that reverse-engineers Apple's proprietary firmware and builds a custom Fedora spin called Fedora Asahi Remix. You are not installing Fedora on your Mac. You are replacing macOS with a Fedora system that speaks Apple's hardware language.
Back up your files before you touch the installer. A botched partition layout can leave you unable to boot either operating system. Run this from a known-good USB drive first if you can.
What is actually happening under the hood
Standard Fedora ships for x86_64 and a handful of ARM64 server platforms. Apple Silicon uses a custom ARM64 architecture with tightly integrated controllers for graphics, audio, networking, and power management. Apple does not publish driver documentation. The Asahi project reads the kernel, traces the firmware calls, and writes open-source drivers that replace the closed macOS stack. Those drivers get merged into a custom kernel, which then boots a Fedora userland. The result is Fedora Asahi Remix. It uses the same package manager, the same SELinux policies, and the same GNOME desktop as standard Fedora. The difference lives in the kernel and the firmware layer. You get a native Linux experience, not a compatibility shim.
Think of it like translating a book. Standard Fedora is written in English. Apple Silicon hardware only understands a specific dialect of French. Asahi Linux is the translation team. They do not give you a dictionary to read the original book. They rewrite the entire text in the dialect the hardware expects. When you boot the Remix ISO, you are loading that translated system. The kernel module stack, the initramfs, and the UEFI bootloader are all rebuilt to match Apple's hardware expectations. Standard Fedora packages install normally on top of that foundation.
Read the kernel changelog before you update. Driver support moves fast, but regressions happen.
Preparing the installation media
You need a USB drive with at least sixteen gigabytes of storage. The installer will format it. Download the latest Fedora Asahi Remix ISO from the official Asahi Linux website. Verify the checksum before writing it to disk. A corrupted image will fail to boot and leave you staring at a black screen. Apple Silicon Macs are strict about UEFI signature validation. A broken boot sector will not even appear in the startup options menu.
Here is how to write the image to your USB drive using the terminal. Replace /dev/sdX with your actual device identifier. Run lsblk first to identify the correct drive. Do not guess.
# Verify the target USB device. Replace sdX with your actual drive letter.
lsblk
# Write the ISO directly to the block device. bs=4M speeds up the transfer.
sudo dd if=fedora-asahi-remix.iso of=/dev/sdX bs=4M status=progress conv=fsync
# Sync ensures all buffered data hits the physical media before you unplug.
sync
The dd command does not show a progress bar by default. The status=progress flag prints a live transfer rate. The conv=fsync flag forces a flush to disk. This prevents partial writes that corrupt the boot sector. If you prefer a graphical tool, Fedora Media Writer handles the checksum verification and block alignment automatically. The terminal method gives you explicit control over the write process.
Check the USB drive with lsblk again. The filesystem should mount as FEDORA-ASAHIXX. If it shows as unformatted or raw, the write failed. Start over.
Booting and running the installer
Shut down your Mac completely. Insert the USB drive. Press and hold the power button until you see the startup options screen. You will see a list of drives and a gear icon. Select the USB drive. If the screen stays black, hold the power button again until the options appear. The Asahi bootloader sometimes takes a few seconds to initialize the display controller. Apple Silicon uses a different firmware handshake than standard UEFI machines. The bootloader waits for the GPU controller to acknowledge the display pipeline before rendering the menu.
The installer launches a graphical environment. It detects your hardware, partitions the drive, and prepares the Fedora Asahi Remix environment. Select your keyboard layout, connect to Wi-Fi, and choose the installation destination. The installer will offer to erase the entire disk. This is expected. Apple Silicon does not support GRUB dual-booting yet. The installer formats the drive with APFS-compatible partitioning for the recovery environment, then lays down Btrfs or XFS for the root filesystem. Choose Btrfs if you want native snapshots. Choose XFS if you prefer a traditional layout.
# After installation, verify the root filesystem type before rebooting.
# This confirms the installer applied your partition choice correctly.
df -T /
# Check that the Asahi kernel is loaded and matches the expected version.
uname -r
# List loaded kernel modules to confirm Apple-specific drivers are active.
lsmod | grep -i apple
The installer will prompt you to reboot. Remove the USB drive when prompted. The system will boot into the Asahi bootloader, then hand off to the Fedora kernel. You will see the standard Fedora login screen.
Trust the partitioner. Manual GPT edits on Apple Silicon break the recovery partition chain.
Verifying the installation
Log in and open a terminal. The first thing you should check is the kernel version. Fedora Asahi Remix ships with a custom kernel that includes the reverse-engineered drivers. Run uname -r and look for the -asahi suffix. If you see a standard Fedora kernel string, the system booted the wrong image or the bootloader configuration is broken.
Check the hardware detection. Apple Silicon integrates the GPU, audio, and networking into a single complex controller. The Asahi drivers expose these as separate kernel modules. Run lspci and lsusb to verify the system sees the hardware. Run dmesg | grep -i apple to see how the kernel initialized the drivers. You should see messages about the Apple GPU, audio controller, and power management subsystem.
# Check the journal for any hardware initialization failures.
# The -xe flags add explanatory context and jump to the end of the log.
journalctl -xe | grep -i "failed\|error\|warning"
# Verify that the network interface is up and has an IP address.
ip addr show
# Confirm SELinux is enforcing. Asahi Remix ships with full SELinux support.
getenforce
If getenforce returns Enforcing, your security policy is active. If it returns Permissive or Disabled, check /etc/selinux/config. The Asahi project maintains SELinux policies for the custom drivers. Do not disable SELinux to fix a missing icon or a broken audio stream. Fix the policy or report the bug. SELinux denials show up in journalctl -t setroubleshoot with a one-line summary. Read those before disabling SELinux.
Run journalctl -xe first. Read the actual error before guessing.
Common pitfalls and what the error looks like
The most common mistake is trying to dual boot. The Asahi installer will not offer a "install alongside macOS" option. If you force a partition layout that keeps the APFS volume, the bootloader will fail to chain-load macOS, and you will lose access to both operating systems. The installer prints a clear warning before formatting. Read it. Back up your Time Machine data or export your files to an external drive before touching the destination disk.
Another frequent issue is expecting full GPU acceleration on day one. The Asahi project develops drivers incrementally. Some M-series chips have full Vulkan support. Others still rely on software rendering for certain workloads. If your desktop feels sluggish, check the GPU status. Run glxinfo | grep "OpenGL renderer". If it says llvmpipe, the system is using CPU rendering. This is normal for newer chips that are still in the driver development cycle. Wait for the next kernel update.
You might also encounter Wi-Fi dropouts. Apple uses a custom firmware blob for the wireless controller. The Asahi project bundles a stripped-down version that complies with licensing restrictions. If your connection drops, check the firmware status. Run dmesg | grep -i firmware. If the firmware fails to load, the network interface will fall back to a limited mode. Reboot and try a different USB port during installation. Sometimes the installer fails to copy the firmware partition correctly.
The dnf upgrade command will refuse to proceed and print Error: Transaction test error: package kernel-asahi conflicts with kernel. The conflict is intentional. The Asahi kernel replaces the standard kernel. Do not force the transaction. Remove the standard kernel package first.
Maintenance and updates
Fedora Asahi Remix follows the same update cycle as standard Fedora. The package manager is dnf. The kernel updates come through the kernel-asahi package. Run dnf upgrade --refresh weekly to pull the latest drivers and security patches. The --refresh flag forces dnf to check the mirror metadata before calculating the transaction. This prevents stale cache issues that cause dependency conflicts. Fedora's release cadence is six months. The N-2 release goes EOL when N+1 ships. Plan upgrades on that cycle.
# Refresh metadata and apply all available updates.
sudo dnf upgrade --refresh
# Reboot after kernel updates. The Asahi bootloader detects the new kernel automatically.
sudo reboot
# Verify the new kernel is active after login.
uname -r
The bootloader configuration lives in /boot/efi/EFI/fedora/. Do not edit files in /usr/lib/. Those files ship with the packages and will be overwritten on the next update. If you need to modify boot parameters, create a drop-in file in /etc/default/grub.d/ or use the Asahi bootloader configuration tool. The project provides a web-based configuration panel that writes the correct UEFI entries. Manual edits drift. Snapshots stay.
systemctl status <unit> shows recent log lines AND state in one view. Always check status before restart.
When to use Fedora Asahi Remix versus alternatives
Use Fedora Asahi Remix when you want a native Linux desktop on Apple Silicon hardware. Use standard Fedora Workstation when you are running x86_64 servers or legacy desktops with broad hardware support. Use macOS when you depend on closed-source creative tools or require seamless iCloud integration. Use a virtual machine when you need to test Fedora packages without touching the host drive. Stay on the Asahi Remix if you are comfortable tracking kernel updates and reporting driver bugs. Switch to a standard ARM64 Fedora image only if you are running a Raspberry Pi or a generic ARM server.
Reboot before you debug. Half the time the symptom is gone.