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.
Can you turn it up in runlevel 4 KDE, or is the device just not being read properly?
See I figured that the problem had something to do with Session Manager and that it was restoring your sound level to a low state. I don't think the Session Manager is active in runlevel 3, but in 4 it is.
The session manager is active in runlevel 3 as well, but your advice is still good -- you should check anyway specialized. Try running `alsamixer` in a console and make sure the volume is turned up, and try playing with the 'M' key (it mutes/unmutes it -- 00 is supposed to be unmuted, but some sound cards interpret it as the opposite. Play around with both settings to see if the sound works). If you can hear sound after playing with alsamixer (press Esc twice to exit), type `alsactl store` as root to save the changes. You may also wish to try running `alsaconf` if you can't get it to work.
Can you please post the output of `lsmod | grep snd` in runlevel 3 (when the sound is working) and in runlevel 4 (when the sound isn't)? The output of `lspci -vv` would also help.
Wait, I thought you said your user was already a part of the 'audio' group. Did you only check this in runlevel 3 before?
By the way, to add a user to a group, don't use
usermod -G group username
(as Melkor's post #28 says)
Instead use
Code:
gpasswd -a username group
The first one makes your user just a part of the groups listed (other than initial group), while the second command simply add your user to that one group. You can also just modify /etc/group.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.