[SOLVED] 14.2 Lost audio input in pulse

metageek · 05-03-2021, 02:54 PM

I'm going crazy with this one. For some unknown reason I've lost my sound card input on pulse. However the input works in Audacity if I select the any of these devices:

HDA Intel PCH: ALC892 Analog (hw:0,0): Front Mic:0
sysdefault: Front Mic:0

(but not pulse:Front Mic:0 or default:Front Mic:0)

pavucontrol shows no hardware input device

relevant dmesg:

Code:

snd_hda_intel 0000:01:00.1: Disabling MSI
snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC892: line_outs=1 (0x14/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 (0x1b/0x0/0x0/0x0/0x0)
snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
snd_hda_codec_realtek hdaudioC0D0:    inputs:
snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input10
input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14

relevant lspci:

Code:

00:1f.3 Audio device: Intel Corporation Device a348 (rev 10)

alsamixer shows the input mic is not muted

So I believe the issue is in pulse. Any hints on how I can get pulse to recognize this hardware again? (I have no idea how it got removed, this worked well since I installed slackware 14.2 on this machine a year ago and I haven't done any changes in configuration).

enorbet · 05-03-2021, 06:02 PM

First I'd run "alsamixer" as root (for global effect) and follow the menu (probably starting with F6) to see if the mic is disabled there. Oulse doesn't speak directly to hardware. It uses ALSA. If it is disabled as well as unmuted in alsamixer enable it (should show a green "M" toggled by Spacebar)) and after "ESC" run "alsactl store". If all seems OK in alsamixer but the mic still doesn't show up (unlikely) you may choose to specify mic parameters in "~/.asoundrc" to control it specifically. This is also where one can control such things as sampling rate if you want top quality. The ALSA asoundrc site is very useful and has examples for most audio chipsets.

I'm not certain buty Audacity's Mic button may do exactly that - toggle the ALSA item.

metageek · 05-03-2021, 09:50 PM

Quote:

Originally Posted by enorbet

First I'd run "alsamixer" as root (for global effect) and follow the menu (probably starting with F6) to see if the mic is disabled there. Oulse doesn't speak directly to hardware. It uses ALSA. If it is disabled as well as unmuted in alsamixer enable it (should show a green "M" toggled by Spacebar)) and after "ESC" run "alsactl store". If all seems OK in alsamixer but the mic still doesn't show up (unlikely) you may choose to specify mic parameters in "~/.asoundrc" to control it specifically. This is also where one can control such things as sampling rate if you want top quality. The ALSA asoundrc site is very useful and has examples for most audio chipsets.

I'm not certain buty Audacity's Mic button may do exactly that - toggle the ALSA item.

I did say in my post that alsamixer showed that the mic was enabled...

I will try messing with .asoundrc, but I am convinced that the problem is in pulse, not in ALSA, as seen from Audacity (the ALSA devices work, the pulse ones don't).

thanks

lovemeslk · 05-03-2021, 10:33 PM

Code:

rm -rf ~/.config/pulse && rm ~/.config/pavucontrol.ini

Then reboot you have a corrupted control file.
enjoy.

metageek · 05-04-2021, 06:55 AM

Quote:

Originally Posted by lovemeslk

Code:

rm -rf ~/.config/pulse && rm ~/.config/pavucontrol.ini

Then reboot you have a corrupted control file.
enjoy.

Bingo! This fixed it. Thanks a lot!