Hi Alkesander,
Thanks for the advice.
Attached are my log files from MM and qmi-proxy.
This time when I set the preferred mode to 2G via MM, the sequence from AT-cmd did not change (first 4G then 2G). And after setting to 4G, the sequence from modem changed to: first 2G then 4G. See
Hey Peter,
> > > Wondering, would you be able to also test 1.18.4 but with these 2
> > > changes reverted? The regex related fix was a big one, maybe it broke
> > > something else.
> > >
> > > 2beae71a6 kerneldevice,generic: simplify DEVPATH matching logic
> > > 1bd70df8a kerneldevice,generic:
Hey Peter,
> > Wondering, would you be able to also test 1.18.4 but with these 2
> > changes reverted? The regex related fix was a big one, maybe it broke
> > something else.
> >
> > 2beae71a6 kerneldevice,generic: simplify DEVPATH matching logic
> > 1bd70df8a kerneldevice,generic: input pattern
On 12/1/21 5:11 AM, Aleksander Morgado wrote:
Hey Peter
Wondering, would you be able to also test 1.18.4 but with these 2
changes reverted? The regex related fix was a big one, maybe it broke
something else.
2beae71a6 kerneldevice,generic: simplify DEVPATH matching logic
1bd70df8a
Hey,
> 2. Then I set the priority to 2G. Both MM and AT-cmd shows the 2G has now
> priority.
>
> # mmcli -m 1 --set-allowed-modes='2g|4g' --set-preferred-mode='2g'
> successfully set current modes in the modem
> #
> # mmcli -m 1 --command="AT+QCFG=\"nwscanseq\""
> response: '+QCFG:
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
Hi Aleksander and Amol,
Il giorno mar 30 nov 2021 alle ore 09:54 Aleksander Morgado
ha scritto:
>
> If this works for you in MBIM I guess it's because the AT commands to
> change bands using the Telit shared utils do wait for the band change
> to take effect before going on. Maybe @Daniele
