Requirements for u-blox LARA0-R2 (R280)

Brendan Simon (eTRIX) brendan.simon at etrix.com.au
Sun Apr 28 13:39:23 UTC 2019


On 26/4/19 4:57 pm, Lars Melin wrote:
> On 4/26/2019 08:00, Brendan Simon (eTRIX) wrote:
>
>> # nmcli d
>> DEVICE   TYPE      STATE         CONNECTION
>> eth0     ethernet  connected     wired-connection-1
>> ttyACM0  gsm       disconnected  --
>> sit0     iptunnel  unmanaged     --
>> tunl0    iptunnel  unmanaged     --
>> lo       loopback  unmanaged     --
>>
>>
>> `nmcli` shows a `ttyACM0` serial device (instead of the network
>> interface device).  I'm expecting something like `cdc-wdm0`.  Is that
>> a correct assumption?
>
> No it is a wrong assumption, there are only cdc_acm serial interfaces
> in this device, no net interfaces.

Thanks Lars.  It works fine on an Ubuntu VM (18.10 Cosmic) and I can see
there is no `wwan` network interface, just the cdc_acm serial interfaces.

Ubuntu is using modemmanager v1.8.2 and network-manager 1.12.4 and
kernel 4.18.0.

My Debian embedded testing system is using modemmanager v1.10.0,
network-manager 1.14.6 and kernel 4.4.0 (custom build, armhf).

Since MM 1.14.6 communicates ok with the modem (i.e. mmcli gives
sensible output), am I safe to assume all the kernel support is there to
bring up the modem via Network Manager?  i.e. can I rule out the 4.4.0
kernel as a source of the problem?

Thanks, Brendan.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20190428/584fa929/attachment.html>


More information about the ModemManager-devel mailing list