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.
If you enable all of the correct features of ALSA in the kernel, then technically, anything that uses ALSA should work properly. However, I had great difficulty getting non-ALSA-based programs (read: anything using SDL) to work at all. I ended up removing everything except basic sound support (the 'soundcore' module) from the kernel and then compiling ALSA from source. This seemed to offer a more consistent result for me.
If you do end up compiling ALSA into your kernel, you might want to consider removing any of the installed ALSA packages as you might end up with conflicts.
Originally posted by Makaelin am I correct in assuming that I can remove the dev package?
If you are talking about the kernel config option for devfs you SHOULD NOT use it. If you are talking about the devs-2.x.x-noarch-x package installed with Slackware then you SHOULD NOT remove it either as it is required for the 2.4.xx kernels. Unless I'm out of my reckonin', that is what populates the /dev directory when you boot to a 2.4.xx kernel. Udev will live side-by-side with it and won't cause any problems as devs isn't used with a 2.6.x kernel and udev ain't used with a 2.4.xx kernel.
Quote:
Originally posted by Makaelin Second, if I enable all the ALSA features in the kernel, what additional packages will I need to have for sound?
As far as alsa goes, I've always had the best luck compiling it as a module, rather than compiling it into the kernel. That way if something ain't right I can do "lsmod" and see the loaded modules. If you compile it into the kernel they won't show up (as they ain't modules). The main thing is to select which driver(s) you need and, again, have them compiled as modules. However, leave OSS deselected. It is depreciated and alsa actually has an oss compatibility library (alsa-oss) that you can download and compile from source for those programs that still depend on OSS stuff, namely any programs that require /dev/dsp and such. All of the main alsa library files are installed with Slack (alsa-lib, alsa-utils and alsa-oss) and I think that, even with Slack 10.0, it is alsa 1.0.8 (but I can't remember right now). After you recompile the kernel and boot to it you may want to download the alsa-driver-1.0.8 file from The ALSA Project and compile it according to the howto (also to be found on their site) for your card/chipset.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.