FS#46435 - [linux] SND_INTEL_HDA now fails on Intel C210 High Definition Controller

Attached to Project: Arch Linux
Opened by Sam (cellardoor) - Friday, 25 September 2015, 12:10 GMT
Last edited by Toolybird (Toolybird) - Saturday, 27 May 2023, 07:14 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I have categorised this as a Kernel bug, since SND_INTEL_HDA is a Kernel module, included in the Kernel via ALSA.

After a pacman -Syu, whenever I boot the computer I see this message, and can find it again later via dmesg:

[ 12.640995] snd_hda_intel: probe of 0000:00:1b.0 failed with error -2

As you can see from my lspci, this is address where the Audio card is located

00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)

I've tried swapping out Kernels, reinstalling ALSA, Pulse, and their interconnecting packages. I've tried rmmod and modprobe-ing snd_intel_hda with various arguments from tips I've found online, to no avail. All it does it put the "snd_hda_intel" error in my dmesg another time.

A set of USB headphones works fine when plugged in, so pulseaudio/alsa themselves work fine. It has to be a Kernel/driver issue. Up until two days ago everything has been fine for years.

I've attached my dmesg and Kernel/PulseAudio/Alsa versions as well.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
Unknown, probably own a machine with this soundcard and be running on the latest kernel.
   versions.txt (0.6 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 27 May 2023, 07:14 GMT
Reason for closing:  No response
Additional comments about closing:  Plus it's old and stale. If still an issue, please report upstream.
Comment by Doug Newgard (Scimmia) - Friday, 25 September 2015, 14:22 GMT
Have you reported this upstream? Nothing will happen here.
Comment by Sam (cellardoor) - Monday, 28 September 2015, 08:35 GMT
Well I would but I don't know who to report it to. The Kernel team or the ALSA team, as I'm guessing they are separate?
Comment by Sam (cellardoor) - Monday, 05 October 2015, 23:49 GMT
Really weird now... I rebooted after a full update today and now apparently I am running realtek... But it's an Intel board and soundcard?

0:45:59 › dmesg | grep snd
[ 13.117001] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3202: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 13.117005] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 13.117006] snd_hda_codec_realtek hdaudioC0D0: hp_outs=2 (0x15/0x1b/0x0/0x0/0x0)
[ 13.117008] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 13.117009] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 13.117010] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18
[ 13.117012] snd_hda_codec_realtek hdaudioC0D0: Dock Mic=0x19
[ 13.117013] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
Comment by mattia (nTia89) - Saturday, 26 February 2022, 14:54 GMT
I cannot reproduce the issue. Is it still valid?

Loading...