SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Well, as the topic says, I recently (overnight) upgraded from Slack 9.1 to 10 using swaret. My sound card was working just fine in 9.1, but now when I try to use something like, let's say alsamixer, I get this...
alsamixer: function snd_ctl_open failed for default: No such device
I also ran alsaconf and it can't find any cards. I have no idea if this has anything to do with it, but I checked my hotplugs blacklist and my soundcard was still in there.
So...can someone help me help Slack find my soundcard?
i had this problem when i upgraded a box from 9.1 to 10. the way i solved it (which, incidentally, is a solution i have found to work for most alsa problems) was to remove the 4 alsa packages (drivers, oss, lib, and utils) and then reinstall them. so, download those four slack packages from one of the mirrors, then fire up package tool, remove the four and then reinstall them. after that, run alsaconf, alsamixer and alsactl store...and you should be fine
i know this seems like a rather window-ish solution, however it seems to be the most effective when dealing with alsa issues. every kernel upgrade and kernel recompile i've vere done has resulted in having to remove/reinstall alsa. i am assuming i am not the only one with these experiences, if however, i am, i would be interested in hearing how others deal with alsa...
friendly_guy - i suggested downloading the packages because i didn't (and still don't) know if Psyddicus has the Slack 10 cd's or not. he doesn't say if he did his swaret uprgade online or with the discs. either way, i agree with Jong, if all you have is the 9.1 cd's then you definitely want to get the new packages.
As for the "no sound" problem, this always happens after a kernel compile. There is no need to uninstall ALL of them either. All you need to do is uninstall the alsa-driver package and then reinstall. This has been covered so many times, it makes my head spin... But, yea, thats what I do after a new kernel compile as well... When you re-compile your kernel, you are deleting your /lib/modules/<uname -r> directory and starting fresh. Thats why your sound doesn't work anymore... All your sound modules and config files just got wiped clean.... The alsa-driver package replaces all those... I think the kernel and alsa teams aught to get together and decide to put these modules somewhere else or come up with a solution somehow. Ussually, after a kernel compile (version upgrade), the sound modules wont work anyway even if they did get left so it doesn't matter.....