From Fedora Project Wiki
 
(111 intermediate revisions by 9 users not shown)
Line 1: Line 1:
=Fedora ARM VFAD - Fedora 17 Test Day=
=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.
==Participants==
==Participants==
=Tests to be performed=
Please add your name, followed by your IRC nick:
==Alpha Release Requirements==
* Paul Whalen - pwhalen
* Jon Masters - jonmasters
* D. Marlin - dmarlin
* Andrew Greene - agreene
* M A - maxam
* Luke Macken - lmacken
* Brendan Conoboy - bconoboy


# A correct checksum must be published for each official release image.
===Test Instructions===
# There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies in the released rootfs images
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 [[Template:Result | 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.
# Starting with the F18-ARM release: In most cases a system installed according to any of the above criteria (or the appropriate Beta or Final  criteria, when applying this criterion to those releases) must  boot to  the 'firstboot'  utility on the first boot after installation (possibly after automated resizing or other  steps, possibly also including a reboot), without  unintended user intervention, unless the user explicitly chooses to boot  in non-graphical mode the system is booted without an interactive user interface (e.g., headless). This includes correctly accessing any encrypted  partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account, set  the root password, and set the timezone and current time.
# Following on from the previous criterion, after firstboot is  completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria,  when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention, if graphic hardware and user interface devices  (pointer, keyboard) are available. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied
# When booting a system installed without a graphical  environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should boot to a state where it is possible to log in through at least one of the  default virtual consoles
# It must be possible to run the default web browser and a  terminal application from all release-blocking desktop environments. The web browser must be able to download files, load extensions, and log into FAS
# The installed system must be able to download and install  updates with yum and the default graphical package manager in all release-blocking desktops
# The default Fedora artwork must either refer to the current  Fedora release under development (Fedora 17), or reference an interim release milestone (e.g. Alpha or Beta). If a release version number  is  used, it must match the current Fedora release under development. This includes artwork used in the installer, graphical bootloader menu,  firstboot, graphical boot, graphical login and desktop background. 
# A system logging infrastructure must be available and enabled  by default. It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages. This  must be done in accordance with relevant standards accepted by the Project.
# It must be possible to trigger a system shutdown using  standard console commands, and the system must shut down in such a way that storage volumes (e.g. simple partitions, LVs and PVs, RAID arrays) are taken offline safely.


===Alpha Test Results===
==Overall Test Results and Board Assignment==
{|class="wikimedia" style="t1" rowclass="th" width="100%"
{|class="wikimedia" style="t1" rowclass="th" width="100%"
! Hardware !! Who's Testing !! Alpha 1 !! Alpha 2 !! Alpha 3 !! Alpha 4 !! Alpha 5 !! Alpha 6 !! Alpha 7 !! Alpha 8 !! Alpha 9 !! Alpha 10
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes
|-
|-
|| Versatile Express (Qemu) || ||{{result|pass|pwhalen}} || || || || || || || || ||
|| Versatile Express (Qemu) ||pwhalen - N/A ||{{result|fail|pwhalen}} || || Kernel oops on boot. Add 'physmap.enabled=0' fixes.
|-
|-
|| Versatile Express+XFCE (Qemu)  || || || || || || || || || || ||
|| Versatile Express+XFCE (Qemu)  ||jonmasters - N/A ||{{result|fail|jcm}} || ||Kernel oops on boot. Add 'physmap.enabled=0' fixes.
|-
|-
|| Pandaboard || || || || || || || || || || ||
|| Pandaboard ||pwhalen - SD ||{{result|pass|pwhalen}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD results ]] || No release notes included.
|-
|-
|| Pandaboard+XFCE || || || || || || || || || || ||
|| Pandaboard+XFCE ||pwhalen - SD || {{result|unknown|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-Pandaboard+XFCE-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 || || || || || || || || || || ||
|| Trimslice Bare/Value Pro/H/H250 || dmarlin - SD || {{result|pass|dmarlin}} || [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-TrimsliceBare-SD | Trim Slice SD results ]] || No release notes included.
|-
|-
|| Trimslice Pro/H/H250 || || || || || || || || || || ||
|| Trimslice Pro/H/H250 || bconoboy - HD, satellit_-SD, maxam  - HFP SD and HD || {{result|pass|maxam}} {{result|pass|satellit_}}  || [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD and HD results ]][[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-TrimSlice-h250-SD | TS Pro HFP TrimSlice-h250-SD  results ]]  || YUM Update works but it has minor issues (Please see results page) and no release notes
|-
|-
|| Highbank || || || || || || || || || || ||
|| Highbank || bconoboy/dmarlin || {{result|pass|dmarlin}} || [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-Highbank-SATA | Highbank SATA results ]] || No release notes included.
|-
|-
|| Beagleboard XM || || || || || || || || || || ||
|| Beagleboard XM ||jonmasters - SD  ,  maxam  - SFP SD || {{result|unknown|maxam}}{{result|pass|jcm}}  || [[ Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-BBXM-SFP-SD | BBXM SFP SD results ]] || (Please see the results page)
|-
|-
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || || || || || || || || || || ||
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) ||agreene - SD|| {{result|pass|agreene}} || [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-Kirkwood_(sheevaplug,_dreamplug,_guruplug,_etc)_-SD | Kirkwood SD results ]] || No release notes included.
|- || || ||
|| Raspberry Pi+XFCE || lmacken - SD || {{result|fail|lmacken}} || [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-RaspberryPi+XFCE-SD | RaspberryPi + XFCE SD results ]] || No RC available. Current nightly doesn't have X installed. Waiting for next image to test again...
|-
|-
|| Raspberry Pi+XFCE || || || || || || || || || || ||
|| Raspberry Pi || lmacken - SD || {{result|pass|lmacken}}  || [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-RaspberryPi-SD | RaspberryPi SD results ]] || Audio support isn't enabled, and there are no release notes included
|-
|-
|| Raspberry Pi || || || || || || || || || || ||
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|unknown|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/dE4K/ Some sort of DMA issue], no release notes and [http://fpaste.org/K6PV/ hangs during reboot]
|}
|}


