Node radio (cm108) "dead" after running apt update apt upgrade and reboot

App_rpt-users
1

I have a CM108 (SHARI) node that was working perfectly but had not been updated in about 2-months.
I did a quick backup then ran the update commands.
After reboot the radio/CM108 is unresponsive/not working with Asterisk.
I am in the initial stages of discovering this problem so I do not have a lot of information yet.
The upgrades appeared to run without any errors or problems.
But now the radio interface seems to be just not responding.

If I run the node tuning menu and command it to transmit (F) I get:
" SimpleUSB tuning CLI did not launch. Try restarting Asterisk."
Of course restoarting asterisk or rebooting does not change anything with this.
Looking at dmesg: the module appears to detect and load properly:
0.925714] usb 1-1: Manufacturer: C-Media Electronics Inc.
[ 0.945838] input: C-Media Electronics Inc. USB Audio Device as /devices/platform/axi/1000120000.pcie/1f00200000.usb/xhci-hcd.0/usb1/1-1/1-1:1.3/0003:0D8C:0012.0001/input/input0
[ 1.001094] hid-generic 0003:0D8C:0012.0001: input,hidraw0: USB HID v1.00 Device [C-Media Electronics Inc. USB Audio Device] on usb-xhci-hcd.0-1/input3

I've also tried commenting out:
And instances of devstr and rebooting, which is usally the "magic" for me to resolve issues like this.
No Success.

;;;;; ASL3 Tune settings ;;;;;
;devstr = 1-2:1.0
rxmixerset = 750
txmixaset = 800
txmixbset = 0
;devstr = 1-1:1.0

uname -a
Linux Pi5 6.12.25+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/Linux

Any attempt to make the node transmit from the asterisk cli just comes back blank with full verbosity turned on:
Pi5CLI> core set verbose 8
Console verbose is still 8.
Pi5CLI> rpt fun 27298 70
Pi5CLI>

2

When I try to use the "F" command in the tuning menu and get the mentioned error: Asterisk coredumps.
May 03 17:48:16 Pi5 systemd[1]: asterisk.service: Main process exited, code=dumped, status=11/SEGV
May 03 17:48:16 Pi5 systemd[1]: asterisk.service: Failed with result 'core-dump'.
May 03 17:48:21 Pi5 systemd[1]: asterisk.service: Scheduled restart job, restart counter is at 1.
May 03 17:48:21 Pi5 systemd[1]: Stopped asterisk.service - Asterisk PBX.
May 03 17:48:21 Pi5 systemd[1]: Starting asterisk.service - Asterisk PBX...
May 03 17:48:21 Pi5 systemd[1]: Started asterisk.service - Asterisk PBX.

3

If I try any commands in the Asterisk CLI that would normally cause the transmitter to key, I do not get a coredump.
But I get no activity or feedback of any kind.
It just does "nothing".

Pi5*CLI> rpt fun 272981 *70
Pi5*CLI> rpt fun 272981 *70
Pi5*CLI> rpt fun 272981 *3622140
Pi5*CLI>
4

I'm pretty stuck here and not sure what to try next.

5

Here's something to try :

cd
wget https://raw.githubusercontent.com/AllStarLink/ASL3/refs/heads/develop/bin/asl-check-install
chmod 755 asl-check-install
sudo ./asl-check-install

This will download and install a new command/script that we plan to include with the "next" set of release packages. The script "checks" a few things and can provide some remediation.

6

So far so good...
II Checking Kernel and DAHDI status

EE Missing one or more DAHDI modules in the running kernel...

8

Did you get the Do you want to try to fix the issue? (y/N) prompt ?

Did you answer "y" ?

9

p.s. if you are pasting text type information into your Community posts I would like to suggest that you first start with 3 back tick characters, then the text, and then another 3 back ticks. That will greatly improve the formatting and readability of the text that you are sharing.

```
text message line 1
text message line 2
...
the last line
```

