Difference between revisions of "Archived:How to write good problem report"

From LinuxTVWiki
Jump to: navigation, search
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[http://robertopapenfus.isuisse.com/1298.htm free live web cam chat] [http://aleaserayo.ibelgique.com/ersitbocz.html airline american flight schedule timetable] [http://xiomarasobel.isuisse.com/2008-04-29-brazilian-shemale.html brazilian shemale pic gallery] [http://isadoraeidson.isuisse.com/st-sauveur-hotel.html st sauveur hotel] [http://cheriemershon.we.bs/page1207.html rohff clips videos]
Good problem report should include
Good problem report should include

Latest revision as of 03:06, 20 November 2008

Good problem report should include

0. Note that you are using V4L CVS.

1. Name of card

2. lspci -vn

3. Dmesg log of module tuning and probing. It also nice to add audio_debug options to modules, tuner_debug option to tuner module and debug option to tda9887

4. Television standard for your country.

5. Exact sequence of actions that causes your problem.

6. Generally, "your problem" is a combination of an app and a driver. Also generally, the problem only exists in one of those, but it isn't always easy to tell where. A big help is to check each part with various tools in the Test_Suite.