The newly stabilized alsa-utils says: Moving old alsa configuration in modules.d to new location in modprobe.d in /etc/ However when I invoke alsaconf it still writes stuff to the depreciated location under /etc/modules.d/alsa. I know from alsa guide that the module handling should now be done by udev, but without copying the information from /etc/modules.d/alsa to /etc/modules.d/modprobe.d/alsa I get this annoying message at re-starting the alsasound init script. * Could not detect custom ALSA settings. Loading all detected alsa drivers. Sorry if this has been reported anywhere else but there are that much alsa bugs that I gave up searching at some point.
This one is related to bug 245879, documentation-wise to bug 223885 and tracked under bug 215626. It therefore should probably be closed as duplicate of one of these bugs.
no, one is a tracker for these bugs, and the other two aren't related. this is kinda annoying now since alsa-utils dies in pkg_setup about a file that is created by alsaconf, part of alsa-utils.
+ 04 Aug 2009; Samuli Suominen <ssuominen@gentoo.org> + +alsa-utils-1.0.20-r4.ebuild, +files/alsa-utils-1.0.20-modprobe.d.patch: + Fix alsaconf to write /etc/modprobe.d/alsa.conf instead of + /etc/modules.d/alsa wrt #251081.
