Dean:
thanks for the comments. i've modified my script, and it now looks like this:
Code:
#!/bin/bash
case "$1" in
resume|thaw)
modprobe snd-intel8x0
/etc/init.d/alsasound start
kmixctrl -r
;;
suspend|hibernate)
kmixctrl -s
killall kmix
/etc/init.d/alsasound unload
modprobe -r snd-intel8x0
;;
esac
exit $?
so far, it doesn't seem to work, though.
a couple of questions, perhaps relevant, that have come to my mind:
(1) fiddling with modules usually requires administrator access (su -), but i presume that these hooks are authorized already by means of the way they are created?!
(2) i've tried to remove the snd_intel8x0 module manually, but it still is listed when i list current modules. why? what am i doing wrong? (i switched to the administrator level with su -, then used modprobe -r snd_intel8x0.
(3) should i look at other modules? (modprobe -l snd* lists quiet a lot that seem to be related to sound output)
(4) there is apparently also another module snd-intel8x0m. should i unload / reload that one?