Click to See Complete Forum and Search --> : aumix forgets settings -- MDK9.1 -- is there a fix?


Satur9
08-10-2003, 07:16 AM
Hi all,

I've searched long and hard for an answer -- through this board, through Google Linux and through various other forums -- and yet still there is no definative answer.

How do you get aumix to remember your settings in Mandrake 9.1??

I know that MDK9.1 sets your sound setting to "mute" by default, and that's no big deal. The problem is that no matter what I do to change the settings, when I reboot the computer the sound settings are back to muted. This means I have to open aumix every time I reboot and readjust the sound.

I've tried launching aumix as a regular user, as su through konsole, and by logging into KDE as root. I've saved the .aumixrx file to /etc/, and I've saved it in my home directory. I've used alsamixer and kmix instead of aumix. None of them remember the settings.

What's the fix? Does anybody know?

thanks,
Tim

deathadder
08-10-2003, 07:27 AM
ive never had that problem before but when i do a fresh install of debian i always chmod 666 /dev/dsp and /dev/mixer

maybe a chmod 666 /dev/mixer will help

just a guess though

Satur9
08-11-2003, 09:04 AM
Perhaps its portends a greater issue that when I chmod 666 /dev/mixer and reboot the permissions are set back to their defaults. In other words, none of the permission changes I make to /dev/mixer last beyond a reboot. This could possibly be happening on a greater level -- there could be other config files that I'm changing that aren't "remembering" those changes.

For now, the work around I have to the aumix problem is crude but effective. I turned up the volume in aumix and then did a "Save To" and saved the settings as .aumixrc in my /home/user directory. Then I created a aumix.sh file in kedit and added the line "aumix -L /home/tim/.aumixrc" and saved the script to the /home/user/.kde/Autostart directory. This way, everytime I start KDE, it loads the script which loads my saved settings to aumix. It fixes the mute problem, but it's a little aggrevating since the /dev/mixer should be doing that already.

Oh well, it works for now.