All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Sergey 'Jin' Bostandzhyan <jin@mediatomb.cc>
Cc: alsa-devel@alsa-project.org, Drago Praznik <dragopraznik@gmail.com>
Subject: Re: Right internal speaker and internal microphone doesn't seem to work
Date: Tue, 07 May 2019 17:52:29 +0200	[thread overview]
Message-ID: <s5hpnous1mq.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190506084046.GA397@xn--80adja5bqm.su>

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
> 

      reply	other threads:[~2019-05-07 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 15:07 Right internal speaker and internal microphone doesn't seem to work Drago Praznik
2019-04-25 16:46 ` Sergey 'Jin' Bostandzhyan
2019-04-28  7:34   ` Takashi Iwai
2019-05-06  8:40     ` Sergey 'Jin' Bostandzhyan
2019-05-07 15:52       ` Takashi Iwai [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hpnous1mq.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=dragopraznik@gmail.com \
    --cc=jin@mediatomb.cc \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.