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.
I have a Creative Sound Blaster Audigy. I was using Slack 9.0 and ran
swaret --update
swaret --upgrade -a
This upgrading about 400 megs of packages, including the Kernel. After doing this, my sound no longer works. When starting KDE here is a message I get:
---
Informational - artsmessage
Error while initilizing sound driver:
device /dev/dsp can't be opened (no such device)
The sound server will continue, using null output device.
---
Where do I begin troubleshooting this problem? I'm asking here because I seem to remember Slack 9.1 has a big change in the way in handles sound, in preparation for the 2.6 kernels.
do you have a safe version of your kernel you can revert to? otherwise, i guess recompiling with support for your sound setup might be one option.
it's weird that should happen, though, because afaik the kernel is included by default in /etc/swaret.exclude. if you changed that, i would change it back ASAP to exclude the kernel from updating in the future.
In the past with other distro's I have generally have a very difficult time configuring sound, often having to compile the newest Kernel and build sound port right into it (ie not a module). Even this did not always work first try.
I was shocked and impressed when Slack 9.0 detected my sound without telling me, without asking questions, without anything.
Can't I get it to 'do that' again, however it did it in the first place?
When you upgraded the kernel, I would guess you upgraded kernel-modules too?
I'm pretty sure that emu10k1 is loaded as a module in
/etc/rc.d/rc.modules.
In the past, when upgrading the kernel and modules (which I prefer to do manually) I swap the rc.modules.new for rc.modules, being careful to comment/uncomment the same lines I had done previously. Shouldn't require recompiling the kernel (unless you want support for your soundcard in the kernel).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.