Valve and Collabora have released the first public preview of Holo Core, an AArch64 port of Arch Linux intended to underpin SteamOS on the forthcoming Steam Frame headset. For developers, the immediate payoff is practical: source packages, compiled binaries, and an Arm development container are now available for testing and package builds before Valve’s hardware reaches consumers.
Collabora detailed the preview on July 17, while Neowin, GamingOnLinux, and Phoronix independently reported the release. This is not a consumer SteamOS download, a Steam Frame firmware image, or a general-purpose Arm version of Arch Linux. It is an early development foundation—and a visible sign that Valve’s Arm transition for Steam Frame has moved beyond internal build systems.
Holo Core is a pure AArch64 port of the Arch Linux package base that Valve and Collabora are preparing for Steam Frame. AArch64 is the 64-bit Arm architecture used by the headset’s processor, in contrast to the x86-64 hardware underpinning the Steam Deck and conventional Windows gaming PCs.
Valve’s current SteamOS work is rooted in Arch Linux, but upstream Arch does not officially support AArch64. That makes the task considerably more complicated than rebuilding a handful of applications for a different CPU. Valve needs a maintainable operating-system package base that can track a fast-moving rolling distribution while remaining reproducible enough to ship on fixed hardware.
The preview includes prepared package binaries, their source definitions, and a
For the Steam ecosystem, publishing those materials matters more than the availability of a test image. It gives developers, toolchain maintainers, and curious Linux users a way to inspect the platform Valve is assembling rather than waiting for an opaque finished product.
That detail explains why Valve is not simply consuming an existing Arm Linux distribution or treating the effort as a conventional cross-compilation project. Every package has dependencies, and those dependencies need compatible versions, build instructions, signing information, patches, and a valid order in which to be built.
Collabora says the published preview is tied to a snapshot of Arch Linux’s package-state repository from November 18, 2025, with necessary modifications for AArch64. Pinning that starting point is important. A rolling-release distribution continuously changes package revisions and dependency relationships; trying to assemble a whole new architecture against a moving target without a known-good snapshot is an effective way to produce build failures that cannot be reproduced later.
The engineering problem is therefore split in two:
That makes Holo Core a more consequential project than a niche headset port. If the team can reliably calculate build order, preserve an internally consistent dependency set, and regenerate packages across a rolling distribution, it will have solved much of the unglamorous work needed to make an Arm-based SteamOS sustainable.
The release also signals a degree of confidence in the build machinery. Exposing source packages and containers invites outside inspection. Developers can identify package gaps, test whether their build workflows hold up on Arm, and report failures before Valve is dealing with consumer support cases.
There is a Windows-adjacent implication here, too. Steam Frame’s software story will rely on making a substantial existing PC game ecosystem work on an Arm-powered Linux device. Native Linux Arm titles will be the least complicated part of that equation; games and middleware built around Windows and x86-64 assumptions present a larger compatibility and performance challenge. Holo Core does not solve that compatibility layer by itself, but it supplies the operating-system substrate on which Valve’s broader Steam, SteamVR, graphics-driver, and translation work must run.
For Windows enthusiasts, the comparison is familiar. Windows on Arm has spent years expanding application compatibility while developers migrate tools and binaries toward native Arm64 support. Valve is facing a comparable transition in gaming, but with an Arch-based Linux stack, a headset form factor, and a PC library whose historical center of gravity remains x86 Windows.
Collabora’s example uses the standard Arch-style
The limitations should temper expectations. Holo Core is not an officially supported replacement for Arch Linux on Raspberry Pi-class hardware, an Arm desktop distribution, or a way to convert a Windows PC into a Steam Frame-like device. Its repository contains a curated package subset, not Arch’s complete catalog, and its purpose remains Steam Frame development and image creation.
Collabora says it ultimately wants to work with the upstream Arch Linux project on a common approach to AArch64 support and automated repeatable builds. That is an aspiration rather than a commitment from Arch itself, and no timeline or upstream integration plan has been announced. Still, the public preview gives that discussion a concrete codebase and toolchain instead of a hypothetical proposal.
What it does establish is that Steam Frame’s OS base is no longer merely a rumored Arm adaptation of SteamOS. There are now inspectable packages, a defined snapshot, an AArch64 container, and a public account of the reproducibility problem Valve and Collabora are trying to solve.
The next meaningful test will be whether Holo Core can stay current as Arch Linux moves, while adding the packages and validation required for real Steam Frame software development. Until then, developers have a new target to build against—and Valve has made its Arm-based SteamOS ambitions considerably more tangible.
That means a typical existing Windows game may rely on both a compatibility layer and CPU-architecture translation before it reaches Steam Frame hardware. Holo Core’s maintained Arm Linux package base is therefore a prerequisite for a substantially broader stack than native Arm applications alone.
Valve also identifies Lepton as an alternative route for developers with native Android Arm64 builds. The new guidance does not change Holo Core’s experimental status, but it makes the practical role of the preview clearer: it is foundational infrastructure for Proton, FEX, Vulkan drivers, and the tools needed to support Windows-centered game libraries on an Arm-based Linux headset.
Collabora detailed the preview on July 17, while Neowin, GamingOnLinux, and Phoronix independently reported the release. This is not a consumer SteamOS download, a Steam Frame firmware image, or a general-purpose Arm version of Arch Linux. It is an early development foundation—and a visible sign that Valve’s Arm transition for Steam Frame has moved beyond internal build systems.
A SteamOS Foundation Moves Into Public View
Holo Core is a pure AArch64 port of the Arch Linux package base that Valve and Collabora are preparing for Steam Frame. AArch64 is the 64-bit Arm architecture used by the headset’s processor, in contrast to the x86-64 hardware underpinning the Steam Deck and conventional Windows gaming PCs.Valve’s current SteamOS work is rooted in Arch Linux, but upstream Arch does not officially support AArch64. That makes the task considerably more complicated than rebuilding a handful of applications for a different CPU. Valve needs a maintainable operating-system package base that can track a fast-moving rolling distribution while remaining reproducible enough to ship on fixed hardware.
The preview includes prepared package binaries, their source definitions, and a
base-devel container. Developers with native Arm Linux hardware can run the environment directly. Those on x86-64 Linux systems can use QEMU user-space emulation with binfmt support through Docker, Podman, or Distrobox—although Collabora cautions that executing AArch64 build tools under emulation will be slower.For the Steam ecosystem, publishing those materials matters more than the availability of a test image. It gives developers, toolchain maintainers, and curious Linux users a way to inspect the platform Valve is assembling rather than waiting for an opaque finished product.
This Is Thousands of Packages, Not a One-Button Recompile
Collabora is explicit that Holo Core has not rebuilt “the entire world” of Arch Linux packages. The initial release covers the package set required for Steam Frame development and operating-system image creation. Yet even that limited objective expands into several thousand runtime and build dependencies.That detail explains why Valve is not simply consuming an existing Arm Linux distribution or treating the effort as a conventional cross-compilation project. Every package has dependencies, and those dependencies need compatible versions, build instructions, signing information, patches, and a valid order in which to be built.
Collabora says the published preview is tied to a snapshot of Arch Linux’s package-state repository from November 18, 2025, with necessary modifications for AArch64. Pinning that starting point is important. A rolling-release distribution continuously changes package revisions and dependency relationships; trying to assemble a whole new architecture against a moving target without a known-good snapshot is an effective way to produce build failures that cannot be reproduced later.
The engineering problem is therefore split in two:
- Holo Core must build recent Arch package versions for an architecture upstream Arch does not formally publish.
- Its infrastructure must determine a valid dependency graph and build order as Arch packages evolve.
The CI Work May Matter More Than the Preview Image
Collabora’s announcement places heavy emphasis on continuous integration, or CI: automated systems that build and validate software as its components change. In this case, the company is attempting to create a CI pipeline that can shadow Arch Linux’s evolution even though Arch itself does not provide official AArch64 infrastructure.That makes Holo Core a more consequential project than a niche headset port. If the team can reliably calculate build order, preserve an internally consistent dependency set, and regenerate packages across a rolling distribution, it will have solved much of the unglamorous work needed to make an Arm-based SteamOS sustainable.
The release also signals a degree of confidence in the build machinery. Exposing source packages and containers invites outside inspection. Developers can identify package gaps, test whether their build workflows hold up on Arm, and report failures before Valve is dealing with consumer support cases.
There is a Windows-adjacent implication here, too. Steam Frame’s software story will rely on making a substantial existing PC game ecosystem work on an Arm-powered Linux device. Native Linux Arm titles will be the least complicated part of that equation; games and middleware built around Windows and x86-64 assumptions present a larger compatibility and performance challenge. Holo Core does not solve that compatibility layer by itself, but it supplies the operating-system substrate on which Valve’s broader Steam, SteamVR, graphics-driver, and translation work must run.
For Windows enthusiasts, the comparison is familiar. Windows on Arm has spent years expanding application compatibility while developers migrate tools and binaries toward native Arm64 support. Valve is facing a comparable transition in gaming, but with an Arch-based Linux stack, a headset form factor, and a PC library whose historical center of gravity remains x86 Windows.
Developers Can Test the Build Path, Not the Finished Device
The most useful near-term audience for Holo Core is likely to be developers maintaining Linux packages, game-engine dependencies, Steam tooling, or native utilities that could be part of a Steam Frame workflow. The container can create an Arm build environment without requiring a physical Steam Frame.Collabora’s example uses the standard Arch-style
makepkg process after importing package-signing keys and entering the development container. That is deliberately lower-level than a consumer-facing SDK. It is meant to validate packages and establish the basics of package production, not to let players install a new headset OS on a spare PC.The limitations should temper expectations. Holo Core is not an officially supported replacement for Arch Linux on Raspberry Pi-class hardware, an Arm desktop distribution, or a way to convert a Windows PC into a Steam Frame-like device. Its repository contains a curated package subset, not Arch’s complete catalog, and its purpose remains Steam Frame development and image creation.
Collabora says it ultimately wants to work with the upstream Arch Linux project on a common approach to AArch64 support and automated repeatable builds. That is an aspiration rather than a commitment from Arch itself, and no timeline or upstream integration plan has been announced. Still, the public preview gives that discussion a concrete codebase and toolchain instead of a hypothetical proposal.
The Next Milestone Is a Maintained Arm SteamOS Stack
Valve has not used this announcement to publish Steam Frame pricing, availability, or new launch timing. The Holo Core preview is a software-infrastructure milestone, not a product launch update.What it does establish is that Steam Frame’s OS base is no longer merely a rumored Arm adaptation of SteamOS. There are now inspectable packages, a defined snapshot, an AArch64 container, and a public account of the reproducibility problem Valve and Collabora are trying to solve.
The next meaningful test will be whether Holo Core can stay current as Arch Linux moves, while adding the packages and validation required for real Steam Frame software development. Until then, developers have a new target to build against—and Valve has made its Arm-based SteamOS ambitions considerably more tangible.
Update: Valve outlines Proton, FEX, and Vulkan path for Windows games on Steam Frame (July 18, 2026)
As reported by 9to5Linux, Valve’s Steamworks guidance now adds important detail about how conventional Windows PC games are expected to reach Steam Frame. For most Windows x86 titles, Valve points developers toward Proton for Windows-to-Linux compatibility alongside FEX, which translates x86 code for the headset’s Arm64 processor. Vulkan is identified as the device’s native graphics API.That means a typical existing Windows game may rely on both a compatibility layer and CPU-architecture translation before it reaches Steam Frame hardware. Holo Core’s maintained Arm Linux package base is therefore a prerequisite for a substantially broader stack than native Arm applications alone.
Valve also identifies Lepton as an alternative route for developers with native Android Arm64 builds. The new guidance does not change Holo Core’s experimental status, but it makes the practical role of the preview clearer: it is foundational infrastructure for Proton, FEX, Vulkan drivers, and the tools needed to support Windows-centered game libraries on an Arm-based Linux headset.
References
- Primary source: Neowin
Published: 2026-07-17T21:38:01+00:00
Valve releases its first Arm-based Arch Linux preview for Steam Frame - Neowin
Valve and Collabora have released the first public preview of Holo Core, the aarch64 Arch Linux port being developed for Steam Frame.
www.neowin.net
- Independent coverage: GamingOnLinux
Published: 2026-07-17T17:31:17+00:00
Collabora announce a preview of Holo Core, an AArch64 port of Arch Linux for Steam Frame | GamingOnLinux
Open source firm Collabora who work with Valve (Steam), just announced a preview of Holo Core - the aarch64 port of Arch Linux for Steam Frame.www.gamingonlinux.com
- Independent coverage: Phoronix
Published: Fri, 17 Jul 2026 15:59:00 GMT
Experimental Build Of Holo Core Published: Arch Linux AArch64 For Valve's Steam Frame - Phoronix
As part of Valve's upcoming Qualcomm-powered Steam Frame headset, Valve has been collaborating with Collabora on the Arch Linux AArch64 base for their platformwww.phoronix.com
- Related coverage: collabora.com
Building an Arch Linux aarch64 port for Holo Core
Explore the Holo Core aarch64 preview, with early binaries, sources, and containers for an Arch Linux-based Arm port backed by reproducible CI tooling.www.collabora.com
- Related coverage: tomshw.it
Last edited:
