OpenWrt/LEDE Project

Welcome to the OpenWrt/LEDE Project bug reporting and issue tracking system

Problems to be reported here are for the OpenWrt/LEDE Project targets, sources, toolchain, core packages, build procedures, distribution and infrastructure. Guidelines for submitting a good bug report can be found at the OpenWrt/LEDE Project website. Problems related to LuCI or OpenWrt packages need to be reported in their repositories:

Notifications of all submissions and task changes are sent to lede-bugs@infradead.org.

OpenedIDCategoryTask TypePrioritySeveritySummaryReported InStatus
14.06.20192319PackagesBug ReportVery LowHighusbmode bug which is fixed in usb-modeswitch...openwrt-18.06Unconfirmed Task Description

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

08.12.20181988Base systemFeature RequestVery LowLowusbmode doesn't support HuaweiAltMode from USB_ModeSwit...TrunkUnconfirmed Task Description

USB_ModeSwitch v2.5.1 added a new option called HuaweiAltMode that isn’t present in usbmode yet. It would be great if this could be ported to usbmode as well, please.

09.03.20181424Base systemBug ReportVery LowLowusbmode sits in loop after installTrunkUnconfirmed Task Description

- Name the tree/revision/version

OpenWrt Snapshot r6397-7cc9914

- Name the affected device

Huawei ME909s-120 LTE Card (12d1:15c1) on a PC Engines APU2 (amd64) in MBIM Mode.

- What does it do that it should not do / what does it not do that it should do

usbmode sits in a loop right after installation, doesn’t switch the Modem in MBMI mode and thus no /dev/cdc-wdm0 device is created and prints constantly:

[ 59.838090] usb 1-1.3: usbfs: process 6946 (usbmode) did not claim interface 1 before use
[ 60.048534] usb 1-1.3: usbfs: interface 1 claimed by usbfs while ‘usbmode’ sets config #0
[ 60.131996] usb 1-1.3: usbfs: process 7032 (usbmode) did not claim interface 1 before use
[ 60.342459] usb 1-1.3: usbfs: interface 1 claimed by usbfs while ‘usbmode’ sets config #0

- Steps to reproduce

Install usb-modeswitch on OpenWrt Snapshot r6397-7cc9914

- What you have already done to workaround/fix the problem

Tried LEDE 17.01.4 r3560-79f57e422d without success, but messages are only printed once after “usbmode -s” is called, also there isn’t a cdc-wdm0 device created.

- Any additional info you thinks is important

This HW config is working fine with cdc_mbim on Debian with a 4.9 Kernel and their usb-modeswitch implementation.

Showing tasks 1 - 3 of 3 Page 1 of 1

Available keyboard shortcuts

Tasklist

Task Details

Task Editing