alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Kailang <kailang@realtek.com>, Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	c <kai.heng.feng@canonical.com>, "Maxc[錦榮]" <maxc@realtek.com>,
	"nuno.dias@gmail.com" <nuno.dias@gmail.com>
Subject: Re: Fixing sound on Asus UX534F / some UX533 models
Date: Fri, 3 Jul 2020 16:52:49 +0200	[thread overview]
Message-ID: <19136909-7041-46ff-9033-82e3619792bc@redhat.com> (raw)
In-Reply-To: <531e01c492be4534bf1d98e32f4ddf4b@realtek.com>

Hi,

On 6/29/20 7:54 AM, Kailang wrote:
> Hi Hans,
> 
> The bellowing was Gediminas Aleknavicius (lektuv) mention. (Launchpad #173)
> ==>After running the above commands sound and mic works on both built-in and headset with 2.5mm connector. The model is UX533FTC.
> 
> Internal Mic was worked.

I see and in (Launchpad #174) there is another confirmation that everything
works, this time with an UX534FTC.

I also got a report from a user in the Red Hat bugzilla about this:

On an UX534F just these 2 commands are enough to make everything work:

hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf
hda-verb /dev/snd/hwC0D0 0x20 0x400 0x7774

I'm not entirely sure if using the other 2 commands you gave me
are actively causing problems there, or if they just are not
necessary. I've asked the reporter about this.

So it looks like some models need just:

hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf
hda-verb /dev/snd/hwC0D0 0x20 0x400 0x7774

While others need all 4 commands:

hda-verb /dev/snd/hwC1D0 0x20 0x500 0xf
hda-verb /dev/snd/hwC1D0 0x20 0x400 0x7774
hda-verb /dev/snd/hwC1D0 0x20 0x500 0x45
hda-verb /dev/snd/hwC1D0 0x20 0x400 0x5289

Kailang, is that enough to write a kernel patch for this? If not
what other info do you need ?

Regards,

Hans



>> -----Original Message-----
>> From: Hans de Goede <hdegoede@redhat.com>
>> Sent: Wednesday, June 24, 2020 9:19 PM
>> To: Kailang <kailang@realtek.com>; Takashi Iwai <tiwai@suse.de>
>> Cc: 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
>>
>> Hi,
>>
>> On 6/23/20 12:02 PM, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 6/4/20 8:49 AM, Kailang wrote:
>>>> 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.
>>>
>>> Thank you, and sorry for being somewhat slow to respond.
>>>
>>> I do not have access to the affected hardware myself.
>>>
>>> I've asked users who have reported bugs about this to test these
>>> setting and report back in the following bug-reports:
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439
>>> https://bugzilla.kernel.org/show_bug.cgi?id=206289
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1834751
>>>
>>> I will follow-up when I have heard back from the bug-reporters.
>>
>> Ok, I've gotten the first feedback. I ve asked the users to test the following
>> after running the 4 suggested hda-verb commands:
>>
>> 1. Speakers
>> 2. Headphones output
>> 3. Internal mic.
>> 4. Headset mic. (using a phone headset with builtin mic with a single T-R-R-S
>> connector)
>>
>> I've got feedback from a user with a UX533FTC-A8221R laptop:
>>
>> 1. Speakers: works
>> 2. Headphones output: works
>> 3. Internal mic: doesn't work
>> 4. Headset mic: works
>>
>> So things are looking ok, but we still have some work to do to get the internal
>> mic to work.
>>
>> Kailang do you have any suggestions for getting the internal mic to work?
>>
>> Regards,
>>
>> Hans
>>
>>
>>
>>
>>
>>
>>>>> -----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.
>>>>
> 


  reply	other threads:[~2020-07-03 14:54 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
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 [this message]
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=19136909-7041-46ff-9033-82e3619792bc@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=kailang@realtek.com \
    --cc=maxc@realtek.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).