Re: Failed to find primary AT port

[Aleksander Morgado]

On Thu, Apr 6, 2017 at 12:39 AM, Jan Graczyk  wrote:
> Thank you for your response. I have looked into ModemManager version 1.6.4 
> and this patch you are mentioning in your e-mail does not reflect the line 
> number in src/mm-base-modem.c:
>
> @@ -219,6 +219,12 @@ mm_base_modem_grab_port (MMBaseModem *self,
>"timed-out",
>G_CALLBACK (serial_port_timed_out_cb),
>self);
> +
> +/* For serial ports, optionally use a specific baudrate */
> +if (mm_kernel_device_has_property (kernel_device, 
> "ID_MM_TTY_BAUDRATE"))
> +g_object_set (port,
> +  MM_PORT_SERIAL_BAUD, 
> mm_kernel_device_get_property_as_int (kernel_device, "ID_MM_TTY_BAUDRATE"),
> +  NULL);
>  }
>  /* Net ports... */
>  else if (g_str_equal (subsys, "net")) {
>
> I also have built ModemManager1.6.4 for ARM architecture and run on my 
> development board. However I am getting the following error:
>
> ModemManager[1631]:  [1491431437.689341] [mm-plugin.c:804] 
> mm_plugin_supports_port(): (Generic) [ttymxc2] probe required: 'at, qcdm'
> ModemManager[1631]:  [1491431437.689422] [mm-port-probe.c:1376] 
> mm_port_probe_run(): (tty/ttymxc2) port probing finished: no more probings 
> needed
> ModemManager[1631]:  [1491431437.689575] [mm-plugin-manager.c:283] 
> port_context_supported(): [plugin manager] task 0,ttymxc2: found best plugin 
> for port (Generic)
> ModemManager[1631]:  [1491431437.689678] [mm-plugin-manager.c:265] 
> port_context_complete(): [plugin manager] task 0,ttymxc2: finished in 
> '10.416165' seconds
> ModemManager[1631]:  [1491431437.690192] [mm-plugin-manager.c:979] 
> device_context_continue(): [plugin manager] task 0: no more ports to probe
> ModemManager[1631]:  [1491431437.690297] [mm-plugin-manager.c:813] 
> device_context_complete(): [plugin manager] task 0: finished in '10.417578' 
> seconds
> ModemManager[1631]:   [1491431437.690453] [mm-device.c:525] 
> mm_device_create_modem(): Creating modem with plugin 'Generic' and '1' ports
> ModemManager: symbol lookup error: ModemManager: undefined symbol: 
> mm_gdbus_modem_voice_skeleton_get_type
>
> Could you tell me which version of ModemManager I should use?

If you want to configure baudrate via udev rules, you should use
ModemManager from git master. Or, default to 57600bps in the modem.

But, as Dan said in a couple of emails back, this modem should be
running in QMI mode, and therefore controlled via cdc-wdm port and
with data connection over a WWAN port. If this is a custom system
you're preparing, you should check your build and see why the qmi_wwan
or cdc-wdm kernel modules aren't being built or used.

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

RE: Failed to find primary AT port

[Jan Graczyk]

Hello Dan,

I have built ModemManager1.4.0 (only this version is running properly on 
Quectel UC20 modem currently) for ARM architecture with your suggestions:

> The UC20 should be using QMI, not AT ports.  qmi_wwan support for the
> UC20 has been there since 2013.  But to use it, you need to:
> 
> 1) ensure qmi_wwan has been built for your kernel
> 2) ensure you build ModemManager with libqmi support (--with-qmi=yes)

However after executing these commands:

mmcli -m 0 --simple-disconnect
mmcli -m 0 --simple-connect="pin=1234,apn=internet"

I am still getting the message:

 "Failed to find primary AT port"

What else need to be done to fix this problem? 

Best Regards,

Jan Graczyk

-Original Message-
From: Dan Williams [mailto:d...@redhat.com] 
Sent: Wednesday, April 5, 2017 10:58 AM
To: Jan Graczyk <j...@nytec.com>
Cc: modemmanager-devel@lists.freedesktop.org
Subject: Re: Failed to find primary AT port

On Wed, 2017-04-05 at 17:29 +, Jan Graczyk wrote:
> Hello Dan,
> 
> Is ModemManager baud rate configurable to a different value? I know 
> that by default ModemManager runs properly with modem baud rate set to 
> 57600.

Aleksander committed a patch two weeks ago that allow configuring the baud rate 
from udev rules, see:

https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=11a26f10668659fb0c043ec9bc88debacce8cab1

Dan

