From Fedora Project Wiki


Fedora 25 for AArch64

For the first time, all of our secondary architectures, AArch64, Power64 (ppc64, ppc64le) and s390x, are released simultaneously, rather than trailing a little behind. This includes the Server edition for all architectures and the Cloud and Docker base images for AArch64 and Power64. Along with all the same enhancements as in the primary architectures in Fedora 25, AArch64 and Power64 now have support for golang, nodejs, mongodb; along with numerous other architecture-specific enhancements. The architecture release notes pages on the wiki have more specifics for each. Download these from https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/25_Beta/ .

Another Step in the Fedora Journey

The Fedora Project has embarked on a great journey... redefining what an operating system should be for users and developers. Such innovation does not come overnight, and Fedora 25 is one big step on the road to the next generation of Linux distributions. But that does not mean that Fedora 25 is some "interim" release; there are great new features for Fedora users to deploy in their production environments right now! There are many features in this new release, highlighted here. For more detailed information on Fedora 25, please read the Release Notes.

Server

Fedora 25 Server edition is more streamlined and introduces more modularity, which will become a major factor in future Fedora releases, even as unnecessary packages were removed and the installer has a smaller footprint. FreeIPA 4.3 is a major feature for Fedora 25 Server. FreeIPA is an integrated security information management solution. This new version of FreeIPA features simplified replica installation and improved replication technology management.

Cloud

Fedora is on its way to being the best platform for containerized applications, from base Fedora container images to a full-featured platform as a service to run and manage them. As we continue on this part of the journey, we are packaging OpenShift Origin so it is easy to deploy. OpenShift Origin is a Platform as a Service system based around Kubernetes, a production-grade container orchestration project. OpenShift Origin is optimized for application development and deployment. Origin makes it easy for developers to get started building applications in containers and for operators to manage them. While not shipped in Fedora 25, per se, we have new infrastructure for developing container images with applications layered on top of the base Fedora Docker image. Fedora Developers will also see a layered image build service, which provides tools for Fedora contributors to start creating and shipping layered container images in Fedora 25 and beyond.

Make Fedora Even Better

If you want to take an active hand in making Fedora even better, there are many ways you can contribute. There are many roles that you can participate. Visit http://whatcanidoforfedora.org/ for more information! While this is a general release, there is always a chance you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode IRC. As testing progresses, common issues are tracked on the Common F25 Bugs page.

For tips on reporting a bug effectively, read "how to file a bug report."

Mirror List

Supported Hardware

Overview of Hardware Support Status

Hardware ACPI PCI SATA On-Board Network USB DVD Display Audio link Notes
Hardware virtualization with QEMU
Pass pass
none
Applied Micro X-Gene (Mustang)
Pass pass
Pass pass
none
none
Tested with APM Tianocore - 3.06.18
Advanced Micro Devices Opteron A1100 (Seattle)
Pass pass
Pass pass
none
Tested with 1002C firmware.
SoftIron Overdrive 1000 (Seattle)
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
[1]
none
Firmware from Oct 19th.
ARM Juno R1/R2 Development Platform
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Warning warn
[2]
none
Tested with custom built linaro 16.02 firmware. Boots in DT or ACPI mode. Unable to boot from SATA DVDs. (linaro 16.9 seems broken with USB devices, use 16.07 for USB DVD install)
Qualcomm Datacenter Technologies QDF2432
Pass pass
Warning warn
[3]
Pass pass
  1. DVD boot from both USB and SATA DVD
  2. HDLCD only works in DT mode.
  3. Legacy interrupts only

Network Installation

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

http://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/chap-pxe-server-setup.html
Note
The above documentation references grubx86.efi, but this is the name for x86_64 EFI grub binaries. The grub binary name on AArch64 systems is grubaa64.efi.

The instructions above reference installing grub-efi and shim for copying into the TFTP directory. This will not work for aarch64 binaries. One option is to download the rpms from the tree below and use rpm2cpio to extract and copy the files from there.

Once configured use the Fedora 25 for AArch64 installation tree below:

Installation Tree

http://dl.fedoraproject.org/pub/fedora-secondary/releases/25/Server/aarch64/os/

Install with QEMU

Note
You will need to use qemu-2.3.0-4+ for the below to work.

To use Fedora 25 on QEMU you will need to use 'edk2-20160418gita8c39ba-1' (currently in updates for all releases of Fedora) or later.

sudo dnf install edk2-aarch64 libguestfs-tools-c

To install:

sudo virt-install    \
      --name Fedora_25_AArch64 --ram 4096 --arch aarch64 \
      --disk size=8 --os-variant fedora22   \
      --location https://dl.fedoraproject.org/pub/fedora-secondary/releases/25/Everything/aarch64/os/
*Add kickstart with (root password is 'fedora'):
      --extra-args "inst.ks=https://pwhalen.fedorapeople.org/kickstarts/Fedora-Minimal-AArch64.ks"

For a full list of QEMU installation options and instructions:

http://fedoraproject.org/wiki/Architectures/AArch64/Install_with_QEMU

Reported Bugs and Known Issues

  • When using an encrypted partition, "plymouth.enable=0" must be added to the kernel command line. Failure to do so will not allow the passphrase to be entered to unlock the encrypted partition. (BZ#1172740).