From Fedora Project Wiki

Fedora ARM VFAD - Final push to F17

  • When: Friday June 15th at 12PM EDT
  • Where: #fedora-arm on Freednode

Please join on Friday June 15th as we test all available images to be used in the Fedora 17 ARM RC1. All can participate - even if you lack hardware you can greatly assist us by testing the functionality of our QEMU images, as well as in updating our wiki where appropriate. Our aim is to remove outdated material, and add areas that include answers to frequently asked questions, installation and usage instructions for specific hardware and anything else that may help Fedora ARM users.


Please add your name, followed by your IRC nick:

  • Paul Whalen - pwhalen
  • Jon Masters - jonmasters
  • D. Marlin - dmarlin
  • Andrew Greene - agreene
  • M A - maxam
  • Luke Macken - lmacken
  • Brendan Conoboy - bconoboy

Test Instructions

Please add your name to the wiki beside the hardware you will be testing as well as the media you will be using (eg SATA, SD). See this link for examples on how to report test results. Then copy the wiki source of the below tests and results chart to a page you will create, using the hardware you are testing as the end of the url. For example if you are testing a Pandaboard with SD card, use a link similar to "Architectures/ARM/Quality Assurance/2012-06-15-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart., and an assessment if the image is ready.

Overall Test Results and Board Assignment

Hardware Who's Testing Result Link to Results Page Final Notes
Versatile Express (Qemu) pwhalen - N/A
Fail fail pwhalen
Kernel oops on boot. Add 'physmap.enabled=0' fixes.
Versatile Express+XFCE (Qemu) jonmasters - N/A
Fail fail jcm
Kernel oops on boot. Add 'physmap.enabled=0' fixes.
Pandaboard pwhalen - SD
Pass pass pwhalen
Pandaboard SD results No release notes included.
Pandaboard+XFCE pwhalen - SD Pandaboard+XFCE-SD boots to multi-user rather then graphical, various GUI issues including inability to update, shutdown, reboot or mount devices on demand. No sound. No release notes.
Trimslice Bare/Value Pro/H/H250 dmarlin - SD
Pass pass dmarlin
Trim Slice SD results No release notes included.
Trimslice Pro/H/H250 bconoboy - HD, satellit_-SD, maxam - HFP SD and HD
Pass pass maxam
Pass pass satellit_
TS Pro HFP SD and HD results TS Pro HFP TrimSlice-h250-SD results YUM Update works but it has minor issues (Please see results page) and no release notes
Highbank bconoboy/dmarlin
Pass pass dmarlin
Highbank SATA results No release notes included.
Beagleboard XM jonmasters - SD , maxam - SFP SD
Pass pass jcm
BBXM SFP SD results (Please see the results page)
Kirkwood (sheevaplug, dreamplug, guruplug, etc) agreene - SD
Pass pass agreene
Kirkwood SD results No release notes included.
Raspberry Pi+XFCE lmacken - SD
Fail fail lmacken
RaspberryPi + XFCE SD results No RC available. Current nightly doesn't have X installed. Waiting for next image to test again...
Raspberry Pi lmacken - SD
Pass pass lmacken
RaspberryPi SD results Audio support isn't enabled, and there are no release notes included
Efika SmartTop iMX maxam - HFP SD iMX HFP SD results Some sort of DMA issue, no release notes and hangs during reboot

Testing Template

  1. Copy the below tests and results chart to a page that you create .
  2. Does your downloaded image have the correct checksum?
    • Run the command: sha256sum --check *CHECKSUM
  3. Check the image size:
    • xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB?
  4. Copy the image to your SD card:
    • xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot?
  5. Do all default services start properly?
    • Watch for service-start failure messages during boot.
  6. Check the boot result:
    • If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI?
    • If no graphical hardware is present, does the system successfully boot to a login prompt? (Note: depending on the image, the login prompt may appear on a connected monitor or on a serial console)
  7. Are you able to download and install updates with yum, and if available the default graphical package manager?
    • Test this using the command: yum install sl and yum update - then use the graphical package manager for your desktop (if applicable) to install zsh
  8. Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.
    • Test using the command: tail -f /var/log/message
  9. Are you able to shutdown the system using standard console commands?
    • Test poweroff or halt or reboot or shutdown -h now
  10. If audio device support is present, does it work?
    • Test with: play /usr/share/sounds/alsa/*wav
  11. Are the final branded release notes from the Documentation team present on the installed media?
    • Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry.
  12. Graphical user interfaces only: Is it possible to run Firefox and a terminal application? Use the browser to download a small file -, load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>), and log into FAS.
  13. Graphical user interfaces only is the default Fedora artwork used? (Default wallpaper -
  14. Graphical user interfaces only: Are the desktop's panels working and fully functional?
  15. Graphical user interfaces only: Is media automatically detected when inserted? To test - plug in a USB device or other removable media. Does the system automatically mount the device?
  16. Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? Use the GUI to logout, reboot and shutdown the system.
  17. Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? I.e., does every button do what it is supposed to do? Do GUI actions align correctly with the pointer positioin?
  18. Graphical user interfaces only: Menu sanity:
    • All Applications listed in the system menus (or equivalent) must have icons which have a consistent appearance and sufficiently high resolution to avoid appearing blurry
    • Do all applications listed under the Applications menu or category start successfully?
    • Do all applications listed under the Applications menu or category must withstand a basic functionality test and not crash after a few minutes of normal use. They must also have working Help and Help -> About menu items
    • Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications
  19. Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?
    • Create an ssh key: ssh-keygen # Use a passphrase
    • Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted
    • Connect to the remote system: ssh YourUserId@RemoteSystem # You should be prompted for the passphrase. Select the checkbox marked "Unlock this key when I log in" (or similar wording)
    • Log out.
    • Log back in to the system.
    • Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.


Test Result Notes