Hey,
>
> I am trying to configure Sierra Wireless MC7354 module on Ubuntu 14.04 and
> its not working properly .Please advise what could be wrong…Any help in ths
> regard is much appreciated. Many Thanks
>
>
>
>
>
> Nabeel
>
>
>
> ModemManager version 1.0.0
>
>
This is a way too old MM
On Mon, 2017-09-18 at 21:38 -0700, Aleksander Morgado wrote:
> On Mon, Sep 18, 2017 at 8:13 AM, Ben Chan
> wrote:
> > Similar to firmware revision, hardware revision is useful
> > information
> > for identifying characteristics about a modem module. Both MBIM and
> > QMI
On 18/09/17 09:10, Ben Chan wrote:
> This patches fixes commit 334273979 "broadband-modem-mbim: preserve
> unlock retries for PIN1 when appropriate", which doesn't correctly
> propagate the unlock retries information for PIN1 observed from
> responses to MBIM_CID_PIN set operations (see commit
On 18/09/17 09:10, Ben Chan wrote:
> This patch adds a mm_iface_modem_get_unlock_retries helper for getting
> the current MMUnlockRetries value of a MMIfaceModem object, which later
> allows us to partially update (e.g. a specific MMModemLock) the
> MMUnlockRetries value of a MMIfaceModem object.
Hey,
>
> I m having issues with the above modem.The modem is detected and lsusb
> output is ok but mmcli -L shows no modem found. Please see attached log
> image.
> Can you please advise whats wrong.
>
What libqmi, libmbim and ModemManager versions are you using?
Also, there's no attached
Hi,
I m having issues with the above modem.The modem is detected and lsusb
output is ok but mmcli -L shows no modem found. Please see attached log
image.
Can you please advise whats wrong.
Many Thanks
Nabeel
___
ModemManager-devel mailing list
On Mon, 2017-09-18 at 21:30 -0700, Aleksander Morgado wrote:
> On Mon, Sep 18, 2017 at 9:10 AM, Ben Chan
> wrote:
> > This patches fixes commit 334273979 "broadband-modem-mbim: preserve
> > unlock retries for PIN1 when appropriate", which doesn't correctly
> > propagate the
Hi Aleksander and Rowan,
2017-09-19 18:53 GMT+02:00 Aleksander Morgado :
>>
>>
>> Interesting, in the testing lab they noticed that they only saw this being a
>> problem when ModemManager was running. But if your telling me that it’s
>> related to the modules firmware...