How to Install Linux on an Apple M3 MacBook (2026)

A new mainline Linux kernel just started booting on Apple M3 MacBooks. That is not the same thing as "Linux now runs great on M3 Macs," and if you buy an M3 machine expecting a smooth Fedora or Arch install this week, you are going to be disappointed. Here is what actually changed, what still does not work, and what a realistic install looks like right now.

What "M3 Boots Linux" Actually Means at the Kernel Level

The recent Linux 7.2 point release added the initial bring-up code for M3-generation Apple Silicon into the mainline kernel tree. That is a meaningful milestone, but it is narrower than it sounds. Bring-up support means the kernel can initialize the chip, find memory, and get a console or basic framebuffer working, not that every peripheral on the machine talks to Linux correctly.

This distinction matters because the Asahi Linux project, the volunteer effort responsible for nearly all Apple Silicon Linux support, spent years reverse-engineering Apple's undocumented hardware interfaces for M1 and M2 chips before that work made it into mainline. M3 support follows the same path, just starting later and moving through a kernel community that has gotten stricter about how out-of-tree Apple Silicon patches get merged. Asahi's lead developer, Hector Martin, stepped back from the project's leadership in early 2025 after friction with DRM subsystem maintainers over review and rebasing requirements, and that governance shake-up slowed the pace at which new Apple Silicon patches, including M3 work, moved upstream.

So when you read that M3 MacBooks "can boot Linux for the first time," read it as: the foundation is now in the tree developers actually build from, not as a green light for daily use.

What Works on M3 Right Now, and What Doesn't

Apple's chips bundle GPU, Wi-Fi, audio codecs, and power management into tightly integrated silicon with no public documentation, so every one of those subsystems needs its own reverse-engineering effort. On M1 and M2 Macs, Asahi Linux has closed most of those gaps over several years. M3 is starting that process from a much earlier point.

Here is the realistic breakdown for M3 as of this kernel cycle:

• Working or close to working: basic boot to a console, framebuffer display output, USB-C ports, keyboard and trackpad input through Apple's SPI-based drivers, and NVMe storage access.
• Not working or barely functional: GPU acceleration, Wi-Fi, audio output and input, Thunderbolt/USB4 at full speed, sleep and suspend states, and the Neural Engine.

The GPU gap is the biggest one. Apple redesigned the GPU architecture starting with M3 to add dynamic caching, a hardware feature that changes how the GPU allocates memory for shader execution. Asahi's existing GPU driver, built by reverse-engineering the M1/M2 architecture, does not simply extend to this new design. For more on this, see read about and folks, we have a vibe coded linux distro!.

It requires fresh reverse-engineering work, and that work was still in early stages when this kernel support landed. Expect to run an M3 Linux install with software rendering only, which means a functional but sluggish desktop with no hardware-accelerated graphics.

Wi-Fi and audio face a similar problem: Apple's custom silicon for both uses firmware blobs and initialization sequences that Asahi engineers have to extract and reimplement piece by piece. That work took roughly two to three years for M1 and M2 after those chips shipped. There is no reason to expect M3 will move meaningfully faster, given the smaller pool of contributors working on it.

Which Distros and Projects Actually Support This

Asahi Linux is not a distribution in the traditional sense. It is a set of kernel patches, firmware tooling, and a bootloader chain (m1n1, which hands off to U-Boot) that other distributions build on top of. The project maintains its own installer and ships two primary user-facing options.

Fedora Asahi Remix is the most polished path, offering GNOME and KDE Plasma spins that bundle Asahi's patches with Fedora's package base. It is what the Asahi team recommends for most users because it tracks their patches most closely and gets updates fastest.

Arch Linux ARM users can pull Asahi's packages through a community repository, which gives more control but requires more manual configuration and a higher tolerance for breakage.

Debian and openSUSE both have unofficial or experimental Apple Silicon support tracks maintained by smaller groups of contributors, but neither matches the completeness of the Fedora-based option. Because M3 support just entered mainline, none of these distributions have validated, tested images for M3 machines yet. Anyone installing today is effectively testing patches that haven't had years of shakeout the way M1 support has.

Step-by-Step: What Installing Linux on an M3 MacBook Actually Involves

If you want to try this now, understand that you are signing up for an early-adopter experience, not a weekend dual-boot project with a guaranteed working laptop at the end. Here is what the process looks like in practice.

1. Back up everything. Apple Silicon Macs use a signed boot chain and a shared APFS container between macOS and any other OS you install, and mistakes here can leave the machine unable to boot into either system without a recovery reinstall.

2. Run the installer from macOS. Boot into macOS and open Terminal to run the Asahi Linux installer script directly from the project's site, using a curl command that downloads and executes the installer. This tool handles repartitioning the APFS container, downloading Apple's firmware components needed for the bootloader, and setting up the m1n1/U-Boot chain that lets the machine's boot picker offer Linux as an option alongside macOS.

3. Choose your distribution during the installer's prompts. For M3 machines specifically, expect the installer to flag limited hardware support up front, since the project is transparent about what is and isn't ready.

4. Reboot into the boot picker. After installation, hold the power button to access Apple's native boot picker, since Apple Silicon Macs don't use GRUB or a traditional boot menu the way x86 Linux machines do.

5. Adjust your expectations immediately. No Wi-Fi means you'll need a USB Ethernet adapter or USB Wi-Fi dongle for network access, no audio means silence until that driver work lands, and no GPU acceleration means a workable but visually basic desktop.

Should You Actually Do This Today?

If you own an M1 or M2 MacBook, Asahi Linux is genuinely usable as a daily driver for many workloads, with working GPU acceleration, Wi-Fi, and audio after years of development. M3 is not there. The kernel-level boot support that just landed is the first rung of a ladder Asahi climbed for M1 and M2 over roughly two to three years, and there's no shortcut this time around.

That said, if you like living on the edge of open source hardware support, testing patches, and filing bug reports that actually help move a reverse-engineering project forward, an M3 MacBook running Fedora Asahi Remix right now is a legitimate way to contribute. Just don't plan on using it as your only machine, and don't expect video calls, music playback, or Wi-Fi to work without workarounds. For everyone else, the more sensible move is to bookmark the Asahi Linux project's progress reports and revisit this once GPU and Wi-Fi support for M3 actually ship — based on the pace of past chip generations, that's a matter of years rather than months.