> Best Regards,
> 
> Jan Graczyk
> 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Tuesday, April 4, 2017 12:19 PM
> To: Jan Graczyk <j...@nytec.com>
> Cc: modemmanager-devel@lists.freedesktop.org
> Subject: Re: Failed to find primary AT port
> 
> On Tue, 2017-04-04 at 18:45 +, Jan Graczyk wrote:
> > Hello All,
> > 
> > I am trying to build ModemManager for ARM architecture. However 
> > during the compilation I have got the following problem:
> > 
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgmodule-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgio-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgobject-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lglib-2.0
> > 
> > How can I resolve this problem? I appreciate your help very much.
> 
> You need to install neccesary build dependencies for your chosen 
> architecture too.  Looks like you're missing glib and its associated 
> libraries for ARM installed in the cross-compile library directory.
> 
> Dan
> 
> > Jan Graczyk
> > 
> > -Original Message-
> > From: Jan Graczyk
> > Sent: Monday, April 3, 2017 2:27 PM
> > To: 'Dan Williams' <d...@redhat.com>
> > Cc: modemmanager-devel@lists.freedesktop.org
> > Subject: RE: Failed to find primary AT port
> > 
> > Hello Dan,
> > 
> > Thank you for your response. The next question I have for you is how 
> > to cross compile ModemManager for ARM architecture. I am using 
> > ModemManager version 1.4.2 to build. Is that version stable enough 
> > to run on ARM based processor? The version of ModemManager on my 
> > target is 1.4.0 and it is working well.
> > 
> > Best Regards,
> > 
> > Jan Graczyk
> > 
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Friday, March 31, 2017 3:15 PM
> > To: Jan Graczyk <j...@nytec.com>
> > Cc: modemmanager-devel@lists.freedesktop.org
> > Subject: Re: Failed to find primary AT port
> > 
> > On Fri, 2017-03-31 at 21:09 +, Jan Graczyk wrote:
> > > Hello Dan,
> > > 
> > > There is no problem with connecting to this modem (mini PCIe 
> > > Quectel
> > > UC20 modem module) from kermit and sending AT commands. However 
> > > when I issue the following commands:
> > > 
> > >  mmcli -m 0 --simple-disconnect
> > >  mmcli -m 0 --simple-connect="pin=1234,apn=internet"
> > > 
> > > the ModemManager sends debug message "Failed to find primary AT 
> > > port"
> &g

RE: Failed to find primary AT port

[Jan Graczyk]

Hello Dan,

Thank you for your response. I have looked into ModemManager version 1.6.4 and 
this patch you are mentioning in your e-mail does not reflect the line number 
in src/mm-base-modem.c:

@@ -219,6 +219,12 @@ mm_base_modem_grab_port (MMBaseModem *self,
   "timed-out",
   G_CALLBACK (serial_port_timed_out_cb),
   self);
+
+/* For serial ports, optionally use a specific baudrate */
+if (mm_kernel_device_has_property (kernel_device, 
"ID_MM_TTY_BAUDRATE"))
+g_object_set (port,
+  MM_PORT_SERIAL_BAUD, 
mm_kernel_device_get_property_as_int (kernel_device, "ID_MM_TTY_BAUDRATE"),
+  NULL);
 }
 /* Net ports... */
 else if (g_str_equal (subsys, "net")) {

I also have built ModemManager1.6.4 for ARM architecture and run on my 
development board. However I am getting the following error:

ModemManager[1631]:  [1491431437.689341] [mm-plugin.c:804] 
mm_plugin_supports_port(): (Generic) [ttymxc2] probe required: 'at, qcdm'
ModemManager[1631]:  [1491431437.689422] [mm-port-probe.c:1376] 
mm_port_probe_run(): (tty/ttymxc2) port probing finished: no more probings 
needed
ModemManager[1631]:  [1491431437.689575] [mm-plugin-manager.c:283] 
port_context_supported(): [plugin manager] task 0,ttymxc2: found best plugin 
for port (Generic)
ModemManager[1631]:  [1491431437.689678] [mm-plugin-manager.c:265] 
port_context_complete(): [plugin manager] task 0,ttymxc2: finished in 
'10.416165' seconds
ModemManager[1631]:  [1491431437.690192] [mm-plugin-manager.c:979] 
device_context_continue(): [plugin manager] task 0: no more ports to probe
ModemManager[1631]:  [1491431437.690297] [mm-plugin-manager.c:813] 
device_context_complete(): [plugin manager] task 0: finished in '10.417578' 
seconds
ModemManager[1631]:   [1491431437.690453] [mm-device.c:525] 
mm_device_create_modem(): Creating modem with plugin 'Generic' and '1' ports
ModemManager: symbol lookup error: ModemManager: undefined symbol: 
mm_gdbus_modem_voice_skeleton_get_type

Could you tell me which version of ModemManager I should use?

Best Regards,

Jan Graczyk

-Original Message-
From: Dan Williams [mailto:d...@redhat.com] 
Sent: Wednesday, April 5, 2017 10:58 AM
To: Jan Graczyk <j...@nytec.com>
Cc: modemmanager-devel@lists.freedesktop.org
Subject: Re: Failed to find primary AT port

On Wed, 2017-04-05 at 17:29 +, Jan Graczyk wrote:
> Hello Dan,
> 
> Is ModemManager baud rate configurable to a different value? I know 
> that by default ModemManager runs properly with modem baud rate set to 
> 57600.

Aleksander committed a patch two weeks ago that allow configuring the baud rate 
from udev rules, see:

https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=11a26f10668659fb0c043ec9bc88debacce8cab1

Dan

> Best Regards,
> 
> Jan Graczyk
> 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Tuesday, April 4, 2017 12:19 PM
> To: Jan Graczyk <j...@nytec.com>
> Cc: modemmanager-devel@lists.freedesktop.org
> Subject: Re: Failed to find primary AT port
> 
> On Tue, 2017-04-04 at 18:45 +, Jan Graczyk wrote:
> > Hello All,
> > 
> > I am trying to build ModemManager for ARM architecture. However 
> > during the compilation I have got the following problem:
> > 
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgmodule-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgio-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgobject-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lglib-2.0
> > 
> > How can I resolve this problem? I appreciate your help very much.
> 
> You need to install neccesary build dependencies for your chosen 
> architecture too.  Looks like you're missing glib and its associated 
> libraries for ARM installed in the cross-compile library directory.
> 
> Dan
> 
> > Jan Graczyk
> > 
> > -Original Message-
> > From: Jan Graczyk
> > Sent: Monday, April 3, 2017 2:27 PM
> > To: 'Dan Williams' <d...@redha

Re: Failed to find primary AT port

[Dan Williams]

On Wed, 2017-04-05 at 17:29 +, Jan Graczyk wrote:
> Hello Dan,
> 
> Is ModemManager baud rate configurable to a different value? I know
> that by default ModemManager runs properly with modem baud rate set
> to 57600.

Aleksander committed a patch two weeks ago that allow configuring the
baud rate from udev rules, see:

https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=11a26f10668659fb0c043ec9bc88debacce8cab1

Dan

> Best Regards,
> 
> Jan Graczyk
> 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com] 
> Sent: Tuesday, April 4, 2017 12:19 PM
> To: Jan Graczyk <j...@nytec.com>
> Cc: modemmanager-devel@lists.freedesktop.org
> Subject: Re: Failed to find primary AT port
> 
> On Tue, 2017-04-04 at 18:45 +, Jan Graczyk wrote:
> > Hello All,
> > 
> > I am trying to build ModemManager for ARM architecture. However
> > during 
> > the compilation I have got the following problem:
> > 
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgmodule-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgio-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lgobject-2.0
> > /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> > x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> > gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> > -lglib-2.0
> > 
> > How can I resolve this problem? I appreciate your help very much.
> 
> You need to install neccesary build dependencies for your chosen
> architecture too.  Looks like you're missing glib and its associated
> libraries for ARM installed in the cross-compile library directory.
> 
> Dan
> 
> > Jan Graczyk
> > 
> > -Original Message-
> > From: Jan Graczyk
> > Sent: Monday, April 3, 2017 2:27 PM
> > To: 'Dan Williams' <d...@redhat.com>
> > Cc: modemmanager-devel@lists.freedesktop.org
> > Subject: RE: Failed to find primary AT port
> > 
> > Hello Dan,
> > 
> > Thank you for your response. The next question I have for you is
> > how 
> > to cross compile ModemManager for ARM architecture. I am using 
> > ModemManager version 1.4.2 to build. Is that version stable enough
> > to 
> > run on ARM based processor? The version of ModemManager on my
> > target 
> > is 1.4.0 and it is working well.
> > 
> > Best Regards,
> > 
> > Jan Graczyk
> > 
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Friday, March 31, 2017 3:15 PM
> > To: Jan Graczyk <j...@nytec.com>
> > Cc: modemmanager-devel@lists.freedesktop.org
> > Subject: Re: Failed to find primary AT port
> > 
> > On Fri, 2017-03-31 at 21:09 +, Jan Graczyk wrote:
> > > Hello Dan,
> > > 
> > > There is no problem with connecting to this modem (mini PCIe
> > > Quectel
> > > UC20 modem module) from kermit and sending AT commands. However
> > > when 
> > > I issue the following commands:
> > > 
> > >  mmcli -m 0 --simple-disconnect
> > >  mmcli -m 0 --simple-connect="pin=1234,apn=internet"
> > > 
> > > the ModemManager sends debug message "Failed to find primary AT 
> > > port"
> > > to Linux console. However if I will power down and power up the 
> > > development board the ModemManager starts running properly. The 
> > > problem only happen when I issue the above disconnect and then 
> > > connect command.
> > 
> > The UC20 should be using QMI, not AT ports.  qmi_wwan support for
> > the
> > UC20 has been there since 2013.  But to use it, you need to:
> > 
> > 1) ensure qmi_wwan has been built for your kernel
> > 2) ensure you build ModemManager with libqmi support (--with-
> > qmi=yes)
> > 
> > This will solve both your problems, most likely.
> > 
> > Dan
> > 
> > > Best Regards,
> > > 
> > > Jan Graczyk
> > > 
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@redhat.com]
> > > Sent: F

