ALSA unable to find card [SOLVED]

BuddhiArch · 2020-05-20 17:11:35

So, I'm using audio and microphones just fine. But, I have to screen-cast and record.

Then, upon

ffmpeg -video_size 1024x768 -framerate 25 -f x11grab -i :0.0+100,200 -f alsa -ac 2 -i hw:0 output.mkv

[x11grab @ 0x55accec104c0] Stream #0: not enough frames to estimate rate; consider increasing probesize
Input #0, x11grab, from ':0.0+100,200':
  Duration: N/A, start: 1589994434.035745, bitrate: N/A
    Stream #0:0: Video: rawvideo (BGR[0] / 0x524742), bgr0, 1024x768, 25 fps, 1000k tbr, 1000k tbn, 1000k tbc
ALSA lib pcm.c:2642:(snd_pcm_open_noupdate) Unknown PCM hw:0
[alsa @ 0x55accec1c180] cannot open audio device hw:0 (No such file or directory)
hw:0: Input/output error

I went to https://trac.ffmpeg.org/wiki/Capture/ALSA

Then, tried out

arecord -l

Receiving this really bizarre output,

ALSA lib control.c:1379:(snd_ctl_open_noupdate) Invalid CTL hw:0
arecord: device_list:283: control open (0): No such file or directory
ALSA lib control.c:1379:(snd_ctl_open_noupdate) Invalid CTL hw:1
arecord: device_list:283: control open (1): No such file or directory

Last edited by BuddhiArch (2020-05-25 07:29:23)

V1del · 2020-05-20 19:27:29

You have a broken ALSA config somewhere check your home directory configs (.asoundrc, asound.conf, /etc/asound.conf) and maybe post

strace arecord -l

BuddhiArch · 2020-05-20 20:13:39

I don't have any of those asound files.

The only configuration I have in ALSA is in /etc/modprobe.d/dha_fix.conf

options snd_hda_intel dmic_detect=0

For

strace arecord -l

,

https://pastebin.com/e51BQVtL

and,

alsactl restore

gives

 alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
Found hardware: "HDA-Intel" "Realtek ALC3254" "HDA:10ec0295,10280949,00100002 HDA:8086280b,80860101,00100000" "0x1028" "0x0949"
Hardware is initialized using a generic method
Found hardware: "HDA-Intel" "Nvidia GPU 80 HDMI/DP" "HDA:10de0080,00000000,00100100" "0x0000" "0x0000"
Hardware is initialized using a generic method

Last edited by BuddhiArch (2020-05-20 20:23:47)

V1del · 2020-05-20 21:48:26

/home/buddhi/.config/alsa/asoundrc then.

BuddhiArch · 2020-05-21 03:00:33

# Find and use input "Microphone" for input
pcm.usb
{
    type hw
    card Microphone
}
pcm.!default
{
    type asym
    playback.pcm
    {
    	# Use the dmix plug to allow multiple outputs.
        type plug
        slave.pcm "dmix"
    }
    capture.pcm
    {
        type plug
        slave.pcm "usb"
    }
}

V1del · 2020-05-21 11:24:41

There's no USB mic in that restore output, but that should just break the default pcm, what's more problematic is that none of the system wide config files are sourced. Do you have a ALSA config overriding environment variable? Remove/move away both of these for now, what do you get for

dmesg | grep snd

BuddhiArch · 2020-05-21 18:48:30

So, my general configurations are a bootstrap from https://github.com/lukesmithxyz/voidrice . I don't understand all the things build in it, although, I'm learning it.

I don't know if that is helpful, but making that clear.

Hm... I commented all the lines of .config/alsa/asoundrc, rebooted, and

 dmesg | grep snd

 [    3.586191] snd_hda_intel 0000:00:1f.3: dmic_detect option is deprecated, pass snd-intel-dspcfg.dsp_driver=1 option instead
[    3.586208] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[    3.586474] snd_hda_intel 0000:01:00.1: dmic_detect option is deprecated, pass snd-intel-dspcfg.dsp_driver=1 option instead
[    3.586482] snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
[    3.586542] snd_hda_intel 0000:01:00.1: Disabling MSI
[    3.586547] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[    3.886372] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    4.047642] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3254: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[    4.047644] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    4.047645] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[    4.047646] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[    4.047647] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[    4.047649] snd_hda_codec_realtek hdaudioC0D0:      Headphone Mic=0x1b
[    4.047650] snd_hda_codec_realtek hdaudioC0D0:      Headset Mic=0x19

When I commented /etc/modprobe.d/dha_fix.conf,

 dmesg | grep snd

