From Fedora Project Wiki

(What to test?)
(What to test?)
Line 9: Line 9:
 
== What to test? ==
 
== What to test? ==
  
Today's instalment of Fedora Test Day will focus on the
+
Today's instalment of Fedora Test Day will focus on the MDraid
  
 
== Who's available ==
 
== Who's available ==

Revision as of 16:42, 29 September 2009

DATE TIME WHERE
Thu Sep 10, 2009 ALL DAY #fedora-test-day)

What to test?

Today's instalment of Fedora Test Day will focus on the MDraid

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 NVIDIA graphics adapter. To confirm whether you have supporting hardware, run the following command:
    /sbin/lspci -d 10de: | grep -iq VGA && echo "Join Nouveau Fedora Test Day" || echo "No nVidia graphics hardware found." 
  • Rawhide (tips on installing Rawhide below), or the live CD available for this test day (again see below).
  • Your hardware profile uploaded to Smolt according to these instructions
  • Make sure to back up your existing xorg.conf file, if you have one, so you can recover if the nouveau driver causes you trouble

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

If you do not want to use an installed Rawhide system to test, you can use the latest Rawhide nightly live CD. Tips on using a live image are available at FedoraLiveCD.

Warning.png
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.
Note.png
If you have a slightly older Test Day Live image
This tip may be useful if you have a very recent Live image from a previous test day.

If you are a Fedora account holder, you can use rsync over SSH to update your existing ISO image in just a few minutes. First, cd to the directory containing your existing ISO image file. Then change its file name to testday-20090909-(arch).iso and run this command:

rsync -Pv fedorapeople.org:/home/fedora/adamwill/public_html/20090909_test_day_images/testday-20090909-(arch).iso .

Test

Follow each of these test cases:

Multihead test case:

You will need two or more monitors to perform the multihead test.

Report your results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component xorg-x11-drv-nouveau. 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 Adam Williamson 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 10DE) of your card, if you know it - you can usually find this information in the output of the command lspci -nn.

Results