Thursday 31 May 2012

Raspberry Pi compiling and development on Fedora 17

My last post explained how to run Fedora 17 on the Raspberry Pi.  An SD card is OK to run software from, but it is not the best configuration for doing things (like compiling software) that involve lots of random "disk" reads and writes.

If you are going to be compiling lots software it makes sense to use a USB hard-drive.  This guide explains how to boot Fedora 17 from an SD card (the Raspberry Pi must boot from an SD card) but run the root file-system from a USB hard-drive.

In addition to the assumptions in my last post, I am assuming:

  • Your USB hard-drive is /dev/sdb when connected to your computer.   If your USB hard-drive is on a different device file then make sure you work out what it is and use the right file-name in the instructions below - getting this wrong could permanently lose data.
Complete steps 1 and 2 from my last post before continuing here:
  1. Delete the unnecessary root filesystem from the SD card:
    # fdisk /dev/mmcblk0 (commands I entered and comments in bold below)

    Command (m for help): d
    Partition number (1-4): 2
    Command (m for help): w
    The partition table has been altered!

    Calling ioctl() to re-read partition table.

    Syncing disks.
  2. Update the SD card so that the Raspberry Pi looks for the root file-system on a USB hard-drive:
    # mkdir /tmp/boot_pi
    # mount /dev/mmcblk0p1 /tmp/boot_pi

    # vim /tmp/boot_pi/cmdline.txt (change root=/dev/mmcblk0p2 to root=/dev/sda2 - this really is /dev/sda here as that is how it will appear on the Raspberry Pi)

    # umount /tmp/boot_pi

    # rmdir /tmp/boot_pi
  3. Connect the USB hard-drive to your computer (unmount it if your computer automounts it for you) and write the image to the hard-drive:
    # xzcat f17arm-latest-arm-rpi-mmcblk0.img.xz > /dev/sdb
  4. Delete the unnecessary boot partition from the hard-drive and resize the root file-system:
    # fdisk /dev/sdb (commands I entered and comments in bold below)

    Command (m for help): p

    Disk /dev/sdb: 80.0 GB, 80026361856 bytes
    81 heads, 63 sectors/track, 30629 cylinders, total 156301488 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000

       Device Boot      Start         End      Blocks   Id System
    /dev/sdb1   *          63     1044224      522081    c  W9...
    /dev/sdb2         1044225     7784447     3370111+  83  Linux

    Command (m for help): d
    Partition number (1-4): 2

    Command (m for help): n
    Partition type:
       p   primary (1 primary, 0 extended, 3 free)
       e   extended
    Select (default p): p
    Partition number (1-4, default 2): 2
    The first sector must be the start sector of /dev/sdb2 (above).  This number may be different on your hard-drive.  It should be the default value here - but check it carefully anyway.

    First sector (1044225-156301488, default 1044225): 1044225
    The last sector should be the default if you want to use all available space on the hard-drive.  If the default is what you want just press return.

    Last sector, +sectors or +size{K,M,G} (1044225-156301488, default 156301488):

    Using default value 156301488

    Command (m for help): d
    Partition number (1-4): 1

    Command (m for help): w

    The partition table has been altered!

    Calling ioctl() to re-read partition table.

    Syncing disks.
    # e2fsck -f /dev/sdb2
    # resize2fs /dev/sdb2
    # mkdir /tmp/rootfs_pi
    # mount /dev/sdb2 /tmp/rootfs_pi
    # rm -f /tmp/rootfs_pi/etc/systemd/system/multi-user.target.wants/rootfs-resize.service
    # umount /tmp/rootfs_pi
    # rmdir /tmp/rootfs_pi
  5. Now eject the SD card from your reader and disconnect your USB hard-drive, put the SD card in your Raspberry Pi and connect the USB hard-drive and power up.  Once it has booted log in as "root" using the password "fedoraarm".  (Assuming that you are connected over a wired LAN with a DHCP server) the Raspberry Pi will automatically obtain an IP address and LAN settings (I am going to assume this is the case - if not the process for configuring networking is exactly the same as it is on any other Fedora 17 machine).
  6. Update your packages:
    # yum update

    Don't worry about the fact that a new kernel is installed - even though this new kernel is not Raspberry Pi compatible.  When a new kernel is installed using "yum update" the old one (and it's modules) are not removed.  Also, because of the way the UBOOT partition in the images works, installing a new kernel does not change the default kernel used when you boot.
