Hey Bruce,
Adding Bjørn in CC
> I never saw a response on this question, but I finally figured out --
> with some assistance from a Quectel engineer -- that the error is a
> kernel error related to USB communication with the modem as everything
> is being shut down for the reboot, and that ModemM
> ModemManager[16118]: [1724536442.509495] [plugin-manager] task
> 1,ttyACM0: found '8' plugins to try
> ModemManager[16118]: [1724536442.509503] [plugin-manager] task
> 1,ttyACM0: will try with plugin 'nokia'
> ModemManager[16118]: [1724536442.509510] [plugin-manager] task
> 1,ttyACM0: will try
Hi,
>
> I have a dual SIM IOT device which was running modem-manager 1.10 on Ubuntu
> 16.04. Recently upgraded to modem-manager 1.20.0 on Ubuntu 22.04.
>
>
>
> When switching from the first slot to the second slot, modem-manager is stuck
> with 3GPP status "registered" with the warning messages
Hey,
> I would really appreciate it if someone could clarify the license of the
> introspection XMLs, since there is no license declaration in those files.
>
> I am trying to build a cli tool querying information from ModemManager over
> dbus and am wondering what my license choices are in order
> we have been having issues with SimCom SIM7100E and MM since at least version
> 1.20.5 (even older maybe, we have reports MM 1.18.4 works ok).
> Have also tried using latest dev releases (MM 1.23.9, MBIM 1.31.5, QMI
> 1.35.5) but the modem still fails to function correctly.
> I have created thi
I never saw a response on this question, but I finally figured out --
with some assistance from a Quectel engineer -- that the error is a
kernel error related to USB communication with the modem as everything
is being shut down for the reboot, and that ModemManager has no direct
link to the iss
Hi Aleksander,
I followed-up on
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/874
and the problem seems to be resolved in newer version.
Specifically, I backported these 2 patches:
https://github.com/balena-os/meta-balena/pull/3478/commits/2d53d2cb60a155ece0563fbb39629056e2c
Thanks. I will do some checks on the latest MM devel release on Simtech
modems, we have reports 1.22.0 is broken on these modems but I need to get
the hw first to do some testing before I report back here.
On Thu, Aug 1, 2024 at 12:33 AM Aleksander Morgado <
aleksande...@chromium.org> wrote:
> He
Hi Aleksander,
Hey
>
> > I hope someone can help shed some light onto this issue as I am at a
> loss.
> >
> > I am investigating an issue that is occurring in a few IoT devices where
> either the modem has trouble registering to the network or it is being
> rejected shortly after a data connection
El 31/7/24 a las 10:37, Aleksander Morgado escribió:
Hey Alex,
On Mon, Feb 19, 2024 at 2:31 AM Alex Villacís Lasso
wrote:
El 16/2/24 a las 17:48, Alex Villacís Lasso escribió:
I have this old phone, a Samsung E3210B pre-Android feature phone that
I wish to use as a fallback option when (more
Hi Dominik,
Your issues might be related to the introduction of QMI PCO in
ModemManager 1.20 commit af9b6d4f [8]. If no valid PCO information is
returned, you'll get the mm_utils_bin2hexstr assertion error, which was
later fixed in ModemManager 1.20.6, see #740 (comment 1963193) [9].
So runn
Hi Félix,
Il giorno mer 31 lug 2024 alle ore 17:12 Félix R.
ha scritto:
>
> Hi,
>
> I hope someone can help shed some light onto this issue as I am at a loss.
>
Did you already get in touch with Telit technical support?
I think that this could be better analyzed looking at modem debug traces.
Hey Florin,
> I followed-up on
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/874 and
> the problem seems to be resolved in newer version.
> Specifically, I backported these 2 patches:
> https://github.com/balena-os/meta-balena/pull/3478/commits/2d53d2cb60a155ece0563fbb
Hey Alex,
> >
> > On Mon, Feb 19, 2024 at 2:31 AM Alex Villacís Lasso
> > wrote:
> >> El 16/2/24 a las 17:48, Alex Villacís Lasso escribió:
> >>> I have this old phone, a Samsung E3210B pre-Android feature phone that
> >>> I wish to use as a fallback option when (more frequently than I would
> >>
Hey,
>
> Is there a way to set a default SIM slot?
>
> I have a OpenWrt device with an eUICC (slot 1) and UICC-slot (slot 2). The
> eUICC is always selected as the active slot on boot (but does not work).
> Switching the slot generally works, but no connection can be established:
> "device not
Hey
> I hope someone can help shed some light onto this issue as I am at a loss.
>
> I am investigating an issue that is occurring in a few IoT devices where
> either the modem has trouble registering to the network or it is being
> rejected shortly after a data connection is established. I'm tr
On Wed, Jul 31, 2024 at 5:12 PM Florin wrote:
>
> Hi all,
> we updated MM and QMI to the above versions and now the Quectel EC25 modem
> won't work anymore.
> Previously, with MM 1.20.6 and QMI 1.32.4 the modem functioned correctly.
>
> At system start, the modem fails to get initialized, and MM
Hey Martin!
>
> Now enabling does not lead to an error message anymore, but the modem
> still seems to have problems, as it remains in the "searching" state:
>
If it needs to fallback to 2G it may take a while, did you wait long
enough? I realize your email is >1month old, were you able to move
t
Hey!
> From a quick look at src/mm-broadband-modem-qmi.c ModemManager now seems to
> use DMSSetEventReport to enable indications for OperatingMode which is not
> supported by older devices.
>
We should never break support for older devices, at least that is the
target! If anyone ever sees a modem
Hey!
>
> It seems the disable command is not much different than
> "--simple-disconnect". The disable command as it stands today is a bit
> misleading because it gives an impression that modem is disabled (the state
> is reported "disabled" in mmcli -m 0 output) but modem is actually still
> r
em is actually still registered on a network.
Amol
From: Daniele Palmas
Sent: Friday, July 19, 2024 4:00 PM
To: Amol Lad
Cc: ModemManager (development)
Subject: Re: mmcli --disable command
Hi Amol,
Il giorno sab 13 lug 2024 alle ore 08:50 Amol Lad ha scritto:
&g
Hi Amol,
Il giorno sab 13 lug 2024 alle ore 08:50 Amol Lad ha scritto:
>
> Hi,
>
> I'm trying this with ModemManager release 1.22.0 with Telit FN990A28 modem
> (but it might be true for other modems as well).
>
> # mmcli -m 0 --disable
> successfully disabled the modem
> # mmcli -m 0 --command=A
El 3/3/24 a las 03:14, Aleksander Morgado escribió:
Hey Alex,
On Mon, Feb 19, 2024 at 2:31 AM Alex Villacís Lasso
wrote:
El 16/2/24 a las 17:48, Alex Villacís Lasso escribió:
I have this old phone, a Samsung E3210B pre-Android feature phone that
I wish to use as a fallback option when (more f
Hi Reinhard, hi Dylan,
On 2024-06-17 22:47, Reinhard Speyerer wrote:
> if your use case is SMS only you could try to make ModemManager ignore the
> QMI port similar to what is done in 77-mm-zte-port-types.rules for another
> ZTE device and see if it gets you any further.
Thank you! The following
On Sun, Jun 16, 2024 at 03:52:08PM +, Martin wrote:
> Hi,
>
> On 2024-06-16 17:00, Dylan Van Assche wrote:
> > It would be useful to mention the name of the modem and manufacturer
> > as a lot of modems identify themselves as QUALCOMM INCORPORATED, even
> > though they are made by other manufa
Hi,
On 2024-06-16 17:00, Dylan Van Assche wrote:
> It would be useful to mention the name of the modem and manufacturer
> as a lot of modems identify themselves as QUALCOMM INCORPORATED, even
> though they are made by other manufacturers.
It is an USB dongle, saying "Vodafone Mobile Connect" and
Hi,
On 16/06/2024 16:46, Martin wrote:
Hi,
this used to work long time ago on Debian 10 or 11, but now on
Debian 12 (modemmanager 1.20.4-1, libqmi-glib5 1.32.2-1), I get:
$ sudo mmcli --modem=0 --messaging-list-sms
error: modem not enabled yet
$ sudo mmcli --modem=0 --enable
error: couldn't en
I appreciate the responses. The resolution turned out to be that when I enabled
serial support in the kernel and in the OpenEmbedded recipe for ModemManager, I
didn't also explicitly enable QMI in the ModemManager build. Adding that, I
believe the parameters OE sent to configure were:
--with-at
Hey Bruce,
Thanks to everyone who joined the discussion, all the points already
raised are valid. Just some small notes from my side.
>
> I have a question about using both QMI and the serial interface with
> ModemManager.
>
> I had little difficulty getting ModemManager's SimpleModem to connect
Hey,
>
> I am in the same situation and my Quectel BG770A-GL modem is using the
> EMUX instead of the standard CMUX mode.
>
> Quectel is only providing full PPP support for this EMUX mode and so
> would like to know what could be
> the best way to add support for thoses /dev/pts virtual devices in
Hello,
I am in the same situation and my Quectel BG770A-GL modem is using the
EMUX instead of the standard CMUX mode.
Quectel is only providing full PPP support for this EMUX mode and so
would like to know what could be
the best way to add support for thoses /dev/pts virtual devices in MM
I've seen this firmware bug before. AT&T uses the default eps bearer for
Internet connectivity and the default setting in quectel's firmware is
incorrect for most subscriptions.
Setting the default bearer apn to an empty string before enabling the modem
fixed this for me.
On Tue, Apr 23, 2024, 09
Hi Bruce,
You can use ModemManager's API to set APN. ModemManager will do it using
QMI protocol and there should be no need to send additional AT
command unless you're doing something more custom not handled by
ModemManager.
I've been using Quectel (EG/EC) modems over USB with ModemManager and as
Thanks Aleksander!
The fix works.
Amol
From: Aleksander Morgado
Sent: Monday, April 22, 2024 2:35 PM
To: Amol Lad
Cc: ModemManager (development)
Subject: Re: SIM PIN Unlock Error in MM 1.22.0
Hey Amol,
>
> We are getting following error when trying t
On Fri, Apr 19, 2024 at 04:39:46PM +, Bruce Johnson wrote:
> I have a question about using both QMI and the serial interface with
> ModemManager.
>
> I had little difficulty getting ModemManager's SimpleModem to connect to
> T-Mobile (USA) using a Quectel EG25-G, but we found that modem wasn
Hey Amol,
>
> We are getting following error when trying to send pin to the SIM card. The
> problem is not observed in MM 1.20.4. However, please note that the SIM card
> does unlocks after the below command even though error is reported.
>
> # mmcli -i 0 --pin=1234
> error: couldn't send PIN co
Hey,
Sorry bother you again. In our local another PC, the way previous I used
> don't work by method 'sudo systemctl start ModemManager'.
> But command method 'sudo ModemManager' works.
> There are 2 attachments for reference.
> ModemManager.log was generated by command
> 'sudo ModemManager --de
Hi Aleksander,
Thank you for all the explanations. I wasn't aware the initial EPS bearer
needs to be configured separately. Your guesses about the empty APN were
right, I can see:
# qmicli -d /dev/cdc-wdm0 -p --wds-get-lte-attach-pdn-list
Attach PDN list retrieved:
Current list: '1'
Pending list:
On Tue, Apr 9, 2024 at 11:28 AM Garfield Watkins
wrote:
>
> Is there any other workaround you can suggest ? I really do need these
> virtual terminals exposed by the multiplexer.
>
Without adjusting MM to support the specific use case of the ptys, I'm
not sure there is any easy way to handle thi
Is there any other workaround you can suggest ? I really do need these
virtual terminals exposed by the multiplexer.
On 4/9/24 11:24, Aleksander Morgado wrote:
Hey
No unfortunately they are not. They (the psuedo terminals) are created by
opening /dev/ptmx which creates a terminal(s) in /dev
Hey
>
> No unfortunately they are not. They (the psuedo terminals) are created by
> opening /dev/ptmx which creates a terminal(s) in /dev/pts/ . These are not
> enumerated in any way. Oh well... let me try your suggestion and see if it
> works.
>
If the ptys don't have an entry in sysfs, not
associated
> with the old device name, remove the old name from the modem, and add the new
> name. I could make the replacement logic into a function to keep the code
> more readable if you would prefer.
>
Aren't we fully re-probing the modem from scratch upon the net
interfac
No unfortunately they are not. They (the psuedo terminals) are created
by opening /dev/ptmx which creates a terminal(s) in /dev/pts/ . These
are not enumerated in any way. Oh well... let me try your suggestion and
see if it works.
On 4/9/24 11:05, Aleksander Morgado wrote:
On Tue, Apr 2, 202
On Tue, Apr 2, 2024 at 3:43 PM Garfield Watkins
wrote:
>
> Unfortunately there doesn't seem to be a way for to write a udev rule against
> a pseudo terminal...
>
Are they not notified via udev really?
You could also try to set it up with ModemManager not running with
udev support (--test-no-ude
Hey!
>
> First of all I wanted to say thanks for developing and supporting a great
> piece of software.
>
Thanks to you for using it!
> We have a few thousand devices running ModemManager 1.18.6 and Quectel EC21
> modem. Our service provider Twilio/Kore keeps reporting that on some devices
>
Hey Radu,
>
> I attached 1 OK log (ModemManager-1.23.4-ok.log - git
> 6a8797927c1ef9df1f56513b742f01de86f5167f), and one not ok log
> (ModemManager-1.23.5-nok.log git 6388b583c7b9c25d3061a070f54f9d97d59e2b2c).
>
> Please let me know if I can be of any help.
> Radu
>
I looked at the two logs and
Unfortunately there doesn't seem to be a way for to write a udev rule
against a pseudo terminal...
On 3/8/24 11:31, Aleksander Morgado wrote:
Hey Garfield,
I have a situation where I have a ublox modem, the LISA u200, wired up using
its SPI bus as the communication channel. On the DTE side i
Sorry for the late reply,
I completely understand why there may be concerns at editing such critical
code for a use case that is not very common.
Unfortunately my current situation requires renaming the interfaces.
Multiple modems may take turns being 'selected' (having the interface
renamed) to
Hey!
This is strange, but possible, because I did touch device probing
between those two releases. Could you send a MM debug log with your
failed modem detection using git main?
On Tue, Mar 26, 2024 at 10:05 PM Radu C wrote:
>
> Hi,
>
> As a test I tried the latest MM (git SHA-1
> 6388b583c7b9c
Vodafone (21401).
I don't have the 3GPP knowledge about this at hand, but I'd guess that
no-suitable-cells-in-location-area instructs the modem not to attempt
registering with the network any more.
Can you try to repeat the test, but once re-enabling the SIM card, run an
airplane mode cy
Thanks, Aleksander for your reply, I will check with them.
BR,
Ankur
On Fri, Mar 8, 2024 at 3:06 PM Aleksander Morgado
wrote:
> Hey Ankur,
>
> >
> > I want to report an issue with the modem manager in Ubuntu 22.04. Even
> though the modem firmware is updated, the modem manager service causes
>
Hello Artem,
> I am trying to get SIMCOM A7602E-H modem to work with ModemManager 1.14.12
> and the problem is the modem hangs after some time unless power cycled. If I
> disable ModemManager, the modem is working for a long time.
>
Any chance you can get MM debug logs to see if any of the requ
Hey,
>
> Recently I have encountered an issue related to reconnecting cellular.
>
> *OS*: Raspian OS Lite (32 bits) -> Linux panells3 6.1.0-rpi7-rpi-v8 #1
> SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux
> *Modem*: SIM7600G-H
>
> The SIM is active. Using mmcli I can see that th
Hey,
>
> Still having serious issues with this issue..
>
> Is there any insight where the QMI errors are coming from? Is it the modem
> that is telling MM that there is something wrong?
>
The errors start to happen when we try to read information from the
SIM card. The first problem in the debug
Hey Ankur,
>
> I want to report an issue with the modem manager in Ubuntu 22.04. Even though
> the modem firmware is updated, the modem manager service causes frequent
> disconnection issues. However, when I disable the modem manager service and
> use qmicli and minicoM methods, the modem works
Hi Aleksander,
Thanks for your reply.
I want to report an issue with the modem manager in Ubuntu 22.04. Even
though the modem firmware is updated, the modem manager service causes
frequent disconnection issues. However, when I disable the modem manager
service and use qmicli and minicoM methods,
Hi,
Still having serious issues with this issue..
Is there any insight where the QMI errors are coming from? Is it the modem
that is telling MM that there is something wrong?
Daniel
On Thu, 1 Feb 2024, 17:48 Daniel Edwards,
wrote:
> Hi,
>
> I'm reaching out to seek guidance regarding an issue
Hey Garfield,
> I have a situation where I have a ublox modem, the LISA u200, wired up using
> its SPI bus as the communication channel. On the DTE side is a raspberry pi
> SBC with a custom spi platform driver that exposes a tty device for modem.
> This driver is not capable of multiplexing an
Hey Menno,
> > After many hours we finally found out ModemManager is probing the devices,
> > so we added the udev rules:
> >
> > /etc/udev/rules.d/78-custom-mm-blacklist-internal-modem.rules :
> >
> > ACTION!="add|change|move", GOTO="custom_mm_blacklist_internal_modem_end"
> > ATTRS{idVendor}=="
Spot on!
This was exactly the problem!
Thank you.
On 3/3/24 10:07, Aleksander Morgado wrote:
On Wed, Feb 14, 2024 at 11:21 AM Garfield Watkins
wrote:
I think what confused me is that without the ModemManager i.e. using just
cgact=1,1 to manually connect, i suddenly got an ip address assigne
Hey Alex,
On Mon, Feb 19, 2024 at 2:31 AM Alex Villacís Lasso
wrote:
>
> El 16/2/24 a las 17:48, Alex Villacís Lasso escribió:
> > I have this old phone, a Samsung E3210B pre-Android feature phone that
> > I wish to use as a fallback option when (more frequently than I would
> > like) my broadban
Hey.
> Please let me understand the issue with multiple WWANs frequently
> disconnecting and reconnecting I am using Sierra wireless modems on the
> Ubuntu 22.04 desktop. I have updated the drivers and tried all available
> internet options, but no luck. It is not modems are not getting connect
On Wed, Feb 14, 2024 at 11:21 AM Garfield Watkins
wrote:
>
> I think what confused me is that without the ModemManager i.e. using just
> cgact=1,1 to manually connect, i suddenly got an ip address assigned to the
> network interface provided by the modem. I thought it was NetworkManager
> runni
Hey,
>
>
> I'm running into trouble with ModemManager, there seems to be no way to
> disable probing for certain devices.
> I have found countless threads discussing the lack of this feature, but none
> of them refer to my specific troubles.
>
We did have lots of problems in the past with block
Hey Pradeep!
>
> Good morning.
> Can you help to recommend to us which modemmanager to use for updating
> from 1.16.6-3?
>
> I found these two stable releases, which one you recommend given that we are
> currently using MM 1.16:
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/tag
Hello Aleksander,
Good morning.
Can you help to recommend to us which modemmanager to use for updating
from 1.16.6-3?
I found these two stable releases, which one you recommend given that we
are
currently using MM 1.16:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/tags/1.22.0
h
El 16/2/24 a las 17:48, Alex Villacís Lasso escribió:
I have this old phone, a Samsung E3210B pre-Android feature phone that
I wish to use as a fallback option when (more frequently than I would
like) my broadband internet service goes down. When using ModemManager
1.18.x, I could plug in this
Hi Aleksander,
I found these two stable releases, which one you recommend given that we
are
currently using MM 1.16:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/tags/1.22.0
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/tags/1.20.6
Are there any libqmi and libmbi
I think what confused me is that without the ModemManager i.e. using
just cgact=1,1 to manually connect, i suddenly got an ip address
assigned to the network interface provided by the modem. I thought it
was NetworkManager running its dhcp client on that interface after
getting a dhcp discover
Hey!
On Tue, Feb 13, 2024 at 1:49 PM Garfield Watkins
wrote:
>
> Did you connect the modem using NetworkManager (e.g. using nmcli) or
> did you connect the modem using mmcli?
>
> I see where you are going with this. It seems I expected more of the
> interaction between the ModemManager and Netwo
>
> Thanks for your reply, I will try out the suggested methods.
> And another thing is we are planning to update ModemManager
> ,currently we are at 1.16.6-2) and we can go to 1.20 stable versions.
> Is there any stable version that you can push into ModemManager sources?
> https://www.freedesktop
Aleksander Morgado writes:
> Hey Bjørn,
>
> I'm getting some strange reports of failures in the netlink
> communication when adding new multiplexed links in a MBIM modem, using
> cdc_mbim. I also have the kernel dmesg but it doesn't give any
> reference to the error, the only valid thing I have i
Hi Aleksander,
Thanks for your reply, I will try out the suggested methods.
And another thing is we are planning to update ModemManager
,currently we are at 1.16.6-2) and we can go to 1.20 stable versions.
Is there any stable version that you can push into ModemManager sources?
https://www.freedes
Did you connect the modem using NetworkManager (e.g. using nmcli) or
did you connect the modem using mmcli?
I see where you are going with this. It seems I expected more of the
interaction between the ModemManager and Network Manager . To answer
your question, no I have only used mmcli. Let me t
Hey,
On Tue, Feb 13, 2024 at 1:18 PM Garfield Watkins
wrote:
>
> Bearer 0 is the initial default bearer.
>
> Bearer 1 is the connected bearer
>
> Output from mmcli -b 1 is:
>
> -
> General|path: /org/freedesktop/ModemManager1/Bearer/1
>
Bearer 0 is the initial default bearer.
Bearer 1 is the connected bearer
Output from mmcli -b 1 is:
-
General | path: /org/freedesktop/ModemManager1/Bearer/1
| type: default
-
Status
Hey,
On Mon, Feb 12, 2024 at 9:37 AM Garfield Watkins
wrote:
>
> I have created a plugin for an LTE modem. This modem exposes 1 AT command
> port (e.g. ttyUSB0) and one ethernet port via usb (cdc_ether).
>
> When the modem is inserted via USB, the kernel enumerates some serial
> ports(ttyUSB0 -
long time.
Ideally, if we do 6 checks and it fails, we would mark the modem as
invalid as we do. But as soon as the SIM card is then properly
detected by the device, the device should notify about the change, and
in that case we would re-probe the whole device from scratch. If that
is not happe
Hey
>
> I have some old devices that I cannot do OS upgrades, and they're running
> Debian9, mmcli 1.6.4. Is it possible to do some sort of manual upgrade so
> that it can work with ublox L201?
>
Yes, it should be possible to use a much newer ModemManager than 1.6.4
in that old box, likely supp
Hey Pradeep!
>
> We are using RM520N-GL in our SD-WAN edge device in USB mode on M.2 Slot.
> We are facing an issue where AT USB ports(ttyUSB2, ttyUSB3) are not
> enumerated .
> We are using "modemmanager - 1.16.6-2" and also added RM520 blob to "
> /lib/udev/rules.d/77-mm-quectel-port-types.rul
Hi,
I have a similar problem [1] with a SIM7600SA modem. With the SIM
cards from one provider, there are no problems, but the SIM cards from
another provider can cause this issue.
[1] https://github.com/openwrt/packages/issues/23171
Cheers,
Yegor
On Mon, Feb 5, 2024 at 1:20 PM Ralf Glaser wrot
Aleksander Morgado writes:
> Hey all,
>
> I wrote a doc explaining how IPv4/IPv6 connectivity in LTE networks is
> setup (a very basic case scenario), including different possible
> interactions between host, modem and network, and focusing on how all
> these are exposed by ModemManager.
>
> It h
>
> Thank you for your answer. This works, indeed, and it is the information I
> was looking for. However, I have a follow-up question:
>
> When using the multiplex property, a virtual interface called
> mbimmux. is created.
>
> Is it possible to control the interface name and the VLAN ID used for
Hey,
> In my application, I use ModemManager to connect the modem, and then I
rename the network interface to a special name that is required by another
part of my system (and change the name back if the modem disconnects).
Is it not possible to rename the interface before even MM tries to grab t
Hey,
> First of all, i would like to thank you for taking time reading and
> answering this.
> We are currently using Modem Manager on various project and planned to
> move from SIMCOM (qmi) chipset to Quectel for cost reduction.
>
> We successfully makes Quectel working with ModemManager with PP
Hey,
>
> We getting connection disconnect randomly with below log from MM. We do
> have a way to recover from it but is there a way to know the cause of
> disconnect? Such as whether it is "network initiated disconnection" or
> "modem initiated". Any pointers in this regard will be helpful (to fi
HI,
Thank you for your answer. This works, indeed, and it is the information I
was looking for. However, I have a follow-up question:
When using the multiplex property, a virtual interface called mbimmux. is created.
Is it possible to control the interface name and the VLAN ID used for this
inte
Radu C writes:
> Hi,
>
> There are multiple tutorials online on how to connect a modem to a 5G core
> with multiple PDUs using mbimcli (like
> https://www.kernel.org/doc/html/latest/networking/cdc_mbim.html#mbim-data-channel-userspace-abi,
> or
> https://paldan.altervista.org/linux-mbim-wwan-mult
uot;, last_part);
+if (last_part != NULL) {
+device_removed (self, subsystem, last_part);
+}
+
+// Free the memory allocated by g_strsplit
+g_strfreev(parts);
+
+kernel_device = mm_kernel_device_udev_new (self->priv->udev,
device);
+d
Aleksander Morgado writes:
> On Wed, Nov 8, 2023 at 9:49 AM Bjørn Mork wrote:
>>
>> Amol Lad writes:
>>
>> > It seems the failure is occurring at the last chunk (#61). The status
>> > returned in "134". Please advise if any idea what this error status means?
>> >
>> > Bjørn, I saw one of your p
On Wed, Nov 8, 2023 at 9:49 AM Bjørn Mork wrote:
>
> Amol Lad writes:
>
> > It seems the failure is occurring at the last chunk (#61). The status
> > returned in "134". Please advise if any idea what this error status means?
> >
> > Bjørn, I saw one of your post in the mailing list regarding
>
On Tue, Nov 7, 2023 at 12:46 AM Thilo-Alexander Ginkel wrote:
>
> Problem solved. Just submitted a MR [1] for the unlock script.
>
> Thanks,
> Thilo
>
> [1]
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1091
>
>
Thanks!
You made a lot of people happy, you would
Hey,
> # mmcli -m 0 --simple-connect="apn=,multiplex=requested"
> error: couldn't connect the modem:
> 'GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code0:
> failed to create net link for device: failed to add link for device: Could
> not allocate link: Failed to add l
you sure you got an EM7455?
Or did someone sell you a re-labeled EM74x1?
Does it work with the official Sierra firmware tools and EM7455
firmware? Are you able to snoop on an upgrade to figure out if there's
some step we're missing or failing?
Bjørn
It seems the failure is occurring at the last chunk (#61). The status returned
in "134". Please advise if any idea what this error status means?
Bjørn, I saw one of your post in the mailing list regarding
qmi-firmware-update failure? Any idea what is this error?
Below is the log from qmi-firmw
Problem solved. Just submitted a MR [1] for the unlock script.
Thanks,
Thilo
[1]
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1091
On Sun, Nov 5, 2023 at 12:02 AM Thilo-Alexander Ginkel
wrote:
> Hello again,
>
> I got a prototype working that successfully unlo
Hello again,
I got a prototype working that successfully unlocks my modem via
/dev/wwan0at0. Currently I have that device name hardcoded. Is there a way
to infer it from the mbim device name?
Thanks,
Thilo
Hi,
It seems the previous mail was rejected, so here it is with a zip for trace.
Vincent
-Message d'origine-
De : Vincent ESCARGUEL
Envoyé : mardi 24 octobre 2023 15:53
À : Aleksander Morgado
Cc : ModemManager (development)
Objet : RE: EM9191 PCIe with CM4
Hi,
I've
Hey
> [19 окт 2023, 00:10:26] [Debug] Asynchronously initiating USSD session...
> error: couldn't initiate USSD session:
> 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.NotSupported:
> Operation not supported'
>
> ussd do not work for me ...
>
Very likely that your modem fails
Hey,
> I’m using a Sierra EM9191(sdx55) with PCIe on a raspberry CM4.
> Until now I had a firmware based on openWRT21.02, for which Aleksander had
> tuned the MM1.18.2 and few drivers.
> It worked nicely but we bought a new lot of CM4 and I need to upgrade few
> files for it to boot (start4.elf
1 - 100 of 2041 matches
Mail list logo
