You are not logged in.

#1 2012-06-01 13:57:25

NorthernLights
Member
Registered: 2011-08-11
Posts: 7

Internal Mic not working

Hey Guys,

I have been trying to get my internal mic working on my laptop for ages now without any success any advice would be greatly appreciated. I have followed the alsa configuration on the arch wiki. I have also looked at the wiki for my laptop https://wiki.archlinux.org/index.php/To … _X505-Q830

The error I get at the pre boot screen says the following
Found hardware "HDA-Intel" "Conexant CX20583 (Pebble HSF)" "HDA:14f15067, 1179ffd5, 00100301" "0x1179" "0xff50"
/usr/sbin/alsactl: setcontrol:1328: failed to obtain info for control #2 (no such file or directory)
/usr/sbin/alsactl: setcontrol:1328: failed to obtain info for control #3 (no such file or directory)

The output of alsa-info script can be found here: http://pastebin.com/XngB9twv

Cheers

Offline

#2 2012-06-01 18:31:04

Pres
Member
Registered: 2011-09-12
Posts: 423

Re: Internal Mic not working

Are you using arecord to test?

Offline

#3 2012-06-01 18:50:04

ConnorBehan
Package Maintainer (PM)
From: Long Island NY
Registered: 2007-07-05
Posts: 1,359
Website

Re: Internal Mic not working

Is it unmuted if you go into alsamixer and press F4?


6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.

Offline

#4 2012-06-01 18:58:38

pvibert
Member
Registered: 2011-07-18
Posts: 12

Re: Internal Mic not working

Also make sure it's set to capture: in the F4 (Capture) section of alsamixer, move to the Capture slider and hit space. Should show CAPTURE beneath the slider.

Offline

#5 2012-06-02 04:37:23

rossmcd
Member
From: Zambia
Registered: 2011-04-13
Posts: 25

Re: Internal Mic not working

Yes. Make sure it's set to capture. Are you using pulseaudio? If so:

# pacman -S pavucontrol
$ pavucontrol

You then click on the "Input Devices" tab of pavucontrol, make sure it looks similar to this:
http://i.imgur.com/edacq.jpg
BTW, I don't use ubuntu. Just light-themes.
Make sure that it is unmuted there, then see if the slider indicating volume level moves. If it does, you're in luck!



-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

Offline

#6 2012-06-02 04:59:50

rossmcd
Member
From: Zambia
Registered: 2011-04-13
Posts: 25

Re: Internal Mic not working

Ok, will not do it again. Sorry about that.

Offline

#7 2012-06-02 05:47:34

pigiron
Member
From: USA
Registered: 2009-07-14
Posts: 150

Re: Internal Mic not working

hmmm... just to further add to the confusion factor...

I went through your alsa-info data... and good job including it in your initial post.

!!Modprobe options (Sound related)
!!--------------------------------

snd_hda_intel: model=dell-vostro

Try changing that ALSA model "quirk" from dell-vostro to hp-laptop.

Next, like Pres is alluding to, use arecord for testing. In your case, use something like this on a command line:

arecord -f cd -vv -V stereo -D plughw:0,0 /dev/null

Even though you're using PulseAudio, that should work with no changes to your ALSA config file. So use it to try recording some sound while looking for a "bouncing" text VU meter. Even though I don't see anything obviously wrong with your current alsamixer setting, try changing some of those controls in another terminal if it doesn't seem to work... while keeping one eye on the arecord VU meters.

And lastly...

The error I get at the pre boot screen says the following
Found hardware "HDA-Intel" "Conexant CX20583 (Pebble HSF)" "HDA:14f15067, 1179ffd5, 00100301" "0x1179" "0xff50"
/usr/sbin/alsactl: setcontrol:1328: failed to obtain info for control #2 (no such file or directory)
/usr/sbin/alsactl: setcontrol:1328: failed to obtain info for control #3 (no such file or directory)

Every once in awhile, the ALSA developers will change the "wiring" involved with Intel HDA chips. So after a system update, the ALSA settings normally saved during a shutdown of your box may become "stale" and therefore start complaining when it tries to read it back during a boot.

There's an easy fix... just fire up alsamixer and verify that the setting are still what you want, then enter this on the command line (with root authority):

alsactl -f /var/lib/alsa/asound.state store

This will overwrite the file with new ALSA settings.

Last edited by pigiron (2012-06-02 05:53:08)

Offline

Board footer

Powered by FluxBB