From Fedora Project Wiki
Line 183: Line 183:
| [https://bugs.freedesktop.org/show_bug.cgi?id=20901 FAIL]
| [https://bugs.freedesktop.org/show_bug.cgi?id=20901 FAIL]
| PASS
| PASS
| N/A
| PASS
| N/A
| N/A
| i855GM
| i855GM

Revision as of 20:20, 10 September 2009

DATE TIME WHERE
Fri Sep 11, 2009 All day #fedora-test-day)

What to test?

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

Related feature pages:

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

  • 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

How to test?

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

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

Architecture MD5SUM
i686 4e09b55dcf898038d6959aa5893b3d35
x86_64 6b1b617a7dd1ef42ee0cbb9fcd14a162
Live USB label bug
If you put the image on a USB stick, boot will likely fail with the message No root device found. Boot has failed, sleeping forever. In this case, use the command /sbin/dosfslabel (if your USB stick is FAT32-formatted) or /sbin/e2label (ext2/3/4-formatted) to find the label for the USB stick. When booting, hit tab twice at the Fedora boot screen to edit the kernel boot parameters, and change the root= section to read root=live:LABEL=(label), where (label) is the label you found.

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.

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.

Results

User Smolt Profile Basic (KMS) Basic (no KMS) Multi-head DPMS DRI2/GLX Xv Fast user switch VT switch Suspend Comments
Sample user HW PASS PASS PASS PASS PASS PASS PASS PASS FAIL [1] i945 (0641)
  1. ↑ See RHBZ #XXXXXX
User:jjorge HW PASS N/A N/A PASS PASS PASS PASS PASS PASS i810 on 1GHz/256MB desktop
User:czhang HW FAIL [1] FAIL [2] N/A FAIL [3] N/A N/A N/A N/A N/A GMA950/945GM
  1. ↑ See RHBZ #522016
  2. ↑ See RHBZ #522016
  3. ↑ See RHBZ #522358
User:monreal HW PASS FAIL later FAIL [1] PASS PASS FAIL [2] PASS PASS GM965/GL960
  1. ↑ will file bug
  2. ↑ will file bug
User:orthob HW PASS PASS N/A FAIL [1] FAIL [2] PASS PASS PASS PASS Mobile 4 Chipset
  1. ↑ See RHBZ #522358
  2. ↑ See RHBZ #522360
User:micclass HW FAIL [1] FAIL [2] N/A FAIL [3] FAIL [4] FAIL [5] PASS PASS N/A i855GM
  1. ↑ modeset works, but comes up in textmode
  2. ↑ screen stays dark after boot
  3. ↑ no screensaver
  4. ↑ no 3D acceleration
  5. ↑ xv not working, See RHBZ #501435
Michal Nowak HW FAIL [1] FAIL [2] N/A FAIL [3] FAIL [4] FAIL PASS PASS N/A i855GM
  1. ↑ See RHBZ #522544
  2. ↑ See RHBZ #522551
  3. ↑ See RHBZ #522588
  4. ↑ See RHBZ #521461
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2009-09-11_Intel&oldid=123757"