about
implementing these changes. Thanks.
Best Regards,
Matthew Starr
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
a new MM and older NM. In this case the
serial port would never recover from a data session since there is nothing to
call Disconnect().
If you could implement #3 with detection of if Disconnect() is implemented, and
if not fall back to #2. Then you could implement this in all currently
suppo
[1559059489.884415] (ttyACM0) device open count is 2 (open)
May 28 16:04:49 canect2 daemon.debug ModemManager[305]:
[1559059489.884725] (ttyACM0): --> 'AT+CIND?'
May 28 16:04:49 canect2 daemon.debug ModemManager[305]:
[1559059489.888515] (ttyACM0): <-- '+CIND:
5,2,1,0,0,0,0,0,2,0,0,0OK'
hen the pppd shutdown process may not be
> > > happening properly in NM and the connected TTY may not go well back to
> > > command mode. I think there was some open issue about this.
> >
> > I have reported a past issue where ModemManager
the old logs I have or possibly recreate the
condition and file a new issue in GitLab if that would help track it.
>
> --
> Aleksander
> https://aleksander.es
Best regards,
Matthew Starr
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
sktop.nm_dispatcher' (using servicehelper)
May 6 18:31:50 canect2 daemon.info NetworkManager[311]:
[1557167510.9628] manager: NetworkManager state is now CONNECTED_LOCAL
May 6 18:31:50 canect2 daemon.info NetworkManager[311]:
[1557167510.9858] device (ttyACM0): state change: failed -> disc
.
Regards,
Matthew Starr
> Date: Mon, 22 Oct 2018 11:39:37 +0200
> From: Sven Schwermer
> To: Aleksander Morgado
> Cc: modemmanager-devel@lists.freedesktop.org
> Subject: Re: Infinite connection loop
> Message-ID: <41689DBE-1755-4F85-BFA7-
> 97cf6e588...@svenschwermer.de>
rce() function is called and self->priv->forced_close is
set to TRUE, that is when the port stops working in ModemManager. At that
point the forced_close value is never reset to FALSE.
Best regards,
Matthew Starr
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
> -Original Message-
> From: Matthew Starr
> Sent: Monday, August 06, 2018 11:36 AM
>
> > -Original Message-
> > From: Matthew Starr
> > Sent: Thursday, July 19, 2018 2:22 PM
> > To: 'Aleksander Morgado'
> >
> > > -O
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Thursday, July 19, 2018 2:16 PM
>
> Hey,
>
> On Thu, Jul 19, 2018 at 3:47 PM, Matthew Starr
> wrote:
> > I am running ModemManager 1.8.0 and NetworkManager
yACM0): state change: prepare -> failed (reason
'unknown') [40 120 1]
Jul 19 13:18:06 canect2 daemon.warn NetworkManager[309]:
[1532006286.6295] device (ttyACM0): Activation: failed for connection 'Aeris'
Jul 19 13:18:06 canect2 daemon.info NetworkManager[309]:
[15
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Tuesday, May 08, 2018 2:53 AM
>
> Hey!
>
> On 08/05/18 00:26, Matthew Starr wrote:
> > Added reading the ID_MM_UBLOX_PORT_READY_DELAY udev flag value
> and using
> &
Added reading the ID_MM_UBLOX_PORT_READY_DELAY udev flag value and using
it as an init delay when a value is set.
The 20 second delay for the TOBY-L4 +READ URC has been reimplemented
using the new ID_MM_UBLOX_PORT_READY_DELAY udev value.
---
plugins/ublox/77-mm-ublox-port-types.rules | 2 ++
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Monday, May 07, 2018 2:31 PM
> On Mon, May 7, 2018 at 6:47 PM, Matthew Starr <mst...@hedonline.com>
> wrote:
> >> -Original Message-
> >> F
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Monday, May 07, 2018 10:59 AM
> On Mon, May 7, 2018 at 4:32 PM, Matthew Starr <mst...@hedonline.com>
> wrote:
> >> -Original Message-
> >> F
Added reading the ID_MM_UBLOX_PORT_READY_DELAY udev flag value and
using it as an init delay when a value is set.
The 20 second delay for the TOBY-L4 +READ URC has been reimplemented
using the new ID_MM_UBLOX_PORT_READY_DELAY udev value.
A 2 second delay for the TOBY-R2 was added since sometimes
ably get the TOBY-R200 to initialize with
ModemManager I needed to have it use a 2 second delay using the
ID_MM_UBLOX_PORT_READY_DELAY udev flag in the 77-mm-ublox-port-types.rules
file. Without this the modem is sometimes never initialized by MM. I am
planning on adding that to the
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Thursday, May 03, 2018 6:49 AM
>
> Hey!
>
> On Wed, May 2, 2018 at 10:34 PM, Matthew Starr <mst...@hedonline.com>
> wrote:
> > Added reading the ID_MM_UB
Added reading the ID_MM_UBLOX_PORT_READY_DELAY udev flag value and
using it as an init delay when a value is set.
The 20 second delay for the TOBY-L4 +READ URC has been reimplemented
using the new ID_MM_UBLOX_PORT_READY_DELAY udev value.
---
plugins/ublox/77-mm-ublox-port-types.rules | 2 ++
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Tuesday, May 01, 2018 11:47 AM
> On Tue, May 1, 2018 at 6:20 PM, Matthew Starr <mst...@hedonline.com>
> wrote:
> > Add reading the ID_MM_PORT_READY_DELA
Add reading the ID_MM_PORT_READY_DELAY udev flag value and using it as
an init delay when a value is set.
The 20 second delay for the TOBY-L4 +READY URC has been reimplemented
using the new ready delay timeout value.
---
plugins/ublox/77-mm-ublox-port-types.rules | 2 ++
Added support for a ID_MM_PORT_READY_DELAY udev tag which can be used to
delay the init of a modem. This is useful for modems that may not
respond correctly within some amount of time after a reset.
---
src/mm-port-probe.c | 8
src/mm-port-probe.h | 1 +
2 files changed, 9 insertions(+)
ed.
Do you know if the TOBY-L4 has a unique USB product ID? If so, do you know
what it is?
Regards,
Matthew Starr
>
> --
> Aleksander
> https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Wednesday, April 11, 2018 3:21 AM
> To: Dan Williams
> Cc: Matthew Starr; modemmanager-devel@lists.freedesktop.org
> Subject: Re: [PATCH] u-blox: ignore non-AT ttyACM interfac
> -Original Message-
> From: Reinhard Speyerer [mailto:rs...@arcor.de]
> Sent: Tuesday, April 10, 2018 4:23 PM
> To: Matthew Starr
> Cc: Dan Williams; modemmanager-devel@lists.freedesktop.org
> Subject: Re: [PATCH] u-blox: ignore non-AT ttyACM interfaces
>
> On Tu
For the TOBY-R2, LISA-R2, and LARA-R2, the only valid AT ports are
ttyACM0, ttyACM1, and ttyACM2. All other ttyACM ports cause MM to
wait 20-30 seconds probing the port on startup.
Ignoring the non-AT ttyACM ports allows MM to not wait 20-30 seconds
probing and therefore startup much faster with
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Friday, April 06, 2018 3:37 AM
> To: Matthew Starr
> Cc: Dan Williams; modemmanager-devel@lists.freedesktop.org
> Subject: Re: u-blox TOBY-R200 Intermittent Long Registration o
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Thursday, April 05, 2018 3:50 PM
> To: Matthew Starr; modemmanager-devel@lists.freedesktop.org
> Subject: Re: u-blox TOBY-R200 Intermittent Long Registration on Simple
> Connect
>
> On
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Thursday, April 05, 2018 1:22 PM
> To: Matthew Starr; modemmanager-devel@lists.freedesktop.org
> Subject: Re: u-blox TOBY-R200 Intermittent Long Registration on Simple
> Connect
>
> On
is between the fast and slow registration and
what might be causing it? Any ideas how to fix it?
Best regards,
Matthew Starr
Apr 3 19:28:08 canect2 daemon.info ModemManager[253]:
[1522783688.313995] Simple connect started...
Apr 3 19:28:08 canect2 daemon.debug ModemManager[253]:
[1522783
This patch fixed the issue. The u-blox LARA R204 modem now works without any
issues. Thanks.
Best regards,
Matthew Starr
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Monday, April 02, 2018 8:09 PM
> To: Aleksander Morgado; modemm
(3)OK'
**
ERROR:ublox/mm-modem-helpers-ublox.c:817:mm_ublox_get_modem_mode_any: assertion
failed: (any != MM_MODEM_MODE_NONE)
Aborted
This same error occurs every time ModemManager is run. I compiled with the
options --without-qmi and --without-mbim since they are not used by my modem.
Best regards,
M
by ModemManager.
Best regards,
Matthew Starr
> -Original Message-
> From: Aleksander Morgado [mailto:aleksan...@aleksander.es]
> Sent: Wednesday, February 07, 2018 2:01 PM
> To: Matthew Starr
> Cc: Dan Williams; modemmanager-devel@lists.freedesktop.org
> Subject: Re:
>
> Try this patch instead...
>
> Dan
>
> ---
> src/mm-iface-modem-3gpp.c | 28 +++-
> 1 file changed, 15 insertions(+), 13 deletions(-)
>
> diff --git a/src/mm-iface-modem-3gpp.c b/src/mm-iface-modem-3gpp.c
> index baf743fb..77b502c0 100644
> ---
ion time?
Any ideas how I could speed this up or make ModemManager realize the modem is
registered already?
Best regards,
Matthew Starr
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
35 matches
Mail list logo
