media-sound/alsa-utils-1.0.24.2-r1 has "modprobe -l" in /etc/init.d/alsasound This option is not existing anymore in kmod's modprobe. Also Debian manpage says: -l --list List all modules matching the given wildcard (or "*" if no wildcard is given). This option is provided for backwards compatibility and may go away in future: see find(1) and basename(1) for a more flexible alternative.
media-sound/alsa-utils-1.0.25 just updated this package, but nevertheless there is also modprobe -l in /etc/init.d/alsasound
+*alsa-utils-1.0.25-r1 (20 Feb 2012) + + 20 Feb 2012; Tony Vroon <chainsaw@gentoo.org> +alsa-utils-1.0.25-r1.ebuild, + +files/alsasound.confd-r4, +files/alsasound.initd-r5: + Use -I option on alsactl restore to avoid aborting unnecessarily, as per Adam + Nielsen in bug #281631. libsamplerate is both a build & run time dependency, + as per Albert W. Hopkins in bug #403557. Remove unsupported autoload/unload + as it breaks with kmod, as per Ulenrich in bug #404535. The unsupported broken functionality has been removed from the ebuild. Thank you for your bug report.
Created attachment 303863 [details] Modified 1.0.24 init script - using "find" instead of "modprobe -l" With the init included in alsa-utils-1.0.25-r1 oss modules aren't loaded.
Created attachment 303865 [details] Config for the attached init
Created attachment 303867 [details] Config for the attached init
The attached patches will not be accepted as the functionality in question has been removed.
When Alsa crashes or freezes, it's very convenient to be able to do '/etc/init.d/alsasound restart'. Is that functionality kept? On Fedora, which I also use, this is impossible, and I have to restart the computer. Do you recommend not using modules for Alsa?
(In reply to comment #7) > Do you recommend not using modules for Alsa? The use of modules for ALSA is not a supported configuration. If you want to use it anyway, *you* are responsible for making sure modules are loaded & unloaded. If the sound driver and hardware state can desync badly enough to cause a "crash", that is a bug which should be reported upstream so that it can be investigated and fixed. Not hidden by repeatedly restarting the driver.
I agree that bugs should be reported (and fixed), and I do so. But in the mean time, restarting Alsa is very convenient. Convenient is a nice feature! I'll probably move away from modules now, if only to get easier updates. Thanks for your answer!
