On Fri, Feb 7, 2020 at 11:28 AM Martin wrote:
>
> On 2020-02-07 09:30, Aleksander Morgado wrote:
> > > I'm using a modem just for SMS, i.e. no mobile internet.
> > > Therefore, NM does not control my modem and maybe I will remove NM.
> > > I can set the pin u
Hey hey,
This is the third bugfix release in the ModemManager 1.12.x series.
Overview of changes in ModemManager 1.12.6
---
The list of changes in this version includes:
* SIM:
** Updated logic to avoid sending PIN/PUK to the SIM card when not require
> I'm noticing a (minor) issue in MM 1.12.4 release. The operator code is
> "53005" but leading "0" is missing in MNC field when displayed using
> -location-get command as below. I've noticed that if there are one or more
> leading zeros then both MCC and MNC do not report it. I've a test APN
Hey!
>
> It will be more useful to show correct carrier-configuration and revision.
> Currently it shows “default” and “—” for revision. Any suggestion how this
> can be done? Also find below !IMPREF AT Command which gives the carrier
> configuration/revision.
>
The carrier configuration/revis
Hey!
>
> any chance you have another look into this? I am ready to retest any further
> patch.
>
I bought one ME909s-120 from eBay, I should have it next week...
that's why I didn't bug you with more test requests.
--
Aleksander
https://aleksander.es
___
> >
> > any chance you have another look into this? I am ready to retest any
> > further patch.
> >
>
> I bought one ME909s-120 from eBay, I should have it next week...
> that's why I didn't bug you with more test requests.
>
Already got the device, and pushed a new commit to the MR. Could you re
Hey!
>
> In some private APNs, location assistance servers are not reachable or not
> needed. Is there a way to disable location assistance?
>
These are only used if A-GPS (MSA/MSB) is enabled, you can just enable
plain GPS instead on those locations.
--
Aleksander
https://aleksander.es
__
Hey Amol,
>
>
> Is there any way to disable XTRA location assistance? From where modemmanager
> receives assistance servers information? Is this comes from the modem? I see
> requests to download these files on cellular link. Who starts the download?
> Is it modemmanager or modem?
>
Are you re
Hey Adrien,
>
> I need your help to resolve a memory leak problem. I make some tests with a
> little and simple software:
>
> int main(int argc, char* argv[])
> {
>
> MMManager *manager;
> GError *error = NULL;
> GDBusConnection *connection = g_bus_get_sync(G_BUS_TYPE_SYSTEM, NULL,
>
Hey,
> There are no "memory leaks" per se; instead, there is memory that is
> allocated but it is still reachable at program exit. The blocks
> reported above are due to idle sources scheduled in the default
> GMainContext, looks like there is some "cleanup in idle" logic
> happening in the GDBusC
Hey hey,
This is the fourth bugfix release in the ModemManager 1.12.x series.
Overview of changes in ModemManager 1.12.8
---
The list of changes in this version includes:
* Plugin manager:
** Updated logic to allow new ports added to a device up to 15
Hey Adrien,
> > There are no "memory leaks" per se; instead, there is memory that is
> > allocated but it is still reachable at program exit. The blocks
> > reported above are due to idle sources scheduled in the default
> > GMainContext, looks like there is some "cleanup in idle" logic
> > happen
Hey Giacinto,
> I would like to add some Cinterion/Gemalto/Thales modems in
> ModemManager, and I have some questions:
Nice!
> - first of all, if code from the modem vendors are welcome
> - is there a procedure to submit commits? I see that on the gitlab
> page there are some pull requests. Is i
Hey,
For systems where there is usually one single object available, mmcli
still needed to provide the exact modem/sim index number or a fixed
UID setup by the user as a udev tag.
I've tried to hack up a simpler solution which I hope is even easier
to use; see
https://gitlab.freedesktop.org/mobi
Hey!
I've received a Fibocom FM150 5G module (thanks Fibocom!), and have
been able to integrate all the 5G related specific bits in
ModemManager, applicable to the default QMI modem implementation.
The integration includes a new 5GNR capability, a new 5G mode, and
also the possibility to select a
Hey!
See the following MR:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/263
It introduces per-object specific logging, so that e.g. all logs
generated by the same modem object are all prefixed with the same
"modemX" string, e.g.:
ModemManager[270221]: [158567497
Hey,
>
>
>
> I am trying to get a UART connected modem working with Modem Manager.
>
>
>
> When I run ModemManager in Debug I get this error
>
>
>
> Could not acquire the 'org.freedesktop.ModemManager1' service name
>
>
You need to stop the system-managed ModemManager before you run your
own ins
On Fri, Apr 3, 2020 at 8:09 PM Adeel Ahmed wrote:
>
> Maybe it is related to policykit blocking?
>
> On 4/3/20 10:08 PM, modemmanager-devel-requ...@lists.freedesktop.org wrote:
> > Could not acquire the 'org.freedesktop.ModemManager1'
>
No, this is because there is already a process owning the we
Hey,
>
> I now see that the port /dev/ttyAMA0 is not whitelisted.
>
>
>
> I found a post from an old mailing list on identifying the kernel driver and
> whitelisting it using this
>
>
>
> ACTION!="add|change|move", GOTO="mm_platform_device_whitelist_end"
>
> SUBSYSTEM!="platform", GOTO="mm_platfo
Hey Teijo,
> I'm working on a patch to detect M2M eUICC profile switches on Quectel
> modems. Upon testing with Quectel EG25, which uses QMI, I noticed that
> when MM reinitializes a modem (either due to hot-swap or MM restarting),
> some of the QMI CIDs don't appear to be released. After ~10 time
Hey!
> On 14.4.2020 17.55, Teijo Kinnunen wrote:
>
> > Possibly this could also be something in qmi-proxy side. I assume it is
> > expected that even after MM disconnects from it, it's supposed to
> > execute all queued QMI operations. Looking at the code, it seems that if
> > sending the respons
Hey Tim!
> When debugging the problems with Quectel EC25 I was getting this error:
>
> QMI protocol error (14): ''CallFailed'' call end reason (1):
> ''generic-unspecified'', verbose call end reason (3,1069): [cm] (null)
>
> These call end error codes seem to be documented here:
>
> https://devel
Hey!
I developed support for USSD actions in QMI modems using the Voice
interface. Tests and reviews welcome!
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/270
--
Aleksander
https://aleksander.es
___
ModemManager-devel
Hey Enrico!
>
> So, I was following this ML lately, to notice I am not the only one having
> the issue of modem not being able to establish a connection sometimes, with
> errors like "Call failed".
> I seen that error many times. I will for sure need to dig deeper into this,
> but my question w
Hey!
>
> I assume the "(tty/ttyUSB6) at port timed out 10 consecutive times" is a
> real error, for unknown reasons. What's worrying me is how it is
> handled. I do not expect the modem to disconnect and disappear from
> ModemManager due to an error like this, which seems to be related to the
> o
Hey!
> I am looking for a way to integrate the current telit GPS code in MM 1.12.x
> but on a LE910C1 that is currently using the qmi interface.
>
If you're using the modem in QMI mode, are you sure you don't already
have GPS control using either the LOC or PDS QMI services? Or does the
Telit mo
Hey!
> > Anyway, as you also said, having lost the AT port may indicate other
> > kinds of internal problems, so attempting to trigger a reset ourselves
> > wouldn't be that bad in this case? I'm open to suggestions on how to
> > best handle this. Until now ModemManager hasn't done too many contro
Hey Enrico,
> sorry for the intrustion and for going over this again but...
> You mentioned the Librem5 and it's use of MM.
>
Yes!
> I was wondering if I could use one of my QMI modems to do phone calls.
> I seen the voice interfaces, but audio routing remains a mistery to me even
> today. :)
>
Hey,
>
> I didn't found information in Telit documentation about the GPS control with
> QMI. I'll try to poke them directly. On the other side, I did enable the gps
> with success using mmcli but didn't had any data location under the
> --location-get command.
> Here is the log when I do the co
ing commit:
commit 28869463a1f93d980c72ae4e8c7997c9be899535
Author: Aleksander Morgado
Date: Tue Dec 3 09:55:07 2019 +0100
iface-modem: allow Command() while in Failed state
Allow the generic command API while in FAILED state, in case the modem
integrator has some special commands to re
Hey!
> So, due to some issues I will have to rewrite my code from scratch anyway.
> And so this time I am doing it with a different use-case in mind.
>
> I should monitor incoming and outgoing voice calls for a modem. How may I
> manage objects lifetime, assuming ModemManager and the modem may d
Hey,
> What do you mean by a "signel GObject"? A list ? Or building a new GObject
> type on my own?
>
I mean a new GObject type of your own.
> And, secondly, is there a way to obtain the audio port from MM? In my setup,
> ttyUSB0 and ttyUSB2 are marked as AT port, audio is ttyUSB1.
>
If you k
Hey,
See comments below.
>
> I am newbie in the ModemManager world.
> I am developing a router which has 5G Modem as one of WAN I/F.
>
> The WAN I/F works now with a modem vender's CM software.
> But we want our product to be independent from specific modem H/W.
> So I guessed utilizing ModemMana
Hey Enrico,
>
> So - i was considering using a GList of my own structs to track down objects
> and maintain it when observing state transitions.
> Now I was wondering how to manage:
> - async operation concurrency: am I guaranteed only a single async operation
> runs? Or should I lock somehow th
Hey Enrico,
>
> Gegarding audio ports- in udev I can't find any hint about the device I am
> currently using for testing, a Huawei E3131 dongle.
> Should I tag the audio port myself like I see in other cases?
Yes please, and send us a patch either via email or gitlab so that it
can be included i
Hey!
> After digging for documentation with no success, I migrate the location
> interface to mm-shared-telit and added a qmi interface for the telit plugin.
> For the merge request, would it be OK to merge that kind of changes in 1.12
> or it must me on master for the next release?
>
The merg
Hey!
> >
> > > After digging for documentation with no success, I migrate the location
> > > interface to mm-shared-telit and added a qmi interface for the telit
> > > plugin. For the merge request, would it be OK to merge that kind of
> > > changes in 1.12 or it must me on master for the next
Hey,
> I retested my linux box with your recommendation and got a log message.
> I attach the log file in this email but I wonder if the attached file can be
> uploaded to the maillist also..
>
> I used the device path you suggested -
> "/sys/devices/platform/1a0c.usb/usb2/2-1 ".
> And I add
Hey
>
> From the log file I uploaded/attached, I found one problem.
> Our modem talks with a specific settings - /dev/ttyUSB1, baudrate:115200,
> parity:none, data:8, stop:1, flow:xon_xoff.
> But ModemManager tried with baudrate 57600 only.
>
You need to add udev tags to configure the baudrate a
Hey!
> I would like to ask some advice for Voice calls handling.
> I will at some point get a MMModemVoice to which I'll connect some GSignals
> to keep track of when new call objects are added and removed (e.g.: via
> mmcli).
> My callbacks will be invoked with the MMModemVoice object as argume
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 using the QMI protocol
> > (i.e. without your changes) but enabling both "nmea" and "raw"
> > locations?
> > Also,
Hey,
> Let me provide some additional information and new test log messages.
>
> The problem I reported is improved one setp. Originally it was like:
>root at LEDE:~# mmcli -L
>error: couldn't create manager: Timeout was reached
>
> Now it is like:
>root@LEDE:~# mmcli -L
>No modems
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 deta
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 be
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"
> > > > loca
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 y
s 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
>
>
> On Thu, 7 May 2020, Enrico Mioso wrote:
>
> > Date: Thu, 7 May 2020 15:59:44
> > From: Enrico
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 gathe
Hey,
> > > > > > 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"
Hey David,
> > Could you clone and build the following libqmi branch?
> > https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/115
> >
> > Once you have it, you'll be able to configure the NMEA traces via qmicli,
> > e.g.:
> > $ sudo qmicli -d /dev/cdc-wdm1 -p --loc-set-nmea-ty
Hey hey,
This is the fifth bugfix release in the ModemManager 1.12.x series.
Overview of changes in ModemManager 1.12.10
---
The list of changes in this version includes:
* mmcli:
** Add missing 'allowed-auth' bearer property in the output.
** Remo
Hey,
>
> root@localhost:~# mmcli -b 2
>
> General| dbus path:
> /org/freedesktop/ModemManager1/Bearer/2
> | type: default
>
> Status | connected: yes
>
Hey!
On Thu, May 14, 2020 at 4:36 PM Zahari Petkov wrote:
>
> Hi,
>
> We are facing an issue with a Quectel EC21-A module and Twilio SIM cards
> using ModemManager v1.12.8. I found similar error logs with Soracom SIM cards
> and other Quectel modems as well.
>
> A new and freshly activated Twil
Hey!
> I am trying to update the code for the Radio/Bands of Cinterion
> modules, and it seems a nasty job, because of the way the indicators
> evolved.
> Today in the code there is a parser for this format (only for the test part):
> AT^SCFG=?
> ...
> ^SCFG: "Radio/Band",("1-479",
Hey,
> > > I am trying to update the code for the Radio/Bands of Cinterion
> > > modules, and it seems a nasty job, because of the way the indicators
> > > evolved.
> > > Today in the code there is a parser for this format (only for the test
> > > part):
> > > AT^SCFG=?
> > > ...
> > >
Hey!
> > > > root@localhost:~# mmcli -b 2
> > > >
> > > > General| dbus path:
> > > > /org/freedesktop/ModemManager1/Bearer/2
> > > > | type: default
> > > >
> > > > Status
Hey,
> On Fri, May 15, 2020 at 9:02 PM Aleksander Morgado
> wrote:
> >
> > Hey,
> > > > > I am trying to update the code for the Radio/Bands of Cinterion
> > > > > Today in the code there is a parser for this format (only for the
> > > &g
Hey,
> > > > > > > I am trying to update the code for the Radio/Bands of Cinterion
> > > > > > > Today in the code there is a parser for this format (only for the
> > > > > > > test part):
> > > > > > > AT^SCFG=?
> > > > > > > ^SCFG: "Radio/Band",("1-479","0-1")
> > > > > > >
> > > > > >
Hey,
> > > > > > > > > I am trying to update the code for the Radio/Bands of
> > > > > > > > > Cinterion
> > > > > > > > > Today in the code there is a parser for this format (only for
> > > > > > > > > the test part):
> > > > > > > > > AT^SCFG=?
> > > > > > > > > ^SCFG: "Radio/Band",("1
Hey!
> I'm now developing my application with ModemManager.
> I want to add a feature that can directly assign which plugin to use for my
> modem. Instead of using the filter to match appropriate plugin.
>
I'm not totally sure we'd like to support this, truth be told. The
different available plu
Hey Giacinto,
> I have finally submitted a merge request for the band reading and
> setting for Cinterion Modems.
>
> Not sure whether is it good quality, thou. I would appreciate a review
> and comments.
> Starting for example from the naming of the udev variable, and then
> the use of other vari
Hey
>
> I am experiencing a strange issue with state-changed GSignal of MMCall object.
> In particular, my user-data is not passed, instead a pointer with an address
> like 0x01, at least so it seems via GDB.
>
> I connect my GSignal this way:
> call_statechange_signal = g_signal_connect(c, "stat
Hey,
> I'm trying to get the GPS data from my modem, but I receive "strange"
> character as output:
>
> mmcli -m 0 --location-status
>
>Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea,
> agps-msa, agps-msb
> | enable
Hey,
>> > I'm now developing my application with ModemManager.
>> > I want to add a feature that can directly assign which plugin to use for
>> > my modem. Instead of using the filter to match appropriate plugin.
>> >
>>
>> I'm not totally sure we'd like to support this, truth be told. The
>> dif
Hey!
--
>GPS | nmea: ¤ÅAΦUiΔΠ,,1aBéØΠ,X0aBEΓΩ5f4P
> | ¤ÅA:t(ΔΠ,X0aBéøΠ,X0aBéØΠ*lXi
> | ¤ÅA2Ej_Π,(1aRÇØΠNX0YDEΓΩ2ù5P
> Λ | ¤ÅA:4*ΔΠAXDaBéØΠ,X0aBéØΠ,X0a"%L"
>
>
How did you
Hey!
> ./configure --prefix=/usr --disable-static && make
> sudo checkinstall --install=no
> sudo dpkg -i libqmi_1.24.12-1_amd64.deb
>
> but during the install I got this error:
> dpkg: errore nell'elaborare l'archivio libqmi_1.24.12-1_amd64.deb (--install):
> tentata sovrascrittura di "/usr/bin
Hey!
> I am experiencing a crash in Modemmanager, triggered by the following
> scenario:
> 1 - Start a voice call from mmcli to my mobile phone.
> 2 - Answer the call there.
> 3 - From the mobile phone, call back my Huawei E3131 device.
>
> This results in the following crash: let me know if I ca
Hey!
> Can you please suggest what is best way to change SIM card when using mmcli?
> My task is to execute some USSD codes on as many SIM cards as
> possible, I tried to use script with --3gpp-ussd-initiate and
> --3gpp-ussd-respond and it works, but I don't know how to change SIM
> card as fast
Hey!
> Devices you have mentioned look like embedded/oem solutions.
> Do you know of any consumer grade USB modems with SIM hotplug and
> modemmanager support?
Nope I'm sorry, I don't right away.
> You have also mentioned AT commands, are they standard or vendor specific?
Telit uses AT#QSS whic
Hey Enrico,
> > I am experiencing a crash in Modemmanager, triggered by the following
> > scenario:
> > 1 - Start a voice call from mmcli to my mobile phone.
> > 2 - Answer the call there.
> > 3 - From the mobile phone, call back my Huawei E3131 device.
> >
> > This results in the following crash
Hey,
> Thank you very very much for your great work, as always Aleksander.
>
>
> BTW- maybe something interesting is happening here:
> [mrkiko@mStation ~]$ mmcli -o 44 --start
> error: couldn't start the call:
> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: Couldn't start
> the c
Hey,
> Therefore I thing there must be something wrong with my memory
> management in the new code, but I don't see where, nor Aleksander's
> review highlighted some problems in that sense.
>
Once I review the new changes you do, I'll take a look with memory
management in mind to see where the is
> > BTW- maybe something interesting is happening here:
> > [mrkiko@mStation ~]$ mmcli -o 44 --start
> > error: couldn't start the call:
> > 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: Couldn't
> > start the call: Unhandled response '^CCALLSTATE: 1,4''
> >
> > but in reality cal
Hey Alex
> I have been trying to add support for the Quectel EM20-G LTE modem on
> openwrt, using a similar method to how the support for the RM500Q modem
> was implemented. I made changes to the qmi_wwan driver using the
> attached patch (which also has backported changes for the RM500Q).
>
Not
Hey!
> sorry for the disturbance.
>
> when answering calls with the Huawei E3131, I experience an assertion failure:
> ERROR:mm-iface-modem-voice.c:1923:in_call_setup_context_step: code should not
> be reached
>
> full log including some personal data attached :D
> Using ModemManager git HEAD at
Hey all,
I'm going to suggest we change the filter policy to 'strict' when none
explicitly requested. In the past 1.12 release we already suggested
distributions to request 'strict' explicitly, so it's probably a good
idea to move on and just make it the new default for 1.14.
Under the 'strict' f
Hey,
On Wed, Jun 3, 2020 at 9:51 PM Alex Ballmer wrote:
>
> I have noticed that Sierra Wireless MC4755 modems can operate in both
> QMI and MBIM modes. Modemmanager seem to try to use the modem as-is in
> whatever mode it is currently operating in.
>
> However, some features are only available in
Hey hey!
This is the first release candidate for the next 1.14 stable version. There are
important packaging changes involved, so this RC is mainly targeted for
downstream package maintainers; please test your packaging updates and report
issues, if any found.
The main packaging updates are th
Hey!
> I am facing an unexpected - as far as I can tell - behavior with ModemManager
> 1.12.8 and network manager is 1.22.10 on Ubuntu 20.04, the modem is LE910 V2.
>
> During and ongoing connection, lasting since 38 minutes, the tty port is
> force closed after the following message
>
> (t
Hey!
>> I thought this should have been fixed in
>> 5f29bd64de8127cb326488d68a2a2b64a45e1f45, but I don't see the relevant
>> "PPP is required for connection, will ignore disconnection reports"
>> message that should happen once the modem gets connected in PPP mode.
>>
>> If you have the setup wit
Hey Martin,
> what happened to mm_common_build_capability_combinations_any()
> in 1.13.900? Does libmm-glib need a soname bump?
>
The "mm-common-helpers.h" file is not really part of the API, it's not
even installed, so I've kind of felt safe updating that implementation
without caring much about
Hey Giuseppe,
> I am not at all an expert of modem manager but I hope this is the right
> place where to post my question.
>
> I am trying to use a WWAN module on a laptop. The module is named "Dell
> Wireless 5570 HSPA+ (42Mbps) Mobile Broadband Card" (a.k.a. Sierra
> Wireless AirPrime 7W5P6).
>
>> Could it be that the log is really from a MM 1.10 run instead of a MM
>> 1.12 run? The fix to ignore disconnection reports when PPP is used was
>> only added in MM 1.12.0 IIRC.
>>
>
> that was indeed the case, problem solved! :D
>
Nice! thanks for checking
--
Aleksander
https://aleksander.es
Hey!
>
> but it seems the ID_MM_CANDIDATE variable isn't there.
>
> $ udevadm info /dev/cdc-wdm0
> P: /devices/pci:00/:00:1d.0/usb3/3-1/3-1.6/3-1.6:2.12/usbmisc/cdc-wdm0
> N: cdc-wdm0
> L: 0
> E:
> DEVPATH=/devices/pci:00/:00:1d.0/usb3/3-1/3-1.6/3-1.6:2.12/usbmisc/cdc-wdm0
> E: DE
Hey,
> > $ udevadm info /dev/cdc-wdm0
> > P: /devices/pci:00/:00:1d.0/usb3/3-1/3-1.6/3-
> > 1.6:2.12/usbmisc/cdc-wdm0
> > N: cdc-wdm0
> > L: 0
> > E: DEVPATH=/devices/pci:00/:00:1d.0/usb3/3-1/3-1.6/3-
> > 1.6:2.12/usbmisc/cdc-wdm0
> > E: DEVNAME=/dev/cdc-wdm0
> > E: MAJOR=180
> > E
Hey Brian,
> I am using Sierra Wireless MC7455 modems and randomly when I try to create a
> bearer I get the error
> GDBus.Error:org.freedesktop.ModemManager1.Error.Core.WrongState: modem in
> unknown state. Once I get this error all commands besides getting
> information give either this err
Hey,
>
> Taken following logs from ModemManager daemon for NOTE 2 ##
> LOG attached with the mail ..
>
The logs are missing the "device probing phase". Could you attempt to
gather them again but this time including the full sequence since the
ports are detected, not just the enabling ph
Hey,
> Jun 20 00:28:02 tcs-imx6 ModemManager[568]: [1592612882.225945]
> (ttyUSB2): --> 'AT+CEMODE?'
> Jun 20 00:28:02 tcs-imx6 ModemManager[568]: [1592612882.245189]
> (ttyUSB2): <-- '+CEMODE: 1OK'
> Jun 20 00:28:02 tcs-imx6 ModemManager[568]: [1592612882.247212]
> (ttyUSB2) device open cou
Hey,
> Yes, No GPS capabilities reporting by mmcli ...
> mmcli -m 0 --location-status
>
> Location | capabilities: 3gpp-lac-ci
>| enabled: 3gpp-lac-ci
>| signals: no
>
>
> mmcli -m 0 --location-enable-gps-nm
Hey
On Sat, Jun 20, 2020 at 3:39 PM Ramu wrote:
>
> I applied patches you mentioned for UDEV tags ... Seems to be working now..
>
> mmcli -m 0 --location-status
>
> Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, gps-unmanaged
>| enabled: 3gp
Hey,
> > Anyway, FWIW, I'd explore the PCIe driver option first if I were you.
> > That's the only mode tested by anyone, so it is more likely to work.
> Is there anybody reading this willing and knowlegable enough to work on
> a kernel driver for inclusion in mainline? I'm able to provide funding
Hey hey,
This is the sixth bugfix release in the ModemManager 1.12.x series.
Overview of changes in ModemManager 1.12.12
---
The list of changes in this version includes:
* Voice interface:
** Fix assertion in call setup/teardown logic.
* Plugins:
Hey hey,
This is a new major release of ModemManager, which will be the base for the
1.14.x stable series (the new "mm-1-14" branch in git). The release has been
tagged as "1.14.0".
Thanks to everyone involved!
ModemManager 1.14.0
---
The following note
Hey,
> It seems that my modem supports pretty much all modes:
>
> Modes| supported: allowed: 2g; preferred: none
>|allowed: 3g; preferred: none
>|allowed: 2g, 3g; preferred: 3g
>|allowed:
Hey Leo,
> It's the BroadMobi BM806U (Qualcomm MDM 9225) and I suspect it was taken out
> from a D-Link DWR-921 C3:
>
> https://openwrt.org/toh/d-link/d-link_dwr-921#tab__revision_c3
>
> It only has the cdc-wdm0 and wwan0 ports.
>
> I was able to enable the LTE-FDD band 1, 3 and 8 earlier but now
Hey
>
> I am using a ModemManager - 1.8.4 ( Ubuntu 16.06.4) running on a Sierra
> Wireless EM74xx modem.
>
> I am starting the ModemManager with --paranoid argument to blacklist some of
> the ports in the udev.
>
> But when the ModemManager starts up I get the following error message.
>
> db
Hey Friedrich,
>
> While looking around for information about ModemManager, I stumbled
> upon some formatting mistakes on
> https://www.freedesktop.org/software/ModemManager/man/latest/mmcli.1.html:
>
> * In the "EXAMPLES" section, the shell sessions are lacking newlines;
>
> * In the "SEE ALS
Hey Tim,
>
> Could you add Ubuntu focal builds (including armhf and arm64) to your
> modemmanager/libqmi/libmbim Ubuntu PPA's for stable builds?
>
Yes, it's in my TODO list. I also have to update the older release
PPAs with the latest stables.
--
Aleksander
https://aleksander.es
___
Hey!
>
> We’re facing a problem where ModemManager (v1.10.0) doesn’t respect the
> allowed modes when the modem (Quectel BG96) fails to connect the first try.
>
> First, we set the allowed modes to 4G (--set-allowed-modes=4g) which works.
> We verified this by running AT+QCFG=“nwscanmode” which
Hey!
> > We’re facing a problem where ModemManager (v1.10.0) doesn’t respect the
> > allowed modes when the modem (Quectel BG96) fails to connect the first try.
> >
> > First, we set the allowed modes to 4G (--set-allowed-modes=4g) which works.
> > We verified this by running AT+QCFG=“nwscanmode
201 - 300 of 2974 matches
Mail list logo
