Quectel em12-g minimal kernel version

[Nicholas Smith]

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.


All the best,
Nick

Google Summer of Code 2021 Mentor

All the best,
Nicholas

Nicholas Smith
NB Embedded Systems Consulting
Suite 4139
681 New Cleveland Road
Gumdale, QLD 4154
ABN: 33 644 764 763

nicholas at nbembedded.com

Google Summer of Code 2021 Mentor



On Thu, 24 Jun 2021 at 21:40, Bjørn Mork <bjorn at mork.no> wrote:
>
> Alexander Dydychkin <alexander.dydychkin at vicuesoft.com> writes:
>
> > Hi dear developers,
> >
> > I want to ask you about the minimal supported version of Quectel
> > by qmi_wwan driver.
> > I have following case:
> > - Ubuntu 18.04.3 (kernel 5.0)
> > - Inserted the module to the machine and have following log (1st one is
> > Sierra, 2nd and 3d are Quectel modules):
> > lsusb -t
> > /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 10000M
> > /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
> >     |__ Port 14: Dev 85, If 0, Class=Hub, Driver=hub/4p, 480M
> >         |__ Port 1: Dev 86, If 0, Class=Human Interface Device,
> > Driver=usbhid, 12M
> >         |__ Port 2: Dev 89, If 0, Class=Vendor Specific Class,
> > Driver=qcserial, 480M
> >         |__ Port 2: Dev 89, If 2, Class=Vendor Specific Class,
> > Driver=qcserial, 480M
> >         |__ Port 2: Dev 89, If 3, Class=Vendor Specific Class,
> > Driver=qcserial, 480M
> >         |__ Port 2: Dev 89, If 8, Class=Vendor Specific Class,
> > Driver=qmi_wwan, 480M
> >         |__ Port 3: Dev 88, If 0, Class=Vendor Specific Class, Driver=, 480M
> >         |__ Port 3: Dev 88, If 5, Class=CDC Data, Driver=cdc_mbim, 480M
> >         |__ Port 3: Dev 88, If 3, Class=Vendor Specific Class, Driver=, 480M
> >         |__ Port 3: Dev 88, If 1, Class=Vendor Specific Class, Driver=, 480M
> >         |__ Port 3: Dev 88, If 4, Class=Communications, Driver=cdc_mbim,
> > 480M
> >         |__ Port 3: Dev 88, If 2, Class=Vendor Specific Class, Driver=, 480M
> >         |__ Port 4: Dev 87, If 4, Class=Communications, Driver=cdc_mbim,
> > 480M
> >         |__ Port 4: Dev 87, If 2, Class=Vendor Specific Class, Driver=, 480M
> >         |__ Port 4: Dev 87, If 0, Class=Vendor Specific Class, Driver=, 480M
> >         |__ Port 4: Dev 87, If 5, Class=CDC Data, Driver=cdc_mbim, 480M
> >         |__ Port 4: Dev 87, If 3, Class=Vendor Specific Class, Driver=, 480M
> >         |__ Port 4: Dev 87, If 1, Class=Vendor Specific Class, Driver=, 480M
>
>
> Both Quectel modems are configured for MBIM.  They work with qmi_wwan in
> this mode regardless of kernel/driver version.
>
> > mbimcli and qmicli don`t work with Quectel right now.
>
> They should work with mbimcli.  That's all I can say based on the
> provided info.
>
> But more details are necessary to
> understand the problem
>
> > So my questions are:
> > - Did I do something wrong? Or kernel 5.0 is too old for my Quectel em12-g?
> > - Should Quectel em12-g work  "out-of-the-box" with kernel  5.13?
> > - Any corner cases with Quectel? Any guides? :)
>
> Can't answer specifically for the em12-g.  But in general, any USB MBIM
> modem should work "out-of-the-box" with a 5.x kernel.
>
>
> Bjørn
> _______________________________________________
> libqmi-devel mailing list
> libqmi-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libqmi-devel