On Friday 03 December 2004 10:43 am, you wrote: > I had a different sound issue, where my blacklisted modules where being > loaded by 'discover' long before I wanted them to be. > > Adding the line 'skip modulename' to /etc/discover.conf was all I needed > to get the module to quit loading... > > For my sound to work I had to actually load it from an init script last > (right before kdm). I also call aumix at this time to restore my mixer > settings. > > This might be a solution for you as well... if the same script loaded > you sound modules and called aumix on success... > > I would also check to see if there is a module option you can load the > module with that would set your levels. > > Best of luck, > E > Hi
Thanks a lot. You did lead me to the solution after all.Great. Discover was what was loading that esssolo1 in the first place. Now that I plugged in the line skip esssolo1 It wont load. Now, I took out the blacklist from HotPlug, just to see if it behaves the same way, and as it turnes out, if hotplug loads the module, I dont have the same problem with the MIC. So after all, I dont even need to use the aumix solution. The problem was that discover loaded the module with the MIC set loud, and hotplug doesnt do that. Great. I will include a bug report to Debian. Thanks for all your help Bence > -----Original Message----- > From: Benedek Frank [mailto:[EMAIL PROTECTED] > Sent: Friday, December 03, 2004 10:51 AM > To: p; [EMAIL PROTECTED] > Subject: Re: MIC's loud and Speaker screams when sound module loads. > Why? > > On Friday 03 December 2004 05:52, p wrote: > > On Thu, Dec 02, 2004 at 01:11:43PM -0800, Benedek Frank wrote: > > > > __deletia__ > > > > > Can you tell me, when the recompile is done, what do I do? How do I > > > insert the module late, when KDM starts? Write a little script like > > > > > > modprobe esssolo1 > > > > > > ??? > > > > // > > > > insmod <name of module> > > > > kthxbye. > > > > b. > > > > // > > Hi > > I got somewhat further. Now, I established that aumix in fact works, > just not > early enough. If I set the name of the file under /etc/rd.2/S20aumix to > S10aumix, it will load sooner, and the screaming goes away sooner too. > It is > almost acceptable now. However I would still very much like to know what > > loads the esssolo1 module. I blacklisted it, and I blacklisted all the > other > sound related things, snd_es1938. > > Now, the snd_es1938 wont load, and that is half success. However the > esssolo1 > loads, even blacklisted. Upon boot, it shows, that essolo1 and e100 > (ethernet) are the only two modules that load prior to Hotplug's > execution. > What on earth loads those two modules? It says "Hardware detection" > right > before they are loaded. > > THanks > > Bence -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]