The Pandaboard is one of the most popular ARM devices available and provides users with either a desktop environment or minimal installation (text based).
- 1 GHz Dual core Cortex A9 Processor (OMAP 4430-4460)
- 1 GB DDR2 RAM
- HDMI v1.3
- 10/100Mbit/s Ethernet
- 802.11 b/g/n WiFi
For more information on the Pandaboard visit their website.
Running Fedora on a Pandaboard
This page will give you detailed instructions for running Fedora 17 GA on your Pandaboard. There are two images to choose from on the Pandaboard - with the XFCE desktop, the other providing a serial console (text based).
Download the image
The first step is to download the Fedora 17 image. The prebuilt images include kernels and can be written directly to an SD Card and booted without any additional steps or configuration. The serial console image requires a minimum of 2GB and the XFCE desktop requires a minimum of 4 GB.
Writing the Image
You can write the image to an SD card of your choosing but it does have to meet the minimum size requirements noted above (2GB for the serial image, 4GB for the XFCE Desktop). Connect the SD card to your computer and make note of the drive. To write the image to your SD card run the following command, changing the drive to the location of your SD card.
For the Serial Image:
xzcat Fedora-17-armhfp-panda-mmcblk0.img.xz > /dev/<location-of-your-SD-card>
For the XFCE Desktop:
xzcat Fedora-17-armhfp-panda-xfce-mmcblk0.img.xz > /dev/<location-of-your-SD-card>
Once completed run the below command to ensure the entire image is written to the card:
- You will need to download Win32 Image Writer as well as a tool to extract the image such as 7-Zip.
- Once downloaded and installed right click on the disk image and select "7-Zip->Extract files here"
- Launch Win 32 Disk Imager and select the extracted disk image and the SD card you would like to write the files to. Click "Write". Be very careful during this step - all data on the selected drive will be lost!
- Please note that the Default Archive Utility.app will not extract the .xz file. A third party app will have to be used to decompress it. There are multiple options for that
- Once the xz utility is installed, open a terminal and make a note of the current drives.
- Connect the SD card to the mac and make a note of the drive.
- Open Disk Utility and make sure that the card and all the partitions in the card (if any) is unmounted
- In the terminal change to the directory where the .xz file is located
- If xz was installed from the .pkg or macport or homebrew then run the following command
xzcat Fedora-17-armhfp-panda-xfce-mmcblk0.img.xz > /dev/<location-of-the-SD-card>
- If the Unarchiver app from App Store was used then just click and decompress the .xz file and then run the following (may require sudo)
dd if=Fedora-17-armhfp-panda-xfce-mmcblk0.img of=/dev/<location-of-the-SD-card>
- Click and eject the SD card
Using Fedora on the Pandaboard
Connect the newly created media to your Pandaboard and power on. No further steps are required and your system should boot to a text based log in prompt (serial image) or to a graphical log in (XFCE Desktop image). The default root password is "fedoraarm". This should be changed immediately.
- Yum requires the system time be correct for HTTPS to function. If yum updates are not working check your clock.
- The tar.xz rootfs archives do not preserve SELinux information or file capabilities. If you use these to create your own filesystem image it is recommended that you switch SELinux to use warnings instead of enforcing for first boot, then relabel and reinstall packages that rely upon filesystem capabilities such as glibc-common and ping.
- Images are designed to be written to 2GB (console) or 4GB (xfce) SD cards. On first boot the partition will be resized to the maximum allowable amount. On the second boot the filesystem will be resized to fill the expanded partition. This works for SD cards, SATA Disks, and SSD drives.
- The XFCE Desktop image uses the HDMI port for display, which will work as a dvi-d also.
- The powerVR gpu is currently not available in the omapdrm driver used in Fedora kernel-omap.
- Each time the panda boots a new random MAC address is generated. This is because there is no EEPROM to store the mac address. To have the same eth0 MAC address after reboot the /etc/sysconfig/network-scripts/ifcfg-eth0 file needs to have MACADDR= line added.
- Known release issues
There are Fedora ARM users all around the globe - if you need assistance, would like to provide feedback or contribute to Fedora ARM please visit us on the IRC - we can be found in armon Freenode. You can also contact us on the mailing list -
The image file can be loop mounted.
- Inflate the archive:
- Print the partition table:
fdisk -l Fedora-17-armhfp-panda-xfce-mmcblk0.img Disk Fedora-17-armhfp-panda-xfce-mmcblk0.img: 3775 MB, 3775922176 bytes 255 heads, 63 sectors/track, 459 cylinders, total 7374848 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 Fedora-17-armhfp-panda-xfce-mmcblk0.img1 * 63 1044224 522081 c W95 FAT32 (LBA) Fedora-17-armhfp-panda-xfce-mmcblk0.img2 1044225 7374847 3165311+ 83 Linux
- The /boot partition starts at sector 63, where each sectore is 512 bytes.
mount -o loop,offset=$(( 63 * 512 )) Fedora-17-armhfp-panda-xfce-mmcblk0.img /mnt/boot
- The rootfs partition starts are sector 1,044,225
mount -o loop,offset=$(( 1044255 * 512 )) Fedora-17-armhfp-panda-xfce-mmcblk0.img /mnt/rootfs
At this point you may customize the image however you wish.