Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#2319 - usbmode bug which is fixed in usb-modeswitch... #8392

openwrt-bot opened this issue Jun 14, 2019 · 0 comments

FS#2319 - usbmode bug which is fixed in usb-modeswitch... #8392

openwrt-bot opened this issue Jun 14, 2019 · 0 comments


Copy link

@openwrt-bot openwrt-bot commented Jun 14, 2019


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 ) 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:

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
# 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

A non-working example (after reboot):

root@OpenWrt:# echo 3 > /sys/bus/usb/devices/1-2/bConfigurationValue
# umbim -d /dev/cdc-wdm0 caps
ERROR: mbim message timeout

At least one other person in OpenWRT bug tracker confirms this:

Although he has another problem with looping messages (probably unrelated to this bug)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant