Revision as of 17:49, 28 June 2013

Fedora 19 for ARM

The Fedora ARM team is pleased to announce the Fedora 19 for ARM is now available for download from:

https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/19-Beta/Images/armhfp/

Fedora 19 for ARM includes two image types - one for use with platforms requiring a VFAT partition(Pandaboard), the other for use with devices that boot from an EXT partition(Trimslice). For each of these there are a number of desktop choices including MATE, KDE, XFCE, LXDE, SOAS and a minimal image that does not include the desktop. Any of these images can be used with QEMU.

For the Trimslice

IMPORTANT
You must use the latest Device Tree enabled Uboot to boot the Fedora 19 Trimslice image, which you can find here. Failure to do so will result in a non-booting system.

Download the image of your choice for use in the Trimslice:

wget http://dl.fedoraproject.org/pub/fedora-secondary/releases/test/19-Beta/Images/armhfp/Fedora-armhfp-19-Beta-1-sda.raw.xz

Copy the image to the intended media:

xzcat Fedora-armhfp-19-Beta-1-sda.raw.xz > /dev/<location-of-your-media>

Insert into the Trimslice and boot. Fedora will boot to an initial setup screen allowing you to create your user, set the root password and timezone.

For the Pandaboard and Pandaboard ES

Download the image of your choice for use with the Pandaboard or Pandaboard ES.

wget http://dl.fedoraproject.org/pub/fedora-secondary/releases/test/19-Beta/Images/armhfp/Fedora-OMAP-armhfp-19-Beta-1-sda.raw.xz

Writing the image As root copy the image to the intended media:

xzcat Fedora-OMAP-armhfp-19-Beta-1-sda.raw.xz > /dev/<location-of-your-media>

Before Booting the OMAP Image

Before booting the OMAP image you will need to populate the first partition specific to your device.

For Versatile Express Emulation with QEMU

Even without hardware its possible to run the Fedora 19 ARM Beta using QEMU. To this we will use the generic image.

wget http://dl.fedoraproject.org/pub/fedora-secondary/releases/test/19-Beta/Images/armhfp/Fedora-armhfp-19-Beta-1-sda.raw.xz

Extract the image:

unxz Fedora-armhfp-19-Beta-1-sda.raw.xz

Mount the image and extract the kernel and initramfs for use with booting.

sudo kpartx -av Fedora-armhfp-19-Beta-1-sda.raw

Make a temporary mount point

mkdir /tmp/boot
sudo mount /dev/mapper/loop0p1 /tmp/boot
sudo cp /tmp/boot/initramfs-3.9.2-301.fc19.armv7hl.img .
sudo cp /tmp/boot/vmlinuz-3.9.2-301.fc19.armv7hl .

To boot:

sudo qemu-system-arm -machine vexpress-a9 -m 1024 -nographic -net nic -net user \
 -append "console=ttyAMA0,115200n8 rw root=/dev/mmcblk0p3 rootwait physmap.enabled=0" \
 -kernel vmlinuz-3.9.2-301.fc19.armv7hl \
 -initrd initramfs-3.9.2-301.fc19.armv7hl.img \
 -sd Fedora-armhfp-19-Beta-1-sda.raw \

For convenience you can also download a script for booting the system here. To run the script:

chmod 755 boot-vexpress
./boot-vexpress -h
Usage: ./boot-vexpress [--gui] --kernel=vmlinuz... --ramfs=initramfs --image=fsimage [--dtb=vexpress.dtb]

To boot the image:

sudo ./boot-vexpress --kernel=vmlinuz-3.9.2-301.fc19.armv7hl --ramfs=initramfs-3.9.2-301.fc19.armv7hl.img --image=Fedora-armhfp-19-Beta-1-sda.raw

Booting with device tree is possible, although passing --gui for graphics will not work. Booting without device tree is recommended for F-19, as it will work in both serial and graphics mode, whereas passing a DTB will only work with serial.

Calxeda EnergyCore (HighBank)

The Fedora 19 Beta for ARM includes support for systems that are able to perform a network installation using a kickstart, including enterprise hardware such as the Highbank. A working kickstart can be found here.

For more detailed instructions on setting this up, please visit this page.

Known Issues

Significant logical volume noise on first boot. This is harmless and resolved after rebooting the system.
Initial setup is not run on first boot.

@@ Line 4: / Line 4: @@
 https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/19-Beta/Images/armhfp/