RE: Failed to find primary AT port

[Jan Graczyk]

Hello Dan,

Is ModemManager baud rate configurable to a different value? I know that by 
default ModemManager runs properly with modem baud rate set to 57600.

Best Regards,

Jan Graczyk

-Original Message-
From: Dan Williams [mailto:d...@redhat.com] 
Sent: Tuesday, April 4, 2017 12:19 PM
To: Jan Graczyk <j...@nytec.com>
Cc: modemmanager-devel@lists.freedesktop.org
Subject: Re: Failed to find primary AT port

On Tue, 2017-04-04 at 18:45 +, Jan Graczyk wrote:
> Hello All,
> 
> I am trying to build ModemManager for ARM architecture. However during 
> the compilation I have got the following problem:
> 
> /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> -lgmodule-2.0
> /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> -lgio-2.0
> /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> -lgobject-2.0
> /home/jgraczyk/var_som_mx6_debian/toolchain/gcc-linaro-4.9-2016.02-
> x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-
> gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld: cannot find
> -lglib-2.0
> 
> How can I resolve this problem? I appreciate your help very much.

You need to install neccesary build dependencies for your chosen architecture 
too.  Looks like you're missing glib and its associated libraries for ARM 
installed in the cross-compile library directory.

Dan

> Jan Graczyk
> 
> -Original Message-
> From: Jan Graczyk
> Sent: Monday, April 3, 2017 2:27 PM
> To: 'Dan Williams' <d...@redhat.com>
> Cc: modemmanager-devel@lists.freedesktop.org
> Subject: RE: Failed to find primary AT port
> 
> Hello Dan,
> 
> Thank you for your response. The next question I have for you is how 
> to cross compile ModemManager for ARM architecture. I am using 
> ModemManager version 1.4.2 to build. Is that version stable enough to 
> run on ARM based processor? The version of ModemManager on my target 
> is 1.4.0 and it is working well.
> 
> Best Regards,
> 
> Jan Graczyk
> 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Friday, March 31, 2017 3:15 PM
> To: Jan Graczyk <j...@nytec.com>
> Cc: modemmanager-devel@lists.freedesktop.org
> Subject: Re: Failed to find primary AT port
> 
> On Fri, 2017-03-31 at 21:09 +, Jan Graczyk wrote:
> > Hello Dan,
> > 
> > There is no problem with connecting to this modem (mini PCIe Quectel
> > UC20 modem module) from kermit and sending AT commands. However when 
> > I issue the following commands:
> > 
> >  mmcli -m 0 --simple-disconnect
> >  mmcli -m 0 --simple-connect="pin=1234,apn=internet"
> > 
> > the ModemManager sends debug message "Failed to find primary AT 
> > port"
> > to Linux console. However if I will power down and power up the 
> > development board the ModemManager starts running properly. The 
> > problem only happen when I issue the above disconnect and then 
> > connect command.
> 
> The UC20 should be using QMI, not AT ports.  qmi_wwan support for the
> UC20 has been there since 2013.  But to use it, you need to:
> 
> 1) ensure qmi_wwan has been built for your kernel
> 2) ensure you build ModemManager with libqmi support (--with-qmi=yes)
> 
> This will solve both your problems, most likely.
> 
> Dan
> 
> > Best Regards,
> > 
> > Jan Graczyk
> > 
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Friday, March 31, 2017 1:51 PM
> > To: Jan Graczyk <j...@nytec.com>; modemmanager-devel@lists.freedesk 
> > to p.org
> > Subject: Re: Failed to find primary AT port
> > 
> > On Fri, 2017-03-31 at 20:35 +, Jan Graczyk wrote:
> > > Hello All,
> > > 
> > > I have a problem with ModemManager failing to find primary AT 
> > > port.
> > > Her is the ModemManager debug log:
> > 
> > What kind of modem is this?
> > 
> > Does it require a specific baud rate and/or serial settings?
> > 
> > Can you talk to the modem with 'minicom' on that port when 
> > ModemManager isn't running?
> > 
> > Dan
> > 
> > > root@linaro-alip:~# ModemManager --debug& [1] 1574 root@linaro-al 
> > > ip :~#
> > > ModemManager[1574]:   [1490989871.011

RE: Failed to find primary AT port (Jan Graczyk)

[Einar Jón]

>
> Hello Dan,
>
> Thank you for your response. The next question I have for you is how to cross 
> compile ModemManager for ARM architecture. I am using ModemManager version 
> 1.4.2 to build. Is that version stable enough to run on ARM based processor? 
> The version of ModemManager on my target is 1.4.0 and it is working well.
>

What environment are you using? I use buildroot, and building
ModemManager as a packace there is really straightforward. I can also
confirm that qmi_wwan can work, like Dan says.

>
> On Fri, 2017-03-31 at 21:09 +, Jan Graczyk wrote:
>> Hello Dan,
>>
>> There is no problem with connecting to this modem (mini PCIe Quectel
>> UC20 modem module) from kermit and sending AT commands. However when I
>> issue the following commands:
>>
>>  mmcli -m 0 --simple-disconnect
>>  mmcli -m 0 --simple-connect="pin=1234,apn=internet"

What's your kernel version?
Note that you may need to compile in some extra features from Quectel
in order to get everything to work. A simple way to check is "ls
/dev/ttyUSB*", which should return 4 devices (ttyUSB0 to ttyUSB3).
If that's missing, you might want to add the extra source lines in
this document:
http://support.lyconsys.com/download/3gplus5/Android/USB/Quectel_WCDMA_Linux_USB_Driver_User_Guide_V1.4_Preliminary_20151103.pdf

Or just update your kernel to a newer version (kernel 4.4 seems to
have all the Quectel additions). Without the Quectel additions and the
tty ports the modem is really fragile, and the smallest error can make
it lose connection until the next modem restart (by rebooting the
device or sending an AT+QRST=1,0 command to ttyUSB2 or ttyUSB3).

When installed, you should see a bunch of ttyUSB ports in the System
section of mmcli -m 0:
  System   | device:
'/sys/devices/pci:00/:00:17.0/:01:00.0/:02:08.3/usb2/2-3'
   |drivers: 'qmi_wwan, option1'
   | plugin: 'Generic'
   |   primary port: 'cdc-wdm0'
   |  ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), ttyUSB3
