Hey Zurab,
> Why sending arbitrary AT command requires ModemManager &
> NetworkManager running in debug mode?
Sending arbitrary AT commands requires either ModemManager --debug or
configuring --with-at-command-via-dbus. The main reason was to avoid
users interfering with ModemManager's own state
Hey
> Thanks for your answer!
>
> interesting stuff ... it seems to be exactly what I need.
>
> Why is "3gpp eps-ue-mode-operation" not part of the profile setting?
>
Don't think that setting is considered part of the profile settings in
any modem I've looked at.
> Is it already in a usable
Hey,
> We're using ModemManager via NetworkManager.
> It looks like this means the "simple" interface (MMIfaceModemSimple) is used
> This causes a connection to be setup in a simple way, e.g. via
> enable (mm_base_modem_enable) and register
> (register_in_3gpp_or_cdma_network).
>
> I'd like to
Hey,
>> >> In our case we have switched the modem to mbim mode to be able to
>> >> receive / be aware of sim removal notifications.
>> >>
>>
>> > Didn't we already add the SIM removal notifications in QMI modems?
>> > Have you tried with ModemManager git master
Hey,
>>
>> >> In our case we have switched the modem to mbim mode to be able to receive
>> >> / be aware of sim removal notifications.
>> >>
>>
>> > Didn't we already add the SIM removal notifications in QMI modems?
>> > Have you tried with ModemManager git master recently?
>>
>
> Since which
Hey,
>
> However on the target platform, the modem module is not connected trough USB
> but trough an ordinary serial UART. And: that serial port is not provided by
> a serial-usb-adapter, but is a native embedded serial uart, the platform
> driver is 'atmel_usart_serial'.
>
> I can open a
>
> For our proprietary modemcontroller we had the solution to provide the PDP
> authentication information also in the first memory location, for which no
> APN was stored either.
>
> So i tried to set initial bearer settings, but without success:
>
> mmcli -m 1
>
Hey hey,
This is the sixth bugfix release in the ModemManager 1.14.x series.
Overview of changes in ModemManager 1.14.12
---
* MBIM:
** Plug memleak in disconnection logic.
** Don't fail IPv4v6 connection attempt if only IPv4 succeeds.
* QMI:
Hey,
>
> I've been working on updating ModemManager to allow setting up QMAP
> data aggregated links transparently, either with qmi_wwan
> add_mux/del_mux or with qmi_wwan+rmnet (pass_through=Y).
>
> See
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/447
>
I've
Hey,
> > We're using a Cinterion ELS61-E R2 modem and ModemManager-1.14.0.
> > It looks like we're facing a PDN activation problem which maybe caused
> > by ModemManager.
> >
> > Our modem is happily connected, using 4G and PDP Context ID (CID) 1.
> > The CID refers to type=ipv4 and
Hey Nick!
>
> I am using it with Quectel EM-12G and RM500Q, a recent version of MM works
> pretty well with them. Not sure though where to find supported device info
> except in the qmi_wwan.c source and the ModemManager plug-in source.
Yes, that's also a good way to know it :)
--
Aleksander
Hey,
> At the moment I am considering using the following modems for different
> implementations and I pretend to use the ModemManager.
>
> Quectel - EC25
A lot of people are using the EC25 and other Quectel modules, yes.
> Sierra Wireless - WP7607
>
I truly have no idea about this one.
>
Hey hey,
Just a quick update to fix the builds with GLib < 2.54.
This is the first bugfix release in the 1.16.x series, built from the mm-1-16
branch.
ModemManager 1.16.2
---
* build: fixed with GLib < 2.54.
* qmi: fixed network regitration
Hey
> > I've been working on updating ModemManager to allow setting up QMAP
> > data aggregated links transparently, either with qmi_wwan
> > add_mux/del_mux or with qmi_wwan+rmnet (pass_through=Y).
> >
> > See
> > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/447
Hey all!
I've been working on updating ModemManager to allow setting up QMAP
data aggregated links transparently, either with qmi_wwan
add_mux/del_mux or with qmi_wwan+rmnet (pass_through=Y).
See
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/447
For the
Hey Norbert,
Giacinto, added you in CC, in case you have some suggestion.
>
> We're using a Cinterion ELS61-E R2 and seem to suffer from a lot of
> "packet data disconnects" and cell/rat/MO switching.
> We're advised to force the modem to use 3G/2G (or 4G/2G) Radio Access
> Technology with the
On 24/2/21 10:10, yegorsli...@googlemail.com wrote:
> From: Yegor Yefremov
>
> Move the code into the main() routine.
> ---
Merged, thanks
> examples/network-scan-python/network-scan-python | 9 +++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git
Hey hey,
This is a new major release of ModemManager, which will be the base for the 1.16.x stable series
(the new "mm-1-16" branch in git). The release has been tagged as "1.16.0".
Thanks to everyone involved!
ModemManager 1.16.0
---
The following
Hey Michal,
>
> I've prepared some patches for ModemManager, libqmi and libmbim which will:
>
> introduce new UIM messages to read configuration of all facility locks from
> QMI modem and to disable the locks
> create new API in MM to disable facility locks on QMI and MBIM modems
> add new cli
Hey all,
The following merge request in gitlab contains a rework of how
charsets are managed in the MM daemon. Reviews and comments welcome!
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/438
The charsets APIs have been changed in a way that 2 sets are given: to
On 15/2/21 17:53, yegorsli...@googlemail.com wrote:
> From: Yegor Yefremov
>
> Move the code into the main() routine and pass main_loop as
> a parameter to the signal handler.
> ---
Merged, thanks!
> .../modem-watcher-python/modem-watcher-python | 25 ---
> 1 file changed, 16
On 15/2/21 17:53, yegorsli...@googlemail.com wrote:
> From: Yegor Yefremov
>
> Move comments under the class and method definitions.
>
> Also rework boolean handling.
> ---
Merged, thanks!
> examples/modem-watcher-python/ModemWatcher.py | 52 +--
> 1 file changed, 25
On 13/2/21 17:19, yegorsli...@googlemail.com wrote:
> From: Yegor Yefremov
>
> Otherwise we get the following exception:
>
> Traceback (most recent call last):
> File "/root/network-scan-python", line 57, in
> networks = modem3gpp.scan_sync()
> gi.repository.GLib.Error:
On 13/2/21 17:19, yegorsli...@googlemail.com wrote:
> From: Yegor Yefremov
>
> Use autopep8 utility to resolve issues like spaces before brackets
> and wrong hanging indentation.
>
> Also treat objects like boolean variables to check whether they are
> None or not.
> ---
Merged, thanks
>
-watcher-python/ModemWatcher.py
> index a18725b1..8091d9f3 100644
> --- a/examples/modem-watcher-python/ModemWatcher.py
> +++ b/examples/modem-watcher-python/ModemWatcher.py
> @@ -18,10 +18,10 @@
> # Copyright (C) 2014 Aleksander Morgado
> #
>
> -import os, sys, gi
> -
>
> > Btw. Debian 11 (bullseye) has its "hard freeze" on 2021-03-12.
> > It might be good to have 1.16 ready before 2021-03-02 to get it in.
> >
>
> Oh, that should be fine
>
I think MM 1.16 should happen sometime in the following days. I had a
bunch of things in my mind that I would have wanted
Hey John,
>
> This started as an nmci question but I realised I don't understand how to
> configure bearer contexts with mmcli either.
>
> My starting point was creating a connection using nmcli (I wanted to really
> use ipv6.method "disabled" but that's another story.)
>
> sudo nmcli
Hey,
> In our case we have switched the modem to mbim mode to be able to receive /
> be aware of sim removal notifications.
>
Didn't we already add the SIM removal notifications in QMI modems?
Have you tried with ModemManager git master recently?
> Are QMI WDS indications still received when
Hey,
> > > I think we need to understand why, in the case of suspend/resume
> > > cycle and using only QMI, we're not receiving and processing the WMS
> > > indications properly:
> > > * As said above, does the host even awake when the SMS arrives and
> > > we're using QMI?
> > > * Is it any
> > I think we need to understand why, in the case of suspend/resume
> > cycle and using only QMI, we're not receiving and processing the WMS
> > indications properly:
> > * As said above, does the host even awake when the SMS arrives and
> > we're using QMI?
> > * Is it any different (host
On Sun, Jan 31, 2021 at 10:24 PM Mateusz Lamparski wrote:
>
> ok, i noticed a connection drop , what file is for log?
>
I assume you can do "sudo journalctl -u ModemManager". If you enabled
debug logging, we should see all protocol messages in the log.
--
Aleksander
https://aleksander.es
Hey Dylan,
> > > So with these your modem always stays connected over USB? How does
> > > ModemManager react to this when resuming/suspending? ModemManager
> > > still reprobes the device right?
> > Yes, the modem remains connected over USB, even over many
> > suspend/resume cycles. MM doesn't
On Fri, Jan 29, 2021 at 7:18 PM Mateusz Lamparski wrote:
>
> Hej, sorry but i did not understand,, are there any clues ?
I tried to explain it to you in a previous email, but I think we're
lost in translation... :)
There could be a bug in ModemManager (MM not processing the disconnect
Hey!
> > > Alexsander already gave you the link, fill an issue in gitlab (
> > > https://gitlab.freedesktop.org/NetworkManager/ModemManager/-/issues
> > > ) and check the tickbox saying "This issue is confidential and
> > > should only be visible to team members with at least Reporter
> > >
Hey!
On Fri, Jan 29, 2021 at 12:55 PM Frederic Martinsons
wrote:
>
> Alexsander already gave you the link, fill an issue in gitlab
> (https://gitlab.freedesktop.org/NetworkManager/ModemManager/-/issues) and
> check the tickbox saying "This issue is confidential and should only be
> visible to
On Fri, Jan 29, 2021 at 11:37 AM Mateusz Lamparski wrote:
>
> im already like i showed to You have debuging on on mmcli.
> System is debian Buster.
>
Do you get the full ModemManager debug log if you run "journalctl -u
ModemManager" ?
If so, please reproduce the issue (wait until the pings start
Hey,
> /usr/bin/mmcli --set-logging=DEBUG
I don't know what system you're using, but the next thing to do would
be to get the system log (either syslog or journalctl output) to see
if the ModemManager daemon debug logs are available when the problem
was reproduced. Please investigate a bit how
On Fri, Jan 29, 2021 at 10:29 AM t...@torunska2.pl wrote:
>
> Ok, do it looks now promising,
>
>
> Can You help me to do that?
> What do I need to do now?
>
You need to run ModemManager daemon with debug logs and try to
reproduce the problem, see:
Hey,
> Tnak You for the reply ,
> ok, so the IP setting of wwan0 are by default set witch dhclient -4
> wwan0 realy no idea what dhclient does there , but after restart it
> all
> works perfect, til some time.
>
Ah, ok. So what's probably happening here is that at some point the
network is
Hey,
>
> Help me to understand whats is going on, connected byt ping -I wwan0
> wp.pl is not woprking no network istead.
>
The mmcli output below shows the modem is connected. But, does the
wwan0 interface have correct IP settings configured in the interface?
Also, if the WWAN connection is not
Hey,
> I am finding a unexpected behaviour and I would like to know how does the
> ModemManager work in situations like this one, when the modem has no signal
> at all or the signal is quite poor:
>
> [1607682864.814360] Received notification (service 'basic-connect',
> command
Hey Giacinto,
>
> for Cinterion modems that support the profiles, there is a special
> command to read them (ATI61, no mbim equivalent, maybe qmi but I
> wouldn't know it; and an at^scfg? option to read the current one) as a
> list and would fit well with option 2.
> The second option would also
On 16/1/21 17:30, Mateusz Lamparski wrote:
> How to check this modemmanager log ?
See https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
--
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
Hey hey,
This is the fifth bugfix release in the ModemManager 1.14.x series.
Overview of changes in ModemManager 1.14.10
---
* Modem interface:
** Plug MmGdbusModem leak when bearers are updated.
** Don't consider charset setup failure as fatal.
> No idea what happend look here are commande :
> file rc.wwan0
> #!/bin/bash
> /usr/bin/mmcli -m 0 -e
> /usr/bin/mmcli --verbose --simple-connect="apn=internet,ip-type=ipv4" -m
> 0
> /usr/sbin/dhclient -4 wwan0
>
> reply
> [22:23][root@torunska2][~] $ /etc/init.d/rc.wwan0
> successfully enabled
Hey,
> I picked the single property for the initial implementation so that MM
> would notify consumers when the profiles list changed via OTA update.
> If we are moving to a D-Bus method to list them instead, then we
> should preserve this behavior somewhere else (i.e. a separate signal).
>
Hey all,
Eric wrote an initial draft of the API to expose profiles (provisioned
contexts) in DBus here:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/179
The initial implementation he wrote relies on a read-only "Profiles"
property exposed in the 3GPP interface,
Hey,
> On 2021-01-08 11:43, Aleksander Morgado wrote:
> > If any of you is also waiting for a new 1.16, please please test git
> > master as much as possible!
>
> Are there more 1.14 releases planned?
>
Possibly, bugfix-only
> Btw. Debian 11 (bullseye) has its
Hey Teijo,
> There are some new features in MM master branch that we would like to
> take in production use in the near future. Are there any plans or
> schedules for MM 1.16 stable version release, so that we could adjust
> our plans accordingly?
>
I had quite some things scheduled in my TODO
Hey,
> I'm trying to use ModemManager (in conjunction with NetworkManager) to manage
> a Quectel EC25 mini-pcie module (which is actually USB) using QMI. More
> specifically, I need it to play-nice with suspend-to-ram, and minimise the
> frequency at which it wakes up the host.
> I've managed
Hey,
> Thanks to the logs of ModemManager, I could identify several places
> where we lose some time during the resume sequence of a suspend/resume
> cycle:
>
> 1. ModemManager waits a fixed amount of time to make sure that all
> ports of a modem show up using udev, losing ~1.5s
It's a bit more
Hey Jessy & Nick
>> I would like to add support for SIM switching to ModemManager.proto for
>> OpenWrt, but the only way to achieve this currently (AFAIK) is by using
>> qmicli --sim-switch-slot. I have it working by calling qmicli, but is it
>> possible to do it without depending on qmicli?
Hey
Those warnings are expected
On Thu, 24 Dec 2020, 03:49 Mateusz Lamparski, wrote:
> So i dont understand?
>
> now in journalctl -xe
> I spoted some warings or errors ?
>
> gru 24 03:39:31 debian ModemManager[835]: [modem0] couldn't load
> carrier config: QMI PDC not supported
> gru 24
On Wed, Dec 23, 2020 at 2:45 PM Mateusz Lamparski wrote:
>
> So, the reply is simple i cant do anything what i liked ? ;(
> ___
You cannot store SMS messages; that's the only thing you cannot do
(with the firmware you're using) from all the things you needed to do,
I think.
--
Aleksander
Hey Mateusz,
For context for everyone, this email is in reply to this one:
https://lists.freedesktop.org/archives/modemmanager-devel/2020-December/008326.html
> [21:38][root@debian][~] $ mmcli -m 0
>
> General |dbus path:
>
Hey Mateusz,
> Sorry for my bad ENGLISH, ,
> i have a task to do an failover script with 2 wan connections
> 1.cable main one
> 2. LTE using (manufacturer: Huawei Technologies Co., Ltd.,model: HUAWEI
> Mobile V7R11,firmware revision: 11.617.15.00.00)
>
> i wroted a script and it is working
Hey all,
I'd like to ask for help from anyone willing to work a bit more in ModemManager.
Everyone in this list always has a "preferred" module to work with,
usually because that may be the only module at hand. But there are
tasks that are orthogonal to all modules and protocols, like e.g. the
Hey,
> Thanks for the answer Aleksander, by the way, I finally got a nano sim for my
> model and all went well. But, sadly same errors happens if the sim is locked
> (same error on CSCS than when the sim was missing).
>
> I'll try at the beginning of next week to implement what you suggest on
Hey!
>
> After a sim was inserted in the dongle, no problems have been notices so I it
> seems that a missing sim prevent modem initialization (which, to my opinion
> should not be , it should failed only on enable step).
>
Yes, I agree. If the CSCS=X operation fails, we should still go on,
Hey,
> >>> Please take a look at the recent Cinterion plugin changes, because
> >>> Giacinto has already implemented this kind of thing for Cinterion
> >>> modems, using the SetInitialEpsBearerSettings() method:
> >>>
Hey Artur,
> I am wondering if I may get some insight on the GPS refresh rate. When I
> change the rate from the default 30 seconds to say, 5, the utc timestamp on
> the nmea string does not change. When I disable the location gathering and
> re-enable it the timestamp updates once.
Hey,
> > The DIAG/QCDM ports were extremely important in some old CDMA modems
> > that required them for control instead (or in addition to) the AT
> > ports, at least for several purposes like gathering access tech info
> > and such. Due to that, MM has been attempting QCDM probing by default
>
Hey Dan and all,
The DIAG/QCDM ports were extremely important in some old CDMA modems
that required them for control instead (or in addition to) the AT
ports, at least for several purposes like gathering access tech info
and such. Due to that, MM has been attempting QCDM probing by default
in all
> > I noticed that your Ubuntu focal PPA for modemmanager is failing builds for
> > armhf arm64
> > (https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-focal).
> >
> > Do you know what the issue is? I would love to be able to use these for the
> > various armhf/arm64 boards I
Hey Tim,
> I noticed that your Ubuntu focal PPA for modemmanager is failing builds for
> armhf arm64
> (https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-focal).
>
> Do you know what the issue is? I would love to be able to use these for the
> various armhf/arm64 boards I
mmcli we are getting same error as
> before (error :- modemmanager should in debug mode ).
> how we can proceed on these ?
>
> On Sun, Dec 6, 2020 at 1:17 PM Aleksander Morgado
> wrote:
>>
>> Hey
>>
>> > After board boots we are changing the Mo
Hey!
>
> Checking the timestamps of the mm daemon and libraries the build order was
> incorrect, looks like libqmi and mbim was built after MM so it wasn’t picked
> up as a dependency when running the configure.
Ahhh, see, that's also a good reason why we didn't see the cdc-wdm
ports probed :)
Hey,
On Fri, Dec 4, 2020 at 11:47 PM Enrico Mioso wrote:
>
> Hello!!
> I wanted to disable the radio interface on a device reported as:
> Bus 002 Device 003: ID 413c:81b6 Dell Computer Corp. DW5811e Snapdragon™ X7
> LTE
> I would have liked something equivalent to
> AT+CFUN=0
>
> but no serial
Hey
> After board boots we are changing the ModeManger.service as
> (ExecStart=/usr/sbin/ModemManager --debug)
> but that is not good practice.
>
> How We can run ModemManager in debug mode while compiling yocto image
> itself ?
> build platform = yocto
The --debug option gives you
Hey Marc,
> I am trying a new modem on my system and some weird things are happening.
> Trying to get the gps to come up but its not being shown as available but the
> mm debug shows there is a port there. Wondering how I can debug this to get
> it enabled ?
>
> ModemManager[248]:
Hey Carl,
> Quectel has lot of customers, and most of them are use system like
> openwrt, android, others embedded -linux.
> and the kernel version used is usually is V3.x,V4.x.
> it will spend very much time (for quectel-self and customers):
> if
Hey Rafal!
> Jan 1 04:51:00 zubrOS ModemManager[342]: [17460.859237] [filter]
> cdc-wdm devices allowed:yes
> Jan 1 04:51:35 zubrOS kernel: [ 54.178239] qmi_wwan_q 1-1:1.4: cdc-wdm0:
> USB WDM device
I saw your merge request and replied about that there, the problem you
had with
Hey Martin,
> > Download here:
> >
> > http://www.freedesktop.org/software/ModemManager/ModemManager-1.14.8.tar.xz
> >
> > Verify it:
> > $ sha256sum ModemManager-1.14.8.tar.xz
> > fe1a26ba51b4bda7abd09ad4dadedd87d8b8154809fc9d88e94f75fdfff19295
> > ModemManager-1.14.8.tar.xz
>
>
Hey hey,
This is the fourth bugfix release in the ModemManager 1.14.x series.
Overview of changes in ModemManager 1.14.8
---
* Build:
** Fixed distcheck with new gtk-doc releases.
** ModemManager-names.h was being included in the dist tarball, but
Hey all,
I've been working on several updates to the udev/generic backends in
the kerneldevice object. The main changes are done to better support
non-USB modems (e.g. the new PCI based modules), and most of the
changes are improvements and fixes in the generic backend used e.g. in
OpenWRT, to
Hey all,
I've reworked the core daemon logic related to device subsystems, see
changes and description in gitlab:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/388
The main purpose is to make it easier to introduce new subsystems
(e.g. rpmsg for qualcomm socs, or
Hey Giacinto,
> > > We're running 1.14.2 on a Cinterion (PLS62W) module.
> > >
> > > The modem is connected for a while and suddenly loses registration
> > > causing MM to start a forced disconnect of the bearer, but the attempt
> > > at disconnection fails.
> > >
> > > Oct 29 22:11:24.709516
Hey,
> The issue I am experiencing , which I don't know if it may be related with
> this, is that in some cases (even after a host system reboot) the
> ModemManager is not able to list my modem (mmcli -L), even though it is
> available in the system via lsusb command. I try to force a modems
Hey,
> We're running 1.14.2 on a Cinterion (PLS62W) module.
>
> The modem is connected for a while and suddenly loses registration
> causing MM to start a forced disconnect of the bearer, but the attempt
> at disconnection fails.
>
> Oct 29 22:11:24.709516 ModemManager[530]: [1604009484.709151]
Hey,
> Does this mean that modem like the Fibocom L860-GL (pcie modem) will now work
> with QMI and/or MBIM?
>
No, not yet.
It just means that the codebase will no longer assume all QMI ports
are from qmi_wwan and all MBIM ports are from cdc_mbim. Adding support
for PCIe modules is still
Hey Jessy
> I am working with some Cinterion modems (PLAS9) and have seen them lock up
> completely (requiring a hard reset as the AT channel does not even accept
> commands anymore).
>
> The reason I am posting about this here is that ModemManager doesn't realize
> the modem is gone. Every
Hey,
> We are giving AT command to EC20 module using ModemManager. Its working
> fine for most of the command , but while giving some AT commands, i am
> getting syntax error
> for eg.
> mmcli -m 0 --command="AT+QCFG="nwscanseq"
>
Using this should work:
mmcli -m 0
Hey,
> With the connection established (with NM and MM still disabled), running
>
> sudo qmicli --device=/dev/cdc-wdm0 --nas-get-system-info
>
> returns
>
> [/dev/cdc-wdm0] Successfully got system info:
> WCDMA service:
> Status: 'none'
> True Status:
Hey,
> Thank-you for your advice. We've managed to install version 1.14.2 with no
> further issues following the steps you outlined.
>
> Unfortunately, when using the software, we didn't quite get the result that
> we were hoping for - our modem reported capability is still only shown as
>
Hey Dani
>
> And repeated the installation with
>
> --libdir=/usr/lib/x86_64-linux-gnu/
>
Yes, this is the correct way to do it in Ubuntu.
i.e. ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu/
>
>
>
> CC mm-helper-enums-types.lo
>
> CCLD libhelpers.la
>
> /usr/bin/grep:
Hey,
> > > I seem we have done for "QMI based on QTRT" in libqmi.
> > > For QUALCOMM's data services, there are lots of QMI library,
> > > and libqmi used a more simply solution. (in fact, if just send QMI,
> > > QTRT is also not a good idea)
> >
> > Why do you say QRTR is not a
Hey,
> > > So the process can next:
> > > 1. rmnet physic driver probe, create netcard
> > > rmnet_usb0/rmnet_mhi0/rmnet_ipa0, and call register_rmnet_data
> > > 2. rmnet data driver create rmnet_data0
> >
> > Are you suggesting that there is always a virtual network
Hey Carl,
> Some ideas from me.
Thanks for your comments, very much appreciated.
> The discussion is based on QUALCOMM's rmnet driver and his data
> services.
> We are discussing how porting these software to MM and libqmi.
> But I think QUALLCOMM's solution is
Hey,
> > > And an additional question I have; what if we start using QMAP also
> > > for qmi_wwan based modems that support it? I think it would be very
> > > similar to your current needs with QRTR/IPA, right? See
> > > https://lists.freedesktop.org/archives/libqmi-devel/2018-July/002935.html
>
Hey Eric,
And an additional question I have; what if we start using QMAP also
for qmi_wwan based modems that support it? I think it would be very
similar to your current needs with QRTR/IPA, right? See
https://lists.freedesktop.org/archives/libqmi-devel/2018-July/002935.html
Maybe we can setup a
>
> ModemManager 1.10.8 on Ubuntu 16.04.4 LTS.
> Sierra Wireless EM74xx modem
>
> I had a test where I set the APN as invalid in the modem.
> After a few hours, the ModemManager daemon restarted owing to the
> following error.
>
> dbus[1001]: [system] Activating via systemd: service
>
Hey,
> > > It does mean that MM will have to instantiate net ports and
> > > then assign the mux ID to the QmiDevice, and then set it again in the
> > > Bind Mux Data Port message, which leaves room for those potentially
> > > getting out of sync.
> >
> > Why would this not be a problem in the
Hey!
>
> As part of the QRTR integration into MM we're trying to figure out
> whose responsibility it is to make rmnet_data net interfaces for a
> QRTR/IPA-based modem. I had started an MR[1] that gave this
> responsibility to libqmi, but it's not clear this is the right place
> for this to go.
>
Hey hey,
This is the third bugfix release in the ModemManager 1.14.x series.
It is a small update w.r.t. 1.14.4, fixing issues related to missing GError
initializations. The main fix that makes this release really needed is one in
the QMI modems facility locks loading logic (in the 1.14 branch
Hey hey,
This is the second bugfix release in the ModemManager 1.14.x series.
Overview of changes in ModemManager 1.14.4
---
* Location interface:
** Allow cell ID only updates.
* Messaging interface:
** Fixed memory leak when SMS parts being
Hey,
>
> I don't know location of the official librmnetctl repo. We are using snapshot
> from branch LC.UM.1.0 of
> https://source.codeaurora.org/quic/lc/chromiumos/third_party/librmnetctl
>
If we're looking at using just some netlink socket based operations,
and if there is no "official"
Hey Michał,
>
> Thank you for the reply. As you suggested I created MMPortRmnet to handle
> data port setup:
> https://gitlab.freedesktop.org/mkm/ModemManager/-/commit/b25310666e41a19150fe2b18ff3b7cce73f9129a
> It includes all the code that uses the rmnet library to configure devices but
> it
Hey,
> I'm working with a cinterion, PLS62W module and using PPP. One of the
> issues I run into is that in certain scenarios, like sudden loss of
> registration(due to poor signal) where MM disconnects the bearer, the
> primary data port (and at port) ttyACM0 becomes unusable.
> I think somehow
> The real issue that is leading me through all of these tests is improving my
> understanding of lifecycles when working with async MM functions. I want to
> make sure that there is no possible scenario where I destroy one of my C++
> objects that tracks a MMModem, in the destructor I cancel
Hey!
>
> Now I just need to understand why even when I call mm_modem_create_bearer and
> immediately cancel the GCancellable, My callback is called with the error
> "Operation was cancelled", but the bearer is still created. This is an
> unrelated issue, so I can create a new email thread on
501 - 600 of 2422 matches
Mail list logo
