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.
Hi all there, I did a fresh slack64 14 (no multilib) install and right after I moved to current.
After reboot the system looks ok, except the volume icon on the kde bar indicates no volume (silence) but sound comes out the same. I click to set the volume and the PCM slider is gone.
The only solution is kill kmix and restart it. Click on the icon and now PCM slider appears and I can control the volume no problem.
This happens every time I boot.
My system:
Code:
Linux darkstar 3.8.13 #1 SMP Mon Sep 17 13:38:05 CDT 2012 x86_64 Intel(R) Pentium(R) 4 CPU 3.06GHz GenuineIntel GNU/Linux
Fri May 3 03:23:05 UTC 2013
ap/alsa-utils-1.0.27-x86_64-1.txz: Upgraded.
Added rc.alsa-oss script, disabled by default so that applications that try
to use OSS compatibility when they could be using ALSA won't steal exclusive
access to the audio device.
Obviously the default config in KDE needs to be changed. This is the danger of using -current.
If you want it to work the way it did previously, you need to enable the new rc.alsa-oss script.
From the Changelog:
Obviously the default config in KDE needs to be changed. This is the danger of using -current.
If you want it to work the way it did previously, you need to enable the new rc.alsa-oss script.
thx rkelsen, but re-enabling the rc.oss script didn't solve the issue. I still have to kill kmix and run it again for each boot
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.