You are not logged in.
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.
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.
UT99 still works like a charm with the lastest ptches from this year. And "Die Siedler 2" .. ok, dosbox, but it works ![]()
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 ... ![]()
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 ![]()
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 ![]()
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?
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)
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.
/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).
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).
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).
No pulseaudio here.
Sorry, what do you expect alamixer to do for me in this context? It changes volume, well, bright. And now?
Aehm ... how would I do that?
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?
Oh, you did reboot after raspi-config, did you?
@raspi-config: Thanks for testing ... looks like I'll need to craft my own tool ![]()
Glad it works on RPi 4
to expand the partition you can use "raspi-config": "su" -> raspi-config -> Advanced -> expand ... (don't know how that menu entry is named). Root password is "toor".
I'll need to test the USB3 port on my RPi400. Do you get these errors when you use a SD-card, too?
I just finished uploading the image for RaspberryPi3+. It is based on Devuan Chimaera + TDE 14.1:
I just uploaded a new image of Devuan Chimaera + TDE 14.1. The image was tested on RPi 3+, it should work on RPi4 and RPi 400, too.
https://github.com/zwieblum/devuan-imag … tde.img.xz
UID/PWD: pi/pi and root/toor
Enjoy ![]()
Just uploaded the spring 2021 update: newest devuan beowulf, linuxcnc 2.8.1, all tools upgraded to latest version and most noticable: TDE 14.1. Enjoy ![]()
PREEMPT RT:
ISO: https://github.com/zwieblum/devuan-imag … 021-04.iso
SHA256: https://github.com/zwieblum/devuan-imag … iso.sha256
RTAI Kernel:
ISO: https://github.com/zwieblum/devuan-imag … 021-04.iso
SHA256: https://github.com/zwieblum/devuan-imag … iso.sha256
Release 2021.04 and up: root / toor and user / user.
oops, late reply ![]()
I think they should be included in the image, but I am not sure if they are worth the trouble: the realtime patchset is unmatained since some months and the armbian kernel only builds inside the armbian docker image or on the device itself - in both cases the .config is included.
Is there a working devuan image for RaspberryPi Zero W around somewhere? I know I had one winning ~ 2 years ago, but the ascii image of devuan does not work on current Zeros any more ![]()
Hi friends of Devuan and it's desendents!
This is my remaster of Exegnulinux + LinuxCNC 2.8 + HTML Docs, NCAM, PREEMPT Kernel, smictrl, ... and a whole toolkit with
F-Engrave, dmap2gcode, g-Code_Ripper, pycam 0.7, dxf2gcode, pcb2gcode & pcb2gcodeGUI, KiCad, Gimp, Inkscape, Slic3r, Printrun, OpenScad ... and some more ![]()
Architecture: amd64
https://github.com/zwieblum/devuan-imag … 8_2302.iso
https://github.com/zwieblum/devuan-imag … iso.sha256
Please feel free to test an give feedback ![]()

PWD/UID: root/root and user/user
Nik
For all owners of OrangePi Zero (LTS) and OrangePi PC Plus: I've remastered the latest armbian images to use devuan.
https://github.com/zwieblum/devuan-images