DMK Engineering URI stops working after Software update

AllStarLink
,
1

I’m trying to figure out why my node stopped working after I did a software update. I am using a Raspberry Pi 5 with an SSD drive. The URI is a DMK Engineering with a green light and no heartbeat. I checked, and the Pi does see URI. I connected the URI to a different node, and it works fine. Is this a configuration issue or a driver issue?

Here are the packages that were updated on 11/03/25.

  • allmon3

  • autoconf

  • automake

  • autopoint

  • autotools-dev

  • bluez-firmware

  • dahdi-dkms

  • dahdi-linux

  • dahdi-source

  • debhelper

  • dh-autoreconf

  • dh-strip-nondeterminism

  • dwz

  • firmware-atheros

  • firmware-brcm80211

  • firmware-intel-graphics

  • firmware-intel-misc

  • firmware-libertas

  • firmware-marvell-prestera

  • firmware-mediatek

  • firmware-misc-nonfree

  • firmware-nvidia-graphics

  • firmware-realtek

  • gettext

  • intltool-debian

  • libarchive-cpio-perl

  • libarchive-zip-perl

  • libc-bin

  • libc-dev-bin

  • libc-devtools

  • libc-l10n

  • libc6

  • libc6-dbg

  • libc6-dev

  • libdebhelper-perl

  • libdtovl0

  • libfile-stripnondeterminism-perl

  • libgpiolib0

  • libltdl-dev

  • libmail-sendmail-perl

  • libssl3

  • libsub-override-perl

  • libsys-hostname-long-perl

  • libtool

  • linux-headers-6.12.47+rpt-common-rpi

  • linux-headers-6.12.47+rpt-rpi-2712

  • linux-headers-6.12.47+rpt-rpi-v8

  • linux-headers-rpi-2712

  • linux-headers-rpi-v8

  • linux-image-6.12.47+rpt-rpi-2712

  • linux-image-6.12.47+rpt-rpi-v8

  • linux-image-rpi-2712

  • linux-image-rpi-v8

  • linux-kbuild-6.12.47+rpt

  • linux-libc-dev

  • locales

  • m4

  • openssl

  • po-debconf

  • raspberrypi-sys-mods

  • raspi-firmware

  • raspi-utils

  • raspi-utils-core

  • raspi-utils-dt

  • raspi-utils-eeprom

  • raspi-utils-otp

  • raspinfo

  • rpi-eeprom

Nov 3, 2025, 11:04 PM 8 packages
undefined ----

  • bind9-dnsutils

  • bind9-host

  • bind9-libs

  • libtiff6

  • libxslt1.1

  • linux-headers-6.1.0-40-arm64

  • linux-headers-6.1.0-40-common

  • linux-headers-arm64

Dave KA9WXN

2

I have found a resolution! For some reason, when the system finished its reboot after the update, it changed the URI port assignment in the system configuration.

The fix was straightforward:

Find the new URI device path: Run the command:

Bash

ls -l /dev/usb/
This displayed the URI device and port information, showing the new path.

Update the Allstarlink configuration: Edit the /etc/asterisk/simpleusb.conf file to reflect the correct device path for the node. (e.g., changing device = /dev/usb/hiddev0 to the new path found in step 1.)

Restart Asterisk: Apply the changes by restarting the Asterisk service:

Bash

sudo systemctl restart asterisk
After these steps, the URI's heartbeat resumed, and the node is working again! Hope this helps anyone else encountering similar issues after a major kernel or firmware update on a Raspberry Pi running Allstarlink.

2 Likes