RE: MIC's loud and Speaker screams when sound module loads. Why?
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
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,
From: Benedek Frank [mailto:email@example.com]
Sent: Friday, December 03, 2004 10:51 AM
To: p; firstname.lastname@example.org
Subject: Re: MIC's loud and Speaker screams when sound module loads.
On Friday 03 December 2004 05:52, p wrote:
> On Thu, Dec 02, 2004 at 01:11:43PM -0800, Benedek Frank wrote:
> > 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>
I got somewhat further. Now, I established that aumix in fact works,
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.
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
sound related things, snd_es1938.
Now, the snd_es1938 wont load, and that is half success. However the
loads, even blacklisted. Upon boot, it shows, that essolo1 and e100
(ethernet) are the only two modules that load prior to Hotplug's
What on earth loads those two modules? It says "Hardware detection"
before they are loaded.
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact