I tested a recent nightly build of the dsd-neo "AppImage" under Red Hat Enterprise Linux 9.7, and was able to successfully scan a local P25 system!
I started in a basic command-line environment, and learned that I needed to ensure that the libXau, libxcb, and fuse-overlayfs packages were installed. Then I ran the following script.
Initially, I set the "center frequency" to the numerical center of the system's frequency range, but that didn't work as well as setting it to the currently active control frequency. Screenshot:

As it happens, many of the P25 channels are also on a currently operational EDACS system. When I tested dsd-neo on this EDACS system, though, it froze after the first call. I did not investigate further.
Nevertheless, seeing the P25 output was pretty cool. Thanks, @arancormonk!
I started in a basic command-line environment, and learned that I needed to ensure that the libXau, libxcb, and fuse-overlayfs packages were installed. Then I ran the following script.
Bash:
#!/bin/bash
export TZ="America/Denver"
RTL_ID="0"
# Las Cruces P25 - https://www.radioreference.com/db/sid/13465
CSV_SITE="lc.csv"
#CSV_GROUPS="db/groups/391/391.csv"
# center frequency
#FREQ="853.309M"
FREQ="852.950M"
AGC="0"
PPM="0"
BW="24"
# trunking with RTL-SDR Blog V4
dsd-neo -ft -i rtl:"$RTL_ID":"$FREQ":"$AGC":"$PPM":"$BW":0:2 -T -C "$CSV_SITE" -o null -N 2> console_log.txt
Initially, I set the "center frequency" to the numerical center of the system's frequency range, but that didn't work as well as setting it to the currently active control frequency. Screenshot:

As it happens, many of the P25 channels are also on a currently operational EDACS system. When I tested dsd-neo on this EDACS system, though, it froze after the first call. I did not investigate further.
Nevertheless, seeing the P25 output was pretty cool. Thanks, @arancormonk!
Last edited: