In a recent change in Tumbleweed, somthing seems to have changed with the default values of pulseaudio’s mixers: My speakers buzz with ear-bursting sound as soon as the sound driver is set up. Using alsamixer, which lets you pick out single channels for volumes, I found out that all input/output sliders are at the maximum, and an entry “front mic” is, as long there is no mic connected, the reason for this distortion.
I would now like to mute this channel systemwide as a default. However, I’m not so competent in Linux’ sound mess pulseaudio/alsa, so I really don’t have the slightest idea where I can do this. KDE/phonon not even gives me any possibility to do this on a per user base. alsamixer lets me do it, on the command line, but any setting is lost with the next reboot.
Any help appreciated!
You could search pavucontrol for a configuration that might allow you to do this.
Alternatively, just physically unplug the front mic. It is the front and not the back mic … (no ? )
The speakers are buzzing as long as no mic is connected. As soon as I connect something to the jack, everything is fine again.
Might it also be considered an error that all channels, also the recording inputs, are initialized at maximum gain?
There is a bug report raised on the 3.0 kernel (I think) because it has this behaviour. Perhaps with you using Tumbleweed with the 3.0 kernel you have encountered that bug.
Does not the work around (to physically unplug the mic) work ?
Please, NEXT time post on the Tumbleweed forum area if you are using tumblweed.
I am going to close this thread and move it to Tumbleweed area (in about 20 minutes) . Please, do NOT reply to this thread until after it has been moved. I need 20 minutes for this post warning NNTP users to make it out the NNTP gateway (before I move the thread). I request all NNTP users look for this thread in the Tumbleweed area.
Thank you for your patience and understanding.
This thread was previously in the Multimedia area, but the user has Tumbleweed on their PC, and I believe this to be a Tumbleweed / 3.0 kernel issue. Hence the thread has been moved to Tumbleweed. Users (both WEB based and NNTP) are invited now to reply to this thread. I quoted the original post in the thread so that NNTP users have a ‘hook’ in which they can reply.
My problem that I don’t know any way how to mute single channels in a openSUSE/pulseaudio situation, however, is not Tumbleweed specific. So you can see it both ways ;). Didn’t yet know that it was Tumbleweed-specific when posting.
It probably is NOT Tumbleweed specific, but you did state this …
Ergo it was introduced with a recent Tumbleweed recent change …
Now I have read complaints of users in the Pre-Release-Beta forum area who noted this with the 3.0 RC7 kernel. Tumbleweed has a 3.0.0.39 kernel currently …
But its pretty clear to me this does not belong in Multimedia based on what I have been reading on all our forums for the past few months.
The general rule of thumb is if you have problem with audio that comes with the kernel (and in this case alsa sound driver comes packaged with the kernel) and if your kernel version (which provides the audio) is NOT a stock kernel (and Tumbleweed is not) then such a post should be in Tumbleweed (if you are using Tumbleweed kernel) or in Pre-Release/Beta if using a non-standard kernel newer than what comes with openSUSE-11.4.
IMHO Tumblweed is where you have a FAR better chance of getting the correct reply.
… anyway, … none of this exchange between you and me is solving this problem.
What might be useful would be to find the bug report that I recall being mentioned in a Pre-Release/Beta thread on the 3.0 kernel.
See post #5 in this thread: Kernel 3.0
Thanks for the link. Concerning the interaction Kernel/Alsa, Pulseaudio and then Phonon if you use KDE, it’s rather hard to find out the real culprit if something goes wrong…
Obviously no kernel developper uses sound on intel hd, because this error renders the system pretty unusable concerning audio :(((.