@igorzwx its obvious you are a chatbot, and because you are a chatbot there is nothing you can say that will prove that you are not.

igorzwx is obviously still stuck on ChatGPT4, they attempted to fix hallucinations in the ChatGPT5 release

https://en.wikipedia.org/wiki/Hallucina … elligence)

Hi, I would resort to configuring ALSA directly at the system level and not rely on any app.

I would edit /etc/asound.conf defining a mono 'type dsnoop' device that corresponds to the Mic.
(use 'arecord -l' to show you the CARD names ALSA is using)

pcm.dji_mic {
        type dsnoop
        ipc_key 34848
        ipc_key_add_uid true
        ipc_perm 0666
        slave.pcm {
            type hw
            card "DJITHINGY"
            device 0  # mic
            channels 1
        }
    }

I would the wrap that device definition with another of 'type route' with two channels, which maps the
single mic channel onto both channels.

pcm.stereo_dji_mic {
    type route
    slave.pcm  dji_mic
    ttable {
      0.0 1.0 # left to left at full volume
      0.1 1.0  # left to right at full volume
    }
    channels 2
}

I would then wrap the stereo mic with type plug to manage format conversions

pcm.source {
   type plug
   slave.pcm stereo_dji_mic
}

Once configured run 'arecord -L'
if /etc/asound.conf is wrong or has syntax errors etc that command will barf with an error message you can google

The above is off the top of my head but should enable you to search for what you need.

@igorzwx are you are volunteering to show me the math where 'average' > 50% ?

After all the bad news I have read about trixie I will be postponing dist-upgrade (or full-ugrade).

I have no need or interest in a distro optimised for cloud (AWS etc) or hosting dozens of VM's.
I was hoping for a change in leadership and a board moving away from commercialisation of the distro, but it looks like IBM\Redhat have won.
At some point I will need to break away from Debian as the upstream for technical reasons, and unfortunately that will mean Devuan too.
For the long term there is only one possible way out I can see, the freezing of the distro (here before 'usrmerge') as 'Trinity Desktop Environment' did with KDE3.
History is a great teacher, if you think 'usrmerge' is a good idea then go research the reason for the split in the first place (Bell Labs, AT&T).

I do not understand this craze for constantly replacing reliable efficient software for newer software which brings nothing to the table other than being newer and doing something differently (not better).
New kernels (security fixes and new modules for new hardware) will be required from time to time, and the occasional new userspace app to manage them, but that is it.
To me that looks like the perfect distro model for "Continuous Integration" or if you prefer the term, "Rolling Release"

"If it ain't broken don't fix it!"

Only use resources for fixing what is broken, not willy-nilly changing of packages.

Andre4freedom, can you post what you changed in  /etc/hosts and describe what did\didnt happen.
Once I know that I can test my install to see if it is affected.

rolfie cannot see what you did or their results.
You will need to post more information for rolfie to be able to help you.

What commands did you actually enter ?
What was the result of those commands ?

How did you reboot your PC ?
What boot options did you select ?
What did the PC report ?

I suggest you try again, this time making *exact* notes most of which you can cut and paste, then after rebooting post them here on the forum.

@rolfie experience has taught me that when it comes down to UEFI the wonderful thing about standards is that there are so many to choose from. This varies at the BIOS version level not just the model. Even totally ridiculous ideas should not be dismissed until they have been attempted to make something boot that wont.

@r2, I had issues with Devuan 5.0.1 USB not booting on a Dell Laptop (it should have at least booted to the installer, 5.0.0 did).
I discovered that on booting USB the internal storage would be disabled. This it turns out is a Dell 'Security Feature' in my particular BIOS and the only way around it (untested) is to pre-load the USB's UEFI keys and enable 'Secure Boot'. So at that point I gave up jumping through Dell hoops, removed the NVMe and installed Devuan via a VM, booted fine when reinstalled in the laptop.

The last time i looked...

Errors were encountered while processing:
nvidia-persistenced

This error was caused by the dep package script failing to start (not stopping first) an already running daemon.
Just manually stop 'nvidia-persistenced' and then 'apt -f install' to let the script start 'nvidia-persistenced' itself and complete.