I’m in charge of setting up repeater linking for 3 sites on a private network. I bought 5 Dell wyse 3040 mini PCs and have 2 RIM-lite, another on the way. The idea is to make one node Internet accessable as a hub, then the 3 repeaters each get a wyse and a rim. They can be linked to each other or via the hub. The hub would allow Internet access in, then link to the other sites as needed.
I got Debian 12 loaded on all 5 pcs no problem. I got asl3 installed with no errors. I have the hub setup with no radio, registered, port forwarded, can link to other Internet nodes. I setup pjsip and can connect with a few phones. Allmon3 connecting perfect. Great start, very excited!
The next one has a rim attached (but no radio). Got it configured, and setup the private node. Can link to the hub no problem. I can verify the PTT led comes on when it should. Perfect so far, just duplicate this twice more!
Third one doesn’t have a rim attached, but should still be ok I assume. Got it configured, but asterisk won’t start up properly. Log shows failure to load dahdi. I’ve tried a changing it to a pseudo radio, like the hub, but it still fails to load.
So thinking maybe it’s just that hardware I tried again on a 4th PC with the same results.
This is my first excursion into ASL and asterisk and didn’t know what to do next. What suggestions do you ask have to troubleshoot?
Lack of a dahdi module means your install was not completed successfully. Look for errors from the dahdi-dkms modules. Most likely culprit is you’re missing kernel headers.
Others have had issues on the 3040’s with Secure Boot enabled.
Spot on! I must have missed a check box when installing Debian. Simply running:
$ sudo apt install linux-headers-$(uname -r)
a reboot, and the two nodes came right up.
Just a few things…
does not hurt to check that dahdi is loading (not commented out) in modules.conf
see if it exists
/usr/lib/x86_64-linux-gnu/asterisk/modules
But a recompile of dahdi is an option.
I will say those 3040’s have shown to be a bit buggy at times with it’s bios.
You might update that and try again. Perhaps you have.
Just some thoughts in paths you might try.