Test Day:2013-04-25 Radeon

Click here to set up this language box

DATE	TIME	WHERE
2013-04-25	ALL DAY	#fedora-test-day	webchat

In construction
The Test Day page is yet in construction. It will be ready for the Test Day - when this message is removed :) .

Arriving after the date above?
If you come to this page after the test day is completed, your testing of Radeon is still valuable, and you can use the information on this page to test Radeon with your graphics card and provide feedback. If you are visiting after the release of Fedora 19, please wait for the next Radeon test day.

What to test?

Today's Fedora Test Day will focus on the radeon driver for ATI/AMD Radeon graphics cards.

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 - Dave Airlie (airlied), Jerome Glisse (jglisse)
• Quality Assurance - Martin Holec (Martix) UTC 10:00-18:00, Adam Williamson (adamw) UTC 16:00-00:00

What's needed to test

• An ATI Radeon (or FireGL) graphics adapter. To confirm whether you have supporting hardware, run the following command under root:

  /sbin/lspci -d 1002: | grep -iq VGA && echo "Join Radeon Fedora Test Day" || echo "Sorry, no Radeon graphics hardware found."

• An updated Fedora 19 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 19, 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 19 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture	SHA256SUM
[ x86_64]
[ i686]

Testing

Basic

Elementary functionality tests, which should pass on supported GPU.

• Boot
• Virtual Terminal
• X restart
• Rendercheck (can take some time to complete, from 10 minutes to an hour or two)
• GLX
• Mesa demos
• Suspend

Desktop

Basic desktop usage scenarios, which should pass on supported GPU.

• Gnome Shell
• KDE 4
• Screen rotation
• User switch
• Multihead You will need two or more monitors to perform the multihead test.

Video

Tests focused on different video playback acceleration features. Some older GPUs may not support XvBA.

• XVideo
• XVMC
• XvBA

3D applications/Games

Following applications has been carefully selected to test and exploit various OpenGL features using different rendering engines. If one applications test fails, next may work. Working HW 3D acceleration is needed.

• PyMOL
• Stellarium
• SuperTuxKart
• Xonotic
• VDrift
• 0 A.D.

Please file bugs for any failures you find if running these tests. But remember, crashes, rendering issues and glitches bugreports are more important then performance issues. Use your common sense and your knowledge about your GPU limits before reporting performance issues.

Experimental

Some recommended test cases for people, who likes trying new technology (Wayland, OpenCL) or who are interested in particular scenarios, eg. Steam, Wine.

• Hybrid graphics You will need a laptop with two GPUs. Intel and ATI (PowerXpress) or Intel and nVidia (Optimus).
• Steam
• WebGL
• Wine

Report your results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component xorg-x11-drv-ati. 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 from Example user 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 1002) 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 tests

User	Smolt Profile	Basic test	GNOME 3 start	KDE 4 effects	DPMS	XVideo	Rotation	X restart	Rendercheck	GLX	User switch	VT switch	Suspend	Multihead	Comments
Example user	RV516	pass	pass	pass	pass	pass	pass	pass	pass	pass	pass	N/A	fail	warn
User	Smolt Profile	Basic test	GNOME 3 start	KDE 4 effects	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	RV516	pass	pass	N/A	fail	warn
User	Smolt Profile	Pymol	Avogadro	OpenArena	Tux Racer	mesa-demos	Comments