Bug 696219 - No sound input using snd-hda-intel
Summary: No sound input using snd-hda-intel
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-13 15:21 UTC by Michael Wiktowy
Modified: 2013-04-23 17:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-23 17:28:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
hardware info included as per instructions at: http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html (25.88 KB, text/plain)
2011-04-13 15:21 UTC, Michael Wiktowy
no flags Details

Description Michael Wiktowy 2011-04-13 15:21:23 UTC
Created attachment 491806 [details]
hardware info included as per instructions at: http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html

Description of problem:
Input mixer does not function correctly. This is a long-standing issue and the mixer has not functioned in any previous kernel by my knowledge.

Normal pulseaudio mixer volume control has a single slider for microphone input that does not allow any microphone input at any gain setting.

Workaround:
pavucontrol needs to be installed and this presents a "Front Left" and "Front Right" Input slider. When these are locked together, they act exactly like the single one (no sound input) but when they are unlocked and one is set to maximum and the other set to minimum, sound input works perfectly. In fact, the gain of the microphone input seems to be correlated to the difference between the two slider settings.

However, any changes to the gain using the normal mixer or automated gain control by VOIP software locks the channels together and reverses this workaround.

This can be worked around more permanently by creating a /etc/modprobe.d/alsa-base.conf file containing the following line:

options snd-hda-intel position_fix=1 enable=yes

This was reported previously at:
http://bugzilla.redhat.com/show_bug.cgi?id=653016

Lennart Poettering suggested that this was a kernel bug and should be reported upstream.

How reproducible:
Always

Additional info:
See attached hardware info included as per instructions at:
http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html

Related Bug:
https://bugzilla.redhat.com/show_bug.cgi?id=620189

Comment 1 Michael Wiktowy 2011-06-10 19:57:37 UTC
The problem remains in F15 but the position_fix workaround no longer works in F15

Comment 2 Josh Boyer 2012-02-02 17:19:06 UTC
Do you still see this with the 3.2 or 3.3 kernels?

Comment 3 Michael Wiktowy 2012-02-05 18:48:48 UTC
The problem continues to exist in the 3.2 kernel that is in a fully updated Fedora 16.

Also the workaround stopped working-around quite some time ago. I can't manually work around this by setting the two mixer slider halves differently since both Skype and Google Talk clients seem to auto-adjust the mic volume and set both halves equal again no matter what I do.

Other than a few other less critical quirks, Fedora 16 runs on this System 76 Starling netbook quite well.

Comment 4 Michael Wiktowy 2012-02-05 19:30:41 UTC
This seems to be the most relevant bugzilla upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=12070

It is discouraging that this issue hasn't been touched in over 3 years.

Comment 5 Fedora End Of Life 2013-04-03 15:36:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 6 Justin M. Forbes 2013-04-05 19:50:39 UTC
Is this still an issue with the 3.9 kernels in F19?

Comment 7 Justin M. Forbes 2013-04-23 17:28:31 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a
response in 2 weeks.  If you are still experiencing this issue,
please reopen and attach the relevant data from the latest kernel you are
running and any data that might have been requested previously.


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