Lenovo ideapad S10 internal microphone doesn't work

[brianhanna]

Binary package hint: alsa-base

In Intrepid and Jaunty Alpha 2, the internal microphone on the Lenovo ideapad S10 doesn't work.

After quite a bit of searching, I suspect this machine has a different pin-out from other machines with the Realtek ALC269 codec.

Under Jaunty Alpha 2, I tried all of the options for model that I could find in the alsa-base file.

Using "options snd-hda-intel model=eeepc-p703" seemed to make the mic work using sound recorder but caused other problems (such as no Master channel to control speaker volume). In the default setup, everything seems to work except the internal mic. The internal speakers work but attempting to use the internal mic causes feedback through the speakers

Under Intrepid, even the keyboard hotkeys worked to control the volume. This is broken under Jaunty alpha 2.

Expected behavior - internal speakers work and volume can be controlled with keyboard hotkeys. internal speakers disconnected when headphone plugged in and headphones work. Internal and external microphones work.

Please let me know if I can provide more info.

[brianhanna (brianhanna)]

I just figured out this is fixed upstream. After updating to alsa 1.0.18a, everything works. Hopefully the updated version of alsa can be incorporated before Jaunty release?

[Luke Yelavich (themuso)]

Could you please try and update to the latest jaunty kernel, and check whether the microphone works? There is a chance the fix went into a recent kernel upload, and there have been a few kernel updates since Jaunty alpha 2.

Thanks.

[brianhanna (brianhanna)]

Problem is still not fixed in Jaunty Alpha 3. Updating ALSA to 1.0.18a fixes it. Apparently the newest ALSA has not been incorporated into the kernel.

[Dernhelm (dernhelmspublicaddress)]

Jaunty Alpha 5 didn't have this problem until a recent update—now the keyboard volume controls don't work anymore. And I have ALSA 1.0.18 installed.

[gritty (kent-uoregon)]

I am using:
$ apt-cache policy alsa-base
alsa-base:
  Installed: 1.0.18.dfsg-1ubuntu5
$ apt-cache policy alsa-utils
alsa-utils:
  Installed: 1.0.18-1ubuntu10

I ran the following to upload some information for you to reference.
$ bash utils_alsa-info.sh
ALSA Information Script v 0.4.56
...
My ALSA information is located at
http://www.alsa-project.org/db/?f=5d5f87aded9e5bedd99906741e83e76ce5de3383
...

I am running:
Ubuntu-Netbook-Remixx 9.04 (Jaunty Jackalope) Daily Build
jaunty-netbook-remix-i386.img 17-Mar-2009 03:13

[Morjgus (m-ullmann)]

I confirm this bug for Jaunty UNR final. It is a fresh installation.

The capture tab of alsamixer shows [mic boost] and [internal boost] only.

[Oliver Horn (oliverhorn)]

You should try to add

options snd-hda-intel model=basic

to the /etc/modprobe.d/alsa-base(.conf)

It works beautiful for me.

[Morjgus (m-ullmann)]

Oliver's tip works. Great!

[EAB (adair-boder)]

This is what was in the alsa-base file:

http://pastebin.com/m637a8dae

I changed it with the last line commented out like so:

# options snd-hda-intel model=ALC269

and added your line

options snd-hda-intel model=basic

then I restarted alsa like so

sudo /etc/init.d/alsa-utils restart

and got the following:

 * Shutting down ALSA... [ OK ]
 * Setting up ALSA... Invalid card number.

Then I rebooted the computer and tried to record -- its exactly like it was before. Any thoughts?

(btw, running Jaunty here)

[Sergio Melas (sergiomelas-gmail)]

Worked for me. Great!

[Lucas (lucasmocellin)]

I tried that model-basic, and it *seems* to work.

because I can see at pulse audio server the microphone is working, and when I run skype, this gets the internal mic working, but I cannot hear my voice at skype call test.

alsom, gnome recorder records a lot of noise, I don't know what is going on, I tried to change the preferences/sound back to ALSA, but it didn't work. Now the only option I can use at skype is "pulse" any other I get "audio problems" error message from skype.

