Re: u-blox R410M modem (QMI) configuration with modern Network-manager

2018-11-30 Thread Tim Harvey
On Fri, Nov 30, 2018 at 12:26 PM Dan Williams wrote: > > On Fri, 2018-11-30 at 11:24 -0800, Tim Harvey wrote: > > On Fri, Nov 30, 2018 at 3:12 AM Aleksander Morgado > > wrote: > > > Hey, > > > > > > > I'm trying to use a u-blox QMI R410M with

Re: u-blox R410M modem (QMI) configuration with modern Network-manager

2018-11-30 Thread Tim Harvey
On Fri, Nov 30, 2018 at 3:12 AM Aleksander Morgado wrote: > > Hey, > > > I'm trying to use a u-blox QMI R410M with network manager on Ubuntu > > bionic witht he following which works fine on Ubuntu xenial: > > > > # nmcli connection add type gsm ifname cdc-wdm0 con-name mymodem apn $APN > > #

u-blox R410M modem (QMI) configuration with modern Network-manager

2018-11-29 Thread Tim Harvey
Greetings, I'm trying to use a u-blox QMI R410M with network manager on Ubuntu bionic witht he following which works fine on Ubuntu xenial: # nmcli connection add type gsm ifname cdc-wdm0 con-name mymodem apn $APN # nmcli connection up id mymodem The modem's QMI interface is indeed

Re: primary device changing from boot to boot

2017-09-05 Thread Tim Harvey
On Tue, Sep 5, 2017 at 1:59 PM, Dan Williams <d...@redhat.com> wrote: > On Tue, 2017-09-05 at 12:32 -0700, Tim Harvey wrote: >> On Tue, Sep 5, 2017 at 9:53 AM, Dan Williams <d...@redhat.com> wrote: >> > On Tue, 2017-09-05 at 09:38 -0700, Tim Harvey wrote: >> >

Re: primary device changing from boot to boot

2017-09-05 Thread Tim Harvey
On Tue, Sep 5, 2017 at 9:56 AM, Pičugins Arsenijs wrote: > I don't know if it's going to help you with this issue, but if you can > hardcode a path to the serial port somewhere, take a look in the > "/dev/serial/by-id" directory - it has symlinks to /dev/tty* entries that >

Re: primary device changing from boot to boot

2017-09-05 Thread Tim Harvey
On Tue, Sep 5, 2017 at 9:53 AM, Dan Williams <d...@redhat.com> wrote: > On Tue, 2017-09-05 at 09:38 -0700, Tim Harvey wrote: >> On Fri, Sep 1, 2017 at 1:22 PM, Dan Williams <d...@redhat.com> wrote: >> > On Fri, 2017-09-01 at 13:01 -0700, Tim Harvey wrote: >> &

Re: primary device changing from boot to boot

2017-09-05 Thread Tim Harvey
On Fri, Sep 1, 2017 at 1:22 PM, Dan Williams <d...@redhat.com> wrote: > On Fri, 2017-09-01 at 13:01 -0700, Tim Harvey wrote: >> Greetings, >> >> I've got a Sierra Wireless HL7588 modem which exposes three ttyACM >> devs via the cdc_acm driver. The device appears

Re: MC7455 'Call Failed'

2017-06-27 Thread Tim Harvey
On Fri, Jun 23, 2017 at 9:23 AM, Dan Williams <d...@redhat.com> wrote: > On Thu, 2017-06-22 at 15:11 -0700, Tim Harvey wrote: >> On Thu, Jun 22, 2017 at 2:59 PM, Dan Williams <d...@redhat.com> >> wrote: >> > On Thu, 2017-06-22 at 23:29 +0200, Aleksander Morgad

Re: MC7455 'Call Failed'

2017-06-23 Thread Tim Harvey
On Wed, Jun 21, 2017 at 10:00 AM, Aleksander Morgado <aleksan...@aleksander.es> wrote: > On Wed, Jun 21, 2017 at 6:22 PM, Tim Harvey <thar...@gateworks.com> wrote: >> error: couldn't start network: QMI protocol error (14): 'CallFailed' >> call end reason (1018): gs

Re: MC7455 'Call Failed'

2017-06-22 Thread Tim Harvey
On Thu, Jun 22, 2017 at 2:59 PM, Dan Williams <d...@redhat.com> wrote: > On Thu, 2017-06-22 at 23:29 +0200, Aleksander Morgado wrote: >> On Thu, Jun 22, 2017 at 10:11 PM, Tim Harvey <thar...@gateworks.com> >> wrote: >> > > > Also, I'm unclear how to Networ

Re: MC7455 'Call Failed'

2017-06-22 Thread Tim Harvey
On Thu, Jun 22, 2017 at 8:35 AM, Aleksander Morgado wrote: > Hey, > >> >> The MC7455 presents two QMI+WWAN pairs which I think is quite common >> for the Sierra Wireless modems. The first appears to be raw-ip and the >> 2nd 802.3. Most of the qmicli commands won't work