From Fedora Project Wiki

(Created page with "{{autolang|base=yes}} {|border="1" |-style="color: white; background-color: #3074c2; font-weight: bold" | DATE || TIME || WHERE || |- | 2013-10-23 || ALL DAY || [irc://irc.fr...")
 
(minor f20 updates, will try and use results app next)
Line 7: Line 7:
 
|-
 
|-
 
|}
 
|}
 
{{admon/note | Want to run this test day? | This test day is in need of someone to coordinate it. This page is merely a copy of the F19 Test Day wiki page so the data might not be accurate. However, most of the test cases should be valid for F20. More accurate information will be posted as we get closer to the actual test day.}}
 
  
 
== What to test? ==
 
== What to test? ==
Line 25: Line 23:
  
 
* An ATI Radeon (or FireGL) graphics adapter.  To confirm whether you have supporting hardware, run the following command under root: <pre>/sbin/lspci -d 1002: | grep -iq VGA && echo "Join Radeon Fedora Test Day" || echo "Sorry, no Radeon graphics hardware found."</pre>
 
* An ATI Radeon (or FireGL) graphics adapter.  To confirm whether you have supporting hardware, run the following command under root: <pre>/sbin/lspci -d 1002: | grep -iq VGA && echo "Join Radeon Fedora Test Day" || echo "Sorry, no Radeon graphics hardware found."</pre>
* An updated [http://alt.fedoraproject.org/pub/alt/nightly-composes/ Fedora 19 pre-release], or the special live image (see [[Test Day:2012-09-19_Radeon#Live_image|below]])
+
* An updated [http://alt.fedoraproject.org/pub/alt/nightly-composes/ Fedora 20 pre-release], or the special live image (see [[Test Day:2013-10-23_Graphics_Radeon#Live_image|below]])
  
 
== How to test? ==
 
== How to test? ==
Line 31: Line 29:
 
=== '''Update your machine''' ===
 
=== '''Update your machine''' ===
  
If you're running Fedora 19, make sure you have all the current updates for it installed, using the update manager. Or you can use a live image:
+
If you're running Fedora 20, make sure you have all the current updates for it installed, using the update manager (and with the updates-testing repository enabled). Or you can use a live image:
  
 
=== '''Live image''' ===
 
=== '''Live image''' ===
  
Optionally, you may download a non-destructive Fedora 19 live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].
+
Optionally, you may download a non-destructive Fedora 20 live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].
  
 
{|
 
{|
Line 100: Line 98:
 
=== Report your results ===
 
=== Report your results ===
  
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=19&component=xorg-x11-drv-ati 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 [[Xorg/Debugging|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 the model of your graphics adapter. 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 <tt>lspci -nn</tt>.
+
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=20&component=xorg-x11-drv-ati 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 [[Xorg/Debugging|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 the model of your graphics adapter. 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 <tt>lspci -nn</tt>.
  
 
== Results ==
 
== Results ==

Revision as of 20:38, 18 October 2013

DATE TIME WHERE
2013-10-23 ALL DAY #fedora-test-day webchat

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 -
  • Quality Assurance -

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 20 pre-release, or the special live image (see below)

How to test?

Update your machine

If you're running Fedora 20, make sure you have all the current updates for it installed, using the update manager (and with the updates-testing repository enabled). Or you can use a live image:

Live image

Optionally, you may download a non-destructive Fedora 20 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture SHA256SUM

Testing

Basic

Elementary functionality tests, which should pass on supported GPU.

Desktop

Basic desktop usage scenarios, which should pass on supported GPU.

Video

Tests focused on different video playback acceleration features. Some older GPUs may not support XvBA.

3D applications/Games

Following applications has been carefully selected to test and exploit various OpenGL features using different rendering engines. If one applications test fails, next may work. Working HW 3D acceleration is needed.

Please file bugs for any failures you find if running these tests. But remember, crashes, rendering issues and glitches bugreports are more important then performance issues. Use your common sense and your knowledge about your GPU limits before reporting performance issues.

Experimental

Some recommended test cases for people, who likes trying new technology (Wayland, OpenCL) or who are interested in particular scenarios, eg. Steam, Wine.

  • Hybrid graphics You will need a laptop with two GPUs. Intel and ATI (PowerXpress) or Intel and nVidia (Optimus).
  • Steam
  • WebGL
  • Wine - Install 'wine' and try to play your favorite game. Important: Always check if your game is supported, visit: http://appdb.winehq.org Lot of bugs are actually Wine bugs, not related to GPU drivers, so be careful

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 the model of your graphics adapter. 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

Note.png
Long notes
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.

Basic

User Graphics card Boot Virtual Terminal X restart Rendercheck GLX Mesa demos Suspend Comments
Example user HD 3000
Pass pass
Pass pass
Pass pass
Pass pass
N/A
Fail fail [1]
Warning warn [2]
  1. RHBZ #123456
  2. RHBZ #234567
User Graphics card Boot Virtual Terminal X restart Rendercheck GLX Mesa demos Suspend Comments

Desktop

User Graphics card Gnome Shell KDE 4 Screen rotation User switch Multihead Comments
Example user HD 3000
Pass pass
Pass pass
N/A
Fail fail [1]
Warning warn [2]
  1. RHBZ #123456
  2. RHBZ #234567
User Graphics card Gnome Shell KDE 4 Screen rotation User switch Multihead Comments

Video

User Graphics card XVideo XVMC VA-API Comments
Example user HD 3000
Pass pass
Fail fail [1]
Warning warn [2]
  1. RHBZ #123456
  2. RHBZ #234567
User Graphics card XVideo XVMC VA-API Comments

3D Applications/Games

User Graphics card PyMOL Stellarium SuperTuxKart Xonotic VDrift 0 A.D. Comments
Example user HD 3000
Pass pass
Pass pass
Pass pass
N/A
Fail fail [1]
Warning warn [2]
  1. RHBZ #123456
  2. RHBZ #234567
User Graphics card PyMOL Stellarium SuperTuxKart Xonotic VDrift 0 A.D. Comments

Experimental

User Graphics card Hybrid graphics Steam WebGL Wine Comments
Example user HD 3000
Pass pass
N/A
Fail fail [1]
Warning warn [2]
  1. RHBZ #123456
  2. RHBZ #234567
User Graphics card Hybrid graphics Steam WebGL Wine Comments