Bug 628003 - Internal mic on Dell E6510 not functioning (Codec: IDT 92HD81B1C5)
Summary: Internal mic on Dell E6510 not functioning (Codec: IDT 92HD81B1C5)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-27 16:10 UTC by Dylan R. Semler
Modified: 2011-06-28 13:51 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
: 699978 (view as bug list)
Environment:
Last Closed: 2011-06-28 13:51:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Contents of /proc/asound/card0/codec#0 with options snd-hda-intel model=dell-s14 (7.99 KB, application/octet-stream)
2010-08-27 16:10 UTC, Dylan R. Semler
no flags Details

Description Dylan R. Semler 2010-08-27 16:10:45 UTC
Created attachment 441551 [details]
Contents of /proc/asound/card0/codec#0 with options snd-hda-intel model=dell-s14

Description of problem:
The internal microphone on the Dell E6510 does not work.  I have adjusted the mixer levers and ensured that the capture device is not muted.  When attempting to record an audio file, no sound is captured.

Version-Release number of selected component (if applicable):
kernel: 2.6.33.8-149.fc13.x86_64
alsa-plugins-pulseaudio-1.0.22-1.fc13.x86_64
report-plugin-localsave-0.14-1.fc13.x86_64
alsa-lib-1.0.23-1.fc13.x86_64
alsa-utils-1.0.23-3.fc13.x86_64
alsa-firmware-1.0.23-1.fc13.noarch
alsa-lib-devel-1.0.23-1.fc13.x86_64
alsa-plugins-pulseaudio-1.0.22-1.fc13.i686
alsa-tools-firmware-1.0.23-1.fc13.x86_64
report-config-localsave-0.14-1.fc13.x86_64
alsa-lib-1.0.23-1.fc13.i686

How reproducible:
Always

Steps to Reproduce:
1. Turn on computer with an IDT 92HD81B1C5 Intel HD audio device (e.g. Dell E6510)
2. View mixer levels and verify that capture devices are not muted
3. Attempt to record a sound file using (e.g. using audacity)

Actual results:
No sound is recorded

Expected results:
The sound picked up by the microphone is recorded

Additional info:
The microphone can be made to work by adding the following line to a modprobe.conf file:
options snd-hda-intel model=dell-s14

With this option set, the microphone works as expected and sound can be recorded.

$ lspci -vvv
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
	Subsystem: Dell Device 040b
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 32
	Region 0: Memory at e9660000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: HDA Intel
	Kernel modules: snd-hda-intel
01:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1)
	Subsystem: Dell Device 040b
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at e3080000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: HDA Intel
	Kernel modules: snd-hda-intel

Comment 1 Dylan R. Semler 2010-09-02 13:05:20 UTC
Problem still exists with kernel 2.6.34.6-47.fc13.x86_64

Comment 2 Nate P. 2010-10-26 19:23:09 UTC
Confirming that by adding the following line:

options snd-hda-intel model=dell-s14

to /etc/modprobe.d/dist-alsa.conf fixes the issue completely for me as well.

Running kernel 2.6.34.7-61.fc13.x86_64

Comment 3 Reinout van Schouwen 2010-11-01 09:40:17 UTC
Duplicate of bug 616197. Confirming this problem still exists on Fedora 14 and the solution from comment #2 is correct!

Comment 4 Reinout van Schouwen 2011-04-27 12:27:38 UTC
I can't reproduce the problem in F15 beta.

Comment 5 Bug Zapper 2011-05-31 15:18:18 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Nate P. 2011-06-05 04:38:26 UTC
Confirming that this issue is no longer present in the Fedora 15 Final release.  This bug can be closed.

Comment 7 Bug Zapper 2011-06-28 13:51:56 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.


Note You need to log in before you can comment on or make changes to this bug.