1) add yourself to the 'audio' group (log out and log in again)
Code: Select all
useradd -G audio username
3) arts or esound stopped?
4) OSS modules unloaded?
5) speakers on?
6) As root
Code: Select all
modprobe snd-pcm-oss
Code: Select all
aplay /usr/share/sounds/alsa/Noise.wav
Code: Select all
cat /proc/asound/cards
Code: Select all
cat /proc/asound/modules
Code: Select all
aplay -l
Code: Select all
cat /proc/asound/version
Code: Select all
apt-get update && apt-get install alsa-utils
Download this script alsa-info.sh save it as alsa-info.sh
To run and create the info file
Code: Select all
bash ./alsa-info.sh --no-upload <-- without this option it will upload to alsa-project.org
Code: Select all
less /tmp/alsa-info.txt
Code: Select all
bash ./alsa-info.sh --pastebin
If none of that works then you need to find the specific audio chipset to add to your /etc/modprobe.d/alsa-base.conf file.The HDA analyzer tool provides a graphical interface to access the raw HD-audio control, based on pyGTK2 binding. The program gives you an easy-to-use GUI stuff for showing the widget information and adjusting the amp values, as well as the proc-compatible output.
This tool can parse also proc files (/proc/asound/card#/codec*) and output from alsa-info.sh script and monitor mode (check --help option).
Each combination of audio codec, audio mixer and audio device name requires a very specific configuration in the alsa-base.conf file.
The following string needs to be added to the /etc/modprobe.d/alsa-base.conf file
options snd-hda-intel model=YOUR_MODEL
You can find your codec chip name using this command
Code: Select all
cat /proc/asound/card*/codec* | grep Codec
find your codecs and model and add the appropriiate line to /etc/modprobe.d/alsa-base.conf
Valid model names (that replace YOUR_MODEL) depending on the codec chip, can be found here and here.
Also check to see if there is more than one alsactl executable in your path and remove the wrong/oldest one.
Code: Select all
sudo which alsactl
Code: Select all
# which alsactl
/usr/sbin/alsactl
For release Squeeze or any later release, alsaconf is no longer available in package alsa-utils. So try to configure alsa by running the command 'alsactl init' as root. Just ignore the error message like 'Unknown hardware' (this issue said to be fixed in alsa-utils .20), then reboot and try to test your sound. For more details please see http://forums.debian.net/viewtopic.php?f=6&t=39116
For more info see:
http://wiki.debian.org/ALSA
SoundTroubleshooting - - https://help.ubuntu.com/community/SoundTroubleshooting
HdaIntelSoundHowto - https://help.ubuntu.com/community/HdaIntelSoundHowto
http://alsa.opensrc.org/index.php/.asoundrc
MORE NOTES ON HD-AUDIO DRIVER - http://www.kernel.org/pub/linux/kernel/ ... Audio.html
How can I change the default ALSA device http://alsa.opensrc.org/FAQ026
Alsa-sound-mini-HOWTO http://www.alsa-project.org/~valentyn/#toc5
ALSA Multi-channel Audio mini-HOWTO http://www.cse.ohio-state.edu/~bondhugu/alsamch.shtml
If none of these steps work, either take your computer back to where you bought it or get used to not having sound. Sound is overrated anyway. :)