<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#663300" bgcolor="#FFFFFF"> On 26/4/19 4:57 pm, Lars Melin wrote: <blockquote type="cite" cite="mid:44e6a619-965d-2fb4-f9ce-e1dfce83cf99@gmail.com">On 4/26/2019 08:00, Brendan Simon (eTRIX) wrote: <blockquote type="cite"># 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? </blockquote> No it is a wrong assumption, there are only cdc_acm serial interfaces in this device, no net interfaces. </blockquote> 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. </body> </html>