Please note that in the ChirpStack v4 documentation we have updated the Multitech documentation. In the past AEP version there was a lot of magic symlinking happening to make the USB vs SPI MTAC module work (the USB version has been deprecated quite some time ago).
Thank you brocaar! So it sounds like with the newer MultiTech gateway/conduits, we can’t even use an older mlinux firmware to get around this issue.
“newer Multitech gateway/conduits” is relative To know which Multitech gateway / conduit works with with mLinux version, it is better to ask this to Multitech directly.
I think there are two things that you could do:
Debug issue on mLinux
What you could do is check the logs. There might be helpful info in /var/log/messages.
As well you could try:
To see if that prints any helpful information. That is basically what the /etc/init.d/lora-packet-forwarder-ap1 start would do to start the packet-forwarder.
Migrate to mPower
This is recommended by Multitech and this is now covered in the new ChirpStack documentation. In my case, I migrated my Conduit from mLinux to mPower by downloading the mPower firmware image and updating it using the same steps to migrate to or upgrade your mLinux firmware.