ME936 MBIM

[Aleksander Morgado]

On Fri, Jul 22, 2016 at 10:33 AM, Sebastian Sjoholm
<sebastian.sjoholm at gmail.com> wrote:
>
> root at B19:~# mbim-network /dev/cdc-wdm0 start
> /usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
> /usr/bin/mbim-network: 138: /usr/bin/mbim-network: [[: not found
> Loading profile at /etc/mbim-network.conf...
>     APN: ran3.dynamic.com
>     APN auth protocol: unset
>     APN user: unset
>     APN password: unset
>     mbim-proxy: no
> 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: '235913000400239' SIM ICCID:
> '89211380007175100017' Ready info: 'unknown' Telephone numbers: (0)
> 'unknown' [/dev/cdc-wdm0] Session not closed: TRID: '3'
> Saving state at /tmp/mbim-network-state-cdc-wdm0... (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: 'umts,
> hsdpa, hsupa, custom' Current cellular class: 'gsm' Provider ID: '23591'
> Provider name: 'WMR' Roaming text: 'unknown' Registration flags:
> 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID:
> '4'
> Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 4)
> Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0
> --attach-packet-service --no-open=4 --no-close '...
> Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 5)
> Starting network with 'mbimcli -d /dev/cdc-wdm0
> --connect=apn='ran3.dynamic.com' --no-open=5 --no-close '...
> Network started successfully
> Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7)
>
> Network seems to have started, but now when I check status I get transaction
> timeout, actually I get transaction timeout on all MBIM commands after this.

You could try to use the mbim-proxy setup to see if we're really
seeing transaction timeouts triggered by the device.

E.g. set PROXY=yes in the /etc/mbim-network.conf profile file; and
then run the mbim-proxy yourself before the mbim-network commands
(path to mbim-proxy depends on your distro or your configure flags):
$ sudo /usr/libexec/mbim-proxy --verbose


-- 
Aleksander
https://aleksander.es