From: Kailang <kailang@realtek.com>
To: Takashi Iwai <tiwai@suse.de>, Hans de Goede <hdegoede@redhat.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
c <kai.heng.feng@canonical.com>,
"nuno.dias@gmail.com" <nuno.dias@gmail.com>
Subject: RE: Fixing sound on Asus UX534F / some UX533 models
Date: Thu, 4 Jun 2020 06:49:20 +0000 [thread overview]
Message-ID: <b647b169111f4c46a7c81ec80c551498@realtek.com> (raw)
In-Reply-To: <s5hr1uxhc6k.wl-tiwai@suse.de>
Hi Hans de Goede,
Please test below.
hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf
hda-verb /dev/snd/hwC0D0 0x20 0x400 0x7774
hda-verb /dev/snd/hwC0D0 0x20 0x500 0x45
hda-verb /dev/snd/hwC0D0 0x20 0x400 0x5289
I think Headset Mic will work.
BR,
Kailang
> -----Original Message-----
> From: Takashi Iwai <tiwai@suse.de>
> Sent: Tuesday, June 2, 2020 8:42 PM
> To: Hans de Goede <hdegoede@redhat.com>
> Cc: Kailang <kailang@realtek.com>; c <kai.heng.feng@canonical.com>;
> alsa-devel@alsa-project.org; nuno.dias@gmail.com
> Subject: Re: Fixing sound on Asus UX534F / some UX533 models
>
> On Tue, 02 Jun 2020 11:51:49 +0200,
> Hans de Goede wrote:
> >
> > Hi Kai-Heng Feng, Takashi,
> >
> > I see that you are on the notification list for this bug:
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439
> >
> > So you may have already seen this. Some owners of affected laptops
> > (which have non working speakers / headphone output atm), have done
> > some heroic debugging work and come up with a set of
> > 2 hda-verb commands which fix this.
> >
> > I'm not all that familiar with writing hda quirks, so I was hoping
> > that one of you 2 can come up with a patch to fix this at the kernel
> > level.
> >
> > This would also resolve these 2 bugs, which I believe are the same bug
> > really:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=206289
> > https://bugzilla.redhat.com/show_bug.cgi?id=1834751
>
> Adding verbs are trivial and it can be done even without patching kernel but
> providing by a patch via patch module option of snd-hda-intel driver.
>
> But, before moving forward, I'd like to confirm about the correctness (and the
> safeness) of those verbs.
>
> Kailang, could you check the COEF verbs mentioned in the bug entry above?
>
>
> thanks,
>
> Takashi
>
> ------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2020-06-04 6:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 9:51 Fixing sound on Asus UX534F / some UX533 models Hans de Goede
2020-06-02 12:41 ` Takashi Iwai
2020-06-04 6:49 ` Kailang [this message]
2020-06-23 10:02 ` Hans de Goede
2020-06-24 13:18 ` Hans de Goede
2020-06-29 5:54 ` Kailang
2020-07-03 14:52 ` Hans de Goede
2020-07-05 13:25 ` Hans de Goede
2020-07-09 8:53 ` Kailang
2020-07-09 9:29 ` Hans de Goede
2020-06-04 7:05 ` Kailang
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=b647b169111f4c46a7c81ec80c551498@realtek.com \
--to=kailang@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=hdegoede@redhat.com \
--cc=kai.heng.feng@canonical.com \
--cc=nuno.dias@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).