<div dir="ltr"><div>Apologies .. I meant "1199:9051" - that is the modem I use. And the kernel I use is 3.12.13. </div>If you are adventurous ;), would you mind upgrading the firmware to the latest and see if that still works :) ? Also whats the kernel version you use ? Rgds, Gopa. </div><div class="gmail_extra"> <div class="gmail_quote">On Wed, Aug 13, 2014 at 7:52 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"> Gopakumar Choorakkot Edakkunni wrote the following: <div class="">> Going back to the VID/PID, I was looking up the qmi_wwan.c in the kernel > sources and I find that the 1109:9051 is not in the QMI_FIXED_INTF table in > the kernel version I am running (3.12.13) !! And in the kernel version > 3.12.16 for example, I see the 1109:9051 in the table (correctly as Aircard > 340U). But I promise it was just working perfectly fine till the firmware > upgrade :) - which means it was either working purely by "chance" (is that > possible!!) or that the PID changed after a firmware upgrade (highly > unlikely ?). > > At any rate, I will try out the 3.12.16 kernel tomorrow or just add > 1109:9051 to the list in 3.12.13 and see how it goes. Will update tomorrow. </div>Mine runs at 1199:9051, id the 1109 a typo ? ATI shows revision: SWI9X15C_01.05.11.23 r13063 carmd-fwbuild1 2013/03/30 23:11:32 Which is almost certinaly the older rev, Cheers, Davidm <div><div class="h5"> > On Wed, Aug 13, 2014 at 5:26 PM, Gopakumar Choorakkot Edakkunni < > <a href="mailto:gopakumar.c.e@gmail.com">gopakumar.c.e@gmail.com</a>> wrote: > > > Hi Aleksander, > > > > Thanks a lot for the suggestions. I tried them out, but that did not solve > > the problem. I upgraded to libqmi 1.10.2 to get the latest clis .. I cross > > checked with a couple of other people with Sierra/Netgear 340U modems > > running linux and they are facing the same issue too. The firmware version > > just before this latest one was all hunky dory and great, unfortunately the > > upgrade to the latest has caused this issue. > > > > Before issuing the command you suggested: > > > > wwan0 Link encap:Ethernet HWaddr C2:4A:EB:3B:51:7C > > inet6 addr: fe80::c04a:ebff:fe3b:517c/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:139 errors:0 dropped:0 overruns:0 > > carrier:0 <<<<========== These are DHCP packets > > going out > > collisions:0 txqueuelen:1000 > > RX bytes:0 (0.0 B) TX bytes:48174 (47.0 > > KiB) <<<<========== No response > > > > > > Now I issue the command: > > > > root:~# qmicli -d /dev/cdc-wdm0 > > --wda-set-data-format="802-3" > > [/dev/cdc-wdm0] Successfully set data format > > QoS flow header: no > > Link layer protocol: '802-3' > > Uplink data aggregation protocol: 'disabled' > > Downlink data aggregation protocol: 'disabled' > > NDP signature: '0' > > Downlink data aggregation max datagrams: '0' > > Downlink data aggregation max size: '0' > > > > As seen in ifconfig below, it has no change (DHCP requests have been going > > on continuosly in the meantime via udhcpc) : > > > > root:~# ifconfig wwan0 > > wwan0 Link encap:Ethernet HWaddr C2:4A:EB:3B:51:7C > > inet6 addr: fe80::c04a:ebff:fe3b:517c/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:306 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:0 (0.0 B) TX bytes:115308 (112.6 > > KiB) <<<<<=========== Still no response > > > > Rgds, > > Gopa. > > > > > > > > > > > > > > On Wed, Aug 13, 2014 at 4:13 PM, Aleksander Morgado < > > <a href="mailto:aleksander@aleksander.es">aleksander@aleksander.es</a>> wrote: > > > >> On Wed, Aug 13, 2014 at 9:19 PM, Dan Williams <<a href="mailto:dcbw@redhat.com">dcbw@redhat.com</a>> wrote: > >> > Bjorn: I see that the Sierra drivers expect the following layout > >> > > >> > Serial: > >> > 1199:68A2 - blacklisted: 8, 10, 11, 19, 20 > >> > 1199:68C0 - blacklisted: 8, 10, 11 > >> > 1199:9057 - blacklisted: 0, 1, 5, 8, 10, 11 ("Netgear AC341U IPT2 mode") > >> > > >> > Net: > >> > 1199:68A2 - 8, 10, 19 ("MDM9x15 PDNs") > >> > 1199:68C0 - 8, 10, 19 > >> > 1199:9057 - 8, 10, 11 > >> > > >> > Which means that qmi_wwan is missing: > >> > > >> > 1199:68a2: 10 > >> > 1199:68c0: 19 > >> > 1199:9057: 10, 11 > >> > > >> > No idea whether adding these to qmi_wwan would be useful or not, you've > >> > done more work than I with these devices, and I'm not sure where we > >> > landed on whether or not to expose the non-functional QMI interfaces > >> > through qmi_wwan. > >> > >> It was decided not to expose the non-functional ones. > >> > >> E.g. the MC7304 (0x1199, 0x68c0) exposed interfaces 8, 10 and 11. 8 > >> and 10 were both QMI (one with raw-ip by default, the other one with > >> 802-3 by default), and 11 was the non-functional one, so it was > >> removed from the driver. > >> > >> -- > >> Aleksander > >> <a href="https://aleksander.es" target="_blank">https://aleksander.es</a> > >> > > > > </div></div>> _______________________________________________ > libqmi-devel mailing list > <a href="mailto:libqmi-devel@lists.freedesktop.org">libqmi-devel@lists.freedesktop.org</a> > <a href="http://lists.freedesktop.org/mailman/listinfo/libqmi-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/libqmi-devel</a> -- David McCullough, <a href="mailto:davidm@spottygum.com">davidm@spottygum.com</a>, Ph: 0410 560 763 </blockquote></div> </div>