![](https://seccdn.libravatar.org/avatar/d991d5ad7afad8ce9bebef1463891ddf.jpg?s=120&d=mm&r=g)
As far as I concern, if SuSE didn't reflect ALSA changed labeling option in its /etc/modprobe.conf or modules.conf - it's a bug on SuSE's side. Alex -------------------
On 11/14/2003 11:14 PM, Alex Daniloff wrote:
I found it very interesting, I compiled ALSA as modules in the kernel, but sound didn't work, snd-cmipci module was bitching about unrecognized options in modprobe.conf. As soon as I commented out the options for snd-cmipci in /etc/modprobe.conf my sound start working like a charm. It looks like snd-cmipci module from the plain 2.6.0-test9 kernel doesn't understand customized options put by SuSE into original /etc/modules.conf file. Go figure...
Actually, ALSA changed the option labeling, dropping the snd_ before
(i.e. snd_enable is now just enable). It isn't some SUSE thing, it was an ALSA thing, which according to their web site was for consistency
with the kernel.
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com