Automatic Activation, Hotplug and UDEV, Configuration
Post Reply
usonic
Posts: 3
Joined: Sat Oct 17, 2015 10:06 pm

ZTE 631 issue

Post by usonic » Sat Oct 17, 2015 11:15 pm

Hello,

Having very specific problem with this device which has ID 19d2:2000, maybe someone could help to figure it out:
Once modem is plugged it, all works fine. It appears as 19d2:2000, then it is switched to 19d2:0117 which is properly working modem mode.
However, after random amount of uptime, usally few days, syslog prints following:

Code: Select all

Sep 24 18:00:30 raspberrypi kernel: [68443.692980] option1 ttyUSB2: option_instat_callback: error -71
Sep 24 18:00:30 raspberrypi kernel: [68443.698955] option1 ttyUSB2: option_instat_callback: error -71
Sep 24 18:00:30 raspberrypi kernel: [68443.704977] option1 ttyUSB2: option_instat_callback: error -71
Sep 24 18:00:30 raspberrypi kernel: [68443.708641] usb 1-1.5: USB disconnect, device number 6
Sep 24 18:00:30 raspberrypi kernel: [68443.708704] option1 ttyUSB2: usb_wwan_indat_callback: resubmit read urb failed. (-19)
Sep 24 18:00:30 raspberrypi kernel: [68443.708911] option1 ttyUSB2: usb_wwan_indat_callback: resubmit read urb failed. (-19)
Sep 24 18:00:30 raspberrypi kernel: [68443.709087] option1 ttyUSB2: usb_wwan_indat_callback: resubmit read urb failed. (-19)
Sep 24 18:00:30 raspberrypi kernel: [68443.709245] option1 ttyUSB2: usb_wwan_indat_callback: resubmit read urb failed. (-19)
Sep 24 18:00:30 raspberrypi kernel: [68443.710971] option1 ttyUSB2: option_instat_callback: error -71
Sep 24 18:00:30 raspberrypi kernel: [68443.713369] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Sep 24 18:00:30 raspberrypi kernel: [68443.713522] option 1-1.5:1.0: device disconnected
Sep 24 18:00:30 raspberrypi kernel: [68443.714292] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Sep 24 18:00:30 raspberrypi kernel: [68443.714412] option 1-1.5:1.1: device disconnected
Sep 24 18:00:30 raspberrypi pppd[1852]: Modem hangup
Sep 24 18:00:30 raspberrypi pppd[1852]: Connect time 1140.6 minutes.
Sep 24 18:00:30 raspberrypi pppd[1852]: Sent 191163 bytes, received 179915 bytes.
Sep 24 18:00:30 raspberrypi kernel: [68443.721319] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Sep 24 18:00:30 raspberrypi kernel: [68443.721431] option 1-1.5:1.2: device disconnected
Sep 24 18:00:30 raspberrypi pppd[1852]: Connection terminated.
Sep 24 18:00:30 raspberrypi pppd[1852]: Exit.
Sep 24 18:00:31 raspberrypi ifplugd(ppp0)[1889]: Link beat lost.
Sep 24 18:00:31 raspberrypi ifplugd(ppp0)[1889]: Exiting.
Sep 24 18:00:31 raspberrypi kernel: [68444.453396] usb 1-1.5: new high-speed USB device number 7 using dwc_otg
Sep 24 18:00:31 raspberrypi kernel: [68444.555295] usb 1-1.5: New USB device found, idVendor=19d2, idProduct=0016
Sep 24 18:00:31 raspberrypi kernel: [68444.555339] usb 1-1.5: New USB device strings: Mfr=3, Product=2, SerialNumber=0
Sep 24 18:00:31 raspberrypi kernel: [68444.555359] usb 1-1.5: Product: ZTE WCDMA Technologies MSM
Sep 24 18:00:31 raspberrypi kernel: [68444.555377] usb 1-1.5: Manufacturer: ZTE, Incorporated
Sep 24 18:00:31 raspberrypi kernel: [68444.566387] option 1-1.5:1.0: GSM modem (1-port) converter detected
Sep 24 18:00:31 raspberrypi kernel: [68444.567128] usb 1-1.5: GSM modem (1-port) converter now attached to ttyUSB0

and after this, mode is switched to 19d2:0016 and it stays even after reboot. I have to unplug and plug modem again to return to 19d2:0117 mode. I would like to know if usb-modeswitch could somehow set modem back to 19d2:0117 mode after this crash. Basically I need a solution to return to 19d2:0117 without physically accessing machine.
It looks like situation is as described here:
Annother notorious candidate is again 19d2:2000. It may be switched O.K. by an existing rule, but there is no driver loading if your model is new and its ID is not yet added to the "option" module.
Disable the rule running "eject" and the ID will be handled by usb_modeswitch.
but I not clearly understand what should I do. Explanation of "Disable the rule running "eject" and the ID will be handled by usb_modeswitch" would really help.

Also, not sure if I understand configs properly, but maybe placing file 19d2:2000 or 19d2:0016 to /etc/usb_modeswitch.d with content like:

Code: Select all

TargetVendor=   0x19d2
TargetProductList="0117"

MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
MessageContent3="55534243123456702000000080000c85010101180101010101000000000000"

NeedResponse=1
would it help too?

Regards

Josh
Site Admin
Posts: 6534
Joined: Sat Nov 03, 2007 12:30 am

Re: ZTE 631 issue

Post by Josh » Sun Oct 18, 2015 9:35 am

There is no way to switch a 3G USB modem back to the initial mode. It's a one-way street.

The problem here is likely Pi's 'unique' USB architecture and Raspbian's botched USB driver. There is an improved kernel driver available somewhere; you should be able to track it down with Google's help.

usonic
Posts: 3
Joined: Sat Oct 17, 2015 10:06 pm

Re: ZTE 631 issue

Post by usonic » Sun Oct 18, 2015 7:49 pm

Thank you for suggestion, however, could you point me to exact direction? Am I looking for custom kernel, kernel module, GSM modem driver or something else? I just need right keyword for Google, because my recent searches were not success.

Josh
Site Admin
Posts: 6534
Joined: Sat Nov 03, 2007 12:30 am

Re: ZTE 631 issue

Post by Josh » Sun Oct 18, 2015 9:05 pm

If I remember correctly, the improved driver is named "dwc2".

Post Reply