(at), wwan0 (net), cdc-wdm0 (qmi)'

Good luck
Einar Jón
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

RE: Failed to find primary AT port

[Jan Graczyk]

Hello Dan,

Thank you for your response. The next question I have for you is how to cross 
compile ModemManager for ARM architecture. I am using ModemManager version 
1.4.2 to build. Is that version stable enough to run on ARM based processor? 
The version of ModemManager on my target is 1.4.0 and it is working well.

Best Regards,

Jan Graczyk

-Original Message-
From: Dan Williams [mailto:d...@redhat.com] 
Sent: Friday, March 31, 2017 3:15 PM
To: Jan Graczyk <j...@nytec.com>
Cc: modemmanager-devel@lists.freedesktop.org
Subject: Re: Failed to find primary AT port

On Fri, 2017-03-31 at 21:09 +, Jan Graczyk wrote:
> Hello Dan,
> 
> There is no problem with connecting to this modem (mini PCIe Quectel
> UC20 modem module) from kermit and sending AT commands. However when I 
> issue the following commands:
> 
>  mmcli -m 0 --simple-disconnect
>  mmcli -m 0 --simple-connect="pin=1234,apn=internet"
> 
> the ModemManager sends debug message "Failed to find primary AT port"
> to Linux console. However if I will power down and power up the 
> development board the ModemManager starts running properly. The 
> problem only happen when I issue the above disconnect and then connect 
> command.

The UC20 should be using QMI, not AT ports.  qmi_wwan support for the
UC20 has been there since 2013.  But to use it, you need to:

1) ensure qmi_wwan has been built for your kernel
2) ensure you build ModemManager with libqmi support (--with-qmi=yes)

This will solve both your problems, most likely.

Dan