10

I just got back,
It's late!
I accidentally deleted the original post :frowning:
But have this in the buffer still:


[2025-05-03 17:41:59.275] Asterisk 22.2.0+asl3-3.4.5-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2025-04-30 14:30:28 UTC
[2025-05-03 17:41:59.643] ERROR[960] loader.c: res_timing_dahdi declined to load.
[2025-05-03 17:41:59.763] ERROR[1033][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2025-05-03 17:41:59.763] ERROR[1033] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2025-05-03 17:45:52.162] Asterisk 22.2.0+asl3-3.4.5-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2025-04-30 14:30:28 UTC
[2025-05-03 17:45:52.353] ERROR[1545] loader.c: res_timing_dahdi declined to load.
[2025-05-03 17:45:52.489] ERROR[1593][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2025-05-03 17:45:52.489] ERROR[1593] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2025-05-03 17:48:15.404] ERROR[1689] channel.c: FRACK!, Failed assertion user_data is NULL (0)
[2025-05-03 17:48:15.404] ERROR[1689] : Got 10 backtrace records
[2025-05-03 17:48:21.510] Asterisk 22.2.0+asl3-3.4.5-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2025-04-30 14:30:28 UTC
[2025-05-03 17:48:21.710] ERROR[1693] loader.c: res_timing_dahdi declined to load.
[2025-05-03 17:48:21.838] ERROR[1739][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2025-05-03 17:48:21.838] ERROR[1739] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2025-05-03 18:04:57.155] Asterisk 22.2.0+asl3-3.4.5-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2025-04-30 14:30:28 UTC
[2025-05-03 18:04:57.346] ERROR[2064] loader.c: res_timing_dahdi declined to load.
[2025-05-03 18:04:57.483] ERROR[2125][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2025-05-03 18:04:57.483] ERROR[2125] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2025-05-03 18:04:57.531] ERROR[2126] chan_simpleusb.c: Channel 272981: Device string 1-1:1.3 was not found.
[2025-05-03 18:08:00.755] Asterisk 22.2.0+asl3-3.4.5-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2025-04-30 14:30:28 UTC
[2025-05-03 18:08:00.954] ERROR[2304] loader.c: res_timing_dahdi declined to load.
[2025-05-03 18:08:01.083] ERROR[2352][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2025-05-03 18:08:01.083] ERROR[2352] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2025-05-03 18:08:10.687] ERROR[2393] channel.c: FRACK!, Failed assertion user_data is NULL (0)
[2025-05-03 18:08:10.687] ERROR[2393] : Got 10 backtrace records
[2025-05-03 18:08:16.888] Asterisk 22.2.0+asl3-3.4.5-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2025-04-30 14:30:28 UTC
[2025-05-03 18:08:17.114] ERROR[2397] loader.c: res_timing_dahdi declined to load.
[2025-05-03 18:08:17.253] ERROR[2443][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2025-05-03 18:08:17.253] ERROR[2443] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2025-05-03 18:09:25.295] Asterisk 22.2.0+asl3-3.4.5-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2025-04-30 14:30:28 UTC
[2025-05-03 18:09:30.616] ERROR[2557] loader.c: res_timing_dahdi declined to load.
[2025-05-03 18:09:30.627] ERROR[2605][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2025-05-03 18:09:30.627] ERROR[2605] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2025-05-03 18:10:18.425] Asterisk 22.2.0+asl3-3.4.5-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2025-04-30 14:30:28 UTC
[2025-05-03 18:10:18.667] ERROR[2765] loader.c: res_timing_dahdi declined to load.
[2025-05-03 18:10:18.754] ERROR[2813][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2025-05-03 18:10:18.754] ERROR[2813] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2025-05-03 18:10:48.011] ERROR[2854] channel.c: FRACK!, Failed assertion user_data is NULL (0)
[2025-05-03 18:10:48.012] ERROR[2854] : Got 10 backtrace records
[2025-05-03 18:10:54.028] Asterisk 22.2.0+asl3-3.4.5-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2025-04-30 14:30:28 UTC
[2025-05-03 18:10:54.270] ERROR[2898] loader.c: res_timing_dahdi declined to load.
[2025-05-03 18:10:54.355] ERROR[2944][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2025-05-03 18:10:54.356] ERROR[2944] app_rpt/rpt_bridging.c: Failed to request pseudo channel


