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.
I have Slackware64 Current, pulseaudio / ALSA, and alsamixer, with this configuration. Until a few days ago I could use alsamixer to change change volume, the change was immediately effective for all applications using sound, and life was good. Then a few days ago I upgraded pulseaudio from 14.0 to 14.2, and alsamixer stopped working: pressing the up and down arrows no longer changes either the volume or the colored bar representing the master control. Other mixers (f.i. pavucontrol) seem to have a similar problem, basically the cursor is stuck at whatever level was set at boot. This happens as root as well as my regular user, and downgrading pulseaudio to 14.0 and rebooting restores everything to a working state.
I couldn't get it working for a while either. I took a close look at the man page, and saw alsamixer or alsamixergui opens on card 0. This is not a problem until you have more than 1 audio card; as I do. aplay -l shows I have audio on my Nvidia card, and I audio on the system board. The Nvidia card is 0, the default. I'm using card 1 the analog card on the system board.
So, alsamixer -c1 works, as does alsamixergui -c1.
Long story short, check aplay -l and make sure you are trying to use it with the correct card.
Hope this helps. ( yes, I'm on current fully updated to Jan31. )
While I do have a second on board card (disabled in BIOS), ID games don't seem to be the problem here. The output of aplay -l (and aplay -L) stays the same after the upgrade. This is the output of alsa-info.sh with pulseaudio 14.2, the one I posted above is with pulseaudio 14.0. Ignoring the garbage caused by different installation times etc., the difference seem to be only in some levels:
Answering my own question: this is actually in the PulseAudio FAQ: alsmamixer doesn't work since making the pulse plugin the alsa default. TL;DR: the volume for PulseAudio is now 16 bits, so you now have to use the keys 1-9 if you want useful values out of alsamixer. Because, you know, why not break all ALSA mixers out there.
Last edited by lcd047; 02-18-2021 at 09:43 AM.
Reason: better wording
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.