[SOLVED] Microphone problem with Dell Latitude 5410

[aus9]

EDIT
ahh found specs

http://www.dell.com/downloads/global/products/latit/en/latitude-e5510-e5410-specsheet.pdf

It claims you have a digital mic....well we have a problem

either your bios is playing up or is not set
or
your webcam module is not loading correctly

[jur]

Code: [Select]


tc@box:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 
Bus 001 Device 003: ID 0c45:6419 Microdia
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:0020 
tc@box:~$


[aus9]

grrrr


ok I have another suggestion but this is little long so bear with me

1) you have a module loaded which is uvcvideo

and guess what I have the same...but I run Debian normally and it has a package called
guvcview

here are some screenshots that might tease you but I am sure you know why I am showing you



yep I can see the lsusb id

and



tells me the name of cam and I can choose its inbuilt mic or the normal mic

2) If interested you need to build it from source as I can not see in repository

I can build it using deb packages but I am not allowed to submit it as its not built from source so anyhows

source is

http://guvcview.berlios.de/Doc.html

3) I have not looked at the other webcam apps in that repository but I am keen to see your id
then knowing your id
make sure we load the correct module
then hopefully we get alsamixer to give us a mic switch

[aus9]

you could put in a request for an extension here?

http://forum.tinycorelinux.net/index.php?board=46.0

[jur]

I hacked the debian package using Jason's script:

Code: [Select]

tc@box:~$ guvcview
guvcview 1.4.5
video device: /dev/video0
Init. Laptop_Integrated_Webcam_2M (location: usb-0000:00:1a.0-1.4)
.
.
.


vid:0c45
pid:6419
driver:uvcvideo
checking format: 1196444237
VIDIOC_G_COMP:: Invalid argument
   compression control not supported
fps is set to 1/30
drawing controls

fps is set to 1/30
no codec detected for H264
no codec detected for MP3 - (lavc)
Checking video mode 640x480@32bpp : OK
 Could not grab image (select timeout): Success
using device id:1
[code][/code]

[jur]

Haven't gotten anything out of the mic yet.

[jur]

The audio panel in guvcview also has a /dev/dsp for input - that is shown as id 0 while the intel-hda is shown as id 1. So it would appear the digital mic has someting to do with /dev/dsp?

[Rich]

Hi jur

So it would appear the digital mic has someting to do with /dev/dsp?

That certainly would not be unreasonable since DSP's are specifically designed to handle real time tasks
such as audio and video processing in the digital domain.

[aus9]

ok thanks for that but can you be explicit about the guvcview .....tab audio  what options do you have.

I used mtpaint.....file pulldown  actions...time delayed snapshot

2) your specs claim you have a digital mic but aplay -l so far does not show it


3) why not try the model= stuff from your link and see if we can get to it?

4) google suggests your webcam could be

0c45:63ea   Laptop Integrated Webcam 2M (found in Dell Studio 1555 notebooks)   Sonix Technology

http://tips-linux.net/en/linux-ubuntu/linux-driver/webcam-linux-drivers

or

0c45:6450  Laptop_Integrated_Webcam_2M from microdia

http://hardware4linux.info/component/43921/

[jur]

ok thanks for that but can you be explicit about the guvcview .....tab audio  what options do you have.

The options I already mentioned... id=0 is /dev/dsp and id=1 is the intel hda as in the pic posted. No other info shows up at all, nothing. The id numbers I got from terminal as I ran guvcview from a terminal so I could see the output (posted above as well). There is no webcam option in the audio tab. So I guess the conclusion must be, the mic is NOT a part of the webcam, explaining the webcam's absense in alsamixer and guvcview.

2) your specs claim you have a digital mic but aplay -l so far does not show it


3) why not try the model= stuff from your link and see if we can get to it?

I tried by adding that line to alsa.conf and adding it to backup, and tried 2 different options but it did not produce a result. I worked through the wiki but it was not  clear to me how to do it, so I punted with /usr/local/share/alsa/alsa.conf. [/quote]

4) google suggests your webcam could be

0c45:63ea   Laptop Integrated Webcam 2M (found in Dell Studio 1555 notebooks)   Sonix Technology

http://tips-linux.net/en/linux-ubuntu/linux-driver/webcam-linux-drivers

or

0c45:6450  Laptop_Integrated_Webcam_2M from microdia

http://hardware4linux.info/component/43921/

Well as you already know, microdia shows up in lsusb! When I googled microdia, the only thing I found had to do with flash mem and readers, so I concluded that is referring to the built-in card reader. So if microdia IS the webcam, where is the card reader? So microdia is the webcam, apparently.

But what about guvcview showing the mic as /dev/dsp?

[jur]

While guvcview was running I thought I would record something with the capture buttons, but it segfaulted. I also tried skype and arecord but same results as before.

[aus9]

I am off to work but will give you step by step manual model stuff tonight after work.

Does this webcam work for any other distro other than msoft?

[aus9]

hi

steps to change alsa model....note...... won't help with webcam

I am not sure what persistence you have on your hard drive, so opt may be on your hard drive or not

1)  Do all the commands with root powers please

2) edit your /mnt/somewhere/boot/grub/menu.lst kernel line so it reads

kernel /boot/bzImage blacklist=snd_hda_intel (plus any other stuff)

If paranoid reboot to check you have lost sound otherwise continue until (5) for full reboot

3) edit with root powers the file called bootlocal so it reads....plus other stuff you have there


##!/bin/sh
  - put other system startup commands here
/sbin/modprobe snd_hda_intel model=dell-s14
/usr/local/etc/init.d/alsasound start
/bin/sleep 5


4) If you have an etc/asound.state in your backup file for /opt/.filetool.lst
use root powers to delete that line

if you have used a personalized alsamixer settings file.....rename it and delete its entry from your filetool.lst file please


5) Now do a full reboot...not a logout ok

6) Now as a local user....run alsamixer and see if you have a new setting for digital mic or not
or other changes

7) If something new appears....it could be good so adjust your mic level, activate etc....unmute etc, raise volumes etc

then try out arecord and aplay

then save those settings as new file by running command

sudo alsactl -f /home/tc/asound.state store

Then (assuming you saved new file) we use root powers to

add that file to your backup so /opt/.filetool.lst has new entry

home/tc/asound.state

----depending on whether you have home in your persistence settings or not

AND

we need to restore those sound settings for alsa .....with root powers we add a line to bootlocal (3) so it now reads
##!/bin/sh
  - put other system startup commands here
/sbin/modprobe snd_hda_intel model=dell-s14
/usr/local/etc/init.d/alsasound start
/bin/sleep 5
/usr/local/sbin/alsactl -f /home/tc/asound.state restore

(This only becomes effective on full reboot)

------------

if that did not work then swap a new model number.......... model=auto

then we get ugly and try a codec thats not yours

model=dell-m6-dmic

(this allegedly gives you digital mic but belongs to codec for STAC92HD73*

then try

model=dell-m6

[jur]

OK you did it! 

dell-s-14 did the trick. I did try it last night with a modprobe but that didn't work. I know really nothing about modprobe.

There are fewer sliders on alsamixer, eg there is only one capture. It still has 'mic' and 'front mic'. 'Front mic' is probably the socket as 'mic' did the trick.

guvcview looks identical as before in the audio tab. skype mic works.

Thanks for staying the distance aus9! You could probably paste a bunch of stuff into the wiki.

[aus9]

hi
You could probably paste a bunch of stuff into the wiki.

me thinks you think it needs improving?

feel free to edit the wiki or
pm with what you did not like and I will see ok?