Re: AW: AW: AW: 03f0:521d Hewlett-Packard again
Hi, i finally did a test with mbim and the firmware I got from HP, without success. So we will stuck with the option driver here, which will be okay for me and most of the users. Thx for you help, I never had a device which sucked more and there about 500 Notebooks with this crap in it, which should run with linux :/ regards Harald ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: AW: AW: AW: 03f0:521d Hewlett-Packard again
Hi, finally it works with the option driver. We'll need this firmware update: 12.500.00.09.1803 Rev.A(7 Mai 2015) http://h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=ob_149013_1#tab3 --- drivers/usb/serial/option.c~2014-09-06 01:34:59.0 +0200 +++ drivers/usb/serial/option.c 2014-09-16 15:50:45.0 +0200 @@ -79,6 +79,8 @@ #define OPTION_PRODUCT_ETNA_KOI_MODEM 0x7100 #define OPTION_PRODUCT_GTM380_MODEM0x7201 +#define HP_VENDOR_ID0x03F0 + #define HUAWEI_VENDOR_ID 0x12D1 #define HUAWEI_PRODUCT_E1730x140C #define HUAWEI_PRODUCT_E1750 0x1406 @@ -980,6 +982,12 @@ { USB_VENDOR_AND_INTERFACE_INFO(HUAWEI_VENDOR_ID, 0xff, 0x06, 0x7C) }, +{ USB_VENDOR_AND_INTERFACE_INFO(HP_VENDOR_ID, 0xff, 0x02, 0x01) }, +{ USB_VENDOR_AND_INTERFACE_INFO(HP_VENDOR_ID, 0xff, 0x02, 0x02) }, +{ USB_VENDOR_AND_INTERFACE_INFO(HP_VENDOR_ID, 0xff, 0x02, 0x03) }, +{ USB_VENDOR_AND_INTERFACE_INFO(HP_VENDOR_ID, 0xff, 0x02, 0x04) }, +{ USB_VENDOR_AND_INTERFACE_INFO(HP_VENDOR_ID, 0xff, 0x02, 0x05) }, + { USB_DEVICE(NOVATELWIRELESS_VENDOR_ID, NOVATELWIRELESS_PRODUCT_V640) }, { USB_DEVICE(NOVATELWIRELESS_VENDOR_ID, NOVATELWIRELESS_PRODUCT_V620) }, { USB_DEVICE(NOVATELWIRELESS_VENDOR_ID, NOVATELWIRELESS_PRODUCT_V740) }, regards Harald ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: AW: AW: AW: 03f0:521d Hewlett-Packard again
Hi, any idea whats wrong trying, with the option driver? Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0): --> 'ATD*99***1#' Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0): <-- '+CME ERROR: 4' Nov 8 17:29:39 ThinClient ModemManager[4131]: Simple connect started... Nov 8 17:29:39 ThinClient ModemManager[4131]: PIN: unspecified Nov 8 17:29:39 ThinClient ModemManager[4131]: Operator ID: unspecified Nov 8 17:29:39 ThinClient ModemManager[4131]: Allowed roaming: yes Nov 8 17:29:39 ThinClient ModemManager[4131]: APN: internet.t-d1.de Nov 8 17:29:39 ThinClient ModemManager[4131]: IP family: ipv4 Nov 8 17:29:39 ThinClient ModemManager[4131]: Allowed authentication: unspecified Nov 8 17:29:39 ThinClient ModemManager[4131]: User: tm Nov 8 17:29:39 ThinClient ModemManager[4131]: Password: tm Nov 8 17:29:39 ThinClient ModemManager[4131]: Number: *99# Nov 8 17:29:39 ThinClient ModemManager[4131]: Simple connect state (4/8): Wait to get fully enabled Nov 8 17:29:39 ThinClient ModemManager[4131]: Simple connect state (5/8): Register Nov 8 17:29:39 ThinClient ModemManager[4131]: Already registered in network '26201', automatic registration not launched... Nov 8 17:29:39 ThinClient ModemManager[4131]: Simple connect state (6/8): Bearer Nov 8 17:29:39 ThinClient ModemManager[4131]: Creating new bearer... Nov 8 17:29:39 ThinClient ModemManager[4131]: Creating Broadband bearer in broadband modem Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0) device open count is 2 (open) Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0) device open count is 1 (close) Nov 8 17:29:39 ThinClient ModemManager[4131]: New bearer created at DBus path '/org/freedesktop/ModemManager1/Bearer/0' Nov 8 17:29:39 ThinClient ModemManager[4131]: Simple connect state (7/8): Connect Nov 8 17:29:39 ThinClient ModemManager[4131]: Connecting bearer '/org/freedesktop/ModemManager1/Bearer/0' Nov 8 17:29:39 ThinClient ModemManager[4131]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) Nov 8 17:29:39 ThinClient ModemManager[4131]: Launching 3GPP connection attempt with APN 'internet.t-d1.de' Nov 8 17:29:39 ThinClient ModemManager[4131]: Looking for best CID... Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0) device open count is 2 (open) Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0): --> 'AT+CGDCONT?' Nov 8 17:29:39 ThinClient NetworkManager[4076]: [1478622579.2804] (ttyUSB0): modem state changed, 'registered' --> 'connecting' (reason: user-requested) Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0): <-- '+CGDCONT: 1,"IP","internet.t-d1.de","0.0.0.0",0,0+CGDCONT: 2,"IP","internet.t-d1.de","0.0.0.0",0,0+CGDCONT: 3,"IPV6","0.0.0.0.0.0","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0 Nov 8 17:29:39 ThinClient ModemManager[4131]: Found '9' PDP contexts Nov 8 17:29:39 ThinClient ModemManager[4131]:PDP context [cid=1] [type='ipv4'] [apn='internet.t-d1.de'] Nov 8 17:29:39 ThinClient ModemManager[4131]:PDP context [cid=2] [type='ipv4'] [apn='internet.t-d1.de'] Nov 8 17:29:39 ThinClient ModemManager[4131]:PDP context [cid=3] [type='ipv6'] [apn='0.0.0.0.0.0'] Nov 8 17:29:39 ThinClient ModemManager[4131]:PDP context [cid=4] [type='ipv4v6'] [apn='0.0.0.0.0.0.0.0.0.0'] Nov 8 17:29:39 ThinClient ModemManager[4131]:PDP context [cid=5] [type='ipv6'] [apn='0.0.0.0.0.0'] Nov 8 17:29:39 ThinClient ModemManager[4131]:PDP context [cid=6] [type='ipv4v6'] [apn='0.0.0.0.0.0.0.0.0.0'] Nov 8 17:29:39 ThinClient ModemManager[4131]:PDP context [cid=7] [type='ipv6'] [apn='0.0.0.0.0.0'] Nov 8 17:29:39 ThinClient ModemManager[4131]:PDP context [cid=8] [type='ipv4v6'] [apn='internet.t-d1.de'] Nov 8 17:29:39 ThinClient ModemManager[4131]:PDP context [cid=9] [type='ipv6'] [apn='internet.t-d1.de'] Nov 8 17:29:39 ThinClient ModemManager[4131]: Found PDP context with CID 1 and PDP type ipv4 for APN 'internet.t-d1.de' Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0) device open count is 3 (open) Nov 8 17:29:39 ThinClient ModemManager[4131]: Connection through a plain serial AT port (ttyUSB0) Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0) device open count is 4 (open) Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0) device open count is 3 (close) Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0): --> 'ATD*99***1#' Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0): <-- '+CME ERROR: 4' Nov 8 17:29:39 ThinClient ModemManager[4131]: Got failure code 4: Operation not supported Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0) device open count is 4 (open) Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0) device open count is 3 (close) Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0): --> 'AT+CEER' Nov 8 17:29:39 ThinClient ModemManager[4131]: (ttyUSB0): <-- '+CEER: "CC setup error"
Re: AW: AW: AW: 03f0:521d Hewlett-Packard again
Harald Jung writes: > cdc_mbim 1-3:2.0 wwan0: register 'cdc_mbim' at usb-:00:14.0-3, CDC > MBIM, 26:02:bf:cc:23:fc > usbcore: registered new interface driver cdc_mbim > usbnet_bh: cdc_mbim 1-3:2.0 wwan0: rxqlen 0 --> 5 > cdc_ncm_rx_verify_nth16: cdc_mbim 1-3:2.0 wwan0: invalid NTH16 > signature <0x686d636e> That's extremely useful and does explain why you are having problems: 0x686d636e is 'ncmh', indicating that the modem is running in 32bit header mode. We don't support that. But I don't understand why this happens with the driver versions you are using. We have seen this problem before, caused by a bug in the driver initialization sequence. But that was fixed ages ago. I don't remember exactly, but I do wonder if this wasn't also a symptom of the NDP ordering thing? But you've already tested that, so that's not it either. What seems very clear is that these Huawei firmwares are extremely sensitive to anything remotely unexpected from the driver, and that they default to this optional, and pretty pointless, 32bit mode. I have had enough of that. You're probably better off with some other modem. Or you can rearrange the driver initialization until it matches whatever Huawei thinks it should do. I am unable to care anymore. Let Huawei figure it out. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: AW: AW: AW: 03f0:521d Hewlett-Packard again
cdc_mbim 1-3:2.0 wwan0: register 'cdc_mbim' at usb-:00:14.0-3, CDC MBIM, 26:02:bf:cc:23:fc usbcore: registered new interface driver cdc_mbim usbnet_bh: cdc_mbim 1-3:2.0 wwan0: rxqlen 0 --> 5 cdc_ncm_rx_verify_nth16: cdc_mbim 1-3:2.0 wwan0: invalid NTH16 signature <0x686d636e> 8021q: adding VLAN 0 to HW filter on device wwan0 cdc_ncm_rx_verify_nth16: cdc_mbim 1-3:2.0 wwan0: invalid NTH16 signature <0x686d636e> cdc_ncm_rx_verify_nth16: cdc_mbim 1-3:2.0 wwan0: invalid NTH16 signature <0x686d636e> cdc_ncm_rx_verify_nth16: cdc_mbim 1-3:2.0 wwan0: invalid NTH16 signature <0x686d636e> ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: AW: AW: AW: 03f0:521d Hewlett-Packard again
Harald Jung writes: > wwan0 Link encap:Ethernet HWaddr 8E:1B:BF:B0:35:62 > inet addr:37.84.135.42 Bcast:37.84.135.43 Mask:255.255.255.252 > inet6 addr: fe80::8c1b:bfff:feb0:3562%lo/64 Scope:Link > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:41 dropped:0 overruns:0 frame:0 OK, so you got some errors counted. That's interesting because it means that was some packet on the link. Could you enable a few debugging messages and see if any of them are triggered? Something like this might do (or maybe do too much - adjust as necessary...): echo 'module cdc_ncm +fp' >/sys/kernel/debug/dynamic_debug/control echo 'module usbnet +fp' >/sys/kernel/debug/dynamic_debug/control ethtool -s wwan0 msglvl rx_err on Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: AW: AW: AW: 03f0:521d Hewlett-Packard again
Hi, sorry... after a poweroff it is the same as before: Nov 8 14:54:57 ThinClient ModemManager[2418]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered) Nov 8 14:54:57 ThinClient NetworkManager[2511]: [1478613297.3220] (ttyUSB0): modem state changed, 'connecting' --> 'registered' (reason: user-requested) Nov 8 14:54:57 ThinClient NetworkManager[2511]: [1478613297.3221] modem-broadband[ttyUSB0]: failed to connect modem: "SM deactivation", 0, "No cause information available" Nov 8 14:54:57 ThinClient NetworkManager[2511]: [1478613297.3221] device (ttyUSB0): state change: prepare -> failed (reason 'unknown') [40 120 1] Nov 8 14:54:57 ThinClient NetworkManager[2511]: [1478613297.3226] device (ttyUSB0): Activation: failed for connection 'Verbindung mit GSM' Nov 8 14:54:57 ThinClient NetworkManager[2511]: [1478613297.3237] device (ttyUSB0): state change: failed -> disconnected (reason 'none') [120 30 0] ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: AW: AW: AW: 03f0:521d Hewlett-Packard again
Hi, I've tried again with option (kernel 4.8.6, ModemManager 1.6.2), something changed. Nov 8 14:44:05 ThinClient ModemManager[2416]: Creating modem with plugin 'Generic' and '4' ports Nov 8 14:44:05 ThinClient ModemManager[2416]: Could not grab port (tty/ttyUSB2): 'Cannot add port 'tty/ttyUSB2', unhandled serial type' Nov 8 14:44:05 ThinClient ModemManager[2416]: Could not grab port (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type' Nov 8 14:44:05 ThinClient ModemManager[2416]: (ttyUSB1): port attributes not fully set Nov 8 14:44:05 ThinClient ModemManager[2416]: Modem for device at '/sys/devices/pci:00/:00:14.0/usb1/1-3' successfully created Nov 8 14:44:05 ThinClient ModemManager[2416]: couldn't load Supported Modes: 'Couldn't retrieve supported modes' Nov 8 14:44:05 ThinClient sudo: root : TTY=unknown ; PWD=/ ; USER=cdb ; COMMAND=/usr/bin/couchdb Nov 8 14:44:05 ThinClient sudo: pam_unix(sudo:session): session opened for user cdb by (uid=0) Nov 8 14:44:06 ThinClient ModemManager[2416]: Modem: state changed (unknown -> disabled) Nov 8 14:44:06 ThinClient NetworkManager[2509]: [1478612646.0090] (ttyUSB1): modem state changed, 'disabled' --> 'enabling' (reason: user preference) Nov 8 14:44:06 ThinClient ModemManager[2416]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling) Nov 8 14:44:06 ThinClient NetworkManager[2509]: [1478612646.0101] manager: (ttyUSB1): new Broadband device (/org/freedesktop/NetworkManager/Devices/7) Nov 8 14:44:06 ThinClient NetworkManager[2509]: [1478612646.0103] device (ttyUSB1): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Nov 8 14:44:06 ThinClient NetworkManager[2509]: [1478612646.0105] device (ttyUSB1): modem state 'enabling' Nov 8 14:44:06 ThinClient NetworkManager[2509]: [1478612646.0111] device (ttyUSB1): state change: unavailable -> disconnected (reason 'none') [20 30 0] Nov 8 14:44:06 ThinClient ModemManager[2416]: (ttyUSB1): port attributes not fully set Nov 8 14:44:06 ThinClient ModemManager[2416]: (ttyUSB3): port attributes not fully set Nov 8 14:44:06 ThinClient ModemManager[2416]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering) Nov 8 14:44:06 ThinClient ModemManager[2416]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home) Nov 8 14:44:07 ThinClient ModemManager[2416]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered) Nov 8 14:44:07 ThinClient NetworkManager[2509]: [1478612647.1374] (ttyUSB1): modem state changed, 'enabling' --> 'registered' (reason: user-requested) Nov 8 14:44:11 ThinClient sshd[2986]: SSH: Server;Ltype: Version;Remote: 192.168.93.23-60544;Protocol: 2.0;Client: OpenSSH_7.2p2 Ubuntu-4ubuntu2.1 Nov 8 14:44:11 ThinClient sshd[2986]: SSH: Server;Ltype: Kex;Remote: 192.168.93.23-60544;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none [preauth] Nov 8 14:44:11 ThinClient sshd[2986]: WARNING: could open open /etc/ssh/moduli (No such file or directory), using fixed modulus Nov 8 14:44:11 ThinClient sshd[2986]: userauth_pubkey: key type ssh-dss not in PubkeyAcceptedKeyTypes [preauth] Nov 8 14:44:14 ThinClient sshd[2986]: Accepted password for root from 192.168.93.23 port 60544 ssh2 Nov 8 14:44:14 ThinClient sshd[2986]: SSH: Server;Ltype: Kex;Remote: 192.168.93.23-60544;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none Nov 8 14:44:14 ThinClient sshd[2986]: WARNING: could open open /etc/ssh/moduli (No such file or directory), using fixed modulus Nov 8 14:44:14 ThinClient sshd[2994]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory Nov 8 14:44:14 ThinClient sshd[2994]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory Nov 8 14:44:32 ThinClient kernel: EXT4-fs (sdb6): re-mounted. Opts: (null) Nov 8 14:44:33 ThinClient NetworkManager[2509]: [1478612673.5284] device (ttyUSB1): Activation: starting connection 'Verbindung mit GSM' (1d6ca10b-2716-4d34-a47f-bc8d95ef52f8) Nov 8 14:44:33 ThinClient NetworkManager[2509]: [1478612673.5286] device (ttyUSB1): state change: disconnected -> prepare (reason 'none') [30 40 0] Nov 8 14:44:33 ThinClient ModemManager[2416]: Simple connect started... Nov 8 14:44:33 ThinClient ModemManager[2416]: Simple connect state (4/8): Wait to get fully enabled Nov 8 14:44:33 ThinClient ModemManager[2416]: Simple connect state (5/8): Register Nov 8 14:44:33 ThinClient ModemManager[2416]: Simple connect state (6/8): Bearer Nov 8 14:44:33 ThinClient ModemManager[2416]: Simple connect state (7/8): Connect Nov 8 14:44:33 ThinClient ModemManager[2416]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) Nov 8 14:44:33 ThinClient NetworkManager[2509]: [1478612673.5310] (ttyUSB1): modem state changed, 'registered' --> '
Re: AW: AW: AW: 03f0:521d Hewlett-Packard again
Hi, I tried again with mbim, because its a branded huawei mu736. Same results as before: ifconfig shows errors and I don't receive any bytes. option 1-3:2.2: GSM modem (1-port) converter detected usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0 usbcore: registered new interface driver cdc_ncm usbcore: registered new interface driver cdc_wdm cdc_mbim 1-3:2.0: setting rx_max = 16384 cdc_mbim 1-3:2.0: setting tx_max = 16384 cdc_mbim 1-3:2.0: NDP will be placed at end of frame for this device. cdc_mbim 1-3:2.0: cdc-wdm0: USB WDM device cdc_mbim 1-3:2.0 wwan0: register 'cdc_mbim' at usb-:00:14.0-3, CDC MBIM, 8e:1b:bf:b0:35:62 usbcore: registered new interface driver cdc_mbim 8021q: adding VLAN 0 to HW filter on device wwan0 wwan0 Link encap:Ethernet HWaddr 8E:1B:BF:B0:35:62 inet addr:37.84.135.42 Bcast:37.84.135.43 Mask:255.255.255.252 inet6 addr: fe80::8c1b:bfff:feb0:3562%lo/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:41 dropped:0 overruns:0 frame:0 TX packets:72 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:5622 (5.4 KiB) Has someone any ideas? should we go on with option, or mbim? could it help to disable ipv6? Here is a pdf doc from huawei: http://consumer.huawei.com/en/solutions/m2m-solutions/products/support/application-guides/detail/mu736-en.htm?id=17942 These are my patches so far: --- drivers/usb/serial/option.c~2014-09-06 01:34:59.0 +0200 +++ drivers/usb/serial/option.c 2014-09-16 15:50:45.0 +0200 @@ -79,6 +79,8 @@ #define OPTION_PRODUCT_ETNA_KOI_MODEM 0x7100 #define OPTION_PRODUCT_GTM380_MODEM0x7201 +#define HP_VENDOR_ID0x03F0 + #define HUAWEI_VENDOR_ID 0x12D1 #define HUAWEI_PRODUCT_E1730x140C #define HUAWEI_PRODUCT_E1750 0x1406 @@ -980,6 +982,12 @@ { USB_VENDOR_AND_INTERFACE_INFO(HUAWEI_VENDOR_ID, 0xff, 0x06, 0x7C) }, +{ USB_VENDOR_AND_INTERFACE_INFO(HP_VENDOR_ID, 0xff, 0x02, 0x01) }, +{ USB_VENDOR_AND_INTERFACE_INFO(HP_VENDOR_ID, 0xff, 0x02, 0x02) }, +{ USB_VENDOR_AND_INTERFACE_INFO(HP_VENDOR_ID, 0xff, 0x02, 0x03) }, +{ USB_VENDOR_AND_INTERFACE_INFO(HP_VENDOR_ID, 0xff, 0x02, 0x04) }, +{ USB_VENDOR_AND_INTERFACE_INFO(HP_VENDOR_ID, 0xff, 0x02, 0x05) }, + { USB_DEVICE(NOVATELWIRELESS_VENDOR_ID, NOVATELWIRELESS_PRODUCT_V640) }, { USB_DEVICE(NOVATELWIRELESS_VENDOR_ID, NOVATELWIRELESS_PRODUCT_V620) }, { USB_DEVICE(NOVATELWIRELESS_VENDOR_ID, NOVATELWIRELESS_PRODUCT_V740) }, --- drivers/usb/serial/usb_wwan.c.orig 2016-11-08 12:24:25.240201286 +0100 +++ drivers/usb/serial/usb_wwan.c 2016-11-08 12:29:53.320201286 +0100 @@ -21,6 +21,8 @@ #define DRIVER_AUTHOR "Matthias Urlichs " #define DRIVER_DESC "USB Driver for GSM modems" +#define HW_bcdUSB 0x0110 +#define HP_VENDOR_ID 0x03F0 #include #include @@ -220,6 +222,7 @@ int i; int left, todo; struct urb *this_urb = NULL;/* spurious */ + struct usb_host_endpoint *ep=NULL; int err; unsigned long flags; @@ -256,6 +259,17 @@ memcpy(this_urb->transfer_buffer, buf, todo); this_urb->transfer_buffer_length = todo; +if((HP_VENDOR_ID == port->serial->dev->descriptor.idVendor) + && (HW_bcdUSB != port->serial->dev->descriptor.bcdUSB)){ + ep = usb_pipe_endpoint(this_urb->dev, this_urb->pipe); + if(ep && (0 != this_urb->transfer_buffer_length) +&& (0 == this_urb->transfer_buffer_length % +ep->desc.wMaxPacketSize)){ +this_urb->transfer_flags |= URB_ZERO_PACKET; +} +} + + spin_lock_irqsave(&intfdata->susp_lock, flags); if (intfdata->suspended) { usb_anchor_urb(this_urb, &portdata->delayed); --- drivers/net/usb/cdc_mbim.c.orig 2016-11-08 12:33:55.430201286 +0100 +++ drivers/net/usb/cdc_mbim.c 2016-11-08 12:39:56.800201286 +0100 @@ -626,6 +626,9 @@ { USB_VENDOR_AND_INTERFACE_INFO(0x12d1, USB_CLASS_COMM, USB_CDC_SUBCLASS_MBIM, USB_CDC_PROTO_NONE), .driver_info = (unsigned long)&cdc_mbim_info_ndp_to_end, }, + { USB_VENDOR_AND_INTERFACE_INFO(0x03f0, USB_CLASS_COMM, USB_CDC_SUBCLASS_MBIM, USB_CDC_PROTO_NONE), + .driver_info = (unsigned long)&cdc_mbim_info_ndp_to_end, + }, /* default entry */ { USB_INTERFACE_INFO(USB_CLASS_COMM, USB_CDC_SUBCLASS_MBIM, USB_CDC_PROTO_NONE), .driver_info = (unsigned long)&cdc_mbim_info_zlp, regards Harald ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.fre
Re: AW: AW: 03f0:521d Hewlett-Packard again
Harald Jung - ECOS Technology writes: > I've enabled the quirk and made shure that it is active, but it > doesn't make any difference. OK, thanks for testing anyway. Then we don't have to worry about adding that device ID to the driver. > With ifconfig I see only tx packets, but no rx packets. But that also means that I'm out of ideas here. Let's try to figure out the problem with the option driver first. There is something really fishy going on there, and I suspect the issues might be related. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
AW: AW: 03f0:521d Hewlett-Packard again
just fyi: T: Bus=03 Lev=01 Prnt=01 Port=10 Cnt=01 Dev#= 5 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=02 Prot=01 MxPS=64 #Cfgs= 2 P: Vendor=03f0 ProdID=521d Rev=00.01 S: Manufacturer=Hewlett-Packard S: Product=HP hs3110 HSPA+ Mobile Broadband Device C: #Ifs= 3 Cfg#= 2 Atr=a0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim I: If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=05 Driver=option Bus 003 Device 005: ID 03f0:521d Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 bDeviceSubClass 2 bDeviceProtocol 1 bMaxPacketSize064 idVendor 0x03f0 idProduct 0x521d bcdDevice0.01 iManufacturer 5 Hewlett-Packard iProduct4 HP hs3110 HSPA+ Mobile Broadband Device iSerial 0 bNumConfigurations 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 337 bNumInterfaces 6 bConfigurationValue 1 iConfiguration 2 configuration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 bInterfaceSubClass 2 bInterfaceProtocol 1 iInterface 0 ** UNRECOGNIZED: 05 24 00 10 01 ** UNRECOGNIZED: 04 24 02 03 ** UNRECOGNIZED: 05 24 01 00 00 ** UNRECOGNIZED: 05 24 06 00 00 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 bInterfaceSubClass 2 bInterfaceProtocol 2 iInterface 0 ** UNRECOGNIZED: 05 24 00 10 01 ** UNRECOGNIZED: 04 24 02 02 ** UNRECOGNIZED: 05 24 01 00 01 ** UNRECOGNIZED: 05 24 06 01 01 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 2 bInterfaceClass 255 bInterfaceSubClass 2 bInterfaceProtocol 3 iInterface 0 ** UNRECOGNIZED: 05 24 00 10 01 ** UNRECOGNIZED: 04 24 02 02 ** UNRECOGNIZED: 05 24 01 00 02 ** UNRECOGNIZED: 05 24 06 02 02 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInt
AW: AW: 03f0:521d Hewlett-Packard again
Hi, I've enabled the quirk and made shure that it is active, but it doesn't make any difference. With ifconfig I see only tx packets, but no rx packets. regards Harald -Ursprüngliche Nachricht- Von: Bjørn Mork Gesendet: Don 3 November 2016 15:42 An: Harald Jung - ECOS Technology CC: Dan Williams ; ModemManager (development) Betreff: Re: AW: 03f0:521d Hewlett-Packard again Harald Jung - ECOS Technology writes: > Hi, > > > > now i've got two notebooks with this mobile device, the older one works with > the option driver, the newer one not. Cannot explain that. The USB descriptors look identical for all serial functions AFAICS. The only noticable difference between the two devices is the CCID function. I assume that is a SIM interface? Don't think it matters in any way. > I've tried both with mbim, it works until the ip is set to the wwan > interface, but no network connection is possible. This might be related to the /sys/class/net/[iface]/cdc_ncm/ndp_to_end quirk thingy. AFAIR, we ended up enabling that by default for all Huawei devices recently. But that doesn't work for the HP OEMs using HPs vendor ID. Verify that you have the file and that it shows the expected default value 'N': grep . /sys/class/net/*/cdc_ncm/ndp_to_end Then try to enable the quirk and see if that makes a difference: echo Y > /sys/class/net/[iface]/cdc_ncm/ndp_to_end If it does, then I guess we need to add this HP device ID to the quirk list. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel