From Fedora Project Wiki
< Architectures | ARM
Puiterwijk (talk | contribs) mNo edit summary |
|||
| (50 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{autolang|base=yes}} | |||
[[Category:Fedora ARMv7]][[Category:Fedora 19]] | |||
=Fedora 19 for ARM= | =Fedora 19 for ARM= | ||
The Fedora ARM team is pleased to announce the Fedora 19 for ARM is now available for download from: | The Fedora ARM team is pleased to announce that the Fedora 19 for the ARM Architecture is now available for download from: | ||
http://download.fedoraproject.org/pub/fedora-secondary/releases/19/ | |||
Fedora 19 for ARM includes two image types - one for use with platforms requiring a VFAT partition (such as Texas Instruments's OMAP4-based PandaBoard), the other for use with devices that boot from an EXT3/4 partition (such as CompuLab's Tegra2-based TrimSlice). For each of these image types, there are a number of images providing for a variety of desktop choices (including MATE, KDE, XFCE, LXDE, SOAS), as well as a minimal image that does not include the desktop. Any of these images can be used with QEMU on an x86_64 desktop to emulate a fully functional ARM environment. | |||
The image-based installation process involves downloading an image file (depending upon the target type and desktop/non-desktop option desired), inserting removable media into a "host" system (e.g. an ARM or x86_64 PC class desktop, laptop, etc.) and performing a few simple commands to write this image onto the media. This media is then used by the ARM "target" system to boot the Fedora 19 environment. | |||
== | ==Determining the location of installation media== | ||
{{admon/warning| | {{admon/warning|NOTE The following instructions will provide a means to determine the correct device to use in the examples below for "location-of-your-media". It is extremely important to verify the location chosen as a target of this installation, since an incorrect location could result in destructive damage to one or more unrelated host filesystems containing unrelated data. If in doubt following these instructions, consult an expert or ask for assistance on the mailing list, or #fedora-arm IRC.}} | ||
Download the image of your choice for use with the | Determine the location of your chosen installation media, such as an SD Card. This can be done conveniently using the "lshw" package, which may not be installed on your host system: | ||
<pre> | |||
sudo yum install lshw | |||
sudo lshw | |||
</pre> | |||
The output will contain information about removable media, such as (the device name will quite possibly differ on your system from this example): | |||
<pre> | |||
*-scsi:1 | |||
physical id: 3 | |||
bus info: usb@2:1.8.3 | |||
logical name: scsi6 | |||
capabilities: emulated scsi-host | |||
configuration: driver=usb-storage | |||
*-disk | |||
description: SCSI Disk | |||
product: SD Card Reader | |||
vendor: APPLE | |||
physical id: 0.0.0 | |||
bus info: scsi@6:0.0.0 | |||
logical name: /dev/sdb | |||
version: 2.00 | |||
capabilities: removable | |||
configuration: sectorsize=512 | |||
*-medium | |||
physical id: 0 | |||
logical name: /dev/sdb | |||
</pre> | |||
In the example, the device location is /dev/sdb, which will quite likely differ on your system. | |||
=For the CompuLab TrimSlice= | |||
{{admon/warning|IMPORTANT | You must use the latest Device Tree enabled U-Boot 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 of your choice for use with the TrimSlice: | |||
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal | TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal | ||
wget http:// | wget http://download.fedoraproject.org/pub/fedora-secondary/releases/19/Images/armhfp/Fedora-$TYPE-armhfp-19-1-sda.raw.xz | ||
Copy the image to the intended media: | Copy the image to the intended media: | ||
xzcat Fedora-$TYPE-armhfp-19-1-sda.raw.xz > /dev/<location-of-your-media> | xzcat Fedora-$TYPE-armhfp-19-1-sda.raw.xz > /dev/<location-of-your-media> | ||
Insert into the | 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 Texas Instruments PandaBoard and PandaBoard ES = | |||
Download the image of your choice for use with the | Download the image of your choice for use with the PandaBoard or PandaBoard ES. | ||
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal | TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal | ||
wget | wget http://download.fedoraproject.org/pub/fedora-secondary/releases/19/Images/armhfp/Fedora-$TYPE-VFAT-armhfp-19-1-sda.raw.xz | ||
===Writing the image === | ===Writing the image === | ||
| Line 27: | Line 66: | ||
====Manual==== | ====Manual==== | ||
As root copy the image to | As root copy the image to this intended media (e.g. SD Card): | ||
<pre> | |||
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal | |||
Once the | xzcat -v Fedora-XFCE-VFAT-armhfp-19-1-sda.raw.xz > /dev/<location-of-your-media> | ||
</pre> | |||
Once writing the image to the intended media (e.g. SD Card) has been completed, remove and reinsert the media into your host PC. You will need to copy some U-Boot bootloader files into place for booting the target system. The mount points in the example below are specific to Fedora 18 and may need to be adjusted for your host system: | |||
<pre> | <pre> | ||
USER= # replace with your user account name on the host PC | USER= # replace with your user account name on the host PC | ||
TARGET= #choose panda or panda_es | TARGET= # choose panda or panda_es | ||
sudo cp /run/media/$USER/__/usr/share/uboot-panda/{MLO,u-boot.bin,u-boot.img,uEnv.txt.$TARGET /run/media/$USER/UBOOT/ | sudo cp /run/media/$USER/__/usr/share/uboot-panda/{MLO,u-boot.bin,u-boot.img,uEnv.txt.$TARGET} /run/media/$USER/UBOOT/ | ||
mv /run/media/$USER/UBOOT/uEnv.txt.$TARGET /run/media/$USER/UBOOT/uEnv.txt | |||
sync | sync | ||
</pre> | </pre> | ||
You should now be able to remove the media from your host PC, insert into your device and boot. If you are using an image that provides a desktop you will need to use a display to configure your user account, root password and timezone. For the minimal image this is done in text mode over the console. | You should now be able to remove the media from your host PC, insert into your device, and boot it. If you are using an image that provides a desktop, you will need to use a display to configure your user account, root password and timezone. For the minimal image, this is done in text mode over the serial console. | ||
==== Arm-creator.py ==== | ==== Arm-creator.py ==== | ||
Jon Chiappetta has simplied the process for creating a bootable image for the | Jon Chiappetta has simplied the process for creating a bootable image for the PandaBoard and PandaBoard ES. The script can be used from commandline or through a text menu that will allow you to choose the specific details for your device. | ||
<pre> | |||
./arm-creator.py -h | |||
Usage: ./arm-creator.py [-h --help] --install --image=/path/to/Fedora-ARM.img.xz [--board=<type>] --disk=/dev/... | Usage: ./arm-creator.py [-h --help] --install --image=/path/to/Fedora-ARM.img.xz [--board=<type>] --disk=/dev/... | ||
</pre> | |||
== | ===== Commandline ===== | ||
<pre> | |||
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal | |||
TARGET= #choose panda or panda_es | |||
./arm-creator.py --install --image=/path/to/Fedora-$TYPE-VFAT-armhfp-19-1-sda.raw.xz --board=$TARGET --disk=<path-to-media> | |||
</pre> | |||
Even without hardware | ===== Text Menu ===== | ||
<pre> | |||
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal | |||
./arm-creator.py --image=/path/to/Fedora-$TYPE-VFAT-armhfp-19-1-sda.raw.xz | |||
</pre> | |||
Additional information on arm-creator.py including usage can be found [[Fedora_ARM_Creator |Here]]. | |||
=For Versatile Express Emulation with QEMU= | |||
No ARM hardware? No problem! Even without hardware, it is possible to run the Fedora 19 for ARM images using the QEMU emulator program. Any image can be used, and you can choose a script method or manual depending on your preference. | |||
===Manual Preparation === | |||
<pre> | |||
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal | |||
wget http://download.fedoraproject.org/pub/fedora-secondary/releases/19/Images/armhfp/Fedora-$TYPE-armhfp-19-1-sda.raw.xz | |||
</pre> | |||
Extract the image: | Extract the image: | ||
<pre> | |||
unxz Fedora-$TYPE-armhfp-19-1-sda.raw.xz | |||
</pre> | |||
Extract the kernel and initramfs for use with booting. | |||
<pre> | |||
virt-copy-out -a Fedora-$TYPE-armhfp-19-1-sda.raw /boot /tmp | |||
ls -l /tmp/boot | |||
</pre> | |||
Instead of using virt-copy-out, you can use this: | |||
<pre> | |||
sudo kpartx -av Fedora-$TYPE-armhfp-19-1-sda.raw | |||
mkdir /tmp/boot | |||
sudo mount /dev/mapper/loop0p1 /tmp/boot | |||
sudo cp /tmp/boot/initramfs-3.9.5-301.fc19.armv7hl.img . | |||
sudo cp /tmp/boot/vmlinuz-3.9.5-301.fc19.armv7hl . | |||
sudo umount /tmp/boot | |||
sudo kpartx -dv Fedora-$TYPE-armhfp-19-1-sda.raw | |||
</pre> | |||
To boot: | To boot: | ||
<pre> | <pre> | ||
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" \ | -append "console=ttyAMA0,115200n8 rw root=/dev/mmcblk0p3 rootwait physmap.enabled=0" \ | ||
-kernel vmlinuz-3.9. | -kernel vmlinuz-3.9.5-301.fc19.armv7hl \ | ||
-initrd initramfs-3.9. | -initrd initramfs-3.9.5-301.fc19.armv7hl.img \ | ||
-sd Fedora-armhfp-19 | -sd Fedora-$TYPE-armhfp-19-1-sda.raw \ | ||
</pre> | </pre> | ||
| Line 79: | Line 155: | ||
To boot the image: | To boot the image: | ||
<pre> | <pre> | ||
sudo ./boot-vexpress --kernel=vmlinuz-3.9. | sudo ./boot-vexpress --kernel=vmlinuz-3.9.5-301.fc19.armv7hl --ramfs=initramfs-3.9.5-301.fc19.armv7hl.img --image=Fedora-$TYPE-armhfp-19-1-sda.raw | ||
</pre> | </pre> | ||
Booting with device tree is possible, although passing <b>--gui</b> 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. | Booting with device tree is possible, although passing <b>--gui</b> for graphics will not work at this time (this is due to ongoing platform reword occurring within the Versatile Express kernel code). 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. | ||
=== livemedia-modifier === | |||
The livemedia-modifier tool written by Jon Chiappetta can be used to perform the above steps and is available [http://fossjon.fedorapeople.org/review/livemedia-modifier/livemedia-modifier-2.4-1.fc18.noarch.rpm here]. After installing you can run the script using the following example: | |||
<pre> | |||
# Extract the image | |||
unxz Fedora-$TYPE-armhfp-19-1-sda.raw.xz | |||
# Run livemedia-modifier | |||
livemedia-modifier --image=Fedora-$TYPE-armhfp-19-1-sda.raw --platform=vexpress --nocompress | |||
</pre> | |||
The modifier will create a copy of the original image, all changes will be made on the copy preserving the original image integrity. | |||
Additional usage instructions can be found [[Architectures/ARM/livemedia-modifier | here]]. | |||
= Calxeda EnergyCore (HighBank) = | = Calxeda EnergyCore (HighBank) = | ||
Fedora 19 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 [http://fedorapeople.org/~pwhalen/f19/f19-highbank.ks here]. | |||
For more detailed instructions on setting this up, please visit this [[Architectures/ARM/F18/HighBank |page]]. | For more detailed instructions on setting this up, please visit this [[Architectures/ARM/F18/HighBank |page]]. | ||
= Resize the Root Filesystem = | |||
By default the images in Fedora are 8GB and can be resized to fit your media. | |||
yum install dracut-modules-growroot cloud-utils-growpart | |||
Rebuild the initramfs or install a new kernel to use the module. | |||
<pre> | |||
#Rebuild your existing initramfs | |||
KERVER= #use your kernel version eg - '3.9.5-301.fc19.armv7hl.tegra' for the Trimslice | |||
dracut -f --kver=$KERVER | |||
mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 \ | |||
-n initramfs-$KERVER \ | |||
-d /boot/initramfs-$KERVER.img /boot/uInitrd-$KERVER | |||
# When the system is rebooted, the root partition will be resized to fill the remaining space on the media. Lastly you will need to increase the filesystem size: | |||
ROOT_PART= # location of your root partition, usually '/dev/sda3' or '/dev/mmcblk0p3' | |||
resize2fs $ROOT_PART | |||
</pre> | |||
= Booting for the First Time = | |||
===Initial-setup=== | |||
* During the first boot the system will launch the 'initial-setup' utility. For graphical images this will occur on the display, for minimal images this will occur on the serial console. Failure to complete the initial-setup will prevent logging into the root account. To log in to the root account without completing the initial-setup you will need to minimally edit '/etc/passwd' file and remove the 'x' from the line beginning with 'root' (this will allow you to log into the root account without entering a password). | |||
= Known Issues = | = Known Issues = | ||
* | * A known issue exists wherein OMAP3-based devices, such as the Texas Instruments BeagleBoard and BeagleBone, are are unable to boot the standard installation images (this is due to a Cortex-A15 errata option that was enabled in the kernel and has been disabled). We hope to issue updated installation images once Fedora 19 transitions to Linux kernel 3.10. At this time, technical users may choose to manually replace the kernel in order to enable support for these devices. Others are encouraged to wait for updated images. | ||
Latest revision as of 11:00, 6 June 2017
Fedora 19 for ARM
The Fedora ARM team is pleased to announce that the Fedora 19 for the ARM Architecture is now available for download from:
http://download.fedoraproject.org/pub/fedora-secondary/releases/19/
Fedora 19 for ARM includes two image types - one for use with platforms requiring a VFAT partition (such as Texas Instruments's OMAP4-based PandaBoard), the other for use with devices that boot from an EXT3/4 partition (such as CompuLab's Tegra2-based TrimSlice). For each of these image types, there are a number of images providing for a variety of desktop choices (including MATE, KDE, XFCE, LXDE, SOAS), as well as a minimal image that does not include the desktop. Any of these images can be used with QEMU on an x86_64 desktop to emulate a fully functional ARM environment.
The image-based installation process involves downloading an image file (depending upon the target type and desktop/non-desktop option desired), inserting removable media into a "host" system (e.g. an ARM or x86_64 PC class desktop, laptop, etc.) and performing a few simple commands to write this image onto the media. This media is then used by the ARM "target" system to boot the Fedora 19 environment.
Determining the location of installation media
NOTE The following instructions will provide a means to determine the correct device to use in the examples below for "location-of-your-media". It is extremely important to verify the location chosen as a target of this installation, since an incorrect location could result in destructive damage to one or more unrelated host filesystems containing unrelated data. If in doubt following these instructions, consult an expert or ask for assistance on the mailing list, or #fedora-arm IRC.
Determine the location of your chosen installation media, such as an SD Card. This can be done conveniently using the "lshw" package, which may not be installed on your host system:
sudo yum install lshw sudo lshw
The output will contain information about removable media, such as (the device name will quite possibly differ on your system from this example):
*-scsi:1
physical id: 3
bus info: usb@2:1.8.3
logical name: scsi6
capabilities: emulated scsi-host
configuration: driver=usb-storage
*-disk
description: SCSI Disk
product: SD Card Reader
vendor: APPLE
physical id: 0.0.0
bus info: scsi@6:0.0.0
logical name: /dev/sdb
version: 2.00
capabilities: removable
configuration: sectorsize=512
*-medium
physical id: 0
logical name: /dev/sdb
In the example, the device location is /dev/sdb, which will quite likely differ on your system.
For the CompuLab TrimSlice
IMPORTANT
You must use the latest Device Tree enabled U-Boot to boot the Fedora 19 Trimslice image, which you can find here. Failure to do so will result in a non-booting system.
You must use the latest Device Tree enabled U-Boot 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 with the TrimSlice:
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal wget http://download.fedoraproject.org/pub/fedora-secondary/releases/19/Images/armhfp/Fedora-$TYPE-armhfp-19-1-sda.raw.xz
Copy the image to the intended media:
xzcat Fedora-$TYPE-armhfp-19-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 Texas Instruments PandaBoard and PandaBoard ES
Download the image of your choice for use with the PandaBoard or PandaBoard ES.
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal wget http://download.fedoraproject.org/pub/fedora-secondary/releases/19/Images/armhfp/Fedora-$TYPE-VFAT-armhfp-19-1-sda.raw.xz
Writing the image
There are two options for writing the image and preparing your media for boot. Below are step by step instructions on how to do it manually, or using a python script that will walk you through the process.
Manual
As root copy the image to this intended media (e.g. SD Card):
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal xzcat -v Fedora-XFCE-VFAT-armhfp-19-1-sda.raw.xz > /dev/<location-of-your-media>
Once writing the image to the intended media (e.g. SD Card) has been completed, remove and reinsert the media into your host PC. You will need to copy some U-Boot bootloader files into place for booting the target system. The mount points in the example below are specific to Fedora 18 and may need to be adjusted for your host system:
USER= # replace with your user account name on the host PC
TARGET= # choose panda or panda_es
sudo cp /run/media/$USER/__/usr/share/uboot-panda/{MLO,u-boot.bin,u-boot.img,uEnv.txt.$TARGET} /run/media/$USER/UBOOT/
mv /run/media/$USER/UBOOT/uEnv.txt.$TARGET /run/media/$USER/UBOOT/uEnv.txt
sync
You should now be able to remove the media from your host PC, insert into your device, and boot it. If you are using an image that provides a desktop, you will need to use a display to configure your user account, root password and timezone. For the minimal image, this is done in text mode over the serial console.
Arm-creator.py
Jon Chiappetta has simplied the process for creating a bootable image for the PandaBoard and PandaBoard ES. The script can be used from commandline or through a text menu that will allow you to choose the specific details for your device.
./arm-creator.py -h Usage: ./arm-creator.py [-h --help] --install --image=/path/to/Fedora-ARM.img.xz [--board=<type>] --disk=/dev/...
Commandline
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal TARGET= #choose panda or panda_es ./arm-creator.py --install --image=/path/to/Fedora-$TYPE-VFAT-armhfp-19-1-sda.raw.xz --board=$TARGET --disk=<path-to-media>
Text Menu
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal ./arm-creator.py --image=/path/to/Fedora-$TYPE-VFAT-armhfp-19-1-sda.raw.xz
Additional information on arm-creator.py including usage can be found Here.
For Versatile Express Emulation with QEMU
No ARM hardware? No problem! Even without hardware, it is possible to run the Fedora 19 for ARM images using the QEMU emulator program. Any image can be used, and you can choose a script method or manual depending on your preference.
Manual Preparation
TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal wget http://download.fedoraproject.org/pub/fedora-secondary/releases/19/Images/armhfp/Fedora-$TYPE-armhfp-19-1-sda.raw.xz
Extract the image:
unxz Fedora-$TYPE-armhfp-19-1-sda.raw.xz
Extract the kernel and initramfs for use with booting.
virt-copy-out -a Fedora-$TYPE-armhfp-19-1-sda.raw /boot /tmp ls -l /tmp/boot
Instead of using virt-copy-out, you can use this:
sudo kpartx -av Fedora-$TYPE-armhfp-19-1-sda.raw mkdir /tmp/boot sudo mount /dev/mapper/loop0p1 /tmp/boot sudo cp /tmp/boot/initramfs-3.9.5-301.fc19.armv7hl.img . sudo cp /tmp/boot/vmlinuz-3.9.5-301.fc19.armv7hl . sudo umount /tmp/boot sudo kpartx -dv Fedora-$TYPE-armhfp-19-1-sda.raw
To boot:
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.5-301.fc19.armv7hl \ -initrd initramfs-3.9.5-301.fc19.armv7hl.img \ -sd Fedora-$TYPE-armhfp-19-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.5-301.fc19.armv7hl --ramfs=initramfs-3.9.5-301.fc19.armv7hl.img --image=Fedora-$TYPE-armhfp-19-1-sda.raw
Booting with device tree is possible, although passing --gui for graphics will not work at this time (this is due to ongoing platform reword occurring within the Versatile Express kernel code). 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.
livemedia-modifier
The livemedia-modifier tool written by Jon Chiappetta can be used to perform the above steps and is available here. After installing you can run the script using the following example:
# Extract the image unxz Fedora-$TYPE-armhfp-19-1-sda.raw.xz # Run livemedia-modifier livemedia-modifier --image=Fedora-$TYPE-armhfp-19-1-sda.raw --platform=vexpress --nocompress
The modifier will create a copy of the original image, all changes will be made on the copy preserving the original image integrity.
Additional usage instructions can be found here.
Calxeda EnergyCore (HighBank)
Fedora 19 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.
Resize the Root Filesystem
By default the images in Fedora are 8GB and can be resized to fit your media.
yum install dracut-modules-growroot cloud-utils-growpart
Rebuild the initramfs or install a new kernel to use the module.
#Rebuild your existing initramfs KERVER= #use your kernel version eg - '3.9.5-301.fc19.armv7hl.tegra' for the Trimslice dracut -f --kver=$KERVER mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 \ -n initramfs-$KERVER \ -d /boot/initramfs-$KERVER.img /boot/uInitrd-$KERVER # When the system is rebooted, the root partition will be resized to fill the remaining space on the media. Lastly you will need to increase the filesystem size: ROOT_PART= # location of your root partition, usually '/dev/sda3' or '/dev/mmcblk0p3' resize2fs $ROOT_PART
Booting for the First Time
Initial-setup
- During the first boot the system will launch the 'initial-setup' utility. For graphical images this will occur on the display, for minimal images this will occur on the serial console. Failure to complete the initial-setup will prevent logging into the root account. To log in to the root account without completing the initial-setup you will need to minimally edit '/etc/passwd' file and remove the 'x' from the line beginning with 'root' (this will allow you to log into the root account without entering a password).
Known Issues
- A known issue exists wherein OMAP3-based devices, such as the Texas Instruments BeagleBoard and BeagleBone, are are unable to boot the standard installation images (this is due to a Cortex-A15 errata option that was enabled in the kernel and has been disabled). We hope to issue updated installation images once Fedora 19 transitions to Linux kernel 3.10. At this time, technical users may choose to manually replace the kernel in order to enable support for these devices. Others are encouraged to wait for updated images.