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.
Hi, I have seen alsa drive some people crazy, and now it is my turn...
Here is the situation. Installed Slackware 10.2 with 2.4 kernel. I then compiled and installed my custom 2.6.14 kernel, configuring yes to alsa support, and my soundcard. Also installed udev and hotplug before I rebooted. Making sure udev is executable. So, after reboot everything is fine, except that there is no sound.
I run alsaconf, and it seems to find my soundcard. It writes some lines to modprobe.conf. Then I run alsamixer to tune the settings, and get "function snd_ctl_open failed for default: No such file or directory". And when starting KDE I get the message "Error while initializing the sound driver: device /dev/dsp can't be opened (No such file or directory)".
As far as I can see, the 2.6 kernel autoloads the correct modules for my soundcard. The problem seems to be that there are no sound devices created by udev in the /dev directory. So I then tried to create these devices by hand with help of the snddevices script found in the alsa driver source. Then I got no errormessages anymore, but still, no sound could be heard. And after a reboot, the devices were no longer there, of course. Back to square one again.
I have read a bit about reinstalling alsa-drivers, utils, and libraries after a custom kernel compile. However, what exactly does the alsa-drivers package do? Are they not just the alsa kernel modules for all soundcards? Which I configured and compiled in the kernel already. Look at my lsmod, the modules are there and loaded.
What do I need to do? This really drives me crazy...
Originally posted by Macky I have read a bit about reinstalling alsa-drivers, utils, and libraries after a custom kernel compile. However, what exactly does the alsa-drivers package do? Are they not just the alsa kernel modules for all soundcards? Which I configured and compiled in the kernel already. Look at my lsmod, the modules are there and loaded.
You are right. You don't need the alsa-driver package if you've compiled your own kernel.
The other two - alsa-utils and alsa-libs should be installed already.
Got the sound to work, suddenly. I manually executed "udevstart", and the neccessary sound devices got created. Sound worked perfectly in KDE after that. So I guess that for some reason, udev fails to recognize the alsa sound kernel modules at boot. Maybe because the autoloaded alsa modules are delayed in their initialization... and simply not finished by the time udev is executed?