Re: ModemManager Process is shutting down

2020-10-19 Thread ratnavel
Thanks Aleksander. Will update and try on it On Fri, Oct 16, 2020 at 9:20 PM Aleksander Morgado wrote: > Hey, > > > Before Logs: > > > > ModemManager[104]: Signal strength (umts): -79 dBm > > ModemManager[104]: Signal strength: -79 dBm --> 55% > > ModemManager[104]: Modem

Re: ModemManager Process is shutting down

2020-10-16 Thread ratnavel
Before Logs: ModemManager[104]: Signal strength (umts): -79 dBm ModemManager[104]: Signal strength: -79 dBm --> 55% ModemManager[104]: Modem /org/freedesktop/ModemManager1/Modem/1: access technology changed (unknown -> umts) ModemManager[104]: Modem /org/freedesktop/ModemManager1/Modem/1:

ModemManager Process is shutting down

2020-10-14 Thread ratnavel
could possibly be the issue here ? Thanks, Ratnavel ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Reloading stats failed: QMI operation failed: Transaction timed out

2020-07-16 Thread ratnavel
Thanks on the input. In this case it seems to be in a permanently stuck state and no communication whatsoever. Will check for any other symptoms leading to this state. Thanks, Ratnavel On Wed, Jul 15, 2020 at 12:36 PM Bjørn Mork wrote: > Aleksander Morgado writes: > > >> &g

Re: Reloading stats failed: QMI operation failed: Transaction timed out

2020-07-16 Thread ratnavel
* Planning to upgrade to *02.33.03.00* Any other pointers to confirm this is a modem firmware issue? Thanks, Ratnavel On Wed, Jul 15, 2020 at 12:16 PM Aleksander Morgado < aleksan...@aleksander.es> wrote: > Hey! > > > > > WARNING: CPU: 1 PID: 0 at /linux-4.10.0/net

Re: Reloading stats failed: QMI operation failed: Transaction timed out

2020-07-14 Thread ratnavel
( qmi_wwan) https://lists.freedesktop.org/archives/libqmi-devel/2015-October/001310.html I will try out with *1.12.x *and check. Thanks, Ratnavel On Mon, Jul 13, 2020 at 8:39 PM Aleksander Morgado wrote: > Hey, > > > > > ModemManager - 1.10.8 ( Ubuntu 16.06.4) running on

Reloading stats failed: QMI operation failed: Transaction timed out

2020-07-13 Thread ratnavel
error mean and is Modem Reset the only option to bring the modem out of this state ? Thanks, Ratnavel ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Rejected Send Message when starting with paranoid as argument

2020-06-29 Thread ratnavel
Thanks Aleksander and Enrico !! Will try out the same. Regards, Ratnavel On Mon, Jun 29, 2020 at 1:12 PM Aleksander Morgado wrote: > Hey > > > > > I am using a ModemManager - 1.8.4 ( Ubuntu 16.06.4) running on a > Sierra Wireless EM74xx modem. > > > &g

Rejected Send Message when starting with paranoid as argument

2020-06-29 Thread ratnavel
t;0" destination=":1.10" (uid=0 pid=1222 comm="/usr/bin/MyDaemond ") This happens only when I start with an argument paranoid. How can this be prevented ? Thanks, Ratnavel ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: ANN: ModemManager 1.8.4

2019-07-04 Thread ratnavel
Hey Aleksander, Thanks for the quick update !! Would try this out. Is this also available with the Ubuntu 16.04 PPA you had mentioned earlier? Thanks, Ratnavel On Thu, Jul 4, 2019 at 7:37 PM Aleksander Morgado wrote: > Hey hey, > > This is the second bugfix release in the ModemMana

ModemManager warning messages

2019-07-02 Thread ratnavel
HI, I am using a ModemManager - 1.6.4 ( Ubuntu 16.06.4) running on a Sierra Wireless EM74xx modem I happen to run the following command multiple times ( modem resets as part of test functionality). mmcli -m 1 --reset The LTE interface came up fine and got connected after the reset but seeing