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 run into problems using sound/mixer in users other than "root," (like I did) you might want to type chmod # /dev/dsp and chmod # /dev/alsamix into the terminal where the # is your user that you want to give priveledges to. Of course, this is a "just in case" scenario, and you need to run alsaconf first :-D
i've actually had some pretty odd errors with alsa!
actually, wouldn't call it an "error", it just doesn't work. I alsaconf > alsmixer > alsactl store'd, but nothing. it worked fine with 10.0, though, so I have no idea what's wrong. going to try compiling the 2.6.10 kernel + alsa stuff myself, I guess. see what happens.
but it sure seems kinda arbitrary in the working area. =/
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.