Dear Brendan Simon,
well, nmcli is coherent with MM, and MM is not able to find out a cdc-wdm
device:
| primary port: ttyACM0
I have no experience with u-blox device, so I am not able to give you a good
recommendation.
Still, maybe looking at the qmi-wwan.c driver in the current git kernel
repository might give you some ideas?
e.g.: commit 9306b38e42cb266f98bff6f6f4c1c652aa79ba45 ("NET: usb: qmi_wwan: add
support for ublox R410M PID 0x90b2").
Have a good day and hope you can solve your problem.
Enrico
On Fri, 26 Apr 2019, Brendan Simon (eTRIX) wrote:
Date: Fri, 26 Apr 2019 03:00:21
From: "Brendan Simon (eTRIX)" <brendan.si...@etrix.com.au>
To: modemmanager-devel@lists.freedesktop.org
Subject: Requirements for u-blox LARA0-R2 (R280)
I'm trying to get a u-blox LARA-R280 device working with my embedded linux
build -- using Linux kernel 4.4.0 (armhf) and
Debian Buster (testing).
* ModemManagerv 1.10.0
* NetworkManager 1.14.6
ModemManager discovers the device ok, but NetworkManger does not see a network
device (e.g. `cdc-wdm0` which is what I get
with a Quectel modem).
# mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [u-blox] LARA-R280
# mmcli -m 0
--------------------------------
General | dbus path: /org/freedesktop/ModemManager1/Modem/0
| device id: cefae5a09feceda70ab244f864cd3239d518b487
--------------------------------
Hardware | manufacturer: u-blox
| model: LARA-R280
| revision: 30.43
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 357364080026759
--------------------------------
System | device:
/sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1
| drivers: cdc_acm
| plugin: u-blox
| ports: ttyACM3 (unknown), ttyACM4 (unknown),
ttyACM5 (unknown),
| ttyACM0 (at), ttyACM1 (at), ttyACM2 (at)
--------------------------------
Status | unlock retries: sim-pin (3), sim-pin2 (3), sim-puk (10),
sim-puk2 (10)
| state: registered
| power state: on
| access tech: lte
| signal quality: 60% (recent)
--------------------------------
# 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?
I hand to Monkey patch my kernel to work with the Quectel device (following
documents from Quetel), but I can't find any
information from u-blox about kernel driver requirements (other than the device
works with standard linux drivers).
Any ideas what drivers I need configured/enabled/patched to get the LARA-R2
module to enumerate as a network device?
Thanks,
Brendan.
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
