Upgrade from 1.18 to 1.21.1 causes change in behavior
VT102 at protonmail.com
Mon Nov 28 19:48:10 UTC 2022
I assumed QMI could be consumed as package (i.e. built against existing so files) and that libqmi didnt have to be built from source for modemmanager to work, but now im realizing in my iterations of trying to solve this i ddint explicitly pass libqmi as required, and it didnt find the minimum version which for ModeManager 1.21 is probably going to have to be built from source.As I mentioned on an arm64v8 machine running Ubuntu20.04 I am unable to compile libqmi on the system (freezes apparentlyinfiintely on qmi-pbm.c.o) so I will have to investigate how to cross compile with the meson build tool chain and go from there.
Sent with Proton Mail secure email.
------- Original Message -------
On Monday, November 28th, 2022 at 5:27 AM, Aleksander Morgado <aleksandermj at chromium.org> wrote:
> > I am working with an mPCI Telit LE910C4 modem connected to a Linux System on a Chip running Ubunut 20.04.
> > With 1.18 ModemManager installed I noticed that serial ports were being listed as ignored except for a GPS port was available through a tty, this meant I couldnt issue AT commands. I also needed bit error rate from the mmlib-glib API so I decided to build ModemManager 1,21.
> > Upon upgrading the modem no longer recognizes as a qmi device, but the AT command tty terminals are available. I was hoping for some advice on how to investigate this behavior. I did not build libqmi from source because whenever I try to compile on the device compilation freezes (overnight) on compiling certain *.o files. However, I am able to get the modem connected.
> > Any advice on how to debug why the modem is no longer being recognized as a qmi device?
> I'm a bit confused, you built MM 1.21 but you didn't build the
> corresponding libqmi? If so, it looks like you built MM without QMI
> support, and that is the reason why your device isn't recognized as a
> QMI device.
More information about the ModemManager-devel