From Fedora Project Wiki

Installing Fedora on your ARM device.

General process

ARM devices come in both 32-bit and 64-bit variations. ARMv8 is the latest version of the arm architecture and adds 64-bit support in the form of aarch64 mode. Aaarch32 is the armv8 32-bit compatibility mode, which is generally backwards compatible with the previous 32-bit ARMv7. Not all ARMv8 devices support both 64-bit and 32-bit execution so its best to check the specifications on a given piece of hardware.

Fedora's ARM support comes in two flavours. Traditional 32-bit support in the form of armhfp (arm hard float) images which are 32-bit and require hardware floating point support, and aarch64 images which run on 64-bit ARMv8 hardware. Generally armhfp images are installed with a fedora provided uboot documented below in the arm-image-installer section. Aarch64 machines are expected to provide a base level of UEFI support. That support may be baked into the system firmware, or provided by fedora as part of the arm-image-installer's uboot.

Stable Releases

The current stable release for ARMv7 can always be found at the ARM Image landing page

The current stable release for aarch64 can always be found at Alternate Architectures landing page

Branched Development Release

The repository for current development releases:

Rawhide Rolling Release

Rawhide Installation Tree(armhfp)

Rawhide Installation Tree(aarch64)

General Installation instructions for all Releases

Aarch64 SBSA/SBBR compliant hardware

Machines which conform to the standard system architecture and boot requirements can be installed using normal fedora installation methods. Those methods are documented in the version specific installation instructions here

Arm Image Installer

The examples provided here are from a Fedora 31 host and may need to be adjusted depending on your host environment.

Used to deploy disk images for ARMv7hl as well as a limited set of Aarch64 SBCs. Execute the following script as a user with sudo privileges. It will copy the selected disk image and write the appropriate U-Boot for the target hardware platform. Optionally you can also enable and disable SE Linux and remove the root password requirement (allowing log in without completing initial setup). To add a board not listed, simply create a bash scriptlet with the commands needed to copy U-Boot to media and add to the 'boards.d' (/usr/share/arm-image-installer/boards.d) directory.

sudo dnf -y install arm-image-installer
Usage: arm-image-installer <options>

	--addconsole    - Add system console to extlinux.conf
	--addkey=       - /path/to/ssh-public-key
	--image=IMAGE	- xz compressed image file name
	--media=DEVICE	- media device file (/dev/[sdX|mmcblkX])
	--norootpass	- Remove the root password
	--resizefs	- Resize root filesystem to fill media device
	--supported	- List of supported hardware
	--target=TARGET	- target board
	--version	- Display version and exit
	-y		- Assumes yes, will not wait for confirmation

Example: arm-image-installer --image=Fedora-Rawhide.xz --target=Bananapi --media=/dev/mmcblk0

All available targets are stored in a file called SUPPORTED-BOARDS:

cat /usr/share/doc/arm-image-installer/SUPPORTED-BOARDS

Network Installation

A network installation is the preferred installation method for current Aarch64 hardware targets but can also be used for ARMv7hl. In order to begin you will need to setup the installation server, a guide can be found below: