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 15, 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...
What's needed to test
How to test?
Update your machine
If you're running Fedora 42, 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 42 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
Architecture |
SHA256SUM
|
i686 |
4553b73f8fab46fbb85384974decc7f9595e5c7af6df76e303cef5e62a76e07f
|
x86_64 |
e59d1886f7b766011b89d88369d09a4dd46bd7ba8a25664e9de0430d0f8725d7
|
Testing
Follow each of these test cases:
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):
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
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
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
N/A
|
|
|
|
Jorge
|
HW
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
|
pass
|
N/A
|
|
|
|
Faelar
|
HW
|
warn [1]
|
pass
|
pass
|
pass
|
fail [2]
|
pass
|
pass [3]
|
pass
|
pass
|
pass
|
N/A
|
N/A
|
- ↑ Artifacts (Non-persistent black horiz. lines)
- ↑ Blank screen, I can't do anything then, reboot forced.
- ↑ renderchecklog.gz
|
NJM
|
HW
|
pass
|
fail [1]
|
pass
|
fail [2]
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
N/A
|
- ↑ GNOME Shell starts and runs, but misrenders nearly everything.
- ↑ Color corruption outside of the video rectangle
RHBZ: 679579
Several mesa-demo apps misrender. RHBZ: 679588
|
Jaroslav Pulchart
|
HW
|
pass
|
pass
|
pass
|
pass
|
pass
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
inprogress
|
|
Reinout van Schouwen
|
HW
|
pass
|
pass
|
pass
|
pass
|
pass
|
|
fail [1]
|
pass [2]
|
|
pass
|
|
|
|
Jordan Clarke
|
HW
|
pass
|
pass
|
pass
|
pass
|
pass
|
|
|
pass
|
|
pass
|
|
|
|
MahMahoritos
|
HW
|
pass
|
[2]
|
pass
|
pass
|
pass
|
[3]
|
pass [4]
|
pass
|
fail [5]
|
warn [6]
|
fail [7]
|
warn [8]
|
- ↑ 1.0 1.1 RHBZ #679685
- ↑ Gnome Shell doesn't start
- ↑ Second startx make Gnome Shell working
- ↑ http://www.fpaste.org/LjZa/
- ↑ Can't switch users without Gnome Shell, only log out option available
- ↑ Can't switch back to Gnome, Ctrl+Alt+F1 craches system at all
- ↑ System sleeps (pm-suspend), then wakes up, but I can't run any programm and 'su' in terminal doesn't work
- ↑ HDMI hotplug (after log in) doesn't work at all; if HDMI is connected before system starts, then everything works fine, every display supports its native resolution
|
Philip V
|
HW[1]
|
[3]
|
fail
|
warn [4]
|
warn
|
fail
|
N/A
|
pass [5]
|
pass
|
N/A
|
N/A
|
fail [6]
|
[8]
|
- ↑ 01:00.0 [0300]: ATI RV280 [Radeon 9200 PRO] [1002:5960] (rev 01)
01:00.1 [0380]: ATI RV280 [Radeon 9200 PRO] (Secondary) [1002:5940] (rev 01)
Dual head did work in Fedora 13.
- ↑ RHBZ #679674
- ↑ The default boot always gets stuck immediately. 'Boot Basic Video' succeeds. Not sure how to report the rest of these tests as testcases assume no 'nomodeset'; 'Boot Basic Video' uses 'nomodeset'.
- ↑ All warnings mean: only works with the forbidden 'nomodeset'/'Boot Basic Video'.
- ↑ https://fedoraproject.org/w/uploads/c/c3/Renderchecklog_RV280.txt
- ↑ Resume after Suspend from Login Screen has dead keyboard and Mouse
- ↑ RHBZ #653803
- ↑ xrandr only sees one monitor with 0Hz refresh rate
|
MadRouter
|
HW
|
pass
|
warn [1]
|
pass
|
pass
|
pass
|
pass
|
pass [2]
|
pass
|
pass [3]
|
pass
|
warn [4]
|
pass
|
- ↑ gnome shell does not start after first boot, start successfully after next boots
- ↑ File:Radeon renderchecklog madrouter.gz
- ↑ work fine from gnome 3 shell, N/A from gnome desktop
- ↑ shut down instead of suspend from gnome 3 shell, but work fine from gnome desktop
|
dbkblk
|
HW
|
pass
|
warn [1]
|
pass
|
pass
|
pass
|
pass
|
warn [2]
|
pass
|
warn [3]
|
warn [4]
|
warn [5]
|
N/A
|
- ↑ Gnome shell does not start after first boot (fallback mode), start successfully when logout > login. OK with "gnome-shell --replace".
- ↑ 44 steps/46. [1](Didn't understood how to upload it here)
- ↑ The switch worked but when i log out the 2nd user, it fall back into the 1st user session and not gdm !!
Moreover, the insight of the overlay window show 3 same nautilus thumbnails instead of the correct thumbnails.
- ↑ Works, but unusable because a message keep showing each second: “[random numbers...] hub 1-0:1.0 Unable to enumerate USB device on port 2“
- ↑ Works with “pm-suspend” but the suspend menu of gnome 3 shut down the computer instead of suspending it.
|
Wyatt Gosling
|
HW
|
warn [1]
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass [2]
|
pass
|
pass
|
pass
|
pass
|
warn [3]
|
- ↑ Artifacts between Plymouth and login screens.
- ↑ only 44 of 46 passed. [2]
- ↑ xrardr output [3]. Login screen chose correct screen as primary, but the session did not. Gnome 3's config tool did not provide a means to fix this. Physically unplugging the display was required for desired behavior.
|
Mira
|
HW
|
pass
|
warn [1]
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
fail [2]
|
N/A
|
- ↑ Always after 1st log-in Gnome in fallback mode, after log-out log-in Gnome shell started
- ↑ System didn't suspend successfully, it just simply switched off
|
geopan
|
HW
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
inprogress [1]
|
pass
|
pass
|
pass
|
pass
|
N/A multihead
|
- ↑ only 44 of 46 passed, but was unable to upload renderchecklog
|
lersek
|
FIXME add link later [1]
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
fail [2]
|
pass [3]
|
pass
|
pass
|
warn [4]
|
N/A
|
- ↑ For lack of a better place, I'll put here the results of the 3D tests I tried:
- pymol: I had to set gpgcheck=0 so that I could install it. Functionality was okay, but it was extremely slow.
- avogadro: tried to build C2H6, the program crashed multiple times with std::bad_alloc. 1.2 GB of RAM was still free.
- openarena: during the first installation with yum, the optical drive started thrashing and the system froze stiff. The second installation (after reboot) completed. I started the program and immediately selected "exit" from the main menu. This crashed my X server and all programs connected to it; I had to re-login.
- tuxracer: functionality was okay, no flicker, no crash. I added "display FPS" to the default settings. In 1920x1200, the refresh rate was steadily below 15 fps. (Probably weak hardware.)
- mesa-demos: bounce was okay, but fbo_firecube exited immediately with SIGBUS, and then any program I touched (ls, ps, firefox) immediately died with EIO. The system became unusable and I had to power it down forcibly.
The OpenGL renderer string was each time Gallium 0.4 on AMD RS880. Summary: 2D works extremely well, but I think I can't use 3D for anything serious.
Sometime during the tests "prelink" started to thrash the CD in the background, without me starting it, and when it completed or stopped, the system crashed. This is a separate (earlier) case than the openarena case above.
- ↑ 44 tests passed of 46 total [4].
- ↑ glxgears synced to monitor refresh rate, 60Hz.
- ↑ Desktop machine powered off completely.
|
Spiro
|
SAPPHIRE Radeon 5850
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass
|
N/A
|
|
Ivo Anjo
|
HW
|
pass
|
pass
|
pass
|
fail
|
pass
|
pass
|
pass [1]
|
pass
|
pass
|
pass
|
pass
|
pass
|
|
Vlads
|
HW
|
pass
|
pass
|
pass
|
pass
|
pass
|
pass [1]
|
pass
|
pass
|
N/A
|
pass
|
warning [2]
|
N/A
|
|
User
|
Smolt Profile
|
Basic test
|
GNOME 3 start
|
DPMS
|
XVideo
|
Rotation
|
X restart
|
Rendercheck
|
GLX
|
User switch
|
VT switch
|
Suspend
|
Multihead
|
Comments
|