Dev1 Galaxy Forum / Chromium + ALSA + jitzsi: mic problem after update

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (samhain) — Tue, 08 Jun 2021 15:28:04 +0000

That makes live easier, thank you!

Now I have :

# /etc/modprobe.d/alsa-base.conf
options snd_usb_audio index=0
options snd_hda_intel index=3,2,1 enable=0,0,1

This makes the soundblaster (3rd card) the soundcard with index #1 and hides the other 2 builtin cards. I still have to assign uniq indizes to the individual cards, otherwise #0 is gone again.

# cat /proc/asound/cards
 0 [CinemaTM       ]: USB-Audio - Microsoft® LifeCam Cinema(TM)
                      Microsoft Microsoft® LifeCam Cinema(TM) at usb-0000:00:1d.0-1.7, high speed
 1 [Creative       ]: HDA-Intel - HDA Creative
                      HDA Creative at 0xf3200000 irq 16

The fun part of that: with only 2 cards left, chromium can handle exact one input source per card correctly, be it card#0 or card#1. Oh my ...

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (Geoff 42) — Tue, 08 Jun 2021 14:56:51 +0000

I had some fun with sound some time ago. The problem was with 2 outputs sharing the module snd-hda-intel. It found HDMI first, which became the default.
The solution I found was to disable HDMI with

# Disable the HDMI card which shows up first, but enable PCH
options snd-hda-intel enable=0,1

in /etc/modprobe.d/alsa-base.conf

http://forums.debian.net/viewtopic.php?t=110572#p525601

Geoff

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (samhain) — Tue, 08 Jun 2021 13:38:18 +0000

Ok, not solved, but there's a workaround for that piece of crap aka chromium:

Make sure the webcam is plugged in at boottime, otherwise alsa card enumeration will assign #0 to some other card. Then make snd_usb_audio card#0 and all other cards "not the default":

# /etc/modprobe.d/alsa-base.conf
options snd_usb_audio index=0
options snd_hda_intel index=-1

Then reboot and observe:

$ cat /proc/asound/cards
 0 [CinemaTM       ]: USB-Audio - Microsoft® LifeCam Cinema(TM)
                      Microsoft Microsoft® LifeCam Cinema(TM) at usb-0000:00:1d.0-1.8, high speed
 1 [MID            ]: HDA-Intel - HDA Intel MID
                      HDA Intel MID at 0xf3120000 irq 37
 2 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xf3000000 irq 17
 3 [Creative       ]: HDA-Intel - HDA Creative
                      HDA Creative at 0xf3200000 irq 16

Now chromium https://meet.jit.si/just-a-room]https:/ … ust-a-room can be started. The preselected mic is still the first input source of the internal soundcard, but by some miracle the usb mic is now selectable and working - at least one of the 12 virtual mics of the single usb mic, usally the second. And what a surprise: the usb mic stays #0 if it's unplugged/replugged.

Now the next question: isn't there a way to reserve #0 for snd_usb_audio, regardless if it's present or not? Assinging a fixed index to snd_hda_intel does not work, as all 3 internal cards are served by that module.

EDIT: Using options snd_hda_intel index=1,2,3 will reserve card #0 for the 4th soundcard or snd_usb_audio - whatever comes first. You might call that a mатрёшка workaround

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (samhain) — Mon, 07 Jun 2021 16:12:20 +0000

I prefer not to build my own kernel - the deb-src for 5.10.28 is gone, as are kernel + headers --> nvidia drivers will not be happy ... and most likely everything with alsa in its name needs to be reverted and rebuilt. Sonds like a doomsday plan to me

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (ralph.ronnquist) — Mon, 07 Jun 2021 13:38:07 +0000

As @GlennW noted the kernel package is available in the alpha-20210503 ISO, which I could find from Devuan's backup, but that doesn't include the headers.

Possibly you could get them from the "orginal source" which I think would be
https://www.kernel.org/pub/linux/kernel … .28.tar.xz

.. but then there's the caveat that this might be well a "red herring"....

EDIT: Note that Debian has a couple of patches applied to header files. Though off the top they don't seem to concern graphics.

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (samhain) — Mon, 07 Jun 2021 11:59:20 +0000

Nop, does not work. linux-headers-5.10.0-0.bpo.5-amd64=5.10.24-1~bpo10+1 would like linux-compiler-gcc-8-x86, which is not available on chimera. Adding beowulf repositories and trying to install that kernel+header results in apt suggesting to kill my system.

Isn't there an archive where I can get the older kernel+headers?

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (ralph.ronnquist) — Mon, 07 Jun 2021 11:39:58 +0000

That might be right; and the corresponding linux-headers would be at least in the server and desktop isos.
Though, the chimaera alpha ISOs are rebuilt every Monday and might now hold only the 5.10.0-7 package(s).

You find linux-image-5.10.0-0 in beowulf-backports. That's kernel version 5.10.24 (as opposed to 5.10.40 that is packaged as linux-image-5.10.0-7 and kernel version 5.10.28 that was packaged into linux-image-5.10.0-6)

