Problems with Sierra Wireless EM7305

2016-07-13 Thread Harald Jung - ECOS Technology
Hi,



when I try to run the modem with qmi support, nm-applet askes for the pin.
The SIM accepts the PIN and after a while the motdem resets itself and 
disappears from the usb bus, to show up after 1-2 seconds again.

If I do it to often, the Modem changes its product_id to 9040 and has only 1 
Interface (udev loads qcserial) and only 1 bConfiguration Value.

And it doesn't work at all, the only thing which helps is to remove all power 
supply.

After that it shows up with the product_id 9041 again.

Kernel Version is 4.5.7



When I Try to run the modem in mbim mode, I'll get this messages:



Jul 12 16:33:37 ThinClient kernel: usbcore: registered new interface driver 
cdc_ncm
Jul 12 16:33:38 ThinClient kernel: usbcore: registered new interface driver 
cdc_wdm
Jul 12 16:33:38 ThinClient kernel: cdc_mbim 3-11:2.12: cdc-wdm0: USB WDM device
Jul 12 16:33:38 ThinClient kernel: cdc_mbim 3-11:2.12 wwan0: register 
'cdc_mbim' at usb-:00:14.0-11, CDC MBIM, a6:b5:9c:ec:6b:b5
Jul 12 16:33:38 ThinClient kernel: usbcore: registered new interface driver 
cdc_mbim
Jul 12 16:33:38 ThinClient ModemManager[2100]: opening device...
Jul 12 16:33:38 ThinClient ModemManager[2100]: cannot connect to proxy: Could 
not connect: Connection refused
Jul 12 16:33:38 ThinClient ModemManager[2100]: spawning new mbim-proxy (try 
1)...
Jul 12 16:33:38 ThinClient ModemManager[2100]: [/dev/cdc-wdm0] Read max control 
message size from descriptors file: 4096
Jul 12 16:33:38 ThinClient ModemManager[2100]: [/dev/cdc-wdm0] unexpected port 
hangup!
Jul 12 16:34:08 ThinClient ModemManager[2100]: proxy configuration failed: 
closed
Jul 12 16:34:08 ThinClient ModemManager[2100]:  Creating modem with 
plugin 'Generic' and '2' ports 
Jul 12 16:34:08 ThinClient ModemManager[2100]:  Could not grab port 
(usbmisc/cdc-wdm0): 'Cannot add port 'usbmisc/cdc-wdm0', unsupported' 
Jul 12 16:34:08 ThinClient ModemManager[2100]:  Couldn't create modem for 
device at '/sys/devices/pci:00/:00:14.0/usb3/3-11': Failed to find 
primary AT port 
Jul 12 16:37:17 ThinClient ModemManager[2100]:  Caught signal, shutting 
down... 
Jul 12 16:37:17 ThinClient NetworkManager[2193]:  ModemManager 
disappeared from bus
Jul 12 16:37:17 ThinClient ModemManager[2100]:  ModemManager is shut down 
Jul 12 16:37:17 ThinClient ModemManager[4512]:  ModemManager (version 
1.4.12) starting in system bus... 
Jul 12 16:37:17 ThinClient NetworkManager[2193]:  ModemManager 
disappeared from bus
Jul 12 16:37:17 ThinClient NetworkManager[2193]:  ModemManager available 
in the bus
Jul 12 16:37:17 ThinClient ModemManager[4512]: opening device...
Jul 12 16:37:17 ThinClient ModemManager[4512]: cannot connect to proxy: Could 
not connect: Connection refused
Jul 12 16:37:17 ThinClient ModemManager[4512]: spawning new mbim-proxy (try 
1)...
Jul 12 16:37:17 ThinClient ModemManager[4512]: [/dev/cdc-wdm0] Read max control 
message size from descriptors file: 4096
Jul 12 16:37:17 ThinClient ModemManager[4512]: [/dev/cdc-wdm0] unexpected port 
hangup!
Jul 12 16:37:19 ThinClient ModemManager[4512]:  Couldn't find support for 
device at '/sys/devices/pci:00/:00:19.0': not supported by any plugin 
Jul 12 16:37:19 ThinClient ModemManager[4512]:  Couldn't find support for 
device at '/sys/devices/pci:00/:00:1c.5/:02:00.0': not supported by 
any plugin 
Jul 12 16:37:35 ThinClient ModemManager[4512]:  Creating modem with 
plugin 'Generic' and '1' ports 
Jul 12 16:37:35 ThinClient ModemManager[4512]:  Could not grab port 
(tty/ttyS0): 'Cannot add port 'tty/ttyS0', unhandled serial type' 
Jul 12 16:37:35 ThinClient ModemManager[4512]:  Couldn't create modem for 
device at '/sys/devices/pci:00/:00:16.3': Failed to find primary AT 
port 
Jul 12 16:37:47 ThinClient ModemManager[4512]: proxy configuration failed: 
closed
Jul 12 16:37:47 ThinClient ModemManager[4512]:  Creating modem with 
plugin 'Generic' and '2' ports 
Jul 12 16:37:47 ThinClient ModemManager[4512]:  Could not grab port 
(usbmisc/cdc-wdm0): 'Cannot add port 'usbmisc/cdc-wdm0', unsupported' 
Jul 12 16:37:47 ThinClient ModemManager[4512]:  Couldn't create modem for 
device at '/sys/devices/pci:00/:00:14.0/usb3/3-11': Failed to find 
primary AT port



