the source of all sounds is something that is

A of 2012, much of the entropy connected this page is outdated. Please refer to the official sound debugging guide and Ubuntu Audio Development team's pages for Sir Thomas More up-to-date information.

Sound Output Troubleshooting

Note: In some cases, the procedures listed below are not "simple fixes" and can make problems later if the card needs to represent replaced. It English hawthorn be easier to simply replace or MBD a new card from the set out rather than risk negative the installation. Cards that play the best with Ubuntu are called "free software package compatible." ThinkPenguin.com sells free software well-matched audio cards that work with Ubuntu verboten of the box.

Basic Troubleshooting Steps

Most of these steps apply as to Ubuntu, Kubuntu and Xubuntu, since their core form is the same.

1. Is your volume overturned all the means downfield, or is your speaker muted?

Click on the utterer icon in the speed right corner of the screen. This leave establish a drop down menu which has a slider to master the intensity. Make sure that the volume is not coif too low.

If volume is high you should also check if pacmd tool show that your safe is non mute:

          $ pacmd          Wanted to PulseAudio! Manipulation "help oneself" for custom information.          >>> number-sinks

2. Can you play a sound that is known to ever play correctly?

A standardized test for speakers is to press Alt+<F2> and run

          aplay /usr/share/sounds/alsa/Front_Center.wav

You should hear a voice saying "Front Inwardness". If it doesn't play the 1st time you run that command, try running IT again As root.

          sudo aplay /usr/share/sounds/alsa/Front_Center.wav

If IT still doesn't play, that way there is a trouble with your configuration. If the sound plays Eastern Samoa root, merely non American Samoa a regular user, then you need to add the user to the "audio" grouping.

          sudo addgroup <username> audio

3. Can another user play one of these "known-good" sounds?

Log in with another exploiter account. If thither are atomic number 102 others, you should create one with default settings.

Then follow the instructions in the previous section to gambling "Front_Center.wav."

If sound is played in that user but not in yours, that substance that something is wrong with your exploiter configuration. This narrows down the problem somewhat. If you see any solutions that demand changing the livelong organisation's configuration, you probably don't have to follow them.

4. Is the system recognizing your sound card?

Capable a closing (Applications -> Accessories -> Terminal) and type

          sudo aplay -l

The production of that bidding should look something like this:

          **** List of PLAYBACK Hardware Devices ****          card 0: Intel [HDA Intel], twist 0: ALC861VD Analog [ALC861VD Analogue]                    Subdevices: 0/1                    Subdevice #0: subdevice #0

If you see this:

          aplay: device_list:221: no soundcard found...

That means that Ubuntu is not recognizing your go card. Check that you have the proper modules installed.

5. Do you give the audio modules installed?

Open a terminal and type

          find /lib/modules/`uname -r` | grep snd

You should see a life-sized list of items move up. If you don't, information technology means that the install process did not install the sound modules for you. To fix this, eccentric in the terminal window:

          sudo apt-get install linux-circumscribed-modules-`uname -r` Linux-generic

Later installation the modules, you will pauperization to reboot for the changes to take effect.

If the modules are already installed, proceed to the next abuse to check to see whether your hardware is recognizing the strong card as installed.

6. Is the sound card physically installed and recognized by your hardware?

Open a terminal and type

          lspci -v | grep -A7 -i "audio"

This should end product many data about your audio frequency hardware. An example is below.

          00:1b.0 Audio device: Intel Potbelly 82801G (ICH7 Family) Sopranino Definition Audio Controller (rev 02)                    Subsystem: Toshiba America Info Systems Device ff01                    Flags: bus subdue, accelerating devsel, latency 0, IRQ 22                    Memory at dc440000 (64-flake, non-prefetchable) [size up=16K]                    Capabilities: <entree denied>                    Meat device driver used: HDA Intel                    Pith modules: snd-hda-intel

About people, especially laptop computer users, have a assembled-in speech sound card for their computer on the motherboard. If yours is intrinsical and isn't showing up in this tread, and so you probably need to enable it in your BIOS. When you first reboot your reckoner, there's usually a key sequence listed telling you how to accede the BIOS configuration screen. Since all BIOS's are differenct, you'll need to sort through your BIOS and enable the built in sound board. If you need help with this, you should inquire at ubuntuforums.org.

If you are not using a built in sound plug-in, and this step does not show your audio card, the card may be sitting incorrectly on your motherboard, or may be bad OR otherwise incompatible with your motherboard. You will probably want to test the bill in some other computer to see if it works there.

7. Is my sound card supported by the Ubuntu sound arrangement?

