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
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.
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...
N
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
> signatu
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
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
>
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, '
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
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 driv
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 packe
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 wit
ung - 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 new
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 betw
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-P
at's *always* static addressing
using IP information reported from the MBIM spec calls to the device.
Dan
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)
Betre
MBIM spec calls to the device.
Dan
>
> 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) manager-d
; 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,
},
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
includ
Harald Jung writes:
> 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"
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_debu
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
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
On 20.09.2016 13:06,
Harald Jung writes:
> Hi,
>
> to be shure i removed usb_modeswitch from the last build and i added
> an udev rule, that the bConfiguration switch happened before
> modemmanager was started.
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore:
Hi,
to be shure i removed usb_modeswitch from the last build and i added an
udev rule, that the bConfiguration switch happened before modemmanager
was started.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
I was able to switch it to Configuration 2 but the mbim driver didn't
grab the device.
On 20.09.2016 04:26, Sebastian Sjoholm wrote:
I use following for Huawei ME936 to force it to MBIM;
ACTION=="add|change", SUBSYSTEM=="usb", \
ENV{DEVTYPE}=="usb_device", \
ATTR{idVendor}=="12d1", ATTR{idProd
> On Sep 19, 2016, at 23:14 , Harald Jung wrote:
>
> I don't think that this device is triggered by any udev rule, so
> usb_modeswitch won't be triggered
>
> grep 03f0 40-usb_modeswitch.rules *
> 40-usb_modeswitch.rules:ATTR{idVendor}=="03f0", ATTR{idProduct}=="002a",
> RUN+="usb_modeswitch '
I don't think that this device is triggered by any udev rule, so
usb_modeswitch won't be triggered
grep 03f0 40-usb_modeswitch.rules *
40-usb_modeswitch.rules:ATTR{idVendor}=="03f0", ATTR{idProduct}=="002a",
RUN+="usb_modeswitch '%b/%k'"
40-usb_modeswitch.rules:ATTR{idVendor}=="03f0", ATTR{idPr
On Mon, 2016-09-19 at 22:06 +0200, Harald Jung wrote:
> At this point i have no idea why cdc_mbim doen't grab the device.
> Just that it is loaded but i think it is just loaded by cdc_ncm
> dependencies.
Check usb_modeswitch/usb_modeswitch_dispatcher. If you move them out
of the way, does that h
At this point i have no idea why cdc_mbim doen't grab the device.
Just that it is loaded but i think it is just loaded by cdc_ncm
dependencies.
On 19.09.2016 22:03, Bjørn Mork wrote:
Harald Jung writes:
echo "03f0 521d" > /sys/bus/usb/drivers/cdc_mbim/new_id
had no effect
And it should no
Harald Jung writes:
> echo "03f0 521d" > /sys/bus/usb/drivers/cdc_mbim/new_id
> had no effect
And it should not. The driver will match the MBIM class.
> usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0
> usbcore: registered new interface driver cdc_ncm
> usbcore: registered new in
Hi,
echo "03f0 521d" > /sys/bus/usb/drivers/cdc_mbim/new_id
had no effect
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
usbcore: registered new interface driver cdc_mbim
T: Bus=01
Harald Jung writes:
> Hi,
>
> two years ago we had some trouble with the HP hs3110 HSPA+
>
> https://lists.freedesktop.org/archives/modemmanager-devel/2014-September/001553.html
>
> The last time the job was done to patch the option driver, this doesn'
> work with the variant of the moden i have
Hi,
two years ago we had some trouble with the HP hs3110 HSPA+
https://lists.freedesktop.org/archives/modemmanager-devel/2014-September/001553.html
The last time the job was done to patch the option driver, this doesn'
work with the variant of the moden i have in another HP notebook.
My last t
33 matches
Mail list logo
