ublox SARA-U260 not showing up in mmcli

[Aleksander Morgado]

On Sat, May 6, 2017 at 6:48 AM, Brent Sink <brents_3 at hotmail.com> wrote:
> Since I have a workaround by pasting what's on the clipboard it's at least
> progress, but I don't know if this is actually preventing modem manager from
> working correctly.

Just to clarify: can you run minicom with 57600bps (not 115200) and
talk to the modem via ttyACM0? I wouldn't have expected this kind of
issues on a USB serial modem, but who knows.

Could you try to add a new file with a new udev rule to set
ID_MM_TTY_BAUDRATE to 115200 and retry? You need ModemManager git
master for this though, no 1.6.x version has this yet.

$ sudo vim /lib/udev/rules.d/78-mm-baudrate.rules

    ACTION!="add|change|move", GOTO="mm_my_modem_end"
    DEVPATH=="/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.4/*",
ENV{ID_MM_TTY_BAUDRATE}="115200"
    LABEL="mm_my_modem_end"

The DEVPATH value you need to change it to match the one in your system; e.g.:

$ realpath /sys/class/tty/ttyACM0/device/
/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.4/1-1.4:1.2

So DEVPATH in this case would be:
"/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.4/"
(skip the /sys prefix and the last block, so that DEVPATH covers all
TTYs in the modem, not just that ttyACM0)

Once the file is in place:
$ sudo udevadm control --reload
$ sudo udevadm trigger

And rerun ModemManager.

Alternatively, you could talk to the device via minicom and change the
baudrate the modem expects to 57600, which is what MM uses as default.

-- 
Aleksander
https://aleksander.es