[SOLVED] Slackware 14: Always need to run alsactl init manually in order to bring live Audio?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Slackware 14: Always need to run alsactl init manually in order to bring live Audio?
Hi all Slackers,
Just updated Slackware from 13.37 to 14 a few days ago.
Alsaconf is gone. Now it appears that I have to run
#alsactl init
manually everytime after login to KDE, else it will be no sound.
#alsactl store after setting #alsamixer and run #alsactl init also doesn't make any differences.
I tried to put alsactl init command into rc.local but without result.
I tried to create /etc/modprobe.d/snd-hda-intel.conf and put the content (a line):
options snd-hda-intel model=auto
I changed the model= to several type (referring to /usr/src/linux/Documentation/sound/alsa/HD-Audio-Models.txt )
This also fails to bring the sound automatically.
Additionally, my KDE keeps asking (pop-up after login):
KDE detected that one or more internal devices were removed.
Do you want KDE to permanently forget about these devices?
This is the list of devices KDE thinks can be removed:
Capture: HDA Intel (ALC269 Analog)
Output: HDA Intel (ALC269 Analog)
Output: HDA Intel, ALC269 Analog (Default Audio Device)
What is happening actually? I think it might be a failure of modprobe. Anyone having the same problem ?
Last time after the initial install of 13.37, I just ran alsaconf once, and the audio is active everytime. Now I have to manually run alsactl init everytime after login into KDE.
For me, there seems to be some conflict between the pci sound card and the NVIDIA graphics card (with HDA? audio), as when both are plugged in together, I can play video with sound through mplayer, but when I try to play mp3's with an audio player I get:
If I take out the video card, I can play mp3's with the correct driver for the sound card.
I've tried Alienbobs alsaconf script, but it reports:
Quote:
No supported PnP or PCI card found
ALSA mixer shows that the pci soundcard is being selected, but I still get the invalid argument error above.
Running 'alsactl init' I get these messages:
Quote:
/usr/share/alsa/init/00main:34: invalid filename '/usr/share/alsa/init/ca0106
Found hardware: "CA0106" "CA0106" "" "ox1102" 0x100a"
Hardware is intialized using a generic method
Ive also created an /etc/modprobe.d/alsa.conf, with the following line:
Quote:
options snd-hda-intel model=auto
Any help to get sound work would be appreciated.
Last edited by clifford227; 10-08-2012 at 05:55 AM.
My last install was Slack 12.2 which I ran up untill last week, and it run both the sound card and the Nvidia graphics card in tandem with no problems.
Quote:
Originally Posted by sycamorex
I had the same problem, Clifford. I blacklisted the module which fixed the problem.
Which module was that sycamorex?
Last edited by clifford227; 10-08-2012 at 06:58 AM.
I think it was snd-hda-intel but I am not at my computer now.
I blacklisted the 'snd-hda-intel' module in /etc/modprobe.d/blacklist.conf, and it removed the Nvidia card from Alsamixer, and now Im getting sound through Mpg123 audio player, which returned errors before the removal.
Audacious (my prefered audio player) still returns the 'invalid argument' error, so I think that is particular to audacious. I'll try upgrading it to the latest version.
I upgraded to Audacious 3.3.2, and I no longer get the error message, and it is able to play sound.
The difficulty in diagnosing where the problem lay with Audacious, was that certain settings in Audacious 3.3.1 (slackware 14 version) preferences may not have been set correctly.
The 'PCM device', the 'Mixer device', and the 'Mixer element', seem to have changed from what I normally have to set for Audacious to output sound.
But Audacious 3.3.2 is outputting sound
Last edited by clifford227; 10-09-2012 at 05:22 AM.
Just stick it in /usr/local/sbin and make it executable.
Eric
Is there a way to do this without this script? As a matter of fact, there is no such file in Slackware 14, i would like to know what to do in "new" way of Slackware 14. I have exacly the same problem just like in post one: two soundcard that are switched on every boot.
I would like to learn the "new" way of setting things in 14 - there is no alsaconf command, was removed, there is no script so i would like to learn and know what to do in this way, where there are no script and alsaconf command.
I blacklisted the 'snd-hda-intel' module in /etc/modprobe.d/blacklist.conf, and it removed the Nvidia card from Alsamixer, and now Im getting sound through Mpg123 audio player, which returned errors before the removal.
Audacious (my prefered audio player) still returns the 'invalid argument' error, so I think that is particular to audacious. I'll try upgrading it to the latest version.
Thanks sycamorex and RJwen.
how to blacklist HDA intel. i don't have blacklist.conf file in the /etc/modprobe.d directory.
i have the same problem...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.