linux-kernel - Re: HDA codec problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hfsv48vk8.wl-tiwai@suse.de>
Date:   Fri, 20 Aug 2021 08:44:07 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     alsa-devel@...a-project.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: HDA codec problem

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