On Thu, 25 Apr 2019 18:46:57 +0200, Sergey 'Jin' Bostandzhyan wrote: > > Hi Drago, > > On Thu, Apr 25, 2019 at 05:07:55PM +0200, Drago Praznik wrote: > > Originally I submitted a post on forum: > > https://forums.linuxmint.com/viewtopic.php?f=49&t=292732 > > > > ... since it didn't help, I ended up here. > > I almost fear we're on the wrong list here, I have a similar problem on > a different notebook, but did not get any answer. I think this list is > much more technical/low-level and not end user oriented. > > That being said - it was suggested on the Alsa Project page, thats how I > got here, so not really sure what the right place for such requests would be. > > 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. thanks, Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
