Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Walt Holman <waltholman09@gmail.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: ASUS GA605WI Tinny sound - No Amp?
Date: Mon, 26 Aug 2024 06:37:07 -0500	[thread overview]
Message-ID: <5db86032-f0eb-46e0-ab79-43c5fc321ffc@gmail.com> (raw)
In-Reply-To: <5a554db6-b278-4cd2-a637-3cc15a3b9caa@opensource.cirrus.com>

On 8/26/24 04:02, Richard Fitzgerald wrote:
> On 24/08/2024 21:39, Walt Holman wrote:
>> Hello,
>>
>> I just purchased an ASUS Zephyrus G16 2024 laptop model # GA605WI. This is a brand new model laptop with the AMD AI 370HX and Radeon 890 setup. This particular model also has an Nvidia 4070 discrete GPU, but the issue I'm having is with the sound. The amplifier doesn't appear to be turning on the additional two speakers, and the sound is only coming out of the tweeters, so it's weak and tinny. This laptop relies on the CS35L56 and what appears to be a couple of amps according to dmesg. From everything that I've read, I thought that maybe it didn't have the correct _DSD setup correctly, but after following a guide for the ROG laptops for creating the proper entries and setting them up as an early load from grub, I believe that they're already there. Once I did that, dmesg reported that there was already a SPKR i2C table that contained the entries, so I'm fairly certain that it's not the ACPI / EFI missing it. I noticed that in the sound/pci/hda/patch_realtek.c file there was 
>> a quirk already for the 605W, but something must be missing still for this model. I'm running 6.11.0 master with the latest git firmware tree. Please let me know what information I can provide to help get this thing running properly :)  Below is some relevant information re: the CS35L56 from dmesg if it helps. Let me know what else I can do. Thanks,
>>
> 
> It looks like your linux-firmware was not installed correctly.
> Did you run the Makefile to install it, or are you just manually copying
> files from the linux-firmware git repo? If you copy files manually, you
> also need to manually create the symlinks that are listed in the WHENCE
> file.
> 
> Specifically, you seem to be missing this symlink:
> 
> Link: cirrus/cs35l56-b0-dsp1-misc-10431e83-spkid1.wmfw -> cs35l56/CS35L56_Rev3.11.16.wmfw
> 
That was it. Thank you for helping me out. I had been just doing a git-clone, git -pull now and again and never even noticed the Makefile. Thanks again,

-Walt


      reply	other threads:[~2024-08-26 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-24 20:39 ASUS GA605WI Tinny sound - No Amp? Walt Holman
2024-08-26  9:02 ` Richard Fitzgerald
2024-08-26 11:37   ` Walt Holman [this message]

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=5db86032-f0eb-46e0-ab79-43c5fc321ffc@gmail.com \
    --to=waltholman09@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.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