On Mon, 06 May 2019 10:40:46 +0200, Sergey 'Jin' Bostandzhyan wrote:
Hi Takashi,
On Sun, Apr 28, 2019 at 09:34:27AM +0200, Takashi Iwai wrote:
Perhaps we should try via the kernel bugtracker, but I'd appreciate if someone could hint users like us to a place where problems like these could be addressed.
Well, the ML itself is right, but there is not many things the developers can help remotely. This is a very vendor-specific stuff, no generic problem, hence it's only the hardware vendor who knows how to fix the problem (most likely some missing extra initialization). Alternatively, you can do trial-and-error by yourself, e.g. applying the existing quirks via model option or fiddling with the pin configurations via hdajackretask.
do you know if there is a way to extract those assignments from the Widows driver/look them up with some tool from a booted Windows system? I understand that the pin descriptions/IDs or whatever are read from the hardware, so in theory they should match and provide the missing info?
Unfortunately I have little knowledge about Windows, but as far as I know, some drivers have the INFO file in a text format that contain the useful information like HD-audio verbs.
Takashi
I still have the harddisk with Win7 that was originally in this notebook, so I could mount it and give it a try if I knew what to do.
Then you noted, that there is not much you could do remotely - would access to the system help?
Kind regards, Jin