regards

Harald



Device Info:



T: Bus=03 Lev=01 Prnt=01 Port=10 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 2
P: Vendor=1199 ProdID=9041 Rev=00.06
S: Manufacturer=Sierra Wireless, Incorporated
S: Product=EM7305
C: #Ifs= 2 Cfg#= 2 Atr=e0 MxPwr=500mA
I: If#=12 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
I: If#=13 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim



Bus 003 Device 004: ID 1199:9041  
Device Descriptor:
  bLength    18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass    0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0    64
  idVendor   0x1199 
  idProduct  0x9041 
  bcdDevice   

AW: 03f0:521d Hewlett-Packard again

2016-09-21 Thread Harald Jung - ECOS Technology
I've put this entry in the usb_device_id mbim_devs struct:



 { USB_VENDOR_AND_INTERFACE_INFO(0x03f0, USB_CLASS_COMM, USB_CDC_SUBCLASS_MBIM, 
USB_CDC_PROTO_NONE),
 .driver_info = (unsigned long)&cdc_mbim_info,
 },



now the mbim driver binds to the interface and it gets a data connection 
including the IP configuration. 



But I can't establish any connection to the internet. I can't even resolve a 
host against the DNS I've got by Networkmanager. 
I see only tx packets but no rx packets. 





Sep 21 15:00:20 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: unavailable -> disconnected (reason 'none') [20 30 0]
Sep 21 15:00:21 ThinClient ModemManager[7986]:  Modem 
/org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed 
(unknown -> registering) 
Sep 21 15:00:21 ThinClient ModemManager[7986]:  Modem 
/org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed 
(registering -> home) 
Sep 21 15:00:21 ThinClient ModemManager[7986]:  Modem 
/org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered) 
Sep 21 15:00:21 ThinClient NetworkManager[2386]:  (cdc-wdm0): modem state 
changed, 'enabling' --> 'registered' (reason: user-requested) 
Sep 21 15:00:33 ThinClient NetworkManager[2386]:  (cdc-wdm0): Activation: 
starting connection 'T-Mobile(Telekom) Vorgabe' 
(d0ccfb13-fc0a-4fa2-8b75-40ea2deeb114)
Sep 21 15:00:33 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Simple connect started... 
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Simple connect state 
(4/8): Wait to get fully enabled 
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Simple connect state 
(5/8): Register 
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Simple connect state 
(6/8): Bearer 
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Simple connect state 
(7/8): Connect 
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Modem 
/org/freedesktop/ModemManager1/Modem/0: state changed (registered -> 
connecting) 
Sep 21 15:00:33 ThinClient NetworkManager[2386]:  (cdc-wdm0): modem state 
changed, 'registered' --> 'connecting' (reason: user-requested) 
Sep 21 15:00:35 ThinClient ModemManager[7986]:  Modem 
/org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) 
Sep 21 15:00:35 ThinClient ModemManager[7986]:  Simple connect state 
(8/8): All done 
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): modem state 
changed, 'connecting' --> 'connected' (reason: user-requested) 
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: prepare -> config (reason 'none') [40 50 0]
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: config -> ip-config (reason 'none') [50 70 0]
Sep 21 15:00:35 ThinClient kernel: mbim:rx fixup
Sep 21 15:00:35 ThinClient kernel: 8021q: adding VLAN 0 to HW filter on device 
wwan0
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): IPv4 static 
configuration:
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  address 37.80.216.78/30
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  gateway 37.80.216.77
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  DNS 10.74.210.210
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  DNS 10.74.210.211
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  [1474462835.279208] 
[/usr/bbsrc/bbbuild/dev-cdb3/std/portage/net-misc/networkmanager-1.0.10-r1/work/NetworkManager-1.0.10/src/devices/nm-device.c:4
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: ip-config -> ip-check (reason 'none') [70 80 0]
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: ip-check -> secondaries (reason 'none') [80 90 0]
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  Writing DNS information 
to /sbin/resolvconf
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): Activation: 
successful, device activated.









