alsa settings getting reset.

Message

mlybarger · Post by **mlybarger** » Tue Aug 31, 2004 10:30 am

my alsa volume levels seem to be getting reset when i logout/login of kde particularry (i don't have another wm installed to test). i have alsasound set to start in the boot run level. i also have the following in my /etc/conf.d/local.start to explictly set the volume:

Code: Select all

amixer -c0 set 'Master' 100 unmute
amixer -c0 set Wave'' 100 unmute
amixer -c0 set 'PCM' 100 unmute

there's a bug in the Wave line, but the others aren't getting set either. the problem doesn'/t seem just boot related, if i set the volumes manually after logging into kde, and logout then back in, the volume levels are reset. i have the sound server disabled in kde. i'm using kde 3.3.0, but i'm not sure if this behavior happens also in kde 3.2.2. if anyone has some ideas/suggestions, it would be most appreciated.

Thanks!
~mark

Corax · Post by **Corax** » Tue Aug 31, 2004 10:44 am

You could use alsactl. Once you stored your settings with

Code: Select all

alsactl store

(must be root)

you can easily restore them with

Code: Select all

alsactl restore

Besides, since using gentoo-dev-soureces-2.6.8-r2 and the kernel-implemented alsa-drivers, I have the same problem with fluxbox. So this issue might not be KDE-only.

eeknay · Post by **eeknay** » Tue Aug 31, 2004 12:52 pm

uhm, i have the same problem, and the store function DOES not work.

mlybarger · Post by **mlybarger** » Tue Aug 31, 2004 4:45 pm

for me the store and restore does appear to store and restore values, but when i log out and back into kde, the values are blanked out. i can manually run alsactl restore to set the values to the latest store. i think it writes these to some /etc/asound.state file or somesuch.

i'm using kernel 2.6.7-r13 or somesuch. i have stayed away from the 2.6.8 series untill it stablizes. i am using the kernel supplied alsa drivers. i have some yamaha card for doing the audio. i'm using the snd-ym<insertsomethinghere> driver. i think i have oss emulation turned on b/c xmms has output set to oss.

i'll turn oss completely off and see how that is handled.

update -

i tried out kde 3.2 and the volumes don't get reset on logout/login. i also tried fluxbox and the volumes stay the same. it seems like a bug in kde 3.3.0. my machine is now in the process of downgrading kde back to 3.2.3. some reason the 3.2.3 kde didn't seem to work very well after the upgrade to 3.3.0. maybe it's the automatic cleaning that happens now in portage. i thought a big advantage of portage was the slots thing so i could have multiple version of a program installed, but now portage wants to auto clean? enough of the rant.

eSinner · Post by **eSinner** » Thu Sep 02, 2004 2:32 am

I have a similar alsa problem. My sound levels arn't being restored to what they were before the previous shutdown/lougout of KDE. It is only happening since the upgrade to KDE 3.3.0, as in 3.2.3 it didn't do this. What annoys me most is that on login a have a sound event playing, which half way through boost the volume to insane levels. If anyone has any idea how to rememdy this, I'd love some assistance.

On the slots thing, I'm pretty sure portage only allows slots with some programs. Things like KDE, Xorg and such will not allow you to have multiple instances installed at the same time. That's why when there's an update for kde, and the command "emerge kde" is issued, it will install the new one, and remove the old one regardless of whether you told it to "upgrade only" or install a new version. Perhaps I am wrong on this, but that is how I have come to understand it.

joefish · Post by **joefish** » Sat Sep 04, 2004 5:41 am

I had this porblem on all versions of KDE 3.2.x It is also happening to me on 3.3.0

GentooSamurai · Post by **GentooSamurai** » Mon Sep 06, 2004 9:05 pm

eeknay wrote:uhm, i have the same problem, and the store function DOES not work.

I am having this same problem my alsa settings stay in place untill I reboot my computer, I am running KDE 3.2.3 after rebooting I have to run this commnd from a root# to get sound working again amixer set Master 100

eeknay · Post by **eeknay** » Mon Sep 06, 2004 9:14 pm

this is a really weired problem...maybe someday we'll figure it out.

GentooSamurai · Post by **GentooSamurai** » Mon Sep 06, 2004 9:38 pm

I just did a search for this type of bug on bugs.kde.org and didn't really come up with any thing that directly pertained to this problem, but this is what I found when I did a search http://bugs.kde.org/simple_search.cgi?i ... ting+reset

devast · Post by **devast** » Mon Sep 06, 2004 11:24 pm

Well i think i had the same problem with 3.2.3... if the kde restart only resets the PCM OR the master volume you can try to disable the sound system in the kde control center, i know there was a switch in 3.2.3 in that panel wich muted the master or the pcm for me(at default), but in 3.3.0 i can't find that switch so i only disabled the whole sound system ( i don't use artsd nowdays, altough i have the arts USE flag).

