Hey
> > I am revisiting this with a little more information, and a better
> > understanding of what you wrote.
> >
> > A simple-connect from ModemManager always fails. I can always connect
> > from qmicli (Abbreviated log below; stripped out raw data in this
> > trace)
> >
> > But as you say, when
ksander Morgado
> ; modemmanager-devel@lists.freedesktop.org
> Subject: [**EXTERNAL**] Re: Can't connect using ModemManager when modem is
> in QMI mode
>
> On Wed, 2022-01-19 at 17:25 +, Bushman, Jeff wrote:
> > Hi Aleksander,
> >
> > I am revisiting this wit
'unspecified',
> password: 'unspecified', autoconnect: 'unspecified')
> [12 Jan 2022, 01:23:09] [Debug] Asynchronously starting network...
> [12 Jan 2022, 01:23:09] [Debug] [/dev/cdc-wdm0] Sent generic request
> (translated)...
> <<<<<<
lt;<<< flags = "none"
<<<<<< transaction = 1
<<<<<< tlv_length = 16
<<<<<< message = "Start Network" (0x0020)
<<<<<< TLV:
<<<<<< type = "IP Family Pre
Hey
On Wed, Dec 1, 2021 at 7:34 PM Bushman, Jeff wrote:
>
> I have attached the modem manager debug logs. Search for "simple connect".
> One odd thing I noticed was a log message about "reseting expected kernel
> data format to 802.3 in data interface 'wwan0'" which is not correct. The
> inter
Hey Jeff,
> I'm running a Sierra Wireless MC7455 modem with SWI9X30C_02.32.11.00 r8042
> CARMD-EV-FRMWR2 firmware. Using ModemManager 1.18.2 on Ubuntu 20.04.
>
> I can get the modem to connect using mmcli -m 0 --simple-connect=. when the
> modem is in MBIM mode.
> I can get the modem to connect
I'm running a Sierra Wireless MC7455 modem with SWI9X30C_02.32.11.00 r8042
CARMD-EV-FRMWR2 firmware. Using ModemManager 1.18.2 on Ubuntu 20.04.
I can get the modem to connect using mmcli -m 0 --simple-connect=. when the
modem is in MBIM mode.
I can get the modem to connect using qmicli and qmi-n
