Test Day:2009-03-12

What to test?
Today's instalment of Fedora Test Day will focus on the Intel graphics card driver. F11 brings a big update to intel graphics for everything in the graphics stack. We're shipping the new kernel memory manager, GEM, kernel modesetting, DRI2, graphical boot (plymouth) integrating with X, screen hotplugging, GLX1.4 and GL framebuffer objects, better fast user switching (multiple X servers can use DRI). There's a lot of new code and it's all turned on by default, so theres a lot of detail and integration work that needs to be done.

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). Note that the Intel X driver was recently renamed from xorg-x11-drv-i810 to xorg-x11-drv-intel.


 * Remove your xorg.conf, unless you have a really good reason to have one. The Virtual line that was required for working multihead in F10 is no longer necessary and may cause problems - please remove it if you have one.


 * FAS Account - you can create an account in 3 minutes if you don't 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.

Live Image
Optionally, you may download a non-destructive rawhide live image for your architecture:
 * i386
 * x86_64

Tips on using a live image are available at FedoraLiveCD.

Note: Creating a LiveUSB of this rawhide image requires the latest version of syslinux, which is currently available in Rawhide and in the latest Windows liveusb-creator. Users of F10 and below can `yum --enablerepo=rawhide update syslinux`

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

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.
 * Plymouth on dualhead gives interesting results, typically black borders on one or both displays. Plymouth cheat-codes: Ctrl-T goes to text mode, Ctrl-V enables verbose mode.
 * 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.
 * If you get to a point where GDM doesn't seem to work right and when you check from a console, there's 5 X processes running - reboot with your ethernet cable unplugged.

Report your results
Once you have completed the tests, add your results to the Results table below, following the example results from Adam Williamson 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 any failures, enter the word FAIL, as a link to the bug report for the failure. If you could not meaningfully run the test due to limitations of your system or because of failures in more basic functionality, 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.