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

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...

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,

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

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

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

Nachricht- Von: Bjørn Mork <bj...@mork.no> Gesendet: Don 3 November 2016 15:42 An: Harald Jung - ECOS Technology <harald.j...@ecos.de> CC: Dan Williams <d...@redhat.com>; ModemManager (development) <modemmanager-devel@lists.freedesktop.org> Betreff: Re: AW: 03f0:521d Hewlett-Pac

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

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

liams <d...@redhat.com>; 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

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

..@redhat.com>; ModemManager (development) manager-de...@lists.freedesktop.org> > 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,

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)_mbim_info, }, now the mbim driver binds to the interface and it gets a data connection including