| DATE | TIME | WHERE | |
| Wed Sep 07, 2011 | ALL DAY | #fedora-test-day | webchat |
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 16, 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 - 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 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 16 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 16, 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 16 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
| Architecture | SHA256SUM |
|---|---|
| i686 | 1d235e29f013db7d85277086a3eb11be81a8b690ddcd16c5f46d2dfbcdd12b83 |
| x86_64 | bdb309a42f99ba1c6221c85912960e4aebe82596fdd2d9027a41f16275d6fa74 |
Testing
Follow each of these test cases:
- QA:Testcase_radeon_basic
- QA:Testcase_radeon_gnome3 - ALL Radeon cards from the Radeon 9500 onwards should support Shell: if you get fallback mode, please report the test as warn and file a bug. Radeon 9200 and earlier cards do not fully support the Shell and use the fallback mode by design
- QA:Testcase_radeon_dpms
- QA:Testcase_radeon_xv
- QA:Testcase_radeon_rotate
- QA:Testcase_radeon_restartx
- QA:Testcase_radeon_rendercheck (can take some time to complete, from 10 minutes to an hour or two)
- QA:Testcase_radeon_glx
- QA:Testcase_radeon_fastuserswitch
- QA:Testcase_radeon_vt
- QA:Testcase_radeon_suspend
Multihead test case:
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, 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
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 | DPMS | XVideo | Rotation | X restart | Rendercheck | GLX | User switch | VT switch | Suspend | Multihead | Comments |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Example user | HW |  |
|
|
|
|
|
|
|
|
N/A | |||
| bruce89 | HW | |
|
|
|
|
 |
 |
|
|
|
|
N/A |
|
| User | Smolt Profile | Basic test | GNOME 3 start | 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 | HW | |
|
N/A | |||
| User | Smolt Profile | Pymol | Avogadro | OpenArena | Tux Racer | mesa-demos | Comments |