Job done.  You now have a perfectly usable and up-to-date Fedora 17 Raspberry Pi SD card and USB hard-drive combination.

Fedora 17 on Raspberry Pi

I received my Raspberry Pi this week and set about installing Fedora, my operating system of choice, on it.  Unfortunately, Fedora 14 is regarded as unstable on the Raspberry Pi and Fedora 17 isn't quite ready for it yet.

However, there are some very good nightly snapshots of Fedora 17 (http://scotland.proximity.on.ca/arm-nightlies/) for Raspberry Pi available.  I thought I would put together a short guide on using these.

This guide assumes:
  • You are logged in as root on a Linux computer
  • Your SD card is /dev/mmcblk0 when inserted into your SD card reader.  If your SD card is on a different device file then make sure you work out what it is and use the right file-name in the instructions below - getting this wrong could permanently lose data.


The first thing to do is to select the image you want to install.  The nightly builds come in three flavours:
  1. Console only (this is the one I use and referred to in the rest of the instructions)
  2. Minimal X Windows
  3. XFCE

Once you have chosen your image the process is:
  1. Download the software (replace the URL here with the one for the image you have selected):
    # wget http://scotland.proximity.on.ca/arm-nightlies/vault/f17arm-latest-arm-rpi-mmcblk0.img.xz
  2. Insert your SD card (unmount it if your computer automounts it for you) and write the image to the card:
    # xzcat f17arm-latest-arm-rpi-mmcblk0.img.xz > /dev/mmcblk0
  3. When your Raspberry Pi boots this image for the first time it will resize the root file-system to use up the whole card.  Waiting for this is tedious and it gets in the way of using your Raspberry Pi right away.  Fortunately, on a Linux PC, you can do this manually (and quickly):
    # fdisk /dev/mmcblk0 (commands I entered and comments in bold below)

    Command (m for help): p

    Disk /dev/mmcblk0: 7822 MB, 7822376960 bytes
    4 heads, 16 sectors/track, 238720 cylinders, total 15278080 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000

            Device Boot      Start         End      Blocks   Id  System
    /dev/mmcblk0p1   *          63     1044224      522081    c  W9...
    /dev/mmcblk0p2         1044225     7784447     3370111+  83  Linux

    Command (m for help): d
    Partition number (1-4): 2

    Command (m for help): n
    Partition type:
       p   primary (1 primary, 0 extended, 3 free)
       e   extended
    Select (default p): p
    Partition number (1-4, default 2): 2
    The first sector must be the start sector of /dev/mmcblk0p2 (above).  This number may be different on your SD card.  It should be the default value here - but check it carefully anyway.

    First sector (1044225-15278079, default 1044225): 1044225
    The last sector should be the default if you want to use all available space on the SD card.  If the default is what you want just press return.

    Last sector, +sectors or +size{K,M,G} (1044225-15278079, default 15278079):

    Using default value 15278079

    Command (m for help): w

    The partition table has been altered!

    Calling ioctl() to re-read partition table.

    Syncing disks.
    # e2fsck -f /dev/mmcblk0p2
    # resize2fs /dev/mmcblk0p2
    # mkdir /tmp/rootfs_pi
    # mount /dev/mmcblk0p2 /tmp/rootfs_pi
    # rm -f /tmp/rootfs_pi/etc/systemd/system/multi-user.target.wants/rootfs-resize.service
    # umount /tmp/rootfs_pi
    # rmdir /tmp/rootfs_pi
  4. Now eject the SD card from your reader, put it in your Raspberry Pi and power up.  Once it has booted log in as "root" using the password "fedoraarm".  (Assuming that you are connected over a wired LAN with a DHCP server) the Raspberry Pi will automatically obtain an IP address and LAN settings (I am going to assume this is the case - if not the process for configuring networking is exactly the same as it is on any other Fedora 17 machine).
  5. Update your packages:
    # yum update

    Don't worry about the fact that a new kernel is installed - even though this new kernel is not Raspberry Pi compatible.  When a new kernel is installed using "yum update" the old one (and it's modules) are not removed.  Also, because of the way the UBOOT partition in the images works, installing a new kernel does not change the default kernel used when you boot.
Job done.  You now have a perfectly usable and up-to-date Fedora 17 Raspberry Pi SD card.