From Fedora Project Wiki
Associated release criterion
This test case is associated with the Basic_Release_Criteria#initialization-requirements release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


Description

This case tests whether a direct deployment of a Fedora image works on a 64-bit ARM platform.

Setup

  1. Insert or connect the media to write the Fedora aarch64 disk image.

How to test

You can quite easily prepare an image on the SD card using Fedora or any Linux distribution, MacOS or Windows. The default settings will provide the user interface on a HDMI monitor with keyboard and mouse support

Manually

 $ xzcat Fedora-IMAGE-NAME.raw.xz | sudo dd status=progress bs=4M of=/dev/XXX # Location of your media (will be sdX or mmcblkX depending on hardware)

Scripted

To install using arm-image-installer:

$ sudo dnf install -y arm-image-installer

To write the image out use the following:

$ sudo arm-image-installer

Usage: arm-image-installer <options>

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

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

For list of supported boards please check SUPPORTED-BOARDS file.

Attach the written medium to the test system and boot it, ensuring the medium takes priority over other boot methods.

Expected Results

  1. When testing a standard Fedora disk image, the system boots to the initial-setup tool.
  2. When testing an Iot disk image, the system boots to log in.