On Thu, Aug 22, 2019 at 11:06 AM Bjørn Mork wrote:
>
> Dan Williams writes:
> > On Wed, 2019-08-21 at 12:23 +, Amol Lad wrote:
> >> Please help with this. What could be the cause of significant MM
> >> startup delay?
> >
> > When started, or when a new modem is plugged attached, ModemManager
Hey all,
From Paul's email, the port type hints for the TTYs exposed by the
MC74xx could help make the probing much faster. I haven't tested them
myself, but we could definitely add them in the release.
# MC74XX: Add port hints
# if 03: primary port
# if 02: raw NMEA port
# if 00: diag/qcdm
Hey
> I am running libqmi 1.22.4 and ModemManager 1.8.4. I want mmcli to display
> e-utran band 28 in its output because I also want the ability to specify band
> 28 as an allowed band.
>
> Qmicli definitely shows band 28 among the supported bands. I have checked in
> the ModemManager
Hey all,
Please review this MR that repurposes the ID_MM_DEVICE_IGNORE tag
(e.g. so that it applies to all port types and to all filter modes)
and also renames/removes some other tags:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/138
The commit doing the
Hey!
> I am announcing AGH: a 3G/4G connection manager (via ModemManager) / XMPP
> control agent, specifically designed for OpenWrt.
>
Great work :)
> Some of it's features:
> Documentation: AGH is documented enough to get you to a good start;
The documentation is extremely verbose, which is
Hey,
When using the "strict" filter in ModemManager, we try to use
different heuristics to guess whether a device is a modem or not.
One of the checks we do is looking at the exposed interfaces: if the
device exposes one or more ttyACM ports that report themselves as "AT
capable"
Hey,
>
> I'm hoping that those with inside knowledge might explain where my
> problem lies.
>
> I have a sim (ee, uk) that works well in an EE 4g hotspot gadget, and
> I'm putting it into a laptop to use it there as I will get more value
> from it. The laptop is a Dell 7280 running ubuntu 19.04,
Hey Dan and all,
> > > > The main issue with this approach is that ModemManager would do a
> > > > lot
> > > > of tasks that were exclusively done by NetworkManager before,
> > > > like
> > > > IP
> > > > addressing setup or IP routing setup. I'm sure we can instruct NM
> > > > to
> > > > play
Hey!
The following MR adds some retry mechanism to the "reloading" of
bands/modes during a set operation.
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/130
E.g. if we were configured with band "EUTRAN 19" and we try to set
"EUTRAN 20" instead, the modem may return
Hey!
> > > > > I need to collect informations about modems (for IMEI) and SIM cards
> > > > > (for IMSI) available to system over D-Bus.
> > > > >
> > > > > While listening to signal InterfacesAdded on interface
> > > > > org.freedesktop.DBus.ObjectManager does work as mentioned in
> > > > >
Hey!
On Sat, Jul 20, 2019 at 3:35 PM Vincent Bernat wrote:
>
> ❦ 20 juillet 2019 12:00 +02, Vincent Bernat :
>
> > ModemManager[989]: Simple connect state (4/8): Wait to get fully
> > enabled
> > ModemManager[989]: Simple connect state (5/8): Register
> > ModemManager[989]: Simple
Hey,
> > > I need to collect informations about modems (for IMEI) and SIM cards
> > > (for IMSI) available to system over D-Bus.
> > >
> > > While listening to signal InterfacesAdded on interface
> > > org.freedesktop.DBus.ObjectManager does work as mentioned in
> > > documentation, ie. returning
Hey,
Until now, most of the SMS properties of a multipart SMS object were
being initialized once the SMS was fully assembled (i.e. when
absolutely all parts were received). This MR updates that logic so
that the common SMS object fields (e.g. pdu-type, number, smsc...) are
initialized as soon as
Hey,
Until now, the only setup we did for the call waiting service was to
unconditionally enable URCs while the modem was enabled, but we were
not doing any specific setup with the network. This MR allows client
applications to query the status of the call waiting service, and also
request to
Hey Carlo, Daniele and all,
Here's a branch that tries to implement #BND based band management for
the ME910, because the 2G bands are managed in a different way than on
the previous original logic.
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/125
Let me know what
Hey,
The following MR is ready for review:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/124
This MR introduces some cleanups on how the registration updates are
managed, and explicitly fixes the "QMI NAS Initiate Network Register"
based implementation, which was
Hey!
> I have an issue with SMS > 160 characters not showing up in my SMS
> application.
>
> When SMS < 160 characters are received, the following steps take place:
>
> - MM emits an 'added' signal
> - in the callback, the SMS client pulls the SMS list with
> 'mm_modem_messaging_list'
> - in the
Hey hey,
This is the second bugfix release in the ModemManager 1.8.x series. I wasn't
really going to push any new stable update in the 1.8.x branch, but there were
some obvious fixes that anyone shipping 1.8.2 would have wanted...
Overview of changes in ModemManager 1.8.4
Hey hey,
This is the second bugfix release in the ModemManager 1.10.x series.
Overview of changes in ModemManager 1.10.4
---
The list of changes in this version includes:
* QMI:
** Fix assertion when cleaning up event report indications.
* MBIM:
Hey,
>
> I am using a ModemManager - 1.6.4 ( Ubuntu 16.06.4) running on a Sierra
> Wireless EM74xx modem
>
That Ubuntu version seems wrong, I assume you mean 16.04?
> I happen to run the following command multiple times ( modem resets as part
> of test functionality).
>
> mmcli -m 1 --reset
> wt., 18 cze 2019 o 14:43 Aleksander Morgado
> napisał(a):
>
> > My opinion is a bit open on this, I liked the first way because we
> > would try to be as robust as possible and totally avoid using the port
> > with wrong CLOCAL settings, but I don't think we can have
Hey,
>
> I’m currently using ModemManager 1.6.10 on Ubuntu 16.04 server, on a system
> without user interaction. The modem is unlocked and enabled based on a
> configuration in a database.
>
> I tried to set an invalid APN on a modem to see if this error situation
> easily could be reported
Hey,
>I have a few questions regarding getting Network Registration status
> in ModemManager.
>
> May I know how can I achieve the following:
> 1. How to get if current network registration state is automatic?
There is no way to know this from the outside right now. By default it
is
Hey,
>
> I am interested in the location and reset feature of ModemManager that is
> available in version >=1.8 Debian package.
>
>
>
> Debian Buster has 1.10 version. Please let me know if 1.10 will be
> backported to Debian Stretch.
>
@Mathieu Trudel-Lapierre may know this?
--
Aleksander
>
> Have you seen the following commit from NetworkManager for pppd? It has
> helped solve many of the issues of being in sync with pppd and MM that I have
> seen:
>
> https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=a251712a729f676c9c2d38e469e4f88e250229ba
>
> Even with
Hey!
In the past months we've seen several reports of issues with the TTY
port "forced closed" and not being able to be reopened after that and
things like that. The root cause from this problem is that MM tries to
reuse the TTY port after MM itself has detected a disconnection (via
+CGEV URCs or
> > > I'm trying to setup GPS support for EM7455 modem by using 1.10.0 release
> > > of MM.
> > > I tried to use following script from [0] to setup unmanaged raw gps
> > > mode so then /dev/ttyUSB1 can be used by gpsd to get coordinates.
> > >
> > > While running step: mmcli -m 0
Hey,
> I'm trying to setup GPS support for EM7455 modem by using 1.10.0 release of
> MM.
> I tried to use following script from [0] to setup unmanaged raw gps
> mode so then /dev/ttyUSB1 can be used by gpsd to get coordinates.
>
> While running step: mmcli -m 0 --location-enable-gps-unmanaged I
Hey hey,
This is the first bugfix release in the ModemManager 1.10.x series.
Unlike previous bugfix releases of stable branches, this release comes with a
new feature that may require packaging updates, see notes to distribution
packagers below.
Overview of changes in ModemManager 1.10.2
> To answer my own question to get current band ID you can use the new (1.10)
> option:
>
> qmicli -p -d /dev/cdc-wdm0 --nas-get-rf-band-info
> [/dev/cdc-wdm0] Successfully got RF band info
> Radio Interface: 'lte'
> Active Band Class: 'eutran-20'
> Active Channel:'6400'
>
Please note that
> It looks like ModemManager takes the highest numbered CID it sees and assumes
> it needs to use the next one available or if at the max CID then reuse it.
> In the case of the TOBY-R200, only CID 1 and 31 are used so ModemManager
> tries to reuse CID 31 but the modem reports an error since
Hey all,
This MR fixes an issue with the modem state reported as "registered"
even if the registration was really denied, comments welcome:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/107
--
Aleksander
https://aleksander.es
Hey Dan & all,
The original fix I had for this issue was to always add raw commands
to the head of the queue inside the serial port:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/103
The new fix I have for this issue is to setup a new queue of
operations at modem
Hey Brendan,
Looking at the tags we set, we're just ignoring the ports we don't
want to use or we don't support, but we're not explicitly specifying
the purpose of each of the ports:
# LARA-R2 port types
# ttyACM0 (if #0): primary
# ttyACM1 (if #2): secondary
# ttyACM2 (if #4): tertiary
#
Hey Nick, Rick and everyone,
I've pushed a MR to integrate MM 1.10 (including the new key-value output
support) in the openwrt repo:
https://gitlab.freedesktop.org/mobile-broadband/mobile-broadband-openwrt/merge_requests/3
Nick; it's not really based on the previous work you did. The main change
Hey,
>
> I have some trouble with pulling a received SMS from the ModemManager
> messaging-list. Roughly described I'm doing things like so:
>
> gdbus_sms = MM_GDBUS_MODEM_MESSAGING(mm_sms->modem_messaging);
> g_signal_connect (gdbus_sms, "added",
> G_CALLBACK
>
> > It's the modem firmware itself handling that, MM will just report
> > whatever the modem is reporting.
> >
> > E.g. if the modem is registered and connected in LTE, and the LTE
> > network disappears (e.g. low signal quality, out of coverage) then the
> > modem will try to handover to 3G or
Hey,
>
> First what are the conditions where a cellular data connection will be
> automatically disconnected due to bad signal/loss of network? Also what
> program handles the disconnect (NetworkManager, ModemManager, pppd)?
>
It's the modem firmware itself handling that, MM will just report
Hey,
> I need to collect informations about modems (for IMEI) and SIM cards
> (for IMSI) available to system over D-Bus.
>
> While listening to signal InterfacesAdded on interface
> org.freedesktop.DBus.ObjectManager does work as mentioned in
> documentation, ie. returning properties on newly
Hey!
> > Is there any interest in making ModemManager an official OpenWrt
> > package?
>
> Yes. Aleksander already requested help doing that:
> https://lists.freedesktop.org/archives/modemmanager-devel/2019-April/007201.html
>
> > It seems like they would accept it. Is there a TODO?
> >
> On Ubuntu 18.10 Cosmic (MM 1.8.2) I get the following.
>
> # ls /dev/ttyACM*
> /dev/ttyACM0 /dev/ttyACM2 /dev/ttyACM4
> /dev/ttyACM1 /dev/ttyACM3 /dev/ttyACM5
>
> # lsmod | grep acm
> cdc_acm 32768 4
>
> # mmcli -L
>
> Found 1 modems:
>
Hey!
>
> Any update on the patch? :)
> In the meantime I got response from Telit that they won't fix the original
> problem which made me create this patch.
>
Oh wow, I forgot about it, sorry...
I have pushed it to a new merge request in gitlab now:
Hey,
> Is there support for simple-connect where instead of overwriting the APN I
> can just select the APN with the profile #.
>
> In qmcli, I can just do this:
> --wds-start-network="3gpp-profile=3"
>
> reason is some carriers like Verizon have the internet APN in slot 3 and I do
> not want
Hey Enrico,
> I am writing to report an issue we are having with Wistron NeWeb (WNC) Modem
> device.
> libmbim -> GIT version at commit 67ba57f89fd3a2f4b280361e650eaef0057baeaa
> libqmi -> GIT version at commit 38d6729b0822a96e757162208fd8c88bb648085b
> MM -> GIT version at commit
Hey!
> since long I use a simple Python script that fetches text
> messages via org.freedesktop.ModemManager.Modem.Gsm.SMS.List().
> However, polling is boring. Is there a way to get SMS
> asynchronously, e.g. by D-Bus callback?
>
In the new MM1 .0 DBus API you have the Modem.Messaging interface
Hey,
I maintained an unofficial openwrt feed for MM/libqmi/libmbim in
bitbucket.org, I've just moved it to fd.o gitlab alongside the actual
projects:
https://gitlab.freedesktop.org/mobile-broadband/mobile-broadband-openwrt
BTW, if anyone would like to work on integrating these in the upstream
On Mon, Apr 8, 2019 at 10:06 AM Stelling2 Carsten
wrote:
>
>
> General |dbus path: /org/freedesktop/ModemManager1/Modem/0
>|device id: 57296b70bd5c42eaf98afb46f49dbc8f83716b88
>
>
Hey!
>
> I report that modem Telit LE910-EU1 (MBIM)
>
> is supported by ModemManager.
>
>
>
> USB ID: 1bc7:0032
>
>
>
> Please, add this modem to the list of supported modems here:
>
> https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/
>
Thanks, added to the list now.
Do
Hey,
If anyone is interested in contributing more to ModemManager and would
like to have more test devices to play with, please drop me a private
email and we'll try to fix that.
Cheers!
--
Aleksander
https://aleksander.es
___
ModemManager-devel
Hey!
> > https://gitlab.freedesktop.org/mobile-broadband/libmbim/merge_requests/8
> > https://gitlab.freedesktop.org/mobile-broadband/libqmi/merge_requests/35
> >
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/88
>
> I tested the patches against the following
On Thu, Apr 4, 2019 at 10:10 AM Pavlin Georgiev wrote:
>
> Hi.
>
> I report that modem Dell F3607gw v2
> is supported by ModemManager.
>
> USB ID 413c:8184 Dell Computer Corp. F3607gw v2 Mobile Broadband Module
>
> Please, add this modem to the list of supported modems here:
>
Hey!
> If you or your company are using ModemManager in a professional
> product, would you mind sharing your experience in the mailing list?
>
The ModemManager/NetworkManager stack is used in the NIO ES8 elecric
SUV to provide mobile broadband connectivity.
https://www.nio.io/es8
--
On Wed, Apr 3, 2019 at 6:46 PM Pavlin Georgiev wrote:
>
> Hi.
>
> I report that modem Ericsson N5321
> is supported by ModemManager.
>
> USB ID 0bdb:193e Ericsson Business Mobile Networks BV
>
> Please, add this modem to the list of supported modems here:
>
Hey,
On Wed, Apr 3, 2019 at 3:14 PM Pavlin Georgiev wrote:
>
> I have found inconsistency and remove it.
> Now I send the logs for Sierra Wireless EM7355 again
>
Added now, thanks
--
Aleksander
https://aleksander.es
___
ModemManager-devel mailing
On Wed, Apr 3, 2019 at 2:18 PM Pavlin Georgiev wrote:
>
> Hi.
>
> I report that modem Qualcomm, Inc. Siemens SG75
> is supported by ModemManager.
>
> USB ID 05c6:6000 Qualcomm, Inc. Siemens SG75
>
> Please, add this modem to the list of supported modems here:
>
On Wed, Apr 3, 2019 at 1:59 PM Pavlin Georgiev wrote:
>
> Hi.
>
> I report that modem Huawei K3765
> is supported by ModemManager.
>
> USB ID 12d1:1465
>
> Please, add this modem to the list of supported modems here:
> https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/
>
On Wed, Apr 3, 2019 at 1:44 PM Pavlin Georgiev wrote:
>
> Hi.
>
> I report that modem Sierra Wireless EM7355
> is supported by ModemManager.
>
> USB ID 1199:9041
>
Looks like the attached mmcli.log is from a MC7455?
> Please, add this modem to the list of supported modems here:
>
On Wed, Apr 3, 2019 at 12:19 PM Pavlin Georgiev wrote:
>
> Hi.
>
> I report that modem Sierra Wireless MC7455
> is supported by ModemManager.
>
> USB ID 1199:9071
>
> Please, add this modem to the list of supported modems here:
>
On Wed, Apr 3, 2019 at 8:38 AM Pavlin Georgiev wrote:
>
> Hi.
>
> I report that modem Sierra Wireless EM8805
> is supported by ModemManager.
>
> Please, add this modem to the list of supported modems here:
> https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/
>
Added, thanks
On Wed, Apr 3, 2019 at 8:27 AM Pavlin Georgiev wrote:
>
> Hi.
>
> I report that modem Sierra Wireless EM7345
> is supported by ModemManager.
>
> Please, add this modem to the list of supported modems here:
> https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/
>
> Thank you.
>
On Wed, Apr 3, 2019 at 8:23 AM Pavlin Georgiev wrote:
>
> Hi
>
> I report that modem Zoom 4595 from Omega Technologies
> is supported by ModemManager.
>
> Please, add this modem to the list of supported modems here:
> https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/
>
On Wed, Apr 3, 2019 at 8:07 AM Pavlin Georgiev wrote:
>
> Supported modem Nokia 21M-02
> Hi
>
> When I open the web page with supported modems in ModemManager
> https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/
> and I check for "Nokia 21M-02"
> then I see that the device
Hey,
The following MR updates the Location interface in order to allow
enabling MSA or MSB A-GPS. Until now the A-GPS source was bound to
trying MSA only, there was no way to enable MSB A-GPS.
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/84
Comments welcome!
--
Hey!
> The following MR adds support for reporting the current carrier config
> in use, and also implements automatic carrier config switching based
> on QMI PDC, initially done for the DW5821e.
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/66
>
> A single modem
Hey
> Please see the following MR to allow controlling the "unmanaged GPS"
> source even if "raw/nmea GPS" sources are already being used,
> applicable to the DW5821e where QMI LOC is used for "raw/nmea" instead
> of a TTY.
>
>
On Thu, Mar 28, 2019 at 3:05 PM John Marrett wrote:
>
> Aleksander,
>
>
>>> What libqmi version are you using? If you're using 1.22.0, please
>>> update to 1.22.2 and retest.
>>>
>
> Sorry for the delay in getting back to you and the list. With 1.22.2 we see
> debug messages but also see a
> > >
> > > This is RHEL7 so I’m using the 1.6 branch of MM and 1.18.0 libqmi; for MM
> > > I
> > tried building our own 1.16.4 when we suspected MM being the core issue,
> > with no change in behavior.
> > >
> >
> > Hard to say what the issue is, but you're really using somewhat old
> >
Hey!
If you or your company are using ModemManager in a professional
product, would you mind sharing your experience in the mailing list?
Even generic descriptions would be appreciated, but if you can share
also platform details that would be great. Of course, only asking for
information that
>
> Yeah, mixed feelings from me too. I guess before we do that, can we ask
> what commands people want to use? I'd rather it not be used a short
> circuit for stuff that could be fixed in MM or implemented fairly
> easily for a device. That's my only reservation, that having it may
> reduce the
> We're looking at using the AT port to get a few status values that don't
> appear to be readily available from QMI. One we need in particular is device
> temperature (there's a hardware failure condition that manifests as a very
> high temperature value). Of course any hints on how to pull
Hey!
See comments below.
On Thu, Mar 21, 2019 at 1:14 PM Lech Perczak
wrote:
>
> Some modems (Namely: Telit LE910 V2) report nonzero NwError code,
> outside of 3GPP TS 24.008 - in "register-state set command-done" response,
> while status code equals MBIM_STATUS_ERROR_NONE.
> In such cases
> https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices
> lists the supported modems, but the link seems old.
>
> In particular, MC7304 is already end-of-life, and Sierra-Wireless guys
> have suggested MC7455 / MC7430.
>
> Are any of MC7455 / MC7430 supported (yet) on
> > I actually tried exactly this: I restarted the modem without
> > ModemManager running, sent AT to the modem until I got +PBREADY as
> > part of the reply and then started ModemManager. Unfortunately, this
> > leads to the same behaviour. Same old +CEER: "SM
> > deactivation",187,"Last PDN
Hey,
> I am trying to find a way to use the AT ports or mbim ports that occupied by
> MM as all the device ports were used by MM. eg. I want send AT command to the
> modem, but MM occupies the AT port. Is there any way to make MM stop using
> the AT port for a while but not kill the MM? To do
> (a) the modem itself caring about the context #
> (b) or somehow the network caring about the context # (which I didn't
> think was passed to the network at all)
> (c) or is it settings on the PDP Context itself that are wrong and if
> the settings were correct any context # would work
> (d)
> > ModemManager does not know how to use the cdc-ncm ports exposed by the
> > modem, the implementation is missing.
> > IIRC we had some attempt to implement this, and I even got some HL
> > modules sent by Sierra to me, but I'm missing the devkit to use them
>
> That explains the issues I’m
Hey,
> I can even connect via --simple-connect. The problem is that NetworkManager
> always connects via pppd over the CDC-ACM port. I would have expected to
> establish the connection via one of the CDC-NCM ports (wwan0..4).
ModemManager does not know how to use the cdc-ncm ports exposed by
> > Random question, what does +CSQ report? MM uses +CIND because it gives
> > async notifications, which +CSQ does not. CSQ is usually tied to RSSI
> > though, which still isn't as useful for LTE.
>
> Interestingly, the ublox AT manual says, that +CSQ reports the RSRP in LTE,
> but it doesn’t
Hey,
>
> This is RHEL7 so I’m using the 1.6 branch of MM and 1.18.0 libqmi; for MM I
> tried building our own 1.16.4 when we suspected MM being the core issue, with
> no change in behavior.
>
Hard to say what the issue is, but you're really using somewhat old
versions. Any chance you can
> > The following commit introduced a hard dependency on libqmi for the dell
> > plugin:
> >
> > commit 1093c124b4cb "dell,dw5821e: use DMS extension method to load
> > properly formatted firmware version"
> >
> > so ModemManager fails to build under --without-qmi.
>
> Oops, let me fix that.
>
>
Hey!
On Tue, Mar 12, 2019 at 10:50 PM Ben Chan wrote:
>
> The following commit introduced a hard dependency on libqmi for the dell
> plugin:
>
> commit 1093c124b4cb "dell,dw5821e: use DMS extension method to load properly
> formatted firmware version"
>
> so ModemManager fails to build under
Hey,
> It would be fine, if the “service installer” adds the polkit.service
> dependency, if MM is compiled with --with-polkit=yes.
>
Yes, makes sense. Could you open a new Issue here so that we track the
change? https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues
--
> Do I continue to configure the ModemManager install the same following that?
> Now running ModemManager --debug gives me the following error:
> ModemManager: symbol lookup error: ModemManager: undefined symbol:
> mm_gdbus_modem3gpp_set_initial_eps_bearer
>
If you're installing in /usr/local,
Hey,
> Thought I'd gotten through all the issues, but have one more that I can't
> seem to figure out:
>
> Have built and installed mbim-glib 1.18.0 in /usr/local/lib (as well as
> qmi-glib).
> Using ./configure of :
> ./configure LDFLAGS="-L/usr/local/lib/libqmi-glib.so.5 -lqmi-glib
>
dcd5db8280f00565c82685d794 Mon Sep 17 00:00:00 2001
> From: Aleksander Morgado
> Date: Fri, 12 May 2017 18:24:13 +0200
> Subject: [PATCH 1/1] allow specifying the PDP CID to use
>
> Some operators, most notably Verizon, require connection to be
> performed through a specific PDP
> I’m trying to use ModemManager 1.8.2 with a Verizon LTE Cat-M1 modem. Verizon
> requires using PDP context #3 for the internet connection. I read the thread
> from 2017
> (https://lists.freedesktop.org/archives/modemmanager-devel/2017-May/004663.html)
> in which a patch was proposed to
Hey all,
Please see the following MR to allow controlling the "unmanaged GPS"
source even if "raw/nmea GPS" sources are already being used,
applicable to the DW5821e where QMI LOC is used for "raw/nmea" instead
of a TTY.
> I am working on creating a mobile embedded linux device using an LE910
> module. I have been successful in using it to connect to the internet using
> qmicli tools, however, I'd like to have more sophisticated network management
> using ModemManager and NetworkManager. Unfortunately, I'm
> Thanks for clarification. This means, Daniele's patches work like expected.
>
> Additional note: To make Daniele's patches work, I had to revert Aleksander's
> patch
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/72
> to enable XMM features for Telit.
>
Yeah, I
>
> But setting the preferred mode fails.
>
> mmcli -m 0 --set-preferred-mode=2G
> error: setting preferred mode requires list of allowed modes
>
This is expected; you only want to set a "preferred mode" if you're
configuring multiple "allowed modes".
E.g. if you just want 2G, you would do:
Hey Dan & all,
The following MR adds support for reporting the current carrier config
in use, and also implements automatic carrier config switching based
on QMI PDC, initially done for the DW5821e.
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/66
A single modem may
Hey John
>
> I'd welcome any feedback you can offer on my analysis.
>
There's really little we can learn from the issue at ModemManager
level if the error reported is just "generic-unspecified", so if you
have actual network traces as you do those will give you much better
information.
BTW, you
Hey Daniel.
> I'm experiencing a connection loop, where it switches between connected and
> disconnected.
>
> Logfiles:
> - Normal log (https://pastebin.com/jQdzjRVW)
> - Debug log (https://pastebin.com/44V1kUxn)
>
> Has anyone experience this before? Or could anyone explain a bit what is
>
Hey Quincy,
> The Intel wants to remove the AT commands uesd for GNSS in the plugins/xmm
> from release 1.9.990, including AT+XLCSLSR, AT+XLCSSLP, AT+XLSRSTOP, as the
> Intel do not want to put those AT commands in open license. And the Intel
> offer a more powerful synthetic AT command to
> > > Within the debug output I found the following line
> > > ModemManager[623]: [1550762368.321591] MBIM-powered Telit modem
> > > found...
> > > which points out, that calling
> > > if (mm_port_probe_list_is_xmm (probes))
> > > did not find the XMM support.
> >
> > It didn't find it, because
Hey!
> Within the debug output I found the following line
> ModemManager[623]: [1550762368.321591] MBIM-powered Telit modem
> found...
> which points out, that calling
> if (mm_port_probe_list_is_xmm (probes))
> did not find the XMM support.
It didn't find it, because the XACT=? check failed:
Hey!
> I just realized I forgot to add the error and code.
> Now it should be there!
>
> Kind regards,
>
> Daniel Vlaardingerbroek
>
> Op wo 20 feb. 2019 om 15:01 schreef Daniel Vlaardingerbroek
> :
>>
>> Hi,
>>
>> I'm trying to connect to the Bearer interface via DBus, but it's giving me
>> an
Hey,
> Thank you for your fast response.
> With your patch applied to 1.10.0, the error message is still the same.
> Is there anything I can provide for debugging?
>
Could you send MM debug logs with the patch applied?
--
Aleksander
https://aleksander.es
Hey,
> I'm using ModemManager 1.10.0, and libmbim 1.18.0 in conjunction with Telit
> LE910-EU V2.
> It all works fine, but I'm not able to set the preferred GSM mode or access
> technology.
> I'm confused by this error message "Cannot change modes: only one combination
> supported', because
> to try out one or another patch, I like to compile modemmanager. My
> target systems are ARM (32 bits), so naturally I like to cross-compile
> it on a faster architecture. This worked well in the past (versions
> 0.5 and 0.6), but so far I fail with 1.10.
>
> It seems, that modemmanager needs
901 - 1000 of 2422 matches
Mail list logo
