Hi,
I’ve read a post here on getting the gl-mifi modem to recover after bad signal. However the post is a little old now and don’t describe exactly my situation, and it doesn’t resolve my issue.
I am running LEDE firmware version 2.271.
My device is gl-mifi with ec-25 modem.
When I boot up my device, the modem uses ttyUSB0, ttyUSB1, ttyUSB2 and ttyUSB3. These is the desired state. There are several scripts etc that depend on the ttyUSB3 allocation in particular.
After the device experiences a loss of 3G/4G signal I guess some script (from gl-inet?) attempts to recover the modem with a reset or something? Firstly, could somebody tell me where this script lives please?
After a while of intermittent signal loss, something causes the modem to start using ttyUSB4 instead of ttyUSB3. Unfortunately my dmesg log has wrapped around, but I can try to reproduce later and get the exact sequence when this happened. But in essence it is “GSM modem (1-port) converter now disconnected from ttyUSB3” then “GSM modem (1-port) converter now attached to ttyUSB4”. So this will have happened following a modem reset triggered by the ‘modem reset script’ I’m guessing.
I have tried
echo 1 > /sys/class/leds/gl-mifi:3gcontrol/brightness
sleep 1
echo 0 > /sys/class/leds/gl-mifi:3gcontrol/brightness
But while this causes the USB connection to be torn down and re-connected, it always comes back again with ttyUSB4.
I also tried echo “usb1”> /sys/bus/usb/drivers/usb/unbind as a last resort, but this didn’t help and it also screwed up the other USB connections on bus1 (lsusb below):
Bus 001 Device 017: ID 2c7c:0125
Bus 001 Device 010: ID 05e3:0752 Genesys Logic, Inc.
Bus 001 Device 009: ID 05e3:0618 Genesys Logic, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So it seems like the kernel thinks that /dev/ttyUSB3 isn’t available for some reason. Perhaps something died in a bad way after one of the previous modem resets. Does anyone have any tips for troubleshooting this at kernel level? Is there any way to remedy this without completely rebooting the device? Or to stop it happening at all in the first place?
Many thanks,
Robin