usbmode bug which is fixed in usb-modeswitch...
Username: Evren Yurtesen
Origin: https://bugs.openwrt.org/index.php?do=details&task_id=2319
I wrote a bug report but then the bug report said wrong token and I lost the report... :(
Now again but shorter version. The usb-modeswitch (which seems to be an openwrt project, a rewrite of original usb_modeswitch
https://git.openwrt.org/project/usbmode.git
) needs to set some devices to config 0 before switching to config 3.
BTW
this is fixed in usb-modeswitch... Here is the link to discussion about this:
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2710&start=22
Some devices need to be set to config 0 first to be able to switch to config 3. Otherwise they hang...
Here a working example:
root@OpenWrt:~# echo 0 > /sys/bus/usb/devices/1-2/bConfigurationValue
root@OpenWrt:~# echo 3 > /sys/bus/usb/devices/1-2/bConfigurationValue
root@OpenWrt:~# umbim -d /dev/cdc-wdm0 caps
devicetype: 0001 - embedded cellularclass: 0001 voiceclass: 0001 - no-voice simclass: 0002 dataclass: 8000003F smscaps: 0003 controlcaps: 0001 maxsessions: 0003 deviceid: 867377023108313 firmwareinfo: 11.617.06.00.00 hardwareinfo: RM1ME909ASM
root@OpenWrt:~#
A non-working example (after reboot):
root@OpenWrt:~# echo 3 > /sys/bus/usb/devices/1-2/bConfigurationValue
root@OpenWrt:~# umbim -d /dev/cdc-wdm0 caps
ERROR: mbim message timeout
root@OpenWrt:~#
At least one other person in OpenWRT bug tracker confirms this:
https://bugs.openwrt.org/index.php?do=details&task_id=1424
Although he has another problem with looping messages (probably unrelated to this bug)
https://forum.openwrt.org/t/usbmode-sits-in-loop-after-install/12624