| DATE | TIME | WHERE |
| Wed Apr 14, 2010 | ALL DAY | #fedora-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 41 pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
- Your hardware profile uploaded to Smolt according to these instructions
How to test?
Update your machine
If you're running Fedora 41, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, 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 Fedora 41 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
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)
Multihead test case:
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 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 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, 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 test | Rotation 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 | PASS | N/A | FAIL [1] | |
| User | Smolt Profile | Basic test | XVideo test | Rotation test | X restart test | DPMS test | GLX test | User switch test | VT switch test | Suspend test | Rendercheck test | Multihead test | Comments |