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.
Hello, if anyone could help me with this I would appreciate it.
I installed Slackware 9.1 a few weeks ago. I am very happy with the distro thus far but ran into a snag this morning. I ran the following
Swaret --update
Swaret --upgrade -a
The program ran fine and I only had it look in the 9.1 FTP database.
After it finished downloading and installing 18 packages, I rebooted.
I don't remember what packages and don't know where to go look to find out but I know that an ARTS upgrade was one of them.
Anyway, now when I start X I get an error message stating:
Error While initializing the sound driver
Device DEV/DSP cant be opened (no such device)
the sound server will continue using the null output
I also tried gnome and it says that no sound devices exist.
I looked and /dev/dsp points to /dev/dsp0 and both files exist.
They have full permissions as well
I also ran alsaconfig and it probed for cards and found none
Sound has always worked fine until now. It was working right before I upgraded with swaret.
I am lost here. Any help would be much appreciated as I do not want to reload Slackware from scratch for something this goofy.
I am assuming all was well until you did the swaret upgrade? If that is wrong let me know.
What output do you see when you type lsmod as root in a console? If that is blank none of your modules are loaded and hence your sound card module is not loaded.
I, too, have an assumption. When you ran 'alsaconfig', you meant to say 'alsaconf' - right? If not, I'd recommend you try alsaconf because I believe THAT program is the official graphical setup program bundled with 9.1
I recommend that you get slapt-get instead because Swaret is out of date and really doesn't work as well as slapt-get. Also, if you can, try getting the alsa packages and the tools, programs, and etc. manually so that you can avoid any conflictions related to system files/dependancies etc.
alsa was probably upgraded... you will need to do some searches on your video card, to see what steps you should take.
First try running alsaconf, see if it detects a card.. if it does continue on with alsamixer and unmute everything. and see if you can get sound working.
if not...
post the output of lspci, and lsmod. that should give some starter information to point you in the right direction.
I had this same problem after running swaret about a month ago. I ran a few searches on google and many people suggested upgrading to kernel 2.4.24 via Swaret. I did that and sound worked again.
Originally posted by Ninja Cow I had this same problem after running swaret about a month ago. I ran a few searches on google and many people suggested upgrading to kernel 2.4.24 via Swaret. I did that and sound worked again.
Good point. If swaret upgraded alsa then it might have removed the old alsa-driver package, which is the kernel modules, and installed new files. The old ones would have been somewhere down in /lib/modules/2.4.22 and the new ones would be in /lib/modules/2.4.24. On reboot the system would not have been able to modprobe the sound modules from /lib/modules/2.4.22 since they would be gone. An upgrade to kernel 2.4.24 and a reboot would have the modules loading from /lib/modules/2.4.24. Since the sound was working before an upgrade, upgrading the kernel to 2.4.24 would be the first thing to try if it isn't installed. What does the command uname -r show?
I tried everything above, and my sound still wouldn't work after I ran swaret. So I ran 'swaret --remove alsaX' (replace x with the name of the alsa package), then from the command promt I mounted slackware disk 1, and typed 'cd /mnt/cdrom/slackware/ap',
and ran './install-packages', and selected all alsa packages. Then I did the same for '/mnt/cdrom/slackware/l'. Then I ran 'alsaconf', 'alsamixer', and 'alsactl store', and I had sound back.
Noah
Originally posted by njbrain I tried everything above, and my sound still wouldn't work after I ran swaret. So I ran 'swaret --remove alsaX' (replace x with the name of the alsa package), then from the command promt I mounted slackware disk 1, and typed 'cd /mnt/cdrom/slackware/ap',
and ran './install-packages', and selected all alsa packages. Then I did the same for '/mnt/cdrom/slackware/l'. Then I ran 'alsaconf', 'alsamixer', and 'alsactl store', and I had sound back.
Noah
Nice job, Noah. I am sure this will help others. =D
I tried the same thing when upgrading to current, though. Didn't fly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.