Re: Problems with Sierra LTE MC7710 Device

[Bjørn Mork <bjorn mork no>]

Harald Jung <support ecos de> wrote:

>Hi,
>
>Am 17.01.2013 19:02, schrieb Bjørn Mork:
>> echo 1 >/sys/bus/usb/devices/1-1.5/bConfigurationValue 
>
>ha! that did the job.
>
>Jan 17 23:11:32 ThinClient klogd: usbcore: registered new interface 
>driver usbserial
>Jan 17 23:11:32 ThinClient klogd: usbcore: registered new interface 
>driver usbserial_generic
>Jan 17 23:11:32 ThinClient klogd: USB Serial support registered for
>generic
>Jan 17 23:11:32 ThinClient klogd: usbserial: USB Serial Driver core
>Jan 17 23:11:32 ThinClient klogd: usbcore: registered new interface 
>driver cdc_wdm
>Jan 17 23:11:32 ThinClient klogd: usbcore: registered new interface 
>driver qcserial
>Jan 17 23:11:32 ThinClient klogd: USB Serial support registered for 
>Qualcomm USB modem
>Jan 17 23:11:32 ThinClient klogd: qcserial 1-1.5:1.0: Qualcomm USB
>modem 
>converter detected
>Jan 17 23:11:32 ThinClient klogd: usb 1-1.5: Qualcomm USB modem 
>converter now attached to ttyUSB0
>Jan 17 23:11:32 ThinClient klogd: qcserial 1-1.5:1.2: Qualcomm USB
>modem 
>converter detected
>Jan 17 23:11:32 ThinClient klogd: usb 1-1.5: Qualcomm USB modem 
>converter now attached to ttyUSB1
>Jan 17 23:11:32 ThinClient klogd: qcserial 1-1.5:1.3: Qualcomm USB
>modem 
>converter detected
>Jan 17 23:11:32 ThinClient klogd: usb 1-1.5: Qualcomm USB modem 
>converter now attached to ttyUSB2
>Jan 17 23:11:32 ThinClient klogd: qmi_wwan 1-1.5:1.8: cdc-wdm0: USB WDM
>
>device
>Jan 17 23:11:32 ThinClient klogd: qmi_wwan 1-1.5:1.8: wwan0: register 
>'qmi_wwan' at usb-0000:00:1a.0-1.5, WWAN/QMI device, 6e:1c:71:79:b3:45
>Jan 17 23:11:32 ThinClient klogd: usbcore: registered new interface 
>driver qmi_wwan
>.
>blah
>.
>Jan 17 23:12:49 ThinClient pppd[3878]: Plugin 
>/usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.
>Jan 17 23:12:49 ThinClient pppd[3878]: pppd 2.4.5 started by root, uid
>0
>Jan 17 23:12:49 ThinClient pppd[3878]: Using interface ppp0
>Jan 17 23:12:49 ThinClient pppd[3878]: Connect: ppp0 <--> /dev/ttyUSB2
>Jan 17 23:12:49 ThinClient NetworkManager[2146]: <warn> 
>/sys/devices/virtual/net/ppp0: couldn't determine device driver;
>ignoring...
>Jan 17 23:12:49 ThinClient pppd[3878]: CHAP authentication succeeded
>Jan 17 23:12:49 ThinClient pppd[3878]: CHAP authentication succeeded
>Jan 17 23:12:56 ThinClient pppd[3878]: Could not determine remote IP 
>address: defaulting to 10.64.64.64
>Jan 17 23:12:56 ThinClient pppd[3878]: local  IP address 88.128.183.22
>Jan 17 23:12:56 ThinClient pppd[3878]: remote IP address 10.64.64.64
>Jan 17 23:12:56 ThinClient pppd[3878]: primary   DNS address
>10.74.210.210
>Jan 17 23:12:56 ThinClient pppd[3878]: secondary DNS address
>10.74.210.211
>
>
>Harald

Great!

Do you happen to know why the device was using configuration #2 by default? That's unexpected. Recent versions of usb_modeswitch will do that if it sessions a MBIM configuration, but only if you have the cdc_mbim driver. So I don't think that can explain this.



Bjørn