How To Restart Sound After Hibernation / Suspend To Disk?

I'm currently trying to figure out how to prevent my sound card from stopping to work after going into hibernation / suspend to disk mode.

Since I need to first brush up on the issue, I first need to be able to restart the sound card manually after hibernation (to save the the trouble of having to reboot every time, which defeats the purpose of hibernation ...)

Could someone tell me how to do this? Is there a particularly process that needs to be restarted?

Cheers

**** ludens

You wouldn't happen to be using a DELL Inspiron 1420, would you?

Oh, sorry, I forgot to paste my technical data ... :

Panasonic Let's Note CF-Y2 (I think that model is called a ToughBook outside of Japan)
CPU: Intel Pentium M processor 1.50GHz
Display: Intel 855GM Chip set, SXGA+ (1,400x1,050) 14.1 inch TFT
System: openSUSE 10.3 (i586)
KDE: 3.5.7 "release 72"

Check out my howto:
http://www.suseforums.net/index.php?showtopic=50527
With the help of some forum members we were able to do it for my sound card. Since I don't know anything about your hardware you may have to change the driver that's loaded and unloaded. Also please file a bug report.

trippinnik:

Thanks for the link, will look into it later today.

Cheers

Ok, I've tried trippinnik's solution, but so far no success. I suppose I need to modify the hook somehow, could someone help me with it? I posted some questions below.

For reference, here is trippinnik's code:

#!/bin/bash

case "$1" in
** resume|thaw)
******modprobe -l 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 $?

My questions:
(1) Does the order of 'resume|thaw' vs 'suspend|hibernate' matter? Should suspend come first?
(2) What is the command modprobe -l snd_intel8x0 supposed to so? (In my understanding, modprobe -l lists modules, so perhaps the '-l' shouldn't be there?)
(3) What does the last line 'exit $_?' do? Is it necessary? The example hook at http://en.opensuse.org/Pm-utils doesn't contain that line ...
(4) Under Yast2 > Sound, my driver is listed as 'snd-intel8x0' (a hypthen instead of the underbar). Which one is correct? (I tried the hook of course with the changed name, but it didn't work either, so I'm at a loss ... )

I helped trippinnik with this script. The basic framework is based on scripts located in '/usr/lib/pm-utils/sleep.d' for suse 10.3.

Should look like:

#!/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 $?

The 'modprobe -l snd_intel8x0' line should be 'modprobe snd_intel8x0'. The '_' character gets parsed as '-', so that is ok.

A most interesting thread ....

How much of this thread is applicable to the following wiki:
http://en.opensuse.org/S2ram

Does this wiki need a big update as a result of the work in this thread?

Edit - there is even an openSUSE-10.1 Nvidia suspend how to, full of a zillion caveats about its applicability to other SuSE versions.
http://en.opensuse.org/NVidia_Suspend_HOWTO

Dean:

thanks for the comments. i've modified my script, and it now looks like this:

#!/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?

(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? [/b]

Removing sound modules is always difficult, IMHO, ... often a device will be using the sound module, which can make the removal success less than problematic.

For example, if you type:
<span style="font-family:Courier New">rcalsasound restart</span> to restart afterward.

Also, I know NOTHING about suspend/resume on laptops, so I will gracefully bow out of this discussion, and hope you can sort this. Good luck!