ALSA, KDE 3.2, Kernel 2.6 and a wierd problem
Hello Forum ;-)
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