We are happy to announce the availability of Fedora Linux Asahi Remix 45 Beta. This pre-release will bring the freshly announced Fedora Linux 45 Beta to Apple Silicon Macs. We expect to announce general availability of Fedora Linux Asahi Remix 45 in about a month. This will coincide with the overall Fedora Linux 45 release.
Fedora Linux Asahi Remix is developed in close collaboration with the Fedora Asahi SIG and the Asahi Linux project. Fedora Asahi Remix 45 Beta includes all of the Changes from Fedora Linux 45. Notably, this is the first Fedora Asahi Remix release to include out of the box initial support for Apple M3, M3 Pro and M3 Max systems, which are now officially supported by Asahi Linux upstream. The GPU drivers to enable performant 3D acceleration on these M3 systems are not included at this point and will be available via a Mesa update in the future. This release also includes support for hardware accelerated H.264 and VP9 video decoding for all Apple Silicon systems; additionally, Apple M3 systems include support for AV1 decoding.
You can try out Fedora Asahi Remix 45 Beta today by following our installation guide. Existing systems, running Fedora Asahi Remix 43 or 44, can be updated following the usual Fedora upgrade process. Upgrades via Fedora Workstation’s Software application are unfortunately not supported and DNF’s System Upgrade plugin has to be used.
Since this is a beta release, we expect that you may encounter bugs or missing features. Please report any Remix-specific issues in our tracker. You may also reach out in our Discourse forum or our Matrix room for user support.
Start the discussion at discussion.fedoraproject.org
Facts Only
* Fedora Linux Asahi Remix 45 Beta is available.
* This pre-release brings Fedora Linux 45 Beta to Apple Silicon Macs.
* General availability of Fedora Linux Asahi Remix 45 is expected in approximately one month, coinciding with the full Fedora Linux 45 release.
* Fedora Asahi Remix 45 Beta includes all changes from Fedora Linux 45.
* The beta provides initial out-of-the-box support for Apple M3, M3 Pro, and M3 Max systems.
* Apple M3 systems are officially supported by Asahi Linux upstream.
* Support includes hardware accelerated H.264 and VP9 video decoding for all Apple Silicon systems.
* Apple M3 systems also include AV1 decoding support.
* GPU drivers for performant 3D acceleration on M3 systems are not included in this release but will be available via a future Mesa update.
* Existing Fedora Asahi Remix 43 or 44 systems can be updated using the usual Fedora upgrade process, requiring DNF’s System Upgrade plugin.
* Users should report Remix-specific issues in the tracker or forums.
Executive Summary
Full Take
The rollout of a beta designed to introduce new hardware support and driver dependencies creates an immediate tension between access and stability. The core pattern here is the careful staging of feature introduction: foundational compatibility (M3 support) is provided, while performance-critical components (GPU drivers) are deliberately deferred to subsequent updates. This structure suggests a prioritization of achieving broad adoption and initial functional compatibility over immediate peak performance, which is a necessary, though sometimes frustrating, trade-off in open-source development. The requirement for users to utilize the DNF System Upgrade plugin, bypassing standard desktop tools, highlights an intentional architectural divergence—forcing users toward the command-line reality of the underlying system management rather than relying on generalized application interfaces.
This process reflects a common dynamic where forward momentum demands an immediate release, but rigorous engineering necessitates incremental refinement. The implication is that cognitive sovereignty here lies in understanding the pacing: recognizing that 'beta' status means acknowledging known limitations (the missing GPU acceleration) while embracing the tangible progress (new hardware support and media decoding). The challenge for the community is ensuring the communication successfully frames this phased approach not as a delay, but as a controlled progression toward feature maturity.
What assumptions are made about user tolerance for partial features versus full functionality? How does the delayed delivery of GPU drivers influence the perceived value of the initial M3 support? Does deferring performance enhancements necessarily breed distrust if the process is transparently managed?