Test Day:2010-09-29 Radeon

In other languages: English (en) русский (ru) [edit]

DATE	TIME	WHERE
Wed Sep 19, 2010	ALL DAY	#fedora-test-day

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 14, please wait for the next Radeon test day.

What to test?

Today's instalment of 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 - Adam Williamson (adamw)

What's needed to test

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

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

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

Architecture	SHA256SUM
i686	8443f115fd7d7fe1f25b29eb8ea167f1057db8e70149ce27fa6533a412094ee6
x86_64	067f1c5a5f53ff1bc2a8d3c6f484e7b99c00f4f4c350c1ba1ae6ac177a07b62b

Test

Follow each of these test cases:

• QA:Testcase_radeon_basic
• QA:Testcase_radeon_xvideo
• QA:Testcase_radeon_rotate
• QA:Testcase_radeon_restartx
• QA:Testcase_radeon_dpms
• QA:Testcase_radeon_glx (3D support for r600 and r700 cards - anything in the Radeon HD 2xxx, HD 3xxx, or HD 4xxx series - is quite experimental at this time, expect problems)
• QA:Testcase_radeon_fastuserswitch
• QA:Testcase_radeon_vt
• QA:Testcase_radeon_suspend
• QA:Testcase_radeon_rendercheck (requires 15 minutes)
• QA:Testcase_radeon_compositing_manager

Multihead test case:

• QA:Testcase_radeon_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_radeon_3D_pymol
• QA:Testcase_radeon_3D_avogadro
• QA:Testcase_radeon_3D_openarena
• QA:Testcase_radeon_3D_tuxracer
• QA:Testcase_radeon_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-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, 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 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	Rotation	X restart	DPMS	GLX	User switch	VT switch	Suspend	Rendercheck	Compositing	Multihead	Comments
Example user	HW	PASS	PASS	PASS	PASS	PASS	PASS	PASS	PASS	PASS	PASS	N/A	FAIL
Walter Justen	HW	PASS	FAIL										ATI RV610 Radeon HD 2400 XT
User	Smolt Profile	Basic test	XVideo	Rotation	X restart	DPMS	GLX	User switch	VT switch	Suspend	Rendercheck	Compositing	Multihead	Comments