Usb_modeswitch stopped autoswitching for new Resin OS versions

raspberrypi3
network

#1

We are running a few devices with GSM-Sticks to connect to the internet, but on new installations of the resin.os the usb_modeswitch is not automated anymore. Was there a recent development we missed or did this stop working for an unknown reason.
The OS used are: Resin OS 2.15.1+rev1 (production) where automated usb_modeswitch doesnt work anymore
The OS used where it works is: Resin OS 2.13.6+rev1 (production) where automated usb_modeswitch works

The Usb Devices to be switched are Huawei GSM-Sticks (E3533, E303, MS2372h, MS2131i)

Was this an inteded change or an accidental one?


#4

Automated switch for Huawei E3531 still works.

Just for further clarification some Hardware IDs:

E3533
before switch
Bus 001 Device 007: ID 12d1:157d Huawei Technologies Co., Ltd.
after switch
Bus 001 Device 008: ID 12d1:14db Huawei Technologies Co., Ltd. E353/E3131
switch command
sudo usb_modeswitch -v 0x12d1 -p 0x157d -J

E3531
before switch
Bus 001 Device 009: ID 12d1:1f01 Huawei Technologies Co., Ltd. E353/E3131 (Mass storage mode)
after switch
Bus 001 Device 010: ID 12d1:14dc Huawei Technologies Co., Ltd.
switch command
sudo usb_modeswitch -v 0x12d1 -p 0x1f01 -J


#5

Hi there @thinktank

Between v2.13.6+rev1 and v2.15.1+rev1, usb_modeswitch was upgraded to v2.5.0 from v2.2.5, which I believe is causing the issue you are seeing. I do not know of any other changes between those OS version sets regarding usb_modeswitch. At first pass, reading the changelog for usb_modeswitch I do not see any smoking guns between those two versions that would explain what you are seeing, but I have asked some colleagues who know more about this subsystem than myself.

Thank you!


#9

Hi,
as part of each release we are testing MS2372h, MS2131i and they switch as intended.
What device type are you running on?


#13

Hi @Ichus,


#14

Hi @Ichus,

can you let us know what device type are you running on?

Thanks!

P.S. Sorry for the previous message / mention, I just changed keyboard shortcuts and the message was sent by accident.


#16

Hi @zrzka

We are running the newest RaspberryPi boards with sleepypi’s


#17

Hi @Ichus,

For clarity, you mean the Raspberry Pi 3 and the Sleepy Pi 2, correct?

Thank you so much for getting back to us!


#18

hey @xginn8,
correct


#19

Hi @Ichus,

Could you please retest on the latest available OS and get back to us?

There have been quite a few changes since you first reported. It would be good to have your results on the latest OS.


#21

I will get around to setup a new testing device soon.
Thanks for your help


#22

Hello ! Any news on the testing front ? Thanks !


#24

Hi @Ichus any news on the testing? did the new OS release fix your issue?


#26

Hi @curcuz @cyplo,
I have not tested the new OS, I broke my setup to an annoying point, but will hopefully get to reset this next week.
But I’ll take a look at the new OS soon!


#27

Thanks ! let us know how it goes :slight_smile:


#28

Here the ‘first glance’ overview:
Tested Sticks sofar are Huawei E3533, Huawei E303 Huawei MS2372h
The MS2372h is working like it used to,
The E303 is not switched, but this can be faulty hardware (the stick might be broken anyway)
The E3533 is now switched into debug mode, which runs in serial mode (like the MS2372h), but did not get a connection out of it yet ( have not spend time or energy trying yet though )

When I take a deeper look into it, I’ll provide more data for the tests


#30

Heya !
I was wondering if you had a chance to do any further tests @Ichus ? :slight_smile:


#32

sadly not yet, other tasks are more urgent