From Fedora Project Wiki

Revision as of 04:19, 24 February 2011 by Laputa (talk | contribs) (→‎Results)

DATE TIME WHERE
Thu Feb 24, 2011 All day #fedora-test-day)

What to test?

Today's 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 42, 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 42 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture SHA256SUM
i686 4553b73f8fab46fbb85384974decc7f9595e5c7af6df76e303cef5e62a76e07f
x86_64 e59d1886f7b766011b89d88369d09a4dd46bd7ba8a25664e9de0430d0f8725d7

Testing

Follow each of these test cases:

Multihead test case:

You will need two or more monitors to perform the multihead test.

Optional extended OpenGL test cases (some of these will require you to at least move around in games):

These will provide more detailed testing of 3D functionality. Please file bugs for any failures you find if running these tests.

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, use the result template to enter your result, as shown in the example result 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 test GNOME 3 start DPMS XVideo Rotation X restart Rendercheck GLX User switch VT switch Suspend Multihead Comments
Example user HW
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
N/A
Fail fail [1]
Warning warn [2]
  1. RHBZ #123456
  2. RHBZ #234567
Artur Szymczak HW
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
N/A N/A
kparal HW
Pass pass
Pass pass
Warning warn [1]
Pass pass
Pass pass
Warning warn
[2]
none
none
none
none
none
none
00:02.0 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
  1. RHBZ #582532
  2. I saw some Xserver traceback after logging out, but I am not able to reproduce it again.
ignotusp HW
Pass pass
Pass pass
Pass pass
Warning warn [1]
none
none
none
none
none
none
none
none
  1. RHBZ #675040
Matěj Cepl HW
Pass pass
Pass pass
Pass pass
Fail fail [1]
Pass pass
Pass pass
Pass pass
[2]
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
  1. RHBZ #679776
  2. [1]
I tested also pymol and mesa-demos w/o any issues
laputa HW
Pass pass
Pass pass
Pass pass
Pass pass
Warning warn [1]
Pass pass
Pass pass
[2]
Pass pass
Pass pass
Pass pass
Fail fail
Pass pass
  1. RHBZ #679990
  2. [2]
User Smolt Profile Basic test GNOME 3 start DPMS XVideo Rotation X restart Rendercheck GLX User switch VT switch Suspend Multihead Comments