any idea?

tks.

[Oliver Horn (oliverhorn)]

Hi,

you have to put Front Mic to 100% and Front Mic Boost to 0% in your HDA Intel (Alsa mixer). Maybe you have to set Recorder to 100% and activate the mic, but it seems like it is tuning itself down while using skype.
Then start skype and set all audio on HDA Intel (hw:Intel,0) and do the test call.

Does it work?

[dpolancom (lospolanco)]

Sry guys I'm a complete newbie and I don't know hot to use Oliver's tip. Could you plz give me some more detailed help?
thx

[dpolancom (lospolanco)]

Oliver's tip worked for me but when I make the test call I hardly could hear my voice back even configurating the mics as Oliver suggested. Any idea of what to do to improve the mic volume?

[ghormax (aisuru2001)]

Oliver's tip also worked for me but created another problem with sound. I get a certain permanent noise level and sometimes a loud ugly shriek (like the brakes of a train). So I removed the line again but my mike doesn't work any longer. Could there not be another way? Eric suggested updating ALSA drivers to version 1.0.20 but unfortunately I do not know how.

[Oliver Horn (oliverhorn)]

Hello ghormax,

do you still have this problem when front mic is turned off?

[dpolancom (lospolanco)]

Hi I have the same problem, and my mic volume is very low even when it's set to max... the line in doesn't work so I can't use headphones or another mic... so i can listen music, but still cannot use skype due the low volume. And I have to turn the mic off coz it produces feedback...
I don't know either how to update the drivers... plz help

[bishops (bashir-saade)]

Hello I have updated my alsa to 1.0.20, and changed the /etc/modprobe.d/alsa-base(.conf) file as Olivier said. My microphone worked for a bit (one day or two) and then something happened (I'm still trying to figure out what) and it stopped working. It picks up sound I can hear it but it does not record and it does not work on skype.
anyone can help?

[palehorse (4-launchpad-net-gourmetgeek-com)]

Okay, I'm going to put my two cents in because I see threads/bugs relating to two related problems but I haven't yet been able to fix both problems simultaneously.

I have experienced the problem regarding the internal mic for the s10e not being available as a recording device which is fixed with:

options snd-hda-intel model=basic

But this creates a different problem whereas the internal speakers do not mute automatically when headphones are plugged in. Which is fixed with:

options snd-hda-intel model=laptop
and this issue is also fixed with:
options snd-hda-intel model=lenovo

However, fixing the headphone sensing problem breaks the recording device problem (as well as all options, switches, etc) leaving only the playback mixers available.

Since these two problems seem to be related I think any solution proposed should only consider this problem resolved if the mic can be used while headphone "sensing" is also functioning.

I would be happy to try any solutions suggested a post back the results in this thread or any other that may be appropriate for those linux geeks who are savvy with this driver but may not have the equipment necessary to test on (s10e, et al).
I am going to post a copy of this message in any thread I can find on launchpad.net regarding this issue in the hopes that this problem can be resolved once and for all for everyone experiencing it.

Thanks, in advance, to anyone who makes an effort on this issue.

[palehorse (4-launchpad-net-gourmetgeek-com)]

Yep, sure enough... Related to Bug #109838
Amongst elsewhere that I've found on the net. This seems to be a pretty common problem. I hope someone has a solution to this.
I'd offer to code if I could but I'm just a glorified keyboard jockey myself.
That being said, anything I can do to help.

[Björn Leder (bjoern-leder)]

I am running Kubuntu 9.04 on a S10. Updating Alsa to 1.0.20 solved the problem for me. After the update you can add additional channels to kmix: 'Capture' and 'Input Source'. The first one has to enabled and the second one can be used to switch between internal and external mic. Both of them are working now with Skype.

[Björn Leder (bjoern-leder)]

I should add, that I did not alter /etc/modprobe.d/alsa-base(.conf).

Also the update procedure for Alsa is explained on their wiki: http://alsa.opensrc.org/index.php/Quick_Install.

[palehorse (4-launchpad-net-gourmetgeek-com)]

Well, while it's not the most elegant solution (I keep hoping that some day Linux won't have that huge gap in learning between Joe-surf-the-net and Ubergeek) it's not so involved that it wasn't doable.
I'm disappointed that this revision hasn't been incorporated into Ubuntu and pushed out as an update yet. I really wish the Linux community would aim toward Apple's "one-button" idea of ease of use along with MS's "our software supports every piece of hardware on god's green earth" level of support (I am aware that MS doesn't code drivers, I'm speaking in terms of the entire platform).
I suppose we should be leaning on the OEM's a little bit more to show them the buying power of the linux community. If their goal really is to sell more hardware, then buying power is everything.
Okay, I'm rambling now. The solution worked wonderfully without modification to the alsa-base.conf file.

