[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 "DebuggingSoundProblems" page has been changed by diwic:
http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=67&rev2=68

Comment:
Move information that is old and outdated to DebuggingSoundProblems/OldAndOutdated

  
   1. Is your sound system plugged in and switched on?  I spent an hour trying to diagnose a sound issue when the problem was that I had switched off the speakers to answer a phone call and forgot that I had done so. :-(
  
-  2. Is your speaker or microphone muted? Check here:
+  1. Is your speaker or microphone muted? Check here:
     * [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]]
     * [[Audio/CheckForMutedMicrophone|Check for muted microphone]]
  
- == Checking volume levels ==
+ = Advanced troubleshooting =
  
- Before messing around with uninstalling and installing various sound programs to fix a problem, check your volume levels.  It is often the case that a muted channel is the problem, even though the description may not sound immediately relevant.  In this regard, muted Surround or Center channels are common culprits. So unmute and raise the volume of one channel at a time and check whether sound is then produced by a running sound application e.g. Banshee.
+ If the basic troubleshooting does not help, here are some additional things to try. However, when trying these steps, remember where you were so you can easily go back in case something goes wrong. Also, should you ever need to do anything in this section for your sound to work (for a new installation), you should report a bug using "ubuntu-bug audio". 
  
+  1. For mixer problems, you can try controlling the [[Audio/Alsamixer|mixers at ALSA level]].
- You can access the volume levels for the various channels from the command line or the GUI.
- 
-  1. From command line:  Open a terminal window and launch ''alsamixer''.  Then unmute as described above.
-   * Note: Often you need to specify the card you want to control, do that by launching ''alsamixer -c0'' or ''alsamixer -c1'' etc, where the number after ''-c'' corresponds to your soundcard's index. To know what indexes your soundcards have, see below (under "Checking sound device assignment").
- 
-  1. From GUI:  This can be done by running something like ''gnome-alsamixer'' from a terminal window or navigating to your your Volume Control.  Then unmute as described above.  Also check that your switches are set correctly - for instance that if you use the analog output the analog switch is set ON or that the digital or S/PDIF switch is set OFF. You can select which tracks/switches are visible in Volume Control (see above) under Edit->Preferences.
-   * Note: These controls have equivalent functionality to alsamixer but with a graphical interface.  Checking or unchecking devices in the these accomplishes the exact same thing as unmuting or muting devices, respectively, in alsamixer.
-   * The sound volume control is also accessible from Menu->Sound&Video->Volume Control. It may be hidden in your menus but can be shown by going to System > Preferences > Main Menu and under Applications > Sound&Video ticking Volume Control.
- 
- == Checking sound device assignment ==
- 
-  1. Most sound applications output to card0 by default. In some cases, other audio devices (like a USB MIDI Keyboard) might be recognized as a soundcard and take card0, bumping your real soundcard to card1.  To see which devices are connected to which cards, do the following: 
-   * {{{
-  cat /proc/asound/cards
- }}} 
-  1. You can manipulate the device number assignment by adding modifying /etc/modprobe.d/sound.conf (create it if necessary). Next boot, the snd-usb-audio device will get index 1 (by default it will be 2).
-   * {{{
-  options snd slots=,snd-usb-audio
- }}}
- The index numbers (0, 1, ... 7) signify the priority of the device, with the highest priority device being 0, then 1, and so forth.  In theory, applications should first attempt to use the highest priority device first, but if for some reason the application is unable to use the device, it will use the next highest priority device.  For example, if you have a USB sound card that can get picked up with OSS, which browsers, flash, and skype may not output, if you set your USB card at first priority, it will play when using, say, Banshee, but your other applications will play through your other soundcard.  For more information see Documentation/sound/alsa/ALSA-Configuration.txt in the kernel source.
- 
- == Checking permissions and resources ==
- 
-   1. Make sure that all users needing access to the Sound Device can "Use audio devices" in the "User Privileges" tab of users-admin (System->Administration->Users and Groups).
-   1. Test different "Sound Servers": Go to System > Preferences > Sound ("Multimedia Systems Selector" in earlier editions of Ubuntu). From there, you can test the different options. In some scenarios several different sound servers may be installed, and only one may work. This is probably the origin of the problem if you cannot play audio with xine or rhythmbox, but you can with xmms or helix/realplayer. 
-   1. If the application sounds work, but the system sounds do not (login, logout, error sounds...) try removing the .asoundrc* files from your own directory (e.g. with 'rm .asoundrc*'). It should make the system sounds work without a reboot.
-   1. If you can get absolutely no sound and you have an onboard sound chip you can try to disable it in the BIOS. This solves the problem is some cases.
-   1. If you have no sound and you have a regular sound card type "lsmod | grep snd" in the terminal and see if there is more than one card listed.  It's possible that you have a motherboard sound chip that is interfering.  Add it to the bottom of the blacklist file.  For example, sudo nano /etc/modprobe.d/blacklist then add "blacklist snd_via82xx" to the bottom. 
  
  = Reporting Sound Bugs =
  
  Please do not report problems on this page; use the normal support channels instead.  See http://www.ubuntu.com/support
  
- If you feel you have encountered a software bug, the way to report it varies between versions.
+ If you feel you have encountered a software bug, the way to report it is to run the following terminal command:
- Run the following terminal command:
  {{{
  ubuntu-bug audio
  }}}
@@ -80, +52 @@

  
  [[Audio/SameHardware|Here's an article]] of how to determine whether you have the same hardware as the original bug reporter.
  
- = Further sound troubleshooting =
- 
- After reporting a bug you might want to see the community documentation:
- 
-  * https://help.ubuntu.com/community/SoundTroubleshootingProcedure
-  * https://help.ubuntu.com/community/Sound
-  * https://help.ubuntu.com/community/SoundTroubleshooting
-  * https://help.ubuntu.com/community/DebuggingSoundProblemsMisc
- 
  ----
  CategoryDocumentation  CategoryBugSquad CategoryDebugging