DebuggingSoundProblems
|
Size: 4991
Comment: add category games
|
← Revision 77 as of 2014-07-26 11:08:14 ⇥
Size: 3355
Comment: Streamlined the article to ease bug reporter workflow. No content changes.
|
| 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 |
= Preliminary checks before filing a bug report = |
| Line 6: | 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` |
Before filing a bug report, please check on the following: 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 10: | Line 11: |
| 1. Is your speaker or microphone muted? Check here: * [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]] * [[Audio/CheckForMutedMicrophone|Check for muted microphone]] |
|
| Line 11: | Line 15: |
| == Contributed by Carl Karsten == | = How to report audio bugs = |
| Line 13: | Line 17: |
| Here are the commands and web sites I found helpful in getting sound working. | Please do not report general problems on this page; use the normal support channels instead. For more on this, please see [[http://www.ubuntu.com/support]]. |
| Line 15: | Line 19: |
| carl@ubuntu:~$ aplay -l | If you have found a software bug, please report it by via the following terminal command: {{{ ubuntu-bug -s audio }}} |
| Line 17: | Line 23: |
| aplay: device_list:200: no soundcards found... | This will submit a detailed bug report with necessary information about your current system. |
| Line 19: | Line 25: |
| Script to gather specs about sound things: http://alsa.opensrc.org/index.php?page=aadebug |
If the above fails for some reason, you may file a bug report, then upload alsa-info information [[Audio/AlsaInfo|according to these instructions]]. |
| Line 22: | Line 27: |
| To try to figure out what sound card (chip set) you have: | == Things to specify in your bug report == |
| Line 24: | Line 29: |
| $ lspci -v and lspnp -v, look for lines like this: | First, should you ever need to do anything in this section for your sound to work in a brand new installation you should report a bug. |
| Line 26: | Line 31: |
| 0000:01:05.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) | 1. For mixer problems, you may control the [[Audio/Alsamixer|mixers at ALSA level]]. 1. A hardware enablement or regression bug may have been fixed upstream. Hence, please test the latest snapshot of [[Audio/UpgradingAlsa|upgrading your ALSA drivers]], mention which version specifically you tested, if this resolves your problem. 1. 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]]. 1. Using very new hardware? [[Audio/HDAGeneric|Here's how to check]] whether your built-in sound card has driver support. |
| Line 28: | Line 36: |
| or | = Triaging sound bugs = |
| Line 30: | Line 38: |
| 06 ESS1878 multimedia controller: audio | 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 32: | Line 43: |
| “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 | 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 34: | Line 45: |
| If you have an ISA card, you MUST pass isapnp=0 to modprobe. | * 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 36: | Line 47: |
| 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 |
[[Audio/SameHardware|Here's an article]] of how to determine whether you have the same hardware as the original bug reporter. |
| Line 39: | Line 49: |
| Now figure out which module you need. | = Further Information = |
| Line 41: | Line 51: |
| 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. == 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 |
The [[https://launchpad.net/~ubuntu-audio-dev|Ubuntu Audio Developer's team]] maintains a set of Audio relevant wiki pages [[Audio|here]]. |
| Line 108: | Line 54: |
| 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 CategoryCleanup |
CategoryDocumentation CategoryBugSquad CategoryDebugging |
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Preliminary checks before filing a bug report
- Before filing a bug report, please check on the following:
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:
How to report audio bugs
Please do not report general problems on this page; use the normal support channels instead. For more on this, please see http://www.ubuntu.com/support.
If you have found a software bug, please report it by via the following terminal command:
ubuntu-bug -s audio
This will submit a detailed bug report with necessary information about your current system.
If the above fails for some reason, you may file a bug report, then upload alsa-info information according to these instructions.
Things to specify in your bug report
First, should you ever need to do anything in this section for your sound to work in a brand new installation you should report a bug.
For mixer problems, you may control the mixers at ALSA level.
A hardware enablement or regression bug may have been fixed upstream. Hence, please test the latest snapshot of upgrading your ALSA drivers, mention which version specifically you tested, if this resolves your problem.
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)