[no subject]
auth 9af38645 subscribe linux-usb tschae...@t-online.de -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH net,stable] net: cdc_ncm: fix control message ordering
I will test also a further device(k5150), which was not working since 3.13, later this week. The test was ok. The K5150 from HUAWEI/Vodafone (mbim) works again. At least with IPv4. No statement about IPv6. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH net,stable] net: cdc_ncm: fix control message ordering
Am Montag, 17. März 2014, 16:25:18 schrieben Sie: This is a context modified revert of commit 6a9612e2cb22 (net: cdc_ncm: remove ncm_parm field) which introduced a NCM specification violation, causing setup errors for some devices. These errors resulted in the device and host disagreeing about shared settings, with complete failure to communicate as the end result. I applied this patch to 3.14.0rc6. I can confirm that the huawei devices E3276 und E5776 (both DTAG branded) work again. I will test also a further device(k5150), which was not working since 3.13, later this week. Thanks a lot, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH net-next v6 0/3] The huawei_cdc_ncm driver / E3276 problem
Am 14.03.2014 10:24, schrieb Enrico Mioso: Other than this, I do not have this device at hand, so can't see what happens. From the version number, I expect the firmware being HiSilicon (not Qualcomm). Try also using dhcpcd if you can / want / like :) . Thank you. dhcpcd doesn’t work too. I have two devices with the same problem the E3276 (Deutsche Telekom branded) and the E5776(Deutsche Telekom branded). The device E3276 is also available as HILINK-Version, this version still works with newer kernels, but uses also a different driver (cdc_ether). Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re:usb: cdc-wdm:
Am 23.12.2013 08:41, schrieb Bjørn Mork: my QMI (MC7710, E392) and MBIM (MC7710, DWM-156) modems all work fine with v3.13-rc3 and IPv6, except for the Huawei E367 which doesn't support IPv6 PDPs at all (at least not with the firmware revision I have). None of the modems seem to respond to DHCPv6 solicits. The MC7710 and E392 support RS/RA. All support management protocol address configuration. Which should be the default for MBIM in any case, given that it is a standard part of the protocol and the DHCP and RA daemon in modem firmware is a really ugly hack. Only for clarification: Should I test the mbim device only with the information I get from: mmlci -b no autoconfig: RS/RA, no dhcpv6? (windows behavior was different) Regarding IPv4 at mbim no dhcpv4? qmi-devices: test with dhcpv4 test with RS/RA, without dhcpv6 ncm: Happy New Year! Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] usb: cdc-wdm: avoid hanging on zero length reads
Hi Bjørn, it seems to me that this patch solved some problems. ( time out ) Some other problems introduced in 3.13 are still there. mbim wwan and dhcpv4 does not work (worked in 3.12) K5150 huawai ncm wwan and dhcpv4 does not work (ncm worked in 3.12) E5776 Unfortunately I can not test IPv6-behavior at the moment. (the agreement was limited, I am not sure, if I get a new one) Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: huawei E5776 (hilink) 3.12--3.13 not working anymore
Am 27.11.2013 13:33, schrieb Bjørn Mork: Thomas Schäfer tschae...@t-online.de writes: Hi, I have it already mentioned somewhere. Sorry for duplicates. The Huawei E5776 (normal use, classic IPv4, hilink mode (with webinterface and RFC1918 IP- config including NAT) So this is always connected and you don't normally use ModemManager or any other userspace utility to manage it? Yes. I am not sure if Networkmanager was involved, but if so, he did only dhcp. (or I started the dhcpcd ) I guess it should be a wwan device at all then, but I don't see how we can avoid that given that both PID and subclass/protocol is same as managed modems. Some other hilink-devices, I have seen, use cdc_ether instead, still working with 3.13. Anyway, this is obviously not the problem in your case. worked well with 3.12 and before, but it doesn't work any more with 3.13. At least one local branded version of the huawei E3776 is also affected. Yes, and you already tested reverting all changes to cdc_ncm with that modem, was that so? You still have the same problems with the v3.12 version of cdc_ncm running on v3.13-rc1+? If I remember correctly yes. How about looking at usbmon differences? That should show us where things start to go wrong. I will try it tonight. Thomas PS: in the meantime I was shocked by the change of 0930:1319 Ericsson H5321gw from cdc_ncm to mbim in older kernel-versions. But this is a different site. I will test mbim on this device later, because first tests are stopped by compiling problems at the live-CD. -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: huawei E5776 (hilink) 3.12--3.13 not working anymore
Am 27.11.2013 13:33, schrieb Bjørn Mork: How about looking at usbmon differences? That should show us where things start to go wrong. Here are the two cases 3.12 with a short connection dhcp and ping 3.13 with failing dhcp I hope I caught the right bus. Because of the size of files (1MB) I send the traces only as link, not as attachment. http://www.cis.uni-muenchen.de/~thomas/e5776-usb-capture-3.12.good-case.pcapng http://www.cis.uni-muenchen.de/~thomas/e5776-usb-capture-3.13.bad-case.pcapng Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
huawei E5776 (hilink) 3.12--3.13 not working anymore
Hi, I have it already mentioned somewhere. Sorry for duplicates. The Huawei E5776 (normal use, classic IPv4, hilink mode (with webinterface and RFC1918 IP- config including NAT) worked well with 3.12 and before, but it doesn't work any more with 3.13. At least one local branded version of the huawei E3776 is also affected. Thomas e5776.tar.xz Description: application/xz-compressed-tar
status of Sierra Wireless MC8305 1199:9011 ?
Hi, Yesterday I have had a access to a new notebook with built in UMTS-device. The live-cd with kernel 3.7 tried qmi_wwan, but failed: [ 12.115215] qmi_wwan 1-1.5:2.5: CDC functional descriptors missing [ 12.115226] qmi_wwan: probe of 1-1.5:2.5 failed with error -1 [ 12.115244] usbcore: registered new interface driver qmi_wwan I tried manually the option-driver, but then the system is crashed. Any hints, test proposals? Thomas Bus 001 Device 008: ID 1199:9011 Sierra Wireless, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x1199 Sierra Wireless, Inc. idProduct 0x9011 bcdDevice0.02 iManufacturer 4 Sierra Wireless Inc iProduct3 MC8305 iSerial 0 bNumConfigurations 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 157 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 1 Qualcomm Configuration bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes2 Transfer TypeBulk Synch Type
Re: huawei_cdc_ncm driver
If that still does not change anything, then I'd really appreciate it if you could run through (assuming the v3.11 driver was OK): git bisect start 9fea037de5f3 v3.11 -- drivers/net/usb/cdc_ncm.c That failed too. (switching was ok, compiling was ok, booting, recognizing the devices ok, but dhcp / RA not ok) So problem seems to be somewhere but not in you driver. Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: huawei_cdc_ncm driver
The second device with problems is Huawei E3276 (Speedstick LTE III, Telekom, no Hilink, but ipv6-cabable version) This device worked before with SLAAC, now with -next-20131107 it doesn't. Ouch. I noticed after submitting this driver that it probably has some flawed logic wrt carrier detection. I wonder if this patch makes any difference (yes, just delete that line): It didn't. I will test again, from time to time linux-next. If the problem is still there while releasing RC-versions, I will cry out again. Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
huawei_cdc_ncm driver
Hi, I know that next-kernel may not stable/work. But for your information. I tried 3.12.0-next-20131107-1-vanilla (next repository from Suse, because compiling needs time and patience :-)) Two devices which worked with cdc_ncm now changed to huawei_cdc_ncm. So far so ok. But: E5776-s-32 (local name here Speedbox LTE mini) does not work anymore via USB-cable: dmesg [ 2826.012219] usb 5-1: new high-speed USB device number 8 using ehci-pci [ 2826.145639] usb 5-1: New USB device found, idVendor=12d1, idProduct=1506 [ 2826.145658] usb 5-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 2826.145669] usb 5-1: Product: HUAWEI Mobile [ 2826.145678] usb 5-1: Manufacturer: HUAWEI Technology [ 2826.152083] option 5-1:1.0: GSM modem (1-port) converter detected [ 2826.152490] usb 5-1: GSM modem (1-port) converter now attached to ttyUSB0 [ 2826.155877] huawei_cdc_ncm 5-1:1.1: MAC-Address: 0c:5b:8f:27:9a:64 [ 2826.156234] huawei_cdc_ncm 5-1:1.1: cdc-wdm0: USB WDM device [ 2826.156867] huawei_cdc_ncm 5-1:1.1 wwan0: register 'huawei_cdc_ncm' at usb-:00:1d.7-1, Huawei CDC NCM device, 0c:5b:8f:27:9a:64 [ 2826.157098] usb-storage 5-1:1.2: USB Mass Storage device detected [ 2826.158778] scsi12 : usb-storage 5-1:1.2 [ 2826.159371] usb-storage 5-1:1.3: USB Mass Storage device detected [ 2826.159657] scsi13 : usb-storage 5-1:1.3 [ 2827.157269] scsi 12:0:0:0: CD-ROMHUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [ 2827.157816] scsi 13:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 [ 2827.162841] sd 13:0:0:0: Attached scsi generic sg1 type 0 [ 2827.164308] sr0: scsi-1 drive [ 2827.165040] sr 12:0:0:0: Attached scsi CD-ROM sr0 [ 2827.165397] sd 13:0:0:0: [sdb] Attached SCSI removable disk [ 2827.165564] sr 12:0:0:0: Attached scsi generic sg2 type 5 dhcp does not work dhcpcd wwan0 err, wwan0: timed out warn, wwan0: using IPV4LL address 169.254.243.114 The second device with problems is Huawei E3276 (Speedstick LTE III, Telekom, no Hilink, but ipv6-cabable version) This device worked before with SLAAC, now with -next-20131107 it doesn't. Kernel 3.12 is without problems. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 12d1 1f16 ; 12d1 1575 mbim IPV6/ipv4
Bjørn Mork bj...@mork.no writes: That was probably a bit too brief. What I meant was: Try changing the last argument to ipv6_stub-ndisc_send_na() from false to true and see if that makes any difference. It made a difference. It works. For checking en detail: http://www.cis.uni-muenchen.de/~thomas/mbim-5150-20131030-any.pcapng Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 12d1 1f16 ; 12d1 1575 mbim IPV6/ipv4
Am Montag, 28. Oktober 2013, 09:46:30 schrieben Sie: The patch requires v3.12 I tried it. It hasn't crashed, but it hasn't worked too. Two traces are attached. Regards, Thomas mbim-5150-20131029-any.pcapng.7z Description: application/7z-compressed mbim-5150-20131029-wwan0.pcapng.7z Description: application/7z-compressed
Re: LTE vodafone K5150 12d1 1f16 ; 12d1 1575 mbim IPV6/ipv4
Hi Bjørn, I tested your patch with the K5150 in mbim-mode with ipv6 only - ok. with Ipv4 only - ok. I have only one mbim-device, this 5150. Let me know, if you need further tests. Thank you! Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 12d1 1f16 ; 12d1 1575 mbim IPV6
Am Donnerstag, 24. Oktober 2013, 11:45:39 schrieben Sie: Did you try any of the ND tuning controls on Linux? Turning on ARP before bringing up the interface might work on IPv6 (but fail for IPv4): ifconfig wwan0 arp This solved the problem. (IPv6 positive , IPv4 at the moment untested) Trying sysctl -w net.ipv6.conf.wwan0.ndisc_notify = 1 would also be interesting (although I have no idea what the effect would be in combination with IFF_NOARP). This was without effect. Another interesting test would be adding the solicited node multicast address manually, but I can't figure out how to do that using e.g. ip maddr You can certainly do it with setsockopt(), but that's a bit more work than it should be. After the first hint solved the problem, only the report of state while it is working: ip maddr .. 6: wwan0 link 33:33:00:00:00:01 link 01:00:5e:00:00:01 link 33:33:ff:16:b0:d2 link 33:33:ff:a7:ad:1c link 33:33:00:00:00:fb link 01:00:5e:00:00:fb inet 224.0.0.251 inet 224.0.0.1 inet6 ff02::fb inet6 ff02::1:ffa7:ad1c inet6 ff02::1:ff16:b0d2 users 2 inet6 ff02::1 inet6 ff01::1 Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 12d1 1f16 ; 12d1 1575 mbim IPV6/ipv4
Am Samstag, 26. Oktober 2013, 16:01:26 schrieben Sie: Thomas Schäfer tschae...@t-online.de writes: Am Donnerstag, 24. Oktober 2013, 11:45:39 schrieben Sie: Did you try any of the ND tuning controls on Linux? Turning on ARP before bringing up the interface might work on IPv6 (but fail for IPv4): ifconfig wwan0 arp This solved the problem. (IPv6 positive , IPv4 at the moment untested) Great! Then I believe we have positive confirmation that this firmware really needs neigbour discovery. Now we only have to figure out how to support that without breaking IPv4. That's your part :-) Now I tested IPv4 with arp, and you are right. It doesn't work. Ping is answered with Destination Host Unreachable. If I switch off arp again with ifconfig wwan0 -arp, ping works. Regards, Thomas PS: I can only test IPv4-only OR IPv6-only. I don't know the behavior of dualstack-mobile-connections. -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 mbim?
Am 24.10.2013 11:45, schrieb Bjørn Mork: Any chance you could snoop the Windows IPv6 session? I'm interesting in seeing the NS and NA messages. In particular any NA from Windows. Don't need many packets, only the part where the modem tries to discover the host L2 address. To answering one question for the moment. Wireshark did not work (interface does not appear) . But nm3.4 does. Because of the size I will store this capture file here for a while. http://www.cis.uni-muenchen.de/~thomas/k5150-nm-capture.cap ra, dhcpv6(DNS) and the ms-connections-test (ncsi) are there. I hope, you see also the things you want to know. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 mbim?
Hi, I have some news about this device. Under Windows 8.1 (6.3)(testversion) with these IDs: USB\VID_12D1PID_1F16REV_0102MI_00 USB\VID_12D1PID_1F16MI_00 USB\Class_02SubClass_0eProt_00 USB\Class_02SubClass_0e USB\Class_02 the device works as mobile broadband device with IPv6. So I think the firmware is ok, or Microsoft has patched its driver a little bit more. One thing has surprised me - I configured the DNS-Resolvers static. But windows/vodafone ?? has added the public IPv6-DNS-resolvers from google, which of course don't work with NAT64. Has MBIM an interface for requesting/setting DNS-resolver-entries? Unfortunately I was not able to capture anything, no net, no usb. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
Am Mittwoch, 9. Oktober 2013, 23:29:49 schrieb Bjørn Mork: will show you a number of interesting debug sites which can be enabled without rebuilding anything. See Documentation/dynamic-debug-howto.txt for details on how to use this. I played a little bit with it, but there are no much debug messages: [ 1636.302763] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=0, on=1 [ 1636.547122] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=1, on=0 [ 1636.568796] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=0, on=1 [ 1666.741226] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=1, on=0 [ 1673.301643] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=0, on=1 [ 1673.545124] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=1, on=0 [ 1673.557197] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=0, on=1 [ 1996.872282] cdc_mbim 1-2:2.0: unknown notification 42 received: index 0 len 8 [ 1996.876271] cdc_mbim 1-2:2.0: unknown notification 2 received: index 0 len 0 [ 2002.287922] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=1, on=1 [ 2002.288004] cdc_mbim 1-2:2.0 wwan0: rxqlen 0 -- 2 [ 2193.313287] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=2, on=0 [ 2215.728510] cdc_mbim 1-2:2.0: unknown notification 42 received: index 0 len 8 [ 2215.732496] cdc_mbim 1-2:2.0: unknown notification 2 received: index 0 len 0 [ 2221.196734] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=1, on=1 [ 2221.196837] cdc_mbim 1-2:2.0 wwan0: rxqlen 0 -- 2 [ 2296.201417] usb 1-2: USB disconnect, device number 3 [ 2296.203103] cdc_mbim 1-2:2.0 wwan0: unregister 'cdc_mbim' usb-:00:1d.7-2, CDC MBIM [ 2296.203213] cdc_mbim 1-2:2.0: cdc_mbim_manage_power() pmcount=2, on=0 Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
Am Samstag, 12. Oktober 2013, 13:46:19 schrieb Bjørn Mork: happens: ifconfig wwan0 arp Nope, that won't make any difference. At least on a proper ethernet interface we still answer NS for our addresses, even if we disable sending them. So the questions still are: Do you see those solicitatins going from the driver to the IP layer? And do you see any Neighbor Advertisement replies from the IP layer? If the respective answers are yes/no, then you should look elsewhere to find the problem. Too restrictive ip6tables maybe? I can exclude restrictive ip6tables( i check it on every test), i will sniff again, this time at the wwan0 interface. Sorry, that I can only offer tests and traces. You see immediately Wireshark wrongly identifies this as USB Mass Storage. I thought, this must be the ugly dummy-CDROM and have ignored these frames completely. Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
Am Samstag, 12. Oktober 2013, 13:46:19 schrieben Sie: So the questions still are: Do you see those solicitatins going from the driver to the IP layer? And do you see any Neighbor Advertisement replies from the IP layer? If the respective answers are yes/no, then you should look elsewhere to find the problem. Too restrictive ip6tables maybe? You asked a lot of questions. I attached two files, captured at wwan0 and at any. Only one thing surprises me. There are more than one routeradvertisements. ( in the past at the qmi devices I have seen it only once per connection) Regards, Thomas k5150-wwan0-ipv6.any.pcapng.7z Description: application/7z-compressed k5150-wwan0-ipv6.wwan0.pcanp.7z Description: application/7z-compressed
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
Bjørn writes: In the meantime, I have got the first ipv4-connection: Yes, that should work. 12d1 1f16 conf 2 Unfortunately IPv6 does only work one way. (no firewall) ModemManager/mmcli works - connected slaac - ok - address and default-route are there ping6 ??? packets go out, they reach their target and are replied, but the answers don't reach the pinging host Is this a problem of mbim or the firmware? The same device works with cdc_ether (Kernel 3.7) with IPv6. (as 12d1 1575). If somebody has an idea, please let me know. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
Bjørn writes: Could be the driver. I don't know if it is ever tested with IPv6, and it does a bit of header magic so it is possible to screw up. Of course, the same goes for the firmware (including the testing, i assume :-) usbmon dumps would be interesting. I attached a file, I am not sure, it is very small, I would expect more. Thomas 1.mon.out.gz Description: GNU Zip compressed data
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
OK, so it didn't switch at all. Then we are back to usb_modeswitch failure (or more likely: missing config for this device). You could test switching it manually: echo 2 /sys/bus/usb/devices/1-2/bConfigurationValue This was the point! [ 4007.213187] usb 1-2: new high-speed USB device number 3 using ehci-pci [ 4007.431431] usb 1-2: New USB device found, idVendor=12d1, idProduct=1f16 [ 4007.431447] usb 1-2: New USB device strings: Mfr=5, Product=4, SerialNumber=7 [ 4007.431457] usb 1-2: Product: K5150 [ 4007.431466] usb 1-2: Manufacturer: Vodafone (Huawei) [ 4007.431475] usb 1-2: SerialNumber: [ 4007.514427] usb-storage 1-2:1.0: USB Mass Storage device detected [ 4007.514702] scsi4 : usb-storage 1-2:1.0 [ 4007.516481] usbcore: registered new interface driver usb-storage [ 4008.540895] scsi 4:0:0:0: CD-ROMVodafone Storage(Huawei) 2.31 PQ: 0 ANSI: 2 [ 4008.542441] scsi 4:0:0:0: Attached scsi generic sg1 type 5 [ 4008.581734] sr0: scsi-1 drive [ 4008.581745] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 4008.583499] sr 4:0:0:0: Attached scsi CD-ROM sr0 [ 4034.699431] usb-storage 1-2:2.2: USB Mass Storage device detected [ 4034.706610] scsi5 : usb-storage 1-2:2.2 [ 4034.743924] usbcore: registered new interface driver cdc_wdm [ 4034.765370] usbcore: registered new interface driver cdc_ncm [ 4034.777380] cdc_mbim 1-2:2.0: cdc-wdm0: USB WDM device [ 4034.778563] cdc_mbim 1-2:2.0 wwan0: register 'cdc_mbim' at usb-:00:1d.7-2, CDC MBIM, e2:01:59:02:07:b3 [ 4034.782301] usbcore: registered new interface driver cdc_mbim [ 4035.708322] scsi 5:0:0:0: Direct-Access Vodafone Storage(Huawei) 2.31 PQ: 0 ANSI: 2 [ 4035.709395] sd 5:0:0:0: Attached scsi generic sg1 type 0 [ 4035.711547] sd 5:0:0:0: [sdb] Attached SCSI removable disk Here are some of my first steps with mbimcli: hpmini:~ # sudo mbimcli -d /dev/cdc-wdm0 --help-basic-connect Aufruf: mbimcli [OPTION …] - Control MBIM devices Basic Connect options --basic-connect-query-device-caps Query device capabilities --basic-connect-query-subscriber-ready-status Query subscriber ready status --basic-connect-query-radio-state Query radio state --basic-connect-query-device-services Query device services --basic-connect-query-pin Query PIN state hpmini:~ # sudo mbimcli -d /dev/cdc-wdm0 --basic-connect-query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'removable' Cellular class: 'gsm' Voice class: 'embedded' Sim class: 'removable' Data class: 'gprs, edge, umts, hsdpa, hsupa, custom' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '1' Custom data class: 'HSPA+' Device ID: '860112020053833' Firmware info: 'V3.0' Hardware info: 'CH1K5150M' hpmini:~ # sudo mbimcli -d /dev/cdc-wdm0 --basic-connect-query-subscriber- ready-status [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262020429000213' SIM ICCID: '89492004115002516990' Ready info: 'unknown' Telephone numbers: (0) 'unknown' hpmini:~ # sudo mbimcli -d /dev/cdc-wdm0 --basic-connect-query-radio-state [/dev/cdc-wdm0] Radio state retrieved: Hardware Radio State: 'on' Software Radio State: 'on' hpmini:~ # sudo mbimcli -d /dev/cdc-wdm0 --basic-connect-query-device-services [/dev/cdc-wdm0] Device services retrieved: Max DSS sessions: '5' Services: (8) Service: 'basic-connect' UUID: [a289cc33-bcbb-8b4f-b6b0-133ec2aae6df]: DSS payload: 0 Max DSS instances: 0 CIDs: device-caps (1), subscriber-ready-status (2), radio-state (3), pin (4), pin-list (5), home-provider (6), visible-providers (8), register-state (9), packet-service (10), signal-state (11), connect (12), provisioned-contexts (13), ip-configuration (15), device-services (16), device-service-subscriber-list (19), packet-statistics (20), network-idle-hint (21), emergency-mode (22) Service: 'sms' UUID:
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
Hi Bjørn, I can't answer your Questions. Do you recommend / know a usb-sniffer for Win8? In the meantime, I have got the first ipv4-connection: hpmini:~ # mbim-network /dev/cdc-wdm0 start Loading profile... APN: internet.telekom Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber- ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262012740108472' SIM ICCID: '8949020694606885' Ready info: 'unknown' Telephone numbers: (1) '+4915127093679' [/dev/cdc-wdm0] Session not closed: TRID: '3' Saving state... (TRID: 3) Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration- state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'TDG' Roaming text: 'unknown' Registration flags: 'none' [/dev/cdc-wdm0] Session not closed: TRID: '4' Saving state... (TRID: 4) Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet- service --no-open=4 --no-close'... Saving state... (TRID: 5) Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=internet.telekom -- no-open=5 --no-close'... Network started successfully Saving state... (TRID: 6) hpmini:~ # (dhcp at wwan0 was ok) Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
Am 09.10.2013 09:03, schrieb Bjørn Mork: modprobe cdc_mbim echo 12d1 1f16 /sys/bus/usb/drivers_mbim/new_id has had no effect. Well, it shouldn't have any effect. The driver should already be autoloaded based on the class. Is it not? Does the probe fail? The driver is not already loaded. Modprobe does not fail, but in dmesg appear only three lines that something is registered. lsmod says cdc_mbim is not in use. There appear no devices. Relevant parts of dmesg would be interesting... And preferably with some debugging too, if the probing really fails. The hard tour, I will try to change from stable to linux-next pre builds(by distribution) and if nothing helps, I could try compiling the source. Within the next days I will do further tests and report here. Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
Am Mittwoch, 9. Oktober 2013, 10:50:38 schrieben Sie: Could you mount debugfs and send the relevant part of /sys/kernel/debug/usb/devices ? I'd like to verify which configuration and altsettings are currently active (1 and 2 before and after plug in of the device) diff -u 1.txt 2.txt --- 1.txt 2013-10-09 23:03:13.68477 +0200 +++ 2.txt 2013-10-09 23:04:20.596385935 +0200 @@ -54,7 +54,29 @@ I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms -T: Bus=01 Lev=01 Prnt=01 Port=05 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 +T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=480 MxCh= 0 +D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=ff MxPS=64 #Cfgs= 2 +P: Vendor=12d1 ProdID=1f16 Rev= 1.02 +S: Manufacturer=Vodafone (Huawei) +S: Product=K5150 +S: SerialNumber= +C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA +I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage +E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms +E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms +C: #Ifs= 3 Cfg#= 2 Atr=a0 MxPwr=500mA +A: FirstIf#= 0 IfCount= 2 Cls=02(comm.) Sub=0e Prot=00 +I: If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=0e Prot=00 Driver= +E: Ad=82(I) Atr=03(Int.) MxPS= 64 Ivl=2ms +I: If#= 1 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=02 Driver= +I: If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver= +E: Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms +E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms +I: If#= 2 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver= +E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms +E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms + +T: Bus=01 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=05c8 ProdID=021a Rev= 1.08 S: Manufacturer=GenesysLogic Technology Co., Ltd. Relevant parts of dmesg would be interesting... And preferably with some debugging too, if the probing really fails. hpmini:~ # dmesg [ 158.783166] usb 1-2: new high-speed USB device number 3 using ehci-pci [ 159.036814] usb 1-2: New USB device found, idVendor=12d1, idProduct=1f16 [ 159.036829] usb 1-2: New USB device strings: Mfr=5, Product=4, SerialNumber=7 [ 159.036840] usb 1-2: Product: K5150 [ 159.036849] usb 1-2: Manufacturer: Vodafone (Huawei) [ 159.036857] usb 1-2: SerialNumber: [ 159.091669] usb-storage 1-2:1.0: USB Mass Storage device detected [ 159.092190] scsi4 : usb-storage 1-2:1.0 [ 159.092519] usbcore: registered new interface driver usb-storage [ 160.111249] scsi 4:0:0:0: CD-ROMVodafone Storage(Huawei) 2.31 PQ: 0 ANSI: 2 [ 160.112164] scsi 4:0:0:0: Attached scsi generic sg1 type 5 [ 160.165484] sr0: scsi-1 drive [ 160.165498] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 160.166807] sr 4:0:0:0: Attached scsi CD-ROM sr0 [ 305.465773] r8169 :03:00.0 eth0: link up [ 305.465800] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 305.675256] NET: Registered protocol family 17 hpmini:~ # modprobe cdc_mbim hpmini:~ # dmesg [ 158.783166] usb 1-2: new high-speed USB device number 3 using ehci-pci [ 159.036814] usb 1-2: New USB device found, idVendor=12d1, idProduct=1f16 [ 159.036829] usb 1-2: New USB device strings: Mfr=5, Product=4, SerialNumber=7 [ 159.036840] usb 1-2: Product: K5150 [ 159.036849] usb 1-2: Manufacturer: Vodafone (Huawei) [ 159.036857] usb 1-2: SerialNumber: [ 159.091669] usb-storage 1-2:1.0: USB Mass Storage device detected [ 159.092190] scsi4 : usb-storage 1-2:1.0 [ 159.092519] usbcore: registered new interface driver usb-storage [ 160.111249] scsi 4:0:0:0: CD-ROMVodafone Storage(Huawei) 2.31 PQ: 0 ANSI: 2 [ 160.112164] scsi 4:0:0:0: Attached scsi generic sg1 type 5 [ 160.165484] sr0: scsi-1 drive [ 160.165498] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 160.166807] sr 4:0:0:0: Attached scsi CD-ROM sr0 [ 305.465773] r8169 :03:00.0 eth0: link up [ 305.465800] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 305.675256] NET: Registered protocol family 17 [ 467.394380] usbcore: registered new interface driver cdc_wdm [ 467.410406] usbcore: registered new interface driver cdc_ncm [ 467.415153] usbcore: registered new interface driver cdc_mbim hpmini:~ # lsmod | grep cdc cdc_mbim 13176 0 cdc_ncm20024 1 cdc_mbim usbnet 39440 2 cdc_mbim,cdc_ncm cdc_wdm18919 1 cdc_mbim No need if the problem is that it doesn't probe at all. But if you have dynamic debugging enabled and debugfs mounted, then egrep 'ncm|mbim' /sys/kernel/debug/dynamic_debug/control hpmini:~ # egrep 'ncm|mbim' /sys/kernel/debug/dynamic_debug/control drivers/net/usb/cdc_ncm.c:450 [cdc_ncm]cdc_ncm_bind_common =_ CDC Union missing - got slave from IAD\012 drivers/net/usb/cdc_ncm.c:994 [cdc_ncm]cdc_ncm_rx_fixup =_ invalid DPT16 signature %u\012
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
Am Montag, 7. Oktober 2013, 16:04:49 schrieben Sie: Have you verified that the latest version of usb-modeswitch doesn't fix this issue? I think I've seen reports that it does, but it would be good if you could test that out and verify it. May be it is intention. Under win8 it does not change its ID. Do we make the same break as MS does. (cdc -- mbim?) I copy my statement from http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3t=1703 There are two modes: Windows 7 and before has 12d1 1575 Windows 8 uses 12d1 1f16 (without switching, or without ID-change) Windows 8 information: hardware IDs USB\VID_12D1PID_1F16REV_0102MI_00 USB\VID_12D1PID_1F16MI_00 comatible IDs USB\Class_02SubClass_0eProt_00 USB\Class_02SubClass_0e USB\Class_02 lsusb -v with kernel 3.7 (like windows 7) Code: Bus 001 Device 004: ID 12d1:1575 Huawei Technologies Co., Ltd. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x12d1 Huawei Technologies Co., Ltd. idProduct 0x1575 bcdDevice1.02 iManufacturer 5 Vodafone (Huawei) iProduct4 K5150 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 71 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 2 configuration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 6 Ethernet Networking bInterfaceProtocol 0 iInterface 0 CDC Header: bcdCDC 1.10 CDC Ethernet: iMacAddress 1 582C80139263 bmEthernetStatistics0x0005 wMaxSegmentSize 1514 wNumberMCFilters0x0003 bNumberPowerFilters 1 CDC Union: bMasterInterface0 bSlaveInterface 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass10 CDC Data bInterfaceSubClass 6 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x (Bus Powered) lsusb -v with kernel 3.11 (like windows 8?) Code: Bus 001 Device 003: ID 12d1:1f16 Huawei Technologies Co., Ltd. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 255 bMaxPacketSize064 idVendor 0x12d1 Huawei Technologies Co., Ltd. idProduct 0x1f16 bcdDevice1.02 iManufacturer 5 Vodafone (Huawei) iProduct4 K5150 iSerial 7 bNumConfigurations 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1
Re: LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether mbim?
hpmini:~ # usb_modeswitch -j -v 12d1 -p 1f16 Search USB devices... Found device, searching for MBIM configuration... 2 hpmini:~ # usb_modeswitch -W -j -v 12d1 -p 1f16 Taking all parameters from the command line * usb_modeswitch: handle USB devices with multiple modes * Version 1.2.5 (C) Josua Dietze 2012 * Based on libusb0 (0.1.12 and above) ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x12d1 DefaultProduct= 0x1f16 TargetVendor= not set TargetProduct= not set TargetClass=not set TargetProductList= DetachStorageOnly=0 HuaweiMode=0 SierraMode=0 SonyMode=0 QisdaMode=0 GCTMode=0 KobilMode=0 SequansMode=0 MobileActionMode=0 CiscoMode=0 MessageEndpoint= not set MessageContent= NeedResponse=0 ResponseEndpoint= not set InquireDevice enabled (default) Success check disabled System integration mode disabled Search USB devices... Found device, searching for MBIM configuration... 2 hpmini:~ # -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
modeswitch? LTE vodafone K5150 (hilink) 12d1 1f16 ; 12d1 1575 cdc_ether
Hi, The vodafone K5150 is a LTE device, default is hilink mode. This works under Linux 3.7 in the same way as it under windows vista does. [ 248.255172] usb 1-1: new high-speed USB device number 3 using ehci_hcd [ 248.518600] usb 1-1: New USB device found, idVendor=12d1, idProduct=1f16 [ 248.518621] usb 1-1: New USB device strings: Mfr=5, Product=4, SerialNumber=7 [ 248.518635] usb 1-1: Product: K5150 [ 248.518647] usb 1-1: Manufacturer: Vodafone (Huawei) [ 248.518658] usb 1-1: SerialNumber: [ 248.568343] Initializing USB Mass Storage driver... [ 248.569941] scsi4 : usb-storage 1-1:1.0 [ 248.570636] usbcore: registered new interface driver usb-storage [ 248.570646] USB Mass Storage support registered. [ 248.711564] usb 1-1: USB disconnect, device number 3 [ 249.215161] usb 1-1: new high-speed USB device number 4 using ehci_hcd [ 249.411707] usb 1-1: New USB device found, idVendor=12d1, idProduct=1575 [ 249.411722] usb 1-1: New USB device strings: Mfr=5, Product=4, SerialNumber=0 [ 249.411732] usb 1-1: Product: K5150 [ 249.411741] usb 1-1: Manufacturer: Vodafone (Huawei) [ 249.494478] cdc_ether 1-1:1.0 eth1: register 'cdc_ether' at usb-:00:1d.7-1, CDC Ethernet Device, 58:2c:80:13:92:63 [ 249.494624] usbcore: registered new interface driver cdc_ether [ 249.515786] systemd-udevd[1212]: renamed network interface eth1 to eth2 [ 249.875661] NET: Registered protocol family 17 Under Linux 3.11 (or may be earlier) this device stops working. Possibly the switch-function has been removed from the kernel, but udev/usb-modeswitch does not know about. May be someone can suggest/provide a switch-sequence. [ 187.632182] usb 1-1: new high-speed USB device number 3 using ehci-pci [ 187.887782] usb 1-1: New USB device found, idVendor=12d1, idProduct=1f16 [ 187.887798] usb 1-1: New USB device strings: Mfr=5, Product=4, SerialNumber=7 [ 187.887809] usb 1-1: Product: K5150 [ 187.887818] usb 1-1: Manufacturer: Vodafone (Huawei) [ 187.887827] usb 1-1: SerialNumber: [ 187.940114] usb-storage 1-1:1.0: USB Mass Storage device detected [ 187.940357] scsi4 : usb-storage 1-1:1.0 [ 187.940669] usbcore: registered new interface driver usb-storage [ 188.960983] scsi 4:0:0:0: CD-ROM Vodafone Storage(Huawei) 2.31 PQ: 0 ANSI: 2 [ 188.961902] scsi 4:0:0:0: Attached scsi generic sg1 type 5 [ 189.001945] sr0: scsi-1 drive [ 189.001956] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 189.003335] sr 4:0:0:0: Attached scsi CD-ROM sr0 Simply eject /dev/sr0 doesn't work. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Driver for TP-Link on Ubunt server 12
Am 01.10.2013 13:27, schrieb edison...@fa.sg: Hi, Please help me to add the driver on my TP-Link device based on the dmesg log below. Ok, this is an TP-link MA260. option and qmi_wwan Kernel-modules work with that device. You should not try to load usbserial. May be you did it or a wrong script. On old kernels you can use /dev/ttyUSB0 for ppp-connection. On newer kernels you should use wwan0 and /dev/cdc_wdm Some information of this device are collected here: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3t=1525 You can ignore the first part, because your device seems to be in the right mode. (already switched) Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Driver for TP-Link on Ubunt server 12
Hi Edison, we should start again. You are using ubuntu 12? Is it right, that your kernel-version is 3.2.0-30 ? (uname -a ) I am not sure, but in this case you can forget qmi and you can focus on option. In your first mail usb-switch did work correctly. you should see 2357:f000 directly after plug in and you should work with 2357:9000. If option doesn't load, then load it via modprobe and echo 2357 9000 /sys/bus/usb-serial/drivers/option1/new_id Then try to use Network/Modemmanager to connect via /dev/ttyUSB0. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: New USB Modem (using option driver new_id)
Am Sonntag, 11. August 2013, 15:08:26 schrieben Sie: Hello, .. 1. Smartfren xStream e781a with vid 0x1bbb and pid 0x0106 2. Smartfren AC682 with vid 0x19d2 and pid 0xffdd I have tested those modems. They run perfectly with option usb serial driver (/sys/bus/usb-serial/drivers/option1/new_id). Do you have also information from windows drivers or did you try modprobe qmi_wwan echo 1bbb 0106 /sys/bus/usb/drivers/qmi_wwan/new_id echo 19d2 ffdd /sys/bus/usb/drivers/qmi_wwan/new_id Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Huawei E3131 wwan interface
Am Montag, 1. Juli 2013, 00:37:14 schrieben Sie: Hi! I'm trying to investigate on the Huawei E3131 wwan interface - Is the E3131 an HILINK-Modem? Have you tried simply starting dhcp/automatic-configuration? Open a Browser to get connected. If dns-redirection doesn't work, try the router or dns/resolver-address. http://192.168.x.x. ip route | grep default cat /etc/resolv.conf Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Huawei 3276 with option and cdc_ncm
Am Freitag, 17. Mai 2013, 14:41:20 schrieben Sie: Thomas Schäfer tschae...@t-online.de writes: Hi, the LTE-stick huawei 3276 (in Germany also alias Telekom Speedstick LTE III) works well One thing is little mysterious. The byte-statistics at the interface differ. while downloading an iso-image via qmi_wwan ( here with 4G XS Stick W100T) RX 733MB TX 29 MB while downloading the same iso-image via cdc_ncm (Huawei 3276) RX 727MB TX 116MB (ignore RX, this difference is only noise ) This in only one example. I did this test after I was surprised about the high TX-values while normal surfing The conditions are the same: IPv4, LTE, nearly equal speed, no uncommon things while watching with iptraf. Kernel 3.9.3-1.g0b5d8f5-desktop (suse) Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Huawei 3276 with option and cdc_ncm
Hello Bjørn ... TX-counter-problem ... This is expected as a result of the cdc_ncm = usbnet design. . The buffer filling may seem strange, but Alexey has explained it several times here on this list. It has to do with device DMA optimizations. Google it or search this list if you want the proper explanation. Thank you for the explanation (again). May be the following question is also repeated. Is there a different way to count the tx bytes? On mobile devices, mostly with volume-limited contracts, this number may have a higher meaning than normal. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Huawei 3276 with option and cdc_ncm
Hi, the LTE-stick huawei 3276 (in Germany also alias Telekom Speedstick LTE III) works well with linux. (also IPv6) Here is the output of dmesg (IPv4-connection). at^ndisdup=1,1,internet.telekom OK ^NDISSTAT:1,,,IPV4 [ 97.342188] usb 1-1: new high-speed USB device number 3 using ehci-pci [ 97.457592] usb 1-1: New USB device found, idVendor=12d1, idProduct=14fe [ 97.457608] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 97.457619] usb 1-1: Product: HUAWEI Mobile [ 97.457628] usb 1-1: Manufacturer: HUAWEI Technology [ 97.548179] Initializing USB Mass Storage driver... [ 97.550976] scsi4 : usb-storage 1-1:1.0 [ 97.552479] scsi5 : usb-storage 1-1:1.1 [ 97.552767] usbcore: registered new interface driver usb-storage [ 97.552776] USB Mass Storage support registered. [ 98.342756] usb 1-1: USB disconnect, device number 3 [ 98.676180] usb 1-1: new high-speed USB device number 4 using ehci-pci [ 98.791457] usb 1-1: New USB device found, idVendor=12d1, idProduct=1506 [ 98.791473] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 98.791483] usb 1-1: Product: HUAWEI Mobile [ 98.791492] usb 1-1: Manufacturer: HUAWEI Technology [ 98.796847] scsi6 : usb-storage 1-1:1.3 [ 98.798934] scsi7 : usb-storage 1-1:1.4 [ 98.831738] usbcore: registered new interface driver usbserial [ 98.831819] usbcore: registered new interface driver usbserial_generic [ 98.831871] usbserial: USB Serial support registered for generic [ 98.849762] usbcore: registered new interface driver option [ 98.849827] usbserial: USB Serial support registered for GSM modem (1-port) [ 98.856298] usb 1-1: MAC-Address: 0c:5b:8f:27:9a:64 [ 98.858361] cdc_ncm 1-1:1.2 wwan0: register 'cdc_ncm' at usb-:00:1d.7-1, Mobile Broadband Network Device, 0c:5b:8f:27:9a:64 [ 98.858455] option 1-1:1.0: GSM modem (1-port) converter detected [ 98.858873] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0 [ 98.858954] option 1-1:1.1: GSM modem (1-port) converter detected [ 98.860613] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1 [ 98.862692] usbcore: registered new interface driver cdc_ncm [ 99.801682] scsi 6:0:0:0: CD-ROMHUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [ 99.802410] scsi 7:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 [ 99.807347] sd 7:0:0:0: [sdb] Attached SCSI removable disk [ 99.807500] scsi 6:0:0:0: Attached scsi generic sg1 type 5 [ 99.807807] sd 7:0:0:0: Attached scsi generic sg2 type 0 [ 99.829118] sr0: scsi-1 drive [ 99.829131] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 99.830262] sr 6:0:0:0: Attached scsi CD-ROM sr0 [ 130.330738] ISO 9660 Extensions: Microsoft Joliet Level 1 [ 130.340973] ISOFS: changing to secondary root [ 398.807736] IPv6: ADDRCONF(NETDEV_UP): wwan0: link is not ready [ 398.812756] usb 1-1: NCM: unexpected notification 0x03! [ 398.820518] NET: Registered protocol family 17 [ 398.820755] usb 1-1: NCM: unexpected notification 0x03! [ 398.828767] usb 1-1: NCM: unexpected notification 0x03! [ 398.836762] usb 1-1: NCM: unexpected notification 0x03! [ 398.844770] cdc_ncm: wwan0: 43 mbit/s downlink 43 mbit/s uplink [ 398.852764] cdc_ncm: wwan0: network connection: connected [ 398.852913] IPv6: ADDRCONF(NETDEV_CHANGE): wwan0: link becomes ready at^ndisdup=1,0 OK ^NDISSTAT:0,,,IPV4 [ 948.121071] usb 1-1: NCM: unexpected notification 0x01! [ 948.129091] usb 1-1: NCM: unexpected notification 0x01! [ 948.137063] cdc_ncm: wwan0: network connection: disconnected What does unexpected notification mean? Should it be investigated, or is it harmless? Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: TP-LINK HSUPA Modem MA180 2357:0201
Am Mittwoch, 9. Januar 2013, 22:24:14 schrieben Sie: No further work need to be done in the kernel. Are you able to provide the Windows .INF files from the device so we can determine what kernel drivers each interface of the device requires? Basically, instead of modeswitching the device, let the fake CD disk appear, tar+gzip the contents of the fake CD, and mail it to me so I can inspect it. Diagnostics USB\VID_2357PID_0201MI_00\637BC1CE00 NMEAUSB\VID_2357PID_0201MI_01\637BC1CE01 Modem USB\VID_2357PID_0201MI_03\637BC1CE03 Networkcard USB\VID_2357PID_0201MI_04\637BC1CE04 mmc USBSTOR\CDROMVEN_TP-LINKPROD_MMC_STORAGEREV_2.31\77ED6A6108630770103305650 What specific model number is this device? Is it the MA180? Or is it the MA260? What model number is printed on the device? Does it have an FCC ID printed anywhere on it? MA180 FCC ID: T7MA180V2 IC: 8853-MA180V1 The examination at linux I will start later this day. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
TP-LINK HSUPA Modem MA180 2357:0201
Here are all infos about this device. I think I catched the relevant data. Switching to modem/network-mode works with eject /dev/sr0 It works with option /dev/ttyUSB2 has accepted at-commands and qmi_wwan (in testcase with interface 1 instead of 0) I was able get an IPv4- connection via qmi-interface. I was not able to get online via IPv6. qmi-version-infos are also inside the attachment. This is, what windows says about this device: Diagnostics USB\VID_2357PID_0201MI_00\637BC1CE00 NMEAUSB\VID_2357PID_0201MI_01\637BC1CE01 Modem USB\VID_2357PID_0201MI_03\637BC1CE03 Networkcard USB\VID_2357PID_0201MI_04\637BC1CE04 mmc USBSTOR\CDROMVEN_TP-LINKPROD_MMC_STORAGEREV_2.31\77ED6A6108630770103305650 Labels at the housing: MA180 FCC ID: T7MA180V2 IC: 8853-MA180V1 Windows-software at the stick is identical to http://www.tp-link.com.de/Resources/software/MA180_V1_Easy_Setup_Assistant.zip (same md5) Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html tp-link-ma180.tgz Description: application/compressed-tar
Re: TP-LINK HSUPA Modem
Am 09.01.2013 09:54, schrieb hockseng leow: I got the dmesg after having the parameters, usbserial.vendor=0x2357 usbserial.product=0x0200 in the linux start-up. That looks not very nice. I already got the modem working under usb_modeswitch. What about other people with the same device? No further work need to be done in the kernel. Sure? Thanks. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: TP-LINK HSUPA Modem
Is this device here the same?: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3t=942hilit=tp+link+hsupa+2357 If, yes. I am a little confused about the three device IDs: 2357:f006 2357:0200 2357:0201 If you like try option, qmi_wwan and post the results. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
new device for option and qmi_wwan
Hello the device called: Telekom Speedstick LTE II Alcatel Alcatel One Touch L100V LTE an may be more. With the ID idVendor=1bbb, idProduct=f017 (cdrom-dummy) and after eject /dev/sr0 idVendor=1bbb, idProduct=011e (network-mode) works well with option and qmi_wwan . echo 1bbb 011e /sys/bus/usb/drivers/qmi_wwan/new_id echo 1bbb 011e /sys/bus/usb-serial/drivers/option1/new_id Here are the information for the patches: USB\VID_1BBBPID_011EMI_00\62259AD200 Application1 interface USB\VID_1BBBPID_011EMI_01\62259AD201 Application2 interface USB\VID_1BBBPID_011EMI_03\62259AD203 Modem Interface USB\VID_1BBBPID_011EMI_04\62259AD204 AlcatelOTDC Wireless Ethernet Adapter USBSTOR\DISKVEN_USBMODEMPROD_MMC_STORAGEREV_2.31\71BB64CD0 USBModem MMC Storage USB Device More details (qmi-infos, lsusb) are attached. Regards, Thomas Bus 001 Device 004: ID 1bbb:011e T A Mobile Phones Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x1bbb T A Mobile Phones idProduct 0x011e bcdDevice0.00 iManufacturer 3 USBModem iProduct2 Mobile Broad Band iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 138 bNumInterfaces 5 bConfigurationValue 1 iConfiguration 1 USBModem Configuration bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage
Re: [PATCH] USB: qcaux: add Pantech vendor class match
P4200: test ok: udev/usbmodeswitch and this patch made the modem usable without user-interaction # dmesg [ 127.708165] usb 1-1: new high-speed USB device number 3 using ehci_hcd [ 127.843187] usb 1-1: New USB device found, idVendor=106c, idProduct=3b14 [ 127.843201] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=0 [ 127.843211] usb 1-1: Product: PANTECH P4200 [ 127.843219] usb 1-1: Manufacturer: Pantech, Incorporated [ 127.875355] Initializing USB Mass Storage driver... [ 127.875726] scsi4 : usb-storage 1-1:1.0 [ 127.876068] usbcore: registered new interface driver usb-storage [ 127.876074] USB Mass Storage support registered. [ 128.794621] usb 1-1: USB disconnect, device number 3 [ 130.412166] usb 1-1: new high-speed USB device number 4 using ehci_hcd [ 130.547468] usb 1-1: New USB device found, idVendor=106c, idProduct=3721 [ 130.547482] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=0 [ 130.547492] usb 1-1: Product: PANTECH P4200 [ 130.547501] usb 1-1: Manufacturer: Pantech, Incorporated [ 130.579114] cdc_acm 1-1:1.0: ttyACM0: USB ACM device [ 130.581675] usbcore: registered new interface driver cdc_acm [ 130.581683] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 130.594518] usbcore: registered new interface driver cdc_wdm [ 130.602740] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device [ 130.603261] qmi_wwan 1-1:1.5: wwan0: register 'qmi_wwan' at usb-:00:1d.7-1, WWAN/QMI device, 2a:c9:20:40:a0:23 [ 130.603357] usbcore: registered new interface driver qmi_wwan Am Mittwoch, 19. September 2012, 22:02:03 schrieben Sie: The three Pantech devices UML190 (106c:3716), UML290 (106c:3718) and P4200 (106c:3721) all use the same subclasses to identify vendor specific functions. Replace the existing device specific entries with generic vendor matching, adding support for the P4200. -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: BEEMO(OPTION) alias PANTECH P4200 LTE-Modem
One mysterious thing: atv at /dev/ttyACM via minicom crashs/resets the modem. Other at-command like ate, ati, c+cgdcont work, but getting all settings via atv fails. Have other pantech-modems this feature too? Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: BEEMO(OPTION) alias PANTECH P4200 LTE-Modem
I collected some additional information about this device. The windows-view: http://www.cis.uni-muenchen.de/~thomas/pantech-p4200-usb.png and the usbsnoop-logfile: http://www.cis.uni-muenchen.de/~thomas/pantech-p4200-usbsnoop.log.bz2 Has anybody suggestions, what could I do next? Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
BEEMO(OPTION) alias PANTECH P4200 LTE-Modem
The P4200 has two IDs, one for CD-Mode, one for modemmode. cd VID 0x106c PID 0x3b14 modem VID 0x106c PID 0x3721 eject /dev/sr0 does work for switching. This (stolen from similar device) usb_modeswitch -v 0x106c -p 0x3b14 -M 5553424312345678240088ff02444556434847 did work too. The serial modem interface is at /dev/ACM0 Under windows there is a networkcard. At the moment I don't know the driver-candidate for linux. qmi_wwan does catch but not work. Here the output of lusb: Code: Bus 001 Device 010: ID 106c:3721 Curitel Communications, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x106c Curitel Communications, Inc. idProduct 0x3721 bcdDevice0.00 iManufacturer 3 Pantech, Incorporated iProduct2 PANTECH P4200 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 189 bNumInterfaces 7 bConfigurationValue 1 iConfiguration 1 Pantech, Incorporated bmAttributes 0xc0 Self Powered MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 2 Abstract (modem) bInterfaceProtocol 1 AT-commands (v.25ter) iInterface 0 CDC Header: bcdCDC 1.10 CDC ACM: bmCapabilities 0x02 line coding and serial state CDC Call Management: bmCapabilities 0x03 call management use DataInterface bDataInterface 1 CDC Union: bMasterInterface0 bSlaveInterface 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass10 CDC Data bInterfaceSubClass 0 Unused bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber3 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass253
Re: surfstick K5006-Z in 3.6.0-rc4
Am Dienstag, 4. September 2012, 11:21:44 schrieben Sie: Could you post the output of lsusb -v or /sys/kernel/debug/usb/devices (with debugfs mounted) for this device? Here they are: dmesg lsusb /sys/kernel/debug/usb/devices [ 1080.264122] usb 1-4: new high-speed USB device number 3 using ehci_hcd [ 1080.400198] usb 1-4: New USB device found, idVendor=19d2, idProduct=1017 [ 1080.400216] usb 1-4: New USB device strings: Mfr=3, Product=2, SerialNumber=4 [ 1080.400229] usb 1-4: Product: ZTE LTE Technologies MSM [ 1080.400241] usb 1-4: Manufacturer: ZTE,Incorporated [ 1080.400253] usb 1-4: SerialNumber: MF821VVDFS02 [ 1080.86] usbcore: registered new interface driver uas [ 1080.452216] Initializing USB Mass Storage driver... [ 1080.453840] scsi4 : usb-storage 1-4:1.0 [ 1080.454128] usbcore: registered new interface driver usb-storage [ 1080.454135] USB Mass Storage support registered. [ 1083.599662] usb 1-4: USB disconnect, device number 3 [ 1088.088111] usb 1-4: new high-speed USB device number 4 using ehci_hcd [ 1088.223941] usb 1-4: New USB device found, idVendor=19d2, idProduct=1018 [ 1088.223955] usb 1-4: New USB device strings: Mfr=3, Product=2, SerialNumber=4 [ 1088.223965] usb 1-4: Product: ZTE LTE Technologies MSM [ 1088.223973] usb 1-4: Manufacturer: ZTE,Incorporated [ 1088.223981] usb 1-4: SerialNumber: MF821VVDFS02 [ 1088.231065] scsi5 : usb-storage 1-4:1.4 [ 1088.282944] usbcore: registered new interface driver cdc_wdm [ 1088.292875] qmi_wwan 1-4:1.3: cdc-wdm0: USB WDM device [ 1088.293426] qmi_wwan 1-4:1.3: wwan0: register 'qmi_wwan' at usb-:00:1d.7-4, WWAN/QMI device, 5a:8e:7f:57:b6:ca [ 1088.293537] usbcore: registered new interface driver qmi_wwan [ 1089.229793] scsi 5:0:0:0: CD-ROMVodafone USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0 [ 1089.230464] scsi 5:0:0:0: Attached scsi generic sg1 type 5 [ 1089.231789] scsi 5:0:0:1: Direct-Access Vodafone Storage 2.31 PQ: 0 ANSI: 0 [ 1089.235281] sd 5:0:0:1: Attached scsi generic sg2 type 0 [ 1089.239118] sd 5:0:0:1: [sdb] Attached SCSI removable disk [ 1089.264303] sr0: scsi-1 drive [ 1089.264313] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 1089.265674] sr 5:0:0:0: Attached scsi CD-ROM sr0 lsusb -v -d 19d2:1018 Bus 001 Device 004: ID 19d2:1018 ONDA Communication S.p.A. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x19d2 ONDA Communication S.p.A. idProduct 0x1018 bcdDevice0.00 iManufacturer 3 ZTE,Incorporated iProduct2 ZTE LTE Technologies MSM iSerial 4 MF821VVDFS02 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 138 bNumInterfaces 5 bConfigurationValue 1 iConfiguration 1 ZTE Configuration bmAttributes 0xc0 Self Powered MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass134 bInterfaceProtocol 16 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 2 bInterfaceProtocol 5 iInterface 0 Endpoint Descriptor: bLength 7
Re: surfstick K5006-Z in 3.6.0-rc4
Despite the patch
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x1018, 0xff, 0xff,
0xff),
.driver_info = (kernel_ulong_t)net_intf3_blacklist },
is included in option, it has no effect.
[ 1109.116127] usb 1-4: new high-speed USB device number 3 using ehci_hcd
[ 1109.251733] usb 1-4: New USB device found, idVendor=19d2, idProduct=1017
[ 1109.251750] usb 1-4: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[ 1109.251764] usb 1-4: Product: ZTE LTE Technologies MSM
[ 1109.251777] usb 1-4: Manufacturer: ZTE,Incorporated
[ 1109.251788] usb 1-4: SerialNumber: MF821VVDFS02
[ 1109.298493] usbcore: registered new interface driver uas
[ 1109.305952] Initializing USB Mass Storage driver...
[ 1109.312239] scsi4 : usb-storage 1-4:1.0
[ 1109.312541] usbcore: registered new interface driver usb-storage
[ 1109.312547] USB Mass Storage support registered.
[ 1112.473337] usb 1-4: USB disconnect, device number 3
[ 1116.932128] usb 1-4: new high-speed USB device number 4 using ehci_hcd
[ 1117.067894] usb 1-4: New USB device found, idVendor=19d2, idProduct=1018
[ 1117.067908] usb 1-4: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[ 1117.067918] usb 1-4: Product: ZTE LTE Technologies MSM
[ 1117.067926] usb 1-4: Manufacturer: ZTE,Incorporated
[ 1117.067934] usb 1-4: SerialNumber: MF821VVDFS02
[ 1117.073642] scsi5 : usb-storage 1-4:1.4
[ 1117.116156] usbcore: registered new interface driver cdc_wdm
[ 1117.125924] qmi_wwan 1-4:1.3: cdc-wdm0: USB WDM device
[ 1117.126454] qmi_wwan 1-4:1.3: wwan0: register 'qmi_wwan' at
usb-:00:1d.7-4, WWAN/QMI device, 46:91:ff:c8:e6:8e
[ 1117.126558] usbcore: registered new interface driver qmi_wwan
[ 1118.073723] scsi 5:0:0:0: CD-ROMVodafone USB SCSI CD-ROM 2.31
PQ: 0 ANSI: 0
[ 1118.074384] scsi 5:0:0:0: Attached scsi generic sg1 type 5
[ 1118.075607] scsi 5:0:0:1: Direct-Access Vodafone Storage 2.31
PQ: 0 ANSI: 0
[ 1118.077038] sd 5:0:0:1: Attached scsi generic sg2 type 0
[ 1118.083514] sd 5:0:0:1: [sdb] Attached SCSI removable disk
[ 1118.100971] sr0: scsi-1 drive
[ 1118.100980] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 1118.101388] sr 5:0:0:0: Attached scsi CD-ROM sr0
I don't have the module option blacklisted.
All other devices I have (two from huawei, two from zte ) with the combination
option/qmi still work.
echo-ing to new_id works too.
Thomas
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
surfstick K5006-Z in 3.6.0-rc3
short status update: Confirmation: the qmi_wwan works as expected. (/dev/cdc-wdm0 and wwan0 work) Missing the option patch for /dev/ttyUSBX for at-commands/classic ppp-connections Thomas dmesg [ 110.500114] usb 1-1: new high-speed USB device number 3 using ehci_hcd [ 110.635759] usb 1-1: New USB device found, idVendor=19d2, idProduct=1017 [ 110.635773] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4 [ 110.635783] usb 1-1: Product: ZTE LTE Technologies MSM [ 110.635791] usb 1-1: Manufacturer: ZTE,Incorporated [ 110.635799] usb 1-1: SerialNumber: MF821VVDFS02 [ 110.695096] usbcore: registered new interface driver uas [ 110.702221] Initializing USB Mass Storage driver... [ 110.705608] scsi4 : usb-storage 1-1:1.0 [ 110.705938] usbcore: registered new interface driver usb-storage [ 110.705945] USB Mass Storage support registered. [ 113.855485] usb 1-1: USB disconnect, device number 3 [ 118.364137] usb 1-1: new high-speed USB device number 4 using ehci_hcd [ 118.499910] usb 1-1: New USB device found, idVendor=19d2, idProduct=1018 [ 118.499924] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4 [ 118.499934] usb 1-1: Product: ZTE LTE Technologies MSM [ 118.499942] usb 1-1: Manufacturer: ZTE,Incorporated [ 118.499951] usb 1-1: SerialNumber: MF821VVDFS02 [ 118.505565] scsi5 : usb-storage 1-1:1.4 [ 118.553541] usbcore: registered new interface driver cdc_wdm [ 118.564997] qmi_wwan 1-1:1.3: cdc-wdm0: USB WDM device [ 118.565530] qmi_wwan 1-1:1.3: wwan0: register 'qmi_wwan' at usb-:00:1d.7-1, WWAN/QMI device, 0e:bd:3d:f1:d4:46 [ 118.565630] usbcore: registered new interface driver qmi_wwan [ 119.505747] scsi 5:0:0:0: CD-ROMVodafone USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0 [ 119.506426] scsi 5:0:0:0: Attached scsi generic sg1 type 5 [ 119.507764] scsi 5:0:0:1: Direct-Access Vodafone Storage 2.31 PQ: 0 ANSI: 0 [ 119.509072] sd 5:0:0:1: Attached scsi generic sg2 type 0 [ 119.51] sd 5:0:0:1: [sdb] Attached SCSI removable disk [ 119.540685] sr0: scsi-1 drive [ 119.540694] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 119.541099] sr 5:0:0:0: Attached scsi CD-ROM sr0 [ 183.808891] NET: Registered protocol family 17 -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: new device for qmi_wwan and option Vodafone/ZTE K5006Z
Am 17.08.2012 08:38, schrieb Marcel Holtmann: Hi Thomas, which German operator is giving you IPv6 over LTE? No one. I do test with the new qmi-wwan-driver: IPv4 at 2G/3G/4G (regular contract t-mobile) IPv6 at 2G/3G in a test environment by vodafone The option-driver(ppp) works for me only in IPv4 at 2G/3G Therefore LTE causes some problems in my environment: IPV4 The classic ppp-dial-in did suddenly stopped to work if an LTE-Tower was there. I had to force the modem to use UMTS/HSPA by additionally AT-commands. The final solution was the new wwan-driver. It works with 2G/3G/4G. IPV6 (2G/3G-APN) worked as long there was no LTE available. But now LTE is in Munich everywhere(t-mobile, vodafone). Yesterday I went to the underground-station ( there is no lte) and all devices connected to 3G/ipv6. Of course I am frequently asking t-mobile, eplus, O2 and vodafone for IPv6, but the answers were insufficient. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: new device for qmi_wwan and option Vodafone/ZTE K5006Z
Now I can confirm the device works via wwan-interface with ipv6 too. In detail: ipv6 works in 3G-mode. (umts/hspa) My problem was: I am more and more surrounded by LTE, and I was not able to force the device to register to the right network. LTE and IPv6 seems to be a new topic, not for the linux-driver, but for the mobileproviders. Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: new device for qmi_wwan and option Vodafone/ZTE K5006Z
The network connection is working via wwan1 , at least with IPv4. The LTE speed here with 8-16Mbit/s is limited by my contract, not the device. At the moment I have problems with IPv6, but I think this is not a problem of the device, more a problem of my apn, which may be only accessible via 3G. Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: new device for qmi_wwan and option Vodafone/ZTE K5006Z
Am Donnerstag, 2. August 2012, 21:25:49 schrieben Sie: Hi Thomas, At the moment I have problems with IPv6, but I think this is not a problem of the device, more a problem of my apn, which may be only accessible via 3G. if you are on Vodafone Germany LTE, then yes, it only gives you IPv4 for some weird reason. I have a normal contract with t-mobile germany (ipv4 only, and nothing more, every question regarding IPv6 fails because of incompetent staff) IPv4 works with 2G/3G/4G, but in 4G I forced to RFC-1918-addresses. In 2G/3G I have had the permission to use an APN with public IPs. Additionally I have got one Test-SIM from Vodafone Germany for IPv6-test- purposes. The new devices are also new for me, the tools are not fully developed yet. So I have some problems, e.g. selection of a specified network. For one device/operator I found the AT-command, but on the other device it does not work, or has to be done via qmi or whatever. I finish here. It starts to be off-topic. I hope someone adds the ID 19d2:1018 with the right subdevices to the option and qmi_wwan modules, and removes the oops. After that testing will be easier. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/3] Fixing usb_wwan NULL pointer dereferencing
I tried this patch-set today, applied to linux-next-20120727. As the RFC Fixing usb_wwan NULL pointer dereferencing set from yesterday it did help to avoid oopses while unplugging the stick. That is the good thing. But there is still a problem - wwan0 doesn't work. /dev/cdc-wdm0 answers to the cli-tool from libqmi. /dev/USBX answers to AT-commands via minicom. As with kernel 3.4 and 3.5 I use for connecting the qmi-ifupdown script provided by Bjørn some months ago. But despite VERBOSITY=true and IF_WWAN_DEBUG=1 I see nothing. The script quits without output. After that dhcpcd says only: err, wwan0: timed out warn, wwan0: using IPV4ALL address 169.254.41.53 The IPv6-variation of the scripts did not work too. Booting older kernel (3.4, 3.5 release, 3.5rc6 ) it works with all the qmi- able-devices I have. huawei E398 (3.4, 3.5) vodafone/ZTE K3565Z (3.4,3.5) vodafone/huawei K5005(3.5) O2/ZTE MF821D (3.5 + patches) For the moment linux-next does not work. Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: qmi wwan interface does not work in this version 3.5.rc7.next.20120720
Am Sonntag, 22. Juli 2012, 08:54:32 schrieben Sie: Thomas Schäfer tschae...@t-online.de wrote: with http://download.opensuse.org/repositories/Kernel:/linux- next/standard/x86_64/kernel-vanilla-3.5.rc7.next.20120720-1.1.x86_64.rpm No one of my sticks works in qmi/wwan mode anymore. The modules seems to be loaded, option and qmi_wwan, but the dial-in-skripts do nothing. While removing the stick, the system crashes. Do you have more details about this crash? netconsole is very useful if you can connect by ethernet to another pc. (That is a good idea) This happens with the Huawei E398 (supported since 3.4) dmesg [ 133.764128] usb 1-4: new high-speed USB device number 3 using ehci_hcd [ 133.899087] usb 1-4: New USB device found, idVendor=12d1, idProduct=1505 [ 133.899102] usb 1-4: New USB device strings: Mfr=3, Product=2, SerialNumber=0 [ 133.899111] usb 1-4: Product: HUAWEI Mobile [ 133.899120] usb 1-4: Manufacturer: Huawei Technologies [ 133.959452] usbcore: registered new interface driver uas [ 133.969406] Initializing USB Mass Storage driver... [ 133.970572] scsi4 : usb-storage 1-4:1.0 [ 133.970960] usbcore: registered new interface driver usb-storage [ 133.970967] USB Mass Storage support registered. [ 134.716146] usb 1-4: USB disconnect, device number 3 [ 144.604138] usb 1-4: new high-speed USB device number 4 using ehci_hcd [ 144.739362] usb 1-4: New USB device found, idVendor=12d1, idProduct=1506 [ 144.739377] usb 1-4: New USB device strings: Mfr=4, Product=3, SerialNumber=0 [ 144.739387] usb 1-4: Product: HUAWEI Mobile [ 144.739395] usb 1-4: Manufacturer: Huawei Technologies [ 144.744396] scsi5 : usb-storage 1-4:1.5 [ 144.745587] scsi6 : usb-storage 1-4:1.6 [ 144.800200] usbcore: registered new interface driver usbserial [ 144.800264] usbcore: registered new interface driver usbserial_generic [ 144.800309] USB Serial support registered for generic [ 144.800325] usbserial: USB Serial Driver core [ 144.812227] usbcore: registered new interface driver cdc_wdm [ 144.816522] usbcore: registered new interface driver option [ 144.816580] USB Serial support registered for GSM modem (1-port) [ 144.816821] option 1-4:1.0: GSM modem (1-port) converter detected [ 144.817153] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0 [ 144.817223] option 1-4:1.1: GSM modem (1-port) converter detected [ 144.822070] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB1 [ 144.822163] option 1-4:1.2: GSM modem (1-port) converter detected [ 144.822628] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB2 [ 144.843517] qmi_wwan 1-4:1.3: cdc-wdm0: USB WDM device [ 144.844156] qmi_wwan 1-4:1.3: wwan0: register 'qmi_wwan' at usb-:00:1d.7-4, WWAN/QMI device, 00:a0:c6:00:00:00 [ 144.844266] usbcore: registered new interface driver qmi_wwan [ 145.745563] scsi 5:0:0:0: CD-ROMHUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0 [ 145.746478] scsi 5:0:0:0: Attached scsi generic sg1 type 5 [ 145.749398] scsi 6:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2 [ 145.750483] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 145.751473] sd 6:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ 145.752841] sd 6:0:0:0: [sdb] Write Protect is off [ 145.752862] sd 6:0:0:0: [sdb] Mode Sense: 0f 0e 00 00 [ 145.753848] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 145.762461] sdb: sdb1 [ 145.766371] sd 6:0:0:0: [sdb] Attached SCSI removable disk [ 145.787558] sr0: scsi-1 drive [ 145.787572] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 145.789625] sr 5:0:0:0: Attached scsi CD-ROM sr0 [ 243.145559] usb 1-4: USB disconnect, device number 4 [ 243.147961] option1 ttyUSB0: option_instat_callback: error -108 [ 243.148375] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [ 243.148471] BUG: unable to handle kernel NULL pointer dereference at (null) [ 243.148508] IP: [a0468527] stop_read_write_urbs+0x37/0x80 [usb_wwan] [ 243.148556] PGD 79d60067 PUD 79d61067 PMD 0 [ 243.148590] Oops: [#1] SMP [ 243.148617] Modules linked in: sr_mod cdrom qmi_wwan usbnet option cdc_wdm usb_wwan usbserial usb_storage uas fuse af_packet ip6table_filter ip6_tables iptable_filter ip_tables x_tables tun edd cpufreq_conservative cpufreq_userspace cpufreq_powersave snd_pcm_oss snd_mixer_oss acpi_cpufreq snd_seq mperf snd_seq_device coretemp arc4 sg hp_wmi sparse_keymap uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops rtl8192ce rtl8192c_common rtlwifi joydev pcspkr microcode mac80211 i2c_i801 lpc_ich r8169 snd_hda_codec_idt cfg80211 snd_hda_intel snd_hda_codec rfkill snd_hwdep snd_pcm wmi snd_timer ac snd soundcore snd_page_alloc battery uhci_hcd i915 drm_kms_helper drm i2c_algo_bit ehci_hcd thermal usbcore video usb_common button processor thermal_sys [ 243.149007] CPU 1 [ 243.149027] Pid: 135, comm
Re: qmi wwan interface does not work in this version 3.5.rc7.next.20120720
Am Sonntag, 22. Juli 2012, 17:08:41 you wrote: Could you do a quick verification: please test if the problem disappear if you blacklist your serial driver (option?). If so, then I hope someone else can look into it. I seem to vaguely remember a similar report, but cannot find it right now. With blacklisted option the system does not crash. qmi_wwan is still loaded, but not working as expected. I will wait until the next compiled linux-next is available. Or even what comes first - the released 3.5. At the moment my time for self compiling is limited. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
qmi wwan interface does not work in this version 3.5.rc7.next.20120720
Hi, with http://download.opensuse.org/repositories/Kernel:/linux- next/standard/x86_64/kernel-vanilla-3.5.rc7.next.20120720-1.1.x86_64.rpm No one of my sticks works in qmi/wwan mode anymore. The modules seems to be loaded, option and qmi_wwan, but the dial-in-skripts do nothing. While removing the stick, the system crashes. May be it is a merge problem of the different trees, or some thing went wrong. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: infos about device ZTE MF821D 2G,3G,4G/LTE usb-modem/networkcard
Bjørn Mork wrote: USB: option: add ZTE MF821D net: qmi_wwan: add ZTE MF821D drivers/net/usb/qmi_wwan.c |9 + drivers/usb/serial/option.c |2 ++ 2 files changed, 11 insertions(+) They work well. Thanks o lot to all people involved, especially Bjørn! [ 1530.917135] usb 1-1: new high-speed USB device number 3 using ehci_hcd [ 1531.034685] usb 1-1: New USB device found, idVendor=19d2, idProduct=0325 [ 1531.034695] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4 [ 1531.034701] usb 1-1: Product: ZTE LTE Technologies MSM [ 1531.034706] usb 1-1: Manufacturer: ZTE,Corporated [ 1531.034711] usb 1-1: SerialNumber: MF821DO2_S02 [ 1531.096945] usbcore: registered new interface driver uas [ 1531.114594] Initializing USB Mass Storage driver... [ 1531.116656] scsi4 : usb-storage 1-1:1.0 [ 1531.116979] usbcore: registered new interface driver usb-storage [ 1531.116986] USB Mass Storage support registered. [ 1534.226808] usb 1-1: USB disconnect, device number 3 [ 1538.457120] usb 1-1: new high-speed USB device number 4 using ehci_hcd [ 1538.574927] usb 1-1: New USB device found, idVendor=19d2, idProduct=0326 [ 1538.574942] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4 [ 1538.574952] usb 1-1: Product: ZTE LTE Technologies MSM [ 1538.574960] usb 1-1: Manufacturer: ZTE,Corporated [ 1538.574969] usb 1-1: SerialNumber: MF821DO2_S02 [ 1538.581337] scsi5 : usb-storage 1-1:1.5 [ 1538.631291] usbcore: registered new interface driver cdc_wdm [ 1538.651999] qmi_wwan 1-1:1.0: not on our whitelist - ignored [ 1538.652495] qmi_wwan 1-1:1.1: not on our whitelist - ignored [ 1538.652636] qmi_wwan 1-1:1.2: not on our whitelist - ignored [ 1538.652692] qmi_wwan 1-1:1.3: not on our whitelist - ignored [ 1538.655984] qmi_wwan 1-1:1.4: cdc-wdm0: USB WDM device [ 1538.657758] qmi_wwan 1-1:1.4: wwan0: register 'qmi_wwan' at usb-:00:1d.7-1, Qualcomm WWAN/QMI device, 6a:db:1d:22:bf:43 [ 1538.659236] usbcore: registered new interface driver qmi_wwan [ 1538.674903] usbcore: registered new interface driver usbserial [ 1538.675590] usbcore: registered new interface driver usbserial_generic [ 1538.677078] USB Serial support registered for generic [ 1538.677108] usbserial: USB Serial Driver core [ 1538.692508] usbcore: registered new interface driver option [ 1538.692571] USB Serial support registered for GSM modem (1-port) [ 1538.693895] option 1-1:1.0: GSM modem (1-port) converter detected [ 1538.694308] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0 [ 1538.694446] option 1-1:1.1: GSM modem (1-port) converter detected [ 1538.694734] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1 [ 1538.694873] option 1-1:1.2: GSM modem (1-port) converter detected [ 1538.695192] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2 [ 1538.695328] option 1-1:1.3: GSM modem (1-port) converter detected [ 1538.695643] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3 [ 1539.586039] scsi 5:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 0 [ 1539.587142] sd 5:0:0:0: Attached scsi generic sg1 type 0 [ 1539.596767] sd 5:0:0:0: [sdb] Attached SCSI removable disk some qmi-infos: [/dev/cdc-wdm0] Device capabilities retrieved: Max TX channel rate: '5000' Max RX channel rate: '1' Data Service: 'simultaneous-cs-ps' SIM: 'supported' Networks: 'gsm, umts, lte' [/dev/cdc-wdm0] Device IDs retrieved: ESN: '0' IMEI: '861311010022209' MEID: 'unknown' [/dev/cdc-wdm0] Device revision retrieved: Revision: 'M9200B-SCAQDBZD-3.3.330115T 1 [May 06 2012 03:00:00]' IPv4 (dhcp) IPV6 (SLAAC) (tested only in IPv4only and IPv6only, without true dualstack) works also as expected and in the same way as the huawei E398/Vodafone K5005. Regards, Thomas Schäfer -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: infos about device ZTE MF821D 2G,3G,4G/LTE usb-modem/networkcard
Am 09.07.2012 10:22, schrieb Oliver Neukum: Am Sonntag, 8. Juli 2012, 13:32:42 schrieb Thomas Schäfer: Not for kernel-code, but usefull for testers/users: udev-rules/usb_modeswitch /lib/udev/rules.d/40-usb_modeswitch.rules Be careful. The expert from draisberghof told me yesterday that is only the SCSI-command for eject and can have collateral damage. His explanation is here: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=946 Could you also post lsusb -v for the card? It was part of the first mail. Now there are two copys in web: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=946 http://www.spinics.net/lists/linux-usb/msg66855.html Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: infos about device ZTE MF821D 2G,3G,4G/LTE usb-modem/networkcard
The modem works at /dev/USB2. In my point of view 19d2 0326 should/could be added to the option driver. Thomas -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
infos about device ZTE MF821D 2G,3G,4G/LTE usb-modem/networkcard
Hi, the ZTE MF821D surfstick with IDs 19d2 0325 19d2 0326 I am describing here is sold by O2 (telefonica germany) named LTE4G. It is possibly a candidate for option and qmi/wwan, or successors. First of all, some things that windows told me: diag 19d2:0326 MI00\6 nema 19d2:0326 MI01\6 at- 19d2:0326 MI02\6 modem 19d2:0326 MI03\6 ndis 19d2:0326 MI04\6 Firmware BD_O2_MF821Dv1.0.0B03 (may be there are typos included) The linux stuff is to find in the text attachments. Filenames and content should be self explaining. I am ready for further questions and/or RFT. Regards, Thomas Schäfer eject /dev/sr1 may be someone finds also the usb_modeswitch-string modprobe option echo 19d2 0326 /sys/bus/usb-serial/drivers/option1/new_id AT-interfaces are to find at /dev/ttyUSB2 /dev/ttyUSB3 Bus 001 Device 003: ID 19d2:0326 ONDA Communication S.p.A. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x19d2 ONDA Communication S.p.A. idProduct 0x0326 bcdDevice0.00 iManufacturer 3 ZTE,Corporated iProduct2 ZTE LTE Technologies MSM iSerial 4 MF821DO2_S02 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 161 bNumInterfaces 6 bConfigurationValue 1 iConfiguration 1 ZTE Configuration bmAttributes 0xc0 Self Powered MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes2 Transfer TypeBulk Synch Type
