On Tue, Mar 6, 2018 at 5:56 PM, Aleksander Morgado
wrote:
> We used ttyACM0 as secondary port until now, just because we had an
> extra AT capable TTY around in addition to the main control ttyACM2
> port.
>
> Turns out, using this ttyACM0 may actually break the
>
> The "gsm" connection type name in NetworkManager is misleading. We use
> "gsm" to refer to all 3GPP connection types (e.g. GSM, GPRS, EDGE,
> UMTS, HSPA, LTE...).
> What is the output of "mmcli -m 0" when you have the modem connected?
> You shouldn't have needed to --set-current-capabilities.
I would be, too, especially interested in any usb dongle or pci device
that could use 4G, but *without* a web ui, rather with mmcli. Telephony
would be a bonus.
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
Hi,
That’s now half a year I’m using modem-manager-gui and mmcli for mainly
smses and ringing, since I did first put my sim card in my computer it
has greatly helped me to get rid of my previous phone, which I anyway
adopted unwillingly/a-bit-forcedly and didn’t have a fully free
operative system
>>> > > Was the wwan0 interface down while you executed simple-connect?
>>> >
>>> > wwan0 being up is the most likely cause. But seeing the debug logs
>>> > to
>>> > confirm this would be good.
>>> >
>>> > I started thinking about solving this in the driver, but ended up
>>> > falling back to the
We used ttyACM0 as secondary port until now, just because we had an
extra AT capable TTY around in addition to the main control ttyACM2
port.
Turns out, using this ttyACM0 may actually break the connection setup
in the wwan interface in a bad way (e.g. not allowing DHCP setup).
The suggestion