Bug 1249364 - Lenovo g50-30 with Conexant CX20751/2 audio codec requires the inv_dmic_split hint to be set for the internal mic to work
Lenovo g50-30 with Conexant CX20751/2 audio codec requires the inv_dmic_split...
Status: NEW
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
25
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-01 21:22 EDT by Alexander Ploumistos
Modified: 2017-07-25 15:08 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-04-28 13:16:13 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
ALSA info (28.11 KB, text/plain)
2015-08-01 21:22 EDT, Alexander Ploumistos
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1002978 None None None Never

  None (edit)
Description Alexander Ploumistos 2015-08-01 21:22:44 EDT
Created attachment 1058427 [details]
ALSA info

This laptop is the gift that keeps on giving...

I could not use the internal microphone in Google Hangouts or Skype. If I yelled at it, a slight whisper might be heard. In Audacity it recorded sounds in stereo just fine. It would only work in the other programs if I set the recording channels -left and right- at significantly different levels in pavucontrol.

After a lot of reading, searching and tests, I discovered that the laptop has an inverted internal microphone (whatever that means) and that perhaps sending the parser the inv_dmic_split hint would solve my problem. I used hdajackretask to enable the hint, rebooted and problem apparently solved. Audacity now records a single channel.

I am attaching the output of the alsa-info.sh script with the workaround enabled in case someone upstream cares to take a look at it.

Btw, as you can see in the attachment, the file that hdajackretask created in /etc/modprobe.d/ contains the following line:

snd_hda_intel: patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw

where the pseudo-firmware file has this:

# cat /usr/lib/firmware/hda-jack-retask.fw
[codec]
0x14f1510f 0x17aa3809 0

[pincfg]
0x16 0x04211040
0x17 0x94170110
0x18 0x40f001f0
0x19 0x04a11030
0x1a 0x94a70120

[hints]
inv_dmic_split=yes

Is this repetition normal or should another bug report be filed?

Oh and on a side note, pavumeter does not display signal levels when something is playing on this machine (with or without the workaround).
Comment 1 247395263 2015-09-10 23:16:28 EDT
Can you fix the bug?
Comment 2 Justin M. Forbes 2015-10-20 15:36:57 EDT
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23.

If you experience different issues, please open a new bug report for those.
Comment 3 Alexander Ploumistos 2015-10-30 19:33:13 EDT
(In reply to Justin M. Forbes from comment #2)
> Fedora 22 has now been rebased to 4.2.3-200.fc22.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.

It's still present.

> If you have moved on to Fedora 23, and are still experiencing this issue,
> please change the version to Fedora 23.

Shame on me, I tested TC6 and TC9, but I had forgotten all about this bug so I didn't check. I'll let you know in a week.
Comment 4 Alexander Ploumistos 2015-11-07 19:30:35 EST
Tested on Fedora 23 with kernels 4.2.3-300 and 4.2.5-300, same deal - no fix yet.
Comment 5 Laura Abbott 2016-09-23 15:44:56 EDT
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.
Comment 6 Alexander Ploumistos 2016-09-24 09:00:26 EDT
The bug is still present in F24, with kernel 4.7.4-200.fc24.
Comment 7 Justin M. Forbes 2017-04-11 10:55:33 EDT
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.
Comment 8 Justin M. Forbes 2017-04-28 13:16:13 EDT
*********** MASS BUG UPDATE **************
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.
Comment 9 Alexander Ploumistos 2017-04-28 19:00:05 EDT
Apologies for the delay.

Just tested 4.10.12-200.fc25.x86_64, it still needs the retasking hack.
Comment 10 Fedora End Of Life 2017-07-25 15:04:47 EDT
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora  'version'
of '24'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.

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