From Fedora Project Wiki
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:AArch64]][[Category:Fedora 24]]
[[Category:AArch64]][[Category:Fedora 24]]
   
   
= Fedora 24 for AArch64 =  
= Fedora 24 for AArch64 =
The Fedora ARM Team is pleased to announce the release of Fedora 24 for AArch64, ready to run on your next generation servers. Fedora 24 is a game-changer for the Fedora Project, and we think you're going to be very pleased with the results.


== Highlights in the Fedora 24 AArch64 Release ==
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 24, 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/24/.
=== Fedora Server ===
FreeIPA 4.3 (Domain Controller role) is included in Fedora 24. This version helps streamline installation of replicas by adding a replica promotion method for new installs. A new topology plugin has also been added that automatically manages new replication segment creation. An effective replica topology visualization tool is also available in the webUI.


More packages have been removed from the default Server edition to make the footprint of the default installation smaller.
== Another Step in the Fedora Journey ==


==== Fedora-Wide Changes ====
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 24 is one big step on the road to the next generation of Linux distributions. But that does not mean that Fedora 24 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 24, please read the [https://docs.fedoraproject.org/release-notes Release Notes].
As with every Fedora release, almost every component has a new version, with improvements across the board.


Under the hood, glibc has moved to 2.23.  The update includes better performance, many bugfixes and improvements to POSIX compliance, and additional locales. The new library is backwards compatible with the version of glibc that was shipped in Fedora 23, and includes a number of security and bug fixes.
== Server ==


We've also updated the system compiler to GCC 6 and rebuilt all packages with that, providing greater code optimization and catching programming errors which had slipped past previous compilers.
Fedora 24 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 24 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 24, 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 <code>#fedora-qa</code> on Freenode IRC. As testing progresses, common issues are tracked on the Common F24 Bugs page.
 
* https://fedoraproject.org/wiki/Common_F24_bugs
 
For tips on reporting a bug effectively, read &quot;how to file a bug report.&quot;
 
* https://fedoraproject.org/wiki/How_to_file_a_bug_report


== Mirror List ==
== Mirror List ==
Line 37: Line 47:
|| Advanced Micro Devices Opteron A1100 (Seattle)    || style="background:lightgrey;"|  ||{{result|pass}}  ||style="background:lightgrey;"| ||{{result|pass}}||style="background:lightgrey;"| ||style="background:lightgrey;"| ||{{result|none}}|| Tested with 74E firmware.  
|| Advanced Micro Devices Opteron A1100 (Seattle)    || style="background:lightgrey;"|  ||{{result|pass}}  ||style="background:lightgrey;"| ||{{result|pass}}||style="background:lightgrey;"| ||style="background:lightgrey;"| ||{{result|none}}|| Tested with 74E firmware.  
|-
|-
|| ARM Juno R1/R2 Development Platform    || style="background:lightgrey;"|  ||{{result|pass}}  ||{{result|pass}} ||{{result|pass}}||style="background:lightgrey;"| ||style="background:lightgrey;"| ||{{result|none}}|| Tested with custom built linaro 16.02 firmware. Boots in DT or ACPI mode from USB cdrom. PCIe, SATA and Gbit ethernet disabled in ACPI mode.
|-
|}
|}


Line 46: Line 59:


{{admon/warning|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. | Grub Binary name]].}}
{{admon/warning|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. | Grub Binary name]].}}
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 24 for AArch64 installation tree below:
Once configured use the Fedora 24 for AArch64 installation tree below:
Line 54: Line 69:
= Install with QEMU =  
= Install with QEMU =  
{{admon/warning|Note | You will need to use qemu-2.3.0-4+ for the below to work.}}
{{admon/warning|Note | You will need to use qemu-2.3.0-4+ for the below to work.}}
To use Fedora 24 on QEMU you will need to use 'edk2-20160418gita8c39ba-1' or later.  
To use Fedora 24 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
  sudo dnf install edk2-aarch64 qemu-system-aarch64 libguestfs-tools-c