Harald







___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


AW: 03f0:521d Hewlett-Packard again

2016-09-22 Thread Harald Jung - ECOS Technology
Hi,

 
how can i tell Networkmanager to setup the IP Parameters with dhcp?
I had a problem like this with another huawei device.

 
Harald

 




-Ursprüngliche Nachricht-
Von: Harald Jung - ECOS Technology 
Gesendet: Mit 21 September 2016 15:12
An: Bjørn Mork 
CC: Dan Williams ; ModemManager (development) 

Betreff: AW: 03f0:521d Hewlett-Packard again

 

I've put this entry in the usb_device_id mbim_devs struct:



 { USB_VENDOR_AND_INTERFACE_INFO(0x03f0, USB_CLASS_COMM, USB_CDC_SUBCLASS_MBIM, 
USB_CDC_PROTO_NONE),
 .driver_info = (unsigned long)&cdc_mbim_info,
 },



now the mbim driver binds to the interface and it gets a data connection 
including the IP configuration. 



But I can't establish any connection to the internet. I can't even resolve a 
host against the DNS I've got by Networkmanager. 
I see only tx packets but no rx packets. 





Sep 21 15:00:20 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: unavailable -> disconnected (reason 'none') [20 30 0]
Sep 21 15:00:21 ThinClient ModemManager[7986]:  Modem 
/org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed 
(unknown -> registering) 
Sep 21 15:00:21 ThinClient ModemManager[7986]:  Modem 
/org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed 
(registering -> home) 
Sep 21 15:00:21 ThinClient ModemManager[7986]:  Modem 
/org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered) 
Sep 21 15:00:21 ThinClient NetworkManager[2386]:  (cdc-wdm0): modem state 
changed, 'enabling' --> 'registered' (reason: user-requested) 
Sep 21 15:00:33 ThinClient NetworkManager[2386]:  (cdc-wdm0): Activation: 
starting connection 'T-Mobile(Telekom) Vorgabe' 
(d0ccfb13-fc0a-4fa2-8b75-40ea2deeb114)
Sep 21 15:00:33 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Simple connect started... 
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Simple connect state 
(4/8): Wait to get fully enabled 
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Simple connect state 
(5/8): Register 
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Simple connect state 
(6/8): Bearer 
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Simple connect state 
(7/8): Connect 
Sep 21 15:00:33 ThinClient ModemManager[7986]:  Modem 
/org/freedesktop/ModemManager1/Modem/0: state changed (registered -> 
connecting) 
Sep 21 15:00:33 ThinClient NetworkManager[2386]:  (cdc-wdm0): modem state 
changed, 'registered' --> 'connecting' (reason: user-requested) 
Sep 21 15:00:35 ThinClient ModemManager[7986]:  Modem 
/org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) 
Sep 21 15:00:35 ThinClient ModemManager[7986]:  Simple connect state 
(8/8): All done 
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): modem state 
changed, 'connecting' --> 'connected' (reason: user-requested) 
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: prepare -> config (reason 'none') [40 50 0]
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: config -> ip-config (reason 'none') [50 70 0]
Sep 21 15:00:35 ThinClient kernel: mbim:rx fixup
Sep 21 15:00:35 ThinClient kernel: 8021q: adding VLAN 0 to HW filter on device 
wwan0
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): IPv4 static 
configuration:
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  address 37.80.216.78/30
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  gateway 37.80.216.77
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  DNS 10.74.210.210
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  DNS 10.74.210.211
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  [1474462835.279208] 
[/usr/bbsrc/bbbuild/dev-cdb3/std/portage/net-misc/networkmanager-1.0.10-r1/work/NetworkManager-1.0.10/src/devices/nm-device.c:4
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: ip-config -> ip-check (reason 'none') [70 80 0]
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: ip-check -> secondaries (reason 'none') [80 90 0]
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): device 
state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  Writing DNS information 
to /sbin/resolvconf
Sep 21 15:00:35 ThinClient NetworkManager[2386]:  (cdc-wdm0): Activation: 
successful, device activated.









