arm (aka ARMv4tl, ARMv5tel, ARMv6j, ARMv7a, ...)
Processor compatibility
The arm 32-bit architecture was initially developed 1985 by Acorn Computers and is now part of Arm Holdings portfolio. For details of the various arm subarchitectures, please see the corresponding wikipedia page. Note that in Gentoo arm refers to 32-bit variants; the 64-bit variants can be found as arm64.
Downloads
- Boot media allow you to boot from, e.g., an USB stick or CD and install Gentoo using a Stage.
- A Stage (previously called Stage 3) is a minimal set of Gentoo binaries to build a system in any way possible.
- Containers and Images provide a ready-to-use Gentoo system, e.g. for cloud or virtual machine usage.
- All release files are signed with an official OpenPGP key and distributed via world-wide download mirrors.
Stages
ARMv4tl stage archives
ARMv5tel stage archives
ARMv6j stage archives
Stages (advanced)
musl stage archives
Hardened musl stage archives
For additional information on using musl based Gentoo systems, please see the musl usage guide. Note that users of musl stages will need to be comfortable filing bug reports and sometimes providing patches.
time64 stage archives
The time64 stages of 32-bit glibc architectures are using 64-bit time values to be
year-2038 proof
(details).
This will become the default for Gentoo in the near future, and if you make a new 32-bit
Gentoo installation and are feeling a bit experimental, we recommend using these stages
already.
Switching over an existing installation from 32-bit time values to 64-bit time values
is possible but not entirely trivial; instructions including helper software will
be published soon. This applies to glibc only; musl has already switched to 64-bit time
values in 2020.
Additional links
Download directory (contents, hashes, and signatures)
While our main distribution site https://distfiles.gentoo.org/ is already backed by a CDN, your download speeds may still vary depending on your location. We encourage you to select mirror sites close to you.
All official Gentoo releases are accompanied by an OpenPGP signature. The corresponding keys as well as instructions on how to verify the signatures can be found on the release media signature page.