Links for direct download of the .deb(s) could be:
linux-image-5.10.0-0.bpo.5-amd64=5.10.24-1~bpo10+1
and
linux-headers-5.10.0-0.bpo.5-amd64=5.10.24-1~bpo10+1

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (GlennW) — Mon, 07 Jun 2021 11:25:47 +0000

the kernel is in the iso, extract the iso to a directory... and look up

/devuan_chimaera_4.0.alpha-20210503_amd64_netinstall/pool/DEBIAN/main/l/linux-signed-amd64/linux-image-5.10.0-6-amd64_5.10.28-1_amd64.deb

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (samhain) — Mon, 07 Jun 2021 10:31:54 +0000

apparmor is not installed, but libapparmor1 - it's pulled in by dbus.

Any idea where I can get the older kernel and headers? I can repackage the kernel from my other machine, but I did not install the headers there (and I need them for nvidia)

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (ralph.ronnquist) — Mon, 07 Jun 2021 09:13:54 +0000

Hmm that observation suggests it relates to the kernel version?
or is there some apparmor involved?

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (samhain) — Mon, 07 Jun 2021 08:58:25 +0000

Definitly. To be more precise: a clone of users homedirectory running on a devuan that was not upgraded (Kernelpackage 5.10.0-6-amd64 and chromium 89) does not show this problem. Chromium 89 + 5.10.0-7 alsow shows this problem.

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (ralph.ronnquist) — Mon, 07 Jun 2021 08:18:51 +0000

Yes it appears to be fully chromium's problem... are you sure it runs with your credentials rather than some "sandbox user" ?

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (samhain) — Mon, 07 Jun 2021 08:05:00 +0000

/dev/snd/controlC0:  samhain        2217 F.... kmix
/dev/snd/controlC1:  samhain        2217 F.... kmix
/dev/snd/controlC2:  samhain        2217 F.... kmix
/dev/snd/controlC3:  samhain        2217 F.... kmix

If that were a problem, chromium could not access card#0, either. Nor could audacity, which works like expected. Killing kmix does not make any difference (well, the device is not accessed by anything then).

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (ralph.ronnquist) — Mon, 07 Jun 2021 07:59:35 +0000

You might try running

fuser -v /dev/snd/*

to see which if any (other) process "owns" the device.

Re: Chromium + ALSA + jitzsi: mic problem after update

dummy@example.com (samhain) — Mon, 07 Jun 2021 07:08:44 +0000

My user is in group audio, all sound devices are accessable. Otherwise audacity would not work (see my first post):

$ ll /dev/snd/*
crw-rw----+ 1 root audio 116, 12  7. Jun 08:56 /dev/snd/controlC0
crw-rw----+ 1 root audio 116, 13  7. Jun 08:56 /dev/snd/controlC1
crw-rw----+ 1 root audio 116, 20  7. Jun 08:56 /dev/snd/controlC2
crw-rw----+ 1 root audio 116, 22  7. Jun 09:01 /dev/snd/controlC3
crw-rw----+ 1 root audio 116, 11  7. Jun 08:56 /dev/snd/hwC0D0
crw-rw----+ 1 root audio 116,  7  7. Jun 08:56 /dev/snd/hwC1D0
crw-rw----+ 1 root audio 116, 19  7. Jun 08:56 /dev/snd/hwC2D1
crw-rw----+ 1 root audio 116,  9  7. Jun 09:04 /dev/snd/pcmC0D0c
crw-rw----+ 1 root audio 116,  8  7. Jun 08:56 /dev/snd/pcmC0D0p
crw-rw----+ 1 root audio 116, 10  7. Jun 09:04 /dev/snd/pcmC0D2c
crw-rw----+ 1 root audio 116,  6  7. Jun 08:56 /dev/snd/pcmC1D10p
crw-rw----+ 1 root audio 116,  2  7. Jun 08:56 /dev/snd/pcmC1D3p
crw-rw----+ 1 root audio 116,  3  7. Jun 08:56 /dev/snd/pcmC1D7p
crw-rw----+ 1 root audio 116,  4  7. Jun 08:56 /dev/snd/pcmC1D8p
crw-rw----+ 1 root audio 116,  5  7. Jun 08:56 /dev/snd/pcmC1D9p
crw-rw----+ 1 root audio 116, 15  7. Jun 09:04 /dev/snd/pcmC2D0c
crw-rw----+ 1 root audio 116, 14  7. Jun 09:04 /dev/snd/pcmC2D0p
crw-rw----+ 1 root audio 116, 18  7. Jun 09:04 /dev/snd/pcmC2D1c
crw-rw----+ 1 root audio 116, 17  7. Jun 08:56 /dev/snd/pcmC2D1p
crw-rw----+ 1 root audio 116, 16  7. Jun 09:04 /dev/snd/pcmC2D2c
crw-rw----+ 1 root audio 116, 21  7. Jun 09:04 /dev/snd/pcmC3D0c
crw-rw----+ 1 root audio 116,  1  7. Jun 08:56 /dev/snd/seq
crw-rw----+ 1 root audio 116, 33  7. Jun 08:56 /dev/snd/timer

"kmix" uses /dev/controlC* non-exclusively. Killing kmix does not make any difference (as expected).