Commit bc75794 Fix: Add the installation details to the manual

4 files Authored by Bart Kuivenhoven 2 years ago , Committed by zoglesby 2 years ago ,
Fix: Add the installation details to the manual

Signed-off-by: Bart Kuivenhoven <bemkuivenhoven@gmail.com>
Signed-off-by: Zach Oglesby <zach@oglesby.co>

    
@@ -0,0 +1,3 @@
+ *.swp
+ *~
+ tmp/
@@ -9,6 +9,7 @@
  	<xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
  	<xi:include href="GettingInvolved.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
  	<xi:include href="Platforms.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ 	<xi:include href="Installing.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
  	<xi:include href="Virtualizing.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
  	<xi:include href="Booting.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
  	<xi:include href="Packages.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
@@ -0,0 +1,711 @@
+ <?xml version='1.0' encoding='utf-8' ?>
+ <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+ <!ENTITY % BOOK_ENTITIES SYSTEM "ARM_Getting_Started_Guide.ent">
+ %BOOK_ENTITIES;
+ ]>
+ 
+ <section id="arm-installation">
+   <title>Installing your board</title>
+   <para />
+   <section id="arm-installation-download">
+     <title>Getting Fedora for ARM</title>
+     <para>
+       This chapter contains information on how to install the development
+       version of Fedora, otherwise known as Rawhide.
+     </para>
+     <section id="arm-installation-download-20">
+       <title>Getting Fedora 20 for ARM</title>
+       <para>
+         Fedora 20 for ARM includes two image types. One for use with platforms
+         requiring a VFAT partition (such as the Texas Instruments' AM335x-based
+         Beaglebone black). The other for use with devices that boot from an EXT3/4
+         partition (such as Compulab's Tegra2-based TrimSlice).
+       </para>
+       <para>
+         For each of these image types there are a number of images providing a
+         variety of desktop choices (including MATE, KDE, XFCE, LXDE and 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.
+       </para>
+       <para>
+         The Fedora 20 images can be downloaded from the following link.
+       </para>
+       <para>
+         <ulink url="http://download.fedoraproject.org/pub/fedora/linux/releases/20/Images/armhfp/">
+           http://download.fedoraproject.org/pub/fedora/linux/releases/20/Images/armhfp/
+         </ulink>
+       </para>
+     </section>
+     <section id="arm-installation-download-rawhide">
+       <title>Getting Fedora Rawhide for ARM</title>
+       <note>
+         <title>Important</title>
+         <para>
+           Fedora Rawhide is pre-release software and not intended for general
+           use.
+         </para>
+       </note>
+       <para>
+         The Rawhide image-based installation process involves downloading an
+         image file (depending upon desktop/non-desktop option desired),
+         inserting removable media into "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 Rawhide environment.
+       </para>
+       <para>
+         The download for the latest Rawhide image should be available in our
+         <ulink url="http://koji.fedoraproject.org/koji/tasks?state=all&amp;view=tree&amp;method=appliance&amp;order=-id">
+           Koji build system
+         </ulink>
+       </para>
+       <section id="arm-installation-download-rawhide-status">
+         <title>OVerview of hardware support status</title>
+         <para>
+           A visual overview of the current hardware status in the Fedora kernel
+           can be found at the
+           <ulink url="https://fedoraproject.org/wiki/Architectures/ARM/Rawhide/Installation/Hardware_Status#Current_Rawhide_ARM_Hardware_Status">
+             Rawhide Hardware Support Matrix
+           </ulink>
+         </para>
+         <note>
+           <title>Note</title>
+           <para>
+             The examples provided in this article are from a Fedora 19/20 host
+             and may need to be adjusted for your particular host environment.
+           </para>
+         </note>
+       </section>
+     </section>
+   </section>
+ 
+   <section id="arm-installation-rawhide-scripted">
+     <title>Scripted</title>
+     <para>
+       Execute the following script as a user with sudo privileges. It will copy
+       the selected disk image and write the appropriate U-Boot for the target
+       hardware platform. Optionally you can also enable and disable SE Linux and
+       remove the root password requirement (allowing log in without a completely
+       initialised setup). To add a board not listed, simply create a bash
+       scriptlet with the commands needed to copy U-Boot to media.
+     </para>
+     <itemizedlist>
+       <listitem>
+         <para>
+           <ulink url="http://pwhalen.fedorapeople.org/fedora-arm-image-installer.tar.bz2" />
+         </para>
+       </listitem>
+     </itemizedlist>
+     <screen>
+ <command>./fedora-arm-image-installer.sh </command>
+ <command></command>
+ <command>Usage: fedora-arm-image-installer.sh &lt;options&gt;</command>
+ <command></command>
+ <command>   --image=IMAGE    - raw image file name</command>
+ <command>   --target=TARGET  - target board</command>
+ <command>          [beaglebone|Cubietruck|panda|trimslice|wandboard_dl|wandboard_quad|wandboard_solo]</command>
+ <command>   --media=DEVICE   - media device file (/dev/[sdX|mmcblkX])</command>
+ <command>   --selinux=ON/OFF - Turn SELinux off/on as needed</command>
+ <command>   --norootpass     - Remove the root password</command>
+ <command>    -y              - Assumes yes, will not wait for confirmation</command>
+ <command>   --version        - Display version and exit</command>
+ <command></command>
+ <command>Example: fedora-arm-image-installer.sh --image=Fedora-Rawhide.xz --target=panda --media=/dev/mmcblk0 --selinux=OFF</command>
+     </screen>
+   </section>
+   <section id="arm-installation-Rawhide">
+     <title>Manual</title>
+     <para>Choose a disk image.</para>
+     <screen>
+ <command><ulink url="http://koji.fedoraproject.org/koji/tasks?state=all&amp;view=tree&amp;method=appliance&amp;order=-id" /></command>
+     </screen>
+     <para>
+       Write the image to your media.
+     </para>
+     <screen>
+ <command>DATE=  # Date of the rawhide image eg - 20140502</command>
+ <command>USER=  # your username </command>
+ <command>TYPE=  # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal</command>
+ <command>MEDIA= #/dev/&lt;location-of-your-media&gt; </command>
+ <command>xzcat Fedora-$TYPE-armhfp-rawhide-$DATE-sda.raw.xz | sudo dd of=$MEDIA; sync</command>
+     </screen>
+     <para>
+       After writing the image, read the new partition table and mount the root
+       partition.
+     </para>
+     <screen>
+ <command>partprobe $MEDIA</command>
+ <command>mkdir /tmp/root; sudo mount /dev/&lt;media-location&gt; /tmp/root</command>
+     </screen>
+     <para>
+       Copy the appropriate U-Boot files for your target hardware listed below.
+     </para>
+   </section>
+   <section id="arm-installation-rawhide-uboot">
+     <title>Write U-Boot to media</title>
+     <para>
+       Follow the steps listed under your architecture to write the appropriate
+       U-Boot for your hardware.
+     </para>
+     <section id="arm-installation-rawhide-uboot-cubietruck">
+       <title>For the CubieTruck (Allwinner A20)</title>
+       <para>
+         <screen>
+ <command>sudo dd if=/tmp/root/usr/share/uboot/Cubietruck/u-boot-sunxi-with-spl.bin of=/dev/&lt;media-location&gt; bs=1024 seek=8 conv=fsync,notrunc</command>
+         </screen>
+         The medium should now be ready to boot on the Cubietruck. insert it into
+         the device and boot.
+       </para>
+     </section>
+     <section id="arm-installation-rawhide-uboot-beaglebone">
+       <title>For the BeagleBone (Black &amp; White)</title>
+       <note>
+         <title>Important</title>
+         <para>
+           At this time a serial consile cable is required for the BeagleBone
+           Black. For those without the option of a serial cable however, please
+           consult 
+           <link linkend="arm-installing-rawhide-noserial">
+             the following sub chapter.
+           </link>
+         </para>
+       </note>
+       <para>
+         The BeagleBone Black/White no longer requires the use of a VFAT
+         partition. When using a VFAT partition, copy the U-Boot files to the
+         first partition (for reference see 
+         <xref linkend="arm-installation-rawhide-beaglebone-black-vfat" />)
+       </para>
+       <screen>
+ <command>sudo dd if=/tmp/root/usr/share/uboot/beaglebone/MLO of=/dev/&lt;media-location&gt; count=1 seek=1 conv=notrunc bs=128k</command>
+ <command>sudo dd if=/tmp/root/usr/share/uboot/beaglebone/u-boot.img of=/dev/&lt;media-location&gt; count=2 seek=1 conv=notrunc bs=384k</command>
+       </screen>
+       <para>
+         The medium should now be ready to boot on the BeagleBone. Insert it into
+         the device and boot.
+       </para>
+ 
+ <!-- ======================================= -->
+ <!--
+      Source: http://fedoraproject.org/wiki/Architectures/ARM/F20/Installation
+ -->
+       <section id="arm-installation-rawhide-beaglebone-black-vfat">
+         <title>BeagleBone (Black) (VFAT partition)</title>
+           <note>
+             <title>Important</title>
+             <para>
+               At this time a serial consile cable is required for the BeagleBone
+               Black. For those without the option of a serial cable however, please
+               consult 
+               <link linkend="arm-installing-rawhide-noserial">
+                 the following sub chapter.
+               </link>
+             </para>
+           </note>
+           <para>
+             Support for the BeagleBone Black has been added in Fedora 20. The GA
+             release includes basic support which will be extended to include HDMI and 
+             USB with the release of the 3.12 kernel. A remix is planned when support 
+             is available. In the interim, the minimal image is recommended.
+             <screen><command>TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal</command>
+ <command>wget <ulink url="http://download.fedoraproject.org/pub/fedora/linux/releases/20/Images/armhfp/Fedora-$TYPE-VFAT-armhfp-20-1-sda.raw.xz">http://download.fedoraproject.org/pub/fedora/linux/releases/20/Images/armhfp/Fedora-$TYPE-VFAT-armhfp-20-1-sda.raw.xz</ulink></command></screen>
+           </para>
+           <para>
+             Copy the image to the intended media: <screen><command>xzcat Fedora-$TYPE-VFAT-armhfp-20-1-sda.raw.xz | sudo dd of=/dev/&lt;location-of-your-media&gt;</command></screen>
+           </para>
+           <para>
+             Auto-mount the newly created media and opy the U-boot files rom the root 
+             partition to the UBOOT partition (when auto-mounting on Fedora the 
+             partitions will show up as follows):
+             <screen><command>USER= #your username</command>
+ <command>cp /run/media/$USER/__/usr/share/uboot-beaglebone/* /run/media/$USER/uboot/</command>
+ <command>cp /run/media/$USER/uboot/uEnv.txt.beaglebone /run/media/$USER/uboot/uEnv.txt</command>
+       </screen>
+           </para>
+           <para>
+             Insert into your BeagleBone Black and boot. 
+             <note><title>NOTE</title>
+               <para>Do not hold any buttons on the BeagleBone Black to allow U-Boot to
+                  be loaded from eMMC. The LEDs will remain lit in U-Boot and will shut
+                  off when the Fedora kernel is booted).
+               </para>
+             </note>
+           </para>
+           <para>
+             Change one option in this file (only for BeagleBone Black):
+       <screen><command>vi /run/media/$USER/uboot/uEnv.txt</command>
+ <command>abcboard=am335x-bone > abcboard=am335x-boneblack</command></screen>
+             <note>
+               <title>U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)</title>
+               <para>
+                 If you have a recent BeagleBone black (04/2014), the bootloader from the
+                 internal eMMC may refuse to process the Fedora boot script with the
+                 following error:
+       <screen>
+ <command>syntax error</command>
+ <command>## Error: "catX" not defined"</command>
+       </screen>
+               </para>
+               <para>
+                 In such case, you may boot into the factory Debian installation on the
+                 eMMC, and replace loader:
+       <screen>
+ <command>cp /media/uboot/u-boot.img /boot/uboot/</command>
+       </screen>
+               </para>
+             </note>
+           </para>
+         </section>
+ <!-- ======================================= -->
+ 
+     </section>
+     <section id="arm-installation-rawhide-uboot-compulab">
+       <title>For the CompuLab Trimslice</title>
+       <note>
+         <title>Important</title>
+         <para>
+           You must have the latest Device Tree enabled U-Boot to boot the Fedora
+           20 Trimslice image, which you can find 
+           <ulink url="http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#v2012.04-1.02">
+             here.
+           </ulink>
+           And environment variables described
+           <ulink url="http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boot_environment_variable">
+             here.
+           </ulink>
+           Failure to do so will result in a non-booting system.
+         </para>
+       </note>
+       <para>
+         The Trimslice requires no additional steps, U-Boot is included on the
+         device.
+       </para>
+     </section>
+     <section id="arm-imstallation-rawhide-uboot-wandboard">
+       <title>For the Wandboard (Freescale i.MX6)</title>
+       <para>
+         Note - The Wandboard includes a Solo, Dual and Quad core configuration.
+         Determine your hardware configuration and use the appropriate value.
+         While the Wandboard Quad has been tested and confirmed working, the Solo
+         and Dual core models should work as well. The Wandboard Solo uses the
+         same DTB as the Dual (imx6dl-wandboard.dtb). Copy the U-Boot for the
+         Wandboard hardware in use:
+       </para>
+       <screen>
+ <command>BOARD= # Choose 'solo', 'dl' or 'quad'</command>
+ <command>sudo dd if=/tmp/root/usr/share/uboot/wandboard__$BOARD/u-boot.imx of=/dev/&lt;location-of-your-media&gt; bs=1k seek=1 conv=fsync; sync</command>
+       </screen>
+       <note>
+         <title>Important</title>
+         <para>
+           MicroSD for booting is located under the heatsink.
+         </para>
+       </note>
+     </section>
+     <section>
+       <title>For the Pandaboard</title>
+       <para>
+         The Pandaboard no longer requires the use of a VFAT partition. When
+         using a VFAT partition, copy the U-Boot files to the first partition
+         (For reference see
+         <xref linkend="arm-installation-rawhide-pandaboard-vfat" />).
+       </para>
+       <screen>
+ <command>sudo dd if=/tmp/root/usr/share/uboot/panda/MLO of=/dev/&lt;location-of-your-media&gt; count=1 seek=1 conv=notrunc bs=128k</command>
+ <command>sudo dd if=/tmp/root/usr/share/uboot/panda/u-boot.img of=/dev/&lt;location-of-your-media&gt; count=2 seek=1 conv=notrunc bs=384k</command>
+       </screen>
+       <para>
+         The medium should now be ready to boot on the Pandaboard. Insert the
+         card into the device and boot.
+       </para>
+ 
+ <!-- ======================================= -->
+ <!--
+      Source: http://fedoraproject.org/wiki/Architectures/ARM/F20/Installation
+ -->
+       <section id="arm-installation-rawhide-pandaboard-vfat">
+         <title>For the Pandaboard (VFAT)</title>
+         <note>
+           <title>
+             Note
+           </title>
+           <para>
+             This respin includes an updated version of 'Arm-Boot-Config' for the
+             Pandaboard to boot. All other packages are from Fedora 20 GA.
+           </para>
+         </note>
+         <para>
+           Fedora 20 did not include support for the Pandaboard due to issues with
+           the DTB. THis has now been resolved with an update to 'arm-boot-config'
+           and the addition of a U-Boot environmental variable 'bootm_size'. Because
+           these changes were not ready in time for the official release, a Fedora
+           Respin was created specifically for use with the Pandaboard, and use all
+           Fedora 20 GA release pachages with the addition of the 
+           'arm-boot-config-0.62-1.fc20' from the Fedora Updates repository.
+         </para>
+         <para>
+           Download the disk image (Minimal and Xfce images available)
+ <screen>
+ <command>TYPE= # Minimal or Xfce</command>
+ <command>wget http://pwhalen.fedorapeople.org/Fedora/20/Fedora-$TYPE-VFAT-armhfp-20-Respin-sda.raw.xz</command>
+ </screen>
+         </para>
+         <para>
+           Write to the media of your choosing
+ <screen>
+ <command>xzcat -v Fedora-Xfce-VFAT-armhfp-20-Respin-sda.raw.xz | sudo dd of=/dev/&lt;location-of-your-media&gt;</command>
+ </screen>
+         </para>
+         <para>
+           Auto-mount the newly created media and copy the U-Boot files from the root 
+           partition to the UBOOT partition (when auto-mounting on Fedora the 
+           partitions will show up as follows):
+ <screen>
+ <command>USER= #your username</command>
+ <command>cp /run/media/$USER/__/usr/share/uboot-panda/* /run/media/$USER/uboot/</command>
+ </screen>
+         </para>
+         <para>
+           Copy the appropriate file to uEnv.txt (depending on your board - panda, 
+           panda-es, panda-a4)
+ <screen>
+ <command>cp /run/media/$USER/uboot/uEnv.txt{.panda,}</command>
+ </screen>
+         </para>
+         <para>
+           Insert into your device and boot. 
+         </para>
+         <section id="arm-installing-Pandaboard-issues">
+           <title>
+             Known issues on the Pandaboard
+           </title>
+           <itemizedlist>
+             <listitem>
+               <para>
+                 When booting for the first time it is possible for the Pandaboard to
+                 get caught in an infinite loop. If this occurs, stop the boot and
+                 load the 'boot.scr' manually by entering the following:
+ <screen>
+ <command>ext4load mmc 0:3 ${loadaddr} /boot/boot.scr; echo Running boot.scr script from mmc ...; source ${loadaddr}</command>
+ </screen>
+               </para>
+             </listitem>
+           </itemizedlist>
+         </section>
+       </section>
+ 
+ <!-- ======================================= -->
+ 
+     </section>
+     <section id="arm-installation-rawhide-uboot-vexpress">
+       <title>For Versitale Express emulation with QEMU</title>
+       <para>
+         No ARM hardware? No problem! Even without hardware, it is possible to
+         run the Fedora 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.
+       </para>
+       <section id="arm-installation-rawhide-uboot-vexpress-existing">
+         <title>Using an existing disk image</title>
+         <para>
+           Choose a disk image.
+         </para>
+         <screen>
+           <ulink url="http://koji.fedoraproject.org/koji/tasks?state=all&amp;view=tree&amp;method=appliance&amp;order=-id" />
+         </screen>
+         <para>
+           Extract the image:
+         </para>
+ <screen>
+ <command>DATE= # Date of the rawhide image eg - 20140502</command>
+ <command>USER= # your username </command>
+ <command>TYPE= # Type of image used. (eg Minimal, KDE, Xfce, SoaS, MATE)</command>
+ <command>unxz Fedora-$TYPE-armhfp-rawhide-$DATE-sda.raw.xz </command>
+ </screen>
+         <para>
+           Install 'libguestfs-tools' to use virt-copy
+         </para>
+ <screen>
+ <command>sudo yum install -y libguestfs-tools</command>
+ </screen>
+         <para>
+           Extract the kernel and initramfs tools for use with booting.
+         </para>
+ <screen>
+ <command>virt-copy-out -a Fedora-$TYPE-armhfp-rawhide-$DATE-sda.raw /boot .</command>
+ </screen>
+         <para>
+           To boot (you will need to determine the kernel version used in the
+           disk image):
+         </para>
+ <screen>
+ <command>KERN= # kernel version</command>
+ <command>INITRD= # initrd version</command>
+ <command>sudo qemu-system-arm -machine vexpress-a9 -m 1024 -nographic -net nic -net user \</command>
+ <command> -append "console=ttyAMA0,115200n8 rw root=/dev/mmcblk0p3 rootwait physmap.enabled=0" \</command>
+ <command> -kernel $KERN \</command>
+ <command> -initrd $INTRD \</command>
+ <command> -sd Fedora-$TYPE-armhfp-rawhide-$DATE-sda.raw \</command>
+ </screen>
+         <para>
+           For convenience you can also download a script for booting the system
+           <ulink url="http://pwhalen.fedorapeople.org/Fedora/20/boot-vexpress">here.</ulink> 
+           To run the script:
+         </para>
+ <screen>
+ <command>chmod 755 boot-vexpress</command>
+ <command>./boot-vexpress -h</command>
+ <command>Usage: ./boot-vexpress [--gui] --kernel=vmlinuz... --ramfs=initramfs --image=fsimage [--dtb=vexpress.dtb]</command>
+ </screen>
+         <para>
+           Booting with device tree is possible, although passing --gui for
+           graphics will not work at this time (this is due to ongoing platform
+           reword occuring within the Versatile Express kernel code). Booting
+           without device tree is recommended for F20, as it will work in both
+           serial and graphics mode, whereas passing a DTB will only work with
+           serial.
+         </para>
+       </section>
+       <section id="arm-installation-rawhide-vexpress-expand">
+         <title>Expanding the disk image</title>
+         <para>
+           You can easily expand the root partition of the disk image using
+           qemu-img.
+         </para>
+         <para>
+           For example to increase the image size by 10GB you can issue:
+         </para>
+ <screen>
+ <command>qemu-img resize ./file.img +10G</command>
+ </screen>
+       </section>
+       <section id="arm-installation-rawhide-vexpress-netinstall">
+         <title>Interactive network installation</title>
+         <para>
+           Fedora rawhide offers the ability to perform a network installation
+           using either 'vexpress-a15' or 'vexpress-a9'. Using 'vexpress-a15'
+           will allow you to leverage more RAM using the LPAE kernel.
+         </para>
+ <screen>
+ <command># vexpress-a15</command>
+ <command># Create the disk image</command>
+ <command>qemu-img create Fedora-QEMU-A15-armhfp-Rawhide-1-sda.raw $SIZE #add a size EG 8G</command>
+ <command># retrieve DTB </command>
+ <command>wget http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/armhfp/os/images/pxeboot/dtb/vexpress-v2p-ca15-tc1.dtb</command>
+ <command># Begin Install</command>
+ <command>sudo virt-install --name Fedora-QEMU-A15-armhfp-Rawhide-1-sda \</command>
+ <command>--ram 2048         \</command>
+ <command>--arch armv7l      \</command>
+ <command>--machine vexpress-a15 \</command>
+ <command>--location=http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/armhfp/os/ \</command>
+ <command>--disk Fedora-QEMU-A15-armhfp-Rawhide-1-sda.raw \</command>
+ <command>--extra-args="console=ttyAMA0 rw" \</command>
+ <command>--os-variant fedora20             \</command>
+ <command>--graphics none \</command>
+ <command>--boot dtb=`pwd`/vexpress-v2p-ca15-tc1.dtb</command>
+ <command></command>
+ <command># vexpress-a9</command>
+ <command># Create the disk image</command>
+ <command>sudo qemu-img create Fedora-QEMU-A9-armhfp-Rawhide-1-sda.raw $SIZE #add a size EG 8G</command>
+ <command># retrieve DTB</command>
+ <command>wget http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/armhfp/os/images/pxeboot/dtb/vexpress-v2p-ca9.dtb</command>
+ <command># Begin Install</command>
+ <command>sudo virt-install \</command>
+ <command>--name Fedora-QEMU-A9-armhfp-Rawhide-1-sda \</command>
+ <command>--ram 1024 \</command>
+ <command>--arch armv7l      \</command>
+ <command>--machine vexpress-a9 \</command>
+ <command>--location=http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/armhfp/os/ \</command>
+ <command>--disk Fedora-QEMU-A9-armhfp-Rawhide-1-sda.raw \</command>
+ <command>--extra-args="console=ttyAMA0 rw" \</command>
+ <command>--os-variant fedora20             \</command>
+ <command>--graphics none \</command>
+ <command>--boot dtb=`pwd`/vexpress-v2p-ca9.dtb </command>
+ </screen>
+       <para>
+         Complete a Text or VNC installation choosing a software package and
+         partitioning scheme (note when choosing LVM or BTRFS you will need to
+         edit the kernel arguments appropriately). The system will attempt to
+         reboot but fail until the next step is completed.
+       </para>
+       </section>
+       <section id="arm-installation-rawhide-vexpress-extracting">
+         <title>Extracting files from the disk image</title>
+         <para>
+           Once completed you will need to copy the kernel and initramfs and DTB
+           from the disk image for use with Virt-Manager or commandline.
+         </para>
+ <screen>
+ <command>KERN= # kernel version</command>
+ <command>INITRD= # initrd version</command>
+ <command># vexpress-a15</command>
+ <command>sudo virt-copy-out -a Fedora-QEMU-A15-armhfp-20-1-sda.raw /boot/{$KERN,$INITRD} .</command>
+ <command>sudo virt-copy-out -a Fedora-QEMU-A15-armhfp-20-1-sda.raw /boot/dtb-*/vexpress-v2p-ca15-tc1.dtb .</command>
+ <command># vexpress-a9</command>
+ <command>sudo virt-copy-out -a Fedora-QEMU-A9-armhfp-20-1-sda.raw /boot/{$KERN,$INITRD} .</command>
+ <command>sudo virt-copy-out -a Fedora-QEMU-A9-armhfp-20-1-sda.raw /boot/dtb-*/vexpress-v2p-ca9.dtb .</command>
+ </screen>
+       </section>
+       <section id="arm-installation-rawhide-vexpress-booting">
+         <title>Booting the new system</title>
+         <para>
+           Once the files have been extracted you can choose to use the system on
+           the commandline or Virt-Manager. Virt-Manager offers additional
+           flexibility and is recommended for most users.
+         </para>
+         <section id="arm-installation-rawhide-vexpress-booting-virtmanager">
+           <title>Virt-Manager</title>
+           <itemizedlist>
+             <listitem>
+               <para>
+                 Open Virt-Manager and select the image created above. Click on
+                 "Edit -> Virtual Machine Details -> View -> Details".
+               </para>
+             </listitem>
+             <listitem>
+               <para>
+                 Under "Boot Options", add the kernel, initramfs and dtb extracted
+                 above (the DTB should point to the correct path).
+               </para>
+             </listitem>
+             <listitem>
+               <para>
+                 For kernel args add (note- if custom partitioning was used for the
+                 installation you will make adjustments to 'root='):
+ <screen>
+ <command># If you selected Standard Partitioning</command>
+ <command>console=ttyAMA0,115200n8 rw root=/dev/vda3 rootwait</command>
+ <command># If you selected LVM</command>
+ <command>console=ttyAMA0,115200n8 rw root=/dev/mapper/fedora-root rootwait</command>
+ </screen>
+               </para>
+             </listitem>
+             <listitem>
+               <para>
+                 When using the A15 DTB and LPAE kernel it is possible to use more
+                 RAM (12 GB tested).
+               </para>
+             </listitem>
+           </itemizedlist>
+         </section>
+       </section>
+     </section>
+     <section id="arm-installation-rawhide-Calxeda-EnergyCore">
+       <title>For the Calxeda EnergyCore (HighBank and Midway)</title>
+       <para>
+         Fedora Rawhide for ARM includes support for systems that are able to
+         perform a network installation using kickstart, including enterprise
+         hardware such as the HighBank and Midway processors from Calxeda. A
+         working kickstart can be found 
+         <ulink url="http://pwhalen.fedorapeople.org/Fedora/20/Fedora-20-Highbank.ks">here</ulink>
+       </para>
+       <para>
+         Note that the same kickstart can be used interchangeably on HighBank
+         and Midway. For more detailed instructions on setting this up visit this
+         <ulink url="https://fedoraproject.org/wiki/Architectures/ARM/F18/HighBank">page</ulink>
+       </para>
+     </section>
+   </section>
+   <section id="arm-installing-rawhide-firstboot">
+     <title>Booting for the first time</title>
+     <section id="arm-installing-rawhide-firstboot-initial-setup">
+     <title>Initial setup</title>
+       <itemizedlist>
+         <listitem>
+           <para>
+             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 system. To
+             log in to the root account without completing the initial-setup you
+             will need to minimally edit the '/etc/passwd' file and remove the 'x'
+             from the line beginning with 'root' (this will allow you to log into
+             the root account while entering an empty password).
+           </para>
+         </listitem>
+       </itemizedlist>
+     </section>
+     <section id="arm-installing-rawhide-firstboot-resizefs">
+       <title>Resize the root filesystem</title>
+       <para>
+         By default the root parition should be re-sized to fillt he media in use
+         on first boot. To use this additional space run:
+ <screen><command>resize2fs /dev/sda3</command></screen>
+       </para>
+     </section>
+   </section>
+   <section id="arm-installing-rawhide-issues">
+     <title>
+       Known issues
+     </title>
+     <itemizedlist>
+       <listitem>
+         <para>
+           Diplay is currenlty not working on all Target hardware platforms.
+           Display is only working in Vexpress when no DTB is used. (BZ#1082815)
+         </para>
+       </listitem>
+       <listitem>
+         <para>
+           Currently initial-setup will only run on minimal images due to on
+           going display issues.
+         </para>
+       </listitem>
+       <listitem>
+         <para>
+           qemu-1.6.2-4.fc20+ is required to boot the 3.15 kernel. (BZ#1091548)
+         </para>
+       </listitem>
+       <listitem>
+         <para>
+           A15 emulation through QEMU provides no output on console.
+         </para>
+       </listitem>
+       <listitem>
+         <para>
+           The installation tree in th Rawhide repo may be broken at times during
+           the development cycle.
+         </para>
+       </listitem>
+       <listitem>
+         <para>
+           Wandboard does not include console speed and needs to be edited during
+           boot. "setenv console ttymxc0,115200" (BZ#1044778)
+         </para>
+       </listitem>
+       <listitem>
+         <para>
+           After new kernel installation the 'fdtdir' in 
+           '/boot/extlinux/extlinux.conf' needs to be manually updated.
+         </para>
+       </listitem>
+     </itemizedlist>
+   </section>
+   <section id="arm-installing-rawhide-noserial">
+     <title>
+       How to use Fedora ARM when no serial cable or display is available.
+     </title>
+     <para>
+       Though not recommended, it is possible to use Fedora ARM without a serial
+       cable or display. When doing so you may want to limit updates to reduce
+       the possiblity of not being able to boot. (This example is from a Fedora
+       19 system, you may need to adjust the mounts used).
+ <screen>
+ <command>USER= # your user account</command>
+ <command>rm /run/media/$USER/__/etc/systemd/system/graphical.target.wants/initial-setup-graphical.service</command>
+ <command>rm /run/media/$USER/__/etc/systemd/system/multi-user.target.wants/initial-setup-text.service</command>
+ <command>mkdir /run/media/$USER/__/root/.ssh/</command>
+ <command>cat /home/$USER/.ssh/id_rsa.pub >> /run/media/$USER/__/root/.ssh/authorized_keys</command>
+ <command>chmod u=rwX,o=,g=-r /run/media/$USER/__/root/.ssh/</command>
+ </screen>
+     </para>
+     <para>
+       Give the system a few minutes to boot. When it obtains an IP you should be
+       able to ssh into the root account.
+     </para>
+   </section>
+ <!--
+      Source: https://fedoraproject.org/wiki/Architectures/ARM/Rawhide/Installation
+ -->
+ </section>
@@ -5,11 +5,10 @@
  ]>
  
  <section id="arm-platforms">
-   <title />
+   <title>Supported platforms</title>
    <para />
- 
  <!--
- four devices supported in F19:
+ <para>four devices supported in F19:</para>
  <orderedlist>
    <listitem>
      <para>PandaBoards</para>
@@ -22,7 +21,8 @@
      </listitem>
  </orderedlist>
  
- more supported in F20:
+ <para>more supported in F20:</para>
+ <orderedlist>
  <listitem>
    <para>
      <emphasis>calxeda</emphasis> - highbank, midway
@@ -58,10 +58,9 @@
      <emphasis>AllWinner and Rockchips</emphasis> - (initial basic support)
    </para>
  </listitem>
- -->
- 
- 
+ </orderedlist>
  
  
+ -->
  
  </section>