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 just upgrade to KDE 3.2. Now, upon login my sound server won't start up, saying that /dev/dsp doesn't exist or something. Anyone familiar with this problem?
Yes I did run alsaconf as root but it tells me I have no supported pnp or pci cards, then no legacy drivers when it probes for them. I've never had a problem with my sound in Linux before.
I ran sclocate dsp and this is what it gave me...
Alright that is werid but it can be fixed, can you do a "lsmod" for us and tell us the output of that?
I think your sound modules/drivers are not being loaded as a result you have no sound, another question are you running kernel 2.6.x or the basic slackware kernel 2.4.22?
I'm not sure with kernel I have. I just installed Slackware 9.1 a few days ago and haven't updated any system files yet, just programs. Btw, this sound thing started (at least it was telling me) right after I upgraded KDE to 3.2.
I had the same problem when I upgraded to 3.2. I recompiled alsa and everything started to work again. I think its a problem with the alsa packages that were used when compiling KDE, but I can't remember at the moment.
Yep, actually that's what I ended up doing late lastnight. I just downloaded the newest driver, lib, and util from ALSA's website and it works just fine now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.