macOS 27 "Golden Gate" Beta Hides Asahi Linux Partitions, Breaking Dual-Boot

Asahi Linux is telling its users to stay away from the macOS 27 "Golden Gate" beta that Apple shipped this week. The reason is straightforward and frustrating: after updating to the beta, the Asahi Linux partition simply disappears from the boot picker. The data is intact, the partition still exists on disk, but the machine refuses to offer it as a boot target.

For anyone running Linux on Apple Silicon, this is the kind of change that turns a working homelab node or development box into a single-OS Mac overnight. If you only have macOS 27 and Asahi installed, and macOS 27 won't surface the Linux partition, you are stuck on macOS until either Apple reverses the behavior or the Asahi Linux project ships a workaround.

What Actually Changed

Apple reworked the boot picker and Startup Disk handling in macOS 27. On Apple Silicon, the boot process is very different from the old Intel Macs and from PC-style UEFI. There is no traditional firmware boot menu you hold a key to reach in the same way. Instead, Apple Silicon Macs use a multi-stage boot chain anchored in the iBoot firmware, and the operating system you can select is governed by signed boot policy stored per-volume.

Asahi Linux works by carving out its own APFS container and installing a custom boot object that the Apple boot picker recognizes as a selectable OS. This is the clever part of the whole project: Asahi never replaces or patches Apple's firmware. It slots into the existing multi-boot mechanism that Apple built for installing multiple macOS versions side by side. When you hold the power button on a supported Mac, the picker enumerates the installed OS entries, and Asahi shows up as one of them.

macOS 27 changes how that enumeration works. The Asahi partition is no longer listed, which strongly suggests Apple altered either the logic that scans for bootable volumes or the policy checks that decide which entries are valid to display. Whether this is an accidental regression or a deliberate tightening of the boot policy is exactly what the project does not yet know.

No Data Loss, But No Boot Either

The important detail for current users is that nothing is being erased. Your Asahi install is still on the drive, untouched. The problem is purely visibility and selectability. That distinction matters because it means a recovery path likely exists once the cause is understood, rather than requiring a full reinstall.

The practical advice from the project is to keep a secondary macOS 26 or earlier installation around. If you boot back into the older macOS, its boot picker behaves the old way and can still see and launch the Asahi partition. This is the same multi-boot capability that makes Asahi possible in the first place, now doing double duty as an escape hatch.

If you have already jumped to macOS 27 Golden Gate as your only macOS and have no older fallback, your options are thin until there is more information. This is the scenario the project is specifically warning people to avoid.

Recommendations For Apple Silicon Linux Users

For anyone running or considering Asahi on Apple Silicon hardware, here is how I would approach the next few weeks:

• Do not install the macOS 27 beta on any machine where Asahi Linux is your working environment. Betas are betas, and this one actively breaks your setup.
• If you run macOS at all alongside Asahi, keep a macOS 26 or earlier install as a dedicated boot fallback. Treat it as part of your recovery toolkit, not as a daily driver.
• Hold any production or homelab Asahi nodes on stable macOS releases. There is no upside to running an OS beta on hardware you depend on, and this incident is a clean illustration of why.
• Watch the Asahi Linux blog and the bug report status before touching Golden Gate.

The project has filed a bug report with Apple over the behavior change and is waiting to hear back. How this resolves will say something about Apple's posture toward third-party operating systems on its silicon. An accidental regression gets fixed in a later beta. A deliberate policy change is a different conversation entirely, and one that the alternative-OS community on Apple hardware has worried about since the M1 first booted Linux.

The Other Half Of The News

There is a brighter item in the same week. Linux 7.2 is set to enable boot support for Apple M3 devices. It is not usable for end users yet, the support is early plumbing rather than a finished daily-driver experience, but it is forward motion on bringing newer Apple Silicon into the fold. The work on M3 enablement and the macOS 27 boot picker problem land at the same time, which captures the ongoing reality of this project: steady progress on hardware support running alongside the constant risk that an Apple software update reshuffles the foundation underneath.

{{IMAGE:2}}

For now the message is simple. If you care about booting Linux on your Mac, skip macOS 27 Golden Gate, keep an older macOS around as insurance, and wait to see what Apple says.