Created attachment 521099 [details]
output of alsa-info.sh with "internal" mixer level set to 0
Description of problem:
The volume level for the internal microphone is set to 0 for a Conexant CX20561 (Hermosa) audio device on a Lenovo X200. The result is that the internal microphone captures audio at very low volumes, even with the PulseAudio mic volume setting at the maximum level.
Appropriate volume levels can be achieved by going through alsamixer, switching to the "HDA Intel" device by pressing F6, and increasing the "Internal" mixer level.
The default level of the internal microphone should be set to an appropriate value, not 0.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot Computer with Conexant CX20561 (Hermosa) audio device (e.g. Lenovo X200)
2. Open Sound settings from "System Settings" window.
3. Navigate to "Input" tab.
4. Set Input volume to maximum value
5. Observe that a maximum of only a couple bars of the input level ever become filled when talking into the microphone
6. Open alsamixer
7. Press F6 and switch soundcard to "HDA Intel"
8. Switch to the "Internal" mixer and raise the volume to an appropriate level
9. View the Sound settings again and observe acceptable input levels.
By default, the internal microphone appears not to work or appears to be very insensitive.
By default, the internal microphone should work at appropriate volume levels.
This issue is reported on the Linux bug tracker as well as the Red Hat Enterprise Bugzilla
Created attachment 521100 [details]
output of alsa-info.sh with "internal" mixer level set to 72
Same behaviour in F16-beta
I confirm it on F16 final and Thinkpad X301. Very annoying to be obliged to pass through alsamix every time I log in (since the internal mic is muted at every login). Anybody knows how to save the setting, at least?
I wrote a little shell script that simply runs amixer with parameters. Works fine for me but definitely not a solution. I don't know the exact parameters anymore but you'll definitely find the information you need in the ALSA-Wiki.
Is this still an issue in the 3.3 kernels in F16?
Yes, the issue still persists with kernel 3.3.7-1.fc16.x86_64.
...and also in 32-Bit: 3.3.7-1.fc16.i686.PAE
The same happens here: Fedora 16 kernel 3.4.7-1.fc16.x86_64. Every time I boot my machine I have to manually invoke 'alsamixer -c0 -Vcapture' to increase internal mic volume
# Mass update to all open bugs.
Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.
Please retest with this kernel, and let us know if your problem has been fixed.
In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with. Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.
If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
Just did the Kernel update and rebooted two times. No change unfortunately: The internal mic keeps being muted also with Kernel 3.6.2-1.fc16.i686.PAE
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.