Quectel em12-g minimal kernel version

[Nicholas Smith]

Actually that QMI service is there....

Service: 'qmi'
             UUID: [d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3]:
      DSS payload: 0
Max DSS instances: 0
             CIDs: msg (1)

... but when I try to use qmicli with --device-open-mbim I get this...

qmicli -p -d /dev/cdc-wdm0 --device-open-mbim --nas-get-signal-strength
[25 Jun 2021, 10:17:27] -Warning ** [/dev/cdc-wdm0] requested MBIM
mode but no MBIM QMUX support available
error: couldn't open the QmiDevice: Could not create endpoint

... Even though I am compiling libqmi  with --enable-mbim-qmux (on OpenWrt)


All the best,
Nick




On Fri, 25 Jun 2021 at 09:22, Bjørn Mork <bjorn at mork.no> wrote:
>
> Nicholas Smith <nicholas at nbembedded.com> writes:
>
> > I can confirm that the Quectel EM12-G most certainly does not play
> > nice with qmi_wwan (at least on the vendor firmware versions I have
> > tested, which includes several, including the latest).  The module
> > always inexplicably crashes after anywhere from between a couple of
> > hours to a couple of days of uptime.  When in MBIM mode it is stable,
> > but you cannot use qmicli to get detailed NAS information, or select
> > bands, etc... so you lose a huge amount of useful functionality.  So,
> > if I want to do anything out of the ordinary, I temporarily switch it
> > into QMI mode before switching back to MBIM mode.
>
> So it doesn't export the QMI service in MBIM mode?  That's pretty
> unusual for a Qualcomm based modem.
>
> You can check this with e.g
>
>  mbimcli -d /dev/cdc-wdm0  --query-device-services
>
> We normally expect an entry like:
>
>                          Service: 'qmi'
>                              UUID: [d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3]:
>                       DSS payload: 0
>                 Max DSS instances: 0
>                              CIDs: msg (1)
>
>
> This MBIM service can be used by libqmi/qmicli for full QMI access.  See
> the --device-open-mbim option.  Actually, it defaults to autodetecting,
> so accessing QMI services should just work.
>
>
>
> Bjørn