Problems with modemmanager and Sierra EM7345 on resume

[Aleksander Morgado]

Hey,

On Mon, Feb 23, 2015 at 9:04 AM, Ernst Lehmann
<lehmann at acheron.franken.de> wrote:
> Hi List,
>
> perhaps this has been asked before. So my appology first.
>
>
> But after 5 days of googling (tons of pages), and trying every hint I
> found. I gave up, and now hope for help from you developers.
>
>
> my setup:
>
> - Thinkpad X1 Carbon 2nd gen
> - Sierra EM7345 4G-Modem.
>
> Ubuntu 14.04. with Networkmanager (0.9.8.8)
>
>
> I tried with:
> - modemmanager-1.0.0 (Ubuntu repo 14.04 default)
> - libqmi-1.8.0 (Ubuntu repo 14.04 default)
> - libmbim-1.6.0 (Ubuntu repo 14.04 default)
>
> and with
> - modemmanager-1.4.4 (build myself, with debian rules)
> - libqmi-1.12.4 (build myself, with debian rules)
> - libmbim-1.12.2 (build myself, with debian rules)
>
> cdc-acm.so is blacklisted...
>
>
> The problem is, after resume the network-manager can not connect to 4G.
> Device not found.
>
>
> nmcli dev list shows me an incrementing GENERAL.UDI for the 4G Modem.
>
> It startet with /org/freedesktop/ModemManger1/Modem/0
>
> and after two cycles of suspend/resume I am on
>
> /org/freedesktop/ModemManager1/Modem2
>
>
> here an example:
>
> ------
>
> GENERAL.DEVICE:                         cdc-wdm0
> GENERAL.TYPE:                           gsm
> GENERAL.VENDOR:                         --
> GENERAL.PRODUCT:                        --
> GENERAL.DRIVER:                         cdc_mbim
> GENERAL.DRIVER-VERSION:
> GENERAL.FIRMWARE-VERSION:
> GENERAL.HWADDR:                         (unknown)
> GENERAL.STATE:                          30 (disconnected)
> GENERAL.REASON:                         0 (No reason given)
> GENERAL.UDI:
> /org/freedesktop/ModemManager1/Modem/2
> GENERAL.IP-IFACE:
> GENERAL.NM-MANAGED:                     yes
> GENERAL.AUTOCONNECT:                    yes
> GENERAL.FIRMWARE-MISSING:               no
> GENERAL.CONNECTION:                     not connected
> CAPABILITIES.CARRIER-DETECT:            no
> CAPABILITIES.SPEED:                     unknown
> CONNECTIONS.AVAILABLE-CONNECTION-PATHS:
> /org/freedesktop/NetworkManager/Settings/{0}
> CONNECTIONS.AVAILABLE-CONNECTIONS[1]:
> 2e5ea13b-1307-4fa5-81b3-803fb6c8927d | T-Mobile(Telekom)
>
> ----------
>
> is there any solution for this device-UDI-increment?
>
> I think of this, as my problem for networkmanager to adress the Modem
> after resume.
>
>
> Thanks for your help, and sorry If it has asked before.
>
> Kind regards
>
> Ernst
>

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.

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/


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.


-- 
Aleksander
https://aleksander.es