https://fedoraproject.org/w/api.php?action=feedcontributions&user=Maxamaxim&feedformat=atomFedora Project Wiki - User contributions [en]2024-03-29T11:52:50ZUser contributionsMediaWiki 1.39.4https://fedoraproject.org/w/index.php?title=Architectures/ARM&diff=293079Architectures/ARM2012-06-20T18:41:01Z<p>Maxamaxim: Added link to the Kirkwood page</p>
<hr />
<div>{{shortcut|Arch:ARM}}<br />
{{lang|en|zh-cn|page=Architectures/ARM}}<br />
<br />
{| style="width: 50%; float: right; margin-left: 2em;"<br />
|-<br />
| style="border-width: 0;" | {{admon/tip | Here are some links to help you get started with Fedora ARM, fast:|<br />
<br />
[https://fedoraproject.org/wiki/Architectures/ARM/Fedora_17_GA Download] Fedora ARM now!<br />
<br />
Includes support for Beagleboard, [[Architectures/ARM/Kirkwood|Dreamplug, Guruplug]], Highbank, [[Architectures/ARM/EFIKA_MX_Smarttop|iMX]], [[Architectures/ARM/Pandaboard|Pandaboard]], Sheevaplug, [[Architectures/ARM/Trimslice|Trimslice]], Versatile Express and more!<br />
<br />
Have a question? Join the Fedora ARM team on IRC in [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode]<br />
}}<br />
|}<br />
<br />
= Introduction =<br />
<br />
ARM chips are the most widely-produced processor family in the world; they have historically been used in cell phones and embedded applications, and are increasingly used in tablet devices and low-power-consumption servers.<br />
<br />
The Fedora-ARM project is an initiative to bring Fedora to this processor family.<br />
<br />
= Communication =<br />
* Mailing list: [https://lists.fedoraproject.org/mailman/listinfo/arm arm@lists.fedoraproject.org] ([http://lists.fedoraproject.org/pipermail/arm/ archives])<br />
* IRC: [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode]<br />
<br />
= Meetings =<br />
* IRC: [irc://irc.freenode.net/fedora-meeting-1 #fedora-meeting-1] each Wednesday at 20:00 UTC (4PM EDT) on [http://freenode.net Freenode] ([https://fedoraproject.org/wiki/Architectures/ARM/Meetings/Archive/ archives])<br />
<br />
* [[Architectures/ARM/Meetings/FUDCon Blacksburg 2012]]<br />
<br />
= Planning =<br />
* [[Architectures/ARM/Planning/Primary|Draft Proposal for Primary Architecture Push]]<br />
<br />
= Resources =<br />
Detailed information on Fedora-ARM:<br />
* [[Architectures/ARM/Using|Running Fedora-ARM on your ARM device, or through emulation on your PC]]<br />
* [http://arm.koji.fedoraproject.org/koji/ Fedora ARM Koji (package builder) instance]<br />
* [[Architectures/ARM/Package Maintainers|Information for Fedora package maintainers on getting your packages to work on ARM]]<br />
* [[Architectures/ARM/Team and Developers|Information for Fedora-ARM team members (and prospective team members!) plus developers]]<br />
* [[Architectures/ARM/CrossToolchain|How to get an armv5tel cross toolchain installed on your x86 Fedora host]]<br />
* [[Architectures/ARM/Building a Kernel for ARM|How to build a kernel and cross-compile for ARM]]<br />
* [[Architectures/Fedora_ARM_Kernels|Building and Installing a Fedora Kernel Package on ARM Systems]]<br />
* [[Architectures/Fedora_ARM_Kernel_Updates|Updating a Fedora Kernel on ARM Systems]]<br />
* [[Architectures/ARM/Performance|Various tips and hacks to improve Fedora ARM performance]]<br />
<br />
= Releases =<br />
* Fedora 17 - Includes kernels for Tegra 2, OMAP, IMX, Kirkwood, Highbank and Qemu systems.<br />
** [http://scotland.proximity.on.ca/arm-nightlies/ Current Snapshots ] including xzcat-able images. Updated nightly.<br />
** [[Architectures/ARM/Fedora_17_GA|Fedora 17 GA]] (includes Versatile Express (QEMU), Trimslice, Beagleboard xM, Pandaboard, Kirkwood Plugs, Highbank and iMX based hardware platforms)<br />
** [[Architectures/ARM/Fedora_17_Beta|Fedora 17 Beta release]] (includes images for Trimslice, Beagleboard XM, iMX and QEMU)<br />
** [http://fedora.roving-it.com/rootfs-f17-hfp-alpha1.tar.bz2 Fedora 17 Alpha 1 release for ARMv7hl] (Optimized for Beagle, Panda, Trimslice, Efika and other ARMv7 devices)<br />
** [http://fedora.roving-it.com/rootfs-f17-sfp-alpha1.tar.bz2 Fedora 17 Alpha 1 release for ARMv5tel] (For use with legacy ARMv5 devices such as the Raspberry Pi, Guruplug and Dreamplug)<br />
* Fedora 16 - Was not released.<br />
* Fedora 15 - Original armv5tel ABI and new faster armv7hl ABI<br />
** [http://fedora.roving-it.com/rootfs-f15-hfp-alpha1.tar.bz2 Fedora 15 Alpha 1 release for ARMv7hl] <br />
** [http://fedora.roving-it.com/rootfs-f15-sfp-alpha1.tar.bz2 Fedora 15 Alpha 1 release for ARMv5tel]<br />
* Fedora 14 - For ARMv5tel<br />
** [http://fedora.roving-it.com/rootfs-f14-minimal-RC1.tar.bz2 Fedora 14 Minimal release for ARM (Final)]<br />
** [http://fedora.roving-it.com/rootfs-f14-xfce-RC1.tar.bz2 Fedora 14 XFCE release for ARM (Final)]<br />
** [http://lists.fedoraproject.org/pipermail/arm/2011-July/001628.html Fedora 14 alpha 1 release for ARM] (obsolete)<br />
* Fedora 13 - For ARMv5tel<br />
** [http://scotland.proximity.on.ca/fedora-arm/rootfs/rootfs-f13-rc1-2011-06-29.tar.bz2 Fedora 13 release for ARM]<br />
* Fedora 12 - For ARMv5tel<br />
** [[Architectures/ARM/Release/12|Fedora 12 release for ARM ]]<br />
<br />
== Development ==<br />
* F17 (Work in progress)<br />
** [[Architectures/ARM/Fedora17_rawhide|Issues with Fedora 17 Rawhide mass rebuild]]<br />
** [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day | Fedora 17 RC1 VFAD Results]]<br />
** [[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day | Fedora 17 RC2 VFAD Results]]<br />
* Fedora 15: Complete, but notes below for reference.<br />
** [[Architectures/ARM/Fedora15 HardFP Bootstrap|Fedora 15 Hardware Floating Point Bootstrap]]<br />
** [[/F15_Koji_build|Building F15 in koji]] - progress and outstanding tasks<br />
<br />
<br />
<!--<br />
<br />
----<br />
<br />
'''OLD PAGE CONTENTS HERE'''<br />
-- page was renamed from ARM --<br />
<br />
= Fedora ARM =<br />
<br />
This is the starting page for the Fedora port to the ARM architecture.<br />
<br />
<br />
<br />
== Goals and Objectives ==<br />
<br />
The primary goal of this project is to provide support for ARM as a [[TomCallaway/SecondaryArchitectures| secondary architecture]] in Fedora.<br />
<br />
A secondary goal is to enable derivative distributions based on the Fedora package collection and repository that are more suitably optimized for embedded and mobile use-cases.<br />
<br />
== Technical Approach ==<br />
<br />
=== Native Compilation ===<br />
<br />
Fedora policy requires that packages be natively compiled. We use a cluster of ARM hardware and QEMU virtual machines to build the packages natively for ARM.<br />
<br />
=== CPU and Architecture Target ===<br />
<br />
The baseline ARM CPU architecture that we have chosen to support is ARMv5TE, Little Endian, Soft-Float, EABI. We believe that this provides a nice baseline and that the pre-built packages and root file system images. You should be able to use this on many of the modern ARM CPUs, including XScale, ARM926 and ARM-11, etc.<br />
<br />
Although we do not provide such binaries, the sources also lend themselves for building for pre-ARMv5TE hardware. The same is true for big-endian CPUs.<br />
<br />
=== Installer and Kernel ===<br />
<br />
We currently do not plan to provide an installer, ISO images, or a kernel. Unlike in the x86 world, different ARM CPU families require different kernel images. Likewise, it is not entirely clear whether it makes sense to provide an installer or ISO images.<br />
<br />
== Contribute ==<br />
* This is a tracking page for packages requiring patching to build on ARM: [[Architectures/ARM/Packages_needing_patching]]<br />
!-- * A list of builds that are failing on ARM architecture is maintained [http://arm.koji.fedoraproject.org/packages_to_be_fixed.html here]. It is a good starting point for anyone willing to contribute to the Fedora-ARM project. The list is updated daily. --<br />
* We have a [[Architectures/ARM/TODO|TODO list]].<br />
* Have a look at the [[Architectures/ARM/Credits| Credits page]]<br />
* Fedora ARM is currently heavily driven by the Seneca Centre for Development of Open Technology (CDOT) at the School of Computer Studies at Seneca College, Toronto. More information about their status can be found in the [http://zenit.senecac.on.ca/wiki/index.php/Fedora_ARM_Secondary_Architecture CDOT ARM wiki]<br />
<br />
=== How to get in touch? ===<br />
* The [https://admin.fedoraproject.org/mailman/listinfo/arm Fedora-ARM mailing list] is available for both user and developer discussions.<br />
* We also have an IRC channel #fedora-arm on Freenode.<br />
* Frequent updates about the effort are available at [http://paulfedora.wordpress.com Paul Whalen's ARM blog]<br />
* Some old postings from November 2009 and earlier are available at the [http://fedora-arm.blogspot.com Fedora-ARM blog]<br />
<br />
=== Tracker Bugs ===<br />
If excluding ARM architectures you need to make the bug block '''F-ExcludeArch-ARM''' <br />
<br />
to see whats currently blocking visit [https://bugzilla.redhat.com/show_bug.cgi?id=F-ExcludeArch-ARM Bugzilla ]<br />
<br />
If a bug is specific to ARM architectures make the bug blocking '''ARMTracker'''<br />
<br />
to see not yet resolved issues visit [https://bugzilla.redhat.com/show_bug.cgi?id=ARMTracker Bugzilla ]<br />
=== Package Maintainer Notes ===<br />
As part of setting up to be a package maintainer, you should have run fedora-packager-setup from the fedora-packager rpm. That will write secondary arch config files in ~/.koji. To kick off a build for a package you maintain, run:<br />
<pre><br />
make SECONDARY_CONFIG="-c ~/.koji/arm-config" build<br />
</pre><br />
<br />
To kick off a koji scratch build, run:<br />
<pre><br />
koji -c ~/.koji/arm-config build --scratch dist-f13 /path/to/srpm<br />
</pre><br />
You can change the dist tag to the dist you want to target.<br />
<br />
There is also a separate [http://arm.koji.fedoraproject.org/koji/ Fedora ARM Koji Webinterface].<br />
--><br />
[[Category:Arch-specific SIGs]][[Category:SIGs]]<br />
[[Category:Fedora special-interest groups|ARM]]<br />
[[Category:Fedora ARM]]<br />
[[Category:Fedora ARM Hardware]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM&diff=293077Architectures/ARM2012-06-20T18:39:07Z<p>Maxamaxim: Added Catagory</p>
<hr />
<div>{{shortcut|Arch:ARM}}<br />
{{lang|en|zh-cn|page=Architectures/ARM}}<br />
<br />
{| style="width: 50%; float: right; margin-left: 2em;"<br />
|-<br />
| style="border-width: 0;" | {{admon/tip | Here are some links to help you get started with Fedora ARM, fast:|<br />
<br />
[https://fedoraproject.org/wiki/Architectures/ARM/Fedora_17_GA Download] Fedora ARM now!<br />
<br />
Includes support for Beagleboard, Dreamplug, Guruplug, Highbank, [[Architectures/ARM/EFIKA_MX_Smarttop|iMX]], [[Architectures/ARM/Pandaboard|Pandaboard]], Sheevaplug, [[Architectures/ARM/Trimslice|Trimslice]], Versatile Express and more!<br />
<br />
Have a question? Join the Fedora ARM team on IRC in [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode]<br />
}}<br />
|}<br />
<br />
= Introduction =<br />
<br />
ARM chips are the most widely-produced processor family in the world; they have historically been used in cell phones and embedded applications, and are increasingly used in tablet devices and low-power-consumption servers.<br />
<br />
The Fedora-ARM project is an initiative to bring Fedora to this processor family.<br />
<br />
= Communication =<br />
* Mailing list: [https://lists.fedoraproject.org/mailman/listinfo/arm arm@lists.fedoraproject.org] ([http://lists.fedoraproject.org/pipermail/arm/ archives])<br />
* IRC: [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode]<br />
<br />
= Meetings =<br />
* IRC: [irc://irc.freenode.net/fedora-meeting-1 #fedora-meeting-1] each Wednesday at 20:00 UTC (4PM EDT) on [http://freenode.net Freenode] ([https://fedoraproject.org/wiki/Architectures/ARM/Meetings/Archive/ archives])<br />
<br />
* [[Architectures/ARM/Meetings/FUDCon Blacksburg 2012]]<br />
<br />
= Planning =<br />
* [[Architectures/ARM/Planning/Primary|Draft Proposal for Primary Architecture Push]]<br />
<br />
= Resources =<br />
Detailed information on Fedora-ARM:<br />
* [[Architectures/ARM/Using|Running Fedora-ARM on your ARM device, or through emulation on your PC]]<br />
* [http://arm.koji.fedoraproject.org/koji/ Fedora ARM Koji (package builder) instance]<br />
* [[Architectures/ARM/Package Maintainers|Information for Fedora package maintainers on getting your packages to work on ARM]]<br />
* [[Architectures/ARM/Team and Developers|Information for Fedora-ARM team members (and prospective team members!) plus developers]]<br />
* [[Architectures/ARM/CrossToolchain|How to get an armv5tel cross toolchain installed on your x86 Fedora host]]<br />
* [[Architectures/ARM/Building a Kernel for ARM|How to build a kernel and cross-compile for ARM]]<br />
* [[Architectures/Fedora_ARM_Kernels|Building and Installing a Fedora Kernel Package on ARM Systems]]<br />
* [[Architectures/Fedora_ARM_Kernel_Updates|Updating a Fedora Kernel on ARM Systems]]<br />
* [[Architectures/ARM/Performance|Various tips and hacks to improve Fedora ARM performance]]<br />
<br />
= Releases =<br />
* Fedora 17 - Includes kernels for Tegra 2, OMAP, IMX, Kirkwood, Highbank and Qemu systems.<br />
** [http://scotland.proximity.on.ca/arm-nightlies/ Current Snapshots ] including xzcat-able images. Updated nightly.<br />
** [[Architectures/ARM/Fedora_17_GA|Fedora 17 GA]] (includes Versatile Express (QEMU), Trimslice, Beagleboard xM, Pandaboard, Kirkwood Plugs, Highbank and iMX based hardware platforms)<br />
** [[Architectures/ARM/Fedora_17_Beta|Fedora 17 Beta release]] (includes images for Trimslice, Beagleboard XM, iMX and QEMU)<br />
** [http://fedora.roving-it.com/rootfs-f17-hfp-alpha1.tar.bz2 Fedora 17 Alpha 1 release for ARMv7hl] (Optimized for Beagle, Panda, Trimslice, Efika and other ARMv7 devices)<br />
** [http://fedora.roving-it.com/rootfs-f17-sfp-alpha1.tar.bz2 Fedora 17 Alpha 1 release for ARMv5tel] (For use with legacy ARMv5 devices such as the Raspberry Pi, Guruplug and Dreamplug)<br />
* Fedora 16 - Was not released.<br />
* Fedora 15 - Original armv5tel ABI and new faster armv7hl ABI<br />
** [http://fedora.roving-it.com/rootfs-f15-hfp-alpha1.tar.bz2 Fedora 15 Alpha 1 release for ARMv7hl] <br />
** [http://fedora.roving-it.com/rootfs-f15-sfp-alpha1.tar.bz2 Fedora 15 Alpha 1 release for ARMv5tel]<br />
* Fedora 14 - For ARMv5tel<br />
** [http://fedora.roving-it.com/rootfs-f14-minimal-RC1.tar.bz2 Fedora 14 Minimal release for ARM (Final)]<br />
** [http://fedora.roving-it.com/rootfs-f14-xfce-RC1.tar.bz2 Fedora 14 XFCE release for ARM (Final)]<br />
** [http://lists.fedoraproject.org/pipermail/arm/2011-July/001628.html Fedora 14 alpha 1 release for ARM] (obsolete)<br />
* Fedora 13 - For ARMv5tel<br />
** [http://scotland.proximity.on.ca/fedora-arm/rootfs/rootfs-f13-rc1-2011-06-29.tar.bz2 Fedora 13 release for ARM]<br />
* Fedora 12 - For ARMv5tel<br />
** [[Architectures/ARM/Release/12|Fedora 12 release for ARM ]]<br />
<br />
== Development ==<br />
* F17 (Work in progress)<br />
** [[Architectures/ARM/Fedora17_rawhide|Issues with Fedora 17 Rawhide mass rebuild]]<br />
** [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day | Fedora 17 RC1 VFAD Results]]<br />
** [[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day | Fedora 17 RC2 VFAD Results]]<br />
* Fedora 15: Complete, but notes below for reference.<br />
** [[Architectures/ARM/Fedora15 HardFP Bootstrap|Fedora 15 Hardware Floating Point Bootstrap]]<br />
** [[/F15_Koji_build|Building F15 in koji]] - progress and outstanding tasks<br />
<br />
<br />
<!--<br />
<br />
----<br />
<br />
'''OLD PAGE CONTENTS HERE'''<br />
-- page was renamed from ARM --<br />
<br />
= Fedora ARM =<br />
<br />
This is the starting page for the Fedora port to the ARM architecture.<br />
<br />
<br />
<br />
== Goals and Objectives ==<br />
<br />
The primary goal of this project is to provide support for ARM as a [[TomCallaway/SecondaryArchitectures| secondary architecture]] in Fedora.<br />
<br />
A secondary goal is to enable derivative distributions based on the Fedora package collection and repository that are more suitably optimized for embedded and mobile use-cases.<br />
<br />
== Technical Approach ==<br />
<br />
=== Native Compilation ===<br />
<br />
Fedora policy requires that packages be natively compiled. We use a cluster of ARM hardware and QEMU virtual machines to build the packages natively for ARM.<br />
<br />
=== CPU and Architecture Target ===<br />
<br />
The baseline ARM CPU architecture that we have chosen to support is ARMv5TE, Little Endian, Soft-Float, EABI. We believe that this provides a nice baseline and that the pre-built packages and root file system images. You should be able to use this on many of the modern ARM CPUs, including XScale, ARM926 and ARM-11, etc.<br />
<br />
Although we do not provide such binaries, the sources also lend themselves for building for pre-ARMv5TE hardware. The same is true for big-endian CPUs.<br />
<br />
=== Installer and Kernel ===<br />
<br />
We currently do not plan to provide an installer, ISO images, or a kernel. Unlike in the x86 world, different ARM CPU families require different kernel images. Likewise, it is not entirely clear whether it makes sense to provide an installer or ISO images.<br />
<br />
== Contribute ==<br />
* This is a tracking page for packages requiring patching to build on ARM: [[Architectures/ARM/Packages_needing_patching]]<br />
!-- * A list of builds that are failing on ARM architecture is maintained [http://arm.koji.fedoraproject.org/packages_to_be_fixed.html here]. It is a good starting point for anyone willing to contribute to the Fedora-ARM project. The list is updated daily. --<br />
* We have a [[Architectures/ARM/TODO|TODO list]].<br />
* Have a look at the [[Architectures/ARM/Credits| Credits page]]<br />
* Fedora ARM is currently heavily driven by the Seneca Centre for Development of Open Technology (CDOT) at the School of Computer Studies at Seneca College, Toronto. More information about their status can be found in the [http://zenit.senecac.on.ca/wiki/index.php/Fedora_ARM_Secondary_Architecture CDOT ARM wiki]<br />
<br />
=== How to get in touch? ===<br />
* The [https://admin.fedoraproject.org/mailman/listinfo/arm Fedora-ARM mailing list] is available for both user and developer discussions.<br />
* We also have an IRC channel #fedora-arm on Freenode.<br />
* Frequent updates about the effort are available at [http://paulfedora.wordpress.com Paul Whalen's ARM blog]<br />
* Some old postings from November 2009 and earlier are available at the [http://fedora-arm.blogspot.com Fedora-ARM blog]<br />
<br />
=== Tracker Bugs ===<br />
If excluding ARM architectures you need to make the bug block '''F-ExcludeArch-ARM''' <br />
<br />
to see whats currently blocking visit [https://bugzilla.redhat.com/show_bug.cgi?id=F-ExcludeArch-ARM Bugzilla ]<br />
<br />
If a bug is specific to ARM architectures make the bug blocking '''ARMTracker'''<br />
<br />
to see not yet resolved issues visit [https://bugzilla.redhat.com/show_bug.cgi?id=ARMTracker Bugzilla ]<br />
=== Package Maintainer Notes ===<br />
As part of setting up to be a package maintainer, you should have run fedora-packager-setup from the fedora-packager rpm. That will write secondary arch config files in ~/.koji. To kick off a build for a package you maintain, run:<br />
<pre><br />
make SECONDARY_CONFIG="-c ~/.koji/arm-config" build<br />
</pre><br />
<br />
To kick off a koji scratch build, run:<br />
<pre><br />
koji -c ~/.koji/arm-config build --scratch dist-f13 /path/to/srpm<br />
</pre><br />
You can change the dist tag to the dist you want to target.<br />
<br />
There is also a separate [http://arm.koji.fedoraproject.org/koji/ Fedora ARM Koji Webinterface].<br />
--><br />
[[Category:Arch-specific SIGs]][[Category:SIGs]]<br />
[[Category:Fedora special-interest groups|ARM]]<br />
[[Category:Fedora ARM]]<br />
[[Category:Fedora ARM Hardware]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Fedora_17_GA&diff=293072Architectures/ARM/Fedora 17 GA2012-06-20T18:35:17Z<p>Maxamaxim: /* Featured Images */ Added link to kirkwood page</p>
<hr />
<div>[[Category:Fedora ARM]][[Category:Fedora 17 GA]]<br />
== Fedora 17 ARM GA ==<br />
We are pleased to announce the general availability (GA) of Fedora 17/ARM. Installable images, kernels, and tar files are now available for download from:<br />
<br />
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/<br />
<br />
== What is included in the GA release? ==<br />
The GA release includes prebuilt images for Versatile Express (QEMU), [[Architectures/ARM/Trimslice|Trimslice]], Beagleboard xM, [[Architectures/ARM/Pandaboard|Pandaboard]], [[Architectures/ARM/Kirkwood|Kirkwood Plugs]], Highbank and [[Architectures/ARM/EFIKA_MX_Smarttop|iMX]] based hardware platforms. Prebuilt images with kernels that can be written directly to SD Card, USB, or SATA drive and booted without any additional steps or configuration. Additionally, separate kernels and tar balls are provided for those who wish to roll their own images.<br />
<br />
== Featured Images ==<br />
Below is a list of currently supplied prebuilt images for the Fedora 17 ARM GA release.<br />
{|width="100%" border="1" cellspacing="2"<br />
! File !! Media !! Targets !! Notes<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-console.tar.xz arm]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-console.tar.xz armhfp]<br />
|<br />
tar.xz<br />
|<br />
arm - armv5tel armhfp - armv7hl<br />
|<br />
This is a simple tarball of a Fedora 17 root filesystem without any kernels or X packages installed. Boots to a getty login prompt, typically on a serial port. Requires a separate kernel.<br />
|-<br />
| <br />
<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-xfce.tar.xz arm]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-xfce.tar.xz armhfp]<br />
|<br />
tar.xz<br />
|<br />
arm - armv5tel armhfp - armv7hl<br />
|<br />
This is a simple tarball of a Fedora 17 root filesystem without any kernels, but with the full XFCE package set installed. Boots to an X login prompt. Requires a separate kernel with frame buffer support.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[[Architectures/ARM/Trimslice|Trimslice]] Bare/Value Pro/H/H250 (Tegra)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to an SD card and placed in the Trimslice's Full Size SD slot (Front slot) and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda-kernel.tar.xz Optional-Kernel]<br />
|<br />
USB SATA<br />
|<br />
[[Architectures/ARM/Trimslice|Trimslice]] Pro/H/H250 (Tegra)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to a Trimslice's internal SSD or Hard Drive and booting without further modification. Write with xzcat file.xz > /dev/sdX, and you're ready to go. When using the internal SSD as your installation target, you may need to first boot with the SD image, then copy the SATA image to the SSD. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-highbank-sda.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-highbank-sda-kernel.tar.xz Optional-Kernel]<br />
|<br />
Native SATA<br />
|<br />
Highbank (Calxeda)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to a Highbank system's SATA or SSD Drive and booting without further modification. Write with xzcat file.xz > /dev/sdX, and you're ready to go. Boots to a "serial" console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-xfce-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[http://fedoraproject.org/wiki/Architectures/ARM/Pandaboard Pandaboard+XFCE (OMAP)]<br />
|<br />
This is a Fedora 17 Hard Float Pandaboard+XFCE Image suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a full XFCE environment with login GUI.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[http://fedoraproject.org/wiki/Architectures/ARM/Pandaboard Pandaboard Console (OMAP)]<br />
|<br />
This is the Fedora 17 Hard Float Pandaboard Image suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0.img.xz HardFP Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-beagle-mmcblk0.img.xz SoftFP Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-beagle-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Beagleboard xM Hard & Soft Float (OMAP)<br />
|<br />
These are Fedora 17 Hard and Soft Float Beagleboard xM Images suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz HardFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-mmcblk0.img.xz SoftFP Image+Kernel]<br> <br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Versatile Express Console (Qemu)<br />
|<br />
These are the Fedora 17 Hard and Soft Float Versatile Express Images suitable for booting with qemu-system-arm without further modification. Requires an external kernel and initrd with a good qemu-system-arm command line; all of which is provided in the boot directory of the kernel file link (or you can extract the files from the main image). Use the included boot-vexpress script to boot to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-xfce-mmcblk0.img.xz HardFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-xfce-mmcblk0.img.xz SoftFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Versatile Express+XFCE (Qemu)<br />
|<br />
These are the Fedora 17 Hard and Soft Float Versatile Express + XFCE Images suitable for booting with qemu-system-arm without further modification. Requires an external kernel and initrd with a good qemu-system-arm command line; all of which is provided in the boot directory of the kernel file link (or you can extract the files from the main image). Use the included boot-vexpress+x script to boot to a full XFCE login GUI.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-mx51-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-mx51-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[[Architectures/ARM/EFIKA_MX_Smarttop|iMX]]<br />
|<br />
This is a Fedora 17 Hard Float iMX Image suitable for writing to an SD card and booting on devices like the Efika Smarttop without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console. This kernel does *not* provide a framebuffer or work with X.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-kirkwood-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-kirkwood-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[[Architectures/ARM/Kirkwood|Sheevaplug, Guruplug, Dreamplug (Kirkwood)]]<br />
|<br />
This is a Fedora 17 Soft Float Kirkwood Image suitable for writing to an SD card and booting on devices such as the GuruPlug, SheevaPlug, and DreamPlug Computers without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and boot by hand. Boots to a serial console. Suggested u-boot commands:<br />
<br />
USB Boot: fatload usb 0 0x6400000 uImage-kirkwood; fatload usb 0 0x7400000 uInitrd-kirkwood; bootm 0x6400000 0x7400000<br />
<br />
SD Boot: fatload mmc 0 0x6400000 uImage-kirkwood; fatload mmc 0 0x7400000 uInitrd-kirkwood; bootm 0x6400000 0x7400000<br />
|-<br />
|<br />
[http://scotland.proximity.on.ca/arm-nightlies/ Nightlies]<br />
|<br />
SD Card<br />
|<br />
Raspberry Pi<br />
|<br />
Raspberry Pi support is not included in Fedora 17 GA because it does not meet the Fedora release guidelines. Specifically, the Raspberry Pi relies upon a custom kernel version, not upstream, as well as special GPU binary blobs which are not acceptable under the current firmware exception. Nonetheless, an '''unsupported''' "nightly" Fedora 17 snapshot is available on the linked page. Likewise, an official Fedora 17 Raspberry Pi Remix will be available shortly and announced separately.<br />
|-<br />
|}<br />
<br />
==Known Issues==<br />
* Yum requires the system time be correct for HTTPS to function. If yum updates are not working check your clock.<br />
* Genesi Efika MX SmartTop generates a kernel warning on reboot and requires use of the reset button to actually reboot.<br />
* Versatile Express images require the kernel parameter 'physmap.enabled=0' be passed to boot correctly. This is included in the boot-vexpress and boot-vexpress+x scripts.<br />
* BeagleBoard-xM generates a kernel warning on reboot and requires use of the reset button to actually reboot.<br />
* 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.<br />
* 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.<br />
* [[Common_F17_bugs|Known release issues]]<br />
<br />
==Contributing to Fedora ARM==<br />
Please join us on the IRC in [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode] or on our mailing list [https://lists.fedoraproject.org/mailman/listinfo/arm arm@lists.fedoraproject.org].<br />
For more information on common and known bugs or tips on how to report bugs please refer to the release notes:<br />
<br />
http://docs.fedoraproject.org/<br />
<br />
There are many ways to contribute beyond bug reporting. You can help translate software and content, test and give feedback on software updates, write and edit documentation, help with all sorts of promotional activities, and package free software for use by millions of Fedora users worldwide. To get started, visit http://join.fedoraproject.org today!</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Fedora_17_GA&diff=293070Architectures/ARM/Fedora 17 GA2012-06-20T18:34:14Z<p>Maxamaxim: Added Catagory</p>
<hr />
<div>[[Category:Fedora ARM]][[Category:Fedora 17 GA]]<br />
== Fedora 17 ARM GA ==<br />
We are pleased to announce the general availability (GA) of Fedora 17/ARM. Installable images, kernels, and tar files are now available for download from:<br />
<br />
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/<br />
<br />
== What is included in the GA release? ==<br />
The GA release includes prebuilt images for Versatile Express (QEMU), [[Architectures/ARM/Trimslice|Trimslice]], Beagleboard xM, [[Architectures/ARM/Pandaboard|Pandaboard]], [[Architectures/ARM/Kirkwood|Kirkwood Plugs]], Highbank and [[Architectures/ARM/EFIKA_MX_Smarttop|iMX]] based hardware platforms. Prebuilt images with kernels that can be written directly to SD Card, USB, or SATA drive and booted without any additional steps or configuration. Additionally, separate kernels and tar balls are provided for those who wish to roll their own images.<br />
<br />
== Featured Images ==<br />
Below is a list of currently supplied prebuilt images for the Fedora 17 ARM GA release.<br />
{|width="100%" border="1" cellspacing="2"<br />
! File !! Media !! Targets !! Notes<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-console.tar.xz arm]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-console.tar.xz armhfp]<br />
|<br />
tar.xz<br />
|<br />
arm - armv5tel armhfp - armv7hl<br />
|<br />
This is a simple tarball of a Fedora 17 root filesystem without any kernels or X packages installed. Boots to a getty login prompt, typically on a serial port. Requires a separate kernel.<br />
|-<br />
| <br />
<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-xfce.tar.xz arm]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-xfce.tar.xz armhfp]<br />
|<br />
tar.xz<br />
|<br />
arm - armv5tel armhfp - armv7hl<br />
|<br />
This is a simple tarball of a Fedora 17 root filesystem without any kernels, but with the full XFCE package set installed. Boots to an X login prompt. Requires a separate kernel with frame buffer support.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[[Architectures/ARM/Trimslice|Trimslice]] Bare/Value Pro/H/H250 (Tegra)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to an SD card and placed in the Trimslice's Full Size SD slot (Front slot) and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda-kernel.tar.xz Optional-Kernel]<br />
|<br />
USB SATA<br />
|<br />
[[Architectures/ARM/Trimslice|Trimslice]] Pro/H/H250 (Tegra)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to a Trimslice's internal SSD or Hard Drive and booting without further modification. Write with xzcat file.xz > /dev/sdX, and you're ready to go. When using the internal SSD as your installation target, you may need to first boot with the SD image, then copy the SATA image to the SSD. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-highbank-sda.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-highbank-sda-kernel.tar.xz Optional-Kernel]<br />
|<br />
Native SATA<br />
|<br />
Highbank (Calxeda)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to a Highbank system's SATA or SSD Drive and booting without further modification. Write with xzcat file.xz > /dev/sdX, and you're ready to go. Boots to a "serial" console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-xfce-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[http://fedoraproject.org/wiki/Architectures/ARM/Pandaboard Pandaboard+XFCE (OMAP)]<br />
|<br />
This is a Fedora 17 Hard Float Pandaboard+XFCE Image suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a full XFCE environment with login GUI.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[http://fedoraproject.org/wiki/Architectures/ARM/Pandaboard Pandaboard Console (OMAP)]<br />
|<br />
This is the Fedora 17 Hard Float Pandaboard Image suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0.img.xz HardFP Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-beagle-mmcblk0.img.xz SoftFP Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-beagle-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Beagleboard xM Hard & Soft Float (OMAP)<br />
|<br />
These are Fedora 17 Hard and Soft Float Beagleboard xM Images suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz HardFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-mmcblk0.img.xz SoftFP Image+Kernel]<br> <br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Versatile Express Console (Qemu)<br />
|<br />
These are the Fedora 17 Hard and Soft Float Versatile Express Images suitable for booting with qemu-system-arm without further modification. Requires an external kernel and initrd with a good qemu-system-arm command line; all of which is provided in the boot directory of the kernel file link (or you can extract the files from the main image). Use the included boot-vexpress script to boot to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-xfce-mmcblk0.img.xz HardFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-xfce-mmcblk0.img.xz SoftFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Versatile Express+XFCE (Qemu)<br />
|<br />
These are the Fedora 17 Hard and Soft Float Versatile Express + XFCE Images suitable for booting with qemu-system-arm without further modification. Requires an external kernel and initrd with a good qemu-system-arm command line; all of which is provided in the boot directory of the kernel file link (or you can extract the files from the main image). Use the included boot-vexpress+x script to boot to a full XFCE login GUI.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-mx51-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-mx51-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[[Architectures/ARM/EFIKA_MX_Smarttop|iMX]]<br />
|<br />
This is a Fedora 17 Hard Float iMX Image suitable for writing to an SD card and booting on devices like the Efika Smarttop without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console. This kernel does *not* provide a framebuffer or work with X.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-kirkwood-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-kirkwood-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Sheevaplug, Guruplug, Dreamplug (Kirkwood)<br />
|<br />
This is a Fedora 17 Soft Float Kirkwood Image suitable for writing to an SD card and booting on devices such as the GuruPlug, SheevaPlug, and DreamPlug Computers without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and boot by hand. Boots to a serial console. Suggested u-boot commands:<br />
<br />
USB Boot: fatload usb 0 0x6400000 uImage-kirkwood; fatload usb 0 0x7400000 uInitrd-kirkwood; bootm 0x6400000 0x7400000<br />
<br />
SD Boot: fatload mmc 0 0x6400000 uImage-kirkwood; fatload mmc 0 0x7400000 uInitrd-kirkwood; bootm 0x6400000 0x7400000<br />
|-<br />
|<br />
[http://scotland.proximity.on.ca/arm-nightlies/ Nightlies]<br />
|<br />
SD Card<br />
|<br />
Raspberry Pi<br />
|<br />
Raspberry Pi support is not included in Fedora 17 GA because it does not meet the Fedora release guidelines. Specifically, the Raspberry Pi relies upon a custom kernel version, not upstream, as well as special GPU binary blobs which are not acceptable under the current firmware exception. Nonetheless, an '''unsupported''' "nightly" Fedora 17 snapshot is available on the linked page. Likewise, an official Fedora 17 Raspberry Pi Remix will be available shortly and announced separately.<br />
|-<br />
|}<br />
<br />
==Known Issues==<br />
* Yum requires the system time be correct for HTTPS to function. If yum updates are not working check your clock.<br />
* Genesi Efika MX SmartTop generates a kernel warning on reboot and requires use of the reset button to actually reboot.<br />
* Versatile Express images require the kernel parameter 'physmap.enabled=0' be passed to boot correctly. This is included in the boot-vexpress and boot-vexpress+x scripts.<br />
* BeagleBoard-xM generates a kernel warning on reboot and requires use of the reset button to actually reboot.<br />
* 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.<br />
* 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.<br />
* [[Common_F17_bugs|Known release issues]]<br />
<br />
==Contributing to Fedora ARM==<br />
Please join us on the IRC in [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode] or on our mailing list [https://lists.fedoraproject.org/mailman/listinfo/arm arm@lists.fedoraproject.org].<br />
For more information on common and known bugs or tips on how to report bugs please refer to the release notes:<br />
<br />
http://docs.fedoraproject.org/<br />
<br />
There are many ways to contribute beyond bug reporting. You can help translate software and content, test and give feedback on software updates, write and edit documentation, help with all sorts of promotional activities, and package free software for use by millions of Fedora users worldwide. To get started, visit http://join.fedoraproject.org today!</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Category:Fedora_17_GA&diff=293068Category:Fedora 17 GA2012-06-20T18:32:43Z<p>Maxamaxim: Added Catagory</p>
<hr />
<div>Pages related to general availability (GA) of Fedora 17/ARM</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Category:Fedora_ARM&diff=293064Category:Fedora ARM2012-06-20T18:28:18Z<p>Maxamaxim: Added Catagory</p>
<hr />
<div>The pages below all deal with the Fedora ARM Architecture.</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=File:Guruplugs.jpg&diff=293028File:Guruplugs.jpg2012-06-20T13:14:47Z<p>Maxamaxim: Guruplugs used at Seneca College to build Fedora for ARM. There are twenty Guruplugs in the Seneca build farm.</p>
<hr />
<div>Guruplugs used at Seneca College to build Fedora for ARM. There are twenty Guruplugs in the Seneca build farm.</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Fedora_17_GA&diff=293026Architectures/ARM/Fedora 17 GA2012-06-20T13:08:27Z<p>Maxamaxim: Added link to the Kirkwood page</p>
<hr />
<div>== Fedora 17 ARM GA ==<br />
We are pleased to announce the general availability (GA) of Fedora 17/ARM. Installable images, kernels, and tar files are now available for download from:<br />
<br />
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/<br />
<br />
== What is included in the GA release? ==<br />
The GA release includes prebuilt images for Versatile Express (QEMU), [[Architectures/ARM/Trimslice|Trimslice]], Beagleboard xM, [[Architectures/ARM/Pandaboard|Pandaboard]], [[Architectures/ARM/Kirkwood|Kirkwood Plugs]], Highbank and [[Architectures/ARM/EFIKA_MX_Smarttop|iMX]] based hardware platforms. Prebuilt images with kernels that can be written directly to SD Card, USB, or SATA drive and booted without any additional steps or configuration. Additionally, separate kernels and tar balls are provided for those who wish to roll their own images.<br />
<br />
== Featured Images ==<br />
Below is a list of currently supplied prebuilt images for the Fedora 17 ARM GA release.<br />
{|width="100%" border="1" cellspacing="2"<br />
! File !! Media !! Targets !! Notes<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-console.tar.xz arm]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-console.tar.xz armhfp]<br />
|<br />
tar.xz<br />
|<br />
arm - armv5tel armhfp - armv7hl<br />
|<br />
This is a simple tarball of a Fedora 17 root filesystem without any kernels or X packages installed. Boots to a getty login prompt, typically on a serial port. Requires a separate kernel.<br />
|-<br />
| <br />
<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-xfce.tar.xz arm]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-xfce.tar.xz armhfp]<br />
|<br />
tar.xz<br />
|<br />
arm - armv5tel armhfp - armv7hl<br />
|<br />
This is a simple tarball of a Fedora 17 root filesystem without any kernels, but with the full XFCE package set installed. Boots to an X login prompt. Requires a separate kernel with frame buffer support.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[[Architectures/ARM/Trimslice|Trimslice]] Bare/Value Pro/H/H250 (Tegra)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to an SD card and placed in the Trimslice's Full Size SD slot (Front slot) and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda-kernel.tar.xz Optional-Kernel]<br />
|<br />
USB SATA<br />
|<br />
[[Architectures/ARM/Trimslice|Trimslice]] Pro/H/H250 (Tegra)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to a Trimslice's internal SSD or Hard Drive and booting without further modification. Write with xzcat file.xz > /dev/sdX, and you're ready to go. When using the internal SSD as your installation target, you may need to first boot with the SD image, then copy the SATA image to the SSD. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-highbank-sda.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-highbank-sda-kernel.tar.xz Optional-Kernel]<br />
|<br />
Native SATA<br />
|<br />
Highbank (Calxeda)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to a Highbank system's SATA or SSD Drive and booting without further modification. Write with xzcat file.xz > /dev/sdX, and you're ready to go. Boots to a "serial" console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-xfce-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[http://fedoraproject.org/wiki/Architectures/ARM/Pandaboard Pandaboard+XFCE (OMAP)]<br />
|<br />
This is a Fedora 17 Hard Float Pandaboard+XFCE Image suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a full XFCE environment with login GUI.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[http://fedoraproject.org/wiki/Architectures/ARM/Pandaboard Pandaboard Console (OMAP)]<br />
|<br />
This is the Fedora 17 Hard Float Pandaboard Image suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0.img.xz HardFP Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-beagle-mmcblk0.img.xz SoftFP Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-beagle-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Beagleboard xM Hard & Soft Float (OMAP)<br />
|<br />
These are Fedora 17 Hard and Soft Float Beagleboard xM Images suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz HardFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-mmcblk0.img.xz SoftFP Image+Kernel]<br> <br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Versatile Express Console (Qemu)<br />
|<br />
These are the Fedora 17 Hard and Soft Float Versatile Express Images suitable for booting with qemu-system-arm without further modification. Requires an external kernel and initrd with a good qemu-system-arm command line; all of which is provided in the boot directory of the kernel file link (or you can extract the files from the main image). Use the included boot-vexpress script to boot to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-xfce-mmcblk0.img.xz HardFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-xfce-mmcblk0.img.xz SoftFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Versatile Express+XFCE (Qemu)<br />
|<br />
These are the Fedora 17 Hard and Soft Float Versatile Express + XFCE Images suitable for booting with qemu-system-arm without further modification. Requires an external kernel and initrd with a good qemu-system-arm command line; all of which is provided in the boot directory of the kernel file link (or you can extract the files from the main image). Use the included boot-vexpress+x script to boot to a full XFCE login GUI.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-mx51-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-mx51-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
[[Architectures/ARM/EFIKA_MX_Smarttop|iMX]]<br />
|<br />
This is a Fedora 17 Hard Float iMX Image suitable for writing to an SD card and booting on devices like the Efika Smarttop without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console. This kernel does *not* provide a framebuffer or work with X.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-kirkwood-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-kirkwood-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Sheevaplug, Guruplug, Dreamplug (Kirkwood)<br />
|<br />
This is a Fedora 17 Soft Float Kirkwood Image suitable for writing to an SD card and booting on devices such as the GuruPlug, SheevaPlug, and DreamPlug Computers without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and boot by hand. Boots to a serial console. Suggested u-boot commands:<br />
<br />
USB Boot: fatload usb 0 0x6400000 uImage-kirkwood; fatload usb 0 0x7400000 uInitrd-kirkwood; bootm 0x6400000 0x7400000<br />
<br />
SD Boot: fatload mmc 0 0x6400000 uImage-kirkwood; fatload mmc 0 0x7400000 uInitrd-kirkwood; bootm 0x6400000 0x7400000<br />
|-<br />
|<br />
[http://scotland.proximity.on.ca/arm-nightlies/ Nightlies]<br />
|<br />
SD Card<br />
|<br />
Raspberry Pi<br />
|<br />
Raspberry Pi support is not included in Fedora 17 GA because it does not meet the Fedora release guidelines. Specifically, the Raspberry Pi relies upon a custom kernel version, not upstream, as well as special GPU binary blobs which are not acceptable under the current firmware exception. Nonetheless, an '''unsupported''' "nightly" Fedora 17 snapshot is available on the linked page. Likewise, an official Fedora 17 Raspberry Pi Remix will be available shortly and announced separately.<br />
|-<br />
|}<br />
<br />
==Known Issues==<br />
* Yum requires the system time be correct for HTTPS to function. If yum updates are not working check your clock.<br />
* Genesi Efika MX SmartTop generates a kernel warning on reboot and requires use of the reset button to actually reboot.<br />
* Versatile Express images require the kernel parameter 'physmap.enabled=0' be passed to boot correctly. This is included in the boot-vexpress and boot-vexpress+x scripts.<br />
* BeagleBoard-xM generates a kernel warning on reboot and requires use of the reset button to actually reboot.<br />
* 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.<br />
* 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.<br />
* [[Common_F17_bugs|Known release issues]]<br />
<br />
==Contributing to Fedora ARM==<br />
Please join us on the IRC in [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode] or on our mailing list [https://lists.fedoraproject.org/mailman/listinfo/arm arm@lists.fedoraproject.org].<br />
For more information on common and known bugs or tips on how to report bugs please refer to the release notes:<br />
<br />
http://docs.fedoraproject.org/<br />
<br />
There are many ways to contribute beyond bug reporting. You can help translate software and content, test and give feedback on software updates, write and edit documentation, help with all sorts of promotional activities, and package free software for use by millions of Fedora users worldwide. To get started, visit http://join.fedoraproject.org today!</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Fedora_17_GA&diff=292727Architectures/ARM/Fedora 17 GA2012-06-19T02:56:28Z<p>Maxamaxim: /* Known Issues */ iMX reboot issue added</p>
<hr />
<div>== Fedora 17 ARM GA ==<br />
We are pleased to announce the general availability (GA) of Fedora 17/ARM. Installable images, kernels, and tar files are now available for download from:<br />
<br />
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/<br />
<br />
== What is included in the GA release? ==<br />
The GA release includes prebuilt images for Versatile Express (QEMU), Trimslice, Beagleboard xM, Pandboard, Kirkwood Plugs, Highbank and iMX based hardware platforms. Prebuilt images with kernels that can be written directly to SD Card, USB, or SATA drive and booted without any additional steps or configuration. Additionally, separate kernels and tar balls are provided for those who wish to roll their own images.<br />
<br />
== Featured Images ==<br />
Below is a list of currently supplied prebuilt images for the Fedora 17 ARM GA release.<br />
{|width="100%" border="1" cellspacing="2"<br />
! File !! Media !! Targets !! Notes<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-console.tar.xz arm]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-console.tar.xz armhfp]<br />
|<br />
tar.xz<br />
|<br />
arm - armv5tel armhfp - armv7hl<br />
|<br />
This is a simple tarball of a Fedora 17 root filesystem without any kernels or X packages installed. Boots to a getty login prompt, typically on a serial port. Requires a separate kernel.<br />
|-<br />
| <br />
<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-xfce.tar.xz arm]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-xfce.tar.xz armhfp]<br />
|<br />
tar.xz<br />
|<br />
arm - armv5tel armhfp - armv7hl<br />
|<br />
This is a simple tarball of a Fedora 17 root filesystem without any kernels, but with the full XFCE package set installed. Boots to an X login prompt. Requires a separate kernel with frame buffer support.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Trimslice Bare/Value Pro/H/H250 (Tegra)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to an SD card and placed in the Trimslice's Full Size SD slot (Front slot) and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda-kernel.tar.xz Optional-Kernel]<br />
|<br />
USB SATA<br />
|<br />
Trimslice Pro/H/H250 (Tegra)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to a Trimslice's internal SSD or Hard Drive and booting without further modification. Write with xzcat file.xz > /dev/sdX, and you're ready to go. When using the internal SSD as your installation target, you may need to first boot with the SD image, then copy the SATA image to the SSD. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-highbank-sda.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-highbank-sda-kernel.tar.xz Optional-Kernel]<br />
|<br />
Native SATA<br />
|<br />
Highbank (Calxeda)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to a Highbank system's SATA or SSD Drive and booting without further modification. Write with xzcat file.xz > /dev/sdX, and you're ready to go. Boots to a "serial" console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-xfce-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Pandaboard+XFCE (OMAP)<br />
|<br />
This is a Fedora 17 Hard Float Pandaboard+XFCE Image suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a full XFCE environment with login GUI.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Pandaboard Console (OMAP)<br />
|<br />
This is the Fedora 17 Hard Float Pandaboard Image suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0.img.xz HardFP Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-beagle-mmcblk0.img.xz SoftFP Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-beagle-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Beagleboard xM Hard & Soft Float (OMAP)<br />
|<br />
These are Fedora 17 Hard and Soft Float Beagleboard xM Images suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz HardFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-mmcblk0.img.xz SoftFP Image+Kernel]<br> <br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Versatile Express Console (Qemu)<br />
|<br />
These are the Fedora 17 Hard and Soft Float Versatile Express Images suitable for booting with qemu-system-arm without further modification. Requires an external kernel and initrd with a good qemu-system-arm command line; all of which is provided in the boot directory of the kernel file link (or you can extract the files from the main image). Use the included boot-vexpress script to boot to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-xfce-mmcblk0.img.xz HardFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-xfce-mmcblk0.img.xz SoftFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Versatile Express+XFCE (Qemu)<br />
|<br />
These are the Fedora 17 Hard and Soft Float Versatile Express + XFCE Images suitable for booting with qemu-system-arm without further modification. Requires an external kernel and initrd with a good qemu-system-arm command line; all of which is provided in the boot directory of the kernel file link (or you can extract the files from the main image). Use the included boot-vexpress+x script to boot to a full XFCE login GUI.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-mx51-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-mx51-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
iMX<br />
|<br />
This is a Fedora 17 Hard Float iMX Image suitable for writing to an SD card and booting on devices like the Efika Smarttop without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console. This kernel does *not* provide a framebuffer or work with X.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-kirkwood-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-kirkwood-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Sheevaplug, Guruplug, Dreamplug (Kirkwood)<br />
|<br />
This is a Fedora 17 Soft Float Kirkwood Image suitable for writing to an SD card and booting on devices such as the GuruPlug, SheevaPlug, and DreamPlug Computers without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and boot by hand. Boots to a serial console. Suggested u-boot commands:<br />
<br />
USB Boot: fatload usb 0 0x6400000 uImage-kirkwood; fatload usb 0 0x7400000 uInitrd-kirkwood; bootm 0x6400000 0x7400000<br />
<br />
SD Boot: fatload mmc 0 0x6400000 uImage-kirkwood; fatload mmc 0 0x7400000 uInitrd-kirkwood; bootm 0x6400000 0x7400000<br />
|-<br />
|}<br />
<br />
==Known Issues==<br />
* Yum requires the system time be correct for HTTPS to function. If yum updates are not working check your clock.<br />
* Genesi Efika MX SmartTop generates a kernel warning on reboot and requires use of the reset button to actually reboot.<br />
* Versatile Express images require the kernel parameter 'physmap.enabled=0' be passed to boot correctly. This is included in the boot-vexpress and boot-vexpress+x scripts.<br />
* BeagleBoard-xM generates a kernel warning on reboot and requires use of the reset button to actually reboot.<br />
* 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.<br />
* [[Common_F17_bugs|Known release issues]]<br />
<br />
==Contributing to Fedora ARM==<br />
Please join us on the IRC in [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode] or on our mailing list [https://lists.fedoraproject.org/mailman/listinfo/arm arm@lists.fedoraproject.org].<br />
For more information on common and known bugs or tips on how to report bugs please refer to the release notes:<br />
<br />
http://docs.fedoraproject.org/<br />
<br />
There are many ways to contribute beyond bug reporting. You can help translate software and content, test and give feedback on software updates, write and edit documentation, help with all sorts of promotional activities, and package free software for use by millions of Fedora users worldwide. To get started, visit http://join.fedoraproject.org today!</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Fedora_17_GA&diff=292723Architectures/ARM/Fedora 17 GA2012-06-19T02:10:09Z<p>Maxamaxim: Fixed Beagleboard name: XM to xM</p>
<hr />
<div>== Fedora 17 ARM GA ==<br />
We are pleased to announce the general availability (GA) of Fedora 17/ARM. Installable images, kernels, and tar files are now available for download from:<br />
<br />
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/<br />
<br />
== What is included in the GA release? ==<br />
The GA release includes prebuilt images for Versatile Express (QEMU), Trimslice, Beagleboard xM, Pandboard, Kirkwood Plugs, Highbank and iMX based hardware platforms. Prebuilt images with kernels that can be written directly to SD Card, USB, or SATA drive and booted without any additional steps or configuration. Additionally, separate kernels and tar balls are provided for those who wish to roll their own images.<br />
<br />
== Featured Images ==<br />
Below is a list of currently supplied prebuilt images for the Fedora 17 ARM GA release.<br />
{|width="100%" border="1" cellspacing="2"<br />
! File !! Media !! Targets !! Notes<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-console.tar.xz arm]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-console.tar.xz armhfp]<br />
|<br />
tar.xz<br />
|<br />
arm - armv5tel armhfp - armv7hl<br />
|<br />
This is a simple tarball of a Fedora 17 root filesystem without any kernels or X packages installed. Boots to a getty login prompt, typically on a serial port. Requires a separate kernel.<br />
|-<br />
| <br />
<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-xfce.tar.xz arm]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-xfce.tar.xz armhfp]<br />
|<br />
tar.xz<br />
|<br />
arm - armv5tel armhfp - armv7hl<br />
|<br />
This is a simple tarball of a Fedora 17 root filesystem without any kernels, but with the full XFCE package set installed. Boots to an X login prompt. Requires a separate kernel with frame buffer support.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Trimslice Bare/Value Pro/H/H250 (Tegra)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to an SD card and placed in the Trimslice's Full Size SD slot (Front slot) and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-trimslice-sda-kernel.tar.xz Optional-Kernel]<br />
|<br />
USB SATA<br />
|<br />
Trimslice Pro/H/H250 (Tegra)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to a Trimslice's internal SSD or Hard Drive and booting without further modification. Write with xzcat file.xz > /dev/sdX, and you're ready to go. When using the internal SSD as your installation target, you may need to first boot with the SD image, then copy the SATA image to the SSD. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-highbank-sda.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-highbank-sda-kernel.tar.xz Optional-Kernel]<br />
|<br />
Native SATA<br />
|<br />
Highbank (Calxeda)<br />
|<br />
This is a Fedora 17 Hard Float Trimslice Image suitable for writing to a Highbank system's SATA or SSD Drive and booting without further modification. Write with xzcat file.xz > /dev/sdX, and you're ready to go. Boots to a "serial" console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-xfce-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Pandaboard+XFCE (OMAP)<br />
|<br />
This is a Fedora 17 Hard Float Pandaboard+XFCE Image suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a full XFCE environment with login GUI.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-panda-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Pandaboard Console (OMAP)<br />
|<br />
This is the Fedora 17 Hard Float Pandaboard Image suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0.img.xz HardFP Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-beagle-mmcblk0.img.xz SoftFP Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-beagle-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Beagleboard xM Hard & Soft Float (OMAP)<br />
|<br />
These are Fedora 17 Hard and Soft Float Beagleboard xM Images suitable for writing to an SD card and booting without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0.img.xz HardFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-mmcblk0.img.xz SoftFP Image+Kernel]<br> <br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Versatile Express Console (Qemu)<br />
|<br />
These are the Fedora 17 Hard and Soft Float Versatile Express Images suitable for booting with qemu-system-arm without further modification. Requires an external kernel and initrd with a good qemu-system-arm command line; all of which is provided in the boot directory of the kernel file link (or you can extract the files from the main image). Use the included boot-vexpress script to boot to a serial console.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-xfce-mmcblk0.img.xz HardFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-vexpress-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-xfce-mmcblk0.img.xz SoftFP Image+Kernel]<br><br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-vexpress-xfce-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Versatile Express+XFCE (Qemu)<br />
|<br />
These are the Fedora 17 Hard and Soft Float Versatile Express + XFCE Images suitable for booting with qemu-system-arm without further modification. Requires an external kernel and initrd with a good qemu-system-arm command line; all of which is provided in the boot directory of the kernel file link (or you can extract the files from the main image). Use the included boot-vexpress+x script to boot to a full XFCE login GUI.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-mx51-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-mx51-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
iMX<br />
|<br />
This is a Fedora 17 Hard Float iMX Image suitable for writing to an SD card and booting on devices like the Efika Smarttop without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console. This kernel does *not* provide a framebuffer or work with X.<br />
|-<br />
|<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-kirkwood-mmcblk0.img.xz Image+Kernel]<br />
[http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-kirkwood-mmcblk0-kernel.tar.xz Optional-Kernel]<br />
|<br />
SD Card<br />
|<br />
Sheevaplug, Guruplug, Dreamplug (Kirkwood)<br />
|<br />
This is a Fedora 17 Soft Float Kirkwood Image suitable for writing to an SD card and booting on devices such as the GuruPlug, SheevaPlug, and DreamPlug Computers without further modification. Write with xzcat file.xz > /dev/mmcblkX, put in the device, and boot by hand. Boots to a serial console. Suggested u-boot commands:<br />
<br />
USB Boot: fatload usb 0 0x6400000 uImage-kirkwood; fatload usb 0 0x7400000 uInitrd-kirkwood; bootm 0x6400000 0x7400000<br />
<br />
SD Boot: fatload mmc 0 0x6400000 uImage-kirkwood; fatload mmc 0 0x7400000 uInitrd-kirkwood; bootm 0x6400000 0x7400000<br />
|-<br />
|}<br />
<br />
==Known Issues==<br />
* Yum requires the system time be correct for HTTPS to function. If yum updates are not working check your clock.<br />
* Versatile Express images require the kernel parameter 'physmap.enabled=0' be passed to boot correctly. This is included in the boot-vexpress and boot-vexpress+x scripts.<br />
* 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.<br />
* [[Common_F17_bugs|Known release issues]]<br />
<br />
==Contributing to Fedora ARM==<br />
Please join us on the IRC in [irc://irc.freenode.net/fedora-arm #fedora-arm] on [http://freenode.net Freenode] or on our mailing list [https://lists.fedoraproject.org/mailman/listinfo/arm arm@lists.fedoraproject.org].<br />
For more information on common and known bugs or tips on how to report bugs please refer to the release notes:<br />
<br />
http://docs.fedoraproject.org/<br />
<br />
There are many ways to contribute beyond bug reporting. You can help translate software and content, test and give feedback on software updates, write and edit documentation, help with all sorts of promotional activities, and package free software for use by millions of Fedora users worldwide. To get started, visit http://join.fedoraproject.org today!</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292663Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T21:27:59Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
* Serge - EdB<br />
* Jeff Bastian - jbastian<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold ||{{result|pass|herrold}} ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| Some non-blocking bugs filed.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD <br /> jbastian - SD+USB ||{{result|pass|pwhalen}} <br /> {{result|inprogress|jbastian}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] <br /> [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD-USB | Pandaboard SD+USB Results ]] || All working. <br /> (in progress)<br />
|-<br />
|| Pandaboard+XFCE || jcapik - SD || {{result|inprogress|jcapik}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard+Xfce-SD | Pandaboard+Xfce SD Results]] || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA, maxam - HFP SD ||{{result|pass|pwhalen}} {{result|pass|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD results ]][[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-SATA-Trimslice_Pro |Trimslice_Pro - SATA]] || All good on the SD and USB HD!<br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Highbank-SATA | Highbank SATA Results ]]|| <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || agreene - GuruPlug - SD, maxam Guruplug SD || {{result|pass|maxam}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD | GuruPlug SD Results]] || [http://fpaste.org/bkHU/ (Specific uboot command used)] All good!<br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|pass|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-SATA-Trimslice_Pro&diff=292662Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-SATA-Trimslice Pro2012-06-18T21:27:13Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|pwhalen}} || <br />
|-<br />
|| 2 ||{{result|pass|pwhalen}} || <br />
|-<br />
|| 3 ||{{result|pass|pwhalen}} || 1.8G<br />
|-<br />
|| 4 ||{{result|pass|pwhalen}} || <br />
|-<br />
|| 5 ||{{result|unknown|pwhalen}} {{result|pass|maxam}}|| Serial works <br />
|-<br />
|| 6 ||{{result|unknown|pwhalen}}{{result|pass|maxam}} || No serial connection. Used ssh to log in. [http://fpaste.org/xPpY/ boots]<br />
|-<br />
|| 7 ||{{result|pass|pwhalen}} || <br />
|-<br />
|| 8 ||{{result|pass|pwhalen}} || <br />
|-<br />
|| 9 ||{{result|fail|pwhalen}}{{result|pass|maxam}} ||System does not come back up after issuing a reboot. No serial connection. [http://fpaste.org/9RQC/ looks good]<br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|pass|pwhalen}} ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292651Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T21:00:58Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
* Serge - EdB<br />
* Jeff Bastian - jbastian<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold ||{{result|pass|herrold}} ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| Some non-blocking bugs filed.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD <br /> jbastian - SD+USB ||{{result|pass|pwhalen}} <br /> {{result|inprogress|jbastian}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] <br /> [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD-USB | Pandaboard SD+USB Results ]] || All working. <br /> (in progress)<br />
|-<br />
|| Pandaboard+XFCE || jcapik - SD || {{result|inprogress|jcapik}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard+Xfce-SD | Pandaboard+Xfce SD Results]] || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA, maxam - HFP SD ||{{result|pass|pwhalen}} {{result|pass|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD results ]][[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-SATA-Trimslice_Pro |Trimslice_Pro - SATA]] || All good on the SD!<br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Highbank-SATA | Highbank SATA Results ]]|| <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || agreene - GuruPlug - SD, maxam Guruplug SD || {{result|pass|maxam}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD | GuruPlug SD Results]] || [http://fpaste.org/bkHU/ (Specific uboot command used)] All good!<br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|pass|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292650Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T21:00:22Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
* Serge - EdB<br />
* Jeff Bastian - jbastian<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold ||{{result|pass|herrold}} ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| Some non-blocking bugs filed.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD <br /> jbastian - SD+USB ||{{result|pass|pwhalen}} <br /> {{result|inprogress|jbastian}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] <br /> [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD-USB | Pandaboard SD+USB Results ]] || All working. <br /> (in progress)<br />
|-<br />
|| Pandaboard+XFCE || jcapik - SD || {{result|inprogress|jcapik}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard+Xfce-SD | Pandaboard+Xfce SD Results]] || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA, maxam - HFP SD ||{{result|pass|pwhalen}} {{result|pass|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD results ]][[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-SATA-Trimslice_Pro |Trimslice_Pro - SATA]] || All good on the SD!<br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Highbank-SATA | Highbank SATA Results ]]|| <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || agreene - GuruPlug - SD, maxam Guruplug SD || {{result|inprogress|agreene}} {{result|inprogress|maxam}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD | GuruPlug SD Results]] || [http://fpaste.org/bkHU/ (Specific uboot command used)] All good!<br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|pass|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD&diff=292648Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-GuruPlug-SD2012-06-18T20:59:09Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || {{result|pass|agreene}}{{result|pass|maxam}}|| <br />
|-<br />
|| 2 || {{result|pass|agreene}}{{result|pass|maxam}} || <br />
|-<br />
|| 3 || {{result|pass|agreene}}{{result|pass|maxam}} || <br />
|-<br />
|| 4 || {{result|fail|agreene}}{{result|pass|maxam}} || [http://fpaste.org/5gwg/ Kernel panic] [http://fpaste.org/0WtG/ Boots!]<br />
|-<br />
|| 5 ||{{result|pass|maxam}} || [http://fpaste.org/dzLO/ boots] [http://fpaste.org/bkHU/ (Specific boot command used)]<br />
|-<br />
|| 6 ||{{result|pass|maxam}} || <br />
|-<br />
|| 7 || {{result|pass|maxam}}|| <br />
|-<br />
|| 8 ||{{result|pass|maxam}} || <br />
|-<br />
|| 9 || {{result|pass|maxam}}|| [http://fpaste.org/4VJj/ reboots just fine!]<br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|pass|maxam}} ||<br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD&diff=292646Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-GuruPlug-SD2012-06-18T20:57:11Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || {{result|pass|agreene}}{{result|pass|maxam}}|| <br />
|-<br />
|| 2 || {{result|pass|agreene}}{{result|pass|maxam}} || <br />
|-<br />
|| 3 || {{result|pass|agreene}}{{result|pass|maxam}} || <br />
|-<br />
|| 4 || {{result|fail|agreene}}{{result|pass|maxam}} || [http://fpaste.org/5gwg/ Kernel panic] [http://fpaste.org/0WtG/ Boots!]<br />
|-<br />
|| 5 ||{{result|pass|maxam}} || [http://fpaste.org/dzLO/ (Specific boot command used)]<br />
|-<br />
|| 6 ||{{result|pass|maxam}} || <br />
|-<br />
|| 7 || {{result|pass|maxam}}|| <br />
|-<br />
|| 8 ||{{result|pass|maxam}} || <br />
|-<br />
|| 9 || {{result|pass|maxam}}|| [http://fpaste.org/4VJj/ reboots just fine!]<br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|pass|maxam}} ||<br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD&diff=292642Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-GuruPlug-SD2012-06-18T20:14:10Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || {{result|pass|agreene}}{{result|pass|maxam}}|| <br />
|-<br />
|| 2 || {{result|pass|agreene}}{{result|pass|maxam}} || <br />
|-<br />
|| 3 || {{result|pass|agreene}}{{result|pass|maxam}} || <br />
|-<br />
|| 4 || {{result|fail|agreene}}{{result|pass|maxam}} || [http://fpaste.org/5gwg/ Kernel panic]<br />
|-<br />
|| 5 ||{{result|pass|maxam}} || Boots! [http://fpaste.org/dzLO/ (Specific boot command used)]<br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292638Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T20:09:58Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
* Serge - EdB<br />
* Jeff Bastian - jbastian<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold ||{{result|pass|herrold}} ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| Some non-blocking bugs filed.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD <br /> jbastian - SD+USB ||{{result|pass|pwhalen}} <br /> {{result|inprogress|jbastian}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] <br /> [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD-USB | Pandaboard SD+USB Results ]] || All working. <br /> (in progress)<br />
|-<br />
|| Pandaboard+XFCE || jcapik - SD || {{result|inprogress|jcapik}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard+Xfce-SD | Pandaboard+Xfce SD Results]] || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA, maxam - HFP SD ||{{result|pass|pwhalen}} {{result|pass|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD results ]][[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-SATA-Trimslice_Pro |Trimslice_Pro - SATA]] || All good on the SD!<br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Highbank-SATA | Highbank SATA Results ]]|| <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || agreene - GuruPlug - SD, maxam Guruplug SD || {{result|inprogress|agreene}} {{result|inprogress|maxam}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD | GuruPlug SD Results]] || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|pass|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292610Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T19:22:41Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
* Serge - EdB<br />
* Jeff Bastian - jbastian<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold ||{{result|pass|herrold}} ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| Some non-blocking bugs filed.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD, jbastian - SD+USB ||{{result|pass|pwhalen}} {{result|inprogress|jbastian}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] || All working.<br />
|-<br />
|| Pandaboard+XFCE || jcapik - SD || {{result|inprogress|jcapik}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard+Xfce-SD | Pandaboard+Xfce SD Results]] || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA, maxam - HFP SD ||{{result|inprogress|pwhalen}} {{result|pass|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD results ]] || All good on the SD!<br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|inprogress|dmarlin}} || || <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || agreene - GuruPlug - SD || {{result|inprogress|agreene}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD | GuruPlug SD Results]] || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|pass|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292604Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T19:03:30Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
* Serge - EdB<br />
* Jeff Bastian - jbastian<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold ||{{result|pass|herrold}} ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| Some non-blocking bugs filed.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD, jbastian - SD+USB ||{{result|pass|pwhalen}} {{result|inprogress|jbastian}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] || All working.<br />
|-<br />
|| Pandaboard+XFCE ||jcapik - SD || || || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA, maxam - HFP SD ||{{result|inprogress|pwhalen}} {{result|pass|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD results ]] || All good on the SD!<br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|inprogress|dmarlin}} || || <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || agreene - GuruPlug - SD || {{result|inprogress|agreene}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD | GuruPlug SD Results]] || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|warn|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292602Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T19:02:55Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
* Serge - EdB<br />
* Jeff Bastian - jbastian<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold ||{{result|pass|herrold}} ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| Some non-blocking bugs filed.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD, jbastian - SD+USB ||{{result|pass|pwhalen}} {{result|inprogress|jbastian}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] || All working.<br />
|-<br />
|| Pandaboard+XFCE ||jcapik - SD || || || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA, maxam - HFP SD ||{{result|pass|pwhalen}} {{result|inprogress|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD results ]] || All good on the SD!<br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|inprogress|dmarlin}} || || <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || agreene - GuruPlug - SD || {{result|inprogress|agreene}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD | GuruPlug SD Results]] || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|warn|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimslicePro-SD&diff=292601Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-TrimslicePro-SD2012-06-18T19:01:48Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==TrimslicePro-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || {{result|pass|maxam}} || <br />
|-<br />
|| 2 || {{result|pass|maxam}} || <br />
|-<br />
|| 3 || {{result|pass|maxam}} || <br />
|-<br />
|| 4 || {{result|pass|maxam}} || <br />
|-<br />
|| 5 || {{result|pass|maxam}} || [http://fpaste.org/HtYZ/ It works mostly!]<br />
|-<br />
|| 6 || {{result|pass|maxam}} || Boots to serial<br />
|-<br />
|| 7 || {{result|pass|maxam}} || <br />
|-<br />
|| 8 || {{result|pass|maxam}} || <br />
|-<br />
|| 9 || {{result|pass|maxam}} || [http://fpaste.org/OPey/ reboot works on SD]<br />
|-<br />
|| 10 ||{{result|warn|maxam}} || [http://fpaste.org/Imf4/ Sound does not work on non GUI ... is it supposed to?]<br />
|-<br />
|| 11 || {{result|pass|maxam}} || <br />
|-<br />
|| 12 || n/a ||<br />
|-<br />
|| 13 || n/a ||<br />
|-<br />
|| 14 || n/a ||<br />
|-<br />
|| 15 || n/a ||<br />
|-<br />
|| 16 || n/a ||<br />
|-<br />
|| 17 || n/a ||<br />
|-<br />
|| 18 || n/a ||<br />
|-<br />
|| 19 || n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimslicePro-SD&diff=292573Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-TrimslicePro-SD2012-06-18T18:09:57Z<p>Maxamaxim: Created page with "==TrimslicePro-HFP-SD== 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..."</p>
<hr />
<div>==TrimslicePro-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || {{result|pass|maxam}} || <br />
|-<br />
|| 2 || {{result|pass|maxam}} || <br />
|-<br />
|| 3 || {{result|pass|maxam}} || <br />
|-<br />
|| 4 || {{result|pass|maxam}} || <br />
|-<br />
|| 5 || {{result|pass|maxam}} || [http://fpaste.org/O7cQ/ HFP Non GUI SD], [http://fpaste.org/G44v/ HFP Non GUI HD],[FAILED] Failed to start LSB: Bring up/down networking. Even after network was setup (after reboots)<br />
|-<br />
|| 6 || {{result|pass|maxam}} || Boots to serial<br />
|-<br />
|| 7 || {{result|pass|maxam}} || [http://fpaste.org/S0n3/ Why is it creating the new ones?] also ...http://mirror.chpc.utah.edu/pub/fedora-secondary/updates/17/armhfp/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates <br />
|-<br />
|| 8 || {{result|pass|maxam}} || <br />
|-<br />
|| 9 || {{result|pass|maxam}} || [http://fpaste.org/OdLL/ reboot works on SD] [http://fpaste.org/Tvqy/ reboot works on HD]<br />
|-<br />
|| 10 || n/a || <br />
|-<br />
|| 11 || {{result|fail|maxam}} || No release notes<br />
|-<br />
|| 12 || n/a ||<br />
|-<br />
|| 13 || n/a ||<br />
|-<br />
|| 14 || n/a ||<br />
|-<br />
|| 15 || n/a ||<br />
|-<br />
|| 16 || n/a ||<br />
|-<br />
|| 17 || n/a ||<br />
|-<br />
|| 18 || n/a ||<br />
|-<br />
|| 19 || n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292572Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T18:09:45Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold ||{{result|pass|herrold}} ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| Some non-blocking bugs filed.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD ||{{result|pass|pwhalen}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] || All working.<br />
|-<br />
|| Pandaboard+XFCE ||jcapik - SD || || || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA, maxam - HFP SD ||{{result|inprogress|pwhalen}} {{result|inprogress|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD results ]] || <br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|inprogress|bconoboy}} || || <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || agreene - GuruPlug - SD || {{result|inprogress|agreene}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-GuruPlug-SD | GuruPlug SD Results]] || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|warn|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292569Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T18:05:48Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxam}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|warn|maxam}} || [http://fpaste.org/7ewb/ unable to open rtc device, imx-sdma imx35-sdma: firmware not found]<br />
|-<br />
|| 6 ||{{result|warn|maxam}} || Boots to serial console, [http://fpaste.org/P9dz/ dma mismatch? still]<br />
|-<br />
|| 7 ||{{result|pass|maxam}} || http://mirror.chpc.utah.edu/pub/fedora-secondary/updates/17/armhfp/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates<br />
|-<br />
|| 8 ||{{result|pass|maxam}} || <br />
|-<br />
|| 9 ||{{result|fail|maxam}} || [http://fpaste.org/J4xd/ reboot/halt fails]<br />
|-<br />
|| 10 ||{{result|warn|maxam}} || [http://fpaste.org/Imf4/ Sound does not work on non GUI ... is it supposed to?]<br />
|-<br />
|| 11 ||{{result|pass|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292564Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T18:00:15Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold ||{{result|pass|herrold}} ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| Some non-blocking bugs filed.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD ||{{result|pass|pwhalen}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] || All working.<br />
|-<br />
|| Pandaboard+XFCE ||jcapik - SD || || || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA, maxam - HFP SD ||{{result|inprogress|pwhalen}} {{result|inprogress|maxam}} || || <br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|inprogress|bconoboy}} || || <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || agreene - guru || {{result|inprogress|agreene}} || || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|warn|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292563Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T17:59:32Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold ||{{result|pass|herrold}} ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| Some non-blocking bugs filed.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD ||{{result|pass|pwhalen}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] || All working.<br />
|-<br />
|| Pandaboard+XFCE ||jcapik - SD || || || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA, maxam - HFP SD ||{{result|inprogress|pwhalen}} {{result|inprogress|maxam}} || || <br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|inprogress|bconoboy}} || || <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || agreene || {{result|inprogress|agreene}} || || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|warn|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292559Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T17:57:13Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold || ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| <br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD ||{{result|pass|pwhalen}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] || All working.<br />
|-<br />
|| Pandaboard+XFCE ||jcapik - SD || || || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA ||{{result|inprogress|pwhalen}} || || <br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|inprogress|bconoboy}} || || <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || || || || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|warn|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails], otherwise reasonable<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292558Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T17:56:17Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
* D. Marlin - dmarlin<br />
* Jon Masters - jonmasters<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || herrold || ||[[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-vexpress | vexpress Results ]]|| <br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||pwhalen - HFP ||{{result|inprogress|pwhalen}} ||[[Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-HFP-Versatile_Express+XFCE | HFP-Versatile_Express+XFCE Results]] ||<br />
|-<br />
|| Pandaboard ||pwhalen - SD ||{{result|pass|pwhalen}} ||[[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-Pandaboard-SD | Pandaboard SD Results]] || All working.<br />
|-<br />
|| Pandaboard+XFCE ||jcapik - SD || || || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || dmarlin -HFP SD || {{result|pass|dmarlin}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-TrimSlice-HFP-SD | TrimSlice HFP SD Results ]] || <br />
|-<br />
|| Trimslice Pro/H/H250 || pwhalen -SATA ||{{result|inprogress|pwhalen}} || || <br />
|-<br />
|| Highbank || bconoboy/dmarlin || {{result|inprogress|bconoboy}} || || <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || || || || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|warn|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || [http://fpaste.org/J4xd/ reboot/halt fails]<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM.txt <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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)<br />
#*Graphical user interfaces only: use the graphical package manager for your desktop (if applicable) to install zsh<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/messages<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292557Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T17:55:42Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxam}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|warn|maxam}} || [http://fpaste.org/7ewb/ unable to open rtc device, imx-sdma imx35-sdma: firmware not found]<br />
|-<br />
|| 6 ||{{result|warn|maxam}} || Boots to serial console, [http://fpaste.org/P9dz/ dma mismatch? still]<br />
|-<br />
|| 7 ||{{result|pass|maxam}} || http://mirror.chpc.utah.edu/pub/fedora-secondary/updates/17/armhfp/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates<br />
|-<br />
|| 8 ||{{result|pass|maxam}} || <br />
|-<br />
|| 9 ||{{result|fail|maxam}} || [http://fpaste.org/J4xd/ reboot/halt fails]<br />
|-<br />
|| 10 ||{{result|warn|maxam}} || [http://fpaste.org/Imf4/ Sound does not work on non GUI ... is it supposed to?]<br />
|-<br />
|| 11 ||{{result|pass|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292528Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T16:13:12Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxam}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|warn|maxam}} || [http://fpaste.org/7ewb/ unable to open rtc device, imx-sdma imx35-sdma: firmware not found]<br />
|-<br />
|| 6 ||{{result|warn|maxam}} || Boots to serial console, [http://fpaste.org/P9dz/ dma mismatch? still]<br />
|-<br />
|| 7 ||{{result|pass|maxam}} || http://mirror.chpc.utah.edu/pub/fedora-secondary/updates/17/armhfp/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates<br />
|-<br />
|| 8 ||{{result|pass|maxam}} || <br />
|-<br />
|| 9 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|pass|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292527Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T16:12:58Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxamaxim}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|warn|maxam}} || [http://fpaste.org/7ewb/ unable to open rtc device, imx-sdma imx35-sdma: firmware not found]<br />
|-<br />
|| 6 ||{{result|warn|maxam}} || Boots to serial console, [http://fpaste.org/P9dz/ dma mismatch? still]<br />
|-<br />
|| 7 ||{{result|pass|maxam}} || http://mirror.chpc.utah.edu/pub/fedora-secondary/updates/17/armhfp/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates<br />
|-<br />
|| 8 ||{{result|pass|maxam}} || <br />
|-<br />
|| 9 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|pass|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292525Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T16:11:49Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxamaxim}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|warn|maxam}} || [http://fpaste.org/7ewb/ unable to open rtc device, imx-sdma imx35-sdma: firmware not found]<br />
|-<br />
|| 6 ||{{result|warn|maxam}} || Boots to serial console, [http://fpaste.org/P9dz/ dma mismatch? still]<br />
|-<br />
|| 7 ||{{result|pass|maxam}} || http://mirror.chpc.utah.edu/pub/fedora-secondary/updates/17/armhfp/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates<br />
|-<br />
|| 8 ||{{result|pass|maxam}} || <br />
|-<br />
|| 9 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292522Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T16:06:38Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxamaxim}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|warn|maxam}} || [http://fpaste.org/7ewb/ unable to open rtc device, imx-sdma imx35-sdma: firmware not found]<br />
|-<br />
|| 6 ||{{result|warn|maxam}} || Boots to serial console, [http://fpaste.org/P9dz/ dma mismatch? still]<br />
|-<br />
|| 7 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 8 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 9 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292520Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T16:00:22Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxamaxim|max}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|unknown|maxam}} || [http://fpaste.org/7ewb/ unable to open rtc device, imx-sdma imx35-sdma: firmware not found]<br />
|-<br />
|| 6 ||{{result|pass|maxam}} || Boots to serial console, [http://fpaste.org/P9dz/ dma mismatch? still]<br />
|-<br />
|| 7 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 8 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 9 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292519Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T16:00:05Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxamaxim max}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|unknown|maxam}} || [http://fpaste.org/7ewb/ unable to open rtc device, imx-sdma imx35-sdma: firmware not found]<br />
|-<br />
|| 6 ||{{result|pass|maxam}} || Boots to serial console, [http://fpaste.org/P9dz/ dma mismatch? still]<br />
|-<br />
|| 7 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 8 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 9 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292518Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T15:57:07Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxam}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|unknown|maxam}} || [http://fpaste.org/7ewb/ unable to open rtc device, imx-sdma imx35-sdma: firmware not found]<br />
|-<br />
|| 6 ||{{result|pass|maxam}} || Boots to serial console, [http://fpaste.org/P9dz/ dma mismatch? still]<br />
|-<br />
|| 7 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 8 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 9 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292517Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T15:56:18Z<p>Maxamaxim: </p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxam}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|unknown|maxam}} || [ http://fpaste.org/7ewb/ unable to open rtc device, imx-sdma imx35-sdma: firmware not found ]<br />
|-<br />
|| 6 ||{{result|pass|maxam}} || Boots to serial console, [ http://fpaste.org/P9dz/ dma mismatch? still ]<br />
|-<br />
|| 7 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 8 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 9 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292505Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T15:38:48Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxam}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 4 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 5 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 6 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 7 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 8 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 9 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|inprogress|maxam}} || <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD&diff=292504Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-IMX-HFP-SD2012-06-18T15:37:00Z<p>Maxamaxim: /* IMX-HFP-SD */</p>
<hr />
<div>==IMX-HFP-SD==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 ||{{result|pass|maxam}} || <br />
|-<br />
|| 2 ||{{result|pass|maxam}} || <br />
|-<br />
|| 3 ||{{result|pass|maxam}} || <br />
|-<br />
|| 4 ||{{result|pass|maxam}} || <br />
|-<br />
|| 5 ||{{result|fail|maxam}} || [http://fpaste.org/dE4K/ Some sort of DMA issue]<br />
|-<br />
|| 6 ||{{result|pass|maxam}} || Boots to serial console <br />
|-<br />
|| 7 ||{{result|pass|maxam}} || <br />
|-<br />
|| 8 ||{{result|pass|maxam}} || <br />
|-<br />
|| 9 ||{{result|fail|maxam}} || [http://fpaste.org/K6PV/ Hangs during reboot]<br />
|-<br />
|| 10 ||n/a || <br />
|-<br />
|| 11 ||{{result|fail|maxam}} || No release notes <br />
|-<br />
|| 12 ||n/a ||<br />
|-<br />
|| 13 ||n/a ||<br />
|-<br />
|| 14 ||n/a ||<br />
|-<br />
|| 15 ||n/a ||<br />
|-<br />
|| 16 ||n/a ||<br />
|-<br />
|| 17 ||n/a ||<br />
|-<br />
|| 18 ||n/a ||<br />
|-<br />
|| 19 ||n/a ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC1]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292489Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T15:20:41Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || || || || <br />
|-<br />
|| Versatile Express+XFCE (Qemu) || || || ||<br />
|-<br />
|| Pandaboard || || || ||<br />
|-<br />
|| Pandaboard+XFCE || || || || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || || || || <br />
|-<br />
|| Trimslice Pro/H/H250 || || || || <br />
|-<br />
|| Highbank || || || || <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || || || || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || maxam - HFP SD ||{{result|inprogress|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day-IMX-HFP-SD | iMX HFP SD results ]] || <br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*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 <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day&diff=292486Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day2012-06-18T14:53:33Z<p>Maxamaxim: /* Participants */</p>
<hr />
<div>=Fedora ARM VFAD - Fedora 17 - RC2 =<br />
<br />
<br />
* When: Monday June 18th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. 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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* M A - maxam<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) || || || || <br />
|-<br />
|| Versatile Express+XFCE (Qemu) || || || ||<br />
|-<br />
|| Pandaboard || || || ||<br />
|-<br />
|| Pandaboard+XFCE || || || || <br />
|-<br />
|| Trimslice Bare/Value Pro/H/H250 || || || || <br />
|-<br />
|| Trimslice Pro/H/H250 || || || || <br />
|-<br />
|| Highbank || || || || <br />
|-<br />
|| Beagleboard XM || || || ||<br />
|-<br />
|| Kirkwood (sheevaplug, dreamplug, guruplug, etc) || || || || <br />
|- <br />
||Raspberry Pi+XFCE || || || || <br />
|-<br />
|| Raspberry Pi || || || || <br />
|-<br />
|| Efika SmartTop iMX || || || ||<br />
|}<br />
<br />
==Testing Template==<br />
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-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page. <br />
#Copy the below tests and results chart to a page that you create .<br />
#*Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#Graphical user interfaces only: Is it possible to run Firefox and a terminal application? <br />
#*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 <br />
#*Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)<br />
#*Log into FAS. <br />
#Graphical user interfaces only is the default Fedora artwork used? <br />
#*Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#Graphical user interfaces only: Is media automatically detected when inserted? <br />
#*Plug in a USB device or other removable media. Does the system automatically mount the device?<br />
#Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work? <br />
#*Use the GUI to logout, reboot and shutdown the system.<br />
#Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use? <br />
#*Does every button do what it is supposed to do? <br />
#*Do GUI actions align correctly with the pointer position?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}<br />
[[Category:Fedora ARM VFAD]][[Category:Fedora 17 ARM VFAD - RC2]]</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day&diff=292204Architectures/ARM/Quality Assurance/2012-06-15-VFAD-Fedora 17 Test Day2012-06-16T00:30:28Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Final push to F17 =<br />
<br />
<br />
* When: Friday June 15th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* Jon Masters - jonmasters<br />
* D. Marlin - dmarlin<br />
* Andrew Greene - agreene<br />
* M A - maxam<br />
* Luke Macken - lmacken<br />
* Brendan Conoboy - bconoboy<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) ||pwhalen - N/A ||{{result|fail|pwhalen}} || || Kernel oops on boot. Add 'physmap.enabled=0' fixes.<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||jonmasters - N/A ||{{result|fail|jonmasters}} || ||Kernel oops on boot. Add 'physmap.enabled=0' fixes. <br />
|-<br />
|| 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.<br />
|-<br />
|| 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.<br />
|-<br />
|| 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.<br />
|-<br />
|| Trimslice Pro/H/H250 || bconoboy - HD, satellit_-SD, maxam - HFP SD and HD || {{result|pass|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD and HD results ]] || YUM Update works but it has minor issues (Please see results page) and no release notes<br />
|-<br />
|| 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.<br />
|-<br />
|| 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)<br />
|-<br />
|| 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.<br />
|- || || ||<br />
|| 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...<br />
|-<br />
|| 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<br />
|-<br />
|| 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]<br />
|}<br />
<br />
==Testing Template==<br />
#Copy the below tests and results chart to a page that you create .<br />
#*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<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#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. <br />
#Graphical user interfaces only is the default Fedora artwork used? (Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png)<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#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?<br />
#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.<br />
#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?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-|| || ||<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-BBXM-SFP-SD&diff=292203Architectures/ARM/Quality Assurance/2012-06-15-VFAD-Fedora 17 Test Day-BBXM-SFP-SD2012-06-16T00:29:35Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || {{result|pass|maxam}} || <br />
|-<br />
|| 2 || {{result|pass|maxam}} || <br />
|-<br />
|| 3 || {{result|pass|maxam}} || <br />
|-<br />
|| 4 || {{result|fail|maxam}}{{result|pass|jcm}} || [http://fpaste.org/yWx1/ Link 1], [http://fpaste.org/BPAh/ Link 2], [http://fpaste.org/AZiI/ Link 3] Not sure if it is the board that has issues (Rev A2 Board won't work)<br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 ||{{result|fail|jcm}} || oopses on reboot at machine reset<br />
|-|| || ||<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-BBXM-SFP-SD&diff=292202Architectures/ARM/Quality Assurance/2012-06-15-VFAD-Fedora 17 Test Day-BBXM-SFP-SD2012-06-16T00:27:21Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || {{result|pass|maxam}} || <br />
|-<br />
|| 2 || {{result|pass|maxam}} || <br />
|-<br />
|| 3 || {{result|pass|maxam}} || <br />
|-<br />
|| 4 || {{result|fail|maxam}}{{result|fail|jcm}} || [http://fpaste.org/yWx1/ Link 1], [http://fpaste.org/BPAh/ Link 2], [http://fpaste.org/AZiI/ Link 3] Not sure if it is the board that has issues (Rev A2 Board won't work)<br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 ||{{result|fail|jcm}} || oopses on reboot at machine reset<br />
|-|| || ||<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day&diff=292187Architectures/ARM/Quality Assurance/2012-06-15-VFAD-Fedora 17 Test Day2012-06-15T23:13:56Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Final push to F17 =<br />
<br />
<br />
* When: Friday June 15th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* Jon Masters - jonmasters<br />
* D. Marlin - dmarlin<br />
* Andrew Greene - agreene<br />
* M A - maxam<br />
* Luke Macken - lmacken<br />
* Brendan Conoboy - bconoboy<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) ||pwhalen - N/A || || ||<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||jonmasters - N/A || || ||<br />
|-<br />
|| 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.<br />
|-<br />
|| 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.<br />
|-<br />
|| 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.<br />
|-<br />
|| Trimslice Pro/H/H250 || bconoboy - HD, satellit_-SD, maxam - HFP SD and HD || {{result|pass|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD and HD results ]] || YUM Update works but it has minor issues (Please see results page) and no release notes<br />
|-<br />
|| 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.<br />
|-<br />
|| Beagleboard XM ||jonmasters - SD , maxam - SFP SD || {{result|unknown|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-BBXM-SFP-SD | BBXM SFP SD results ]] || (Please see the results page)<br />
|-<br />
|| 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.<br />
|- || || ||<br />
|| 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...<br />
|-<br />
|| 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<br />
|-<br />
|| 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]<br />
|}<br />
<br />
==Testing Template==<br />
#Copy the below tests and results chart to a page that you create .<br />
#*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<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#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. <br />
#Graphical user interfaces only is the default Fedora artwork used? (Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png)<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#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?<br />
#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.<br />
#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?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-|| || ||<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-TrimslicePro-SD&diff=292185Architectures/ARM/Quality Assurance/2012-06-15-VFAD-Fedora 17 Test Day-TrimslicePro-SD2012-06-15T23:12:39Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || {{result|pass|maxam}} || <br />
|-<br />
|| 2 || {{result|pass|maxam}} || <br />
|-<br />
|| 3 || {{result|pass|maxam}} || <br />
|-<br />
|| 4 || {{result|pass|maxam}} || <br />
|-<br />
|| 5 || {{result|pass|maxam}} || [http://fpaste.org/O7cQ/ HFP Non GUI SD], [http://fpaste.org/G44v/ HFP Non GUI HD],[FAILED] Failed to start LSB: Bring up/down networking. Even after network was setup (after reboots)<br />
|-<br />
|| 6 || {{result|pass|maxam}} || Boots to serial<br />
|-<br />
|| 7 || {{result|pass|maxam}} || [http://fpaste.org/S0n3/ Why is it creating the new ones?] also ...http://mirror.chpc.utah.edu/pub/fedora-secondary/updates/17/armhfp/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates <br />
|-<br />
|| 8 || {{result|pass|maxam}} || <br />
|-<br />
|| 9 || {{result|pass|maxam}} || [http://fpaste.org/OdLL/ reboot works on SD] [http://fpaste.org/Tvqy/ reboot works on HD]<br />
|-<br />
|| 10 || n/a || <br />
|-<br />
|| 11 || {{result|fail|maxam}} || No release notes<br />
|-<br />
|| 12 || n/a ||<br />
|-<br />
|| 13 || n/a ||<br />
|-<br />
|| 14 || n/a ||<br />
|-<br />
|| 15 || n/a ||<br />
|-<br />
|| 16 || n/a ||<br />
|-<br />
|| 17 || n/a ||<br />
|-<br />
|| 18 || n/a ||<br />
|-<br />
|| 19 || n/a ||<br />
|}</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-TrimslicePro-SD&diff=292184Architectures/ARM/Quality Assurance/2012-06-15-VFAD-Fedora 17 Test Day-TrimslicePro-SD2012-06-15T23:09:14Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || {{result|pass|maxam}} || <br />
|-<br />
|| 2 || {{result|pass|maxam}} || <br />
|-<br />
|| 3 || {{result|pass|maxam}} || <br />
|-<br />
|| 4 || {{result|pass|maxam}} || <br />
|-<br />
|| 5 || {{result|pass|maxam}} || [http://fpaste.org/O7cQ/ HFP Non GUI SD], [http://fpaste.org/G44v/ HFP Non GUI HD],[FAILED] Failed to start LSB: Bring up/down networking. Even after network was setup (after reboots)<br />
|-<br />
|| 6 || {{result|pass|maxam}} || Boots to serial<br />
|-<br />
|| 7 || {{result|pass|maxam}} || [http://fpaste.org/S0n3/ Why is it creating the new ones?]<br />
|-<br />
|| 8 || {{result|pass|maxam}} || <br />
|-<br />
|| 9 || {{result|pass|maxam}} || [http://fpaste.org/OdLL/ reboot works on SD] [http://fpaste.org/Tvqy/ reboot works on HD]<br />
|-<br />
|| 10 || n/a || <br />
|-<br />
|| 11 || {{result|fail|maxam}} || No release notes<br />
|-<br />
|| 12 || n/a ||<br />
|-<br />
|| 13 || n/a ||<br />
|-<br />
|| 14 || n/a ||<br />
|-<br />
|| 15 || n/a ||<br />
|-<br />
|| 16 || n/a ||<br />
|-<br />
|| 17 || n/a ||<br />
|-<br />
|| 18 || n/a ||<br />
|-<br />
|| 19 || n/a ||<br />
|}</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day&diff=292182Architectures/ARM/Quality Assurance/2012-06-15-VFAD-Fedora 17 Test Day2012-06-15T22:56:59Z<p>Maxamaxim: /* Overall Test Results and Board Assignment */</p>
<hr />
<div>=Fedora ARM VFAD - Final push to F17 =<br />
<br />
<br />
* When: Friday June 15th at 12PM EDT<br />
* Where: #fedora-arm on Freednode<br />
<br />
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.<br />
==Participants==<br />
Please add your name, followed by your IRC nick:<br />
* Paul Whalen - pwhalen<br />
* Jon Masters - jonmasters<br />
* D. Marlin - dmarlin<br />
* Andrew Greene - agreene<br />
* M A - maxam<br />
* Luke Macken - lmacken<br />
* Brendan Conoboy - bconoboy<br />
<br />
===Test Instructions===<br />
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.<br />
<br />
==Overall Test Results and Board Assignment==<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Hardware !! Who's Testing !! Result !! Link to Results Page !! Final Notes <br />
|-<br />
|| Versatile Express (Qemu) ||pwhalen - N/A || || ||<br />
|-<br />
|| Versatile Express+XFCE (Qemu) ||jonmasters - N/A || || ||<br />
|-<br />
|| 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.<br />
|-<br />
|| 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.<br />
|-<br />
|| 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.<br />
|-<br />
|| Trimslice Pro/H/H250 || bconoboy - HD, satellit_-SD, maxam - HFP SD and HD || {{result|pass|maxam}} || [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-TrimslicePro-SD | TS Pro HFP SD and HD results ]] || No release notes<br />
|-<br />
|| 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.<br />
|-<br />
|| Beagleboard XM ||jonmasters - SD , maxam - SFP SD || {{result|unknown|maxam}} || [[ Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-BBXM-SFP-SD | BBXM SFP SD results ]] || (Please see the results page)<br />
|-<br />
|| 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.<br />
|- || || ||<br />
|| 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...<br />
|-<br />
|| 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<br />
|-<br />
|| 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]<br />
|}<br />
<br />
==Testing Template==<br />
#Copy the below tests and results chart to a page that you create .<br />
#*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<br />
#Does your downloaded image have the correct checksum?<br />
#*Run the command: sha256sum --check *CHECKSUM <br />
#Check the image size:<br />
#*xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB? <br />
#Copy the image to your SD card: <br />
#*xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot? <br />
#Do all default services start properly? <br />
#*Watch for service-start failure messages during boot.<br />
#Check the boot result:<br />
#*If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI? <br />
#*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)<br />
#Are you able to download and install updates with yum, and if available the default graphical package manager? <br />
#*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<br />
#Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.<br />
#*Test using the command: tail -f /var/log/message<br />
#Are you able to shutdown the system using standard console commands? <br />
#*Test poweroff or halt or reboot or shutdown -h now<br />
#If audio device support is present, does it work? <br />
#*Test with: play /usr/share/sounds/alsa/*wav<br />
#Are the final branded release notes from the Documentation team present on the installed media? <br />
#*Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry. <br />
#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. <br />
#Graphical user interfaces only is the default Fedora artwork used? (Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png)<br />
#Graphical user interfaces only: Are the desktop's panels working and fully functional? <br />
#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?<br />
#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.<br />
#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?<br />
#Graphical user interfaces only: Menu sanity:<br />
#*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 <br />
#*Do all applications listed under the Applications menu or category start successfully? <br />
#*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 <br />
#*Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications <br />
#Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?<br />
#*Create an ssh key: ssh-keygen # Use a passphrase<br />
#*Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted<br />
#*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)<br />
#*Log out.<br />
#*Log back in to the system.<br />
#*Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.<br />
<br />
===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || || <br />
|-<br />
|| 2 || || <br />
|-<br />
|| 3 || || <br />
|-<br />
|| 4 || || <br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-|| || ||<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}</div>Maxamaximhttps://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day-BBXM-SFP-SD&diff=292175Architectures/ARM/Quality Assurance/2012-06-15-VFAD-Fedora 17 Test Day-BBXM-SFP-SD2012-06-15T22:34:10Z<p>Maxamaxim: /* Results */</p>
<hr />
<div>===Results===<br />
{|class="wikimedia" style="t1" rowclass="th" width="100%"<br />
! Test !! Result !! Notes <br />
|-<br />
|| 1 || {{result|pass|maxam}} || <br />
|-<br />
|| 2 || {{result|pass|maxam}} || <br />
|-<br />
|| 3 || {{result|pass|maxam}} || <br />
|-<br />
|| 4 || {{result|fail|maxam}} || [http://fpaste.org/yWx1/ Link 1], [http://fpaste.org/BPAh/ Link 2], [http://fpaste.org/AZiI/ Link 3] Not sure if it is the board that has issues (Rev A2 Board won't work)<br />
|-<br />
|| 5 || || <br />
|-<br />
|| 6 || || <br />
|-<br />
|| 7 || || <br />
|-<br />
|| 8 || || <br />
|-<br />
|| 9 || || <br />
|-|| || ||<br />
|| 10 || || <br />
|-<br />
|| 11 || ||<br />
|-<br />
|| 12 || ||<br />
|-<br />
|| 13 || ||<br />
|-<br />
|| 14 || ||<br />
|-<br />
|| 15 || ||<br />
|-<br />
|| 16 || ||<br />
|-<br />
|| 17 || ||<br />
|-<br />
|| 18 || ||<br />
|-<br />
|| 19 || ||<br />
|}</div>Maxamaxim