[URGENT] Regressions in latest QMI-related packages

Ajay Garg ajaygargnsit at gmail.com
Mon Oct 17 18:05:18 UTC 2016


I tried switching to Direct-IP mode, and ALL mmcli-commands (including *mmcli
-m 0 --set-allowed-modes='2G'*) work fine from mmcli itself (without using
any AT-commands as such).


a)
Is this expected behaviour?

b)
Now, since qmi-proxy is no more there, there are chances of interminglings
due to working of ModemManager and mmcli together, right?

On Mon, Oct 17, 2016 at 8:48 PM, Aleksander Morgado <
aleksander at aleksander.es> wrote:

> On Mon, Oct 17, 2016 at 5:10 PM, Ajay Garg <ajaygargnsit at gmail.com> wrote:
> > :O :O :O :O
> >
> > Of course I switched it to QMI.
> > The previous unit that I did all the tests on, ran perfect when switched
> to
> > QMI mode.
> >
> > Your reply suggests that some functionalities (like switching to
> > 2G-only-mode) would not work in Direct-IP mode.
> > If so, Direct-IP would not serve our purpose.
> >
>
> No, I didn't say that. Switching to 2G mode should be ok in Direct IP
> mode, using AT commands.
>
> > I am in the process of retrieving the "ati" output of the earlier-modem
> (on
> > which things worked perfect in QMI-mode).
> > That could probably help in determining if some firmware-mismatch is
> causing
> > any issue.
> >
> >
> > But Aleksander, this is really bad news.
> > Any idea what might have made things working in the earlier-modem in QMI?
>
> I have no idea; was it a MC8090 as well?
>
> --
> Aleksander
> https://aleksander.es
>



-- 
Regards,
Ajay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20161017/40896e10/attachment.html>


More information about the ModemManager-devel mailing list