Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I decided to investigate Slackware and I thought I was getting along quite well with Slackware64-Xfce until I realized I heard not a sound. Oops, not good. So I have been trying for several days to first diagnose and then repair my problem. No luck thus far. What I hve larned is that I do not understand how to configure ALSA in Slackware.
Various documents on the web suggest using the “ALSA configurator” (alsaconf) to configure ALSA. Apparently that set of tools no longer is packaged with ALSA?
Question: Is there some functional substitute?
If I select ALSA-mixer (alsamixer) it shows me 3 unmuted S/PDIF devices. These evidently relate to the circuits on my System76 laptop labeled as HDA Intel MID which shows priority 0 on the device list.
If I use F6 I can select HDA Intel PCH with priority 1. If I select this I see the ALSA mixer sliders I am accustomed to seeing. The master slider is muted by default. I have learned how to unmute it and save that configuration so that the ALSA mixer is not muted when it comes up. I still hear no sounds of any sort. So that alone does not solve my problem.
Question: Am I correct that I need to set HDA Intel PCH as priority 0 and HDA Intel MID as priority 1 in order to solve my problem? I have no idea how to do that. Can anyone direct me to a document that explains how to do it?
Is there some other way to solve this problem that I have missed?
this is mine.
but for some reason Slackware liked to put my webcam first or my nvidia hdmi so to fix this problem I did this. I created a /etc/modprobe.d/sound.conf
looked like this.
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF version 1.0.25 ---
alias char-major-116 snd
alias char-major-14 soundcore
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd slots=snd-hda-intel,snd-usb-audio
pat named it the /etc/modprobe.d/snd-hda-intel.conf
Diagnosing the issue
Execute the command
lsmod | grep snd
in a terminal window. If there is a reference to snd_hda_intel in the output then the snd-hda-intel kernel module has been loaded as the driver for the controller chip and the codec chips on the HD-audio bus.
The snd-hda-intel kernel module tries to autodetect and configure your sound hardware, but this is not always successful. Some further configuration may help.
Often the fix is simple. Just create a file in the /etc/modprobe.d/ directory and provide suitable options to the snd-hda-intel kernel module. The actual file name is not important although it must have a .conf suffix. You could use snd-hda-intel.conf. Names used by other distributions to hold this information include sound.conf and alsa-base.conf.
This will prefer every other soundcard before using my TV card and my HDMI output. You will just have to replace those with your unwanted driver - as in Drakeo's description lsmod | grep ^snd_pcm should give you the relevant module names. If you want to use it as a reverse list then just don't forget the leading comma after the equals sign. That one line should be everything you need.
We have a solution thanks to the several people who posted and the HowTos on SlackDocs. Let me report the next steps in my successful search for sound with Slackware64-14.1. Doing so might help someone else.
Drakeo was right. I had missed some relevant documents. Slackdocs/HowTo articles-Hardware contains "Audio and snd-hda-intel"and also "Sound Problems on Slackware." These two documents held the keys to this problem. So here is what I did.
I understood that snd_hda_intel showed the proper module being loaded.
Q. What did alsamixer show?
It showed three S/PDIF devices as 0 HDA Intel MID. Using F6 I went to “1 HDA Intel PCH”. This showed the ALSA mixer controls I would expect to see. The Master was not muted.
Q. What was the solution path?
According to "Sound Problems on Slackware" I should be able to test this card by specifying the card to test as follows: "aplay -D plughw:1,0 test.wav" This returned "No such file or directory." So where was test.wav? This set off a rather long search.
In /usr/share/sounds/alsa/ I did not see test.wav but I did see Noise.wav, so I tried that. "aplay -D plughw:1,0 Noise.wav" returned the same “No such file ..." So I next tried this with the full path to Noise.wav doing "aplay -D plughw:1,0 /usr/share/sounds/alsa/Noise.wav"
This worked! OK, now I knew that the card at 1,0 could make noise. It looked to me that the remaining task was to make it the default card.
So I followed Drakeo and went back to the "Audio and snd-hda-intel" document I had missed initially. I then did
A check of modprobe.d showed the file in place. I then rebooted the system.
No joy; alsamixer still reported the HDMI ports as Card 0 and the Intel PCH card as card 1. This was confirmed by aplay -l. If I did cat /etc/modprobe.d/snd-hda-intel.conf it read back “options snd-hda-intel model=auto” as I thought it would.
I then reviewed the several posts on this thread as well as the two HowTos in SlackDocs mentioned earlier. I elected to follow the suggestions in "Sound Problems on Slackware" to create /etc/asound.conf as shown in that document, since card 1, device 0 was also my working alsa card. This seemed to me the simplest approach. With that done I then rebooted hoping to see a change in the default order of preferred sound-cards.
Interesting: There was no apparent change in the order of the cards but asound.conf must route the sound to the proper card because my speakers now work just as they should!
There is one small thing I do not understand but doubtless more experienced Linux folks do. I can no longer start alsa mixer at the cli by simply typing “alsamixer”. Instead I must now specify the card, “alsamixer -c1” If I do that I can control alsamixer from the cli.
I started the Xfce desktop and clicked on the mixer app. Everything worked as it should.
So my problem is solved with my thanks to all who contributed. I learned a lot starting with the fact that the first place to look is SlackDocs!
You know I think Slackware is a keeper and that means I really ought to purchase something from the Slackware store.