Red Hat Bugzilla – Bug 520402
no mic input on thinkpad t61
Last modified: 2010-06-02 08:50:16 EDT
Description of problem:
I'm running the latest F12 rawhide bits and my sound works but the Mic is not being picked up for some reason. Everything works just fine though in my F11 install; on the same system. Both F11 and F12 are bare-metal installs
Version-Release number of selected component (if applicable):
Linux cward.englab.brq.redhat.com 2.6.31-0.125.4.2.rc5.git2.fc12.x86_64 #1 SMP Tue Aug 11 21:00:45 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
rpm -qa pulseaudio
rpm -qa alsa\*
lsmod |grep hda
snd_hda_codec_analog 78528 1
snd_hda_intel 31528 3
snd_hda_codec 80448 2 snd_hda_codec_analog,snd_hda_intel
snd_hwdep 9792 1 snd_hda_codec
snd_pcm 90360 3 snd_hda_intel,snd_hda_codec
snd 74776 11 snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
snd_page_alloc 10464 2 snd_hda_intel,snd_pcm
Let me know what else i can provide to debug this issue.
Please use "gnome-volume-control" and select which input should be used for recording.
I appreciate the response. I have only one input mic and it is selected.
Are you sure?
The mic selection drop-down menu is not shown at all if you only have exactly one mic port on a specific sound card. Which makes your comment a bit strange? How can you say something is selected that is not shown? Could you please attacha screenshot?
Created attachment 359414 [details]
volume control input tab
input tab. 1 of 1 option selected.
rpm -q --whatprovides `which gnome-volume-control`
Created attachment 359415 [details]
volume control hardware tab
here's the hardware tab, 1 output / 1 input.
Let me know if i've filed this under the wrong component; if gnome-media is where the problem is by chance
I can confirm this. I have a t61, and I have 'Analog Stereo Duplex' selected on the hardware tab and 'internal audio analog stereo' on the input tab. Tapping next to the microphone shows no response at all on the input level meter.
Thanks for the confirmation. I hope this issue gets fixed relatively quickly; i need my mic :) I'm still confused about comment #3 though, why it seems like the UI i'm looking at is different from the one Lennart is looking at.
(In reply to comment #8)
> Thanks for the confirmation. I hope this issue gets fixed relatively quickly; i
> need my mic :) I'm still confused about comment #3 though, why it seems like
> the UI i'm looking at is different from the one Lennart is looking at.
Nah, your input tab shows no dropdown for selecting the input. WHich is expected if you only have a single input.
Could you please do a "alsactl init", then please attach the output of "pacmd ls" and "amixer -c0" here. Then, please play around with "alsamixer -c0" and try to enable the mic input by some means. Then, please do another "alsamixer -c0". This should tell us which control you changed.
This is most likely just a mixer initialization issue, so we need to figure out what exactly gets misinitialized.
I have to say i have no idea what i'm doing here, but i got it working. I'm going to restart and see if it still works... and if it's broken, try to reproduce the fix again. But in the mean time...i'm spill the beans about what i know. Basically, it seems the following turned things on.
amixer -c1 cset name='Capture Switch',index=1 values=on,on
The only difference between the amixer output though from when it wasn't working to when it was ...
[cward@cward ~]# diff amixer.out*
< Front Left: Capture 45 [83%] [9.00dB] [on]
< Front Right: Capture 45 [83%] [9.00dB] [on]
> Front Left: Capture 54 [100%] [22.50dB] [on]
> Front Right: Capture 54 [100%] [22.50dB] [on]
I'll attach all the relevant output.
Created attachment 359550 [details]
Created attachment 359551 [details]
amixer (broken config)
Created attachment 359552 [details]
amixer (working config)
Jumped the gun, obviously. Restarted, tried the same command and mic isn't working... continue the debug
okay, so the magic wasn't in the random command i issued (probably badly anyway) but it was with the initial `alsactrl init`
I restarted again and checked that mic wasn't working. Then i issued only alsactrl init and checked again. It's working. I recorded a test file to be sure. Works fine and dandy...
Lennart, final conclusion for the day. diff between amixer out BAD and WORKING (after `alsactrl init` only).
Simple mixer control 'Input Source',0
Items: 'Mic' 'Internal Mic' 'Mix' 'Docking-Station'
< Item0: 'Mic'
> Item0: 'Internal Mic'
So 'Mic' is not working but when Item0 is 'Internal Mic' it is, apparently.
Ah, nice. This is very helpful!
Could you please grab this file:
and stick it into /usr/share/pulseaudio/alsa-mixer/paths/analog-input.conf.common?
Then, please restart PA (try pulseaudio -k). Now you should have the input dropdown menu populated and can easily switch between the internal mike and the one you can plug in.
The fix is now in PA git, will enter rawhide as soon as I do another upload.
Yup. Works. Will my selection of the preferred mic save as default? i guess I'll see when i restart next...
Yes, it will be saved. If it isn't it's a bug.
I'm running pulseaudio-0.9.16-13.test7.fc12.x86_64 and mic isn't working at startup still. I have to run alasctrl init.
Same symptom. There's only one option available in the sound config
Let me know what other info u need / things i can try
Seems the file provided in comment #17 which i had installed has been reset back to it original state (must have done so during last update). When updating the file again to the one provide in comment #17, things work as expected when i load gnome.
So will close this again.
The file is not yet updated in the PA version in rawhide, but is upstream. As soon as I upload a new snapshot this will be fixed inr awhide.