On Mon, Feb 6, 2017 at 5:19 PM, Adam Sherman <[email protected]> wrote: > Sorry for the flood of emails! I'm trying to convey information as it > comes along. > On 2017-02-06 10:54 AM, Adam Sherman wrote: >>> Output of mmcli shows ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0 >>> (qmi), wwp0s20u4i8 (net)'. >> After adding the udev rules, mmcli shows ports: 'ttyUSB0 (unknown), >> ttyUSB1 (unknown), ttyUSB2 (unknown), cdc-wdm0 (qmi), wwp0s20u4i8 >> (net)'. Notable is the addition of ttyUSB1. > > At some point after adding the rule change, qmi-proxy seems to peg one > of my cores basically forever. Is there a log I could look at to > troubleshoot this?
Can you try to manually run the qmi-proxy? $ sudo systemctl stop ModemManager $ sudo killall qmi-proxy $ sudo /usr/lib/libqmi/qmi-proxy --no-exit --verbose > /tmp/qmi-proxy.log 2>&1 & $ sudo systemctl start ModemManager (and retry, log should have gone to /tmp/qmi-proxy.log) -- Aleksander https://aleksander.es _______________________________________________ ModemManager-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
