On Thu, Dec 21, 2017 at 2:41 PM, Aleksander Morgado
wrote:
>
>
>
> On Thu, Dec 21, 2017 at 2:15 PM, Piotr Figiel wrote:
>>
>> Hi,
>> I dug into the issue a little bit deeper and I think I found the
>> source of the problem.
>> The connection state machine seem to enter a dead end in
>> mm-beare
On Thu, Dec 21, 2017 at 2:15 PM, Piotr Figiel wrote:
> Hi,
> I dug into the issue a little bit deeper and I think I found the
> source of the problem.
> The connection state machine seem to enter a dead end in
> mm-bearer-qmi.c on CONNECT_STEP_ENABLE_INDICATIONS_IPV4 case for
> libqmi < 1.18.0.
Hi,
I dug into the issue a little bit deeper and I think I found the
source of the problem.
The connection state machine seem to enter a dead end in
mm-bearer-qmi.c on CONNECT_STEP_ENABLE_INDICATIONS_IPV4 case for
libqmi < 1.18.0.
With this patch it works, you can include it if you find it OK, t
Hi Dan,
thanks for looking at this.
2017-12-20 18:11 GMT+01:00 Dan Williams :
> Can you change MM to log debug info?
> mmcli --set-logging=DEBUG
>
> and then try a connection attempt. That will hopefully yield more
> information, including the QMI protocol dumps so we can see what's
> really hap
