Test Day:2011-02-23 Radeon: Difference between revisions

Revision as of 23:31, 22 February 2011

In other languages: English (en) русский (ru) [edit]

DATE	TIME	WHERE
Wed Feb 23, 2011	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 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...

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

Architecture	SHA256SUM
i686	4553b73f8fab46fbb85384974decc7f9595e5c7af6df76e303cef5e62a76e07f
x86_64	e59d1886f7b766011b89d88369d09a4dd46bd7ba8a25664e9de0430d0f8725d7

Testing

Follow each of these test cases:

QA:Testcase_radeon_basic
QA:Testcase_radeon_gnome3 - ALL Radeon cards should support Shell: if you get fallback mode, please report the test as warn and file a bug
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:

QA:Testcase_radeon_multihead

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	fail ^[1]	warn ^[2]	↑ RHBZ #123456 ↑ RHBZ #234567
User:Jose Jorge	HW	pass	pass	pass	pass	pass	pass	pass	fail ^[1]	pass	N/A	fail ^[2]	warn ^[3]	↑ RHBZ #segfault ↑ RHBZ #123456 ↑ RHBZ #234567
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
Reinout van Schouwen	HW
User	Smolt Profile	Basic test	GNOME 3 start	DPMS	XVideo	Rotation	X restart	Rendercheck	GLX	User switch	VT switch	Suspend	Multihead	Comments

[bz123456-1] RHBZ #123456

[bz234567-2] RHBZ #234567

[bzsegfault-3] RHBZ #segfault

[bz123456-4] RHBZ #123456

[bz234567-5] RHBZ #234567

[6] Artifacts (Non-persistent black horiz. lines)

[7] Blank screen, I can't do anything then, reboot forced.

[8] renderchecklog.gz

[9] GNOME Shell starts and runs, but misrenders nearly everything.

[10] Color corruption outside of the video rectangle

[1]

[2]

[1]

[2]

[3]

[1]

[2]

[3]

[1]

[2]

@@ Line 180: / Line 180: @@
 |
 |
+| <references/>
+|-
+| [[User:reinouts | Reinout van Schouwen]]
+| [http://www.smolts.org/client/show/pub_1598bd36-7ad3-49c7-973f-e9e1e4af67b0 HW]
+|
+|
+|
+|
+|
+|
+|
+|
+|
+|
+|
+|
 | <references/>
 |-

Search