Hi all,
> On 15 Mar 2019, at 16:03, matthew stanger <stange...@gmail.com> wrote:
>
> Anyway, the only thing I can think of is a timing issue with the modem
> firwmare and network registration or initial bearer setup or something
> like that. Perhaps MM isn't querying some ready state well enough, or
> the modem isn't fully set up when we're querying because MM isn't
> asking the right question. NOt sure what else it could be.
> Wonderful observation there. Just realized this modem's boot ready URC is
> '+PBREADY'. There's nothing in MM to support(minus ublox plugin) this cmd,
> which would imply that MM would be sending cmd's before the module is ready.
>
> I made sure that the modem was freshly booted in both cases.
> That'd be the main difference, you waited.
>
> To test this theory out all you need to do is stop MM, plugin/start your
> modem give it ~20 sec's to be sure. Then start MM and see if the connection
> now works. Let me know if that work and then we can go from there.
I actually tried exactly this: I restarted the modem without ModemManager
running, sent AT to the modem until I got +PBREADY as part of the reply and
then started ModemManager. Unfortunately, this leads to the same behaviour.
Same old +CEER: "SM deactivation",187,"Last PDN disconnection not allowed”
Sven
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
