From Fedora Project Wiki
Line 24: Line 24:


===Before Booting the OMAP Image ===
===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.
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.
<pre>
<pre>
USER=your-user-name # replace this with your username
USER=your-user-name # replace this with your username
PARTITION=/dev/<partition> # use the mount command to determine the partition, use the full path (for example /dev/mmcblk0p1)
TARGET=  #this is your target device - panda, panda_es
umount /run/media/$USER/__BOOT/UBOO
umount /run/media/$USER/__BOOT/UBOO
mkfs.vfat /dev/<location-of-your-media>
mkfs.vfat $PARTITION
mkdir /tmp/uboot
mkdir /tmp/uboot
mount /dev/<location-of-your-media> /tmp/uboot
mount /dev/<location-of-your-media> /tmp/uboot
cp /run/media/$USER/__/usr/share/uboot-<device-name>/MLO /tmp/uboot/
cp /run/media/$USER/__/usr/share/uboot-<device-name>/MLO /tmp/uboot/
sync  
sync  
cp /run/media/$USER/__/usr/share/uboot-<device-name>/{uboot.img,uboot.bin,uEnv.txt.<device-name>} /tmp/uboot/
cp /run/media/$USER/__/usr/share/uboot-<target-device-name>/{uboot.img,uboot.bin,uEnv.txt.<device-name>} /tmp/uboot/
sync
sync
umount /tmp/uboot/
umount /tmp/uboot/

Revision as of 02:09, 28 May 2013

Fedora 19 ARM Beta

This is the latest Fedora 19 Beta Release Candidate for the ARM architecture and marks a significant milestone for Fedora on ARM. There two images available for the Beta, one for use in OMAP platforms the other for use in the Trimslice and Exynos5 hardware platforms.

For Trimslice(kernel-tegra)

Warning.png
IMPORTANT
You must use a Device Tree enabled Uboot to boot the Fedora 19 Trimslice image. Failure to do so will result in a non-booting system.

Download the image 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. There is no root password required initially - this something you should change right away.

Once the system is booted it is recommended to do a little clean up. Remove the unneeded kernels:

yum remove kernel kernel-lpae

For OMAP

Download the image for use with Omap platforms (Pandaboard, Pandaboard ES, Beagleboard)

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

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.

USER=your-user-name # replace this with your username
PARTITION=/dev/<partition> # use the mount command to determine the partition, use the full path (for example /dev/mmcblk0p1)
TARGET=   #this is your target device - panda, panda_es 
umount /run/media/$USER/__BOOT/UBOO
mkfs.vfat $PARTITION
mkdir /tmp/uboot
mount /dev/<location-of-your-media> /tmp/uboot
cp /run/media/$USER/__/usr/share/uboot-<device-name>/MLO /tmp/uboot/
sync 
cp /run/media/$USER/__/usr/share/uboot-<target-device-name>/{uboot.img,uboot.bin,uEnv.txt.<device-name>} /tmp/uboot/
sync
umount /tmp/uboot/

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 .
sudo cp -r /tmp/boot/dtb-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 \
 --dtb dtb-3.9.2-301.fc19.armv7hl/vexpress-v2p-ca9.dtb

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 --dtb=dtb-3.9.2-301.fc19.armv7hlvexpress-v2p-ca9.dtb

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.