On 29/4/19 2:57 pm, Lars Melin wrote:
> On 4/29/2019 11:12, Brendan Simon (eTRIX) wrote:
>> I can't get the u-blox LARA R2 device working with ModemManager 1.10.
>>
>> I've tried a Debian Buster (aka Testing) distro that uses
>> ModemManager 1.10 (and kernel 4.19). The serial devices are present
>> but `mmcli -L` does not show any modems.
>>
>> I've also tried the latest Ubuntu 19.04 Disco release (VM image from
>> osboxes.org). It also has ModemManager 1.10 (and kernel 5.0.0) and
>> it also does not work. i.e. the serial devices are present but
>> `mmcli -L` does not show any modems.
>>
>> The only system that I've got to work is Ubuntu 18.10 Cosmic, which
>> uses ModemManager 1.8.2 (and kernel 4.18.0).
>>
>> My guess is that something is broken in ModemManager 1.10 (or some
>> related package or dependency). Can someone confirm that please. Is
>> there anything I can do to test or provide debug info for this. I
>> need to get this working with Debian Buster and MM 1.10.
>>
>> Thanks,
>> Brendan.
>
> Check your dmesg log for creation of ttyACM devices right after the
> LARA R2 is found and probed on the USB bus, you should get 5 of them.
>
> If not then check that cdc_acm is loaded (lsmod) it may have been
> compiled into the kernel in the working system but may have been
> compiled as a module in the non-working systems in which case you have
> to manually load it with "modprobe cdc_acm".
>
> When you have the ttyACM devices and it still doesn't work then is the
> time to check what modemmanager does, the kernel or networkmanager is
> the least likely to be the cause of your problem.
Thanks Lars.
On Ubuntu 18.10 Cosmic (MM 1.8.2) I get the following.
# ls /dev/ttyACM*
/dev/ttyACM0 /dev/ttyACM2 /dev/ttyACM4
/dev/ttyACM1 /dev/ttyACM3 /dev/ttyACM5
# lsmod | grep acm
cdc_acm 32768 4
# mmcli -L
Found 1 modems:
/org/freedesktop/ModemManager1/Modem/1 [u-blox] LARA-R280
# nmcli d
DEVICE TYPE STATE CONNECTION
enp0s3 ethernet connected Wired connection 1
ttyACM0 gsm disconnected --
lo loopback unmanaged --
# nmcli d connect ttyACM0
Device 'ttyACM0' successfully activated with
'f1ec8522-2a76-4e31-938d-87101f2aeb27'.
# lsmod | grep acm
cdc_acm 32768 5
On Ubuntu 19.04 Cosmic (MM 1.10.1) I get the following.
# ls -l /dev/ttyACM*
crw-rw---- 1 root dialout 166, 0 Apr 29 03:02 /dev/ttyACM0
crw-rw---- 1 root dialout 166, 1 Apr 29 03:02 /dev/ttyACM1
crw-rw---- 1 root dialout 166, 2 Apr 29 03:02 /dev/ttyACM2
crw-rw---- 1 root dialout 166, 3 Apr 29 03:02 /dev/ttyACM3
crw-rw---- 1 root dialout 166, 4 Apr 29 03:02 /dev/ttyACM4
crw-rw---- 1 root dialout 166, 5 Apr 29 03:02 /dev/ttyACM5
# lsmod | grep acm
cdc_acm 32768 0
# mmcli -L
No modems were found
# dmesg | grep acm
[ 557.815621] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 557.823421] cdc_acm 1-1:1.2: ttyACM1: USB ACM device
[ 557.831399] cdc_acm 1-1:1.4: ttyACM2: USB ACM device
[ 557.840190] cdc_acm 1-1:1.6: ttyACM3: USB ACM device
[ 557.848698] cdc_acm 1-1:1.8: ttyACM4: USB ACM device
[ 557.856181] cdc_acm 1-1:1.10: ttyACM5: USB ACM device
# journalctl | grep -i modemmanager
Apr 29 03:09:10 osboxes ModemManager[631]: <info> [device
/sys/devices/pci0000:00/0000:00:0b.0/usb1/1-1] creating modem with
plugin 'u-blox' and '6' ports
Apr 29 03:09:10 osboxes ModemManager[631]: <info> Modem for device
'/sys/devices/pci0000:00/0000:00:0b.0/usb1/1-1' successfully created
Apr 29 03:09:16 osboxes ModemManager[631]: <warn> (tty/ttyACM1) at
port timed out 2 consecutive times
Apr 29 03:09:19 osboxes ModemManager[631]: <warn> (tty/ttyACM1) at
port timed out 3 consecutive times
Apr 29 03:09:22 osboxes ModemManager[631]: <warn> (tty/ttyACM1) at
port timed out 4 consecutive times
Apr 29 03:09:25 osboxes ModemManager[631]: <warn> (tty/ttyACM1) at
port timed out 5 consecutive times
Apr 29 03:09:28 osboxes ModemManager[631]: <warn> (tty/ttyACM1) at
port timed out 6 consecutive times
Apr 29 03:09:31 osboxes ModemManager[631]: <warn> (tty/ttyACM1) at
port timed out 7 consecutive times
Apr 29 03:09:33 osboxes ModemManager[631]: <warn> (tty/ttyACM1) at
port timed out 8 consecutive times
Apr 29 03:09:34 osboxes ModemManager[631]: <warn> (tty/ttyACM1) at
port timed out 9 consecutive times
Apr 29 03:09:35 osboxes ModemManager[631]: <error> (tty/ttyACM1) at
port timed out 10 consecutive times, marking modem '(null)' as invalid
Apr 29 03:09:35 osboxes ModemManager[631]: <warn> Modem couldn't be
initialized: couldn't load current capabilities: AT sequence was
cancelled
Apr 29 03:09:35 osboxes ModemManager[631]: <warn> couldn't
initialize the modem: 'Operation was cancelled'
To me everything looks ok from the kernel perspective. I figure
ModemManager is the more likely culprit.
Brendan.
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
