Pavucontrol shows that audio is playing but no output heard

[oveclock3511]

snd_intel8x0 seems to be part of the old ac97 driver as far as I can see. Your card uses the newer snd-hda-intel - again, as far as I can see.

I can't see why the kernel would be trying to load both. Maybe somebody with more experience can comment.

Is there a way to find which package owns a module?

[FreewheelinFrank]

Both are Alsa, I think.

On my Buster machine...

Code: Select all

$ find /lib/modules/`uname -r` | grep snd-intel8x0

Tells me the snd-intel8x0m module is available:

Code: Select all

/lib/modules/4.19.0-15-amd64/kernel/sound/pci/snd-intel8x0m.ko
/lib/modules/4.19.0-15-amd64/kernel/sound/pci/snd-intel8x0.ko

Code: Select all

$ lsmod | grep snd

Tells me snd-intel8x0m is not loaded (snd_hda_intel is)

Code: Select all

$ lspci -nnk | grep -A2 Audio

Tells me my card is using the snd_hda_intel driver and the kernel module is loaded.

Code: Select all

00:1b.0 Audio device [0403]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 21)
	Subsystem: Lenovo Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [17aa:3637]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

Code: Select all

# journalctl -k | grep -Ei "snd|sound|audio|multi"

Tells me the codec in use and the outputs:

Code: Select all

Mar 11 09:00:07 debian kernel: snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Mar 11 09:00:07 debian kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC233: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Mar 11 09:00:07 debian kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Mar 11 09:00:07 debian kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Mar 11 09:00:07 debian kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Mar 11 09:00:07 debian kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Mar 11 09:00:07 debian kernel: snd_hda_codec_realtek hdaudioC0D0:      Mic=0x1a
Mar 11 09:00:07 debian kernel: snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12

Nothing about snd_intel8x0.

Code: Select all

$ aplay -l

Tells me the analog ALC233 is card 0,0

Code: Select all

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC233 Analog [ALC233 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Code: Select all

$ aplay /dev/urandom -f dat -D plughw:0,0

Gets me white noise on the speakers.

Compare and contrast.

Maybe try

Code: Select all

modprobe -r snd_intel8x0

and

Code: Select all

modprobe snd_hda_intel

Just a stab in the dark really.

[oveclock3511]

I am pretty sure it's a kernel issue at this point: i have plugged the jack of the speaker trough a jack splitter and by playing from another device and booting the pc up the sound goes quiter but as soon as the os starts the booting procedure and tries to load the snd_hda the sound of the thing that i am playing from the other device goes up (i almost had an heart attack the first time because i was listening to metallica ).

I genuinely have no clue at this point.

i have reinstalled the system twice on both an ssd and a normal hdd, i have installed other distros but nothing... i just want to listen to stuff and record every once in a while that's all

[Bulkley]

. . . i have installed other distros but nothing...

Are you sure this isn't a hardware problem?

Edited to add, could it be a BIOS problem? I know it sounds dumb but we are into weird with this.

[oveclock3511]

Ok updates:

yesterday i decided that i had enough and i took the motherboard out to find out that the audio chip on the MOBO is an ALC888S and not an ALC1200 like the alsa mixer shows.

After that i picked up a pair of headphones, grounded the jack ground and started poking around the chip with one of the headphone's channels.

the datasheet is the following https://html.alldatasheet.com/html-pdf/ ... C888S.html and after poking pin 7/8 (i am using some rudimentary tools )... sound came out!!! it was unfiltered obviously (because it was directly from the sound chip but hey... it was sound.

So i have two hypothesis now:

1) it's a driver issue (hence the wrong chip detection unless i missed something)
2) something broke in the middle (like an amp circuit or stuff like that) (even if there are no burned traces/popped capacitors/ics that could've been damaged)

[FreewheelinFrank]

Try these tips - the guy helps people on the Mint forum with sound issues and he seems to know something.

http://mreen.epizy.com/SoundFixTips.html?i=2

Have you tried?

Code: Select all

modprobe -r snd_intel8x0
modprobe snd_hda_intel

One thing you could try is hdajackretask.

It will tell you what each pin on the chip is supposed to do. Sometimes the BIOS can tell the chip to use the wrong pin. If you can identify a pin with sound, work out its ID (in hex) and see what hdajackretask says that pin is doing, You can retask the pin. For some people it seems to work. If it doesn't, you can reboot to reset. If it works, apply the boot override. It's part of alsa-tools I think.

Edit:typo,

[oveclock3511]

Now i'll try to install windows xp on the machine to knock out the second hypothesis and then,if everything is fine, i'll reput debian on and retry your tips

also afaik snd-hda-intel depends from intel8x0 ( i am not sure tbh)