-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dave Jones wrote:
> Had similar problems here after the recent alsa-* updates.
>
> Deleted /etc/asound.state, stopped kmix & alsasound, restart alsasound.
>
> Ran alsamixer to setup various levels (default = mute), then alsactl
> store when levels OK.
>
> Restarted kmix, as it seems to save it's volume levels at kde shutdown.
> Feel free to correct me if I'm wrong with this assumption.
>
> Since doing this my sound levels have remained OK over reboot.
>
> Cheers, Dave
Getting closer. Yes, this solves my problem partially. I stop alsasound,
delete the file (kmix isn't running atm), start alsasound, set levels
and wow, I have sound via both hw:0,0 and hw:0,1.
At this point I can restart alsasound as much as I want, works fine each
time, that is until I reboot ~ then I get the same issue, and restarting
alsasound does not help. I have to go through the same process again.
I did a diff on the old and new /etc/asound.state, the only difference
being the volume level:
beast ~ # diff asound.state.working /etc/asound.state -u
- --- asound.state .working 2006-04-15 14:14:44.000000000 +0000
+++ /etc/asound.state 2006-04-15 14:15:23.000000000 +0000
@@ -14,8 +14,8 @@
comment.range '0 - 63'
iface MIXER
name 'Master Playback Volume'
- - value.0 48
- - value.1 48
+ value.0 45
+ value.1 45
}
control.3 {
comment.access 'read write'
@@ -199,8 +199,8 @@
comment.range '0 - 31'
iface MIXER
name 'PCM Playback Volume'
- - value.0 24
- - value.1 24
+ value.0 22
+ value.1 22
}
control.24 {
comment.access 'read write'
So I guess that proves it's not a corrupted state file either. Damn this
is mind-blowing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFEQQFuCt0ZF9kLPvYRAgMrAKCZ+D2EboUMZ9q7bARqcv9MRf51AgCbBREE
5wwgRiunyL9T5l/jFEPvVQw=
=iDxR
-----END PGP SIGNATURE-----
--
[email protected] mailing list
