HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
AsahiLinux
docs
HTML2020–2026
AsahiLinux / docs

docs

Asahi Linux documentation

88Distinct people
111Mentions
1Explicit recommenders
2.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Asahi Linux documentation

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

marcan of the Asahi Linux project got into a discussion on reddit about this, and says that when it comes to hardware, you just can’t know. > I can't prove the absence of a…

adamomada used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year111 dated mentions

Observed mentions: 2020-12-30 09:47:00 UTC to 2026-04-23 11:53:56 UTC.

0102030402020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 21 mentions; 4 submissions, 17 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 31 mentions; 3 submissions, 28 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 43 mentions; 2 submissions, 41 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 13 mentions; 2 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC110
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC21417
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC31328
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC43241
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC13211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC211

From the project README

An excerpt from the repository, fetched Nov 12, 2026.

Read the project’s introduction
Asahi Linux documentation repository This is the Asahi Linux documentation repository. Documentation structure Our documentation is organised into categories. alt: Alternative operating system/Linux distribution support documentation should go here. fw: Documentation on vendor-controlled firmware and firmware interfaces should go here. hw: Any documentation related to hardware belongs here. This is further split into subcategories: cpu: Application processor documentation devices: Documentation relating to specific Mac models peripherals: hardware found in Apple Silicon Macs but not the SoC itself soc: hardware blocks integrated into Apple Silicon SoCs platform: Documentation that applies across the Apple Silicon platform project: Project admin documents and stuff unrelated to hardware or software sw: Documentation for non-firmware software Usage The site is generated using Zensical. Zensical is installed as a Python package. If your distro does not package it, it is available via pip. To build the docs locally for testing, simply install Zensical and run $ zensical serve The website is rebuilt by the CI on every commit and served via GitHub Pages.
Read the full README on GitHub

What Hacker News says

43 sources
> They don't support variations of software at all. They support the hardware. [...] Asahi does not need to support applications at all. From their FAQ page[1]: > We will eventually release a remix of Arch Linux ARM, packaged for installation by end-users, as a distribution of the same name. The majority of the work resides in hardware support, drivers, and tools, and it will be upstreamed to the relevant projects. The distribution will be a convenient package for easy installation by end-users and give them access to bleeding-edge versions of the software we develop. As distro maintainers, it is their job to make sure the applications they package work on the hardware they support. This includes submitting patches upstream when that is not the case, as application maintainers likely wouldn't want to support such a niche environment direc
Read the rest
tly. So, yes, they rely on volunteers to fix issues, but they will likely have to support many applications themselves. There is still a lot of broken software, as this list[2] is surely not exhaustive. Regardless, all this amounts to less choice of software for the user. The Asahi team has already decided to stop supporting Xorg, and say what you will about Xorg, there will be many applications they realistically can't or won't support for whatever reason. > Same deal for any other hardware manufacturer. [...] Really not much different to other hardware manufacturers since Linux started. No, it's very different. First of all, the amount of Linux hackers who volunteered to reverse engineer the wide variety of hardware was orders of magnitude larger than the Asahi team. Even if they limit the amount of devices they support, modern computers are far more complex than in the early days of Linux. Regardless of how talented the Asahi team is, maintaining all the hardware of a modern computer is a sisyphean task for a small group of volunteers. Secondly, hardware manufacturers could see the benefit of getting their hardware to run in Linux, and many eventually took over support from volunteers. Apple has shown no interest in doing so, and has historically been hostile to open source. > Asahi devs have made it clear that Apple has chosen to avoid blocking installation of other operating systems. The fact they allow installation of other operating systems today, doesn't mean that this decision couldn't change in the future. Services are a large part of their business, and allowing a group of hackers to use their hardware without being part of their software ecosystem may seem like a non-issue today, but if this group grows larger assuming projects like Asahi are successful, this might become a considerable loss of income which wouldn't be in their best interest. > Apple has no issue with it. Can you point me to an official ackgnowledgment of Asahi Linux by Apple? Or any indication that leaving this door open was a sign of good will, instead of a lack of interest in closing it? What makes you think they wouldn't eventually lock down Macs in the same way they do iPhones and iPads? > ARM is a stable well supported platform for Linux It's really not. A lot of software works, but when it doesn't, the user is SOL. As you can see on their Broken Software page[2], the major issue is precisely with AArch64 support. This should improve eventually, and Asahi is certainly a torchbearer in this scenario, but today it's yet another hurdle of using Apple hardware. [1]: https://asahilinux.org/about/#is-this-a-linux-distribution [2]: https://github.com/AsahiLinux/docs/wiki/Broken-Software
In Tuxedo Pulse Gen 3
The open bootloader didn't magically appear one night in Apple's git repository. It boots in a notably different way than iOS machines do, and has some (AFAICT) pretty unique capabilities, including a fully-verified signed-boot of macOS partitions, while allowing third-party kernels at the same time. Asahi's "Introduction to Apple Silicon" [0], and specifically "Security modes, Boot Policies, and machine ownership" paragraph outlines some of that, Apple's "Platform Security" [1] whitepaper does too. Asahi's docs also explicitly state the same thing [2]. If you still don't think that shows significant amount of work and care were put into deliberately allowing third-party OS's to work on those machines, I don't think I can convince you otherwise. [0]: https://github.com/AsahiLinux/docs/wiki/Introduction-to-Appl... [1]: https://support.appl
Read the rest
In The first conformant M1 GPU driver
Thanks. How does Apple bootstrap the system in the first place when inserting a blank SSD? Or perhaps you bought a replacement part? I don't see how that could be done if it is true—that the system is bricked/unrecoverable if the macos partition is lost. Surely it can boot from USB or something? Perhaps not, this wiki page linked above implies the iboot can't handle usb or external storage: https://github.com/AsahiLinux/docs/wiki/M1-vs.-PC-Boot
In Fedora Asahi Remix first impressions

Showing the 15 most recent of 43 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.