Commit bc75794 Fix: Add the installation details to the manual

4 files Authored by Bart Kuivenhoven 3 years ago , Committed by zoglesby 3 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>

    
1 @@ -0,0 +1,3 @@
2 + *.swp
3 + *~
4 + tmp/
1 @@ -9,6 +9,7 @@
2   »       <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
3   »       <xi:include href="GettingInvolved.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
4   »       <xi:include href="Platforms.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
5 + »       <xi:include href="Installing.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
6   »       <xi:include href="Virtualizing.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
7   »       <xi:include href="Booting.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
8   »       <xi:include href="Packages.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
  1 @@ -0,0 +1,711 @@
  2 + <?xml version='1.0' encoding='utf-8' ?>
  3 + <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  4 + <!ENTITY % BOOK_ENTITIES SYSTEM "ARM_Getting_Started_Guide.ent">
  5 + %BOOK_ENTITIES;
  6 + ]>
  7 + 
  8 + <section id="arm-installation">
  9 +   <title>Installing your board</title>
 10 +   <para />
 11 +   <section id="arm-installation-download">
 12 +     <title>Getting Fedora for ARM</title>
 13 +     <para>
 14 +       This chapter contains information on how to install the development
 15 +       version of Fedora, otherwise known as Rawhide.
 16 +     </para>
 17 +     <section id="arm-installation-download-20">
 18 +       <title>Getting Fedora 20 for ARM</title>
 19 +       <para>
 20 +         Fedora 20 for ARM includes two image types. One for use with platforms
 21 +         requiring a VFAT partition (such as the Texas Instruments' AM335x-based
 22 +         Beaglebone black). The other for use with devices that boot from an EXT3/4
 23 +         partition (such as Compulab's Tegra2-based TrimSlice).
 24 +       </para>
 25 +       <para>
 26 +         For each of these image types there are a number of images providing a
 27 +         variety of desktop choices (including MATE, KDE, XFCE, LXDE and SOAS), as
 28 +         well as a minimal image that does not include the desktop. Any of these
 29 +         images can be used with QEMU on an x86_64 desktop to emulate a fully
 30 +         functional ARM environment.
 31 +       </para>
 32 +       <para>
 33 +         The Fedora 20 images can be downloaded from the following link.
 34 +       </para>
 35 +       <para>
 36 +         <ulink url="http://download.fedoraproject.org/pub/fedora/linux/releases/20/Images/armhfp/">
 37 +           http://download.fedoraproject.org/pub/fedora/linux/releases/20/Images/armhfp/
 38 +         </ulink>
 39 +       </para>
 40 +     </section>
 41 +     <section id="arm-installation-download-rawhide">
 42 +       <title>Getting Fedora Rawhide for ARM</title>
 43 +       <note>
 44 +         <title>Important</title>
 45 +         <para>
 46 +           Fedora Rawhide is pre-release software and not intended for general
 47 +           use.
 48 +         </para>
 49 +       </note>
 50 +       <para>
 51 +         The Rawhide image-based installation process involves downloading an
 52 +         image file (depending upon desktop/non-desktop option desired),
 53 +         inserting removable media into "host" system (e.g. an ARM or x86_64 PC
 54 +         class desktop, laptop, etc.) and performing a few simple commands to
 55 +         write this image onto the media. This media is then used by the ARM
 56 +         "target" system to boot the Fedora Rawhide environment.
 57 +       </para>
 58 +       <para>
 59 +         The download for the latest Rawhide image should be available in our
 60 +         <ulink url="http://koji.fedoraproject.org/koji/tasks?state=all&amp;view=tree&amp;method=appliance&amp;order=-id">
 61 +           Koji build system
 62 +         </ulink>
 63 +       </para>
 64 +       <section id="arm-installation-download-rawhide-status">
 65 +         <title>OVerview of hardware support status</title>
 66 +         <para>
 67 +           A visual overview of the current hardware status in the Fedora kernel
 68 +           can be found at the
 69 +           <ulink url="https://fedoraproject.org/wiki/Architectures/ARM/Rawhide/Installation/Hardware_Status#Current_Rawhide_ARM_Hardware_Status">
 70 +             Rawhide Hardware Support Matrix
 71 +           </ulink>
 72 +         </para>
 73 +         <note>
 74 +           <title>Note</title>
 75 +           <para>
 76 +             The examples provided in this article are from a Fedora 19/20 host
 77 +             and may need to be adjusted for your particular host environment.
 78 +           </para>
 79 +         </note>
 80 +       </section>
 81 +     </section>
 82 +   </section>
 83 + 
 84 +   <section id="arm-installation-rawhide-scripted">
 85 +     <title>Scripted</title>
 86 +     <para>
 87 +       Execute the following script as a user with sudo privileges. It will copy
 88 +       the selected disk image and write the appropriate U-Boot for the target
 89 +       hardware platform. Optionally you can also enable and disable SE Linux and
 90 +       remove the root password requirement (allowing log in without a completely
 91 +       initialised setup). To add a board not listed, simply create a bash
 92 +       scriptlet with the commands needed to copy U-Boot to media.
 93 +     </para>
 94 +     <itemizedlist>
 95 +       <listitem>
 96 +         <para>
 97 +           <ulink url="http://pwhalen.fedorapeople.org/fedora-arm-image-installer.tar.bz2" />
 98 +         </para>
 99 +       </listitem>
100 +     </itemizedlist>
101 +     <screen>
102 + <command>./fedora-arm-image-installer.sh </command>
103 + <command></command>
104 + <command>Usage: fedora-arm-image-installer.sh &lt;options&gt;</command>
105 + <command></command>
106 + <command>   --image=IMAGE    - raw image file name</command>
107 + <command>   --target=TARGET  - target board</command>
108 + <command>          [beaglebone|Cubietruck|panda|trimslice|wandboard_dl|wandboard_quad|wandboard_solo]</command>
109 + <command>   --media=DEVICE   - media device file (/dev/[sdX|mmcblkX])</command>
110 + <command>   --selinux=ON/OFF - Turn SELinux off/on as needed</command>
111 + <command>   --norootpass     - Remove the root password</command>
112 + <command>    -y              - Assumes yes, will not wait for confirmation</command>
113 + <command>   --version        - Display version and exit</command>
114 + <command></command>
115 + <command>Example: fedora-arm-image-installer.sh --image=Fedora-Rawhide.xz --target=panda --media=/dev/mmcblk0 --selinux=OFF</command>
116 +     </screen>
117 +   </section>
118 +   <section id="arm-installation-Rawhide">
119 +     <title>Manual</title>
120 +     <para>Choose a disk image.</para>
121 +     <screen>
122 + <command><ulink url="http://koji.fedoraproject.org/koji/tasks?state=all&amp;view=tree&amp;method=appliance&amp;order=-id" /></command>
123 +     </screen>
124 +     <para>
125 +       Write the image to your media.
126 +     </para>
127 +     <screen>
128 + <command>DATE=  # Date of the rawhide image eg - 20140502</command>
129 + <command>USER=  # your username </command>
130 + <command>TYPE=  # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal</command>
131 + <command>MEDIA= #/dev/&lt;location-of-your-media&gt; </command>
132 + <command>xzcat Fedora-$TYPE-armhfp-rawhide-$DATE-sda.raw.xz | sudo dd of=$MEDIA; sync</command>
133 +     </screen>
134 +     <para>
135 +       After writing the image, read the new partition table and mount the root
136 +       partition.
137 +     </para>
138 +     <screen>
139 + <command>partprobe $MEDIA</command>
140 + <command>mkdir /tmp/root; sudo mount /dev/&lt;media-location&gt; /tmp/root</command>
141 +     </screen>
142 +     <para>
143 +       Copy the appropriate U-Boot files for your target hardware listed below.
144 +     </para>
145 +   </section>
146 +   <section id="arm-installation-rawhide-uboot">
147 +     <title>Write U-Boot to media</title>
148 +     <para>
149 +       Follow the steps listed under your architecture to write the appropriate
150 +       U-Boot for your hardware.
151 +     </para>
152 +     <section id="arm-installation-rawhide-uboot-cubietruck">
153 +       <title>For the CubieTruck (Allwinner A20)</title>
154 +       <para>
155 +         <screen>
156 + <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>
157 +         </screen>
158 +         The medium should now be ready to boot on the Cubietruck. insert it into
159 +         the device and boot.
160 +       </para>
161 +     </section>
162 +     <section id="arm-installation-rawhide-uboot-beaglebone">
163 +       <title>For the BeagleBone (Black &amp; White)</title>
164 +       <note>
165 +         <title>Important</title>
166 +         <para>
167 +           At this time a serial consile cable is required for the BeagleBone
168 +           Black. For those without the option of a serial cable however, please
169 +           consult 
170 +           <link linkend="arm-installing-rawhide-noserial">
171 +             the following sub chapter.
172 +           </link>
173 +         </para>
174 +       </note>
175 +       <para>
176 +         The BeagleBone Black/White no longer requires the use of a VFAT
177 +         partition. When using a VFAT partition, copy the U-Boot files to the
178 +         first partition (for reference see 
179 +         <xref linkend="arm-installation-rawhide-beaglebone-black-vfat" />)
180 +       </para>
181 +       <screen>
182 + <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>
183 + <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>
184 +       </screen>
185 +       <para>
186 +         The medium should now be ready to boot on the BeagleBone. Insert it into
187 +         the device and boot.
188 +       </para>
189 + 
190 + <!-- ======================================= -->
191 + <!--
192 +      Source: http://fedoraproject.org/wiki/Architectures/ARM/F20/Installation
193 + -->
194 +       <section id="arm-installation-rawhide-beaglebone-black-vfat">
195 +         <title>BeagleBone (Black) (VFAT partition)</title>
196 +           <note>
197 +             <title>Important</title>
198 +             <para>
199 +               At this time a serial consile cable is required for the BeagleBone
200 +               Black. For those without the option of a serial cable however, please
201 +               consult 
202 +               <link linkend="arm-installing-rawhide-noserial">
203 +                 the following sub chapter.
204 +               </link>
205 +             </para>
206 +           </note>
207 +           <para>
208 +             Support for the BeagleBone Black has been added in Fedora 20. The GA
209 +             release includes basic support which will be extended to include HDMI and 
210 +             USB with the release of the 3.12 kernel. A remix is planned when support 
211 +             is available. In the interim, the minimal image is recommended.
212 +             <screen><command>TYPE= # options include KDE, LXDE, XFCE, SoaS, Mate and Minimal</command>
213 + <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>
214 +           </para>
215 +           <para>
216 +             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>
217 +           </para>
218 +           <para>
219 +             Auto-mount the newly created media and opy the U-boot files rom the root 
220 +             partition to the UBOOT partition (when auto-mounting on Fedora the 
221 +             partitions will show up as follows):
222 +             <screen><command>USER= #your username</command>
223 + <command>cp /run/media/$USER/__/usr/share/uboot-beaglebone/* /run/media/$USER/uboot/</command>
224 + <command>cp /run/media/$USER/uboot/uEnv.txt.beaglebone /run/media/$USER/uboot/uEnv.txt</command>
225 +       </screen>
226 +           </para>
227 +           <para>
228 +             Insert into your BeagleBone Black and boot. 
229 +             <note><title>NOTE</title>
230 +               <para>Do not hold any buttons on the BeagleBone Black to allow U-Boot to
231 +                  be loaded from eMMC. The LEDs will remain lit in U-Boot and will shut
232 +                  off when the Fedora kernel is booted).
233 +               </para>
234 +             </note>
235 +           </para>
236 +           <para>
237 +             Change one option in this file (only for BeagleBone Black):
238 +       <screen><command>vi /run/media/$USER/uboot/uEnv.txt</command>
239 + <command>abcboard=am335x-bone > abcboard=am335x-boneblack</command></screen>
240 +             <note>
241 +               <title>U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)</title>
242 +               <para>
243 +                 If you have a recent BeagleBone black (04/2014), the bootloader from the
244 +                 internal eMMC may refuse to process the Fedora boot script with the
245 +                 following error:
246 +       <screen>
247 + <command>syntax error</command>
248 + <command>## Error: "catX" not defined"</command>
249 +       </screen>
250 +               </para>
251 +               <para>
252 +                 In such case, you may boot into the factory Debian installation on the
253 +                 eMMC, and replace loader:
254 +       <screen>
255 + <command>cp /media/uboot/u-boot.img /boot/uboot/</command>
256 +       </screen>
257 +               </para>
258 +             </note>
259 +           </para>
260 +         </section>
261 + <!-- ======================================= -->
262 + 
263 +     </section>
264 +     <section id="arm-installation-rawhide-uboot-compulab">
265 +       <title>For the CompuLab Trimslice</title>
266 +       <note>
267 +         <title>Important</title>
268 +         <para>
269 +           You must have the latest Device Tree enabled U-Boot to boot the Fedora
270 +           20 Trimslice image, which you can find 
271 +           <ulink url="http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#v2012.04-1.02">
272 +             here.
273 +           </ulink>
274 +           And environment variables described
275 +           <ulink url="http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boot_environment_variable">
276 +             here.
277 +           </ulink>
278 +           Failure to do so will result in a non-booting system.
279 +         </para>
280 +       </note>
281 +       <para>
282 +         The Trimslice requires no additional steps, U-Boot is included on the
283 +         device.
284 +       </para>
285 +     </section>
286 +     <section id="arm-imstallation-rawhide-uboot-wandboard">
287 +       <title>For the Wandboard (Freescale i.MX6)</title>
288 +       <para>
289 +         Note - The Wandboard includes a Solo, Dual and Quad core configuration.
290 +         Determine your hardware configuration and use the appropriate value.
291 +         While the Wandboard Quad has been tested and confirmed working, the Solo
292 +         and Dual core models should work as well. The Wandboard Solo uses the
293 +         same DTB as the Dual (imx6dl-wandboard.dtb). Copy the U-Boot for the
294 +         Wandboard hardware in use:
295 +       </para>
296 +       <screen>
297 + <command>BOARD= # Choose 'solo', 'dl' or 'quad'</command>
298 + <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>
299 +       </screen>
300 +       <note>
301 +         <title>Important</title>
302 +         <para>
303 +           MicroSD for booting is located under the heatsink.
304 +         </para>
305 +       </note>
306 +     </section>
307 +     <section>
308 +       <title>For the Pandaboard</title>
309 +       <para>
310 +         The Pandaboard no longer requires the use of a VFAT partition. When
311 +         using a VFAT partition, copy the U-Boot files to the first partition
312 +         (For reference see
313 +         <xref linkend="arm-installation-rawhide-pandaboard-vfat" />).
314 +       </para>
315 +       <screen>
316 + <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>
317 + <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>
318 +       </screen>
319 +       <para>
320 +         The medium should now be ready to boot on the Pandaboard. Insert the
321 +         card into the device and boot.
322 +       </para>
323 + 
324 + <!-- ======================================= -->
325 + <!--
326 +      Source: http://fedoraproject.org/wiki/Architectures/ARM/F20/Installation
327 + -->
328 +       <section id="arm-installation-rawhide-pandaboard-vfat">
329 +         <title>For the Pandaboard (VFAT)</title>
330 +         <note>
331 +           <title>
332 +             Note
333 +           </title>
334 +           <para>
335 +             This respin includes an updated version of 'Arm-Boot-Config' for the
336 +             Pandaboard to boot. All other packages are from Fedora 20 GA.
337 +           </para>
338 +         </note>
339 +         <para>
340 +           Fedora 20 did not include support for the Pandaboard due to issues with
341 +           the DTB. THis has now been resolved with an update to 'arm-boot-config'
342 +           and the addition of a U-Boot environmental variable 'bootm_size'. Because
343 +           these changes were not ready in time for the official release, a Fedora
344 +           Respin was created specifically for use with the Pandaboard, and use all
345 +           Fedora 20 GA release pachages with the addition of the 
346 +           'arm-boot-config-0.62-1.fc20' from the Fedora Updates repository.
347 +         </para>
348 +         <para>
349 +           Download the disk image (Minimal and Xfce images available)
350 + <screen>
351 + <command>TYPE= # Minimal or Xfce</command>
352 + <command>wget http://pwhalen.fedorapeople.org/Fedora/20/Fedora-$TYPE-VFAT-armhfp-20-Respin-sda.raw.xz</command>
353 + </screen>
354 +         </para>
355 +         <para>
356 +           Write to the media of your choosing
357 + <screen>
358 + <command>xzcat -v Fedora-Xfce-VFAT-armhfp-20-Respin-sda.raw.xz | sudo dd of=/dev/&lt;location-of-your-media&gt;</command>
359 + </screen>
360 +         </para>
361 +         <para>
362 +           Auto-mount the newly created media and copy the U-Boot files from the root 
363 +           partition to the UBOOT partition (when auto-mounting on Fedora the 
364 +           partitions will show up as follows):
365 + <screen>
366 + <command>USER= #your username</command>
367 + <command>cp /run/media/$USER/__/usr/share/uboot-panda/* /run/media/$USER/uboot/</command>
368 + </screen>
369 +         </para>
370 +         <para>
371 +           Copy the appropriate file to uEnv.txt (depending on your board - panda, 
372 +           panda-es, panda-a4)
373 + <screen>
374 + <command>cp /run/media/$USER/uboot/uEnv.txt{.panda,}</command>
375 + </screen>
376 +         </para>
377 +         <para>
378 +           Insert into your device and boot. 
379 +         </para>
380 +         <section id="arm-installing-Pandaboard-issues">
381 +           <title>
382 +             Known issues on the Pandaboard
383 +           </title>
384 +           <itemizedlist>
385 +             <listitem>
386 +               <para>
387 +                 When booting for the first time it is possible for the Pandaboard to
388 +                 get caught in an infinite loop. If this occurs, stop the boot and
389 +                 load the 'boot.scr' manually by entering the following:
390 + <screen>
391 + <command>ext4load mmc 0:3 ${loadaddr} /boot/boot.scr; echo Running boot.scr script from mmc ...; source ${loadaddr}</command>
392 + </screen>
393 +               </para>
394 +             </listitem>
395 +           </itemizedlist>
396 +         </section>
397 +       </section>
398 + 
399 + <!-- ======================================= -->
400 + 
401 +     </section>
402 +     <section id="arm-installation-rawhide-uboot-vexpress">
403 +       <title>For Versitale Express emulation with QEMU</title>
404 +       <para>
405 +         No ARM hardware? No problem! Even without hardware, it is possible to
406 +         run the Fedora for ARM images using the QEMU emulator program. Any image
407 +         can be used, and you can choose a script method or manual depending on
408 +         your preference.
409 +       </para>
410 +       <section id="arm-installation-rawhide-uboot-vexpress-existing">
411 +         <title>Using an existing disk image</title>
412 +         <para>
413 +           Choose a disk image.
414 +         </para>
415 +         <screen>
416 +           <ulink url="http://koji.fedoraproject.org/koji/tasks?state=all&amp;view=tree&amp;method=appliance&amp;order=-id" />
417 +         </screen>
418 +         <para>
419 +           Extract the image:
420 +         </para>
421 + <screen>
422 + <command>DATE= # Date of the rawhide image eg - 20140502</command>
423 + <command>USER= # your username </command>
424 + <command>TYPE= # Type of image used. (eg Minimal, KDE, Xfce, SoaS, MATE)</command>
425 + <command>unxz Fedora-$TYPE-armhfp-rawhide-$DATE-sda.raw.xz </command>
426 + </screen>
427 +         <para>
428 +           Install 'libguestfs-tools' to use virt-copy
429 +         </para>
430 + <screen>
431 + <command>sudo yum install -y libguestfs-tools</command>
432 + </screen>
433 +         <para>
434 +           Extract the kernel and initramfs tools for use with booting.
435 +         </para>
436 + <screen>
437 + <command>virt-copy-out -a Fedora-$TYPE-armhfp-rawhide-$DATE-sda.raw /boot .</command>
438 + </screen>
439 +         <para>
440 +           To boot (you will need to determine the kernel version used in the
441 +           disk image):
442 +         </para>
443 + <screen>
444 + <command>KERN= # kernel version</command>
445 + <command>INITRD= # initrd version</command>
446 + <command>sudo qemu-system-arm -machine vexpress-a9 -m 1024 -nographic -net nic -net user \</command>
447 + <command> -append "console=ttyAMA0,115200n8 rw root=/dev/mmcblk0p3 rootwait physmap.enabled=0" \</command>
448 + <command> -kernel $KERN \</command>
449 + <command> -initrd $INTRD \</command>
450 + <command> -sd Fedora-$TYPE-armhfp-rawhide-$DATE-sda.raw \</command>
451 + </screen>
452 +         <para>
453 +           For convenience you can also download a script for booting the system
454 +           <ulink url="http://pwhalen.fedorapeople.org/Fedora/20/boot-vexpress">here.</ulink> 
455 +           To run the script:
456 +         </para>
457 + <screen>
458 + <command>chmod 755 boot-vexpress</command>
459 + <command>./boot-vexpress -h</command>
460 + <command>Usage: ./boot-vexpress [--gui] --kernel=vmlinuz... --ramfs=initramfs --image=fsimage [--dtb=vexpress.dtb]</command>
461 + </screen>
462 +         <para>
463 +           Booting with device tree is possible, although passing --gui for
464 +           graphics will not work at this time (this is due to ongoing platform
465 +           reword occuring within the Versatile Express kernel code). Booting
466 +           without device tree is recommended for F20, as it will work in both
467 +           serial and graphics mode, whereas passing a DTB will only work with
468 +           serial.
469 +         </para>
470 +       </section>
471 +       <section id="arm-installation-rawhide-vexpress-expand">
472 +         <title>Expanding the disk image</title>
473 +         <para>
474 +           You can easily expand the root partition of the disk image using
475 +           qemu-img.
476 +         </para>
477 +         <para>
478 +           For example to increase the image size by 10GB you can issue:
479 +         </para>
480 + <screen>
481 + <command>qemu-img resize ./file.img +10G</command>
482 + </screen>
483 +       </section>
484 +       <section id="arm-installation-rawhide-vexpress-netinstall">
485 +         <title>Interactive network installation</title>
486 +         <para>
487 +           Fedora rawhide offers the ability to perform a network installation
488 +           using either 'vexpress-a15' or 'vexpress-a9'. Using 'vexpress-a15'
489 +           will allow you to leverage more RAM using the LPAE kernel.
490 +         </para>
491 + <screen>
492 + <command># vexpress-a15</command>
493 + <command># Create the disk image</command>
494 + <command>qemu-img create Fedora-QEMU-A15-armhfp-Rawhide-1-sda.raw $SIZE #add a size EG 8G</command>
495 + <command># retrieve DTB </command>
496 + <command>wget http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/armhfp/os/images/pxeboot/dtb/vexpress-v2p-ca15-tc1.dtb</command>
497 + <command># Begin Install</command>
498 + <command>sudo virt-install --name Fedora-QEMU-A15-armhfp-Rawhide-1-sda \</command>
499 + <command>--ram 2048         \</command>
500 + <command>--arch armv7l      \</command>
501 + <command>--machine vexpress-a15 \</command>
502 + <command>--location=http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/armhfp/os/ \</command>
503 + <command>--disk Fedora-QEMU-A15-armhfp-Rawhide-1-sda.raw \</command>
504 + <command>--extra-args="console=ttyAMA0 rw" \</command>
505 + <command>--os-variant fedora20             \</command>
506 + <command>--graphics none \</command>
507 + <command>--boot dtb=`pwd`/vexpress-v2p-ca15-tc1.dtb</command>
508 + <command></command>
509 + <command># vexpress-a9</command>
510 + <command># Create the disk image</command>
511 + <command>sudo qemu-img create Fedora-QEMU-A9-armhfp-Rawhide-1-sda.raw $SIZE #add a size EG 8G</command>
512 + <command># retrieve DTB</command>
513 + <command>wget http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/armhfp/os/images/pxeboot/dtb/vexpress-v2p-ca9.dtb</command>
514 + <command># Begin Install</command>
515 + <command>sudo virt-install \</command>
516 + <command>--name Fedora-QEMU-A9-armhfp-Rawhide-1-sda \</command>
517 + <command>--ram 1024 \</command>
518 + <command>--arch armv7l      \</command>
519 + <command>--machine vexpress-a9 \</command>
520 + <command>--location=http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/armhfp/os/ \</command>
521 + <command>--disk Fedora-QEMU-A9-armhfp-Rawhide-1-sda.raw \</command>
522 + <command>--extra-args="console=ttyAMA0 rw" \</command>
523 + <command>--os-variant fedora20             \</command>
524 + <command>--graphics none \</command>
525 + <command>--boot dtb=`pwd`/vexpress-v2p-ca9.dtb </command>
526 + </screen>
527 +       <para>
528 +         Complete a Text or VNC installation choosing a software package and
529 +         partitioning scheme (note when choosing LVM or BTRFS you will need to
530 +         edit the kernel arguments appropriately). The system will attempt to
531 +         reboot but fail until the next step is completed.
532 +       </para>
533 +       </section>
534 +       <section id="arm-installation-rawhide-vexpress-extracting">
535 +         <title>Extracting files from the disk image</title>
536 +         <para>
537 +           Once completed you will need to copy the kernel and initramfs and DTB
538 +           from the disk image for use with Virt-Manager or commandline.
539 +         </para>
540 + <screen>
541 + <command>KERN= # kernel version</command>
542 + <command>INITRD= # initrd version</command>
543 + <command># vexpress-a15</command>
544 + <command>sudo virt-copy-out -a Fedora-QEMU-A15-armhfp-20-1-sda.raw /boot/{$KERN,$INITRD} .</command>
545 + <command>sudo virt-copy-out -a Fedora-QEMU-A15-armhfp-20-1-sda.raw /boot/dtb-*/vexpress-v2p-ca15-tc1.dtb .</command>
546 + <command># vexpress-a9</command>
547 + <command>sudo virt-copy-out -a Fedora-QEMU-A9-armhfp-20-1-sda.raw /boot/{$KERN,$INITRD} .</command>
548 + <command>sudo virt-copy-out -a Fedora-QEMU-A9-armhfp-20-1-sda.raw /boot/dtb-*/vexpress-v2p-ca9.dtb .</command>
549 + </screen>
550 +       </section>
551 +       <section id="arm-installation-rawhide-vexpress-booting">
552 +         <title>Booting the new system</title>
553 +         <para>
554 +           Once the files have been extracted you can choose to use the system on
555 +           the commandline or Virt-Manager. Virt-Manager offers additional
556 +           flexibility and is recommended for most users.
557 +         </para>
558 +         <section id="arm-installation-rawhide-vexpress-booting-virtmanager">
559 +           <title>Virt-Manager</title>
560 +           <itemizedlist>
561 +             <listitem>
562 +               <para>
563 +                 Open Virt-Manager and select the image created above. Click on
564 +                 "Edit -> Virtual Machine Details -> View -> Details".
565 +               </para>
566 +             </listitem>
567 +             <listitem>
568 +               <para>
569 +                 Under "Boot Options", add the kernel, initramfs and dtb extracted
570 +                 above (the DTB should point to the correct path).
571 +               </para>
572 +             </listitem>
573 +             <listitem>
574 +               <para>
575 +                 For kernel args add (note- if custom partitioning was used for the
576 +                 installation you will make adjustments to 'root='):
577 + <screen>
578 + <command># If you selected Standard Partitioning</command>
579 + <command>console=ttyAMA0,115200n8 rw root=/dev/vda3 rootwait</command>
580 + <command># If you selected LVM</command>
581 + <command>console=ttyAMA0,115200n8 rw root=/dev/mapper/fedora-root rootwait</command>
582 + </screen>
583 +               </para>
584 +             </listitem>
585 +             <listitem>
586 +               <para>
587 +                 When using the A15 DTB and LPAE kernel it is possible to use more
588 +                 RAM (12 GB tested).
589 +               </para>
590 +             </listitem>
591 +           </itemizedlist>
592 +         </section>
593 +       </section>
594 +     </section>
595 +     <section id="arm-installation-rawhide-Calxeda-EnergyCore">
596 +       <title>For the Calxeda EnergyCore (HighBank and Midway)</title>
597 +       <para>
598 +         Fedora Rawhide for ARM includes support for systems that are able to
599 +         perform a network installation using kickstart, including enterprise
600 +         hardware such as the HighBank and Midway processors from Calxeda. A
601 +         working kickstart can be found 
602 +         <ulink url="http://pwhalen.fedorapeople.org/Fedora/20/Fedora-20-Highbank.ks">here</ulink>
603 +       </para>
604 +       <para>
605 +         Note that the same kickstart can be used interchangeably on HighBank
606 +         and Midway. For more detailed instructions on setting this up visit this
607 +         <ulink url="https://fedoraproject.org/wiki/Architectures/ARM/F18/HighBank">page</ulink>
608 +       </para>
609 +     </section>
610 +   </section>
611 +   <section id="arm-installing-rawhide-firstboot">
612 +     <title>Booting for the first time</title>
613 +     <section id="arm-installing-rawhide-firstboot-initial-setup">
614 +     <title>Initial setup</title>
615 +       <itemizedlist>
616 +         <listitem>
617 +           <para>
618 +             During the first boot the system will launch the 'initial-setup'
619 +             utility. For graphical images this will occur on the display, for
620 +             minimal images this will occur on the serial console. Failure to
621 +             complete the initial-setup will prevent logging into the system. To
622 +             log in to the root account without completing the initial-setup you
623 +             will need to minimally edit the '/etc/passwd' file and remove the 'x'
624 +             from the line beginning with 'root' (this will allow you to log into
625 +             the root account while entering an empty password).
626 +           </para>
627 +         </listitem>
628 +       </itemizedlist>
629 +     </section>
630 +     <section id="arm-installing-rawhide-firstboot-resizefs">
631 +       <title>Resize the root filesystem</title>
632 +       <para>
633 +         By default the root parition should be re-sized to fillt he media in use
634 +         on first boot. To use this additional space run:
635 + <screen><command>resize2fs /dev/sda3</command></screen>
636 +       </para>
637 +     </section>
638 +   </section>
639 +   <section id="arm-installing-rawhide-issues">
640 +     <title>
641 +       Known issues
642 +     </title>
643 +     <itemizedlist>
644 +       <listitem>
645 +         <para>
646 +           Diplay is currenlty not working on all Target hardware platforms.
647 +           Display is only working in Vexpress when no DTB is used. (BZ#1082815)
648 +         </para>
649 +       </listitem>
650 +       <listitem>
651 +         <para>
652 +           Currently initial-setup will only run on minimal images due to on
653 +           going display issues.
654 +         </para>
655 +       </listitem>
656 +       <listitem>
657 +         <para>
658 +           qemu-1.6.2-4.fc20+ is required to boot the 3.15 kernel. (BZ#1091548)
659 +         </para>
660 +       </listitem>
661 +       <listitem>
662 +         <para>
663 +           A15 emulation through QEMU provides no output on console.
664 +         </para>
665 +       </listitem>
666 +       <listitem>
667 +         <para>
668 +           The installation tree in th Rawhide repo may be broken at times during
669 +           the development cycle.
670 +         </para>
671 +       </listitem>
672 +       <listitem>
673 +         <para>
674 +           Wandboard does not include console speed and needs to be edited during
675 +           boot. "setenv console ttymxc0,115200" (BZ#1044778)
676 +         </para>
677 +       </listitem>
678 +       <listitem>
679 +         <para>
680 +           After new kernel installation the 'fdtdir' in 
681 +           '/boot/extlinux/extlinux.conf' needs to be manually updated.
682 +         </para>
683 +       </listitem>
684 +     </itemizedlist>
685 +   </section>
686 +   <section id="arm-installing-rawhide-noserial">
687 +     <title>
688 +       How to use Fedora ARM when no serial cable or display is available.
689 +     </title>
690 +     <para>
691 +       Though not recommended, it is possible to use Fedora ARM without a serial
692 +       cable or display. When doing so you may want to limit updates to reduce
693 +       the possiblity of not being able to boot. (This example is from a Fedora
694 +       19 system, you may need to adjust the mounts used).
695 + <screen>
696 + <command>USER= # your user account</command>
697 + <command>rm /run/media/$USER/__/etc/systemd/system/graphical.target.wants/initial-setup-graphical.service</command>
698 + <command>rm /run/media/$USER/__/etc/systemd/system/multi-user.target.wants/initial-setup-text.service</command>
699 + <command>mkdir /run/media/$USER/__/root/.ssh/</command>
700 + <command>cat /home/$USER/.ssh/id_rsa.pub >> /run/media/$USER/__/root/.ssh/authorized_keys</command>
701 + <command>chmod u=rwX,o=,g=-r /run/media/$USER/__/root/.ssh/</command>
702 + </screen>
703 +     </para>
704 +     <para>
705 +       Give the system a few minutes to boot. When it obtains an IP you should be
706 +       able to ssh into the root account.
707 +     </para>
708 +   </section>
709 + <!--
710 +      Source: https://fedoraproject.org/wiki/Architectures/ARM/Rawhide/Installation
711 + -->
712 + </section>
 1 @@ -5,11 +5,10 @@
 2   ]>
 3   
 4   <section id="arm-platforms">
 5 -   <title />
 6 +   <title>Supported platforms</title>
 7     <para />
 8 - 
 9   <!--
10 - four devices supported in F19:
11 + <para>four devices supported in F19:</para>
12   <orderedlist>
13     <listitem>
14       <para>PandaBoards</para>
15 @@ -22,7 +21,8 @@
16       </listitem>
17   </orderedlist>
18   
19 - more supported in F20:
20 + <para>more supported in F20:</para>
21 + <orderedlist>
22   <listitem>
23     <para>
24       <emphasis>calxeda</emphasis> - highbank, midway
25 @@ -58,10 +58,9 @@
26       <emphasis>AllWinner and Rockchips</emphasis> - (initial basic support)
27     </para>
28   </listitem>
29 - -->
30 - 
31 - 
32 + </orderedlist>
33   
34   
35 + -->
36   
37   </section>