Architectures/ARM/Quality Assurance/2012-12-20-VFAD-Fedora 18 Beta-Pandaboard

From FedoraProject

< Architectures | ARM | Quality Assurance(Difference between revisions)
Jump to: navigation, search
m
(Results)
Line 49: Line 49:
 
[  15.211395] omap-hdmi-audio omap-hdmi-audio:  omap-hdmi-hifi <-> omap-hdmi-audio-dai mapping ok</pre></ref>
 
[  15.211395] omap-hdmi-audio omap-hdmi-audio:  omap-hdmi-hifi <-> omap-hdmi-audio-dai mapping ok</pre></ref>
 
|-
 
|-
|| 11 || {{result|pass}} ||
+
|| 11 || {{result|pass}} || <code>Applications -&gt; Documentation -&gt; Release Notes<code> opens in Geany, an HTML editor, instead of Midori.
 
|-
 
|-
|| 12 || ||
+
|| 12 || {{result|pass}} ||
 
|-
 
|-
|| 13 || ||
+
|| 13 || {{result|pass}} ||
 
|-
 
|-
|| 14 || ||
+
|| 14 || {{result|pass}} ||
 
|-
 
|-
|| 15 || ||
+
|| 15 || {{result|pass}} ||
 
|-
 
|-
|| 16 || ||
+
|| 16 || {{result|pass}} ||
 
|-
 
|-
 
|| 17 || ||
 
|| 17 || ||

Revision as of 23:37, 20 December 2012

Jeff Bastian's Pandaboard serial console test results for Fedora ARM VFAD - Fedora 18 - Beta TC3
NOTE: Tests 1-11 were done with the serial console. Tests 12-19 were on a graphical console (HDMI-to-DVI-D cable).

Results

Test Result Notes
1
Pass pass
2
Pass pass
3
Pass pass
4
Pass pass
The first boot showed a systemd error[1] and immediately shut down and rebooted, but the second boot stayed up.
5
Pass pass
6
Pass pass
7
Pass pass
8
Pass pass
9
Pass pass
10
Fail fail
Pragha reported an error with "Reason: Configured audiosink audiobin is not working." And there were error messages on the console during boot related to the sound drivers.[2]
11
Pass pass
Applications -> Documentation -> Release Notes<code> opens in Geany, an HTML editor, instead of Midori.
12
Pass pass
13
Pass pass
14
Pass pass
15
Pass pass
16
Pass pass
17
18
19
  1. first boot error:
    Fedora release 18 (Spherical Cow)
    Kernel 3.6.10-6.fc18.armv7hl.omap on an armv7l (ttyO2)
    
    panda-f18-v7hl login: [   60.562164] systemd[1]: bus_connection_get_unix_fd failed Broken pipe
    [   60.571319] systemd[1]: Failed to get caller's security context on: Broken pipe
    [  OK  ] Stopped Security Auditing Service.
    [  OK  ] Started Show Plymouth Reboot Screen.
    [  OK  ] Stopped target Basic System.
    ...
    
  2. sound driver messages:
    [   14.644195] omap-abe-twl6040 omap-abe-twl6040: platform omap-pcm-audio not registered
    [   14.657562] omap-abe-twl6040 omap-abe-twl6040: snd_soc_register_card() failed: -517
    [   14.674468] platform omap-abe-twl6040: Driver omap-abe-twl6040 requests probe deferral
    [   14.953735] omap-hdmi-audio omap-hdmi-audio: CPU DAI omap-hdmi-audio-dai not registered
    [   14.963256] omap-hdmi-audio omap-hdmi-audio: snd_soc_register_card failed (-517)
    [   14.972717] platform omap-hdmi-audio: Driver omap-hdmi-audio requests probe deferral
    [   14.973968] omap-abe-twl6040 omap-abe-twl6040: platform omap-pcm-audio not registered
    [   14.983062] omap-abe-twl6040 omap-abe-twl6040: snd_soc_register_card() failed: -517
    [   14.991363] platform omap-abe-twl6040: Driver omap-abe-twl6040 requests probe deferral
    [   14.991485] omap-hdmi-audio omap-hdmi-audio: CPU DAI omap-hdmi-audio-dai not registered
    [   15.000091] omap-hdmi-audio omap-hdmi-audio: snd_soc_register_card failed (-517)
    [   15.008819] platform omap-hdmi-audio: Driver omap-hdmi-audio requests probe deferral
    [   15.195861] omap-abe-twl6040 omap-abe-twl6040: snd_soc_register_card() failed: -110
    [   15.209930] omap-abe-twl6040: probe of omap-abe-twl6040 failed with error -110
    [   15.211395] omap-hdmi-audio omap-hdmi-audio:  omap-hdmi-hifi <-> omap-hdmi-audio-dai mapping ok

Tests

  1. Does your downloaded image have the correct checksum?
    • Run the command: sha256sum --check SHA256SUMS
  2. Check the image size:
    • xzcat NameOfImage.xz|wc -c - Is the uncompressed image no larger than 4GB?
  3. 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?
  4. Do all default services start properly?
    • Watch for service-start failure messages during boot.
  5. 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)
  6. 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 (you may want to limit this to one package as updates can take a while depending on your media. eg - yum update bash)
    • Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh
  7. 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/messages
  8. Are you able to shutdown the system using standard console commands?
    • Test poweroff or halt or reboot or shutdown -h now
  9. If audio device support is present, does it work?
    • Test with: play /usr/share/sounds/alsa/*wav
  10. 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.
  11. Graphical user interfaces only: Is it possible to run Midori and a terminal application?
  12. Graphical user interfaces only is the default Fedora artwork used (currently not decided)?
  13. Graphical user interfaces only: Are the desktop's panels working and fully functional?
  14. Graphical user interfaces only: Is media automatically detected when inserted?
    • Plug in a USB device or other removable media. Does the system automatically mount the device?
  15. 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.
  16. Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use?
    • Does every button do what it is supposed to do?
    • Do GUI actions align correctly with the pointer position?
  17. 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
  18. 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.