Hey Kai, Kai Vehmanen <kai.vehmanen@xxxxxxxxxxxxxxx> writes: > Hi Nico, > > On Thu, 27 May 2021, Nico Schottelius wrote: > >> > it seems more kernel config options are missing. Distribution kernels >> > typically enable all the machine drivers, but you are specifically missing >> > CONFIG_SND_SOC_INTEL_SKL_HDA_DSP_GENERIC_MACH=m >> >> I've enabled this one and all machine types and indeed the card is being >> recognised (report at >> http://alsa-project.org/db/?f=5cbe7c293cbb80ab548b892cfc8b991476b0b2aa). >> I checked permissions on /dev/snd, which looks good. >> >> However, obs does not list the microphone at all and >> chromium / jitsi shows the snd-hda-dsp mic, however does not let me >> select it. > > ok, that's great so the driver appears to work now. You could try > to do simple arecord test in terminal: > > arecord -fdat -vv -Dplugw:0,6 -c4 /dev/null That does not work: [15:55] nb3:~% arecord -fdat -vv -Dplugw:0,6 -c4 /dev/null ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM plugw:0,6 arecord: main:830: audio open error: No such file or directory However, recording with audacity produces to results: - no sound recorded by default - sound recorded when I plugin an external headset And using arecord -fdat -vv -c4 /dev/null (without -Dplugw) I get output, but the level is always 00% without the headset, ranges 02 ~ 90% with the headset plugged in. I was wondering if there's a hardware switch "broken" for the detection of the headset and that's why the mic is muted internally? -- Sustainable and modern Infrastructures by ungleich.ch