Good luck

joefish · Post by **joefish** » Tue Sep 07, 2004 2:30 am

The solution is to open kmix, and under 'settings', turn off the option that loads volumes on startup.

GentooSamurai · Post by **GentooSamurai** » Tue Sep 07, 2004 4:02 am

joefish,

I made sure that load volume at startup was unchecked under the configure mixer optio, & I stillhave the same problem

Corpse2 · Post by **Corpse2** » Tue Sep 07, 2004 9:27 am

you can put this

Code: Select all

amixer -c0 set 'Master' 100 unmute 
amixer -c0 set Wave'' 100 unmute 
amixer -c0 set 'PCM' 100 unmute

in you local.start file.

It should solve it, but it would be better if alsmixer did remember it by his own.

GentooSamurai · Post by **GentooSamurai** » Tue Sep 07, 2004 9:55 pm

Corpse2,

Thank you very much that solved the problem for me & just in case other do'nt know the local.start file is in /etc/conf.d/local.start

mlybarger · Post by **mlybarger** » Tue Sep 14, 2004 3:03 am

i'm still havinng this problem ( different machine, still on kde 3.3.0).
logging out/in of kde resets the volume levels. trying to start kmix says:

Code: Select all

mark@robusta Velvet Revolver $ kmix
kmix: ERROR: snd_ctl_open err=No such file or directory
kmix: ERROR: snd_ctl_open err=No such file or directory
mark@robusta Velvet Revolver $ kmix -v
Qt: 3.3.3
KDE: 3.3.0
KMix: 2.1

deepwave · Post by **deepwave** » Mon Oct 04, 2004 12:05 am

Thanks for the solution joefish. Heck, I didn't even think that KMix could do that reset volume on login. Evil! I dream of the day, when all this aRts nonsense will disappear and go way forever.

norikage · Post by **norikage** » Wed Oct 06, 2004 4:03 pm

I had the same problem and i'm not using kde. Though some parts are install as dependencies for apps. I found the answer in this thread. I used alsamixer to set everything as I wanted. then I did what Corax said to store settings with alsactl store. Finally I restore the settings with alsactl restore in /etc/conf.d/local.start with the tip from Corpse2 and everything works ! Thanks Corax and Corpse2 !

bruor · Post by **bruor** » Fri Oct 29, 2004 3:48 am

ok, im runnign 2.6.7-r14 adn kde 3.3.0, i never previously had this problemwith kded but now i am seeing it, all alsa volumes are muted on login, i am using alsactl to store and restore volume levels at command and just to test, if i login to gnome after a reboot, the alsa levels are fine, only when i am logging into kde do the alsa levels get set to completely off.

the only workaround i could find was to use kmix at startup to set a level for the mixer. this is annoying.

just as well to test i set the volume in kde, logged out and logged into gnome and the volume is the same level it was, this is definately a kde 3.3 login issue, whether it be arts accessing alsa etc, im not sure...

alsa settings getting reset.

alsa settings getting reset.

KDE 3.3.0 Login Sound Boost

Thank you

Had similar problem but solved!