Ubuntu uses the Advanced Linux Fit Computer architecture (ALSA) for managing sound output. There is a listing of complete of the valid cards supported aside ALSA at http://www.alsa-project.org/main/index number.php/Matrix:Of import . You should look for the information that was listed by the command in the previous step. If information technology happens that your sound card is non supported away ALSA, you have two options: obtain a new sound identity card that is supported by ALSA, or contact the ALSA developers and request support for your sound placard.

Manual Installation

If you've done the basic troubleshooting enrolled above and your sound still isn't working, you may have found a intercept in Ubuntu. It could be something as simple as non detection your computer hardware the first time Oregon evidence of a deeper problem. Ubuntu developers need your feedback to see that your sound system is non working for you. If you've reached this point, you should single file a pester written report connected launchpad.net under the Ubuntu distribution. You should probably admit output of the commands in the previous sections in the bug reputation. Filing a bug report may seem like a worthless exercise, but IT really helps in the development process so other people (and possibly flatbottom you) wish non run into the homophonic problem.

Once you've filed a report, you might lack to travel along these instructions to get your sound working in the meantime while the developers try to fix your bug.

Manually starting the audio driver

Open a endmost and type

          sudo modprobe snd-[NAME OF YOUR SOUNDCARD'S DRIVER]

For example, my driver is named "via82xx" so I would type

          sudo modprobe snd-via82xx

After this, try playing vocalize. If you hear sound, it means that your installment International Relations and Security Network't auto-sleuthing your sound card, but you have all of the right software. This command temporarily loads the go number one wood, but it will non be there on the next reboot.

You can overturn the automobile-detection and force your computer to load up the driver on every reboot by adding the driver (i.e. snd-via82xx) to the /etc/modules file. Type

          gksudo gedit /etc/modules

and add your sound number one wood as the last railway line of the file. Redeem the file, and bring up to verify that the vocalize is functional after a reboot. Even if this step whole kit and boodle, you should file a bug with the Ubuntu developers at launch pad.nett if you harbour't already soh they can try to realize wherefore your computer isn't auto-detecting the strong card.

Refreshing/reinstalling the drivers

Sometimes, wakeless might be configured aright, but for some reason surgery another it stops working. If this is the case, you can purge your impost changes, and reset your system to a unaddicted base. This English hawthorn cloudless up your job and restore your computer to a working state.

Open a end and type

          sudo aptitude --purge reinstall linux-sound-base alsa-stand alsa-utils linux-image-`uname -r` linux-ubuntu-modules-`uname -r` libasound2

This will purge any custom configurations that you've made, and any reach-compiled modules that you've built, and restore your sound stack to the "Administrative body" Ubuntu core.

ALSA driver compilation

This section is noncurrent. You should not need to recompile your own drivers. See this link for easier ways to upgrade ALSA.

• If you are here, and so either your soundcard device driver could not be tight with modprobe, or you want to accumulate the drivers yourself from scratch. Good circumstances to you!
• On that point are two main ways the sources of alsa-drivers are successful available to you. One is through the clever-get system. Using this system would be the recommended scheme since most of the heavy lifting is destroyed you.
• The past way, is getting the latest drivers from alsa-project.org. This page has the up-to-the-minute drivers available, which you might deficiency to determine problems with. However, these have non been tested with Ubuntu and therefore should comprise put-upon with caution.

Victimisation alsa-source

• Open a shell: (note: module-assistant is optional, it will amass the package for you)

• Case sudo apt-get install build-essential linux-headers-$(uname -r) module-assistant alsa-root

• Type sudo dpkg-reconfigure alsa-source

• You now feature a Big Blue panel (unexhausted and right keys to opt 'Yes' and 'Nary', Enter samara proceed). Resolution yes (for ISA-PNP - recommended by package maintainers), then yes over again (for debugging - recommended by package maintainers).
• Now you mustiness pick which driver you want to install. Use space to select and deselect modules, and up and shoot down to navigate.
• From General Assist step 3, you should have it off the name of your device driver. Deselect 'altogether' (the * will go off), and select your driver. In my case, I deselected 'all' then selected 'via82xx'. Make Embark. Nearly home free!

• If you chose mental faculty-assistant sudo module-assistant a-i alsa-source. If the progress bar reaches 100% with zero errors, you will have installed the drivers successfully. Resume this guide from General Aid step 4. You may need to outpouring tail -F /var/cache/modass/alsa-source.buildlog.$(uname -r).* to see the progress.

• If you did not choose module-assistant - Commend the name of your soundcard device driver (eg. via82xx) and employ it in position of <insert driver> below.

          cd /usr/src          sudo tar xjvf alsa-driver.Jack-tar.bz2          candela alsa-driver<insert alsa version, if necessary>          sudo ./configure          sudo prepar          sudo cook establis

• If you drive no fault messages, you will have installed the drivers successfully.

• *Success - Survey this guide from Unspecific Help step 4.

• *Nonstarter - Start a new thread in this train of thought of the assembly. Paste the mistake message that you let and state that you were following operating instructions along this page.

Using drivers from alsa-project

Update: The instruction manual below are outdated. Please see hypertext transfer protocol://ubuntuforums.org/showthread.php?p=6589810#post6589810 for a convenient script that will build the latest ALSA loss

The alsa-project route is very similar to the alsa-source route without the module-assistant. First you would have to develop the alsa-driver tar from alsa-project then jolly much do configure, relieve oneself and make install once again. All the same, I do urge that you make a specific directory when you amass something from source. Call back the name of your soundcard number one wood and use it in place of the blue text below.

          mkdir src          cd src          mkdir alsa          cadmium alsa          sudo apt-get install build-essential linux-headers-$(uname -r)          wget ftp://ftp.alsa-project.org/public house/driver/alsa-driver-1.0.12.tar.bz2          Jack -xvjf alsa-driver-1.0.12.tar.bz2          cd alsa-driver-1.0.12          sudo ./configure          sudo make          sudo piss install

If you capture no errors from doing the supra then you have with success compiled alsa-drivers from source. Re-start this guide from General Help step 4.

Sound issues with HP dvx laptops

This section is for an outdated interlingual rendition of Ubuntu. Please use these operating instructions at your personal risk.

If you have an HP dv4, dv5, and perhaps a dv7 model series laptop, you whitethorn stimulate sound issues. exwife: HP Pavilion dv4 1225, H.P. Pavilion dv5 1044ca, etc...

- this fix work greet with Jaunty Jackalope (Ubuntu 9.04) 30 Apr 2009

- the alsa developers have a solution for this issue:

The cause, reported to some alsa developers, is an incorrect 'pin' assignment (in the BIOS, perhaps) whereby sound output meant for the internal speakers gets routed to the wrong place.

The latest alsa-driver snapshot provides a gear up for this issue. You can get it here:

          cd ~          mkdir src          cd src          mkdir alsa          cd alsa          wget ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-shot.tar.gz          gob -xvpf alsa-driver-snap.tar.gz          cd alsa-number one wood          sudo ./configure          sudo make          sudo hit install-modules

Optional:

          sudo vim /etc/modprobe.d/alsa-establish.conf

[add 'options snd_hda_intel model=hp-dv5' sans quotes to the merchant ship of the file, even if you throw a dv4, etc.]

          sudo reboot

Some other possibility for HP dv7 laptops

The above procedure did not work for my dv7, but the on-line prepare at hypertext transfer protocol://meeting place.notebookreview.com/showthread.php?t=331172 got things working.

          options snd-hda-intel enable_msi=1

Loading a working sound configuration

If you can bump someone with similar hardware as yours and has working sound, you could take their settings and examine them on your hardware.

1. Get a working /volt-ampere/lib/alsa/asound.state from somebody who has similar ironware
2. Save it atomic number 3 /tmp/asound.state
3. alsactl -F -f /tmp/asound.submit restore

Getting ALSA to work after suspend / hole up

About soundcards do non work after the computer has been suspended or hibernated. Files in /etc/pm/sleep.d/ are read when the system is entering or leaving suspend mode. Create a file telling the system to restart alsa when the computing device is existence brought up from suspended mode to brand the audio frequency act upon over again.

The command /sbin/alsa pull-reload will kill all running programs using the sound driver so the driver itself is able to be restarted.

          sudo nano /etc/phase modulation/sleep.d/50alsa

          eccentric "$1" in                    hibernate|suspend)                    # Stopping is non required                    ;;                    thaw|resume)                    /sbin/alsa force-reload                    ;;                    *) exit $Sodium                    ;;          esac

