Problems with modemmanager and Sierra EM7345 on resume

[Aleksander Morgado]

>>
>> Wait, there's a mismatch of info you gave here. First you said the
>> modem wasn't found after resume; then you said the UDI was
>> incremented. The UDI increment is just ModemManager re-detecting the
>> modem after the suspend. That is not a problem. Actually, in the next
>> stable version of ModemManager (currently in git master) all modems
>> will be fully reprobed when a suspend/resume cycle is detected, so
>> that ModemManager doesn't assume any previous power or protocol state.
>
> That is the message from nm-applet.
>
> Connection activation failed
>
> (32) Device not found
>

If you get both NM and MM logs we could try to see what happens.

>>
>> Now, after the suspend-resume cycle; what's the output of "mmcli -L"?
>> What is the output of "mmcli -L" after some time (e..g. 1min). Could
>> you also get debug logs to confirm what the issue is? See:
>> http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
>
>
>
> Found 1 modems:
>         /org/freedesktop/ModemManager1/Modem/3 [Generic] MBIM [1199:A001]
>
>
> and ascending for the number.
>
>>
>> Anyway, this problem looks like it could be related to this one:
>>   https://bugs.freedesktop.org/show_bug.cgi?id=84994
>> That issue is fixed with libmbim 1.12 and ModemManager git master.
>>
>>
>
> libmbim 1.12.4 is installed.
>
> So I will try ModemManager git-master this evening, and will report.
>

Please compile with:
  --with-suspend-resume=systemd
So that we get notified of suspend/resume events with systemd's logind
interface. I truly don't know if your ubuntu version supports logind,
though.

There's also:
  --with-suspend-resume=upower
But that will only work with old version of upower, as notifying
suspend/resume events got removed in favor of the logid version.


-- 
Aleksander
https://aleksander.es