linux-kernel - Re: Fwd: Asus ROG Zephyrus GX701L sound problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <871qjq6lyf.wl-tiwai@suse.de>
Date:   Tue, 09 May 2023 08:46:48 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux ALSA Subsystem Development 
        <alsa-devel@...a-project.org>, Oder Chiou <oder_chiou@...ltek.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>,
        Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>
Subject: Re: Fwd: Asus ROG Zephyrus GX701L sound problem

On Sun, 07 May 2023 16:06:48 +0200,
Bagas Sanjaya wrote:
> 
> 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

This is a sort of problems that is difficult to help from the upstream
side.  The symptom indicates that the likely culprit is some missing
stuff for speaker amp behind the HD-audio codec, and those are usually
all vendor-specific; the wild west without laws, and only the vendor
knows how to drive.

User may try to apply the existing quirks one-by-one.  If nothing
helps, they can try tracing the HD-audio verbs on Windows over VM
(only if allowed).


Takashi