> Best Regards,
> 
> Jan Graczyk
> 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Friday, March 31, 2017 1:51 PM
> To: Jan Graczyk <j...@nytec.com>; modemmanager-devel@lists.freedeskto
> p.org
> Subject: Re: Failed to find primary AT port
> 
> On Fri, 2017-03-31 at 20:35 +, Jan Graczyk wrote:
> > Hello All,
> > 
> > I have a problem with ModemManager failing to find primary AT port.
> > Her is the ModemManager debug log:
> 
> What kind of modem is this?
> 
> Does it require a specific baud rate and/or serial settings?
> 
> Can you talk to the modem with 'minicom' on that port when 
> ModemManager isn't running?
> 
> Dan
> 
> > root@linaro-alip:~# ModemManager --debug& [1] 1574 root@linaro-alip 
> > :~#
> > ModemManager[1574]:   [1490989871.011911] [main.c:140]
> > main():
> > ModemManager (version 1.4.0) starting in system bus...
> > ModemManager[1574]:  [1490989871.035558] [main.c:65]
> > bus_acquired_cb(): Bus acquired, creating manager...
> > ModemManager[1574]:  [1490989871.047317] [mm-plugin- 
> > manager.c:852] load_plugins(): Looking for plugins in
> > '/usr/lib/arm-
> > linux-gnueabihf/ModemManager'
> > ModemManager[1574]:  [1490989871.049618] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Option'
> > ModemManager[1574]:  [1490989871.051062] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Novatel LTE'
> > ModemManager[1574]:  [1490989871.052389] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Linktop'
> > ModemManager[1574]:  [1490989871.053841] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Samsung'
> > ModemManager[1574]:  [1490989871.055357] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Sierra'
> > ModemManager[1574]:  [1490989871.056738] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Gobi'
> > ModemManager[1574]:  [1490989871.058087] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'X22X'
> > ModemManager[1574]:  [1490989871.059471] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'MTK'
> > ModemManager[1574]:  [1490989871.060811] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'AnyDATA'
> > ModemManager[1574]:  [1490989871.062214] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Pantech'
> > ModemManager[1574]:  [1490989871.063564] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Novatel'
> > ModemManager[1574]:  [1490989871.065070] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Nokia'
> > ModemManager[1574]:  [1490989871.066426] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Motorola'
> > ModemManager[1574]:  [1490989871.067906] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Huawei'
> > ModemManager[1574]:  [1490989871.069276] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'SimTech'
> > ModemManager[1574]:  [1490989871.070701] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Option High-Speed'
>

Re: Failed to find primary AT port

[Dan Williams]

On Fri, 2017-03-31 at 21:09 +, Jan Graczyk wrote:
> Hello Dan,
> 
> There is no problem with connecting to this modem (mini PCIe Quectel
> UC20 modem module) from kermit and sending AT commands. However when
> I issue the following commands:
> 
>  mmcli -m 0 --simple-disconnect
>  mmcli -m 0 --simple-connect="pin=1234,apn=internet"
> 
> the ModemManager sends debug message "Failed to find primary AT port"
> to Linux console. However if I will power down and power up the
> development board the ModemManager starts running properly. The
> problem only happen when I issue the above disconnect and then
> connect command.

The UC20 should be using QMI, not AT ports.  qmi_wwan support for the
UC20 has been there since 2013.  But to use it, you need to:

1) ensure qmi_wwan has been built for your kernel
2) ensure you build ModemManager with libqmi support (--with-qmi=yes)

This will solve both your problems, most likely.

Dan

