Test Day:2013-10-22 Graphics Intel

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(improve the link format)
(add x86_64 mini live, others to come)
Line 33: Line 33:
 
=== '''Live image''' ===
 
=== '''Live image''' ===
  
Optionally, you may download a non-destructive Fedora 20 live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].
+
Optionally, you may download a non-destructive Fedora 20 live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. The 'mini' images contain everything you need for most tests, but not the advanced 3D tests. The 'maxi' images contain all the games and apps for the advanced 3D tests as well.
  
 
{|
 
{|
 
! Architecture !! SHA256SUM  
 
! Architecture !! SHA256SUM  
 
|-  
 
|-  
| ||
+
| [http://fedorapeople.org/groups/qa/201310-Graphics_Test-mini-x86_64.iso x86_64 mini] || 2837ff4f8ccb4bcb72a13f4d9f9b90480a9e571f52891f5361b40d46f53142ae
 
|}
 
|}
  

Revision as of 00:50, 22 October 2013

DATE TIME WHERE
2013-10-22 ALL DAY #fedora-test-day webchat

Contents

What to test?

Today's Fedora Test Day will focus on the intel driver for Intel graphics cards.

If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test with your graphics card and provide feedback.

Who's available

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion...

  • Development -
  • Quality Assurance -

What's needed to test

  • An Intel graphics adapter. To confirm whether you have supporting hardware, run the following command:
    /sbin/lspci -d 8086: | grep -iq VGA && echo "Join Intel Fedora Test Day" || echo "Sorry, no Intel graphics hardware found."
  • An updated Fedora 20 pre-release, or the special live image (see below)

How to test?

Update your machine

If you're running Fedora 20, make sure you have all the current updates for it installed, using the update manager (and with the updates-testing repository enabled). Or you can use a live image:

Live image

Optionally, you may download a non-destructive Fedora 20 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. The 'mini' images contain everything you need for most tests, but not the advanced 3D tests. The 'maxi' images contain all the games and apps for the advanced 3D tests as well.

Architecture SHA256SUM
x86_64 mini 2837ff4f8ccb4bcb72a13f4d9f9b90480a9e571f52891f5361b40d46f53142ae

Testing and reporting results

The testing page provides a list of the tests to run, and lets you report your results. Clicking on a test name will show you the instructions for doing that test, and clicking 'Enter result' will let you enter your result for that test. For the Hardware name, please enter the model number for your graphics adapter as precisely as you can. You can use the lspci -nn command to provide the PCI ID, if you are comfortable doing so.

Don't feel obliged to complete all the tests! They are listed in approximate order of importance, so if you only have time to do a few, start with the first section and work your way down. It's fine to skip any tests you can't complete, or aren't sure you understand - or you can ask in IRC for help.

If you have problems with any of the tests, report a bug to Bugzilla, usually for the component xorg-x11-drv-intel. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Follow the instructions on this page to ensure you include sufficient information in the report.

Basic tests are elementary functionality tests, expected to pass on all supported adapters. Desktop tests cover key desktop functions and again should work on all supported adapters. Video tests cover video playback: some functions may not be supported on older adapters. 3D tests cover more advanced 3D functionality; some more advanced tests may fail on hardware that is not yet fully supported. Crashes, rendering issues and glitches bugreports are more important then performance issues. Experimental tests cover more unusual and experimental functionality.