From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ALSA Subsystem Development <alsa-devel@alsa-project.org>,
Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Subject: Fwd: Asus ROG Zephyrus GX701L sound problem
Date: Sun, 7 May 2023 21:06:48 +0700 [thread overview]
Message-ID: <466c0d68-5fac-74cc-c32e-23174f48add7@gmail.com> (raw)
Hi,
I notice a year-old bug report on bugzilla [1]. As many developers
don't take a look on it, I decided to forward it by email. You will
need to log in to bugzilla in order to contact the reporter.
Quoting from the bug report:
> Hello,
>
> I must mention right at the beginning that I tried all the solutions I found on the forums, but without success.
>
> The problem exists only with the speakers on the laptop, the microphone works, as do the headphones.
>
> I extracted the audio dump from windows and compared it with the dump from Linux and thus created this pinfcg below.
>
> Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01?
>
> ```
>
> [codec]
>
> 0x10ec0294 0x10431f01 0
>
> [pincfg]
>
> 0x19 0x03A11050
>
> 0x1a 0x03A11C30
>
> ```
>
> This is what a quirk should look like:
>
> +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK)
>
> [ 2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
> [ 2.396348] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
> [ 2.396349] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
> [ 2.396350] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
> [ 2.396351] snd_hda_codec_realtek hdaudioC0D0: inputs:
> [ 2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19
> [ 2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
>
>
>
>
> hwinfo --sound :heavy_check_mark:
> 22: PCI 1f.3: 0403 Audio device
> [Created at pci.386]
> Unique ID: nS1_.Qb7ky1jjQRD
> SysFS ID: /devices/pci0000:00/0000:00:1f.3
> SysFS BusID: 0000:00:1f.3
> Hardware Class: sound
> Model: “Intel Comet Lake PCH cAVS”
> Vendor: pci 0x8086 “Intel Corporation”
> Device: pci 0x06c8 “Comet Lake PCH cAVS”
> SubVendor: pci 0x1043 “ASUSTeK Computer Inc.”
> SubDevice: pci 0x1f01
> Driver: “snd_hda_intel”
> Driver Modules: “snd_hda_intel”
> Memory Range: 0x94300000-0x94303fff (rw,non-prefetchable)
> Memory Range: 0x94100000-0x941fffff (rw,non-prefetchable)
> IRQ: 157 (817 events)
> Module Alias: “pci:v00008086d000006C8sv00001043sd00001F01bc04sc03i80”
> Driver Info #0:
> Driver Status: snd_hda_intel is active
> Driver Activation Cmd: “modprobe snd_hda_intel”
> Driver Info #1:
> Driver Status: snd_soc_skl is active
> Driver Activation Cmd: “modprobe snd_soc_skl”
> Driver Info #2:
> Driver Status: snd_sof_pci_intel_cnl is active
> Driver Activation Cmd: “modprobe snd_sof_pci_intel_cnl”
> Config Status: cfg=new, avail=yes, need=no, active=unknown
>
> 29: PCI 100.1: 0403 Audio device
> [Created at pci.386]
> Unique ID: NXNs.SkelvpPm387
> Parent ID: vSkL.ZFPYIgTFUyC
> SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.1
> SysFS BusID: 0000:01:00.1
> Hardware Class: sound
> Model: “nVidia TU104 HD Audio Controller”
> Vendor: pci 0x10de “nVidia Corporation”
> Device: pci 0x10f8 “TU104 HD Audio Controller”
> SubVendor: pci 0x1043 “ASUSTeK Computer Inc.”
> SubDevice: pci 0x186f
> Revision: 0xa1
> Driver: “snd_hda_intel”
> Driver Modules: “snd_hda_intel”
> Memory Range: 0x94080000-0x94083fff (rw,non-prefetchable)
> IRQ: 17 (1698 events)
> Module Alias: “pci:v000010DEd000010F8sv00001043sd0000186Fbc04sc03i00”
> Driver Info #0:
> Driver Status: snd_hda_intel is active
> Driver Activation Cmd: “modprobe snd_hda_intel”
> Config Status: cfg=new, avail=yes, need=no, active=unknown
> Attached to: #13 (PCI bridge)
>
>
> If you need any more data, or smth just say so.
To the reporter: It seems like the hardware problem, right? If so, can
you test on different laptop?
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=216392
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-05-07 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 14:06 Bagas Sanjaya [this message]
2023-05-09 6:46 ` Fwd: Asus ROG Zephyrus GX701L sound problem Takashi Iwai
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=466c0d68-5fac-74cc-c32e-23174f48add7@gmail.com \
--to=bagasdotme@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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