Hi,
I’m observing that NetworkManager (v1.20.2) does not recognise the MTU (=1360)
exposed by the ModemManager’s (v1.10.6) bearer object and instead uses some
default value (=1500). This seems to lead to issues which are fixed when
manually setting the MTU to a lower value. When checking the
Hey David,
> > > >
> > > > With all enable it only shows the 3GPP info with mmcli -m 0
> > > > --loction-get
> > >
> > > Daniele, any idea why we're not receiving NMEA traces via QMI
> > > indications in this case? Do you see something wrong in the sequence
> > > to enable the GNSS location
On Thu, May 7, 2020 at 4:23 PM Enrico Mioso wrote:
>
> Oh, sorry. It makes sense due to the way C structs work, so i may use
> struct _AvModem {
You still need to define the parent GObject here.
>MMObject mmobject;
>/* other members */
> };
>
> Still, if all is OK I should be able to
Hey!
>
> (process:45799): GLib-GObject-WARNING **: 15:52:57.565: specified instance
> size for type 'AvModem' is smaller than the parent type's 'GObject' instance
> size
>
The first element in the AvModem struct that you define must be equal
to the parent object the new type inherits from. In
Hey Daniele,
> > > > Then we need to debug why we were not able to get any LOC indication
> > > > with NMEA traces in David's setup.
> > >
> > > > David, could you retry to setup the location using the QMI protocol
> > > > (i.e. without your changes) but enabling both "nmea" and "raw"
> > > >
Oh, sorry. It makes sense due to the way C structs work, so i may use
struct _AvModem {
MMObject mmobject;
/* other members */
};
Still, if all is OK I should be able to do something like:
mm_object_get_modem(MM_OBJECT(m));
or am I mistaken?
currently, this fails...
thanks again,
Enrico
Hi!!
The relevant code is in NetworkManager/src/devices/wwan . In my impression NM
doesn't ask MM for the MTU, using it's own (default) values for that.
Note that it's only my impression from a superficial look.
Hence, assuming I am right, I guess this isn't a MM related issue.
Enrico
On
Ok, now things are a little bit clearer. However, when running my test code I
face the issue:
Creating object:
(process:45799): GLib-GObject-WARNING **: 15:52:57.565: specified instance size
for type 'AvModem' is smaller than the parent type's 'GObject' instance size
(process:45799):
thank you very very much!! Really.
Enrico
On Thu, 7 May 2020, Aleksander Morgado wrote:
Date: Thu, 7 May 2020 09:34:46
From: Aleksander Morgado
To: Enrico Mioso
Cc: "ModemManager (development)" ,
marco.perini1...@gmail.com
Subject: Re: Correct connection sequence to maximize chances of
Hi Aleksander and David,
Il giorno mar 5 mag 2020 alle ore 17:14 Aleksander Morgado
ha scritto:
>
> Hey Daniele & David
>
> > > Then we need to debug why we were not able to get any LOC indication
> > > with NMEA traces in David's setup.
> >
> > > David, could you retry to setup the location
Hey!
First I'd like to say what a great project! I've got numerous customers
> using this now, and am impressed by the capabilities and breadth of support
> for modems.
>
> I've run into an issue with a customer who is using ModemManager with a
> u-blox modem, and we're seeing a hangup that is
Hey!
> Sorry for deleting the quoted text every time, but without doing so, answers
> may result complicated to read confortably for me.
>
> So, in the end I came to the conclusion that using GObjects is probably the
> best course of cation :)
>
> So I am studying the GLib GObjects page for
12 matches
Mail list logo