Thank you so much!

[EAB (adair-boder)]

palehorse, could you just run me through what you did to fix the issue?

[palehorse (4-launchpad-net-gourmetgeek-com)]

Short answer: I believe I followed these instructions:
http://webupd8.blogspot.com/2009/08/how-to-upgrade-to-alsa-1020-on-ubuntu.html

But as Björn pointed out above, I commented out the lines which I had used previously to specify the model type ("options snd-hda-intel model=basic" et al.) and then I downloaded the source code to alsa 1.0.20 (driver, lib, utils) from here:
ftp://ftp.alsa-project.org/pub/driver/
Then I unpacked them to /usr/src/alsa/

I made sure I had all of the required dependencies by running these commands:
sudo apt-get -y install build-essential ncurses-dev gettext xmlto
sudo apt-get -y install linux-headers-`uname -r`

Then I went into each of the three directories (starting with the driver) and ran:
sudo ./configure
sudo make
sudo make install

Then reboot!
As a precaution, I always make sure I don't do anything else with the computer while I'm building and installing drivers and I don't try to monkey around with injecting the drivers without rebooting.
It all compiled and installed without incident and now the headphones mute properly when I plug them in AND the microphone (as well as all the other sound devices ) are recognized by skype properly.
I did have to go into the volume control in gnome, change the input source to "internal mic" and fiddle with the mixer a little to boost the input but, all in all, it went as smooth as can be.

The downside to this solution which I was alluding to in my previous post is that every time the kernel gets updated by Ubuntu these drivers will have to be rebuilt and reinstalled. This isn't too big a deal though since rebuilding them and reinstalling them is just the 'make' and 'make install' commands from above run again for each of the three components.

And that, my friends, is the extent of my knowledge. Heh. I'm sure there are people on here who can tell you a lot more about this topic than I.
Good luck and remember to report back successes and failures! Only through communication does the community get stronger.

[tekstr1der (tekstr1der)]

FYI, Lenovo S10 internal microphone has been working correctly here for a while now on Karmic.

[EAB (adair-boder)]

Can anyone else confirm that it is now working in Karmic?

[bishops (bashir-saade)]

Yes for me it is working on Karmic.

[StephenCave (stephencave)]

laptop works fine under xp skype etc but but no microphone under ubuntu skype either!!!
---- bishops <email address hidden> wrote:
> Yes for me it is working on Karmic.
>
> --
> Lenovo ideapad S10 internal microphone doesn't work
> https://bugs.launchpad.net/bugs/312403
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “alsa-driver” package in Ubuntu: Won't Fix
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: alsa-base
>
> In Intrepid and Jaunty Alpha 2, the internal microphone on the Lenovo ideapad S10 doesn't work.
>
> After quite a bit of searching, I suspect this machine has a different pin-out from other machines with the Realtek ALC269 codec.
>
> Under Jaunty Alpha 2, I tried all of the options for model that I could find in the alsa-base file.
>
> Using "options snd-hda-intel model=eeepc-p703" seemed to make the mic work using sound recorder but caused other problems (such as no Master channel to control speaker volume). In the default setup, everything seems to work except the internal mic. The internal speakers work but attempting to use the internal mic causes feedback through the speakers
>
> Under Intrepid, even the keyboard hotkeys worked to control the volume. This is broken under Jaunty alpha 2.
>
> Expected behavior - internal speakers work and volume can be controlled with keyboard hotkeys. internal speakers disconnected when headphone plugged in and headphones work. Internal and external microphones work.
>
> Please let me know if I can provide more info.

