Most visited posts/pages in the last 24 hours
Join 189 other subscribers
A listing of random software, tips, tweaks, hacks, and tutorials I made for Ubuntu
This tutorial will try to help you hear sound again! Notice that there is a newer version of this guide available here: https://docs.google.com/document/d/1iTlJ8BfqXUjaHO__TEdlkvuqB1WLOkGaudngc5SFLMI/edit
If you don’t hear sound in flash, open up a Terminal window, and type in it:
sudo ln -s /usr/lib/libesd.so.0 /usr/lib/libesd.so.1
sudo mkdir -p /tmp/.esd/
sudo touch /tmp/.esd/socket
Preliminary Checks:
Make sure your speakers are on turned on, not muted, and on full volume
Make sure your speakers are plugged in correctly (usually plugged into a green jack)
Check 1: Check if the problem is the hardware or the software
Burn a LiveCD of any system (preferrably ubuntu), put it in your disk tray, and reboot. See if you can hear sound (by playing an audio file, or something). If you have windows, see if sound works there.
Success: You hear sound, go to Check 2
Failure: You do not hear sound.
This can be caused by 4 things:
Check 2: Check if ALSA recognizes your soundcard(s)
Boot back into your normal system, open up a Terminal window, and type in it:
aplay -l
Success: You see your soundcard(s)
Type in the Terminal window:
sudo usermod -aG audio `whoami`
Log out, and log back in, then follow the alsamixer section, making sure everything is at full volume, and then test your sound using (you might have to run it a few times):
aplay /usr/share/sounds/alsa/Front_Center.wav
Success: You hear sound
Failure: You do not hear sound. Use this guide: http://idyllictux.wordpress.com/2009/04/21/ubuntu-904-jaunty-keeping-the-beast-pulseaudio-at-bay/
Reboot and then follow the alsamixer section
Failure 1: You see something similar to:
**** List of PLAYBACK Hardware Devices ****
ALSA lib conf.c:3643:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf
ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL hw:0
aplay: device_list:249: control open (0): No such file or directory
ALSA lib conf.c:3643:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf
ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL hw:1
aplay: device_list:249: control open (1): No such file or directory
ALSA lib conf.c:3643:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf
ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL hw:2
aplay: device_list:249: control open (2): No such file or directory
Simply type in it:
sudo apt-get install --reinstall libasound2
Then follow the Alsamixer section
Failure 2: You see something similar to:
aplay: device_list:221: no soundcard found...
Type in the Terminal window:
sudo aplay -l
Success: You see your soundcard(s).
Type in the Terminal window:
sudo usermod -aG audio `whoami`
Reboot, and follow Check 2
Failure 2: Follow Check 3
Check 3: Check if your system recognizes your soundcard(s)
Type in the Terminal window:
lspci -nn | grep '04[80][13]'
Success: You see results, move on to Check 4
Failure: You do not see results, which means that Ubuntu does not detect your soundcard. *TODO: Add more info*
Check 4: Check if your soundcard(s) are supported by ALSA
Look for your soundcard here: http://www.alsa-project.org/main/index.php/Matrix:Main
Success: Your soundcard is listed. Move on to Check 6
Failure: Your soundcard isn’t listed. Move on to Check 5
Check 5: Check if your soundcard(s) are supported by OSS 4
NOTICE: This technique is listed in https://help.ubuntu.com/community/SoundTroubleshooting as a last resort. Use this technique with caution because it removes ALSA, the default sound system in Ubuntu. Do not be surprised if you sometimes randomly log out.
Look for your soundcard here: http://opensound.hg.sourceforge.net/hgweb/opensound/opensound/file/3db750724c2d/devlists/Linux
Success: Your soundcard is listed. Follow the instructions here: https://help.ubuntu.com/community/OpenSound, and then here: http://ubuntuforums.org/showpost.php?p=9872284&postcount=4
Failure: *TODO: Add more info*
Check 6: Check if your the driver for your soundcard(s) is installed
Type in the terminal window:
sudo modprobe snd-
DO NOT PRESS ENTER. Press the TAB key twice.
Press y if it asks you if you want to see all results
Look for your soundcard driver. Mine is via82xx, so I found: snd-via82xx.
Success: You found your soundcard driver. Type in the rest of your soundcard driver, and press ENTER.
Type in the Terminal window:
echo "snd-yoursoundcarddriver" | sudo tee -a /etc/modules
Reboot, then open up a Terminal window, and type in it:
aplay -l
Success: You should see your soundcards. Follow the alsamixer section
Failure: *TODO: Add more info*
Failure: You didn’t find your soundcard driver.
Type in the Terminal window:
sudo apt-get install --reinstall linux-sound-base alsa-base alsa-utils
Reboot, then open up a Terminal window, and type in it:
aplay -l
Success: You see your soundcards. Follow the alsamixer section
Failure: You didn’t see your soundcards.
Follow these instructions: http://ubuntuforums.org/showthread.php?t=1681577
Using Alsamixer
Type in the Terminal window:
alsamixer
Success: You should see a nice mixer
To navigate, use the left and right arrow keys
To increase/decrease volume, use the up and down arrow keys, respectively
To mute/unmute, use the M key. Unmuted channels should appear green at the bottom.
To exit, use the Esc key.
To store your settings for the next boot, exit, and type in it:
sudo alsactl store 0
Or if this is your nth sound card (where n is the number of soundcards in your computer) replace 0 with n-1 (so if this is your second sound card, replace 0 by 1).
To test your sound, exit, and type in it (you might have to repeat it a few times):
aplay /usr/share/sounds/alsa/Front_Center.wav
Success: You hear sound
Failure: You do not hear sound.
Follow Check 2
Failure: Follow Check 2
If you had any problems with this guide, feel free to comment below!
Credits:
http://ubuntuforums.org/showthread.php?t=205449
http://ubuntuforums.org/showpost.php?p=1183439&postcount=1
I don’t know if its Debian Sid with its alsa and kernels, or KDE 4.X in Debian Sid, but it seems that every update brings me KDE Phonon messages of ‘Your sound setup has changed’ and very often, non-working audio. A simple restart of Alsa sometimes fixes this, other times I have to re-order my Phonon devices, and other times I have to reboot (even after a fresh boot) and it works again.
Frustrating.
Pingback: Links 22/7/2011: Linux Kernel 3.0 is Out, New Ubuntu LTS, Oracle Buys Ksplice | Techrights
Seems like PulseAudio is troublesome for alot of people! I wrote a li’l tutorial for removing it in Xubuntu 10.04, but I’ll link to your much more in-depth post! Thanks!
I now have sound but not able to save the setting of alsamixer by using this command “sudo alsactl store 0” every time I shut down then next time I reboot there is no sound, so I have to open a terminal and go through the alsamixer and unmute the master m.
Could you give me the output of this command?
aplay -l; echo "SUDO"; sudo aplay -l
As Requested.
**** List of PLAYBACK Hardware Devices ****
Home directory /home/carolm not ours.
card 0: ICH7 [Intel ICH7], device 0: Intel ICH [Intel ICH7]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ICH7 [Intel ICH7], device 4: Intel ICH – IEC958 [Intel ICH7 – IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
Could you give me the full output of the command please?
this is the full output .
carolm@carolm-OptiPlex-GX620:~$ aplay -l; echo “SUDO”; sudo aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ICH7 [Intel ICH7], device 0: Intel ICH [Intel ICH7]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ICH7 [Intel ICH7], device 4: Intel ICH – IEC958 [Intel ICH7 – IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
SUDO
[sudo] password for carolm:
**** List of PLAYBACK Hardware Devices ****
Home directory /home/carolm not ours.
card 0: ICH7 [Intel ICH7], device 0: Intel ICH [Intel ICH7]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ICH7 [Intel ICH7], device 4: Intel ICH – IEC958 [Intel ICH7 – IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
carolm@carolm-OptiPlex-GX620:~$
Which device of the 2 do you use for sound (Intel ICH or Intel ICH – IEC958)?
I do not know, I thought they are the one card. How do I find out?
On using this command lspci -nn | grep ’04[80][13]’
I get this result
carolm@carolm-OptiPlex-GX620:~$ lspci -nn | grep ’04[80][13]’
00:1e.2 Multimedia audio controller [0401]: Intel Corporation 82801G (ICH7 Family) AC’97 Audio Controller [8086:27de] (rev 01)
Sorry for the delay I live in Australia :)
What ubuntu release do you have?
I have Ubuntu 11.04
When I use the following command to save the alsamixer I get the following.
carolm@carolm-OptiPlex-GX620:~$ sudo alsactl store 0
[sudo] password for carolm:
Home directory /home/carolm not ours.
carolm@carolm-OptiPlex-GX620:~$
Weird, I’ve never had that problem.
Could you give me the full output of this Terminal command?
sudo alsactl store 0 || echo $?
I hope it will give a number at the end.
carolm@carolm-OptiPlex-GX620:~$ sudo alsactl store 0 || echo $?
[sudo] password for carolm:
Home directory /home/carolm not ours.
When I open the home folder there is a file named alsa-info.sh
in properties it says type: shell script (application/x-shellscript)
Cool! Please run it by this command:
bash ~/alsa-info.sh
Select the option to upload the file, and give me the link here. Then I can closely examine the problem.
http://www.alsa-project.org/db/?f=96b35d35d187ead5c6fe6138a480d13f47b0cecf
Seems good, except for the old driver version.
Could you run the command after a reboot (i.e. after the alsamixer settings were reset)?
I ran the command after the Alsamixer was reset.
Should I run the command after I reboot and before the reset of the alsamixer.
remember after I reset the alsamixer the sound works OK it’s just that it will not save the reset.
Before the reset, and give the URL generated here.
http://www.alsa-project.org/db/?f=68e50d15aa4668bcb8a9087cc9c3d0e10debed18
OK, when you have changed your settings, check out this link: http://alsa.opensrc.org/Using_alsactl_to_preserve_volume_state
This doesn’t help me. My alsa works fine… it is new experimental untested junk like pulseaudio and gstreamer used by KDE4 that are the problem.
Running this seemed to fix it for a minute, and then it was broken again automatically:
sudo apt-get install –reinstall gstreamer0.10-alsa gstreamer0.10-plugins-base gstreamer0.10-plugins-good gstreamer0.10-pulseaudio qtgstreamer-plugins pulseaudio pulseaudio-esound-compat pulseaudio-module-x11
Why are there so many people that have reinvented the wheel so now we have a huge number of sound servers and interfaces which all fail the same way at the most basic tasks (possibly simply because multiple are installed at the same time and are fighting)?
And BTW the only thing that shows up in the KDE sound settings is PulseAudio. If ALSA showed up, I would simply choose that and everything would be fine. Can I just uninstall PulseAudio? Highly detailed help like the above is great, but doesn’t apply to this Ubuntu packaging problem, so I don’t know what to try.
You might want to try my new guide (much more detailed, and has more steps) at: https://docs.google.com/document/d/1iTlJ8BfqXUjaHO__TEdlkvuqB1WLOkGaudngc5SFLMI/edit
Pingback: ruby on rails on ubuntu 12.04.2 LTS | knofiller
Thankyou!
This sound problems been plagueing me since I had to upgrade Ubuntu 10.04 to 12.04, the only time the sound worked then was after I restarted after downloading that 80+ mb update on the 26th (then it stopped working when I shut my computer off to run some errands).
But your Sound Troubleshooting post did the trick, though I still can’t help but feel like the other shoes about to drop.
What can I say…..I’m a pessemistic optimist :P
Still, THANKYOU!
Thank you very much. `sudo usermod -aG audio `whoami` ` was the source of my problem. It took me almost a day until I found your webpage for the fix.
Cheers!