All of lore.kernel.org
 help / color / mirror / Atom feed
From: ecmk <info@ecmk.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Kernel patch needed for Asus Q325UAR
Date: Sun, 21 Apr 2019 11:24:31 -0700	[thread overview]
Message-ID: <c341a56c-be1d-2301-1bde-b8eb403c6391@ecmk.org> (raw)
In-Reply-To: <s5hmukp3s6o.wl-tiwai@suse.de>

I just want to confirm that with kernel version 5.0.7-200 the problem 
still exists for Asus Q325UAR

Let me know if you need any additional information for the patch.

Thanks!

On 4/17/19 2:19 AM, Takashi Iwai wrote:
> On Fri, 12 Apr 2019 23:43:50 +0200,
> ecmk wrote:
>> No sound combined with quickly fading sounds for a few
>> seconds. Randomly working but with low quality distorted sound. The
>> model needs to be added to the kernel patch listed bellow.
>>
>>
>> Asus Q325UAR suffers from the same issues as discussed here:
>>
>>
>> [alsa-devel] [PATCH] ALSA: hda/realtek: Enable audio jacks of ASUS
>> UX391UA with, ALC294
>>
>> https://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/143282.html
>>
>>
>> A detailed issue of the problem plus the solution is described here
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784485?comments=all
> Hm, from the reports there, it's not clear whether the existing quirk
> for UX391UA works for your device.  Did you actually test it?  If yes,
> please give alsa-info.sh output running on your machine (with
> --no-upload option), so that I can cook up a patch.
>
>
> thanks,
>
> Takashi

  reply	other threads:[~2019-04-21 18:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 21:43 Kernel patch needed for Asus Q325UAR ecmk
2019-04-17  9:19 ` Takashi Iwai
2019-04-21 18:24   ` ecmk [this message]
2019-04-23 15:14     ` Takashi Iwai
2019-04-23 23:21       ` ecmk
2019-04-30 13:13         ` Takashi Iwai
2019-05-02 23:06           ` ecmk

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=c341a56c-be1d-2301-1bde-b8eb403c6391@ecmk.org \
    --to=info@ecmk.org \
    --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 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.