You are not logged in.
- Topics: Active | Unanswered
#26 Other Issues » debootsrap to set up chroot environment? » 2023-03-04 08:49:11
- samhain
- Replies: 2
Could somebody give me a hint how to set up a minimal devuan chroot environment with debootstrap? I can install debian:
# debootstrap --variant=minbase stretch ./chroot http://deb.debian.org/debian
[...]
I: Base system installed successfully.
But I cannot install devuan:
# debootstrap --variant=minbase chimaera ./chroot http://deb.devuan.org/devuan
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id 72E3CB773315DFA2E464743D94532124541922FB)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on http://deb.devuan.org/devuan...
I: Retrieving apt 2.2.4+devuan1
I: Validating apt 2.2.4+devuan1
I: Retrieving libapt-pkg6.0 2.2.4+devuan1
I: Validating libapt-pkg6.0 2.2.4+devuan1
I: Retrieving base-files 11.1+devuan3
I: Validating base-files 11.1+devuan3
I: Retrieving devuan-keyring 2022.09.04
I: Validating devuan-keyring 2022.09.04
I: Retrieving libeudev1 3.2.9-10~chimaera1
I: Validating libeudev1 3.2.9-10~chimaera1
I: Retrieving init-system-helpers 1.60+devuan1
I: Validating init-system-helpers 1.60+devuan1
I: Retrieving bootlogd 2.96-7+devuan2
I: Validating bootlogd 2.96-7+devuan2
I: Retrieving initscripts 2.96-7+devuan2
I: Validating initscripts 2.96-7+devuan2
I: Retrieving sysv-rc 2.96-7+devuan2
I: Validating sysv-rc 2.96-7+devuan2
I: Retrieving sysvinit-core 2.96-7+devuan2
I: Validating sysvinit-core 2.96-7+devuan2
I: Retrieving sysvinit-utils 2.96-7+devuan2
I: Validating sysvinit-utils 2.96-7+devuan2
I: Retrieving bsdutils 1:2.36.1-8+devuan2
I: Validating bsdutils 1:2.36.1-8+devuan2
I: Retrieving libblkid1 2.36.1-8+devuan2
I: Validating libblkid1 2.36.1-8+devuan2
I: Retrieving libmount1 2.36.1-8+devuan2
I: Validating libmount1 2.36.1-8+devuan2
I: Retrieving libsmartcols1 2.36.1-8+devuan2
I: Validating libsmartcols1 2.36.1-8+devuan2
I: Retrieving libuuid1 2.36.1-8+devuan2
I: Validating libuuid1 2.36.1-8+devuan2
I: Retrieving mount 2.36.1-8+devuan2
I: Validating mount 2.36.1-8+devuan2
I: Retrieving util-linux 2.36.1-8+devuan2
I: Validating util-linux 2.36.1-8+devuan2
I: Chosen extractor for .deb packages: dpkg-deb
I: Extracting base-files...
I: Extracting libeudev1...
I: Extracting init-system-helpers...
I: Extracting bootlogd...
I: Extracting initscripts...
I: Extracting sysv-rc...
I: Extracting sysvinit-core...
I: Extracting sysvinit-utils...
I: Extracting bsdutils...
I: Extracting libblkid1...
I: Extracting libmount1...
I: Extracting libsmartcols1...
I: Extracting libuuid1...
I: Extracting mount...
I: Extracting util-linux...
W: Failure trying to run: chroot "/tmp/chroot" dpkg-deb -f Version
W: See /tmp/chroot/debootstrap/debootstrap.log for details
W: Failure trying to run: chroot "/tmp/chroot" mount -t proc proc /proc
W: See /tmp/chroot/debootstrap/debootstrap.log for details
W: Failure trying to run: chroot "/tmp/chroot" mount -t sysfs sysfs /sys
W: See /tmp/chroot/debootstrap/debootstrap.log for details
W: Failure trying to run: chroot "/tmp/chroot" /sbin/ldconfig
W: See /tmp/chroot/debootstrap/debootstrap.log for details
/tmp/chroot/debootstrap/debootstrap.log:
chroot: failed to run command 'dpkg-deb': No such file or directory
chroot: failed to run command 'mount': No such file or directory
chroot: failed to run command 'mount': No such file or directory
chroot: failed to run command '/sbin/ldconfig': No such file or directory
(END)
So "dpkg-deb" is missing in the evironment.
Forcing it to the include list also fails:
# debootstrap --variant=minbase --include=dpkg chimaera ./chroot http://deb.devuan.org/devuan
I: Checking Release signature
I: Valid Release signature (key id 72E3CB773315DFA2E464743D94532124541922FB)
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on http://deb.devuan.org/devuan...
E: Couldn't find these debs: dpkg
Any clue what I missed?
#27 Re: ARM Builds » Which Raspberry Pi ? » 2022-10-06 16:20:28
Go to aliexpress.com and search for "RK3288" (ASUS Firefly) or "RK3399" for OrangePi4. Both have bad support (armbian at its best). And you can wonder who would be willing to pay €€€ for these ...
#28 Re: Devuan Derivatives » ISO to test: Devuan + Exegnulinux + LinuxCNC + stuff remaster » 2021-08-30 20:48:53
New image for RPi + chimaera + TDE: https://dev1galaxy.org/viewtopic.php?pid=31220#p31220 (no LinuxCNC any more)
#29 Re: ARM Builds » Testimage: RaspberryPi 3+, Chimaera + TDE 14.1 » 2021-08-30 20:43:26
I have uploaded a new version of Devuan Chimera + TDE:
Image: https://github.com/zwieblum/devuan-imag … tde.img.xz
sha256: https://github.com/zwieblum/devuan-imag … .xz.sha256
Release Notes: https://github.com/zwieblum/devuan-imag … /README.md
# UID / PWD:
pi / pi
root / < no password >Enjoy 
Screenshot: https://github.com/zwieblum/devuan-imag … pshot2.png (sorry, don't know how to get the img tag working)
#30 Re: ARM Builds » Testimage: RaspberryPi 3+, Chimaera + TDE 14.1 » 2021-07-29 15:28:27
I uploaded a new chimaera image for RaspberryPi: https://dev1galaxy.org/viewtopic.php?pid=30913#p30913 - version with TDE will come in some days.
#31 Re: Devuan Derivatives » ISO to test: Devuan + Exegnulinux + LinuxCNC + stuff remaster » 2021-07-29 15:26:39
I just uploaded a new chimaera image for RaspberryPi 3A+ / 3B+ / Rpi400. This is a minimal image. It fits fine on a 4GB SD-Card. WiringPi is included, as are the special programs from raspberrypi.org (raspistill, raspi-config ...) - just the right thing to get you started.
Release notes and download link:
https://github.com/zwieblum/devuan-imag … 2021.07.29
direct download link:
https://github.com/zwieblum/devuan-imag … -29.img.xz
#32 Re: Devuan » Debian has fallen. What now? » 2021-07-28 13:32:01
another of my proposal was make the trinity desktop the default in devuan but as aways rejected and without interes
The reson given was that the TDE build sould run iside the devuan buildbot environment. As there is not enough manpower to do this (and from the TDE side there's no need to do this) it will not happen in the "near" future.
That is a shame, trinity desktop looks better visually then kde or gnome in my opinion...
Definitly. But it's just 5 lines to install TDE on devuan
#33 Re: Devuan » Chimaera First Impressions » 2021-07-28 13:19:11
You should get a RPi 3 and try to get chimera running. Fun guaranteed
#34 Re: Devuan Derivatives » An example of how Trinity Desktop Env (TDE) can look on Devuan ASCII » 2021-07-26 21:50:36
Traditional? Is there an other approach? I mean, ok, pure WMs like fvwm or tiling WMs are different ... but DEs? All "modern" DEs simply fall flat when it comes to configurability.
#35 Re: Devuan Derivatives » An example of how Trinity Desktop Env (TDE) can look on Devuan ASCII » 2021-07-23 20:18:22
Your screenshots don't show. "This content has been restricted. Using Cloudfare's basic service in this manner is a violation of the Terms of Service ..."
Could you please attach the screenshots to your postings?
#36 Re: Devuan » Windows 11 will _enforce_ Secure Boot » 2021-07-19 11:40:56
Not any difference in EU. Education system is transformed to create consume drones.
Microsoft doesn't care.
I think they care a lot. It's just they care for the wrong reason.
#37 Re: Devuan Derivatives » ISO to test: Devuan + Exegnulinux + LinuxCNC + stuff remaster » 2021-07-19 10:43:54
Sorry, due to problems with the LinuxCNC project I removed the images. When I find some spare time I'll upload new Chimaera+TDE images - but without LinuxCNC.
#38 Re: Desktop and Multimedia » What games do you play on Devuan?? » 2021-06-12 20:25:44
UT99 still works like a charm with the lastest ptches from this year. And "Die Siedler 2" .. ok, dosbox, but it works
#39 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-08 15:28:04
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,1This 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 16The 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 ... 
#40 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-08 13:38:18
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=-1Then 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 16Now 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
#41 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-07 16:12:20
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 
#42 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-07 11:59:20
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?
#43 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-07 10:31:54
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)
#44 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-07 08:58:25
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.
#45 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-07 08:05:00
/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.... kmixIf 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).
#46 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-07 07:08:44
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).
#47 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-07 04:54:33
Does not change anything.
Maybe I did not make myself clear: The problem is not changing the default sound card. The problem is, that chromium cannnot access any mic other than the ones on card#0 (see the error messages in my first posting).
#48 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-06 13:12:48
No pulseaudio here.
Sorry, what do you expect alamixer to do for me in this context? It changes volume, well, bright. And now?
#49 Re: Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-06 11:28:55
Aehm ... how would I do that?
#50 Desktop and Multimedia » Chromium + ALSA + jitzsi: mic problem after update » 2021-06-05 16:19:47
- samhain
- Replies: 24
I ran into this problem 2 days ago that I have still not solved: I use meet.jits.si for video calls. After the last dist-upgrade 2 days ago chromium is only able to use the analog mic on card#0 (onboard sound, analog mic).
"CinemaTM" is a usb webcam with mic. Chromium should use this as input source. Audacity can record from this and all other devices. But chromium throws these errors and can only use card#0 als input source:
[32699:32699:0605/181623.227218:ERROR:alsa_util.cc(204)] PcmOpen: plughw:CARD=MID,DEV=0,Device or resource busy
[32699:32699:0605/181623.914074:ERROR:alsa_util.cc(204)] PcmOpen: plughw:CARD=MID,DEV=2,Device or resource busy
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
[32699:32699:0605/181624.662853:ERROR:alsa_util.cc(204)] PcmOpen: sysdefault:CARD=MID,Device or resource busy
[32699:32699:0605/181625.338318:ERROR:alsa_util.cc(204)] PcmOpen: front:CARD=MID,DEV=0,Device or resource busy
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
[32699:32699:0605/181626.006963:ERROR:alsa_util.cc(204)] PcmOpen: dsnoop:CARD=MID,DEV=0,Device or resource busy
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
[32699:32699:0605/181626.692565:ERROR:alsa_util.cc(204)] PcmOpen: dsnoop:CARD=MID,DEV=2,Device or resource busy
[32699:32699:0605/181627.363953:ERROR:alsa_util.cc(204)] PcmOpen: hw:CARD=Creative,DEV=0,Device or resource busy
[32699:32699:0605/181629.452046:ERROR:alsa_util.cc(204)] PcmOpen: plughw:CARD=Creative,DEV=0,Device or resource busy
ALSA lib control.c:1471:(snd_ctl_open_noupdate) Invalid CTL CARD=Creative
[32699:32699:0605/181631.507317:ERROR:alsa_util.cc(309)] MixerAttach, CARD=Creative, No such file or directory
[32699:32699:0605/181632.192573:ERROR:alsa_util.cc(204)] PcmOpen: front:CARD=Creative,DEV=0,Device or resource busy
[32699:32699:0605/181632.847111:ERROR:alsa_util.cc(204)] PcmOpen: iec958:CARD=Creative,DEV=0,Device or resource busy
ALSA lib pcm.c:8620:(snd_pcm_set_params) Sample format not available for CAPTURE: Invalid argument
[32699:32699:0605/181633.550498:ERROR:alsa_util.cc(71)] PcmHwParamsSetFormat: Invalid argument
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
[32699:32699:0605/181634.238636:ERROR:alsa_util.cc(204)] PcmOpen: dsnoop:CARD=Creative,DEV=1,Device or resource busy
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
[32699:32699:0605/181634.919781:ERROR:alsa_util.cc(204)] PcmOpen: dsnoop:CARD=Creative,DEV=2,Device or resource busy
ALSA lib pcm.c:8627:(snd_pcm_set_params) Channels count (2) not available for CAPTURE: Invalid argument
[32699:32699:0605/181635.595592:ERROR:alsa_util.cc(77)] PcmHwParamsSetChannels: Invalid argument
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
[32699:32699:0605/181637.037891:ERROR:alsa_util.cc(204)] PcmOpen: sysdefault:CARD=CinemaTM,Device or resource busy
[32699:32699:0605/181637.743723:ERROR:alsa_util.cc(204)] PcmOpen: front:CARD=CinemaTM,DEV=0,Device or resource busy
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
[32699:32699:0605/181638.419383:ERROR:alsa_util.cc(204)] PcmOpen: dsnoop:CARD=CinemaTM,DEV=0,Device or resource busyMy hardware:
$ cat /proc/asound/cards
0 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xf3000000 irq 17
1 [MID ]: HDA-Intel - HDA Intel MID
HDA Intel MID at 0xf3120000 irq 37
2 [Creative ]: HDA-Intel - HDA Creative
HDA Creative at 0xf3200000 irq 16
3 [CinemaTM ]: USB-Audio - Microsoft® LifeCam Cinema(TM)
Microsoft Microsoft® LifeCam Cinema(TM) at usb-0000:00:1d.Audio sinks:
$ aplay -l
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: NVidia [HDA NVidia], Gerät 3: HDMI 0 [HDMI 0]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: NVidia [HDA NVidia], Gerät 7: HDMI 1 [HDMI 1]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: NVidia [HDA NVidia], Gerät 8: HDMI 2 [HDMI 2]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: NVidia [HDA NVidia], Gerät 9: HDMI 3 [HDMI 3]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: NVidia [HDA NVidia], Gerät 10: HDMI 4 [HDMI 4]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 1: MID [HDA Intel MID], Gerät 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 2: Creative [HDA Creative], Gerät 0: CA0132 Analog [CA0132 Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 2: Creative [HDA Creative], Gerät 1: CA0132 Digital [CA0132 Digital]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0Audio sources:
arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: MID [HDA Intel MID], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: MID [HDA Intel MID], device 2: ALC662 rev1 Alt Analog [ALC662 rev1 Alt Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Creative [HDA Creative], device 0: CA0132 Analog [CA0132 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Creative [HDA Creative], device 1: CA0132 Digital [CA0132 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Creative [HDA Creative], device 2: CA0132 What U Hear [CA0132 What U Hear]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: CinemaTM [Microsoft® LifeCam Cinema(TM)], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0Any idea what I can do to persuade chromium to use the usb mic again?
Board footer