[StephenCave (stephencave)]

mic works fine in xp and OK with Skype but using the Ubuntu hard drive - rubbish no sound recorder and it will not work with skype either
---- Zeth <email address hidden> wrote:
> Can anyone else confirm that it is now working in Karmic?
>
> --
> Lenovo ideapad S10 internal microphone doesn't work
> https://bugs.launchpad.net/bugs/312403
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “alsa-driver” package in Ubuntu: Won't Fix
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: alsa-base
>
> In Intrepid and Jaunty Alpha 2, the internal microphone on the Lenovo ideapad S10 doesn't work.
>
> After quite a bit of searching, I suspect this machine has a different pin-out from other machines with the Realtek ALC269 codec.
>
> Under Jaunty Alpha 2, I tried all of the options for model that I could find in the alsa-base file.
>
> Using "options snd-hda-intel model=eeepc-p703" seemed to make the mic work using sound recorder but caused other problems (such as no Master channel to control speaker volume). In the default setup, everything seems to work except the internal mic. The internal speakers work but attempting to use the internal mic causes feedback through the speakers
>
> Under Intrepid, even the keyboard hotkeys worked to control the volume. This is broken under Jaunty alpha 2.
>
> Expected behavior - internal speakers work and volume can be controlled with keyboard hotkeys. internal speakers disconnected when headphone plugged in and headphones work. Internal and external microphones work.
>
> Please let me know if I can provide more info.

[StephenCave (stephencave)]

What is Karmic?
---- tekstr1der <email address hidden> wrote:
> FYI, Lenovo S10 internal microphone has been working correctly here for
> a while now on Karmic.
>
> --
> Lenovo ideapad S10 internal microphone doesn't work
> https://bugs.launchpad.net/bugs/312403
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “alsa-driver” package in Ubuntu: Won't Fix
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: alsa-base
>
> In Intrepid and Jaunty Alpha 2, the internal microphone on the Lenovo ideapad S10 doesn't work.
>
> After quite a bit of searching, I suspect this machine has a different pin-out from other machines with the Realtek ALC269 codec.
>
> Under Jaunty Alpha 2, I tried all of the options for model that I could find in the alsa-base file.
>
> Using "options snd-hda-intel model=eeepc-p703" seemed to make the mic work using sound recorder but caused other problems (such as no Master channel to control speaker volume). In the default setup, everything seems to work except the internal mic. The internal speakers work but attempting to use the internal mic causes feedback through the speakers
>
> Under Intrepid, even the keyboard hotkeys worked to control the volume. This is broken under Jaunty alpha 2.
>
> Expected behavior - internal speakers work and volume can be controlled with keyboard hotkeys. internal speakers disconnected when headphone plugged in and headphones work. Internal and external microphones work.
>
> Please let me know if I can provide more info.

[EAB (adair-boder)]

Maybe try saying more in one post instead of creating 3 posts one right
after the other.
Karmic is the up and coming Ubuntu release.

[Oliver Horn (oliverhorn)]

Its working for me with Karmic UNR.

Good work, thanks! :-)

[vjahns (volker-thalreit)]

The procedure works on a Lenovo ideapad S10e + ubuntu 9.04.

Helpful in activating the microphone has been the website at http://idyllictux.wordpress.com/2009/04/21/ubuntu-904-jaunty-keeping-the-beast-pulseaudio-at-bay/ .

Great work!

[Darik Horn (dajhorn)]

This bug is resolved on my hardware since at least the Maverick release. Last activity has been more than a year ago, so perhaps this bug should be closed.

[Gary M (garym)]

 Does anybody with a Lenovo Ideapad S10 and karmic/lucid/maverick still have the microphone problem or still need a "options" line in the alsabase file?

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.