Test Day:2009-04-01 Radeon

DATE	TIME	WHERE
Wed April 1, 2009	ALL DAY	#fedora-qa)

What to test?

Today's instalment of Fedora Test Day will focus on the radeon driver for ATI 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)
• Quality Assurance - Adam Williamson (adamw)

What's needed to test

• An ATI Radeon (or FireGL) graphics adapter.
• Rawhide (tips on installing Rawhide below), or the live CD available for this test day (again see below).
• FAS Account - you can create an account in 3 minutes if you don't 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
i386	551ca2636525dbf5a3530115cde634ee
x86_64	b0f87f300b83bf4baee86819fae1eaed

Latest syslinux package?
Creating a LiveUSB of this rawhide image requires the latest version of syslinux, which is currently available in Rawhide and in the latest Windows liveusb-creator. Users of F10 and below can upgrade to the latest syslinux package using

yum --enablerepo=rawhide update syslinux

.

Test

Follow each of these test cases:

• QA:Testcase_radeon_basic
• QA:Testcase_radeon_xvideo
• QA:Testcase_radeon_restartx
• QA:Testcase_radeon_dpms
• QA:Testcase_radeon_glx
• QA:Testcase_radeon_fastuserswitch
• QA:Testcase_radeon_vt
• QA:Testcase_radeon_suspend
• QA:Testcase_radeon_rendercheck (requires 15 minutes)

Multihead test case:

• QA:Testcase_radeon_multihead

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

Report your results

If you have problems with any of the tests, report a bug to Bugzilla. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from Adam Williamson 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, as a link to the bug report for the failure. 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

User	Smolt Profile	Basic test	XVideo test	X restart test	DPMS test	GLX test	User switch test	VT switch test	Suspend test	Rendercheck test	Multihead test	Comments
Example user	HW	PASS	PASS	PASS	PASS	PASS	PASS	PASS	PASS	N/A	FAIL
Jerry Amundson	HW	tbd	tbd	tbd	tbd	tbd	tbd	tbd	tbd	tbd	N/A
User	Smolt Profile	Basic test	XVideo test	X restart test	DPMS test	GLX test	User switch test	VT switch test	Suspend test	Rendercheck test	Multihead test	Comments