[Ubuntu Wiki] Update of "DebuggingSoundProblems" by diwic

[Ubuntu Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The following page has been changed by diwic:
http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=57&rev2=58

------------------------------------------------------------------------------
  
  Running Ubuntu Karmic Koala (9.10)? [[https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats|First have a look at this list]] of the most common problems with sound in this release.
  
- 
- == Identifying your hardware ==
- If the output of {{{lspci}}} includes a line similar to {{{00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)}}} (a High Definition Audio device)
- 
- Please paste the output of the following command at the top of your bug description:
- 
- {{{
- find /proc/asound/card* -type f | grep codec | xargs grep "^Codec\|^Vendor Id\|^Subsystem Id\|^Revision Id" | grep -B2 -A1 $(lspci -nv | grep -A1 0403 | grep Subsystem | sed 's/://g' | awk '{ print $2 }')
- }}}
- 
- You should see output similar to:
- {{{
- /proc/asound/card0/codec#0:Codec: Realtek ALC883
- /proc/asound/card0/codec#0:Vendor Id: 0x10ec0883
- /proc/asound/card0/codec#0:Subsystem Id: 0x10438284
- /proc/asound/card0/codec#0:Revision Id: 0x100002
- }}}
- 
- If you are about to file a driver bug (e.g., absolutely no applications output sound, microphone does not work even after toggling nocap, speakers continue to emit sound after headphones have been inserted), and you think that you see a bug report that matches your symptoms, '''STOP''' and check the bug's attachments to see if these 4 bits of data match.  If all four match '''and''' the symptom matches, subscribe to the existing bug.  If '''any''' of the 4 data points disagree, you probably have found one of the myriad cases where many different bugs with different root causes that need different patches have the same symptom on the surface.  In which case: '''file a new bug.'''
  
  
  == Preliminary checks ==
@@ -96, +77 @@

  In general, no-sound/low-sound/headphone-no-sound/no auto-mute/etc. bugs should be:
   * Filed against the '''linux''' source package.
   * Add the '''kernel-sound''' tag
-  * '''Subscribe''' (do not assign) the Ubuntu-audio team
+  * '''Subscribe''' (do not assign) the '''Ubuntu-audio''' team (not the ubuntu-audio-dev team)
  
  Only assign bugs to the "alsa-driver" source package if the reporter is using the alsa-source binary package with module-assistant OR is requesting a blacklist or slots/index modification.
  
-  * Do not mark bugs as duplicates unless you're 100% sure that both the '''hardware''', '''software''', and '''symptom''' match exactly. Slightly different hardware very often requires slightly different fixes.
+  * Do not mark bugs as duplicates unless you're 100% sure that both the '''hardware''', '''software''', and '''symptom''' match exactly. Slightly different hardware very often requires slightly different fixes. If in doubt, file a new bug.
+ 
+ === Identifying your hardware ===
+ If the output of {{{lspci}}} includes a line similar to {{{00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)}}} (a High Definition Audio device)
+ 
+ Please paste the output of the following command at the top of your bug description:
+ 
+ {{{
+ find /proc/asound/card* -type f | grep codec | xargs grep "^Codec\|^Vendor Id\|^Subsystem Id\|^Revision Id" | grep -B2 -A1 $(lspci -nv | grep -A1 0403 | grep Subsystem | sed 's/://g' | awk '{ print $2 }')
+ }}}
+ 
+ You should see output similar to:
+ {{{
+ /proc/asound/card0/codec#0:Codec: Realtek ALC883
+ /proc/asound/card0/codec#0:Vendor Id: 0x10ec0883
+ /proc/asound/card0/codec#0:Subsystem Id: 0x10438284
+ /proc/asound/card0/codec#0:Revision Id: 0x100002
+ }}}
+ 
+ If you are about to file a driver bug (e.g., absolutely no applications output sound, microphone does not work even after toggling nocap, speakers continue to emit sound after headphones have been inserted), and you think that you see a bug report that matches your symptoms, '''STOP''' and check the bug's attachments to see if these 4 bits of data match.  If all four match '''and''' the symptom matches, subscribe to the existing bug.  If '''any''' of the 4 data points disagree, you probably have found one of the myriad cases where many different bugs with different root causes that need different patches have the same symptom on the surface.  In which case: '''file a new bug.'''
+ 
+ 
  
  = Further sound troubleshooting =