Resolved: Error - Asynchronously connecting to the modem: connection setup cancelled.

[Nicholas Smith]

Dear ModemManager developers,

I discovered that the problem can be resolved by unloading some kernel modules and restarting modem manager.

rmmod huawei_cdc_ncm
rmmod cdc_mbim
rmmod sierra
rmmod sierra_net
/etc/init.d/modemmanager restart

mmcli -m 0 -d
mmcli -m 0 -e
mmcli -m 0 --simple-connect="apn=live.vodafone.com”

I can put this in a script in my OS, but I have a question.  These modules do not seem to be required for my system to work, but they are dependences for compiling modem manager.  Why is that so?

-Nicholas S.

> On 13 Jan 2018, at 12:49 am, Nicholas Smith <smith.nicholas910 at gmail.com> wrote:
> 
> Asynchronously connecting to the modem: connection setup cancelled.
> Modem Manager version: 1.7.0
> 
> 
> Greetings,
> 
> I am hoping to get some advice on where to look to get more information to identify the problem that I am experiencing.  The modem I am using is a Sierra Wireless MC7430.  It is registered to the operator, has a good signal (-68dBm) but will not connect to the operator.  I have verified the SIM card in a mobile phone, SIM is activated and working.  What confuses me the most is that the modem was previously working on another APN with another SIM.
> 
> I have blanked out the defined context entries by entering at+cgdcont=x, where x is the index.  When it was previously working I had defined a context in the modem firmware, but this is actually what ModemManager will do for me, correct?  Nonetheless, I have already tried defining the new context using “IP" and the APN in the firmware to no avail.  (The command was at+cgdcont=2,”IP”,”yesoptus”).  I have tried every permutation of settings for the APN’s IP family settings in the firmware, such as IPV4V6, and IPV6, just in case this particular APN is picky.
> 
> Following the blanking out of the entries, I simply reinstalled the firmware on the modem using the supplied Sierra utility (sorry, I haven’t had a chance to try the new feature built into mmcli :) ).  Following that, I rebuilt LEDE from source using the latest snapshot available as of Jan 13th 2018, and updated the feeds, and used the ModemManager-openwrt supplied on Aleksander’s bitbucket profile.  
> 
> What is strangest to me, yet gives me determination to find the cause of the problem, is that it was working before on another APN with another SIM.     I had been using it on various snapshots of LEDE Reboot since November 2017.  The moment I changed the SIM, and changed the APN in /etc/conf/network’s modem manager entry is when the problem seems to have started.  (At that time, there was an APN defined in the modem firmware, but as I mentioned, the firmware has been reinstalled).  However, I had also performed a couple of sysupgrades with LEDE during that time, though I’m not so sure how that could have caused this.
> 
> I will close with some of the technical information.  Am I doing something wrong?  Would the qmi_wwan drivers have changed in this version of LEDE and affected modemmanager?  Should I be blacklisting any drivers when using qmi_wwan?  Gobi drivers are not installed.
> 
> 
> Kernel: 4.9.76
> 
> mmcli -V 1.7.0
> mmcli -m 0 --simple-status
> 
> /org/freedesktop/ModemManager1/Modem/0
> -------------------------
> Status |          state: 'registered'
>        | signal quality: '62' (recent)
>        |          bands: 'u2100, u800, u850, u900, u17ix, eutran-i, eutran-iii, eutran-v, eutran-vii, eutran-viii, eutran-xviii, eutran-xix, eutran-xxi, eutran-xxxviii, eutran-'
>        |    access tech: 'lte'
> -------------------------
> 3GPP   |   registration: 'home'
>        |  operator code: '50503'
>        |  operator name: 'Voda AU'
>        |   subscription: ‘unknown'
> 
> And finally, the error:
> 
> root at lteRouter:/# mmcli -m 0 --simple-connect="apn=yesinternet" -v
> [12 Jan 2018, 07:42:17] [Debug] Forcing request to be run asynchronously
> [12 Jan 2018, 07:42:17] [Debug] Assuming '0' is the modem index
> [12 Jan 2018, 07:42:17] [Debug] ModemManager process found at ':1.3'
> [12 Jan 2018, 07:42:17] [Debug] Modem found at '/org/freedesktop/ModemManager1/Modem/0'
> 
> [12 Jan 2018, 07:42:17] [Debug] Asynchronously connecting the modem...
> error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Cancelled: Connection setup operation has been cancelled’
> 
> 
> 
> Kind Regards,
> 
> Nicholas S.
>