ARM64 narrows the search
A filename containing arm64 or aarch64 identifies a 64-bit ARM target, but does not tell you which machine to write it to. A processor executing the right instructions and a complete computer booting an image with working peripherals are separate requirements.
A useful sequence is to choose the operating system and architecture, identify the exact device, and then check the image's purpose and installation instructions. If the download page does not mention your hardware, consult its platform directory and maintainers' guidance rather than repeatedly trying similarly named images.
Firmware and boot methods differ
Fedora's ARM installation documentation distinguishes machines meeting standard system and boot requirements from image-writing workflows that require a particular target board. AArch64 systems are expected to provide basic UEFI support, whether through system firmware or platform-specific boot components.
A complete disk image for a development board and an installation ISO for a standard platform are therefore not interchangeable just because both target ARM64. Match the manufacturer's firmware guidance to the distribution's instructions, including the conditions for booting from USB, a memory card or another device.
Booting is not the end of device support
The kernel must also support the display, storage, network and other hardware. Ubuntu's Snapdragon documentation discusses device trees, firmware and model-specific issues separately. Reaching the installer does not establish that all functions will be available afterward.
If you get a black screen or no network, record the stage at which it happens. Firmware failing to recognize a boot device and Wi-Fi failing after reaching the desktop need different investigations. Check the download's integrity, then look for issues on the same model.
Identify the kind of image
Read its intended use. Desktop installation media, cloud images, virtual-machine disks and development-board images may all carry ARM64 labels while targeting different environments. Even within one distribution, instructions for one environment are not automatically valid for another.
For a preview or Concept image, read the project's stability and support statements. An image containing additional platform patches may also use a different update source. Save its download page and project instructions so you know which maintenance path to follow later.
Check both the file and its suitability
Start at the distribution's official download page and keep the complete filename, release and verification information. Ubuntu's verification tutorial distinguishes authenticating the checksum list from checking the ISO's SHA-256 integrity. These establish file identity and a correct download; they do not establish hardware compatibility.
Before creating media, confirm the destination device and capacity again and back up anything on it. Never reuse a tutorial's disk identifier without checking your own computer. A valid checksum does not replace the device support instructions: the file and the target each need verification.
When explicit support is hard to find
Search the distribution's device directory, the manufacturer's support pages and the project's issue tracker using the complete model. If the only success report is for a similar device, keep your own model marked unverified. Ask the maintainer with model and firmware details before choosing an image or trial method.
A sound choice matches architecture, platform and purpose and includes a clear recovery route. This article explains that selection process. It does not provide a universal installation command for every ARM computer.
Sources and verification
This article draws on published documentation and editorial guidance. Unless explicitly stated, it does not report our own hardware tests. Sources checked: September 27, 2026.