Asahi Linux, the community project bringing Linux to Apple silicon Macs, has extended official support to M3-based machines. The support is real but partial: core hardware works, several subsystems remain incomplete, and installation carries conditions.
Key takeaways
- Asahi Linux is a community-driven effort to run a mainline-based Linux distribution on Macs built around Apple’s own ARM-based processors, rather than Intel chips.
- Official support for a Mac generation in Asahi terms means the installer will run and a documented set of hardware functions, not that every peripheral and power-management feature is finished.
- Support arriving for a newer chip generation typically lags the hardware’s release by a considerable period, because almost every driver has to be reverse-engineered without vendor documentation.
- Known gaps on newly supported machines have historically included things like certain camera, microphone, display-output and sleep behaviours, so prospective users should read the project’s own feature matrix before installing.
- Installing Asahi does not require disabling Apple’s secure boot entirely or erasing macOS, but it does repartition the internal drive, which makes a verified backup essential.
What is actually happening
The Asahi Linux project has announced that Macs based on Apple’s M3 generation of chips are now within its officially supported hardware set. In practice, that means the project’s installer recognises those machines, a supported kernel and userspace can be installed alongside macOS, and the resulting system boots and runs on real hardware without requiring users to assemble patches themselves.
It is important to read “official support” the way the project uses the term. Asahi maintains a distinction between machines it has never targeted, machines where work is experimental, and machines that have crossed a threshold where installation is documented and the basic experience is expected to work. Crossing that threshold does not mean feature parity with macOS on the same laptop, and it does not mean parity with Asahi’s own support level on earlier chip generations, which have had years of additional driver work behind them.
The accompanying caveats are the substance of the announcement rather than a footnote. Newly supported hardware generations in this project have consistently shipped with a list of subsystems that are missing, partially working, or known to misbehave. The correct source for the current state of any specific model is the project’s own hardware feature table, which is updated as drivers land.
Why this is in the news now
Two things make an announcement like this notable. The first is timing: Apple silicon Macs have been on the market for several years and multiple chip generations have shipped, so each new generation Asahi covers closes part of a gap between the machines people actually own and the machines Linux runs well on. The second is difficulty. Apple does not publish the hardware documentation that would normally let an operating system be ported to a new platform, so support has to be produced through reverse-engineering — observing how macOS drives the hardware and rebuilding equivalent drivers from scratch.
That combination is why the story circulates on developer-oriented forums rather than mainstream technology press. The interest is less “Linux runs on a laptop” and more that a volunteer project has reconstructed working drivers for a closed platform, and has done so in a form that is contributed upstream to the mainline Linux kernel rather than kept as a permanent private fork.
The background a newcomer needs
When Apple moved its Mac line from Intel processors to its own ARM-based designs, the existing body of Linux support for Macs stopped applying. An Intel Mac is, from Linux’s point of view, largely a standard PC with standard buses and firmware conventions. An Apple silicon Mac is a custom system-on-chip with Apple’s own boot process, its own interrupt controller, its own display and GPU blocks, and peripherals connected in ways that no existing Linux driver understood.
Apple’s boot architecture does permit third-party operating systems: the machines can boot code that is not signed by Apple, and each installed OS gets its own security policy without weakening the policy applied to macOS. That deliberate allowance is what makes Asahi possible at all. What Apple does not provide is documentation, driver source, or firmware blobs designed for a non-Apple OS. Everything from storage controllers to power management has therefore been written by the project.
The project’s stated approach is to upstream its work. Rather than shipping a permanently patched kernel, drivers are submitted to the mainline Linux kernel and to the relevant graphics and userspace components, so that in time a standard distribution can boot these machines without Asahi-specific patches. This is slower than maintaining a fork, but it is why work done for one chip generation partially carries over to the next.
Who is affected and how
For owners of M3-based Macs who want Linux on the metal, this is the difference between an unsupported experiment and a documented installation path. That group includes developers who prefer a Linux toolchain, people who need Linux-specific software, and users who want to keep hardware running after vendor OS updates stop arriving.
For people who mainly want Linux applications rather than a Linux machine, the calculus is different. Virtualisation on macOS runs ARM Linux distributions at near-native speed for most workloads and does not touch the disk layout or the boot process. Containers cover a large share of development use cases. Asahi is most compelling when the requirement is the operating system itself — direct hardware access, a Linux desktop session, or kernel-level work.
For the wider Linux ecosystem, the effect is indirect but real. Drivers written for Apple silicon land in the mainline kernel and in graphics stacks used far beyond Macs, and the project’s work on areas such as ARM system support and graphics conformance has value independent of the specific machines.
Where informed people disagree
There is genuine disagreement about whether installing Asahi on a current machine is sensible. One view holds that a documented, upstream-oriented port on capable hardware is worth the rough edges, and that early adopters generate the bug reports that close the remaining gaps. The opposing view is that a laptop is a daily tool, and that missing sleep behaviour or an unreliable peripheral is disqualifying regardless of how impressive the engineering is.
A second disagreement concerns sustainability. Reverse-engineering a moving target depends on a small number of highly specialised contributors, and each new chip generation restarts part of the work. Some observers regard this as a structural fragility; others point to the upstreaming strategy as precisely the mitigation, since code in the mainline kernel outlives any individual contributor’s involvement.
There is also debate about how to describe support levels. Terms like “supported”, “usable” and “daily driver” are used inconsistently across community discussion, and a machine that one person considers ready may fail another’s requirements outright. The project’s own feature tables are more informative than any summary label.
The practical implications
If you are considering an installation, the sequence matters more than the enthusiasm. Take a full backup first and verify it restores, because the installation repartitions the internal drive and partition operations can fail. Update macOS to a version the project lists as compatible, since the installer depends on Apple’s own firmware and boot tooling.
Read the hardware feature table for your exact model before starting, not a general page about the project — support differs between machines that share a chip generation. Expect to keep macOS installed on the same drive; firmware updates are still delivered through it, and dual-booting is the normal configuration rather than a compromise.
Finally, treat the caveat list as a decision input. If a subsystem you depend on daily is listed as incomplete, the honest conclusion is to wait rather than to hope. Support for a hardware generation is a starting point, and gaps close over months.
What to watch next
The signals worth following are the project’s hardware feature tables, which show which subsystems move from missing to working; the flow of drivers into mainline kernel releases, which determines when ordinary distributions can boot these machines unaided; and the state of the graphics stack, historically among the slowest components to mature.
Also worth watching is how quickly support arrives for chip generations released after M3, since that gap indicates whether the project’s tooling has made each successive port faster. None of these timelines are announced in advance, and the project has generally declined to give dates for unfinished work.
Frequently asked questions
Does installing Asahi Linux delete macOS?
No. The standard installation shrinks the existing macOS partition and installs Linux alongside it, leaving macOS bootable. Keeping macOS is in fact recommended, because Apple’s firmware updates are delivered through it. That said, repartitioning a drive is never risk-free, so a complete and verified backup should be made before starting. The installer also requires a macOS version the project considers compatible.
Does Asahi Linux require disabling Apple’s security features?
Not in the way that phrase usually implies. Apple silicon Macs support per-operating-system security policies, so installing a third-party OS with a reduced policy does not weaken the policy protecting the macOS installation. The machines are designed to boot non-Apple code. What is absent is vendor documentation and drivers, not permission — which is why the project’s work is reverse-engineering rather than circumvention.
Is Asahi Linux ready to use as a main operating system?
That depends entirely on which machine and which features you need. On earlier Apple silicon generations, with years of driver work behind them, many people use it daily. On a newly supported generation, some subsystems are typically incomplete. There is no single answer; the project publishes per-model feature tables showing what works, and those tables are the only reliable basis for the decision.
Why does Linux support for Apple silicon take so long?
Because almost nothing can be reused. Apple’s chips use custom interrupt controllers, custom GPU designs, a custom boot process and non-standard peripheral wiring, and Apple publishes no hardware documentation for them. Each driver has to be reconstructed by observing how macOS operates the hardware. Work on one chip generation carries partly over to the next, but every generation introduces changes that must be identified and handled again.
Can I run Linux applications on a Mac without installing Asahi?
Yes, and for many people that is the better option. Virtualisation software runs ARM Linux distributions on macOS with good performance for typical development work, and container tooling covers most build-and-test workflows. Asahi is the right choice when you need the operating system itself — a Linux desktop session, direct hardware access, or kernel-level development — rather than access to Linux software.
What does “official support with caveats” actually mean?
It means the installer handles the machine, installation is documented, and a defined set of hardware works, while a known list of subsystems remains incomplete or unreliable. It is a threshold, not a completion. The caveat list is published alongside the support announcement and is the substantive part of it. Anyone evaluating the machine should read that list rather than the headline support status.
Sources and further reading
- The Asahi Linux project’s own website and documentation, which publishes per-model hardware feature tables and installation instructions.
- Mainline Linux kernel release notes and changelogs, where drivers for Apple silicon platforms appear as they are merged.
- Hacker News discussion threads on the announcement, useful for practitioner accounts but not for verified fact.
- Apple’s published developer and platform security documentation, for the boot and security-policy model that permits third-party operating systems.
Surfaced from the hackernews signal “linux port hardware support”. AI-assisted draft, editorially reviewed.
