I saw those fixes from Hui back when I was trying out different kernel versions in Dec. I feel he would ultimately fix this issue in time. But time has gone on a bit too long. So I wanted to see if it was more of lacking sample hardware that might be holding it back.
I just need to know the pins/values to try. There are Thinkpad C940 quirks and the HP ALC287 quirk. This one is different, but they serve as a good template. Now, where do I get those pins? My system is dual boot, so I can go into Windows. Is there a tool I can run to enumerate possible pins/values? Or do I reuse ones I am seeing here with subtle logic guesses?
(In reply to TT from comment #67) /git.kernel. org/pub/ scm/linux/ kernel/ git/torvalds/ linux.git/ commit/ 14639cc475585f4 5722a3eb57a56d) . /git.kernel. org/pub/ scm/linux/ kernel/ git/torvalds/ linux.git/ log/ q=Hui+Wang
> There has been some kernel fixes for ALC287 codec and Lenovo in December 2020
> (https:/
> ?id=c72b9bfe0f9
>
>
> It looks like the author Hui Wang <email address hidden> has experience
> with HDA codecs:
>
>
> https:/
> ?qt=author&
>
>
> Maybe he's the one to help us out investigating this bug.
I saw those fixes from Hui back when I was trying out different kernel versions in Dec. I feel he would ultimately fix this issue in time. But time has gone on a bit too long. So I wanted to see if it was more of lacking sample hardware that might be holding it back.
I see that the change is probably just a couple lines in this file: https:/ /git.kernel. org/pub/ scm/linux/ kernel/ git/stable/ linux.git/ tree/sound/ pci/hda/ patch_realtek. c?h=v5. 10.13.
I just need to know the pins/values to try. There are Thinkpad C940 quirks and the HP ALC287 quirk. This one is different, but they serve as a good template. Now, where do I get those pins? My system is dual boot, so I can go into Windows. Is there a tool I can run to enumerate possible pins/values? Or do I reuse ones I am seeing here with subtle logic guesses?