It seems that kde overwrites alsaconf and/or kmix in user mode but not in root mode. Sometimes an sudo alsaconf and reboot works
sometimes not. My chipset/driver of the soundcard: intel8x0 nVidia Corporation CK804.
In many forums I found many further suggestions:
1)
rcalsasound stop
alsaconf
rcalsasound start
alsactl store
reboot (warm)
2)
rcalsasound stop
alsaconf
rcalsasound start
alsactl store
reboot (cold)
3)
rcalsasound stop
alsaconf
rcalsasound start
alsactl store
reboot (cold)
4)
uninstall kmix
install kamix
alsaconf
reboot
5)
mknod /dev/mixer1 c 14 16
chgrp audio /dev/mixer1
chmod uog+rw /dev/mixer1
6)
rcalsasound restart
reboot
etc. etc.
All these workarounds does not lead to a stable result.
Does anybody has an idea how to fix the problem definately? (allways having a working kmix or kamix in user mode)
Some further information about my sound system:
rpm -qa | grep alsa
I do not understand what you mean when you state “kde over writes alsa conf and/or kmix”.
Can you say that differrently? Do you mean kmix does not run by default when kde is launched? Do you mean running kde deletes the /etc/modprobe.d/sound configuration file that is setup by alsaconf ?
Please, remember we can not hear the sound from your PC, nor can we see your PC screen.
If you have a problem with your sound, it might also help if you provided the output of a copy and paste of the following command from a terminal (note you need wget installed):
That will give you a URL. Post the URL here. Just the URL.
Also, note if sound works under user “root” but not as a regular user, this could be a permissions problem (although frankly I do not understand what problem you have). Still, did you look at adding your regular user to group audio, per the guidance here: SDB:AudioTroubleshooting - working around a permissions problem - openSUSE being careful to restart after apply that change.
I have read that in other forums: “kde over writes alsa conf and/or kmix”.
I interpret it as follows: starting or closing of kde effects the start script or kmix and/or kamix. The effect is, that kamix or kmix do not start in normal user mode after rebooting.
Concerning:
Also, note if sound works under user “root” but not as a regular user, this could be a permissions problem.
If this is true, then kmix or kamix should never work under a regular user. However, this not the case. Therefore, I could not be a permission problem.
I’m wondering that many contributions of users, forums and usegroups are describing this problem (see the many different suggestions of solving) since open suse 9.0 (even in open suse v 11.1 this problem occurs) independent of the sound chips and drivers. But it seems that there do not exist a principal possibility to solve the problem of loosing kmix or kamix.
and ? did your sound work, or not work, when you ran that script?
and what happens, after booting as a regular user, that you type “kmix” ?
Also, booting and logging into Linux with root permissions is a very bad practise. The practise is so bad, I have a policy of NOT supporting users who do that, so let me know if that is your intention to do (log in X window as user root), as I don’t want to waste your time (nor mine).
Your first post did not make this clear. Rather than “over write”, I think what you meant to say is KDE is not launching kmix when logging on as a regular user. Or is kmix starting, and then being aborted/killed ?
because a lot of alsaconf warm and cold reboots brings it to work.
Okay, but now I rebooted (after doing wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && bash alsa-info.sh), logged in as a regular user and kamix tells me “Did not find any soundcard.”
By the way I have uninstalled kmix because in different forums it was recommended. Then I’ve installed kamix.
Normally, I do not loggin as root. Only if I need to configure hardware or some software.
Yes kde is not launching kmix or kamix.
Definitely, the soundcard-kamix problem is still not solved.
kamix still does not work when I logged in as a regular user.
Another problem that appears when kamix can not start is that
CDROMS are not mounted automatic. K3b does not open CDROMS any more.
However, automatic mount of CDROMS was possible when kamix was running normal under a regular user.