On 07/08/2009 12:31 PM, Maxim Wexler wrote:
The very first thing to try is to change your /etc/conf.d/alsasound so
that it has these two lines:

# Deprecated options:
# Upstream feels, and we wholehartedly agree, that this was a silly idea
UNLOAD_ON_STOP="no"
KILLPROC_ON_STOP="no"

May not help, but that change should be made in any case.


Definitely related to alsa. I deleted alsasound from runlevel boot(why
does the doc insist on putting it there?) and it shutdown normally.
And why the huge raft of drivers for such simple hardware, just two
ports? My desktop has all the bells and whistles and doesn't use half
the drivers of the little netbook

UPDATE Just rebooted and ran lsmod. The modules with the string
'_hda_' in the middle are still loaded. Some of the others, like
'snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device' are gone. Except
for 'snd_pcm, snd_timer, snd'; they're still loaded. The logic, if
any, of what's going on escapes me. If I turned off alsa in rc-update
why should it still load some of the modules. They're not it
modules.autoload.d.

Read through /etc/conf.d/alsasound and look at the environment variables
that are set in that file.  LOAD_ON_START, for example changes the way
/etc/init.d/alsasound behaves.

If it's set to 'yes' then the script does a modprobe -c and greps thru
the output for sound modules and then loads them.  It's all quite well
done for my purposes, but YMMV.


Reply via email to