Harald








___

ModemManager-devel mailing list

ModemManager-devel@lists.freedesktop.org

https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel



___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


AW: 03f0:521d Hewlett-Packard again

2016-11-03 Thread Harald Jung - ECOS Technology
rnateSetting   0
  bNumEndpoints   0
  bInterfaceClass10 
  bInterfaceSubClass  0 
  bInterfaceProtocol  2 
  iInterface  0 
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   1
  bNumEndpoints   2
  bInterfaceClass10 
  bInterfaceSubClass  0 
  bInterfaceProtocol  2 
  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 
  bInterfaceSubClass  2 
  bInterfaceProtocol  5 
  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 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
Device Qualifier (for other device speed):
  bLength10
  bDescriptorType 6
  bcdUSB   2.00
  bDeviceClass  255 
  bDeviceSubClass 2 
  bDeviceProtocol 1 
  bMaxPacketSize064
  bNumConfigurations  1
Device Status: 0x
  (Bus Powered)





regards

Harald





-Ursprüngliche Nachricht-----
Von: Harald Jung - ECOS Technology 
Gesendet: Mit 21 September 2016 00:37
An: Bjørn Mork 
CC: Dan Williams ; ModemManager (development) 

Betreff: Re: 03f0:521d Hewlett-Packard again


may I miss something?
dmesg shows nothing,too
ThinClient,initial:root:˜ $ echo "7 7 7 7" > /proc/sys/kernel/printk
ThinClient,initial:root:˜ $ echo "module cdc_ncm +fp" 
 >/sys/kernel/debug/dynamic_debug/control
ThinClient,initial:root:˜ $ echo "module cdc_mbim +fp" 
 >/sys/kernel/debug/dynamic_debug/control
ThinClient,initial:root:˜ $ echo -n "1-3:2.0" > 
/sys/bus/usb/drivers/cdc_mbim/bind
bash: echo: write error: No such device

Harald

On 20.09.2016 19:55, Bjørn Mork wrote:
> Harald Jung  writes:
>
>> Hi,
>>
>> no idea what I'm doing wrong here:
>>
>> cat /sys/bus/usb/devices/1-3/product
>> HP hs3110 HSPA+ Mobile Broadband Device
>> ls /sys/bus/usb/devices/ |grep 1-3
>> 1-3
>> 1-3:2.0
>> 1-3:2.1
>> 1-3:2.2
>> echo -n "1-3:2.0" > /sys/bus/usb/drivers/cdc_mbim/bind
>> bash: echo: write error: No such device
> You're not doing anything wrong.  That error is consistent with the
> probing failure.  Do you have dynamic debugging enabled?  If so, then
> mount debugfs, do
>
>echo module cdc_ncm +fp >/sys/kernel/debug/dynamic_debug/control
>
>
> and then repeat the manual bind.  Hoping this will produce a more
> specific debug message.
>
>
>
>
> Bjørn


___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


AW: AW: 03f0:521d Hewlett-Packard again

2016-11-04 Thread Harald Jung - ECOS Technology
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


AW: AW: 03f0:521d Hewlett-Packard again

2016-11-04 Thread Harald Jung - ECOS Technology
  ** UNRECOGNIZED:  04 24 02 02
  ** UNRECOGNIZED:  05 24 01 00 02
  ** UNRECOGNIZED:  05 24 06 02 02
  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
Device Qualifier (for other device speed):
  bLength10
  bDescriptorType 6
  bcdUSB   2.00
  bDeviceClass  255 
  bDeviceSubClass 2 
  bDeviceProtocol 1 
  bMaxPacketSize064
  bNumConfigurations  1
Device Status: 0x
  (Bus Powered)








-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

___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel