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.
have you upgraded your alsa-* packages? (alsa-lib, alsa-utils, alsa-oss)?
I belive willysr is referring to the alsa-* packages in the testing/linux-2.6* folder of the slackware directory. This is a must if you are using 2.6 kernel.
right, but there are different binaries to use with the 2.4 kernel then the 2.6 kernel. The default alsa binaries are for the 2.4 kernel. If you are using the 2.6 kernel, you need to use the alsa binaries from the testing/Linux-2.6.*/ directory which is called alsa-driver-1.0.10_2.6.15.3-i486-1.tgz as apposed to the default alsa-driver-1.0.10_2.4.32-i486-2.tgz in the '/l' directory. alsa-lib and alsa-utils are not kernel specific.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.