Hello!
Could you help us on this strange issue?
W dniu pt., 11.01.2019 o 10:24 Przemyslaw Galazka
napisał(a):
> Hello,
>
> we have a standard generic modem (Quactel M66, one uart working in
> transparent mode).
> MM is working just fine - registering and connecting to the home network.
> When N
Quoting matthew stanger :
For 'Type=dbus' services, which most of the distro's use in MM's service
file. Systemd will consider the unit started immediately after the main
service process has been forked off and the service has acquired a name on
the D-Bus bus, as configured by 'BusName='.
I did
>
> But how does systemd measure the "boot time" of each? Is it only the
> time needed by the daemon to be exposed in DBus? Or what?
For 'Type=dbus' services, which most of the distro's use in MM's service
file. Systemd will consider the unit started immediately after the main
service process has
> > on my embedded system, "systemd-analyze blame" says:
> >
> > 15.254s ModemManager.service
> > 10.562s NetworkManager.service
> > ...
> >
> > I.e. MM and NM are the two slowest services in terms of start time.
> > Is there anything I can do about it or try t
On Wed, 2019-02-13 at 16:01 +0100, W. Martin Borgert wrote:
> Hi,
>
> on my embedded system, "systemd-analyze blame" says:
>
> 15.254s ModemManager.service
> 10.562s NetworkManager.service
> ...
>
> I.e. MM and NM are the two slowest services in terms of sta
>
> You need to call "common_create_bearer (task);" before the return here
A true dark knight, thanks Aleksander!
Ana, try this instead:
>From 43c8870b7478f3e5ccdb70a3fc89edddcef96d67 Mon Sep 17 00:00:00 2001
From: Matthew Stanger
Date: Thu, 14 Feb 2019 08:28:14 -0700
Subject: [PATCH] mm-bb-m-c
Hey,
> Give this a try (note this is just a hack to tmp disable the SWWAN feature &
> hopefully I get the ELS61 soon):
> Branched from 1.8.2:
>
> From 63f9ac8a0db1d8902dd7bef329f441ef4ea86c6b Mon Sep 17 00:00:00 2001
> From: Matt Stanger
> Date: Wed, 13 Feb 2019 20:18:00 -0700
> Subject: [PATCH