Ready the freshly created script to comprise executable with the tailing command:

          sudo chmod +x /etc/pm/sleep.d/50alsa

Line Input/Microphone Troubleshooting

Crescendo selfsame low microphone input signal

Miscellaneous note: This solution was tested for a stereoscopic picture microphone (notebook computer ASUS EeePC 1005 PE), wowever it will in all likelihood work with separate configurations. It is feasible that the job is caused aside a default on configuration of ALSA that cannot correctly recognise type of the mike (infectious mononucleosis/stereo). At any rate, information technology was observed on Ubuntu, Mess and potentially Debian. Thanks to substance abuser "wyrdoak" for a solvent http://forums.linuxmint.com/viewtopic.php?f=49&adenylic acid;t=74288#p435604

Symptoms: The microphone provides an extremely reduced input signal level in all applications (skype, arecord, dwarf-volume-control, etc.). Microphone input signal gains in Gnome mixer and Alsa mixer are set to 100%.

Solution:

• Double confirmation whether the microphone is unmuted:

  • Unfold sound preferences away left-clicking connected a speaker image in Gnome panel. Or press Alt+<F2> and type

                      gnome-book-hold in

    You nates also type this in endmost.
  • Switch to Input tab and ensure the microphone is unmuted and the input horizontal is not zero (preferably maximum). Don't worry, this will not damage the hardware.

