Sound not working
From MEPIS Documentation Wiki
Click link above if:
- If your sound isn't working
- You do not know the exact device name
- You know the name but do not have the module name
- Before you click the above link know your module name
- If your sound works after this go to kmix setup
- fixes for specific cards
- minor fixes for kmix
If you have more than one sound device (for example a USB webcam with a microphone), there could be conflicts causing sounds to fail for certain applications.
Run as root this command in the konsole :
alsactl -E CMD=info init
If anything other than your normal soundcard is listed first, you have a conflict and should edit your /etc/modprobe.d/alsa-base.conf file. Detailed fix instructions are beyond the scope of the wiki, so please search the sound forums for help.
Tips and tricks
- Take a look in the KMix settings and make sure that all the sliders are enabled. Then on the Kmix menu bar go to Settings --> Configure Kmix, and make certain the "restore volumes on login" is checked. See the Kmix handbook for details.
- On M8, it is sometimes necessary after installation or upgrading to open a terminal, become root, and type:
alsaconf alsactl store
Notes: 1) alsactl is part of alsa-utils, which is not installed by default; 2) in mid-2009 alsaconf was removed from alsa-utils and is no longer available through the repos. It has been packaged by a Community Member and can be found in the Community repos in the package alsa-utils.
- Try opening a terminal and becoming root, then typing:
- Various tips can be found here for fixing annoyances with sounds
- Make sure KDE sound is operating: click KMenu --> Control Center --> Sound & Multimedia --> Sound System. "Enable the sound system" should be checked. Click the Test Sound button to see if it works.
- For snd-hda-intel systems try opening up kwrite as root and commenting out the first line (if that doesn't work, try commenting out the second line instead if it is not already) in
/etc/modprobe.d/snd-hda-intel (M11: etc/modprobe.d/snd-hda-intel.conf)
then run alsaconf.
- In the second line of that same file, try adding your specific machine model, for instance:
Options snd-hda-intel model=lenovo
Or try putting in the name of your sound card, for instance
Options snd-hda-intel model=Realtek ALC888
You can get your card model by entering in a terminal:
cat /proc/asound/card0/codec#* | grep Codec
NOTE: in MEPIS 11, some users have had success when nothing else worked by simply renaming (e.g., snd-hda-intel.conf.old) or removing that file and rebooting.
- Unless you have just upgraded kernel version--i.e. just done a major system upgrade, perhaps on a fresh install, in which case you should reboot to new kernel version before worrying about sound module--if you have lost sound, and it isn't simply a vol level/mute issue, you should try as root:
instead of using alsaconfig, as it is most likely that the alsa modules have simply become unloaded rather than unconfigured.
- If only root has sound, use KUser to make sure that the regular user is included in the sound group.
- snd-hda-intel how to
- snd-hda-intel solutions
- analysis and solutions
- ALSA documentation on device conflict