NN   The above can be pasted into a forum post or a GitHub issue

root@Pi5:~#

Sorry.

11

Yes I did, and that was the result.

12

The DAHDI module isn’t loaded with the kernel. Please paste the output of the following commands separately:

modprobe dahdi
dpkg -l linux-image*
dpkg -l linux-header*
13 
root@Pi5:/home/steve# modprobe dahdi
root@Pi5:/home/steve#

(nothing)

# modprobe dahdi
root@Pi5:/home/steve# dpkg -l linux-image*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                      Version          Architecture Description
+++-=========================================-================-============-=====================================>
ii  linux-image-6.12.25+rpt-rpi-2712          1:6.12.25-1+rpt1 arm64        Linux 6.12 for Raspberry Pi 2712, Ras>
un  linux-image-6.12.25+rpt-rpi-2712-unsigned <none>           <none>       (no description available)
ii  linux-image-6.12.25+rpt-rpi-v8            1:6.12.25-1+rpt1 arm64        Linux 6.12 for Raspberry Pi v8, Raspb>
un  linux-image-6.12.25+rpt-rpi-v8-unsigned   <none>           <none>       (no description available)
ii  linux-image-6.6.62+rpt-rpi-2712           1:6.6.62-1+rpt1  arm64        Linux 6.6 for Raspberry Pi 2712, Rasp>
un  linux-image-6.6.62+rpt-rpi-2712-unsigned  <none>           <none>       (no description available)
ii  linux-image-6.6.62+rpt-rpi-v8             1:6.6.62-1+rpt1  arm64        Linux 6.6 for Raspberry Pi v8, Raspbe>
un  linux-image-6.6.62+rpt-rpi-v8-unsigned    <none>           <none>       (no description available)
ii  linux-image-6.6.74+rpt-rpi-2712           1:6.6.74-1+rpt1  arm64        Linux 6.6 for Raspberry Pi 2712, Rasp>
un  linux-image-6.6.74+rpt-rpi-2712-unsigned  <none>           <none>       (no description available)
ii  linux-image-6.6.74+rpt-rpi-v8             1:6.6.74-1+rpt1  arm64        Linux 6.6 for Raspberry Pi v8, Raspbe>
un  linux-image-6.6.74+rpt-rpi-v8-unsigned    <none>           <none>       (no description available)
ii  linux-image-rpi-2712                      1:6.12.25-1+rpt1 arm64        Linux for Raspberry Pi 2712 (meta-pac>
ii  linux-image-rpi-v8                        1:6.12.25-1+rpt1 arm64        Linux for Raspberry Pi v8 (meta-packa>
lines 1-19/19 (END)

# dpkg -l linux-header*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                 Version          Architecture Description
+++-====================================-================-============-==========================================>
un  linux-headers                        <none>           <none>       (no description available)
ii  linux-headers-6.1.0-30-arm64         6.1.124-1        arm64        Header files for Linux 6.1.0-30-arm64
ii  linux-headers-6.1.0-30-common        6.1.124-1        all          Common header files for Linux 6.1.0-30
ii  linux-headers-6.1.0-31-arm64         6.1.128-1        arm64        Header files for Linux 6.1.0-31-arm64
ii  linux-headers-6.1.0-31-common        6.1.128-1        all          Common header files for Linux 6.1.0-31
ii  linux-headers-6.1.0-34-arm64         6.1.135-1        arm64        Header files for Linux 6.1.0-34-arm64
ii  linux-headers-6.1.0-34-common        6.1.135-1        all          Common header files for Linux 6.1.0-34
ii  linux-headers-6.12.25+rpt-common-rpi 1:6.12.25-1+rpt1 all          Common header files for Linux 6.12.25+rpt->
ii  linux-headers-6.12.25+rpt-rpi-2712   1:6.12.25-1+rpt1 arm64        Header files for Linux 6.12.25+rpt-rpi-2712
ii  linux-headers-6.12.25+rpt-rpi-v8     1:6.12.25-1+rpt1 arm64        Header files for Linux 6.12.25+rpt-rpi-v8
ii  linux-headers-6.6.62+rpt-common-rpi  1:6.6.62-1+rpt1  all          Common header files for Linux 6.6.62+rpt-r>
ii  linux-headers-6.6.62+rpt-rpi-2712    1:6.6.62-1+rpt1  arm64        Header files for Linux 6.6.62+rpt-rpi-2712
ii  linux-headers-6.6.62+rpt-rpi-v8      1:6.6.62-1+rpt1  arm64        Header files for Linux 6.6.62+rpt-rpi-v8
ii  linux-headers-6.6.74+rpt-common-rpi  1:6.6.74-1+rpt1  all          Common header files for Linux 6.6.74+rpt-r>
ii  linux-headers-6.6.74+rpt-rpi-2712    1:6.6.74-1+rpt1  arm64        Header files for Linux 6.6.74+rpt-rpi-2712
ii  linux-headers-6.6.74+rpt-rpi-v8      1:6.6.74-1+rpt1  arm64        Header files for Linux 6.6.74+rpt-rpi-v8
un  linux-headers-686-pae                <none>           <none>       (no description available)
un  linux-headers-amd64                  <none>           <none>       (no description available)
ii  linux-headers-arm64                  6.1.135-1        arm64        Header files for Linux arm64 configuration>
un  linux-headers-generic                <none>           <none>       (no description available)
ii  linux-headers-rpi-2712               1:6.12.25-1+rpt1 arm64        Header files for Linux rpi-2712 configurat>
ii  linux-headers-rpi-v8                 1:6.12.25-1+rpt1 arm64        Header files for Linux rpi-v8 configuratio>
lines 1-27/27 (END)
14

What about lsmod | grep -i dah?

15

Got back today and powered it up and it is now Magically working.
No further changes or update etc. were attempted since my last post.
No idea what may have changed or why it's working now.
And I certainly had tried multiple reboots earlier (after running the fix attempt script) so it was not a simple reboot that fixed anything.
Will keep an eye on it and try the updates over again (last time I tried yesterday) it said everything was up to date and there was nothing to be done. This was also prior to trying the suggested fix script.
I was not expecting it to suddenly start working like it just did for seemingly no reason.
Further reboots are not breaking it.
Just weird.
Very weird.
This morning it was very much in the 'broken state' reported with reboots not changing anything.
Powered it up this evening and it functionally fixed itself.
It the broken state it was going to be a clean install and restore from backup which probably would have worked , but I was avoiding that to try and figure out what actually happened on the update.

16

I suspect the manual modprobe dahdi may have done something.
But does not explain why it works after reboots now..
I need to double confirm that is true.
Because it might just be only in my mind. LOL

17

Yep working fine after reboots and full power downs.

18

It's working now (for no reason I could figure out).
But-

e# lsmod | grep -i dah
dahdi_dummy            49152  0
dahdi_transcode        49152  0
dahdi                 262144  18 dahdi_dummy,dahdi_transcode
crc_ccitt              49152  1 dahdi
19

Also checked update status and nothing to be updated:
If there was- I could try the whole thing over again and try to break it.

Fetched 779 kB in 1s (746 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
20

That error is clearly because the dahdi modules weren't loaded. Not sure why you had a hiccup but it looks good now.

21

Yeah- strange as heck.