Failed to find primary AT port

Aleksander Morgado aleksander at aleksander.es
Thu Apr 6 17:58:14 UTC 2017


On Thu, Apr 6, 2017 at 12:39 AM, Jan Graczyk <JanG at nytec.com> 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]: <debug> [1491431437.689341] [mm-plugin.c:804] mm_plugin_supports_port(): (Generic) [ttymxc2] probe required: 'at, qcdm'
> ModemManager[1631]: <debug> [1491431437.689422] [mm-port-probe.c:1376] mm_port_probe_run(): (tty/ttymxc2) port probing finished: no more probings needed
> ModemManager[1631]: <debug> [1491431437.689575] [mm-plugin-manager.c:283] port_context_supported(): [plugin manager] task 0,ttymxc2: found best plugin for port (Generic)
> ModemManager[1631]: <debug> [1491431437.689678] [mm-plugin-manager.c:265] port_context_complete(): [plugin manager] task 0,ttymxc2: finished in '10.416165' seconds
> ModemManager[1631]: <debug> [1491431437.690192] [mm-plugin-manager.c:979] device_context_continue(): [plugin manager] task 0: no more ports to probe
> ModemManager[1631]: <debug> [1491431437.690297] [mm-plugin-manager.c:813] device_context_complete(): [plugin manager] task 0: finished in '10.417578' seconds
> ModemManager[1631]: <info>  [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


More information about the ModemManager-devel mailing list