From: Jaroslav Kysela <perex@perex.cz>
To: sboyce@blueyonder.co.uk, Randy Dunlap <rdunlap@infradead.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ALSA <alsa-devel@alsa-project.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.com>
Subject: Re: Ryzen 9 7950x sound module does not not build
Date: Wed, 27 Sep 2023 18:26:19 +0200 [thread overview]
Message-ID: <5cafee23-b1fe-4ee5-8f62-6080707403da@perex.cz> (raw)
In-Reply-To: <4b2c3b4e-9b21-4f80-95e1-58aa7f58131e@blueyonder.co.uk>
On 27. 09. 23 13:27, Sid Boyce wrote:
> On 26/09/2023 23:13, Randy Dunlap wrote:
>> lspci -vv
> 0b:00.6 Audiodevice: Advanced Micro Devices, Inc. [AMD] Family 17h/19h
> HD AudioController
> DeviceName: Realtek ALC897 Audio
> Subsystem: ASUSTeK Computer Inc. Device 87fb
It looks like a standard HDA hardware. The acp module may not be relevant. You
should see some inputs/outputs for this card in pipewire - the snd-hda-intel
module is loaded.
But this hardware may require a new quirk, when the generic code does not work
for you. I suggest to look to the HDA driver documentation in
Documentation/sound/hd-audio tree.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2023-09-27 16:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 1:20 Sid Boyce
2023-09-26 1:48 ` Randy Dunlap
2023-09-26 12:23 ` Sid Boyce
2023-09-26 13:01 ` Bagas Sanjaya
2023-09-26 14:58 ` Sid Boyce
2023-09-26 19:17 ` Sid Boyce
2023-09-26 22:13 ` Randy Dunlap
2023-09-27 11:27 ` Sid Boyce
2023-09-27 15:40 ` Randy Dunlap
2023-09-27 16:23 ` Sid Boyce
2023-09-27 19:14 ` Sid Boyce
2023-10-02 9:43 ` Sid Boyce
2023-09-27 16:26 ` Jaroslav Kysela [this message]
2023-09-27 19:59 ` Sid Boyce
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=5cafee23-b1fe-4ee5-8f62-6080707403da@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=bagasdotme@gmail.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sboyce@blueyonder.co.uk \
--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
all inboxes | Powered by JetHome®