On Tue, 2017-04-04 at 21:27 -0400, Liam Monahan wrote:
> I definitely see the conspicuous gap you see with no dial out to #777
> happening. The
> logs that are there are unpruned straight from journalctl. If I
> hotplug the modem
> back in, then I see additional info about the connection being
On Mon, 2017-04-03 at 11:15 -0400, Liam Monahan wrote:
> Thanks for your guidance.
>
> When the device doesn’t show up in NM, it can’t be seen through
> mmcli. I turned up the logging level to see what’s going on. Maybe
> you have a different reading of this, but the first thing that jumps
>
Thanks for your guidance.
When the device doesn’t show up in NM, it can’t be seen through mmcli. I
turned up the logging level to see what’s going on. Maybe you have a different
reading of this, but the first thing that jumps out at me is that something
seems to be sending NM/MM a TERM
On Wed, 2017-03-29 at 10:48 -0400, Liam Monahan wrote:
> I have a USB cellular modem that will not show up in nm on boot. If
> the system is started up and I unplug and plug it back in, it shows
> up then. These device are deployed out in the field, so manual
> intervention is not a real option
I have a USB cellular modem that will not show up in nm on boot. If the system
is started up and I unplug and plug it back in, it shows up then. These device
are deployed out in the field, so manual intervention is not a real option for
my use case unfortunately.
device is ttyUSB3 and does
