Test Day:2010-09-30 Intel

From FedoraProject

Revision as of 16:29, 28 September 2010 by Dcbw (Talk | contribs)

Jump to: navigation, search
Thu Sep 30, 2010 All day #fedora-test-day)


What to test?

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

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...

What's needed to test

How to test?

Update your machine

If you're running Fedora 22, make sure you have all the current updates for it installed, using the update manager. Or you can use a live image:

Live image

Optionally, you may download a non-destructive Fedora 22 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture SHA256SUM
i686 8443f115fd7d7fe1f25b29eb8ea167f1057db8e70149ce27fa6533a412094ee6
x86_64 067f1c5a5f53ff1bc2a8d3c6f484e7b99c00f4f4c350c1ba1ae6ac177a07b62b


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. In particular, X will not work without KMS anymore (well, the vesa driver will work, but that's not what we're testing here).

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.


User Smolt Profile Basic (KMS) Multi head DPMS DRI2/GLX Xv Fast user switch VT switch Suspend Compositing Comments
Sample user HW PASS PASS PASS PASS PASS PASS PASS FAIL [1] i945 (0641)
diverse_izzue HW PASS FAIL [1] [2] PASS PASS PASS PASS PASS Mobile 4 Series (2a43)
  1. See RHBZ #638123
  2. See RHBZ #638124
User Smolt Profile Basic (KMS) Multi head DPMS DRI2/GLX Xv Fast user switch VT switch Suspend Compositing Comments