[SOLVED] No soundcards found - alsamixer not existing - only dummy output: sound module not loaded
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
No soundcards found - alsamixer not existing - only dummy output: sound module not loaded
Hi all,
I just started with Linux and know relatively little about computers...so am really frustrated with this one
I have a dual booted HP 750 -126ns, with Windows 10 (soundcards get recognized) and Mint Cinnamon 17.3 Rosa (no such luck)
I have been googling everything I could think of and following forums - I believe (but might be wrong) that my problem might be the lack of kernel sound modules...and that is where my knowledge stops
To wrap up:
aplay -l yields no soundcards found
alsamixer yields no such file or directory exists
(Synaptic shows a bucketload of alsa 'thingies' loaded though)
The soundcards are properly installed (it seems)
So - some info
dpkg -l *alsa*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
un alsa <none> <none> (no description available)
ii alsa-base 1.0.25+dfsg- all ALSA driver configuration files
ii alsa-firmware- 1.0.27-2ubun amd64 ALSA software loaders for specifi
ii alsa-oss 1.0.25-1ubun amd64 ALSA wrapper for OSS applications
ii alsa-tools 1.0.27-2ubun amd64 Console based ALSA utilities for
ii alsa-utils 1.0.27.2-1ub amd64 Utilities for configuring and usi
ii bluez-alsa:amd 4.101-0ubunt amd64 Bluetooth ALSA support
ii bluez-alsa:i38 4.101-0ubunt i386 Bluetooth ALSA support
ii gnome-alsamixe 0.9.7~cvs.20 amd64 ALSA sound mixer for GNOME
ii gstreamer0.10- 0.10.36-1.1u amd64 GStreamer plugin for ALSA
ii gstreamer1.0-a 1.2.4-1~ubun amd64 GStreamer plugin for ALSA
un libesd-alsa0 <none> <none> (no description available)
un libsdl1.2debia <none> <none> (no description available)
ii libsox-fmt-als 14.4.1-3ubun amd64 SoX alsa format I/O library
and this last bit, which seems the mother of all problems!!!
modprobe snd_hda_intel
modprobe: ERROR: ../libkmod/libkmod-module.c:180 kmod_module_parse_depline() ctx=0x7f56deffb010 path=/lib/modules/3.19.0-32-generic/kernel/sound/pci/hda/snd-hda-controller.ko error=No such file or directory
modprobe: ERROR: ../libkmod/libkmod-module.c:180 kmod_module_parse_depline() ctx=0x7f56deffb010 path=/lib/modules/3.19.0-32-generic/kernel/sound/pci/hda/snd-hda-controller.ko error=No such file or directory
modprobe: ERROR: could not insert 'snd_hda_intel': Unknown symbol in module, or unknown parameter (see dmesg)
Please note I have NO CLUE about anything and am just blindly following instructions from forums (sometimes I read stuff and wonder if it is still English). Computer is brand new, I dont want to mess anything up
Any help or guidance, in 'Sesame street language' will be VERY welcome
Last edited by JMC_791; 04-10-2016 at 11:49 AM.
Reason: SOLVED
EDIT: Please try Timothy Miller's solution (below) first before responding to my questions.
Not sure I can help with this but...
Since your system is brand new, there's a chance that your sound device (or chip) is not yet supported. Out of curiosity, what are the results from these commands...
Code:
lspci -nnk | grep -i -A7 audio
Code:
lsmod | grep snd
Code:
dmesg | grep -iC 3 "enter name"
Where the command above says "enter name," please replace it with either "snd" or "audio" and see if it reports anything.
With respect to aplay -l and alsamixer, please open the Synaptic package manager and verify the package "alsa-utils" is installed. I'm guessing it is, since you were able to get a result for aplay -l but I'd like to double check anyway.
Regards...
Last edited by ardvark71; 04-10-2016 at 01:30 AM.
Reason: Added information.
If I am correct, it doesn't have a kernel module that works with your sound card (last I read, anyway). You'll need to install a newer one. I haven't had to do this myself, so can't vouch for the modules, but there are a LOT of posts out there already for these Skylake ALC887 sound cards w/ linux (ubuntu in particular).
Again, can't vouch for the validity of the instructions, but if 17.3 is indeed based on 14.04 LTS, should work:
The "Unknown symbol" error in dmesg indicates the sound module is not compiled for kernel in use. That's all I can do to help, I have no clue how this could happen in Ubuntu world or how to fix it "the Ubuntu way". I'm sure an experienced Ubuntu user can tell how to remedy this, a kernel upgrade probably will do, too.
If you are using a current kernel distribution ... the latest general-availability one ... and have done nothing else to it, then I would report the issue to Ubuntu as a possible bug. (It happens. "A lot," actually. They'll need to be alerted. What any distro-publisher sets out to do is actually ferociously complicated ...)
Seems like you have the hardware. Perhaps something got wacky when you did your install. Perhaps re-installing some of the core packages can help overcome the issue. Or maybe it didn't grab libasound2 as a dependency depending on how you did your install. Or other things.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.