DebuggingSoundProblems
Differences between revisions 7 and 75 (spanning 68 versions)
|
Size: 7599
Comment:
|
Size: 3715
Comment: Due to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/839 , chgd "If your problem is related to your hardware..." as non-dev's/adv. users may not know and judge incorrectly.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Do not report problems on this page; use the normal support channels. | #### 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: |
| * 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 * Unmute everything. I had to unmute "Master Surround" even though I only have two speakers, for example. |
= Minimum Requirements for Audio Bugs = |
| Line 7: | Line 8: |
| * 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` * Here is a good sound troubleshooting page: http://linux.iuplog.com/default.asp?item=94639 * See also SoundProblemsHoary and SoundProblemsBreezy * Test different "Sound Servers": Go to System > Preferences > Multimedia Systems Selector. From there, you can test the different options. For me, there are four different sound servers installed, and only one works. This is probably your problem if you cannot play audio with xine or rhythmbox, but you can with xmms or helix/realplayer. * [http://ubuntuforums.org/showthread.php?t=44753 Howto: Happy ALSA, OSS, ESD, with Duplex - Sound Settings] |
First, please make sure all the below mentioned steps are completed, and the results are commented in your report. Failure to do so may delay your bug getting fixed as soon as possible. |
| Line 15: | Line 10: |
| == Useful Commands == | == How to Report Audio Bugs == |
| Line 17: | Line 12: |
| Contributed by Carl Karsten | Please do not report problems on this page; use the normal support channels instead. See http://www.ubuntu.com/support |
| Line 19: | Line 14: |
| Here are the commands and web sites I found helpful in getting sound working. carl@ubuntu:~$ aplay -l aplay: device_list:200: no soundcards found... Script to gather specs about sound things: http://alsa.opensrc.org/index.php?page=aadebug To try to figure out what sound card (chip set) you have: $ lspci -v and lspnp -v, look for lines like this: 0000:01:05.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) or 06 ESS1878 multimedia controller: audio “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 If you have an ISA card, you MUST pass isapnp=0 to modprobe. 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 Now figure out which module you need. http://www.alsa-project.org/alsa-doc/ Pick the manufacturer, Go – This should make it clear what module you need. http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=ESS+Technology&card=.&chip=ES18xx&module=es18xx snd-es18xx Between that, modinfo <module>, and linux/Documentation/sound/alsa/ALSA-Configuration.txt: Module snd-es18xx Module for ESS AudioDrive ES-18xx soundcards. 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) 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. 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. Suggested 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) == PolypAudio == Suggested 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 == Software Mixing == A much better way of getting esd to work with non-esd-aware apps is to make alsa use its software mixer. $ sudo /etc/init.d/alsa-utils stop $ sudo gedit /var/lib/alsa/asound.state (add the following text verbatim to the start of this file) $ sudo /etc/init.d/alsa-utils start |
If you feel you have encountered a software bug, the way to report it is to run the following terminal command: |
| Line 127: | Line 16: |
| # This text should be added to the beginning of # /var/lib/alsa/asound.state. You only need to add # it once -- it is saved across reboots. pcm.asymed { type asym playback.pcm dmix capture.pcm dsnoop } pcm.default { type plug slave.pcm asymed } pcm.dmix { type dmix ipc_key 5678293 ipc_key_add_uid yes slave { pcm 'hw:0,0' period_time 0 period_size 128 buffer_size 2048 format S16_LE rate 48000 } } pcm.dsnoop { type dsnoop ipc_key 5778293 ipc_key_add_uid yes slave { pcm 'hw:0,0' period_time 0 period_size 128 buffer_size 2048 format S16_LE rate 48000 } } |
ubuntu-bug audio |
| Line 168: | Line 19: |
| Now as many programs as you want can all use the sound card simultaneously, both the output and the microphone! ESD-aware apps can use ESD, other apps will still work fine. | This will submit a detailed bug report with information about your current system. |
| Line 170: | Line 21: |
| One notable misfeature of ESD is that it often ruins the A/V sync when playing videos. After setting up the software mixer, you might find it useful to turn esd off altogether (in tthe Sound control panel uncheck "Enable Software Mixing"). Now, especially with GStreamer 0.10, your movies should have perfect A/V sync. | 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 172: | Line 23: |
| It's a shame that software mixing isn't enabled on Ubuntu by default. | == Preliminary checks == |
| Line 174: | Line 25: |
| === More on Software Mixing === | 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 176: | Line 27: |
| 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 | 1. Is your speaker or microphone muted? Check here: * [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]] * [[Audio/CheckForMutedMicrophone|Check for muted microphone]] |
| Line 178: | Line 31: |
| First use section 3 here: http://www.ubuntulinux.org/wiki/RestrictedFormats, then do this: http://alsa.opensrc.org/index.php?page=DmixPlugin | == Advanced troubleshooting == 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 your problem is not fixed. 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". * For mixer problems, you can try controlling the [[Audio/Alsamixer|mixers at ALSA level]]. * You might be helped by checking if it is a hardware bug that is already fixed upstream. You can try [[Audio/UpgradingAlsa|upgrading your ALSA drivers]] to the latest snapshot. * Please make a comment in your bug report regarding what specific version you tested. * If your problem is audio crackling, glitching, or breaking up, and it is hardware specific, you can try applying a [[Audio/PositionReporting|position fix quirk]]. * Using very new hardware? [[Audio/HDAGeneric|Here's how to check]] whether your built-in sound card has driver support. = 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. [[Audio/SameHardware|Here's an article]] of how to determine whether you have the same hardware as the original bug reporter. = Further Information = The [[https://launchpad.net/~ubuntu-audio-dev|Ubuntu Audio Developer's team]] maintains a set of Audio relevant wiki pages [[Audio|here]]. |
| Line 181: | Line 59: |
| Handy links: http://alsa.opensrc.org/index.php?page=OssEmulation CategoryDocumentation CategoryCleanup |
CategoryDocumentation CategoryBugSquad CategoryDebugging |
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Minimum Requirements for Audio Bugs
First, please make sure all the below mentioned steps are completed, and the results are commented in your report. Failure to do so may delay your bug getting fixed as soon as possible.
How to Report Audio 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 is to run the following terminal command:
ubuntu-bug audio
This will submit a detailed bug report with information about your current system.
If the above fails for some reason, you can file a bug report, then upload alsa-info information according to these instructions.
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:
Advanced troubleshooting
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 your problem is not fixed. 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".
For mixer problems, you can try controlling the mixers at ALSA level.
You might be helped by checking if it is a hardware bug that is already fixed upstream. You can try upgrading your ALSA drivers to the latest snapshot.
- Please make a comment in your bug report regarding what specific version you tested.
If your problem is audio crackling, glitching, or breaking up, and it is hardware specific, you can try applying a position fix quirk.
Using very new hardware? Here's how to check whether your built-in sound card has driver support.
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 Information
The Ubuntu Audio Developer's team maintains a set of Audio relevant wiki pages here.
DebuggingSoundProblems (last edited 2014-07-26 11:08:14 by penalvch)