thatguy
n00b
Joined: 18 Feb 2003
Posts: 13
|
 Posted: Thu Jun 12, 2003 9:59 pm Post subject: alsasound loses settings: possible "fix" |
 |
|
If alsa appears to mute all channels on every reboot and you added alsasound to the boot runtime level and you notice a message at startup that says something like "ALSA driver is already running" then you can try to modify the alsasound script not to quit when this happens. If you look at the first if statement in /etc/init.d/alsasound you'll see that it tests if the driver is already loaded. If it is, the script exits with a fail value(1).
| Code: |
# Start driver if it isn't already up.
#if [ -d /proc/asound ]
#then
# eerror "ALSA driver is already running."
# return 1
#fi #
# insert all sound modules
#
|
Of course, this early exit means the script never reaches the part farther down where your settings are restored. (to store them in the first place, use alsamixer, or whatever else to save your levels, then do ) So an ugly hack is just to comment out the first if statement and any code related to loading drivers that appear to already be loaded. Now when you reboot, the script will proceed through the section that calls alsactl restore, and your levels will no longer be muted on every boot. The ALSA guide claims that if you add alsasound to the boot run level, you shouldn't have to add any additional sound modules to /etc/modules.autoload, but I have found this not to be true...
I had previously listed the path to the alsasound script incorrectly, sorry for any confusion |
|
Multimedia