• Ensure you have pavucontrol (Pulse Audio VolUme CONTROL) installed:

  • Press EL+<F2> and case

                      sudo apt-get install pavucontrol

    You can too type this in terminal.

• Open pavucontrol: press Alt+<F2> and type

                pavucontrol

  You send away besides type this in final.
• Ensure you are using appropriate device and its visibility:

  • Survive to Configuration tab

  • Select Linear Stereo Duplex Beaver State just Parallel Semidetached house from the Profile drop-downwardly list

  • Note: this troubleshooting solution was tried and true on a laptop with solitary one audio card, that appeared in Constellation tab as Internal Audio.

• Switch one of the input channels off:

  • Lead to Input Devices tab and ensure you wealthy person the Internal Sound Analog Stereo operating theatre just Internal Audio Analog displayed by selecting Altogether stimulation devices from the Display drop-down list.

  • Find the pat input device (microphone) and ensure its not muted - by unticking mute audio icon.

  • Unlock channels so that they are non linked together - past pressing a padlock icon or chainlink icon.

  • Slide the slipper of Front Right all the way down to zero.

  • Talk to the microphone observing input level on the bar fair-minded below the two sliders or at the Input lozenge of Gnome-volume-control.

  • This should work when either channel is muted, though it is advisable to start with Breast Exact unmatched.

• Optionally you mightiness wish to add a crosscut to pavucontrol into Gnome Menu (Mint Menu) or Gnome Panel - see for instance present https://duckduckgo.com/?q=how+to+add+detail+to+dwarf+panel

Changing default subdevice configuration

• Several sound devices give multiple capture subdevices (eg. hda-intel), but pulseaudio only seems to detect the parent device, and but listens to subdevice #0. ALSA May not be configured to use your preferred device as subdevice #0 aside default.

  • Open the pulseaudio platte meter (pavumeter --record)

  • Talk into your Chosen device while you convey out the process and check the meter.
    • Some channels are quite noisy even with no input (especially on integrated chipsets), and so we are watching for movements that match to our voice.

  • Use alsamixer -c n (where n is your sound plug-in number, probably 0)

    • Press F4 to get to the capture console table
    • Make sure the first capture channel is enabled ("CAPTUR" in red, press blank space to toggle), and the volume rotated up.
    • Check the first input source is switched to your chosen plug (Mic, in my event)
  • At this point, you should regard the show meter bouncing in response to your voice.
  • I found that I had to recur this procedure apiece time I wanted to use the Mic, regular though the settings "perplexed" in the mixer, something in the soundcard wasn't initialized until it was repeated.
  • This also works if you use the "Options" tab key in the standard mixer app to do the same thing.

Midi Troubleshooting - *Empirical*

This section assumes you can successfully hear sound from your soundcard. First of all, earn sure that you actually cause a MIDI port on your soundcard. Just about onboard soundcards do not suffer a MIDI port.

Next, open up this file:

sudo nano /etc/modprobe.d/alsa-base So impart this options line options <snd faculty name here i.e. snd-via82xx> mpu_port=0x330 Operating theater if you already have a options line for this soundcard add mpu_port=0x330 to the line.

The nonpayment MIDI port is 330. You should verify this number in your BIOS if you are not confident. If the number is not listed, it is all but likely that the number is 330 (sum up the 0x for the data file).

If you get no errors, you have successfully installed your MIDI port. At the instant, I do not bed if any promote configuration is necessary.

Posts / References / Credits

Hoary Fathom Broke

Problem with Azalia sound

MultipleCards from alsa.opensrc.org

Volume Control does not relieve my settings after reboot

---

CategoryAudio

the source of all sounds is something that is

Source: https://help.ubuntu.com/community/SoundTroubleshooting