-Fedora 19 for ARM includes twoa number of pre-built images for the Pandaboard and Pandaboard ES which requires special partitioning, the second will support the Trimslice and Versatile Express(QEMU). The Beta for ARM also includes an installation tree in the yum repository which may be used to PXE-boot a kickstart-based installation on systems that support this option, such as the Calxeda EnergyCore (HighBank).
+Fedora 19 for ARM includes two image types - one for use with platforms requiring a VFAT partition(Pandaboard), the other for use with devices that boot from an EXT partition(Trimslice). For each of these there are a number of desktop choices including MATE, KDE, XFCE, LXDE, SOAS and a minimal image that does not include the desktop. Any of these images can be used with QEMU.
 ==For the Trimslice==
 {{admon/warning|IMPORTANT | You must use the latest Device Tree enabled Uboot to boot the Fedora 19 Trimslice image, which you can find [http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#v2012.04-1.02  here].  <b>Failure to do so will result in a non-booting system.</b>}}
-Download the image for use in the Trimslice:
+Download the image of your choice for use in the Trimslice:
   wget http://dl.fedoraproject.org/pub/fedora-secondary/releases/test/19-Beta/Images/armhfp/Fedora-armhfp-19-Beta-1-sda.raw.xz
@@ Line 15: / Line 15: @@
   xzcat Fedora-armhfp-19-Beta-1-sda.raw.xz > /dev/<location-of-your-media>
-Insert into the Trimslice and boot. There is no root password required initially - this something you should change right away.
+Insert into the Trimslice and boot. Fedora will boot to an initial setup screen allowing you to create your user, set the root password and timezone.
-Once the system is booted it is recommended to do a little clean up and remove the unneeded kernels:
- yum remove kernel kernel-lpae
 == For the Pandaboard and Pandaboard ES ==
-Download the image for use with the Pandaboard or Pandaboard ES.
+Download the image of your choice for use with the Pandaboard or Pandaboard ES.
   wget http://dl.fedoraproject.org/pub/fedora-secondary/releases/test/19-Beta/Images/armhfp/Fedora-OMAP-armhfp-19-Beta-1-sda.raw.xz
+Writing the image
 As root copy the image to the intended media:
   xzcat Fedora-OMAP-armhfp-19-Beta-1-sda.raw.xz > /dev/<location-of-your-media>
 ===Before Booting the OMAP Image ===
-Before booting the OMAP image reinsert the media into a host pc. The image should automatically mount, however if it does not you may need to adjust the mount point used in the below example. Use the 'mount' command to determine the name of the partition you will be working with.
+Before booting the OMAP image you will need to populate the first partition specific to your device.
-<pre>
-DEVICE=/dev/<device>  # use the mount command to determine the device, omit any tailing partitions (for example : /dev/sdb or /dev/mmcblk0)
-TARGET=               #this is your target device - panda, panda_es
-# fix the boot partition
-umount ${DEVICE}*1
-mkfs.vfat -n 'BOOT' ${DEVICE}*1
-BOOTUUID=$(blkid -s UUID -o value ${DEVICE}*1)
-# generate a new UUID for later use on the rootfs.
-ROOTUUID=$(uuidgen)
-# fix the rootfs
-umount ${DEVICE}*3
-tune2fs -L 'rootfs' -U "$ROOTUUID" ${DEVICE}*3
-# Create temporary mount points
-mkdir /tmp/{uboot,rootfs}
-sudo mount ${DEVICE}*1 /tmp/uboot
-sudo mount ${DEVICE}*3 /tmp/rootfs
-# copy over the TI boards boot files.
-sudo cp /tmp/rootfs/usr/share/uboot-panda/{MLO,u-boot.img} /tmp/uboot/
-sudo cp /tmp/rootfs/usr/share/uboot-panda/uEnv.txt.$TARGET /tmp/uboot/uEnv.txt
-sync
-# fix the rootfs mount point
-sed -i -e "s|.*\(/.*ext4.*\)$|UUID=${ROOTUUID} \1|" /tmp/rootfs/etc/fstab
-sed -i -e "s|.*\(/boot/uboot.*vfat.*\)$|UUID=${BOOTUUID} \1|" /tmp/rootfs/etc/fstab
-sync
-umount /tmp/rootfs
-umount /tmp/uboot/
-#THE END
-</pre>
 ==For Versatile Express Emulation with QEMU==

Search

Architectures/ARM/F19/Installation: Difference between revisions