Created attachment 1729332 [details] Pavucontrol Description of problem: I cannot use internal microphone in any application that requires sound input. Version-Release number of selected component (if applicable): 13.99.2 How reproducible: Simply start any sound recording application, including google chrome and im programs(Microsoft Teams). Steps to Reproduce: 1. Boot up Fedora 2. Start application 3. Actual results: Microphone is listed but muted. Expected results: Microphone should work and works under Windows Additional info: I have installed pavucontrol and I can see my internal microphone being reported as unplugged, which of course doesn't make sense since it's an internal microphone. Default selection is "microphone" which is being shown as plugged in even though I have no microphone plugged in for real. It used to work on Fedora 32 and some kernel versions before the current one. It still works 1 out of 7 boots,randomly. Even plugging in a pair of headphones does not resolve the issue since no sound is input still.
Created attachment 1731858 [details] dmesg output when the mic doesn't work
Created attachment 1731870 [details] dmesg output when the mic does work
I can confirm this also affects one of my machines, same soundcard. It can also have something to do with alsa AFAIK. I've noticed both in my dmesg and in the other user's here that internal microphone gets assigned a different inputXX when it works than when it doesn't, I don't know if this can be related someway. Do you guys have any clue? This is starting to get frustrating. Basically I have no microphone, and I need it..
After lots of testing and ruined evenings, I finally found a solution (workaround?) for this. Using HDAJackRetask, I had to force pin 0x19, which was showing "Microphone", to "unconnected" as it actually is. I also set pin 0x12 (internal mic) to connected, type of microphone "both". I can't say for sure which of the two made the trick and I'm not going to find out since it's a crucial component and I don't want to mess it up. As a result, I now have an only "Microphone" entry inside Pavucontrol, which works. Headset microphones do work correctly. Hope this comes in handy to others. Look for microphones or lines you don't have and disable them. Also I understand driver problems are quite common but this should be marked as a major issue and taken care of, as it affects major brands machines, and as you well know we all make heavy use of communication devices during these challenging times.
I can confirm the suggested workaround also works for me, thanks.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.