DebuggingSoundProblems
|
Size: 4980
Comment: imported from the old wiki
|
Size: 7748
Comment: Karmic is EOL, don't link to sound fixes for it
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = DebuggingSoundProblems = | #### do not move or rename as the Ubuntu Bug Control team uses this page extensively #### #title Debugging Sound Problems <<Include(Debugging/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>|| |
| Line 3: | Line 6: |
| Do not report problems on this page; use the normal support channels. | = Basic troubleshooting = |
| Line 5: | Line 8: |
| * Check that sound is unmuted and that the volume is turned up * I found it hard to find these controls: its not the "sound" in preferences; click on panel; add to panel; volume controls; speaker icon appears on panel; left click on icon; preferences; played around here and it worked |
Running Lucid (10.04) or later? There is a troubleshooter that checks for some of the most common problems. Open a Terminal (Program -> Accessories -> Terminal), then enter this command: {{{ ubuntu-bug audio }}} |
| Line 8: | Line 13: |
| * Most sound problems are the result of failed hardware detection, so see DebuggingHardwareDetection * When reporting a problem, include (in addition to the information requested in DebuggingHardwareDetection): * Output of `aplay -l` |
== Preliminary checks == |
| Line 12: | Line 15: |
| 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. :-( | |
| Line 13: | Line 17: |
| == Contributed by Carl Karsten == | 2. Is your speaker or microphone muted? Check here (9.10 and later) : * [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]] * [[Audio/CheckForMutedMicrophone|Check for muted microphone]] |
| Line 15: | Line 21: |
| Here are the commands and web sites I found helpful in getting sound working. | == Checking volume levels == |
| Line 17: | Line 23: |
| carl@ubuntu:~$ aplay -l | 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. Rhythmbox. |
| Line 19: | Line 25: |
| aplay: device_list:200: no soundcards found... | You can access the volume levels for the various channels from the command line or the GUI. |
| Line 21: | Line 27: |
| Script to gather specs about sound things: http://alsa.opensrc.org/index.php?page=aadebug |
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"). |
| Line 24: | Line 30: |
| To try to figure out what sound card (chip set) you have: | 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. * Starting with Ubuntu 7.04, 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. |
| Line 26: | Line 34: |
| $ lspci -v and lspnp -v, look for lines like this: | == Checking sound device assignment == |
| Line 28: | Line 36: |
| 0000:01:05.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) | 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, Rhythmbox, but your other applications will play through your other soundcard. For more information see Documentation/sound/alsa/ALSA-Configuration.txt in the kernel source. |
| Line 30: | Line 46: |
| or | == Checking permissions and resources == |
| Line 32: | Line 48: |
| 06 ESS1878 multimedia controller: audio | 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. |
| Line 34: | Line 54: |
| “A word about compatibility: even though most sound cards are claimed to be SoundBlaster compatible, very few currently sold cards are compatible enough to work with the Linux SoundBlaster driver. “ - http://www.tldp.org/HOWTO/Sound-HOWTO/x96.html#AEN120 | = Reporting Sound Bugs = |
| Line 36: | Line 56: |
| If you have an ISA card, you MUST pass isapnp=0 to modprobe. | Please do not report problems on this page; use the normal support channels instead. See http://www.ubuntu.com/support |
| Line 38: | Line 58: |
| If you have an ISA card, you may need to get the IRQ and IO ranges. IRQ 5, DMA channel 1 and 0, IO 0x0220-0x022f, 0x0388-0x0388, 0x0330-0x0331 |
If you feel you have encountered a software bug, the way to report it varies between versions. For Ubuntu Lucid Lynx (10.04) and later, run the following terminal command: {{{ ubuntu-bug audio }}} |
| Line 41: | Line 64: |
| Now figure out which module you need. | For Ubuntu Karmic (9.10), run the following terminal command: {{{ ubuntu-bug -p alsa-base }}} |
| Line 43: | Line 69: |
| http://www.alsa-project.org/alsa-doc/ | This will submit a detailed bug report with information about your current system. |
| Line 45: | Line 71: |
| Pick the manufacturer, Go – This should make it clear what module you need. | For older versions, or if the above fails for some reason, you can file a bug report, then upload alsa-info information [[Audio/AlsaInfo|according to these instructions]]. |
| Line 47: | Line 73: |
| http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=ESS+Technology&card=.&chip=ES18xx&module=es18xx | == Triaging sound bugs == |
| Line 49: | Line 75: |
| snd-es18xx | 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 (not the ubuntu-audio-dev team) |
| Line 51: | Line 80: |
| Between that, modinfo <module>, and linux/Documentation/sound/alsa/ALSA-Configuration.txt: | 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. |
| Line 53: | Line 82: |
| Module snd-es18xx | * 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. |
| Line 55: | Line 84: |
| Module for ESS AudioDrive ES-18xx soundcards. | [[Audio/SameHardware|Here's an article]] of how to determine whether you have the same hardware as the original bug reporter. |
| Line 57: | Line 86: |
| port - port # for ES-18xx chip (0x220,0x240,0x260) mpu_port - port # for MPU-401 port (0x300,0x310,0x320,0x330), -1 = disable (default) fm_port - port # for FM (optional, not used) irq - IRQ # for ES-18xx chip (5,7,9,10) dma1 - first DMA # for ES-18xx chip (0,1,3) dma2 - first DMA # for ES-18xx chip (0,1,3) isapnp - ISA PnP detection - 0 = disable, 1 = enable (default) |
= Further sound troubleshooting = |
| Line 65: | Line 88: |
| Module supports up to 8 cards ISA PnP and autoprobe (without MPU-401 port if native ISA PnP routines are not used). When dma2 is equal with dma1, the driver works as half-duplex. |
After reporting a bug you might want to see the community documentation: |
| Line 69: | Line 90: |
| The power-management is supported. You should be able to figure out a line like this: sudo modprobe snd_es18xx isapnp=0 port=0x220 mpu_port=0x330 dma1=1 dma2=5 irq=5 fm_port=0x388 Hopefully no errors. If so, save the parameters root@ubuntu:/etc # cat /etc/modprobe.conf alias sound-card-0 snd-es18xx options snd-es18xx isapnp=0 port=0x220 mpu_port=0x330 dma1=1 dma2=5 irq=5 fm_port=0x388 This works, but has an alarming side effect: on boot I saw "warning! /etc/modprobe.conf exists but does not include /etc/rc.modules" (or something... it scrolled off and I can't find it in dmesg or messages... where should I look?) So I am guessing there is a better pace to put module parameters. == Revised by DanielTChen == Use /etc/modprobe.d/<module name> instead, e.g., $ echo "options snd-es18xx isapnp=0 port=0x220 mpu_port=0x330 dma1=1 dma2=5 irq=5 fm_port=0x388" | sudo tee -a /etc/modprobe.d/snd-es18xx == root@ubuntu:/etc # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: ES1878 [ESS AudioDrive ES1878], device 0: ES1878 [ESS AudioDrive ES1878] Subdevices: 1/1 Subdevice #0: subdevice #0 /usr/bin/speaker-test (beep...) Hoary - I have sound with aplay, speaker-test and xmms, but not flash-mozilla firefox plugin crimsun: carl: you can create an .asoundrc and overload pcm.dsp0 (never got any more on this tip) == Revised by DanielTChen == The recommended method is to use the polypaudio daemon (esd replacement) and to leave/set applications to use ESounD output. See the Sound section in /usr/share/doc/mozilla-firefox/README.Debian |
* https://help.ubuntu.com/community/SoundTroubleshootingProcedure * https://help.ubuntu.com/community/Sound * https://help.ubuntu.com/community/SoundTroubleshooting * https://help.ubuntu.com/community/DebuggingSoundProblemsMisc |
| Line 110: | Line 96: |
| A problem is the default config is OSS doesn't let 2 apps make sound at the same time. Here is a report of how it was dealt with: Basically get esd to relinquish control of the sound when its not in use. Then add mixing for oss so you can use multiple oss programs at once, like Quake3 and Teamspeak, or in my case, Wolfenstein and Teamspeak First use section 3 here: http://www.ubuntulinux.org/wiki/RestrictedFormats, then do this: http://alsa.opensrc.org/index.php?page=DmixPlugin ---- Handy links: http://alsa.opensrc.org/index.php?page=OssEmulation |
CategoryDocumentation CategoryBugSquad CategoryDebugging |
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Basic troubleshooting
Running Lucid (10.04) or later? There is a troubleshooter that checks for some of the most common problems. Open a Terminal (Program -> Accessories -> Terminal), then enter this command:
ubuntu-bug audio
Preliminary checks
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.
- Is your speaker or microphone muted? Check here (9.10 and later) :
Checking volume levels
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. Rhythmbox.
You can access the volume levels for the various channels from the command line or the GUI.
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").
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.
Starting with Ubuntu 7.04, 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
- 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
- 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, Rhythmbox, 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
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).
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.
- 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.
- 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.
- 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. For Ubuntu Lucid Lynx (10.04) and later, run the following terminal command:
ubuntu-bug audio
For Ubuntu Karmic (9.10), run the following terminal command:
ubuntu-bug -p alsa-base
This will submit a detailed bug report with information about your current system.
For older versions, or if the above fails for some reason, you can file a bug report, then upload alsa-info information according to these instructions.
Triaging sound bugs
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 (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. If in doubt, file a new bug.
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/DebuggingSoundProblemsMisc
DebuggingSoundProblems (last edited 2014-07-26 11:08:14 by penalvch)