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

+

* [[QA:Testcase_intelvideo_basic]]

+

* [[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)

* A minimal test that modesetting is working is to remove <tt>rhgb</tt> from the command line and add <tt>3</tt> 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.

+

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

−

* We're interested in tests on laptops with docking stations, so if you have one, try the tests with it connected.

How to test?

Update your machine

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

Broken images Please do not use the x86-64 image with the sha256sum 067f1c5a5f53ff1bc2a8d3c6f484e7b99c00f4f4c350c1ba1ae6ac177a07b62b which was available on this page until 2010-09-28. It is broken. We apologize for the inconvenience. Please use the rebuilt image with the sha256sum 624ed21266aa75f2eb4949967a342970d5efcf5b842654ced8f5a2570147af63.

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.

Intel GMA 3100: All tests were ok, The compositing one had a little problem, nothing to worry about (When the compositing was activated, Gnome's top panel dissapeared and after clicking sometimes in the blank space it reappeared) As additional information I want to add that the computer has F13 Installed but I used the F14 Live CD to make the tests, also I believe it's important to mention that in KDE i can't have fully transparent panels or good performance of the Kwin Effects (Computer goes slow when enabling them) and in VMWare Player I can't run Windows 7 with Aero because as Vmware says "The system doesn't have 3D Graphics Support" or something like that. These KDE Problems are not present in other distros I've been trying out with the same machine (Kubuntu, Mandriva, OpenSUSE) Just to mention ones... P.S. I wasn't able to start Gnome Shell.

↑After the graphical boot loader screen ("Automatic boot in X seconds..."), the screen switches into low-res text mode with a gray background for 1-2 seconds, then to a high-res text mode with a black background for 1-2 seconds, and then into the graphical animated screen. I would not call this flicker-free (especially the gray background yields a very noticeable flicker).

↑I run this test twice, once with a beamer, then with an LCD display as second display (primary display was the laptop screen). With the beamer, it automatically displayed the same contents on both screens (in gnome-display-properties, the screens were on top of each other), which is nice if you have to give a talk. However, after I moved one of the two screens, the two screens showed different contents and I could not restore the original situation where the two screens showed the same content. With the LCD screen, I did not succeed in having both screens display the same content. Also, I could not make the top panel move to the other screen - it always displayed on the second LCD screen.

↑There is no name in the top-right corner. Instead, I switched users by using the menu: System -> Log out liveuser -> Switch user. So I am not sure whether this is "fast" user switching, but graphically speaking, everything worked fine.

↑Apart from the fact that the graphical desktop was on ctrl-alt-f7, this worked fine.

↑The system is generally unstable after resume (various things fail in non-reproducible ways: when playing a movie, sound doesn't come back or the video image is frozen; sometimes I get many squashfs IO errors and things don't run anymore). But the graphics seem to work OK.