haver you tried checking the audio sink? I have that issue back then when I install DragonOS on my machine.
From Rex’s AIO board package: HackerGadgets AIO Board Package
If you’re using Trixie you’ll need to add an audio sink. On the left side scroll down to
Module Manager. At the bottom ofModule Managertypeaudioand selectlinux_pulseaudio_sinkthen click the+symbol. Then add the audio sink in theSinksmenu on the left side back up towards the top.
Hi
I did now, but i am on DragonOS even before the AIO2 updates and board , so expected that did nothing - check below my settings
Put the Linux sink to try and restart just in case
Same for CubicSDR
I am pretty sure if i could run Gqrx it would run- has happened in the past on Ubuntu
However if i use the Interceptor thing - it works and there is sound if something is up and static/noise if not
So i would probbaly do new fresh install later, was just curious why its happening 
Anyways decided to check just in case
I’ve been having issues getting the RTL to show up at all.
Looks like it should be on…
uname -a
Linux cheri.vpn.something 6.12.52-v8-16k+ #4 SMP PREEMPT Fri Oct 17 13:41:18 EDT 2025 aarch64 GNU/Linux
aiov2_ctl --status
AIO v2 Status
====================
GPS GPIO27: ON
LORA GPIO16: ON
SDR GPIO7: ON
USB GPIO23: ON
--------------------
Source : AC
Status : Charging
Capacity : 100%
Direction : idle
Mode : AC powering system
Voltage : 4.23 V
Current : 0.01 A
Power : 0.04 W
lsusb
Bus 001 Device 004: ID 1a86:8091 QinHeng Electronics USB HUB
Bus 001 Device 003: ID 1eaf:0024 Leaflabs uConsole
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pinctrl | grep GPIO7
7: op dh pu | hi // GPIO7 = output
sudo rtl_test
No supported devices found.
is the DVB blacklisted ?
Yup! That it is. Also had the previous AIO board with the SDR and it worked fine.
vvelox@cheri:~ $ cat /etc/modprobe.d/blacklist.conf
blacklist dvb_usb_rtl2832u
blacklist dvb_usb_rtl28xxu
blacklist dvb_usb_v2
blacklist rtl2830
blacklist rtl2832
blacklist rtl2832_sdr
blacklist rtl2838
vvelox@cheri:~ $ lsmod | grep dvb
vvelox@cheri:~ $ lsmod | grep rtl
vvelox@cheri:~ $ lsmod
Module Size Used by
wireguard 114688 0
libchacha20poly1305 49152 1 wireguard
chacha_neon 65536 1 libchacha20poly1305
poly1305_neon 65536 1 libchacha20poly1305
ip6_udp_tunnel 49152 1 wireguard
udp_tunnel 49152 1 wireguard
libcurve25519_generic 65536 1 wireguard
libchacha 49152 1 chacha_neon
snd_seq_dummy 49152 0
snd_hrtimer 49152 1
snd_seq 98304 7 snd_seq_dummy
snd_seq_device 49152 1 snd_seq
squashfs 65536 0
rfcomm 81920 18
algif_hash 49152 1
algif_skcipher 49152 1
af_alg 49152 6 algif_hash,algif_skcipher
bnep 49152 2
binfmt_misc 49152 1
axp20x_battery 49152 0
axp20x_ac_power 49152 0
axp20x_adc 49152 0
industrialio 114688 3 axp20x_battery,axp20x_ac_power,axp20x_adc
rtc_pcf85063 49152 0
spidev 49152 2
brcmfmac_wcc 49152 0
panel_cwu50 49152 0
vc4 425984 6
joydev 49152 0
hci_uart 65536 0
snd_soc_hdmi_codec 49152 2
brcmfmac 376832 1 brcmfmac_wcc
btbcm 49152 1 hci_uart
rpi_hevc_dec 65536 0
drm_display_helper 49152 1 vc4
snd_soc_simple_card 49152 1
bluetooth 638976 47 hci_uart,btbcm,bnep,rfcomm
snd_soc_spdif_tx 49152 1
cec 65536 1 vc4
pisp_be 49152 0
snd_soc_simple_card_utils 49152 1 snd_soc_simple_card
cdc_acm 49152 0
rp1_aout 49152 2
brcmutil 49152 1 brcmfmac
aes_ce_blk 49152 4
v4l2_mem2mem 65536 1 rpi_hevc_dec
aes_ce_cipher 49152 1 aes_ce_blk
ghash_ce 49152 0
videobuf2_dma_contig 49152 2 pisp_be,rpi_hevc_dec
snd_soc_core 311296 6 rp1_aout,snd_soc_spdif_tx,vc4,snd_soc_hdmi_codec,snd_soc_simple_card_utils,snd_soc_simple_card
videobuf2_memops 49152 1 videobuf2_dma_contig
cfg80211 1032192 1 brcmfmac
videobuf2_v4l2 49152 3 pisp_be,rpi_hevc_dec,v4l2_mem2mem
snd_compress 49152 1 snd_soc_core
ecdh_generic 49152 2 bluetooth
gf128mul 49152 1 ghash_ce
ecc 65536 1 ecdh_generic
sha2_ce 49152 0
sha256_arm64 49152 1 sha2_ce
snd_pcm_dmaengine 49152 1 snd_soc_core
snd_pcm 147456 5 snd_soc_hdmi_codec,snd_compress,snd_soc_simple_card_utils,snd_soc_core,snd_pcm_dmaengine
videodev 344064 4 pisp_be,rpi_hevc_dec,videobuf2_v4l2,v4l2_mem2mem
rfkill 49152 7 bluetooth,cfg80211
sha1_ce 49152 0
libaes 49152 4 aes_ce_cipher,bluetooth,ghash_ce,aes_ce_blk
snd_timer 65536 3 snd_seq,snd_hrtimer,snd_pcm
snd 131072 11 snd_seq,snd_seq_device,snd_soc_hdmi_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm
v3d 212992 8
drm_rp1_dsi 49152 7
videobuf2_common 98304 6 pisp_be,rpi_hevc_dec,videobuf2_dma_contig,videobuf2_v4l2,v4l2_mem2mem,videobuf2_memops
sha1_generic 49152 1 sha1_ce
mc 81920 6 videodev,pisp_be,rpi_hevc_dec,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
drm_ttm_helper 49152 2 drm_rp1_dsi
gpio_keys 49152 0
i2c_brcmstb 49152 0
raspberrypi_hwmon 49152 0
ttm 131072 1 drm_ttm_helper
rp1_pio 65536 0
spi_bcm2835 49152 0
gpu_sched 98304 1 v3d
drm_shmem_helper 49152 1 v3d
drm_dma_helper 49152 2 drm_rp1_dsi,vc4
ocp8178_bl 49152 0
drm_kms_helper 245760 5 drm_dma_helper,drm_rp1_dsi,vc4,drm_shmem_helper,drm_ttm_helper
rp1_fw 49152 1 rp1_pio
raspberrypi_gpiomem 49152 0
i2c_gpio 49152 0
i2c_designware_platform 49152 0
i2c_designware_core 49152 1 i2c_designware_platform
i2c_algo_bit 49152 1 i2c_gpio
spi_dw_mmio 49152 0
rp1_mailbox 49152 1
rp1_adc 49152 0
spi_dw 49152 1 spi_dw_mmio
nvmem_rmem 49152 0
uio_pdrv_genirq 49152 0
uio 49152 1 uio_pdrv_genirq
ledtrig_pattern 49152 0
drm 688128 23 gpu_sched,drm_kms_helper,panel_cwu50,drm_dma_helper,v3d,drm_rp1_dsi,vc4,drm_shmem_helper,drm_display_helper,drm_ttm_helper,ttm
drm_panel_orientation_quirks 65536 1 drm
fuse 196608 3
backlight 49152 4 drm_kms_helper,panel_cwu50,ocp8178_bl,drm
dm_mod 163840 0
ip_tables 65536 0
ipv6 606208 65 wireguard
Would you know whether this script is compatible with the radxa board?
Update: I found at in a different thread that the scrip did not work.
Can anyone here point to the steps for the Radxa boards?
i am having trouble getting meshtastic to work. i checked the antenna connection and lora is enabled but meshtastic says it has no signal.
anyone run into this?
check your config, disable GPS and run meshtasticd in debug. see if there are any obvious issues.
solved in another thread. my channel was wrong, as compared o other nodes in the area
Do you all have working Ethernet on AIOv2?
solved
Ethernet Fix for uConsole CM5 with HackerGadgets AIO v2 Board
clockworkpi-uconsole-cm5.dtboAfter installing the AIO v2 board with its RJ45 Ethernet port, the eth0 network interface does not appear in the system. Running ip link show only shows lo and wlan0 — no Ethernet interface is present despite the hardware being physically connected.
The clockworkpi-uconsole-cm5.dtbo device tree overlay explicitly disables the Ethernet controller. Decompiling the overlay reveals:
fragment@5 {
target-path = "ethernet0";
__overlay__ {
status = "disabled";
};
};
This makes sense for the standard uConsole which has no Ethernet PHY on its carrier board — the CM5 module includes the MAC (Cadence GEM via RP1 south bridge) and the MDIO bus, but without a physical PHY chip connected to the RGMII pins, enabling Ethernet would just produce errors.
However, the AIO v2 board routes the CM5’s RGMII signals to a Broadcom BCM54213PE PHY connected to the RJ45 jack. Since the overlay disables Ethernet before the PHY can be probed, the interface never appears.
Create a secondary device tree overlay that re-enables the Ethernet node. This overlay must be loaded after clockworkpi-uconsole-cm5 so that it overrides the disabled status.
cat > /tmp/enable-ethernet.dts << 'EOF'
/dts-v1/;
/plugin/;
/ {
compatible = "brcm,bcm2712";
fragment@0 {
target-path = "ethernet0";
__overlay__ {
status = "okay";
};
};
};
EOF
sudo dtc -I dts -O dtb -o /boot/firmware/overlays/enable-ethernet.dtbo /tmp/enable-ethernet.dts
Edit /boot/firmware/config.txt and add dtoverlay=enable-ethernet in the [pi5] section, after the uConsole overlay:
[pi5]
...
dtoverlay=clockworkpi-uconsole-cm5
dtoverlay=enable-ethernet
...
The ordering is critical — the enable overlay must come after the disable to override it.
sudo reboot
After reboot, the Ethernet interface appears and the PHY is correctly detected:
$ ip link show eth0
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN ...
link/ether 88:a2:9e:38:b8:53 brd ff:ff:ff:ff:ff:ff
$ dmesg | grep eth
macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 108
macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:00] driver [Broadcom BCM54213PE] (irq=165)
macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode
After plugging in a cable, the link comes up at Gigabit speed:
$ sudo ethtool eth0 | grep -E "Speed|Link"
Speed: 1000Mb/s
Link detected: yes
NetworkManager automatically creates a “Wired connection 1” profile and will obtain an IP via DHCP when a cable is connected.
Ideally, the clockworkpi-uconsole-cm5.dtbo overlay should not unconditionally disable Ethernet. Users with AIO v2 (or any other extension board providing an Ethernet PHY) are forced to create a workaround overlay.
A cleaner approach would be to either:
Remove fragment@5 from the overlay entirely — if no PHY is present, the macb driver will simply fail to find a link partner and the interface will remain in NO-CARRIER state, which is harmless.
Provide a separate overlay (e.g., clockworkpi-uconsole-cm5-no-ethernet.dtbo) for users who explicitly want to disable it, rather than disabling by default.
Document the fix in the AIO v2 setup guide so users with the extension board know to add dtoverlay=enable-ethernet after the uConsole overlay.
The CM5 exposes two Ethernet-related GPIOs:
ETH_RST_N): PHY reset, active low. With the DT fix applied, the kernel manages this pin automatically via the macb driver.ETH_IRQ_N): PHY interrupt line.These pins are not used by the AIO v2’s other peripherals (GPS=GPIO27, LoRa=GPIO16, SDR=GPIO7, USB=GPIO23), so there is no conflict.
That was a mistake on an image that I put out and fixed it the next morning. You must have downloaded that image while I had it posted with the mistake in it. Newer images that’s fixed in.
Or can you try reinstalling the kernel to see if that fixes the overlay. sudo apt reinstall clockworkpi-kernel
I am having trouble getting uconsole yo boot with aio v2 installed. The hardware were Radxa CM5 32g, HG upgrade kit (Radxa adapter board+NVMe extention). System igame was the RadxaOS (debian12 based) that Rex modified and shared. The system booted normally without aio v2. With aio v2 installed, power was on as indicated by green light on clockwork mainboard. The blue led on Radxa CM5 was constantly on at lower brightness, similar to such state when aio v1 was installed.
btw this week will try to fix this with GPT - not wanting to reimage and and start again
even on the command line i get audio with the RTL and FM frequencies commands, but no sound if using SDR ++ bronw, SDR angel and others - so not working with the GUI , not the audio sink , still set as Linux whatever it was
Will post a huge thread soon on what i have been using it though - its great even with the 4 GB model which limits me to only use tiny LLM’s for testing - like using tinny lama to explain captured RF signals in real time as educational test for kids/ people interested in radio - can be applied for the Wi-Fi and Lora stuff later down the line if using the command line . Simple bash script interracting with tiny lama or some other tiny LLM
Too bad RAM and other stuff is way expensive due to AI shortage shit and all the wars/Covid/Scalpers in the last 5 years Anyways ,sometimes the limitation get the best of your imagination
How did you fix the chanel? I want to be on 0 also.
The V2 wouldn’t have the U-Boot issue like the V1. But the orientation of the early version ribbon cable matters. Can you post a photo of the setup?
Looks good but dont leave that antenna connector floating around !!, risking a short.
I do notice differences of the ribbon cable I got compared to the photo on HG website indicating proper installation. The pin next to the 5v pin on the aio v2 side got a through holeconnected to the trace backside, instead of the third pin on the HG website. Also, is it recommended to attemp to power on with aio v2 installed but without ribbon cable connected?
I tried the old way when I was tinkering with aio v1 on Radxa CM5 described inTinckering with RTL-SDR AIO board V1 on uconsole with Radxa CM5, by taping the pin NO. 26&28, corresponding to UART2 TX/RX, the system booted normally. And according to my previous attempts with a version of u-boot that unabled u-boot console interruption in Tinckering with RTL-SDR AIO board V1 on uconsole with Radxa CM5, the problem may not just lie in the state of power of devices attached to UART2. I don’t know if there are testing contact points to see if there are unexpexted high levels on UART2 (espetially RX).
