Test Day:2011-09-08 Intel

Click here to set up this language box

DATE	TIME	WHERE
Thu Sep 08, 2011	All day	#fedora-test-day	webchat

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

• Development - Adam Jackson (ajax)
• Quality Assurance - Adam Williamson (adamw)

What's needed to test

• An Intel graphics adapter (i810 or later, except GMA 500 / Poulsbo)
• An updated Fedora 16 pre-release, or the special live image (see below)
• Your hardware profile uploaded to Smolt according to these instructions

How to test?

Update your machine

If you're running Fedora 16, 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 16 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture	SHA256SUM
i686	1d235e29f013db7d85277086a3eb11be81a8b690ddcd16c5f46d2dfbcdd12b83
x86_64	bdb309a42f99ba1c6221c85912960e4aebe82596fdd2d9027a41f16275d6fa74

Testing

Follow each of these test cases:

• QA:Testcase_intelvideo_basic
• QA:Testcase_intelvideo_gnome3 - ALL i9xx and later adapters should support Shell in most configurations: if you get fallback mode, please report the test as warn and file a bug. i8xx adapters do not support Shell fully and use the fallback mode by design. Early i9xx adapters (up to i945) will not support Shell if the combined resolution of all displays exceeds 2048 in any axis
• QA:Testcase_intelvideo_dpms
• QA:Testcase_intelvideo_xv
• QA:Testcase_intelvideo_rotate
• QA:Testcase_intelvideo_restartx
• QA:Testcase_intelvideo_rendercheck (can take some time to complete, from 10 minutes to an hour or two)
• QA:Testcase_intelvideo_glx
• QA:Testcase_intelvideo_fastuserswitch
• QA:Testcase_intelvideo_vt
• QA:Testcase_intelvideo_suspend

Multihead test case:

• QA:Testcase_intelvideo_multihead

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):

• QA:Testcase_intelvideo_3D_pymol
• QA:Testcase_intelvideo_3D_avogadro
• QA:Testcase_intelvideo_3D_openarena - NOTE: we do not recommend running this test when booted live, live boot 'installs' into a RAM disk and the space requirements for the game will likely exhaust your available RAM
• QA:Testcase_intelvideo_3D_tuxracer
• QA:Testcase_intelvideo_3D_mesa-demos

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

Long notes
Please try to avoid leaving long comments in the table, it makes it difficult to read. If you need to explain an issue in detail, please file a bug, and link to the bug.

Main 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	N/A	fail	warn
lintweaker	[1]	pass	pass	pass	pass	pass	fail get fallback mode	pass [2]	pass	fail	pass	pass	warn
satellit_	Atom N450; live i686	pass	pass	pass			fail init 3 hung on text firstboot (no console)				N/A
kparal	HW	pass	pass	pass	pass	pass	fail	pass [3]	warn	fail	pass	pass	pass
Horst H. von Brand	Netbook	pass	pass	pass	pass	pass	N/A	fail	pass	N/A	pass	pass	N/A
mam	HP dc7900	pass	pass	pass	pass	pass	fail	pass [4]	pass	fail	pass	pass	N/A
User:Piksi	X201 Tablet
Rob Sharp	Lenovo X220	pass	pass	pass	pass	pass		pass [5]	pass	fail	pass	pass	N/A
Ivan	dell mini	pass	pass	pass		pass	fail		pass	fail	pass	pass	N/A
User:Rmarko	Lenovo X200	pass	pass	pass	pass	pass	fail	pass [6]	pass	fail	pass	pass	pass
qux	HW	pass	pass	pass	pass	pass	fail	pass log	pass	warn gnome either crashes with 'oh no!' or freezes with artefacts while continuous switching between users with video and glxgears running at each. Maybe general performance issue, also observed at other machine with nouveau driver	warn	pass	N/A	Common: some artifacts present, like unrendered areas in gnome-terminal while windows switching until pressing 'enter'
User	Smolt Profile	Basic test	GNOME 3 start	DPMS	XVideo	Rotation	X restart	Rendercheck	GLX	User switch	VT switch	Suspend	Multihead	Comments

Extended 3D tests

User	Smolt Profile	Pymol	Avogadro	OpenArena	Tux Racer	mesa-demos	Comments
Example user	HW	pass	pass	N/A	fail	warn
kparal	HW	pass	pass	fail	warn
djuran	HW				pass	pass
User:Rmarko	Lenovo X200	pass	pass	warn	warn	pass
User	Smolt Profile	Pymol	Avogadro	OpenArena	Tux Racer	mesa-demos	Comments