From Fedora Project Wiki
Line 182: Line 182:
| N/A
| N/A
| Radeon X1650 XT
| Radeon X1650 XT
|-
| [[User:Example | Example user]]
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
| PASS
| PASS
| PASS
| PASS
| PASS
| PASS
| PASS
| PASS
| PASS
| PASS
| N/A
| FAIL <ref>See {{bz|XXXXXX}}</ref>
| <references/>
|-
|-
| nphilipp
| nphilipp

Revision as of 19:09, 29 September 2010

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...

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 42 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 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.

Broken images
Please do not use the x86-64 image with the sha256sum 067f1c5a5f53ff1bc2a8d3c6f484e7b99c00f4f4c350c1ba1ae6ac177a07b62b which was available on this page until 2010-09-28. It is broken. We apologize for the inconvenience. Please use the rebuilt image with the sha256sum 624ed21266aa75f2eb4949967a342970d5efcf5b842654ced8f5a2570147af63.
Architecture SHA256SUM
i686 aef08e5186201aa5d8aef92a6d7cabe659b8f60ced16a34d6c756a3fbeb9bd3d
x86_64 624ed21266aa75f2eb4949967a342970d5efcf5b842654ced8f5a2570147af63

Test

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, 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 [1]
  1. ↑ See RHBZ #XXXXXX
David Ramsey [ HW] TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD [1]
  1. ↑ See RHBZ #XXXXXX
Jonathan Mercier HW PASS PASS PASS PASS PASS PASS PASS PASS FAIL need a hardreboot PASS File:Renderchecklog.tar.xz PASS PASS ATI Technologies Inc RV730XT [Radeon HD 4670]
Walter Justen HW PASS PASS PASS PASS PASS PASS PASS PASS PASS PASS File:Walt renderchecklog.gz PASS N/A Dell Optiplex 760, ATI RV610 Radeon HD 2400 XT
Jaromír Mikeš HW PASS PASS PASS PASS PASS PASS PASS PASS PASS PASS PASS N/A Radeon X1650 XT
nphilipp HW PASS PASS PASS PASS PASS PASS PASS PASS PASS PASS File:Renderchecklog-nphilipp-x100e.gz PASS N/A
Vpv HW PASS PASS PASS PASS PASS PASS PASS PASS PASS PASS File:Renderchecklog-vpv-radeon.gz PASS N/A
mhlavink HD4570 PASS PASS PASS PASS PASS PASS PASS PASS PASS PASS 99.2 % File:Renderchecklog-ati-mhlavink.gz PASS N/A fbo_firecube crashes RHBZ #638646. tunnel2 freezes system RHBZ #638680
mcloaked HW PASS PASS PASS startx gave normal session. When logging out back to console a whole slew of messages - killswitch 0 is KILLSWITCH_STATE_UNBLOCKED,Failed to play sound: File or data not found, (gnome-settings-daemon:1617): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion format != NULL failed, Window manage warning: Got a request to focus the no_focus_window with a timestamp of 0. This should not happen!, and later X10: fatal IO error 11 (resource temporarily unavailable) on X server :0.0. after 126 requests (126 known processed) with 0 events remaining. After that doing startx again seemed to start the X session normally, however. PASS PASS PASS PASS Suspend worked. Resume failed to restore wireless connection, and trying to switch off desktop effects failed. Then in a terminal trying "less /var/log/messages" gave "segmentation fault" so no BZ reported. Also ABRT failed to work. Then shutdown failed so had to hard reset. Started test again with no desktop effects enabled - system did suspend and appeared to resume with wireless connection re-established. However doing yum install compiz-gnome at that point in a terminal gave "-bash: /usr/bin/yum: Input/output error" - so suspend is broken for this system. src transform coordinates test failed + mask transform coordinates test failed File:Renderchecklog-ati-mc.gz PASS N/A ATI Technologies Inc M22 [Radeon Mobility X300] [1002:5460]
dmitriychernyy HW PASS PASS PASS PASS PASS PASS PASS PASS PASS Renderchecklog.gz PASS N/A Laptop Asus F3Sr (Radeon HD2400)
dmitriychernyy HW PASS FAIL FAIL PASS PASS FAIL N/A PASS FAIL Renderchecklog.gz N/A N/A Radeon 5770
Fl@sh HW PASS PASS PASS PASS PASS PASS PASS PASS PASS File:Renderchecklog-flAsh.gz PASS N/A ATI Technologies Inc Mobility Radeon HD 2400
Anatoliy HW PASS PASS PASS FAULT Can't start X session from the console.It shows information about starting the process and then system is freezes so i had to hard reset PASS PASS PASS PASS PASS PASS Sorry, I'm not able to upload file yet PASS N/A ATI Technologies Inc RV370 [Sapphire X550 Silent] [1002:5b63]
User Smolt Profile Basic test XVideo Rotation X restart DPMS GLX User switch VT switch Suspend Rendercheck Compositing Multihead Comments
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2010-09-29_Radeon&oldid=199830"