On 06/08/07, Denis Crowdy <[EMAIL PROTECTED]> wrote: > > Amos Shapira wrote: > > On 05/08/07, Denis Crowdy <[EMAIL PROTECTED]> wrote: > >> I'm sure this has worked for me in the past (distant though), but now I > >> just get a long list of "module is in use" messages, despite trying to > >> shut down everything that might be using the card. I have tried fuser, > >> and the entries under /dev/snd, also to no avail. > > > > > > "module is in use" can (always?) come from other modules using it. Try > to > > rmmod other modules which might use it. > Is that a simple case of grepping the output from lsmod? Here's the > output of "lsmod | grep snd": > > snd_hda_intel 21912 2 > snd_hda_codec 205056 1 snd_hda_intel > snd_pcm 79876 2 snd_hda_intel,snd_hda_codec > snd_timer 23684 1 snd_pcm > snd 54020 8 > snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer > soundcore 8672 1 snd > snd_page_alloc 10888 2 snd_hda_intel,snd_pcm
I don't remember whether I had such a problem before (a module not giving the names of modules which use it). Maybe repeated "modprobe -r" of all snd* modules might help. From googl'ing around it looks like such a situation indicates a bug in the module. Try maybe digging the kernel Bugzilla or the ALSA project web site (alsa-project.org). --Amos -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
