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).
Can you fix the bug?
*********** 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.
(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.
Tested on Fedora 23 with kernels 4.2.3-300 and 4.2.5-300, same deal - no fix yet.
*********** 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.
The bug is still present in F24, with kernel 4.7.4-200.fc24.
*********** 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.
*********** 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.
Apologies for the delay. Just tested 4.10.12-200.fc25.x86_64, it still needs the retasking hack.
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.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
No change with 4.13.12-300.fc27.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.15.3-300.f27. 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 experience different issues, please open a new bug report for those.
Running 4.15.3-300.fc27.x86_64, retasking is still required.
*********** 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 27 kernel bugs. Fedora 27 has now been rebased to 4.17.7-100.fc27. 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 28, and are still experiencing this issue, please change the version to Fedora 28. If you experience different issues, please open a new bug report for those.
This laptop is now running kernel-4.17.7-200.fc28, retasking is still required.
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 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. 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 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
Hi, currently on 4.18.12-200.fc28, no change.
Hey Alexander, Would you mind testing https://koji.fedoraproject.org/koji/taskinfo?taskID=30132198 when it finishes building? I took a stab at adding the quirk, but it'd be great if you could check to make sure it works before I send it upstream. Thanks!
Hello Jeremy, I've just tested it and it doesn't work without retasking. Do you need any additional information to help you figure out what could be wrong?
Hmm. Can you try https://koji.fedoraproject.org/koji/taskinfo?taskID=30149762, boot with snd.debug=2 on the command line and attach the output of "journalctl -k --no-hostname"? In theory that should have verbose debug logs.
Created attachment 1492276 [details] System logs without retasking
Created attachment 1492277 [details] System logs with retasking
Didn't work either. I've attached the 4.19.0-0.rc7.git1.1.bz1249364 logs without and with retasking, hope you can get something useful from them.
Okay, it seems like that doesn't actually make it print debugging, so I did more digging and I *think* the way to enable them is by adding: " snd_hda_codec_conexant.dyndbg=+pf snd_hda_codec.dyndbg=+pf" to the kernel boot parameters when you boot that kernel. Sorry :(
Created attachment 1492773 [details] System logs without retasking
Created attachment 1492774 [details] System logs with retasking
(In reply to Jeremy Cline from comment #25) > Okay, it seems like that doesn't actually make it print debugging, so I did > more digging and I *think* the way to enable them is by adding: > > " snd_hda_codec_conexant.dyndbg=+pf snd_hda_codec.dyndbg=+pf" to the kernel > boot parameters when you boot that kernel. Sorry :( No worries, this time there is considerably more audio-related output.
Ah, that's perfect. Can you try https://koji.fedoraproject.org/koji/taskinfo?taskID=30184529? If it doesn't work, please upload logs with the same command line parameters and I'll do some more head-scratching. If it _does_ work, check to make sure the mic mute LED (if the laptop has one) still works.
Created attachment 1493025 [details] 4.19.0-0.rc7.git3.1 system log (without retasking) Well done, this time it works! I am attaching the system log just in case. Will you backport the fix to the 4.18 line as well?
Yay, thanks for sticking with me! I'll submit it upstream and CC it for stable releases. Once the maintainer takes it I'll put into the Fedora stable builds. You'll know it's in a build when the updates system comments on this bug. As long as you're fine with me including your name and email in the patch, I can credit you by adding Reported-by and Tested-by tags[0] to the patch. [0] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes
I almost can't believe that this bug will be closed soon(ish)! Sure, you can go ahead and tag me. Thanks again!
kernel-headers-4.18.14-300.fc29 kernel-4.18.14-300.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-731c2e5ced
kernel-headers-4.18.14-200.fc28 kernel-4.18.14-200.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ef4800cb67
kernel-headers-4.18.14-100.fc27 kernel-4.18.14-100.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-f4bb184a00
kernel-4.18.14-100.fc27, kernel-headers-4.18.14-100.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-f4bb184a00
kernel-4.18.14-200.fc28, kernel-headers-4.18.14-200.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-ef4800cb67
kernel-4.18.14-300.fc29, kernel-headers-4.18.14-300.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-731c2e5ced
kernel-4.18.14-200.fc28, kernel-headers-4.18.14-200.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
kernel-headers-4.18.15-100.fc27 kernel-tools-4.18.15-100.fc27 kernel-4.18.15-100.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ce1ebd480a
kernel-4.18.15-100.fc27, kernel-headers-4.18.15-100.fc27, kernel-tools-4.18.15-100.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-ce1ebd480a
Patch for this issue is _not_ included in f27 builds of the kernel.
kernel-4.18.15-100.fc27, kernel-headers-4.18.15-100.fc27, kernel-tools-4.18.15-100.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
kernel-4.18.14-300.fc29, kernel-headers-4.18.14-300.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.