> Best Regards,   
> 
> Jan Graczyk
> 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com] 
> Sent: Friday, March 31, 2017 1:51 PM
> To: Jan Graczyk <j...@nytec.com>; modemmanager-devel@lists.freedeskto
> p.org
> Subject: Re: Failed to find primary AT port
> 
> On Fri, 2017-03-31 at 20:35 +, Jan Graczyk wrote:
> > Hello All,
> > 
> > I have a problem with ModemManager failing to find primary AT port.
> > Her is the ModemManager debug log:
> 
> What kind of modem is this?
> 
> Does it require a specific baud rate and/or serial settings?
> 
> Can you talk to the modem with 'minicom' on that port when
> ModemManager isn't running?
> 
> Dan
> 
> > root@linaro-alip:~# ModemManager --debug& [1] 1574 root@linaro-alip
> > :~# 
> > ModemManager[1574]:   [1490989871.011911] [main.c:140]
> > main(): 
> > ModemManager (version 1.4.0) starting in system bus...
> > ModemManager[1574]:  [1490989871.035558] [main.c:65]
> > bus_acquired_cb(): Bus acquired, creating manager...
> > ModemManager[1574]:  [1490989871.047317] [mm-plugin- 
> > manager.c:852] load_plugins(): Looking for plugins in
> > '/usr/lib/arm- 
> > linux-gnueabihf/ModemManager'
> > ModemManager[1574]:  [1490989871.049618] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Option'
> > ModemManager[1574]:  [1490989871.051062] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Novatel LTE'
> > ModemManager[1574]:  [1490989871.052389] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Linktop'
> > ModemManager[1574]:  [1490989871.053841] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Samsung'
> > ModemManager[1574]:  [1490989871.055357] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Sierra'
> > ModemManager[1574]:  [1490989871.056738] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Gobi'
> > ModemManager[1574]:  [1490989871.058087] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'X22X'
> > ModemManager[1574]:  [1490989871.059471] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'MTK'
> > ModemManager[1574]:  [1490989871.060811] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'AnyDATA'
> > ModemManager[1574]:  [1490989871.062214] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Pantech'
> > ModemManager[1574]:  [1490989871.063564] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Novatel'
> > ModemManager[1574]:  [1490989871.065070] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Nokia'
> > ModemManager[1574]:  [1490989871.066426] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Motorola'
> > ModemManager[1574]:  [1490989871.067906] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Huawei'
> > ModemManager[1574]:  [1490989871.069276] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'SimTech'
> > ModemManager[1574]:  [1490989871.070701] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Option High-Speed'
> > ModemManager[1574]:  [1490989871.072078] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Generic'
> > ModemManager[1574]:  [1490989871.073583] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Iridium'
> > ModemManager[1574]:  [1490989871.075071] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Altair LTE'
> > ModemManager[1574]:  [1490989871.076609] [mm-plugin- 
> > manager.c:877] load_plugins(): Loaded plugin 'Cinterion'
> > ModemManager[1574]:  [1490989871.078085] [mm-plugin- 
&g

RE: Failed to find primary AT port

[Jan Graczyk]

Hello Dan,

There is no problem with connecting to this modem (mini PCIe Quectel UC20 modem 
module) from kermit and sending AT commands. However when I issue the following 
commands:

 mmcli -m 0 --simple-disconnect
 mmcli -m 0 --simple-connect="pin=1234,apn=internet"

the ModemManager sends debug message "Failed to find primary AT port" to Linux 
console. However if I will power down and power up the development board the 
ModemManager starts running properly. The problem only happen when I issue the 
above disconnect and then connect command.

Best Regards,   

Jan Graczyk

-Original Message-
From: Dan Williams [mailto:d...@redhat.com] 
Sent: Friday, March 31, 2017 1:51 PM
To: Jan Graczyk <j...@nytec.com>; modemmanager-devel@lists.freedesktop.org
Subject: Re: Failed to find primary AT port

On Fri, 2017-03-31 at 20:35 +, Jan Graczyk wrote:
> Hello All,
> 
> I have a problem with ModemManager failing to find primary AT port.
> Her is the ModemManager debug log:

What kind of modem is this?

Does it require a specific baud rate and/or serial settings?

Can you talk to the modem with 'minicom' on that port when ModemManager isn't 
running?

Dan

> root@linaro-alip:~# ModemManager --debug& [1] 1574 root@linaro-alip:~# 
> ModemManager[1574]:   [1490989871.011911] [main.c:140] main(): 
> ModemManager (version 1.4.0) starting in system bus...
> ModemManager[1574]:  [1490989871.035558] [main.c:65]
> bus_acquired_cb(): Bus acquired, creating manager...
> ModemManager[1574]:  [1490989871.047317] [mm-plugin- 
> manager.c:852] load_plugins(): Looking for plugins in '/usr/lib/arm- 
> linux-gnueabihf/ModemManager'
> ModemManager[1574]:  [1490989871.049618] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Option'
> ModemManager[1574]:  [1490989871.051062] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Novatel LTE'
> ModemManager[1574]:  [1490989871.052389] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Linktop'
> ModemManager[1574]:  [1490989871.053841] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Samsung'
> ModemManager[1574]:  [1490989871.055357] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Sierra'
> ModemManager[1574]:  [1490989871.056738] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Gobi'
> ModemManager[1574]:  [1490989871.058087] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'X22X'
> ModemManager[1574]:  [1490989871.059471] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'MTK'
> ModemManager[1574]:  [1490989871.060811] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'AnyDATA'
> ModemManager[1574]:  [1490989871.062214] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Pantech'
> ModemManager[1574]:  [1490989871.063564] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Novatel'
> ModemManager[1574]:  [1490989871.065070] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Nokia'
> ModemManager[1574]:  [1490989871.066426] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Motorola'
> ModemManager[1574]:  [1490989871.067906] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Huawei'
> ModemManager[1574]:  [1490989871.069276] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'SimTech'
> ModemManager[1574]:  [1490989871.070701] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Option High-Speed'
> ModemManager[1574]:  [1490989871.072078] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Generic'
> ModemManager[1574]:  [1490989871.073583] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Iridium'
> ModemManager[1574]:  [1490989871.075071] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Altair LTE'
> ModemManager[1574]:  [1490989871.076609] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Cinterion'
> ModemManager[1574]:  [1490989871.078085] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Via CBP7'
> ModemManager[1574]:  [1490989871.079495] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Telit'
> ModemManager[1574]:  [1490989871.081009] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'ZTE'
> ModemManager[1574]:  [1490989871.082448] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Wavecom'
> ModemManager[1574]:  [1490989871.083927] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Longcheer'
> ModemManager[1574]:  [1490989871.085477] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Nokia (Icera)'
> ModemManager[1574]:  [1490989871.086972] [mm-plugin- 
> manager.c:877] load_plugins(): Loaded plugin 'Ericsson MBM'
> ModemManager[1574]:  [1490989871.087122] [mm

Re: Failed to find primary AT port

[Dan Williams]

On Fri, 2017-03-31 at 20:35 +, Jan Graczyk wrote:
> Hello All,
> 
> I have a problem with ModemManager failing to find primary AT port.
> Her is the ModemManager debug log:

What kind of modem is this?

Does it require a specific baud rate and/or serial settings?

Can you talk to the modem with 'minicom' on that port when ModemManager
isn't running?

Dan

> root@linaro-alip:~# ModemManager --debug&
> [1] 1574
> root@linaro-alip:~# ModemManager[1574]:   [1490989871.011911]
> [main.c:140] main(): ModemManager (version 1.4.0) starting in system
> bus...
> ModemManager[1574]:  [1490989871.035558] [main.c:65]
> bus_acquired_cb(): Bus acquired, creating manager...
> ModemManager[1574]:  [1490989871.047317] [mm-plugin-
> manager.c:852] load_plugins(): Looking for plugins in '/usr/lib/arm-
> linux-gnueabihf/ModemManager'
> ModemManager[1574]:  [1490989871.049618] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Option'
> ModemManager[1574]:  [1490989871.051062] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Novatel LTE'
> ModemManager[1574]:  [1490989871.052389] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Linktop'
> ModemManager[1574]:  [1490989871.053841] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Samsung'
> ModemManager[1574]:  [1490989871.055357] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Sierra'
> ModemManager[1574]:  [1490989871.056738] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Gobi'
> ModemManager[1574]:  [1490989871.058087] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'X22X'
> ModemManager[1574]:  [1490989871.059471] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'MTK'
> ModemManager[1574]:  [1490989871.060811] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'AnyDATA'
> ModemManager[1574]:  [1490989871.062214] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Pantech'
> ModemManager[1574]:  [1490989871.063564] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Novatel'
> ModemManager[1574]:  [1490989871.065070] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Nokia'
> ModemManager[1574]:  [1490989871.066426] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Motorola'
> ModemManager[1574]:  [1490989871.067906] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Huawei'
> ModemManager[1574]:  [1490989871.069276] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'SimTech'
> ModemManager[1574]:  [1490989871.070701] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Option High-Speed'
> ModemManager[1574]:  [1490989871.072078] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Generic'
> ModemManager[1574]:  [1490989871.073583] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Iridium'
> ModemManager[1574]:  [1490989871.075071] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Altair LTE'
> ModemManager[1574]:  [1490989871.076609] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Cinterion'
> ModemManager[1574]:  [1490989871.078085] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Via CBP7'
> ModemManager[1574]:  [1490989871.079495] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Telit'
> ModemManager[1574]:  [1490989871.081009] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'ZTE'
> ModemManager[1574]:  [1490989871.082448] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Wavecom'
> ModemManager[1574]:  [1490989871.083927] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Longcheer'
> ModemManager[1574]:  [1490989871.085477] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Nokia (Icera)'
> ModemManager[1574]:  [1490989871.086972] [mm-plugin-
> manager.c:877] load_plugins(): Loaded plugin 'Ericsson MBM'
> ModemManager[1574]:  [1490989871.087122] [mm-plugin-
> manager.c:902] load_plugins(): Successfully loaded 27 plugins
> ModemManager[1574]:  [1490989871.094817] [main.c:87]
> name_acquired_cb(): Service name 'org.freedesktop.ModemManager1' was
> acquired
> ModemManager[1574]:  [1490989871.095004] [mm-base-
> manager.c:479] mm_base_manager_start(): Starting automatic device
> scan...
> ModemManager[1574]:  [1490989871.136373] [mm-base-
> manager.c:518] mm_base_manager_start(): Finished device scan...
> ModemManager[1574]:  [1490989871.139387] [mm-base-
> manager.c:314] device_added(): (tty/ttymxc0): port's parent platform
> driver is not whitelisted
> ModemManager[1574]:  [1490989871.142340] [mm-base-
> manager.c:314] device_added(): (tty/ttymxc1): port's parent platform
> driver is not whitelisted
> ModemManager[1574]:  [1490989871.144381] [mm-plugin-
> manager.c:739] mm_plugin_manager_find_device_support(): (Plugin
> Manager) [/sys/devices/soc0/soc/210.aips-bus/21ec000.serial]
> Checking device support...
> ModemManager[1574]:  [1490989871.145459] [mm-plugin.c:253]
> apply_pre_probing_filters(): (Option)