[    3.238764] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    3.239514] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[    3.239581] snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
[    3.239633] snd_hda_intel 0000:01:00.1: Disabling MSI
[    3.239639] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[    3.564526] snd_soc_skl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    3.565467] snd_soc_skl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver

My

strace arecord -l

, when both are commented,
https://pastebin.com/4U8xWdc0

Last edited by BuddhiArch (2020-05-21 18:57:49)

V1del · 2020-05-21 18:59:41

So you are randomly using a configuration that changes large parts of your system's configuration and nearly nothing applies to your situation and you don't know what doesn't and now you are wondering why you run into issues?

I suggest you remove everything set up by that. if you want to look at configurations for inspiration, then do so for single files that are relevant (like i3 config if needed) a lot of things in that repo make hard coded assumptions that - while they might be applicable to the original user - will never work on your system and just break stuff.

Last edited by V1del (2020-05-21 19:01:21)

BuddhiArch · 2020-05-21 19:17:30

Ok... I will do that.
I mainly am used to his dwm build, X bindings, and what not... the scripts are very good also.

Just to point something out, the modprobe file fix has nothing to do with this build. Because, It was an issue I had in my first install, and - you can search in my post histories - was a fix you gave me. Because, by default, the arch build did not provided a build that was suited to my computer. That is, I had no sound (still the case, when I un-commented that line).

Last edited by BuddhiArch (2020-05-21 19:19:13)

V1del · 2020-05-21 19:25:59

I know that that one doesn't, I've suggested that fix to you when it came up, and it is irrelevant in this instance since the incorrectly copied configuration broke general ALSA set up, regardless of whether the general kernel module is properly configured.

And on a side note, the dmic_detect parameter got deprecated in the mean time if it's still necessary (there have been fixes on sof so it might not be necessary anymore) you should rather use

options snd_intel_dspcfg dsp_driver=1

instead.

BuddhiArch · 2020-05-25 07:28:44

Hey, so, to give it a closure,

I found a straight forward solution to my problem, in the lines you proposed. I deleted all the configuration files of alsa, or pavucontrol, which are bound, initially - and probably auto-generated - to LARBS's configurations, as well as all my files having to do with alsa and pulseaudio.

I was in a real dilemma to reinstall all my system yet again. And, in the end, what would have changed would be only the sound configs... I didn't know if it was safe to just delete everything. I researched to make sure I deleted everything etc. Now, I know, one thing I may try to solve my problems is, if I don't have a deep knowledge of my configuration, I delete the whole on that system's part, and reinstall and reconfigure it myself. Of course, it this part of the system is not the core structure, like kernel and core modules etc.

So, to summarize it,

In my case,

LARBS's part,

 rm -rf $HOME/.config/alsa/

 rm -rf $HOME/.config/pavucontrol/

Finally, my own, alsa and pulse environments,

 rm -rf /etc/alsa

 rm -rf /etc/pulse

 rm -rf /var/lib/alsa

This makes sure there wont be no lock systems working for alsactl, for example. Which, I was unable to use to reconfigure asound.state. It was, at the end, the main problem, I believe. Together whit the LARBS's pulseaudio's configs.

Then, to get my files back, and normal functionality,

 sudo pacman -Sy pulseaudio pulseaudio-alsa alsa-lib alsa-tools alsa-plugins alsa-utils alsa-firmware

ALSA has many mechanisms to auto-detect, change and protect the configuration it generates.

Finally, I rebooted, and all my troubles, now, would seem so far away, as would say the Beatles.

Thanks V1del for your time, once more helping me out. And, in a side note, I don't need the /etc/modprobe.d/dha_fix.conf anymore. Yes, it seems the fix was incorporated by updates.

Arch Linux

#1 2020-05-20 17:11:35

ALSA unable to find card [SOLVED]

#2 2020-05-20 19:27:29

Re: ALSA unable to find card [SOLVED]

#3 2020-05-20 20:13:39

Re: ALSA unable to find card [SOLVED]

#4 2020-05-20 21:48:26

Re: ALSA unable to find card [SOLVED]

#5 2020-05-21 03:00:33

Re: ALSA unable to find card [SOLVED]

#6 2020-05-21 11:24:41

Re: ALSA unable to find card [SOLVED]

#7 2020-05-21 18:48:30

Re: ALSA unable to find card [SOLVED]

#8 2020-05-21 18:59:41

Re: ALSA unable to find card [SOLVED]

#9 2020-05-21 19:17:30

Re: ALSA unable to find card [SOLVED]

#10 2020-05-21 19:25:59

Re: ALSA unable to find card [SOLVED]

#11 2020-05-25 07:28:44

Re: ALSA unable to find card [SOLVED]

Board footer