From: Takashi Iwai <tiwai@suse.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: alsa-devel@alsa-project.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: HDA codec problem
Date: Fri, 20 Aug 2021 08:44:07 +0200 [thread overview]
Message-ID: <s5hfsv48vk8.wl-tiwai@suse.de> (raw)
In-Reply-To: <12bbf54b-3ef6-8fa8-37fc-5f1e8d134bba@infradead.org>
On Fri, 20 Aug 2021 07:08:34 +0200,
Randy Dunlap wrote:
>
> Hi,
>
> I am having problems getting audio working on my computer:
>
> 00:1f.3 Audio device: Intel Corporation Device f1c8
>
> I did an internet search that said that I would need 5.13 or later to
> have support for this device.
The above is Cometlake-H, and it pretty much depends on the machine
configuration.
> openSUSE 15.3 kernel 5.3.18-59.19-default says:
>
> snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC233: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line
> snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
> snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
> snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
> snd_hda_codec_realtek hdaudioC0D0: inputs:
> snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a
> snd_hda_codec_realtek hdaudioC0D0: Mic=0x19
>
> but produces no sound output.
FWIW, openSUSE Leap 15.3 kernel is based on 5.3 but got tons of
backports, hence its HD-audio part is almost equivalent with 5.13 or
later kernel (except for the recently changed mute-LED handling --
which must be irrelevant with your problem).
The above indicates that the codec is detected and set up. The rest
part is often some vendor-specific quirks. For that, details are
missing completely. At best please give alsa-info.sh output (run the
script with --no-upload and attach the output).
> Kernel 5.13.10 or 5.14-rc6 say:
>
> calling azx_driver_init+0x0/0x20 @ 1
> snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
> snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops)
> snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x200f0000
> snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x200f0000
> snd_hda_intel 0000:00:1f.3: Codec #2 probe error; disabling it...
> snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to single_cmd mode: last cmd=0x000f0001
> hdaudio hdaudioC0D0: no AFG or MFG node found
> snd_hda_intel 0000:00:1f.3: no codecs initialized
If it's the result from the more-or-less similar configuration like
the previous Leap kernel (regarding the audio), this must come from
another part than the sound driver, likely either PCI or arch/x86.
You might need to bisect for that...
thanks,
Takashi
next prev parent reply other threads:[~2021-08-20 6:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 5:08 HDA codec problem Randy Dunlap
2021-08-20 6:44 ` Takashi Iwai [this message]
2021-08-20 13:54 ` Randy Dunlap
2021-08-20 14:11 ` Takashi Iwai
2021-08-20 14:43 ` Randy Dunlap
2021-08-21 19:14 ` Randy Dunlap
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=s5hfsv48vk8.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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).