==Beta Release Requirements==
==Testing Template==
#Copy the below tests and results chart to a page that you create .
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC1/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC1/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC1/armhfp/Fedora-17-armhfp-Images-CHECKSUM
#Does your downloaded image have the correct checksum?
#*Run the command: sha256sum --check *CHECKSUM
#Check the image size:
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB?
#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?
#Do all default services start properly?
#*Watch for service-start failure messages during boot.
#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)
#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
#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
#Are you able to shutdown the system using standard console commands?
#*Test poweroff or halt or reboot or shutdown -h now
#If audio device support is present, does it work?
#*Test with: play /usr/share/sounds/alsa/*wav
#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.
#Graphical user interfaces only: Is it possible to run Firefox and a  terminal application? Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC1/arm/Fedora-17-arm-Images-CHECKSUM,  load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>), and log into FAS.
#Graphical user interfaces only is the default Fedora artwork used? (Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png)
#Graphical user interfaces only: Are the desktop's panels working and fully functional?
#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?
#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.
#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?
#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
#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.


# The images must not be over 4G in size, uncompressed.
===Results===
# When booting a system installed without a graphical  environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should provide a working login prompt without any unintended user  intervention  when boot is complete, and all virtual consoles intended to provide a  working login prompt should do so,  except for a character-mode firstboot if provided.
# In most cases, the installed system must be able to play back sound with gstreamer-based applications (see Blocker_Bug_FAQ), if supported audio output devices are present.
# No part of any release-blocking desktop's panel (or  equivalent) configuration should crash or be entirely non-functional on boot of the installed system using default installation choices.
# Automatic mounting on insertion of removable media must work in release-blocking desktops.
# The default update manager in release-blocking desktops must  periodically check for updates when  running on an installed system.
# All release-blocking desktops' offered mechanisms (if any) for shutting down, logging out and rebooting must work.
 
 
===Beta Test Results===
{|class="wikimedia" style="t1" rowclass="th" width="100%"
{|class="wikimedia" style="t1" rowclass="th" width="100%"
! Hardware !! Who's Testing !! Beta 1 !! Beta 2 !! Beta 3 !!Beta 4 !! Beta 5 !! Beta 6 !! Beta 7 !! Beta 8 !! Beta 9 !! Beta 10
! Test !! Result !! Notes
|-
|-
|| Versatile Express (Qemu) || || || || || || || || || || ||
|| 1 || ||
|-
|-
|| Versatile Express+XFCE (Qemu) || || || || || || || || || || ||
|| 2 || ||  
|-
|-
|| Pandaboard || || || || || || || || || || ||
|| 3 || ||  
|-
|-
|| Pandaboard+XFCE || || || || || || || || || || ||
|| 4 || ||
|-
|-
|| Trimslice Bare/Value Pro/H/H250 || || || || || || || || || || ||
|| 5 || ||  
|-
|-
|| Trimslice Pro/H/H250 || || || || || || || || || || ||
|| 6 || ||  
|-
|-
|| Highbank || || || || || || || || || || ||
|| 7 || ||  
|-
|| Beagleboard XM || || || || || || || || || || ||
|-
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || || || || || || || || || || ||
|-
|| Raspberry Pi+XFCE || || || || || || || || || || ||
|-
|| Raspberry Pi || || || || || || || || || || ||
|}
 
==Final Release Requirements==
 
===Final Test Results===
{|class="wikimedia" style="t1" rowclass="th" width="100%"
! Hardware !! Who's Testing !! Beta 1 !! Beta 2 !! Beta 3 !!Beta 4 !! Beta 5 !! Beta 6 !! Beta 7 !! Beta 8 !! Beta 9 !! Beta 10
|-
|-
|| Versatile Express (Qemu) || || || || || || || || || || ||
|| 8 || ||  
|-
|-
|| Versatile Express+XFCE (Qemu)  || || || || || || || || || || ||
|| 9 || ||  
|-|| || ||
|| 10 || ||  
|-
|-
|| Pandaboard || || || || || || || || || || ||
|| 11 || ||
|-
|-
|| Pandaboard+XFCE || || || || || || || || || || ||
|| 12 || ||
|-
|-
|| Trimslice Bare/Value Pro/H/H250 || || || || || || || || || || ||
|| 13 || ||
|-
|-
|| Trimslice Pro/H/H250 || || || || || || || || || || ||
|| 14 || ||
|-
|-
|| Highbank || || || || || || || || || || ||
|| 15 || ||
|-
|-
|| Beagleboard XM || || || || || || || || || || ||
|| 16 || ||
|-
|-
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || || || || || || || || || || ||
|| 17 || ||
|-
|-
|| Raspberry Pi+XFCE || || || || || || || || || || ||
|| 18 || ||
|-
|-
|| Raspberry Pi || || || || || || || || || || ||
|| 19 || ||
|}
|}
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]

Latest revision as of 13:58, 18 June 2012

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.

Participants

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 - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC1/arm/Fedora-17-arm-Images-CHECKSUM, 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 - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png)
  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.

Results

Test Result Notes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19