SlackwareThis Forum is for the discussion of Slackware Linux.
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.
First of all I want to state, that I use Slackware for about 4 weeks now and I am more than happy with it. It is exactly the way I always wanted SuSE to be (used SuSE for around 9 month) and how Linux should (IMHO) be. The installation was very smooth and easy and upgrading KDE and installing a custom kernel was challenging, but after it was done I was just happy, wiser and a bit proud of myself ;-)
Long story short: I installed, learned and am happy :-)
However, there is a small problem with my soundchip I am not able to solve on my own:
The soundchip and mainboard in question is a C-Media CMI9739 on a MSI-Neo2 i865G board. The soundchip works without problems on my SuSE 8.2, and it also works under Slackware. My problem is, that whenever I start X (and KDE) I need to remove all soundmodules , start alsaconf and only then I have sound.
When I first noticed that behavior, I thought it might be aRts's fault, but now I uninstalled it and still the same problem. When I boot up and my rc.local is executed, the settings of the alsamixer are 'correct', but as soon as I start X (and KDE) the settings are 'wrong' and I need to remove all modules, start alsaconf and only then my sound will work correctly.
Just in case no one knows what I can do, is there a way to execute my remove script and alsaconf in the background after KDE has started ?
If I can provide any further debugging help please just ask and I will post it.
Thank you for you help,
 This is my shellscript to remove the modules:
 This my rc.local (from *sigh* As I am not allowed to post URLs yet:
amixer set Master 90% unmute
amixer set PCM 90% unmute
If I understand your problem correctly, when you launch KDE your mixer settings are getting changed to where you have no sound....
I know that by default KDE wants to load specific mixer settings at start up. You shouldn't have to remove any of your sound kernel modules. If you just fire alsamixer and change it back to the way you like, then go into the KDE control panel under Sound --> Mixer, there is a button to save current mixer settings. There is also a check box to load mixer settings at start up. You can probably just uncheck that box and that way KDE won't try to mess with your settings when it starts up. I know had a similar problem on my sound card (Gametheater XP cs46xx) KDE messes up the left/right balance to where I only get sound out of the right channel. I reset my mixer to my "right" settings then clicked the "Save Mixer" button in the control panel in KDE.
Thank you. I will try to tweak my setting further, but thanks to your tipp I was able to activate the sound for xmms, although the KDE sound does not work. That is not really a problem, as I am not too keen on KDE's Beep's and Tuut's ;-)