<div dir="ltr">I am not sure what happened, but I tried recompiling my kernel and modules again and the USB id of the 340u changed, so the modules do not load now. My new USB id is 1199:0fff. I'm not sure how to solve this.<div> </div><div>With the wrong USB id, both the bConfigurationValue and bNumConfigurations are "1."</div><div> </div></div><div class="gmail_extra"> <div class="gmail_quote">On Sat, Apr 26, 2014 at 1:38 PM, David McCullough <<a href="mailto:david.mccullough@accelecon.com" target="_blank">david.mccullough@accelecon.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Noah Taber wrote the following: <div class="">> I finally had time to properly apply the patch. Nothing has changed. I > still get the following error: > > $ sudo qmi-network /dev/cdc-wdm0 start > Starting network with 'qmicli -d /dev/cdc-wdm0 --wds-start-network= > --client-no-release-cid'... > error: couldn't start network: QMI protocol error (26): 'NoEffect' > Saving state... (CID: 7) > error: network start failed, no packet data handle > Clearing state... </div>Try doing a "status" command first. $ sudo qmi-network /dev/cdc-wdm0 status A recent firmware update to a similar modem here was auto connecting and the "start" command would fail but the modem was ready to go. <div><div class="h5"> > If I run the following: > > $ sudo ifup wwan0 > Ignoring unknown interface wwan0=wwan0. > > Do you think the Ignoring unknown interface has something to do withit? > > More info: > > $ lsmod > Module Size Used by > sierra 8490 0 > qcserial 4385 0 > usb_wwan 6773 1 qcserial > qmi_wwan 9827 0 > cdc_wdm 10245 1 qmi_wwan > usbserial 27099 3 qcserial,sierra,usb_wwan > > [ 3.415013] usb 1-1.3: config 1 has an invalid interface number: 8 but > max is 4 > [ 3.436260] usb 1-1.3: config 1 has an invalid interface number: 9 but > max is 4 > [ 3.449764] usb 1-1.3: config 1 has no interface number 1 > [ 3.459493] usb 1-1.3: config 1 has no interface number 4 > [ 3.478681] usb 1-1.3: New USB device found, idVendor=1199, > idProduct=9051 > [ 3.498711] usb 1-1.3: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 3.516309] usb 1-1.3: Product: AirCard 340U > [ 3.526058] usb 1-1.3: Manufacturer: Sierra Wireless, Incorporated > [ 3.536509] usb 1-1.3: SerialNumber: 013323000120510 > [ 4.342039] udevd[155]: starting version 175 > [ 5.569643] usbcore: registered new interface driver usbserial > [ 5.609398] usbcore: registered new interface driver cdc_wdm > [ 5.714065] usbcore: registered new interface driver usbserial_generic > [ 5.777289] qmi_wwan 1-1.3:1.8: cdc-wdm0: USB WDM device > [ 5.810054] usbserial: USB Serial support registered for generic > [ 5.879582] qmi_wwan 1-1.3:1.8 wwan0: register 'qmi_wwan' at > usb-bcm2708_usb-1.3, WWAN/QMI device, c6:1d:98:b8:37:68 > [ 5.941888] usbcore: registered new interface driver qcserial > [ 6.206575] usbcore: registered new interface driver qmi_wwan > [ 6.243858] usbserial: USB Serial support registered for Qualcomm USB > modem > [ 6.476436] qcserial 1-1.3:1.0: Qualcomm USB modem converter detected > [ 6.571918] usbcore: registered new interface driver sierra > [ 6.776504] usb 1-1.3: Qualcomm USB modem converter now attached to > ttyUSB0 > [ 6.858175] usbserial: USB Serial support registered for Sierra USB modem > [ 7.006262] qcserial 1-1.3:1.2: Qualcomm USB modem converter detected > [ 7.114227] usb 1-1.3: Qualcomm USB modem converter now attached to > ttyUSB1 > [ 7.274019] sierra 1-1.3:1.3: Sierra USB modem converter detected > [ 7.362697] usb 1-1.3: Sierra USB modem converter now attached to ttyUSB2 > > Please let me know your thoughts. Thank you. </div></div>Perhaps try running a dhcp client by hand, I think something like this depending on the packages installed: dhclient wwan0 Also, what is the output of (you might need to change the 1-1 to 1-1.3): cat /sys/bus/usb/devices/1-1/bConfigurationValue and cat /sys/bus/usb/devices/1-1/bNumConfigurations Cheers, Davidm <div class="HOEnZb"><div class="h5"> > > > On Fri, Apr 25, 2014 at 6:42 AM, Noah Taber <<a href="mailto:noahtaber@gmail.com">noahtaber@gmail.com</a>> wrote: > > > I'm going to reply to all previous questions: > > > > Pertinent part of an ifconfig: > > > > wwan0 Link encap:Ethernet HWaddr 22:18:7d:6b:f6:14 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > > My APN is actually broadband. > > > > I'm compiling the patch as I type. Regarding the patch, I noticed that > > the qmi_wwan.c file was already fine. The sierra.c file was missing the > > information. > > > > Thank you everyone. I hope the patch does it for me. I will respond if > > works or if it does not work. > > > > > > On Fri, Apr 25, 2014 at 6:37 AM, Bjørn Mork <<a href="mailto:bjorn@mork.no">bjorn@mork.no</a>> wrote: > > > >> David McCullough <<a href="mailto:david.mccullough@accelecon.com">david.mccullough@accelecon.com</a>> writes: > >> > Aleksander Morgado wrote the following: > >> >> On Fri, Apr 25, 2014 at 1:44 PM, David McCullough > >> >> <<a href="mailto:david.mccullough@accelecon.com">david.mccullough@accelecon.com</a>> wrote: > >> >> > > >> >> > 2. Apply this patch to your kernel if it is not already applied to > >> get all > >> >> > the interfaces for use with the modem in QMI mode. This patch is > >> against > >> >> > linux-3.10 > >> >> > > >> >> > Cheers, > >> >> > Davidm > >> >> > > >> >> > diff --git a/linux-3.10/drivers/net/usb/qmi_wwan.c > >> b/linux-3.10/drivers/net/usb/qmi_wwan.c > >> >> > index fb252c7..fddcfe0 100644 > >> >> > --- a/linux-3.10/drivers/net/usb/qmi_wwan.c > >> >> > +++ b/linux-3.10/drivers/net/usb/qmi_wwan.c > >> >> > @@ -580,6 +580,7 @@ static const struct usb_device_id products[] = { > >> >> > {QMI_FIXED_INTF(0x1199, 0x68a2, 8)}, /* Sierra Wireless > >> MC7710 in QMI mode */ > >> >> > {QMI_FIXED_INTF(0x1199, 0x68a2, 19)}, /* Sierra Wireless > >> MC7710 in QMI mode */ > >> >> > {QMI_FIXED_INTF(0x1199, 0x901c, 8)}, /* Sierra Wireless > >> EM7700 */ > >> >> > + {QMI_FIXED_INTF(0x1199, 0x9051, 8)}, /* Sierra Wireless > >> MC7700 */ > >> >> > {QMI_FIXED_INTF(0x1bbb, 0x011e, 4)}, /* Telekom > >> Speedstick LTE II (Alcatel One Touch L100V LTE) */ > >> >> > {QMI_FIXED_INTF(0x2357, 0x0201, 4)}, /* TP-LINK HSUPA > >> Modem MA180 */ > >> >> > {QMI_FIXED_INTF(0x1bc7, 0x1200, 5)}, /* Telit LE920 */ > >> >> > diff --git a/linux-3.10/drivers/usb/serial/sierra.c > >> b/linux-3.10/drivers/usb/serial/sierra.c > >> >> > index 8894665..16e40c4 100644 > >> >> > --- a/linux-3.10/drivers/usb/serial/sierra.c > >> >> > +++ b/linux-3.10/drivers/usb/serial/sierra.c > >> >> > @@ -288,6 +288,12 @@ static const struct usb_device_id id_table[] = { > >> >> > { USB_DEVICE_AND_INTERFACE_INFO(0x0F3D, 0x68AA, 0xFF, 0xFF, > >> 0xFF), > >> >> > .driver_info = > >> (kernel_ulong_t)&direct_ip_interface_blacklist > >> >> > }, > >> >> > + { USB_DEVICE_AND_INTERFACE_INFO(0x1199, 0x9051, 0xFF, 0xFF, > >> 0xFF), > >> >> > + .driver_info = > >> (kernel_ulong_t)&direct_ip_interface_blacklist > >> >> > + }, > >> >> > + { USB_DEVICE_AND_INTERFACE_INFO(0x1199, 0x9051, 0xFF, 0x00, > >> 0x00), > >> >> > + .driver_info = > >> (kernel_ulong_t)&direct_ip_interface_blacklist > >> >> > + }, > >> >> > { USB_DEVICE(0x0f3d, 0x68A3), /* Airprime/Sierra Wireless > >> Direct IP modems */ > >> >> > .driver_info = > >> (kernel_ulong_t)&direct_ip_interface_blacklist > >> >> > >> >> > >> >> Is this reported to the LKML already? > >> > > >> > Not by me yet, its on my TODO list, happy to have it passed along or > >> to > >> > send it. When I saw the thread here I figured I had better at least > >> chip > >> > in where I am at if it helps. > >> > >> It is already there in v3.14 and most of the stable kernels, including > >> stable-3.10.y > >> > >> I don't think the sierra driver is appropriate for newer non-DirectIP > >> devices. The Netgear 340u is so similar to the other Qualcomm based > >> Sierra devices that I added it to the qcserial driver instead. > >> > >> But this reminds me that I have a pile of patches for other devices. > >> I'll clean those up and submit ASAP. > >> > >> > >> Bjørn > >> > > > > </div></div><div class="HOEnZb"><div class="h5">-- David McCullough, <a href="mailto:david.mccullough@accelecon.com">david.mccullough@accelecon.com</a>, Ph: 0410 560 763 </div></div></blockquote></div> </div>