From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ASUS Proart P16 - Realtek ALC245 not detected properly after kernel 6.15 - worked perfectly with earlier kernels
Date: Sun, 21 Sep 2025 15:23:31 +0200 (CEST) [thread overview]
Message-ID: <18674ef8aff3c300-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18674ef8afbd0900-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #615 was edited from SneakyLittleman:
Hey there, as [reported in the arch forums](https://bbs.archlinux.org/viewtopic.php?id=307540), the ALC245 (and Cirrus Logic amp CS35L56) are not detected properly after kernel 6.15. Anything below 6.14.9 works perfectly fine.
The chip reverts to the "proaudio" profile, with no other option, and the command "alsaucm listcards" returns an empty list.
With older kernels, the command returned:
` 0: hw:1
HDA NVidia at 0xdd080000 irq 143
1: hw:2
HD-Audio Generic at 0xdd7c8000 irq 144
2: hw:3
HD-Audio Generic at 0xdd7c0000 irq 145
3: hw:4
ASUSTeKCOMPUTERINC.-ProArtP16H7606WI_H7606WI-1.0-H7606WI`
and I had access to the correct audio profiles with pipewire.
Willing to submit anything that might help, to fix this. Cheers.
Here's the chip info in that specific laptop:
`66:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller [1022:15e3]
DeviceName: Realtek ALC245
Subsystem: ASUSTeK Computer Inc. Device [1043:1e63]`
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/615
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2025-09-21 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18674ef8afbd0900-webhooks-bot@alsa-project.org>
2025-09-21 13:23 ` GitHub issues - edited [this message]
[not found] <18674ee8046b3b00-webhooks-bot@alsa-project.org>
2025-09-21 13:22 ` ASUS Proart P16 - Realtek ALC245 not detected properly after kernel 6.15 - worked perfectly with earlier kernels GitHub issues - edited
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=18674ef8aff3c300-webhooks-bot@alsa-project.org \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).