Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Kazmin <stas.kazmin@gmail.com>
To: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>
Subject: Re: [HDAudio][ALC295] speakers not working on Acer Travelmate P614
Date: Mon, 29 Jun 2020 15:46:15 +0200	[thread overview]
Message-ID: <32519971.jW2LJBauvq@gluon> (raw)
In-Reply-To: <s5h366ln2vc.wl-tiwai@suse.de>

Hello,

unfortunately I am still lost and do not know how to attack the problem...

But I found this bug: https://bugzilla.kernel.org/show_bug.cgi?id=207423

and I wounder if it related to the problem here?

Best,

Stanislav

On Dienstag, 23. Juni 2020 18:49:59 CEST Takashi Iwai wrote:
> On Tue, 23 Jun 2020 17:49:18 +0200,
> 
> Stanislav Kazmin wrote:
> > Hello, I have the following problem on my Acer TravelMate P614-51T-G2:
> > 
> > I have all the audio sinks correctly identified (like HDMI, DMic,
> > Headphones) but the internal speakers do not produce any sound.
> > 
> > What I have tried so far:
> > 
> > - hard/soft shutdown on Windows and reboot
> > - disable/re-enable speakers and microphone in BIOS
> > - uninstall pulseaudio and test alsa alone (so it is defeitely **not** a
> > pulseaudio issue)
> > - switch from sof-hda-dsp to snd-hda-intel driver (without Dmic support)
> > - retask pins 0x14, 0x16, 0x1b to "Internal Speakers" through
> > hdajackretask
> > (only basic, without advanced features)
> > - removed/reconnected the headphones
> > 
> > `alsamixer` shows all needed sinks and nothing is muted.
> > 
> > I already discussed the issue at sof github
> > https://github.com/thesofproject/ sof/issues/3058 but since the same
> > issue occurs on `snd-hda-intel` legacy river, I was advised to
> > communicate with alsa-devel team.
> > 
> > The alsa-info.sh result are linked at http://alsa-project.org/db/?
> > f=252f92c7a1df3c755d16ee69353b26d2535a4d81
> > 
> > I have tested the kernel 5.8-rc1 but it does not make any difference.
> > 
> > Let me know if I can do anything else to test the issue.
> 
> It's hard to know and the only way is to some trial-and-errors.
> The first shot I'd take is to toggle GPIO pins.  You can change the
> bit via hda-verb program like
>   hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x01
>   hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x01
>   hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x01
> 
> to turn on the bit 0 of GPIO.  The first 0x01 is the node ID and it's
> 0x01 on Realtek, and the last 0x01 the GPIO bit 0.  For toggling the
> bit 1, pass 0x02 in the last argument, and for bit 2, pass 0x04.
> 
> And try turn on EAPD on non-used pins.  This can be done via hda-verb,
> too.
> 
> If this doesn't help, you might need to try some COEF changes as done
> in various quirks in sound/pci/hda/patch_realtek.c.
> 
> 
> HTH,
> 
> Takashi




  parent reply	other threads:[~2020-06-29 13:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 15:49 [HDAudio][ALC295] speakers not working on Acer Travelmate P614 Stanislav Kazmin
2020-06-23 16:49 ` Takashi Iwai
2020-06-23 21:50   ` Stanislav Kazmin
2020-06-24 14:29     ` Stanislav Kazmin
2020-06-29 13:46   ` Stanislav Kazmin [this message]
2020-07-03  9:42     ` Stanislav Kazmin
  -- strict thread matches above, loose matches on Subject: below --
2020-06-20 23:27 Stanislav Kazmin

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=32519971.jW2LJBauvq@gluon \
    --to=stas.kazmin@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox