Re: Assistance Needed with SIM Card Issue Causing QMI Operation Failures
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 I've been > experiencing with ModemManager, specifically related to certain SIM cards > causing QMI operation failures, which ultimately leads to the modem being > marked as invalid. > > To give you a brief overview, the modem still responds to AT commands and > shows that it's connected and registered to the correct home network, but > the modem will not show in mmcli -L, and the device will stay unconnected. > With other SIMs it will work fine. > > The modem is a SIM7600G. > > Here is a log with --debug enabled https://sprunge.us/UR3gvX > > Sometimes the problematic SIM will work and connect the device to the > internet, but I have not found a way to reliably recreate this scenario. > > Cheers, > > Daniel Edwards > Q Yachts Oy > > Technical Engineer > > >
Re: ModemManager Issue with multiple WWAN Sierrawireless Ubuntu 22.04
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, the modem works fine without any disconnections. I tried contacting the modem using Sierra MC7304 & MC7430, but it did not solve the problem. The modem manager provides all the necessary details, but it keeps resetting frequently when I use the internet or live streaming applications. I would appreciate your support in resolving this issue. Please let me know if you require any additional information or logs. On Sun, 3 Mar 2024, 1:39 pm Aleksander Morgado, wrote: > 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 connected, > modems are connected but while giving some load on them they start > misbehaving (WWANs frequently disconnecting and reconnecting) I am using > the default modem manager app from free Desktop org > > > > Appreciate it if someone could help > > > > This looks like the modem resetting itself, which could indicate modem > firmware errors. Make sure you have the latest firmware available from > Sierra installed in the device, and if it still happens, report it at > https://forum.sierrawireless.com/c/modules/mc-em-series/34 > > -- > Aleksander >
Re: ModemManager Issue with multiple WWAN Sierrawireless Ubuntu 22.04
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 fine without any > disconnections. I tried contacting the modem using Sierra MC7304 & MC7430, > but it did not solve the problem. The modem manager provides all the > necessary details, but it keeps resetting frequently when I use the internet > or live streaming applications. > I would appreciate your support in resolving this issue. > Please let me know if you require any additional information or logs. > I'm afraid there is not much we can do, if the issue is the modem crashing. You said that using qmicli or AT commands makes it more stable, so it could really be related to some of the setup MM does, but even in that case, only the manufacturer will be able to analyze the modem crashes. The best path forward you have would be to contact Sierra support so that they guide you in how to retrieve modem traces they can analyze :/ The MC7304 is one of the modems that I test on every MM release, and I haven't noticed any strange myself, but of course my network conditions are not the same as yours. -- Aleksander
Re: Seems like MM_FILTER_RULE_TTY_WITH_NET overrides ID_MM_DEVICE_IGNORE
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}=="[redacted1]" ATTRS{idProduct}=="[redacted2]",
> > ENV{ID_MM_DEVICE_IGNORE}="1"
> > ATTRS{idVendor}=="[redacted1]" ATTRS{idProduct}=="[redacted3]",
> > ENV{ID_MM_DEVICE_IGNORE}="1"
> > LABEL="custom_mm_blacklist_internal_modem_end"
> >
> > but looking at the logs I see:
> >
> > ModemManager[3751]: [filter] (tty/ttyACM0): port filtered: device
> > is blocklisted
> > ModemManager[3751]: [filter] (net/enxd[redacted4]) port allowed:
> > net device
> > ModemManager[3751]: [filter] (net/enxd[redacted4]) port allowed:
> > net device
> > ModemManager[3751]: [filter] (tty/ttyACM0): port allowed: device
> > also exports a net interface
> >
> > So if ModemManager successfully found the device is blocklisted, why does
> > it continue to probe the port?
>
> This is definitely a bug. I've opened
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/833
>
We've been trying to get an idea of why this issue is happening in
your setup but it's not really clear.
Would you be able to send a full MM debug log
(https://modemmanager.org/docs/modemmanager/debugging/#daemon-debug-logs)
and share a bit more about your system? e.g. is it openwrt based or
not, the output of "usb-devices" and "lsusb -v" for this device...
Thanks
--
Aleksander
Re: Assistance Needed with SIM Card Issue Causing QMI Operation Failures
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 log you provided was when reading the preferred operator list, and after that several other SIM file read operations fail. My guess is that either the SIM card gets in a bad state, or maybe it just needs more time to answer. If you have the SIM card at hand and you reproduce the problem, where MM just removes the modem object, you can try to manually run "qmicli -p -d /dev/cdc-wdm0 --uim-get-card-status" operations on the cdc-wdm control port to see if it ever replies or if the card got stuck. Another test would be to fully disable the loading of preferred operator list in MM (assuming that could be the culprit), by clearing up the function pointers in mm-sim-qmi.c: base_sim_class->load_preferred_networks = NULL; base_sim_class->load_preferred_networks_finish = NULL; -- Aleksander
Re: How to probe a modem exposing virtual ports (GSM 07.10 muxed ports)
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 and exposing multiple virtual > channels. > > To overcome this I have a user mode daemon that performs this function by > connection to the single tty port exposed by the spi driver and in turn > creating 5 pseudo tty's (/dev/ptty1 -> /dev/ptty5) to interact with. These > are actually links to /dev/pts/1 to /dev/pts/5. > > I want the ublox plugin to manage this device but there seems to be no way to > filter/grab those ports. > You should be able to add the ID_MM_PHYSDEV_UID udev tags for all those pseudo TTYs, so that ModemManager can "bind" all those ports together to the same modem object, see https://www.freedesktop.org/software/ModemManager/doc/latest/ModemManager/ModemManager-Common-udev-tags.html#ID-MM-PHYSDEV-UID:CAPS -- Aleksander
Re: SIM Reconnection Issues (Modem Manager 1.20.4)
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 the state is connected. I > then proceed to de-activate the SIM remotly. This is where the logs start > (Feb 29 13:00:00). > The logs then show a constant change in state where *enabled -> searching* > and *searching -> enabled* is constantly logged. > All the night is spent like this, switching the state. What I am trying to > test is that upon remot activation of the SIM, the connection is resumed > without problems. > So, fast forward to Mar 01, I activate the SIM remotely and nothing > happens. I end up reseting the modem with "mmcli -m 0 --reset" and then a > restart of the ModemManager.service and finally the connection is > established correctly. > > I am not sure what could be the issue. It is also worth noting that we > have tested this in other boards that have the same modem, and the > behaviour is not the same for every board. > > Would you be able to provide full MM debug logs including the times when the SIM was remotely deactivated and remotely activated? -- Aleksander