To install:
To install:
Line 72: Line 87:


* 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. ([http://bugzilla.redhat.com/show_bug.cgi?id=1172740 BZ#1172740]).
* 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. ([http://bugzilla.redhat.com/show_bug.cgi?id=1172740 BZ#1172740]).
* After installation on the Mustang, you must update the boot entry in UEFI to boot from 'grubaa64.efi' instead of the default 'shim.efi'. Failure to do so will result in an error when unpacking the initrd ([http://bugzilla.redhat.com/show_bug.cgi?id=1309147 BZ#1309147]).
Example
<pre>
TianoCore 1.1.0 UEFI 2.4.0 Oct 20 2015 14:49:32
CPU: APM ARM 64-bit Potenza Rev A3 2400MHz PCP 2400MHz
    32 KB ICACHE, 32 KB DCACHE
    SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz
Board: X-Gene Mustang Board
Slimpro FW:
        Ver: 2.4 (build 01.15.22.00 2015/10/20)
        PMD: 950 mV
        SOC: 950 mV
The default boot selection will start in  3 seconds
[1] Fedora
[2] pxe
[3] Shell
[4] Boot Manager
[5] Reboot
[6] Shutdown
Start: 4
[1] Add Boot Device Entry
[2] Update Boot Device Entry
[3] Remove Boot Device Entry
[4] Set Boot Timeout
[5] Return to main menu
Choice: 2
[1] Fedora
[2] pxe
[3] Return to Main Menu
Update entry: 1
File path of the EFI Application or the kernel: \EFI\fedora\grubaa64.efi
Is your application is an OS loader? [y/n] y
Arguments to pass to the EFI Application:
Description for this new Entry: Fedora
[1] Add Boot Device Entry
[2] Update Boot Device Entry
[3] Remove Boot Device Entry
[4] Set Boot Timeout
[5] Return to main menu
Choice: 5
[1] Fedora
[2] pxe
[3] Shell
[4] Boot Manager
[5] Reboot
[6] Shutdown
Start:
</pre>

Latest revision as of 14:57, 15 September 2016


Fedora 24 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 24, 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/24/.

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 24 is one big step on the road to the next generation of Linux distributions. But that does not mean that Fedora 24 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 24, please read the Release Notes.

Server

Fedora 24 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 24 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 24, 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 F24 Bugs page.

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

Mirror List

Supported Hardware

  • Applied Micro X-Gene (Mustang)
  • Hardware virtualization with QEMU

Overview of Hardware Support Status

Hardware ACPI Network USB DVD Display Audio Link Notes
Hardware virtualization with QEMU
Pass pass
none
Tested with edk2.git-aarch64-0-20160504.b1747.gf143074.noarch.
Applied Micro X-Gene (Mustang)
Pass pass
Pass pass
none
none
Tested with APM Tianocore - 1.15.10.
Advanced Micro Devices Opteron A1100 (Seattle)
Pass pass
Pass pass
none
Tested with 74E firmware.
ARM Juno R1/R2 Development Platform
Pass pass
Pass pass
Pass pass
none
Tested with custom built linaro 16.02 firmware. Boots in DT or ACPI mode from USB cdrom. PCIe, SATA and Gbit ethernet disabled in ACPI mode.

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 24 for AArch64 installation tree below:

Installation Tree

http://dl.fedoraproject.org/pub/fedora-secondary/releases/24/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 24 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 qemu-system-aarch64 libguestfs-tools-c

To install:

sudo virt-install    \
      --name Fedora_24_AArch64 --ram 4096 --arch aarch64 \
      --disk size=8 --os-variant fedora22   \
      --location https://dl.fedoraproject.org/pub/fedora-secondary/releases/24/Server/aarch64/os/
*Add kickstart with (root password is 'fedora'):
      --extra-args "inst.ks=https://pwhalen.fedorapeople.org/kickstarts/Fedora-24-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).