Test Day:2009-09-11 Intel

What to test?
Today's instalment of Fedora Test Day will focus on the Intel graphics card driver.

Related feature pages:


 * Features/IntelKMS
 * Features/DRI2

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 - Dave Airlie, Kristian Høgsberg
 * Quality Assurance - Adam Williamson, James Laska

What's needed to test

 * An Intel graphics adapter (i810 or later, except GMA 500 / Poulsbo)
 * Rawhide (tips on installing Rawhide below), or the live CD available for this test day (again see below).
 * Remove your xorg.conf, unless you have a really good reason to have one.
 * Your hardware profile uploaded to Smolt according to these instructions

Update your machine
See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live Image
If you do not want to use an installed Rawhide system to test, you can use the latest Rawhide nightly live CD. Tips on using a live image are available at FedoraLiveCD.

Testing
Things to test, roughly in dependency order:

Perform each of the following test cases that you are able to with the resources available to you. Some of the tests depend on the others, so obviously if X fails to run with kernel mode setting for you, you will not be able meaningfully to test video playback or 3D application on top of KMS, for instance.


 * Basic test (KMS)
 * Basic test (no KMS)
 * Multi-head (requires multiple monitors)
 * DPMS
 * DRI2/GLX
 * Xv
 * Fast user switching
 * VT switching
 * Suspend / resume
 * Compositing Manager

Miscellaneous notes:


 * A minimal test that modesetting is working is to remove rhgb from the command line and add 3 to boot into text mode. If KMS works, you should have a text mode with a lot more character cells than the standard 80x25 and it will be a little slower.
 * We're interested in tests on laptops with docking stations, so if you have one, try the tests with it connected.
 * Make sure rhgb is in your kernel boot line.

Report your results
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. Once you have completed the tests, add your results to the Results table below, following the example results as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to your Smolt hardware profile (see above for a link with instructions on submitting your hardware profile to Smolt). For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, with a footnote indicator, and put a link to the bug report in the comments column (as in the example line). If you could not perform one test (for example, you cannot perform the more advanced tests because the basic one fails, or you cannot perform the multihead test as you have only one display), enter the word N/A. In the comments column, you can enter the model name and PCI device ID (vendor ID is usually 8086) of your card, if you know it - you can usually find this information in the output of the command lspci -nn.