Hi Aleksander,
After upgrading to the latest version, I am getting a build
error, Couldn’t find "libqmi-glib" error.
Thanks
Rakesh
-Original Message-
From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
Sent: Friday, April 08, 2016 4:06 AM
To: Seethamsetty, Rake
On Fri, Apr 8, 2016 at 4:55 PM, Daniele Palmas wrote:
> 2016-04-08 16:42 GMT+02:00 Aleksander Morgado :
>> When we were completing tasks in idle, the logic was like this:
>>
>> * Schedule task completion in idle
>> * self->priv->task = NULL
>> * (idle) Task completion callback called
>>
>> This
On Fri, Apr 8, 2016 at 3:59 PM, Diego López Montes wrote:
>>> QMI:
>>> flags = "indication"
>>> transaction = 0
>>> tlv_length = 21
>>> message = "Packet Service Status" (0x0022)
>>> TLV:
>>> type = "Connection Status" (0x01)
>>> length
Hi Aleksander,
2016-04-08 16:42 GMT+02:00 Aleksander Morgado :
> When we were completing tasks in idle, the logic was like this:
>
> * Schedule task completion in idle
> * self->priv->task = NULL
> * (idle) Task completion callback called
>
> This meant that the self->priv->task was always set
When we were completing tasks in idle, the logic was like this:
* Schedule task completion in idle
* self->priv->task = NULL
* (idle) Task completion callback called
This meant that the self->priv->task was always set to NULL before the
completion callback was called, which is what we wanted a
Hi Aleksander,
I hope that this is the relevant fragment. Caught it's not easy,
verbosity is too detailed.
ModemManager[21502]: [/dev/cdc-wdm0] Received message (translated)...
>> QMUX:
>> length = 50
>> flags = 0x80
>> service = "nas"
>> client = 3
>> QMI:
On Fri, Apr 8, 2016 at 3:35 PM, Daniele Palmas wrote:
>> All these could very well be due to the issue fixed in this commit:
>> https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8fee9a99f065b845bd0a9915c8777e6ac60a67b2
>>
>> That commit is 1.6-rc2 already, and you say the issue is
2016-04-08 15:13 GMT+02:00 Aleksander Morgado :
> On Fri, Apr 8, 2016 at 2:20 PM, Daniele Palmas wrote:
>> the error seems to appear also with no modem attached.
>>
>> I have the following logs:
>>
>> commit: 1939c5ace50240127276efacec5c7f166483bb79
>> no modem attached
>> http://pastebin.com/Lysi
On Fri, Apr 8, 2016 at 2:20 PM, Daniele Palmas wrote:
> the error seems to appear also with no modem attached.
>
> I have the following logs:
>
> commit: 1939c5ace50240127276efacec5c7f166483bb79
> no modem attached
> http://pastebin.com/LysiMzLz
>
> commit: 1939c5ace50240127276efacec5c7f166483bb79
Hi Aleksander,
2016-04-08 13:11 GMT+02:00 Aleksander Morgado :
> On Thu, Apr 7, 2016 at 12:57 PM, Daniele Palmas wrote:
>> The error seems to be triggered by this:
>>
>> ModemManagere[30896]: [1460023605.770238]
>> [mm-port-probe-at.c:43] mm_port_probe_response_processor_is_at():
>> Parsing AT g
Hey,
>
> sorry for the long -email, but I got stuck again in another problem: the
> re-probe does not start when the ModemManager is in "SIM missing failed
> state" and mm_base_modem_set_valid(..., false) is called.
>
> The current, modified, initialization code has got the following new steps:
>
>
On Thu, Apr 7, 2016 at 12:57 PM, Daniele Palmas wrote:
> The error seems to be triggered by this:
>
> ModemManagere[30896]: [1460023605.770238]
> [mm-port-probe-at.c:43] mm_port_probe_response_processor_is_at():
> Parsing AT got: 'Sending command failed: 'Resource temporarily
> unavailable''
>
>
On Wed, Apr 6, 2016 at 4:54 PM, Dan Williams wrote:
>
>> What do you guys think? I believe the Telit plugin has the same
>> 'issue', it doesn't explicitly support QMI and falls back to the
>> generic plugin for the LN920.
>
> Plugin-specific handling for QMI/MBIM is fine with me. I can't get to
>
Hoola Diego,
>
> I’m dealing with a Sierra Wireless MC7354. I’m testing it on coverage limits
> (removing antenna) on UTMS. In normal operation, RRC_STATE moves between
> CELL_DCH, CELL_FACH and CONNECTING while ModemManager.Modem.state keeps
> CONNECTED. Sometimes the modem reach DISCONNECTED st
On Thu, Apr 7, 2016 at 10:09 PM, Seethamsetty, Rakesh
wrote:
>I am bringing up a Intel Modem XMM7160 on yocto, after starting
> my modem maanger I get the error as CDC_WDM0 unsupported, log attached.
We've seen that sometimes the first mbim responses to the open command
need more wait
15 matches
Mail list logo