Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: dmummenschanz@web.de, alsa-devel@alsa-project.org
Subject: Re: Cannon Lake PCH cAVS (ALC892) not detected by kernel driver
Date: Tue, 8 Feb 2022 15:55:13 -0600	[thread overview]
Message-ID: <209270c3-4a46-d6a1-0f1d-d4400ecc5962@linux.intel.com> (raw)
In-Reply-To: <trinity-f018660b-95c9-442b-a2a8-c92a56eb07ed-1644345967148@3c-app-webde-bap22>



On 2/8/22 12:46, dmummenschanz@web.de wrote:
>    Hello,
> 
>    the audio chip Cannon Lake PCH cAVS ALC892 does not get recognized on
>    my system. Only the HDMI devices are recognized.
> 
>    lspci shows the following audio device:
>    00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
> 
>    dmesg only shows:
> 
>    [  189.559786] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops
>    i915_exit [i915])
>    [  189.581395] input: HDA Intel PCH HDMI/DP,pcm=3 as
>    /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
>    [  189.581503] input: HDA Intel PCH HDMI/DP,pcm=7 as
>    /devices/pci0000:00/0000:00:1f.3/sound/card0/input21
>    [  189.581628] input: HDA Intel PCH HDMI/DP,pcm=8 as
>    /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
>    [  189.581711] input: HDA Intel PCH HDMI/DP,pcm=9 as
>    /devices/pci0000:00/0000:00:1f.3/sound/card0/input23
>    [  189.581849] input: HDA Intel PCH HDMI/DP,pcm=10 as
>    /devices/pci0000:00/0000:00:1f.3/sound/card0/input24
> 
> 
>    ALSA-info file:
>    http://alsa-project.org/db/?f=96102ee84f258d1cac83ed33795356550181511c

I see to references to ALC892 in this profile, is this information based
on the hardware specs or Windows logs?

we usually ask people to try with a more recent kernel, but in your case
I would try to go back to a mainline release. I have no idea what this
version might contain audio-wise: 5.17.0-rc3-drmtip

> 
>    There is a workaround availble:
> 
>    echo auto | tee /sys/devices/pci0000\:00/0000\:00\:1f.3/power/control
>    echo 1 | tee /sys/devices/pci0000\:00/0000\:00\:1f.3/remove
>    echo 1 | tee /sys/bus/pci/rescan
> 
>    unfortunately this doesn't work for me. The device never shows up.
>    Sound on winX works fine on this device btw.
>    I'm happy to assist with any attempts to make the sound work.

  reply	other threads:[~2022-02-08 22:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 18:46 Cannon Lake PCH cAVS (ALC892) not detected by kernel driver dmummenschanz
2022-02-08 21:55 ` Pierre-Louis Bossart [this message]
2022-02-09  7:14   ` Aw: " dmummenschanz
2022-02-09 15:51     ` Pierre-Louis Bossart
2022-02-09 16:47       ` Aw: " dmummenschanz
2022-02-12 11:33         ` dmummenschanz
2022-02-12 19:42           ` Pierre-Louis Bossart
2022-02-13  9:08             ` Takashi Iwai
2022-02-14  6:49               ` dmummenschanz
2022-02-14  7:08                 ` Takashi Iwai
2022-02-14  7:38                   ` dmummenschanz
2022-02-14  8:42                     ` Takashi Iwai
2022-02-14  9:23                       ` Aw: " dmummenschanz
2022-02-14  9:54                         ` 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=209270c3-4a46-d6a1-0f1d-d4400ecc5962@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dmummenschanz@web.de \
    /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