From Fedora Project Wiki

Revision as of 10:35, 16 September 2009 by Mnowak (talk | contribs) (Results)

Wed September 16, 2009 ALL DAY #fedora-test-day (webirc)

What to test?

Today's instalment of Fedora Test Day will focus on sound, including PulseAudio.

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 system and provide feedback.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

What's needed to test

  • A system with some kind of sound card
  • Rawhide (tips on installing Rawhide below), or the live CD available for this test day (again see below)
  • Your sound hardware information uploaded using the alsa-info command: enter y when asked if you want to upload ALSA information to

How to test?

Update your machine

See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live Image

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

Live USB label bug
If you put the image on a USB stick, boot will likely fail with the message No root device found. Boot has failed, sleeping forever. In this case, use the command /sbin/dosfslabel (if your USB stick is FAT32-formatted) or /sbin/e2label (ext2/3/4-formatted) to find the label for the USB stick. When booting, hit tab twice at the Fedora boot screen to edit the kernel boot parameters, and change the root= section to read root=live:LABEL=(label), where (label) is the label you found. In some cases, you may simply need to use the label provided by udev, so if your key normally mounts as /media/KINGSTON, for example, use KINGSTON as the label.
Architecture md5sum
i686 77aeb59bedc8d41e140baf62611ab05f
x86-64 a0fd785614af00a423966fcfc9120c41


Follow each of these test cases that are possible with the hardware you have available:

Report your results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component kernel or PulseAudio. Please follow the debugging and diagnosis steps here (kernel drivers) and here (PulseAudio) before filing your report, as they will help you provide a much more complete and useful bug report. If you are unsure about exactly how to file the report or what information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line 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 sound hardware profile (see above for a link with instructions on submitting your sound hardware profile). 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 References column (as in the example line). For tests you could not perform, enter a dash.

fixme: there is no info in above links about how to upload a hardware profile


User Hardware profile Basic test Volume control Profiles Input References
Example user HW PASS PASS FAIL[1] PASS
Michal Nowak HW1
Michal Nowak HW2 PASS
Kamil Paral HW