[SOLVED] My slackware 14.1 sound suddenly doesn't work
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.
Hi,
Few days ago, my slackware 14.1 suddenly doesn't have sound, Everytime I login to KDE,there was KDE dialog
complaining about audio driver not used anymore.
Now,after I tinkering with KDE audio setting, I got this notification in applet everytime I login:
Code:
The audio playback device HDA Intel PCH (ALC269VC Analog) does not work.
Falling back to .
I would suggest booting to a Live CD of something (Mint would be a good choice) and testing the audio. If it works under the Live CD, then the issue is certainly a
Slackware issue; if it doesn't work under the Live CD, it may well be a hardware issue.
If it is a hardware issue, no amount of mucking about with software will fix it.
go into settings and set your defaults playback apply to device list. do that for all three categories. then reboot. when kde asks you what to do with the devices etc etc. just remove them. what happened it has happen to me before for some reason when kde read alsa it reconfigured. and now you have duplicate copies.
you will find this often when you have installed pulse audio. Another thing I have alsa /etc/modeprobe.d sound.conf
Code:
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd slots=snd-hda-intel,snd-usb-audio,
Last edited by Drakeo; 04-24-2015 at 06:59 AM.
Reason: another thing
@frankbell
This is not hardware issue,
as you can see in my first post, running aplay as root does produce sound and my laptop is dual boot with windows. Windows can play sound normally.
@Drakeo
Tried your answer, put some config in sound.conf inside /etc/modprobe.d/ still doesn't work.
hottdogg,
If you have XFCE installed, does sound work there?
Also, you do have 2 audio devices. It's a configuration error of some kind, and KDE (at least) can't decide which to use. Did you install pulse-audio? Is the "HDA Intel" indeed selected in phonon?
Quote:
my slackware 14.1 suddenly doesn't have sound
Certainly something changed software-wise. Chances are pretty high that you made that change.
You may need to change the order of the devices as recognized by kde.
Go to
System Settings -> Multimedia -> Phonon
Test each card and move those that do play sound to the top using the "Prefer" button. I've had this a few times in KDE under 14.1. In fact there's a few things in KDE that seem to be losing their original settings. Maybe it's an age thing
Hopefully KDE in the next Slackware release will remember things a bit better.
Hello
Maybe I am barking up the wrong tree but even if you don't really have 2 sound chips (eg: onboard or standup card plus HDMI on a video card) the system is seeing a very odd contradiction here. This (below quoted from your 1st post) troubles me -
Notice both devices are listed as Card 0, but one is "device 0" and the other "device 3". This may possibly be somewhat explained byt the subdevices lines but even those seem contradictory. Whether these 2 are physically different or not seems to me to be a non-issue since the system sees them at least somewhat separate, requiring a choice. This may even be as simple as the system sub-listing alternate outputs and probably is due to a buffer chip.
The easy solution, if not final at least a very important step, is to blacklist one and prefer the other. If you need both outputs for switching purposes then you will need a considerably complex config such as commonly found in asoundrc to assign each to specific apps or tasks/roles. It would help a lot if we knew more about nature, brand/model of this system or at least the souncard(s).
Still the first step is to pare down, blacklist one eliminating that variable and see what works. Then report back and we can take step 2.
Hello again,
Apparently when I logged in as root ( I rarely login as root,usually just su),sound works. Sooo...
I tried dugan's solution.
Code:
#usermod -a -G audio hottdogg
And the sound is working again!
But this is strange, in Slackware I never had to explicitly assign audio group to user to make sound works until now.
Is this a hacky solution?
anyway, I'll mark this as solved. Thanks Dugan.
@enorbet
I thing device 3 is for HDMI output(my laptop has hdmi port), I don't want to complicate thing configuring for hdmi output. So won't go further with that.
Btw, this my sound card
Code:
# lspci -v | grep -i audio
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
And the sound is working again!
But this is strange, in Slackware I never had to explicitly assign audio group to user to make sound works until now.
Is this a hacky solution?
If you create a user using the adduser script, it will prompt you to press the UP button to assign a user to common groups. If you don't do this, or create a user using the useradd command, you won't get assigned to these groups. You're likely not assigned to several other important groups like plugdev, printer, power, netdev, etc.
If you used to start the computer in runlevel 3 (ie, you had to run startx to start the WM/DE), then those groups are assigned automatically for that session. Once you switch the boot process to runlevel 4 (so it boots right to KDM), none of those groups are assigned and it relies on what groups you are a part of.
It would probably be a good idea to add yourself to the other important groups, so you have the access you should.
Code:
usermod -a -G wheel,floppy,video,cdrom,plugdev,power,netdev,lp,scanner hottdogg
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.