ModemManager support on ARM?

[Ajay Garg]

Hi All.

Is modem-manager supported on ARM?

For x86, I have had seamless experience of using modem-manager, but am
unsure about ARM.
So, will be grateful for some light in this regard.


Thanks and Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Support for Sierra Wireless MC7455 and MC7430

[Ajay Garg]

Great, thanks a ton Aleksander !!

As usual, the  Quick, Crisp, Effective Aleksander :)
Once again, many thanks !!


Thanks and Regards,
Ajay

On Tue, Mar 19, 2019 at 2:10 PM Aleksander Morgado
 wrote:
>
> > https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices
> > lists the supported modems, but the link seems old.
> >
> > In particular, MC7304 is already end-of-life, and Sierra-Wireless guys
> > have suggested MC7455 / MC7430.
> >
> > Are any of MC7455 / MC7430 supported (yet) on ModemManager?
> >
>
> Both are supported; just keep in mind that for the MC74xx family, you
> also need a new enough kernel (>= 4.5) because these devices run only
> in raw-ip mode, and the raw-ip support for the QMI kernel driver was
> added in 4.5.
>
> --
> Aleksander
> https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Support for Sierra Wireless MC7455 and MC7430

[Ajay Garg]

Hi All.

https://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices
lists the supported modems, but the link seems old.

In particular, MC7304 is already end-of-life, and Sierra-Wireless guys
have suggested MC7455 / MC7430.

Are any of MC7455 / MC7430 supported (yet) on ModemManager?


Will be grateful for a reply.


Thanks and Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Default "ip-type" in modem-manager "simple-connect"?

[Ajay Garg]

Thanks a ton Aleksander !!!

On Fri, Mar 24, 2017 at 2:43 PM, Aleksander Morgado <
aleksan...@aleksander.es> wrote:

> On Fri, Mar 24, 2017 at 4:20 AM, Ajay Garg <ajaygargn...@gmail.com> wrote:
> > If we don't specify ip-type parameter while doing a simple-connect via
> mmcli
> > (http://manpages.ubuntu.com/manpages/trusty/man8/mmcli.8.html), what is
> the
> > default parameter picked? ipv4 or ipv6? Or whatever the network offers?
>
> It defaults to IPv4
>
> --
> Aleksander
> https://aleksander.es
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Are the commands to fetch IMEI/IMSI integrated in mmcli?

[Ajay Garg]

Thanks Aleksander.

That worked like a charm !!


Thanks and Regards,
Ajay

On Tue, Oct 18, 2016 at 12:38 AM, Aleksander Morgado <
aleksan...@aleksander.es> wrote:

> On Mon, Oct 17, 2016 at 8:34 PM, Ajay Garg <ajaygargn...@gmail.com> wrote:
> > https://mail.gnome.org/archives/networkmanager-list/
> 2011-September/msg00137.html
> > seems to be quite an old thread, but the following two are NOT listed in
> > SIM-options in the Modem-manager that I currently use (neither do they
> work)
> > ::
> >
> >   --card-get-imei Get IMEI of the
> modem
> >   --card-get-imsi Get IMSI of the SIM
> > card
> >
> >
> > So, just a quick question, are the above two features present in the
> > "latest" Modem-Manager?
>
> They are not given as command line options, but as part of the SIM/modem
> info:
>
> * If you want to get the IMSI, you can show the information of the SIM
> card (e.g. "mmcli -i 0" for SIM card in index 0), and there you'll get
> the IMSI reported.
> * If you want to get the IMEI, you can show the information of the
> modem (e.g. "mmcli -m 0" for modem in index 0), and there you'll get
> the IMEI reported (in the 3GPP section).
>
> --
> Aleksander
> https://aleksander.es
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Are the commands to fetch IMEI/IMSI integrated in mmcli?

[Ajay Garg]

Hi Aleksander.

https://mail.gnome.org/archives/networkmanager-list/2011-September/msg00137.html
seems to be quite an old thread, but the following two are NOT listed in
SIM-options in the Modem-manager that I currently use (neither do they
work) ::

  --card-get-imei Get IMEI of the modem
  --card-get-imsi Get IMSI of the SIM card


So, just a quick question, are the above two features present in the
"latest" Modem-Manager?

-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: [URGENT] Regressions in latest QMI-related packages

[Ajay Garg]

Ohh... as per
https://lists.freedesktop.org/archives/modemmanager-devel/2016-August/003338.html,
mmcli talks just to ModemManager.

So, as long as ModemManager does not mix up "external requests from mmcli"
and "internally generated requests", I guess we are fine on this front.

On Mon, Oct 17, 2016 at 11:35 PM, Ajay Garg <ajaygargn...@gmail.com> wrote:

> I tried switching to Direct-IP mode, and ALL mmcli-commands (including *mmcli
> -m 0 --set-allowed-modes='2G'*) work fine from mmcli itself (without
> using any AT-commands as such).
>
>
> a)
> Is this expected behaviour?
>
> b)
> Now, since qmi-proxy is no more there, there are chances of interminglings
> due to working of ModemManager and mmcli together, right?
>
> On Mon, Oct 17, 2016 at 8:48 PM, Aleksander Morgado <
> aleksan...@aleksander.es> wrote:
>
>> On Mon, Oct 17, 2016 at 5:10 PM, Ajay Garg <ajaygargn...@gmail.com>
>> wrote:
>> > :O :O :O :O
>> >
>> > Of course I switched it to QMI.
>> > The previous unit that I did all the tests on, ran perfect when
>> switched to
>> > QMI mode.
>> >
>> > Your reply suggests that some functionalities (like switching to
>> > 2G-only-mode) would not work in Direct-IP mode.
>> > If so, Direct-IP would not serve our purpose.
>> >
>>
>> No, I didn't say that. Switching to 2G mode should be ok in Direct IP
>> mode, using AT commands.
>>
>> > I am in the process of retrieving the "ati" output of the earlier-modem
>> (on
>> > which things worked perfect in QMI-mode).
>> > That could probably help in determining if some firmware-mismatch is
>> causing
>> > any issue.
>> >
>> >
>> > But Aleksander, this is really bad news.
>> > Any idea what might have made things working in the earlier-modem in
>> QMI?
>>
>> I have no idea; was it a MC8090 as well?
>>
>> --
>> Aleksander
>> https://aleksander.es
>>
>
>
>
> --
> Regards,
> Ajay
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: [URGENT] Regressions in latest QMI-related packages

[Ajay Garg]

I tried switching to Direct-IP mode, and ALL mmcli-commands (including *mmcli
-m 0 --set-allowed-modes='2G'*) work fine from mmcli itself (without using
any AT-commands as such).


a)
Is this expected behaviour?

b)
Now, since qmi-proxy is no more there, there are chances of interminglings
due to working of ModemManager and mmcli together, right?

On Mon, Oct 17, 2016 at 8:48 PM, Aleksander Morgado <
aleksan...@aleksander.es> wrote:

> On Mon, Oct 17, 2016 at 5:10 PM, Ajay Garg <ajaygargn...@gmail.com> wrote:
> > :O :O :O :O
> >
> > Of course I switched it to QMI.
> > The previous unit that I did all the tests on, ran perfect when switched
> to
> > QMI mode.
> >
> > Your reply suggests that some functionalities (like switching to
> > 2G-only-mode) would not work in Direct-IP mode.
> > If so, Direct-IP would not serve our purpose.
> >
>
> No, I didn't say that. Switching to 2G mode should be ok in Direct IP
> mode, using AT commands.
>
> > I am in the process of retrieving the "ati" output of the earlier-modem
> (on
> > which things worked perfect in QMI-mode).
> > That could probably help in determining if some firmware-mismatch is
> causing
> > any issue.
> >
> >
> > But Aleksander, this is really bad news.
> > Any idea what might have made things working in the earlier-modem in QMI?
>
> I have no idea; was it a MC8090 as well?
>
> --
> Aleksander
> https://aleksander.es
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: [URGENT] Regressions in latest QMI-related packages

[Ajay Garg]

:O :O :O :O

Of course I switched it to QMI.
The previous unit that I did all the tests on, ran perfect when switched to
QMI mode.

Your reply suggests that some functionalities (like switching to
2G-only-mode) would not work in Direct-IP mode.
If so, Direct-IP would not serve our purpose.

I am in the process of retrieving the "ati" output of the earlier-modem (on
which things worked perfect in QMI-mode).
That could probably help in determining if some firmware-mismatch is
causing any issue.


But Aleksander, this is really bad news.
Any idea what might have made things working in the earlier-modem in QMI?




On Mon, Oct 17, 2016 at 8:26 PM, Aleksander Morgado <
aleksan...@aleksander.es> wrote:

> On Mon, Oct 17, 2016 at 5:13 AM, Ajay Garg <ajaygargn...@gmail.com> wrote:
> >
> > Please find the debug-logs-file for ModemManager attached, plus the
> > attempt-logs for starting NetworkManager as per the link.
> >
> >
> > Kindly let know what is the issue, and what steps I need to follow next
> to
> > nail the issue.
> >
>
> Something's wrong somewhere.
>
> Did you by any chance try to switch the MC8090 to QMI mode? (from an
> older email from you,
> https://lists.freedesktop.org/archives/modemmanager-devel/
> 2016-August/003334.html).
> The device is exposing a /dev/cdc-wdm port, but which doesn't respond
> at all, so the Sierra plugin (which does QMI) ends up falling back to
> the AT-only generic modem, and the generic modem doesn't know how to
> manage sierra-specific allowed modes (e.g. switching to 2G-only).
>
> I have never seen any of the MC8090 modems being driven in QMI so I'm
> assuming this is not the right approach. I'd suggest you fallback
> again to "Direct IP" mode, which is what the modem supports (i.e. AT
> commands and a WWAN interface) and then you should see the "Sierra
> legacy" plugin driving the modem.
>
> --
> Aleksander
> https://aleksander.es
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: [URGENT] Regressions in latest QMI-related packages

[Ajay Garg]

In fact, once a steady state is reached, when the following are seen in the
mmcli ::

#
*mmcli -m 0 -e*
successfully enabled the modem

*mmcli -m 0 --set-allowed-modes='2G'*
error: couldn't set current modes: 'GDBus.Error:org.freedesktop.
ModemManager1.Error.Core.Unsupported: Setting allowed modes not supported'

*mmcli -m 0 -r*
error: couldn't reset the modem: 'GDBus.Error:org.freedesktop.
ModemManager1.Error.Core.Unsupported: Cannot reset the modem: operation not
supported'
#



there is no growth as such in ModemManager logs (being run in debug mode);
only occasional following logs are seen ::


#
ModemManager[2423]:  [1476696354.255819] [mm-port-serial-at.c:459]
debug_log(): (ttyUSB2): <-- '+CREG:
2+CREG: 2'
#


What's this mystery???
Is MM experiencing some confusion regarding the /dev/ttyUSB* ports? just a
wild guess :-\



On Mon, Oct 17, 2016 at 2:53 PM, Ajay Garg <ajaygargn...@gmail.com> wrote:

> Hi Aleksander.
>
> Do you see anything in the logs?
> It seems the Sierra-plugin is being identified fine.
>
>
>
> On Mon, Oct 17, 2016 at 8:43 AM, Ajay Garg <ajaygargn...@gmail.com> wrote:
>
>> Thanks Aleksander for your continuous help.
>>
>> We finally received the antenna, but the modem still shows the same
>> behaviour as before ("operation not supported" behaviours).
>>
>>
>> So, I proceeded to gather the debug-logs.
>>
>>
>> a)
>> I followed the following steps for each of libmbim, libqmi and
>> ModemManager sources that you provided ::
>>
>> *./configure --prefix=/usr*
>> *make*
>> *sudo make install*
>>
>>
>> After this, *dpkg -l *show the same versions as before, but *ModemManager
>> --version* at least shows 1.6.2
>> So, I guess the installations went fine functionally.
>>
>>
>> b)
>> I enabled the debug-logs for ModemManager, but somehow the NetworkManager
>> could not be started properly as per the link
>> https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
>>
>> Please find the debug-logs-file for ModemManager attached, plus the
>> attempt-logs for starting NetworkManager as per the link.
>>
>>
>> Kindly let know what is the issue, and what steps I need to follow next
>> to nail the issue.
>>
>>
>> Once again, many thanks for your prompt responses.
>>
>>
>> Thanks and Regards,
>> Ajay
>>
>>
>> On Thu, Oct 13, 2016 at 4:13 PM, Aleksander Morgado <
>> aleksan...@aleksander.es> wrote:
>>
>>> On Thu, Oct 13, 2016 at 12:24 PM, Ajay Garg <ajaygargn...@gmail.com>
>>> wrote:
>>> > Where can I get the latest "official" versions of modem-manager,
>>> libqmi etc.
>>> > for Ubuntu-14.04.3?
>>>
>>> There isn't any official binary build of the latest stable versions
>>> for Ubuntu 14.04; you should get the source tarballs and build them
>>> yourself:
>>> https://www.freedesktop.org/software/libmbim/libmbim-1.14.0.tar.xz
>>> https://www.freedesktop.org/software/libqmi/libqmi-1.16.0.tar.xz
>>> https://www.freedesktop.org/software/ModemManager/ModemManag
>>> er-1.6.2.tar.xz
>>>
>>> Cheers!
>>>
>>> --
>>> Aleksander
>>> https://aleksander.es
>>>
>>
>>
>>
>> --
>> Regards,
>> Ajay
>>
>
>
>
> --
> Regards,
> Ajay
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: [URGENT] Regressions in latest QMI-related packages

[Ajay Garg]

Thanks Jens for the help.

Jens, if I may request, could you instead let me know how to generate
proper rpms from the sources in this case?
That will be a cleaner way, and might help others too who might need these
updated packages as rpms.

Just a pointer to the link explaining how to generate the deb files from
modmemanager/libqmi/libmbim source-files will help :)

On Mon, Oct 17, 2016 at 11:47 AM, Schroer, Jens Peter <
jens.schr...@scypho.com> wrote:

> Ajay,
>
> Judging by your comments you are running a Debian based Linux distro using
> apt to install packages?
> If so, make install will not replace the installed package or update the
> package database.
> It will only copy the binaries to the different locations, and you might
> get version mismatches in worst case.
>
> Try the following:
>
> a) You need to remove the original packages first.
> sudo apt-get remove --purge packagename
>
> So on my ubuntu it would be (the packages names might be different for you
> depending on your distro):
> sudo apt-get remove --purge libqmi-glib1
> sudo apt-get remove --purge libqmi-glib-dev
> sudo apt-get remove --purge libmbim-glib4
> sudo apt-get remove --purge libmbim-glib-dev
> sudo apt-get remove --purge libmm-glib0
> sudo apt-get remove --purge libmm-glib-dev
> sudo apt-get remove --purge modemmanager-dev
>
> Note: as you overwrote some files, above operations might give you errors,
> as the checksums do not match anymore.
> If so, look here if any of this works:
> http://askubuntu.com/questions/438345/how-to-remove-install-
> a-package-that-is-not-fully-installed
>
> b) After all packages are removed, install everything clean from the
> sources again.
> As you might have had installed the old dev packages, I would suggest, do
> a make clean in each of the source
> directories followed by the make install.
> I do not know if there are build time dependencies between the libraries.
> If so, you will have to rebuild in a certain order
> to match those dependencies.
>
> After that, you might need to rebuild the library cache
> sudo ldconfig
>
> c) Try again :)
>
> Hope it helps
> Jens
>
>
> On 2016-10-17 05:13, Ajay Garg wrote:
>
>> Thanks Aleksander for your continuous help.
>>
>> We finally received the antenna, but the modem still shows the same
>> behaviour as before ("operation not supported" behaviours).
>>
>> So, I proceeded to gather the debug-logs.
>>
>> a)
>> I followed the following steps for each of libmbim, libqmi and
>> ModemManager sources that you provided ::
>>
>> ./CONFIGURE --PREFIX=/USR
>> MAKE
>> SUDO MAKE INSTALL
>>
>> After this, DPKG -L show the same versions as before, but MODEMMANAGER
>> --VERSION at least shows 1.6.2
>> So, I guess the installations went fine functionally.
>>
>> b)
>>
>> I enabled the debug-logs for ModemManager, but somehow the
>> NetworkManager could not be started properly as per the link
>> https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
>>
>> Please find the debug-logs-file for ModemManager attached, plus the
>> attempt-logs for starting NetworkManager as per the link.
>>
>> Kindly let know what is the issue, and what steps I need to follow
>> next to nail the issue.
>>
>> Once again, many thanks for your prompt responses.
>>
>> Thanks and Regards,
>> Ajay
>>
>> On Thu, Oct 13, 2016 at 4:13 PM, Aleksander Morgado
>> <aleksan...@aleksander.es> wrote:
>>
>> On Thu, Oct 13, 2016 at 12:24 PM, Ajay Garg <ajaygargn...@gmail.com>
>>> wrote:
>>>
>>>> Where can I get the latest "official" versions of modem-manager,
>>>>
>>> libqmi etc.
>>>
>>>> for Ubuntu-14.04.3?
>>>>
>>>
>>> There isn't any official binary build of the latest stable versions
>>> for Ubuntu 14.04; you should get the source tarballs and build them
>>> yourself:
>>> https://www.freedesktop.org/software/libmbim/libmbim-1.14.0.tar.xz
>>> [1]
>>> https://www.freedesktop.org/software/libqmi/libqmi-1.16.0.tar.xz [2]
>>>
>>> https://www.freedesktop.org/software/ModemManager/ModemManag
>> er-1.6.2.tar.xz
>>
>>> [3]
>>>
>>> Cheers!
>>>
>>> --
>>> Aleksander
>>> https://aleksander.es
>>>
>>
>> --
>> Regards,
>> Ajay
>>
>>
>> Links:
>> --
>> [1] https://www.freedesktop.org/software/libmbim/libmbim-1.14.0.tar.xz
>> [2] https://www.freedesktop.org/software/libqmi/libqmi-1.16.0.tar.xz
>> [3] https://www.freedesktop.org/software/ModemManager/ModemManag
>> er-1.6.2.tar.xz
>>
>> ___
>> ModemManager-devel mailing list
>> ModemManager-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
>>
>
> ___
> ModemManager-devel mailing list
> ModemManager-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: [URGENT] Regressions in latest QMI-related packages

[Ajay Garg]

Looking at
https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-trusty, it
seems that the packages were uploaded in June/July, well before my testing
in August.

The only difference in my testing as of now from previous time, is the
absence of modem-antenna (we are still awaiting its delivery). In that
case, are the previous symptoms possible (killing of qmi-proxy after some
time, and some operations not supported for mmcli)?

I am sorry for sounding such an ass, but I am really tense. Sorry again for
that.




On Thu, Oct 13, 2016 at 11:10 AM, Ajay Garg <ajaygargn...@gmail.com> wrote:

> Hi Aleksander.
>
> We have a Sierra-MC8080, and about a month and half-back, everything was
> working perfectly, when I followed the steps ::
>
>
>
>
> *#sudo
> add-apt-repository -y ppa:aleksander-m/modemmanager-trustysudo apt-get
> updatesudo apt-get install -y modemmanager*
>
>
>
> *#*Now,
>
> a)
> qmi-proxy gets killed after some time (after reboot, and if started
> manually).
>
> b)
> Some operations work, while some don't.
>
> *#*
> *mmcli -L*
>
> Found 1 modems:
> /org/freedesktop/ModemManager1/Modem/0 [Sierra Wireless,
> Incorporated] MC8090
>
> *mmcli -m 0 -e*
> successfully enabled the modem
>
> *mmcli -m 0 --set-allowed-modes='2G'*
> error: couldn't set current modes: 'GDBus.Error:org.freedesktop.
> ModemManager1.Error.Core.Unsupported: Setting allowed modes not supported'
>
> *mmcli -m 0 -r*
> error: couldn't reset the modem: 'GDBus.Error:org.freedesktop.
> ModemManager1.Error.Core.Unsupported: Cannot reset the modem: operation
> not supported'
> *#*
>
>
>
> Following are the package-versions :
>
> *#*
> *dpkg -l | grep -i Modem*
> ii  libmm-glib0:i386
> 1.5.992-3+trustyi386 D-Bus
> service for managing modems - shared libraries
>
> ii  modemmanager
> 1.5.992-3+trustyi386 D-Bus
> service for managing modems
>
> *dpkg -l | grep -i qmi*
> libqmi-glib0:i386
> 1.4.0-1 i386 Support
> library to use the Qualcomm MSM Interface (QMI) protocol
>
> libqmi-glib5:i386
> 1.14.2-2+trusty i386 Support
> library to use the Qualcomm MSM Interface (QMI) protocol
>
> libqmi-proxy
> 1.14.2-2+trusty i386 Proxy to
> communicate with QMI port
>
>
>
>
> *#*
> Please let me know in case anything else is required.
>
> I will be grateful if some pointers are given on an urgent basis.
> Based on our previous testing, we have committed the dates to the customer
> for bulk-delivery, and now we are in a big fix :(
>
>
> Thanks and Regards,
> Ajay
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Latest ModemManagaer and libqmi packages for raspberry-pi?

[Ajay Garg]

Hi Aleksander.

Are there PPAs for Raspberry-Pi. on similar lines as

https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-trusty
https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-xenial


If not, is there a way to get the latest modemmanager and qmi libraries for
raspberry-pi?
I will be happy to help with the mundanes :)


Thanks and Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Modem not connecting on Ubuntu 16.04 (whereas it did on Ubuntu 14.04)

[Ajay Garg]

Thanks Aleksander, for your (as always) detailed and crisp analysis.


On Tue, Aug 30, 2016 at 8:09 PM, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
> On Tue, Aug 30, 2016 at 8:56 AM, Ajay Garg <ajaygargn...@gmail.com> wrote:
>> The reason turned out that I had disable USB-3.0 support in BIOS.
>> When I turned it on, the modem started connecting in both 14.04 and 16.04.
>>
>> However, in 14.04 the "wwan" interface appears fine (and after running
>> "dhclient" on it, the internet works fine).
>> However on 16.04, no "wwan" interface appears, even after mmcli -m 11
>> --simple-connect="apn=airtelgprs.com" has resulted in successful-connection.
>>
>>
>> A maybe related symptom is that ethernet-interfaces appear as "eth0" and
>> "eth1" in 14.04, but as "enp1s0" and "enp2s0" in 16.04. But even then, NO
>> ADDITIONAL INTERFACE appears when mmcli -m 11
>> --simple-connect="apn=airtelgprs.com" has resulted in successful-connection
>> on 16.04.
>>
>> Looks very weird; I will be thankful for any help.
>
> --simple-connect doesn't make interfaces appear/disappear :) The WWAN
> interface should be detected and available before you even attempt to
> run --simple-connect.


:O :O :O

Hasn't happened for me on Ubuntu 14.04.2 / 14.04.3 so far, not even
once in the last 1 month or so I have been working on this. However,
things have been working fine via the commands I shared in my
originating email.

The interface occurs if and only if the --simple-connect runs to
completion, successfully.

Should I be worried?

>
> Looks like you have now the "predictable network interface names"
> support in Ubuntu 16.04, coming from systemd:
> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
>
> This means that you won't have a "wwan0" interface any more; look for
> something like "ww"
>
> Anyway, the correct flow is to avoid manually looking for the network
> interface name. Once you have run "--simple-connect", you'll have a
> connected "bearer" object reported in ModemManager. The bearer object
> will tell you, in its details, what interface name you should use and
> also the specific connection method you're supposed to use (dhcp,
> static, ppp).

Thanks for this info Aleksander, I will keep this in mind if I do have
to take the trouble of evaluating a new version :)


>
> --
> Aleksander
> https://aleksander.es


Thanks and Regards,
Ajay



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Modem not connecting on Ubuntu 16.04 (whereas it did on Ubuntu 14.04)

[Ajay Garg]

Hi All.

I followed the following steps ::

a)
Installed Ubuntu 16.04.

b)
sudo add-apt-repository -y ppa:aleksander-m/modemmanager-xenial
sudo apt-get update
sudo apt-get install -y modemmanager
sudo reboot


c)
I am using a Sierra modem in QMI-mode.

*lsusb*
*Bus 001 Device 017: ID 1199:68a2 Sierra Wireless, Inc. *
Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 003: ID 413c:2107 Dell Computer Corp.
Bus 001 Device 002: ID 8087:07e6 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


d)
*mmcli -L*

Found 1 modems:
/org/freedesktop/ModemManager1/Modem/11 [QUALCOMM INCORPORATED] 0

*mmcli -m 11 -e*
successfully enabled the modem

*mmcli -m 11 --set-allowed-modes='2G'*
successfully set current modes in the modem


*mmcli -m 11 --create-bearer="apn=airtelgprs.com
"*Successfully
created new bearer in modem:
/org/freedesktop/ModemManager1/Bearer/7

*mmcli -m 11 --simple-connect="apn=airtelgprs.com "*
error: couldn't connect the modem: 'Timeout was reached'


I keep getting the timeout-error, irrespecitive of multiple machine-reboots
and modem-resets.

The strangest part is that the same process used to work on Ubuntu-14.04,
so I guess something is screwing up on Ubuntu-16.
I will be grateful to receive any help, kindly let know any
diagnostic-information that would help in catching the root-cause.


Thanks and Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Is Sierra's MC8305 supported by qmi_wwan (WITHOUT USING Gobi driver) in QMI-mode?

[Ajay Garg]

Ahhh... I get it.
Sorry for my stupidity :P

I will ask my hardware-team to order a test-unit, hopefully all goes fine !!

Sorry again, and Thanks again.


Thanks and Regards,
Ajay

On Tue, Aug 16, 2016 at 1:41 PM, Bjørn Mork <bj...@mork.no> wrote:

> Ajay Garg <ajaygargn...@gmail.com> writes:
>
> > Hi All.
> >
> > Just wish to confirm, because
> > http://www.spinics.net/lists/linux-usb/msg88529.html has too many
> > references to Gobi (which I DO NOT INTEND to use).
>
> No need to worry about that. "Gobi" is an out-dated Qualcomm marketing
> thingy (aka "brand name") which described a specific device
> configuration and set of features.  It became less and less specific
> with new generations, until they dropped it for the even more generix
> "Snapdragon" marketing thingy.  The important part for us is that all
> these have QMI.
>
> The term is used in qcserial and qmi_wwan because Gobi 1k and 2k had
> specific USB interface layouts, which allowed us to generalize the probe
> code for those devices.  It doesn't mean that you need any other driver.
> qmi_wwan supports both Gobi and non-Gobi devices. The only difference
> is the USB interface matching macro.
>
>
> Bjørn
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Is Sierra's MC8305 supported by qmi_wwan (WITHOUT USING Gobi driver) in QMI-mode?

[Ajay Garg]

Hi All.

Just wish to confirm, because
http://www.spinics.net/lists/linux-usb/msg88529.html has too many
references to Gobi (which I DO NOT INTEND to use).

So, a confirmation/rejection regarding the modem's support via pure
qcserial/qmi_wwan will make me select my next path.


Thanks and Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sufficient tests to determine that the WWAN0 interface is up and running?

[Ajay Garg]

Thanks Aleksander.

I will keep my system running, and will let know if anything fishy is
observed despite the 3 watcher-tests.
Thanks again !!


Thanks and Regards,
Ajay

On Mon, Aug 15, 2016 at 7:31 PM, Aleksander Morgado <
aleksan...@aleksander.es> wrote:

> On Mon, Aug 15, 2016 at 3:52 PM, Ajay Garg <ajaygargn...@gmail.com> wrote:
> > I have a modem in QMI-mode, and through your help, I have been able to
> get
> > it up and running.
> >
> >
> > Now, my architecture is such ::
> >
> > *
> > There is a python-script, which monitors the health of "wwan0" interface.
> >
> > *
> > There is an application-binary in C, which uses POSIX-socket APIs to
> create
> > a socket (and the socket is created from wwan0, as that is the only
> active
> > interface).
> >
> >
> >
> > Now, things are working fine so far.
> > I have put in the following tests in the python-script ::
> >
> > 1)
> > Ensure power state: 'on' in output of "mmcli -m modem-id".
> >
> > 2)
> > Ensure state: 'connected' in output of "mmcli -m modem-id".
> >
> > 3)
> > Ensure there is a ipv4 address assigned to wwan0-interface.
> >
> >
> > I run the above 3 tests every 30 seconds, and assume that if all 3 match
> as
> > expected, then the wwan0-interface is fine (and any user-applications
> using
> > POSIX-Socket APIs would continue to achieve new socket-instantiations
> fine).
> >
> >
> >
> > Are the 3 tests sufficient?
> > Or any other tests should/must be put?
> >
> >
> > Will be grateful for pointers, that could help make the wwan-interface-up
> > testing bullet-proof.
>
> Those should be enough; unless you also want to test real Internet
> connectivity as well, e.g. doing a periodic ping -I wwan0 x.x.x.x.
>
> --
> Aleksander
> https://aleksander.es
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Meaning of "signal quality" in output of "mmcli -m modem-id"

[Ajay Garg]

On Mon, Aug 15, 2016 at 7:29 PM, Aleksander Morgado <
aleksan...@aleksander.es> wrote:

> On Mon, Aug 15, 2016 at 3:43 PM, Ajay Garg <ajaygargn...@gmail.com> wrote:
> > Let's say modem-id is 0.
> > So, in the output of "mmcli -m 0", we get an output for signal quality in
> > the form ::
> >
> > signal quality: '71' (recent)
> >
> >
> > What is this value?
> > Is this related to the value returned by "AT+CSQ" in any manner?
> >
> >
> > In particular, if the value returned by "AT+CSQ" is x, then the
> > signal-strength in dbm is given by ::
> >
> > -113 + (2 * x)
> >
> > Is there a correlation for the signal-quality returned by "mmcli -m
> > modem-id" (71 in this case)?
>
> That would be 71%.
>
> For +CSQ, we do this:
>   quality = CLAMP (quality, 0, 31) * 100 / 31;
>
> See https://cgit.freedesktop.org/ModemManager/ModemManager/
> tree/src/mm-broadband-modem.c#n1837
>
>
Thanks Aleksander.

So, that would make the AT+CSQ equivalent strength equal to
   int(71 * 31 / 100)


Thanks a ton !!


Thanks and Regards,
Ajay

> --
> Aleksander
> https://aleksander.es
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Crash in Modem-Manager on Ubuntu

[Ajay Garg]

Thanks Aleksander for the reply.

A small query, if a modem supports both DirectIP and QMI, which is the
recommended mode?

AT-command-set is highly modem-specific, while QMI is a standard-protocol.
So, if there are "n"  modems supporting both DirectIP and QMI, they are
guaranteed to expose identical QMI "APIs", while their AT "APIs" could
potentially be different.

Are my thoughts in line?

On Mon, Aug 15, 2016 at 1:28 PM, Aleksander Morgado <
aleksan...@aleksander.es> wrote:

> On 13/08/16 03:24, Ajay Garg wrote:
> > First of all, my requirement is to have network-connectivity via the
> > modem; and have the ability to read SMSes and run AT-commands WITHOUT
> > losing the network-connectivity.
> >
> > I guess mmcli would do the trick, as modem-manager now comes plugged
> > in with qmi-daemon, while serializes all requests being sent to the
> > modem-serial-port (thereby having just one process have access to the
> > serial-port).
> >
> > So, assuming (please correct me if I am wrong) that I am correct with
> > my above hypotheses, will the above architecture work for a modem in
> > DirectIP-mode (I guess not, but please confirm/reject).
>
> If you're running in Direct IP mode, ModemManager will use AT commands
> over a serial port AND a WWAN network interface for data. You will be
> able to do SMS messaging and network connectivity at the same time, as
> the serial port isn't used for connection.
>
> If you're running in QMI mode, you will also be able to do SMS messaging
> and connectivity at the same time. Connection will go through the WWAN
> network interface, and the SMS messaging commands via QMI and the
> /dev/cdc-wdm port (not a TTY).
>
> --
> Aleksander
> https://aleksander.es
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Basic (Idiotic) questions about ModemManager / mmcli / libqmi / modems / life

[Ajay Garg]

Thanks a ton Aleksander for your confirmations .. it makes me feel really
good !!

On Mon, Aug 15, 2016 at 1:42 PM, Aleksander Morgado <
aleksan...@aleksander.es> wrote:

>
> > So, the story so far ::
> >
> >
> > a)
> > As soon as a QMI-modem is plugged in, the kernel presents the
> > following two interfaces AUTOMATICALLY ::
> >
> >  * /dev/cdc-... QMI-port interface
> >  * a wwan-interface
> >
> > Kernel takes the help of udev/qcserial/qmi_wwan for the above, and
> > each of these three modules/drivers are required  for proper
> > functioning of QMI-modem.
> >
> > This will happen even if none of user-apps like
> > NetworkManager/ModemManager/mmcli/qmicli are even installed. This is
> > all the kernel's playground till now.
> >
>
> Yes; except for the qcserial bit; qcserial is only a TTY thing. For a
> /dev/cdc-wdm port and a wwan interface, you need qmi_wwan and cdc-wdm.
>
> >
> > b)
> > Now, on systems like Ubuntu, NetworkManager and ModemManager start by
> default.
> >
> > If version of libqmi on the system is greater than 1.7, then a
> > daemon-process "qmi-proxy" will be spawned by ModemManager (since
> > ModemManager starts automatically on system-boot), and all
> > QMI-requests/responses will be routed via "qmi-proxy".
> >
> >
>
> Yes.
>
> > c)
> > In user-space, the user may play with the modem via following tools ::
> >
> >  * mmcli (via mmcli <-> ModemManager <-> qmi-proxy <->
> > /dev/cdc-.. <-> modem)
> >
> >  * qmicli (via qmicli <-> qmi-proxy <-> /dev/cdc-.. <-> modem)
> >
> >  * any custom user-qmi-app (via user-qmi-app <-> qmi-proxy <->
> > /dev/cdc-.. <-> modem)
> >
> >
> > Important thing to note in this step is that from mmcli / qmcli /
> > user-qmi-app perspective, each app thinks that the app has exclusive
> > control of /dev/cdc-.. <-> modem. Obviously, this is being made
> > possible via concurrent/serialized handing of requests by qmi-proxy.
> >
> > Kindly correct me if any of my cumulative understanding is wrong till
> > this point.
> >
> >
>
> Yes.
>
> >
> > Question 4 :
> > =
> >
> > Is it 100% safe to mix the usage of qmicli / mmcli (or any any other
> > custom-user-app for that matter)? This is assuming that none of the
> > apps will shutdown/reinstantiate /dev/cdc-.. QMI-port.
> >
> > For example, can we instantiate a connection via qmicli, and then read
> > the stored SMSes via mmcli, and then may be run some other command via
> > qmicli again on the same modem?
> >
> > I am assuming that qmicli and mmcli are stateless applications (i.e.
> > they do not maintain any INTERNAL states for any modem).
> >
> > Will be grateful to have a confirmation / rejection on my hypothesis
> > of question 4.
> >
>
> qmicli is stateless; unless explicitly requested to keep state (i.e.
> --client-cid=[CID] and --client-no-release-cid). Most of the operations
> can be run in a stateless mode, where each operation just creates a new
> client and performs one single operation. If you want to integrate this
> in a script that periodically runs the same operation over and over,
> though, you may want to create one single client and re-use the same CID
> over multiple operations.
>
> mmcli is stateless, but ModemManager, the one doing the work, isn't.
>
> You're free to mix both, but taking into account that if you modify the
> state with e.g. qmicli, ModemManager may not be aware of it. e.g. if you
> set the device in low power with qmicli, ModemManager may still think
> that it is in full-power mode.
>
> If you want to mix both, I'd suggest to keep ModemManager/mmcli for the
> operations that may modify any kind of state, and qmicli (or some other
> qmi-proxy based application) for any other read-only operation. E.g. you
> could run ModemManager to control the modem and the Mobile Radio Monitor
> (https://sigquit.wordpress.com/2013/09/17/mobile-radio-monitor) to check
> the detailed signal/power statistics of the module at the same time.
>
>
Fortunately, all my requirements could be met by "mmcli" ::

 * Setting/Instantiating Connection (-m id --create-bearer, -m id
--simple-connect)
 * Reading SMSes (-m id --messaging-list-sms, -s)
 * Getting signal-strength (-m id)


As soon as I upgraded the ModemManager (as suggested by you in another
thread), qmi-proxy came into picture, and all my earlier concerns of
concurrency were solved immediately (because of qmi-proxy being the sole
door through which ALL qmi-requests are routed to the modem).


I do have some minor queries, but they have a highly-local scope.
As far as the bigger picture is concerned, things have fitted in perfectly
:)


Once again, thanks a ton to everyone for the help !!


Thanks and Regards,
Ajay


> --
> Aleksander
> https://aleksander.es
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: [SOLVED} Re: qmi-proxy not being listed

[Ajay Garg]

On Mon, Aug 15, 2016 at 1:23 PM, Aleksander Morgado <
aleksan...@aleksander.es> wrote:

> On 14/08/16 14:25, Ajay Garg wrote:
> > qmi-proxy started automatically now on reboot, seems
> > the process is initiated if there is at least one /dev/cdc-wdm..
> > interface.
>
> No. qmi-proxy is never anywhere configured to start on boot; it's not a
> "system daemon".
>
> qmi-proxy is started by libqmi if there is any program using libqmi that
> requests to use the proxy and the proxy isn't running already.
>
> E.g. if you configure to start ModemManager on boot, ModemManager will
> launch the qmi-proxy automatically when it tries to open a /dev/cdc-wdm
> QMI port.
>
>
Perfect !!
I checked, and this is precisely what is happening (qmi-proxy being started
by ModemManager).

Thanks a ton !!


Thanks and Regards,
Ajay



> --
> Aleksander
> https://aleksander.es
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Can neither see "wwan" interface, nor does network work in Sierra-modem-in-QMI-mode

[Ajay Garg]

Hi Thomas.

On Sun, Aug 14, 2016 at 11:59 PM, Thomas Schäfer <tschae...@t-online.de>
wrote:

> I am a little bit confused.
>
> I started everytime with step "c)" (mmcli -L to get the right number)
>
> Step "b)"(setting the bearer manually)  was never necessary.
>
> Because of the enumeration I also rarely used step  "a)".
>
> By the way: Does your ISP provide IPv6 too?
>

I doubt, but I guess that is independent of the spurious issue I am facing.
And I am sorry, I meant "dhclient wwan0" hangs 2/10 times (and works fine
8/10 times).



>
> Regards
>
> Thomas Schäfer
>
>
>
> Am Sonntag, 14. August 2016, 23:29:19 schrieb Ajay Garg:
> > Thanks Thomas !!!
> >
> > Following algorithm "mostly"  works ::
> >
> >
> > ##
> > a)
> > Check whether the required bearer already exists, via ::
> >
> >mmcli -m 0 --list-bearers
> >mmcli -b /path/of/bearer/as/returned/by/above/command
> >
> > If yes, then go to step c).
> >
> > b)
> >mmcli -m 0 --create-bearer="apn=airtelgprs.com"
> >
> > c)
> >mmcli -m 0 --simple-connect="apn=airtelgprs.com"
> >
> > d)
> >dhclient -r wwan0
> >dhclient wwan0
> > ##
> >
> > In everything goes right, then telnet/ping work fine.
> >
> > In the beginning, I said "mostly", because the last step (dhclient wwan0)
> > hangs 8/10 times. Whenever this happens, the only remedy that I have
> found
> > so far is rebooting the machine.
> >
> >
> > Is there a saner way to have the "dhclient wwan0" work fine every time?
> >
> >
> > Thanks and Regards,
> > Ajay
> >
> > On Sun, Aug 14, 2016 at 7:52 PM, <tschae...@t-online.de> wrote:
> > > Modemmanager doesn't make the ip-settings.
> > > This is normally done by networkmanager or by yourself.
> > >
> > > See mmcli -b 0
> > >
> > > The hint using ip instead of ifconfig was no joke!
> > >
> > > Ifconfig doesn't list down interfaces.
> > >
> > > Ip l does.
> > >
> > > The simplest thing in  your case seems to me, is to starting
> > > dhclient/dhcpcd or something similar on your wwan-device.
> > > Alternatively try to do the settings according to mmcli -b 0 via ip
> > > manually.
> > >
> > > Thomas
> > >
> > >
> > >
> > >
> > > Am 14.08.2016 15:52 schrieb Ajay Garg <ajaygargn...@gmail.com>:
> > >
> > > Hi All.
> > >
> > > This post is mostly similar to https://lists.freedesktop.org/
> > > archives/libqmi-devel/2016-August/001647.html, except there I am
> trying
> > > with "qmicli" throughout, and here I try with "mmcli" throughout.
> > >
> > > Anyways, for brevity, I will put in the complete relevant-content here
> > > too.
> > >
> > > I switched my modem into QMI-mode, and rebooted the SOC
> > > (Ubuntu-on-SSD-interfaced-with-modem). After reboot, following is the
> > > information ::
> > >
> > >
> > > == Pre-Requisites are in place ==
> > >
> > > 
> > > root@logic-desktop:~# *lsusb*
> > > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > > Bus 001 Device 005: ID 1199:68a2 Sierra Wireless, Inc.
> > > Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
> > > Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
> > > Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
> > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > >
> > >
> > > root@logic-desktop:~# *ps -aux | grep qmi-proxy*
> > > root   865  0.0  0.1  28032  5732 ?Sl   18:58   0:00
> > > /usr/lib/libqmi/qmi-proxy root  2563  0.0  0.0   4692  2072 pts/2
> > > S+   19:05   0:00 grep --color=auto qmi-proxy
> > >
> > > root@logic-desktop:~# *lsmod | grep sierra*
> > >
> > > root@logic-desktop:~# *lsmod | grep qcserial*
> > > qcserial   13006  0
> > > usb_wwan   19306  1 qcserial
> > > usbserial  38972  2 qcserial,usb_wwan
> > >
>

Re: Can neither see "wwan" interface, nor does network work in Sierra-modem-in-QMI-mode

[Ajay Garg]

Thanks Thomas !!!

Following algorithm "mostly"  works ::


##
a)
Check whether the required bearer already exists, via ::

   mmcli -m 0 --list-bearers
   mmcli -b /path/of/bearer/as/returned/by/above/command

If yes, then go to step c).

b)
   mmcli -m 0 --create-bearer="apn=airtelgprs.com"

c)
   mmcli -m 0 --simple-connect="apn=airtelgprs.com"

d)
   dhclient -r wwan0
   dhclient wwan0
##

In everything goes right, then telnet/ping work fine.

In the beginning, I said "mostly", because the last step (dhclient wwan0)
hangs 8/10 times. Whenever this happens, the only remedy that I have found
so far is rebooting the machine.


Is there a saner way to have the "dhclient wwan0" work fine every time?


Thanks and Regards,
Ajay

On Sun, Aug 14, 2016 at 7:52 PM, <tschae...@t-online.de> wrote:

> Modemmanager doesn't make the ip-settings.
> This is normally done by networkmanager or by yourself.
>
> See mmcli -b 0
>
> The hint using ip instead of ifconfig was no joke!
>
> Ifconfig doesn't list down interfaces.
>
> Ip l does.
>
> The simplest thing in  your case seems to me, is to starting
> dhclient/dhcpcd or something similar on your wwan-device.
> Alternatively try to do the settings according to mmcli -b 0 via ip
> manually.
>
> Thomas
>
>
>
>
> Am 14.08.2016 15:52 schrieb Ajay Garg <ajaygargn...@gmail.com>:
>
> Hi All.
>
> This post is mostly similar to https://lists.freedesktop.org/
> archives/libqmi-devel/2016-August/001647.html, except there I am trying
> with "qmicli" throughout, and here I try with "mmcli" throughout.
>
> Anyways, for brevity, I will put in the complete relevant-content here too.
>
> I switched my modem into QMI-mode, and rebooted the SOC 
> (Ubuntu-on-SSD-interfaced-with-modem).
> After reboot, following is the information ::
>
>
> == Pre-Requisites are in place ==
>
> 
> root@logic-desktop:~# *lsusb*
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 005: ID 1199:68a2 Sierra Wireless, Inc.
> Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
> Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
> Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
>
> root@logic-desktop:~# *ps -aux | grep qmi-proxy*
> root   865  0.0  0.1  28032  5732 ?Sl   18:58   0:00 
> /usr/lib/libqmi/qmi-proxy
> root  2563  0.0  0.0   4692  2072 pts/2S+   19:05   0:00 grep 
> --color=auto qmi-proxy
>
> root@logic-desktop:~# *lsmod | grep sierra*
>
> root@logic-desktop:~# *lsmod | grep qcserial*
> qcserial   13006  0
> usb_wwan   19306  1 qcserial
> usbserial  38972  2 qcserial,usb_wwan
>
> root@logic-desktop:~# *lsmod | grep qmi_wwan*
> qmi_wwan   21469  0
> cdc_wdm18518  2 qmi_wwan
> usbnet 37829  1 qmi_wwan
> 
>
>
>
>
>
> == Initial-Interface Listing ==
>
> 
> root@logic-desktop:~# *ifconfig*
> eth1  Link encap:Ethernet  HWaddr 00:90:0b:4c:65:fa
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>   Memory:d070-d071
>
> eth2  Link encap:Ethernet  HWaddr 00:90:0b:4c:65:fb
>   inet6 addr: fe80::290:bff:fe4c:65fb/64 Scope:Link
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:3910 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:3448 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:3143983 (3.1 MB)  TX bytes:540896 (540.8 KB)
>   Memory:d060-d061
>
> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:2398 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:2398 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:188946 (188.9 KB)  TX bytes:188946 (188.9 KB)

Can neither see "wwan" interface, nor does network work in Sierra-modem-in-QMI-mode

[Ajay Garg]

Hi All.

This post is mostly similar to https://lists.freedesktop.org/
archives/libqmi-devel/2016-August/001647.html, except there I am trying
with "qmicli" throughout, and here I try with "mmcli" throughout.

Anyways, for brevity, I will put in the complete relevant-content here too.

I switched my modem into QMI-mode, and rebooted the SOC
(Ubuntu-on-SSD-interfaced-with-modem).
After reboot, following is the information ::


== Pre-Requisites are in place ==


root@logic-desktop:~# *lsusb*
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 1199:68a2 Sierra Wireless, Inc.
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


root@logic-desktop:~# *ps -aux | grep qmi-proxy*
root   865  0.0  0.1  28032  5732 ?Sl   18:58   0:00
/usr/lib/libqmi/qmi-proxy
root  2563  0.0  0.0   4692  2072 pts/2S+   19:05   0:00 grep
--color=auto qmi-proxy

root@logic-desktop:~# *lsmod | grep sierra*

root@logic-desktop:~# *lsmod | grep qcserial*
qcserial   13006  0
usb_wwan   19306  1 qcserial
usbserial  38972  2 qcserial,usb_wwan

root@logic-desktop:~# *lsmod | grep qmi_wwan*
qmi_wwan   21469  0
cdc_wdm18518  2 qmi_wwan
usbnet 37829  1 qmi_wwan






== Initial-Interface Listing ==


root@logic-desktop:~# *ifconfig*
eth1  Link encap:Ethernet  HWaddr 00:90:0b:4c:65:fa
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Memory:d070-d071

eth2  Link encap:Ethernet  HWaddr 00:90:0b:4c:65:fb
  inet6 addr: fe80::290:bff:fe4c:65fb/64 Scope:Link
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:3910 errors:0 dropped:0 overruns:0 frame:0
  TX packets:3448 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:3143983 (3.1 MB)  TX bytes:540896 (540.8 KB)
  Memory:d060-d061

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:2398 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2398 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:188946 (188.9 KB)  TX bytes:188946 (188.9 KB)






== Connection-Establishment ==


root@logic-desktop:~# *mmcli -m 0 -e*
successfully enabled the modem

root@logic-desktop:~# *mmcli -m 0 --simple-connect="apn=airtelgprs.com
"*
successfully connected the modem

root@logic-desktop:~# *mmcli -m 0*

/org/freedesktop/ModemManager1/Modem/0 (device id
'6eef1b98754cbd133c7a802b89bfcccb55c2f464')
  -
  Hardware |   manufacturer: 'QUALCOMM INCORPORATED'
   |  model: '0'
   |   revision: 'SCAUTNZ  1  [Oct 21 2011 09:30:38]'
   |  supported: 'gsm-umts'
   |current: 'gsm-umts'
   |   equipment id: '013087000947186'
  -
  System   | device:
'/sys/devices/pci:00/:00:14.0/usb1/1-4/1-4.1'
   |drivers: 'qmi_wwan, qcserial'
   | plugin: 'Sierra'
   |   primary port: 'cdc-wdm0'
   |  ports: 'ttyUSB1 (at), cdc-wdm0 (qmi), wwan0 (net)'
  -
  Numbers  |   own : 'unknown'
  -
  Status   |   lock: 'sim-pin2'
   | unlock retries: 'sim-pin (10), sim-pin2 (3), sim-puk
(10), sim-puk2 (10)'
   |  state: 'connected'
   |power state: 'on'
   |access tech: 'gsm'
   | signal quality: '71' (recent)
  -
  Modes|  supported: 'allowed: 2g; preferred: none
   |  allowed: 3g; preferred: none
   |  allowed: 2g, 3g; preferred: none
   |  allowed: 2g, 3g; preferred: 2g
   |  allowed: 2g, 3g; preferred: 3g'
   |current: 'allowed: 2g, 3g; preferred: none'
  -
  Bands|  supported: 'dcs, egsm, pcs, g850, u2100, u1900, u800, u850'
   |current: 'dcs, egsm, pcs, g850, u2100, 

[SOLVED] Re: Simplest way to read SMSes-content from a QMI-modem

[Ajay Garg]

Sorry, my bad.

Following works seamlessly ::

##
root@logic-desktop:~# *mmcli -s  /org/freedesktop/ModemManager1/SMS/22*
SMS '/org/freedesktop/ModemManager1/SMS/22'
  ---
  Content|  number: '+919818782593'
 |text: 'Trying again'
  ---
  Properties |PDU type: 'deliver'
 |   state: 'received'
 | storage: 'me'
 |smsc: '+919810051829'
 |   timestamp: '160808142935+05'
##

Sorry for the noise.

Thanks and Regards,
Ajay



On Sun, Aug 14, 2016 at 6:38 PM, Ajay Garg <ajaygargn...@gmail.com> wrote:

> Hi All.
>
> I can tetrieve the metadata of the SMSes, via
>
>
> #
> logic@logic-desktop:~$ *mmcli -m 0 --messaging-list-sms*
>
> Found 14 SMS messages:
> /org/freedesktop/ModemManager1/SMS/34 (received)
> /org/freedesktop/ModemManager1/SMS/35 (received)
> /org/freedesktop/ModemManager1/SMS/36 (received)
> /org/freedesktop/ModemManager1/SMS/37 (received)
> /org/freedesktop/ModemManager1/SMS/38 (received)
> /org/freedesktop/ModemManager1/SMS/39 (received)
> /org/freedesktop/ModemManager1/SMS/40 (received)
> /org/freedesktop/ModemManager1/SMS/41 (received)
> /org/freedesktop/ModemManager1/SMS/42 (received)
> /org/freedesktop/ModemManager1/SMS/43 (received)
> /org/freedesktop/ModemManager1/SMS/44 (received)
> /org/freedesktop/ModemManager1/SMS/45 (receiving)
> /org/freedesktop/ModemManager1/SMS/46 (received)
> /org/freedesktop/ModemManager1/SMS/47 (received)
> #
>
> But how do I actually read the SMS-content?
>
>
> I tried using https://raw.githubusercontent.com/openshine/ModemManager/
> master/test/sms-get.py, but it gives errors as follows ::
>
> #
> logic@logic-desktop:~$ *python sms-get.py
> /org/freedesktop/ModemManager1/Modem/0*
> Traceback (most recent call last):
>   File "sms-get.py", line 43, in 
> proxy = bus.get_object(MM_DBUS_SERVICE, objpath)
>   File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in
> get_object
> follow_name_owner_changes=follow_name_owner_changes)
>   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in
> __init__
> self._named_service = conn.activate_name_owner(bus_name)
>   File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in
> activate_name_owner
> self.start_service_by_name(bus_name)
>   File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in
> start_service_by_name
> 'su', (bus_name, flags)))
>   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651,
> in call_blocking
> message, timeout)
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown:
> The name org.freedesktop.ModemManager was not provided by any .service files
> #
>
>
> What is the simplest/most-recommended way to read the SMS-contents?
>
> Will be grateful for pointers.
>
> Thanks and Regards,
> Ajay
>



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

qmi-proxy note being listed

[Ajay Garg]

Hi All.

Currently, I have a modem locked into DirectIP mode, and I am waiting for
the OEM-password to switch it into QMI mode.
Meanwhile, I am fitting the pieces of software-architecture, and as the
first step, trying to ensure that qmi-proxy daemon starts automatically on
system-boot.

However, it does not.

Following is the pre-requisite information I can think of for debugging
(collected at system boot-up).

###
root@logic-desktop:~# *uname -a*
Linux logic-desktop 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15
17:45:15 UTC 2015 i686 i686 i686 GNU/Linux

root@logic-desktop:~# *ps -aux | grep -i network*
root   713  0.0  0.3  54676 14932 ?Ssl  08:41   0:00
NetworkManager
root  2539  0.0  0.1   5524  4600 ?S09:24   0:00
/sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf
/run/sendsigs.omit.d/network-manager.dhclient-eth2.pid -lf
/var/lib/NetworkManager/dhclient-2b9c33ee-08e8-49aa-a10f-5f4f8864de92-eth2.lease
-cf /var/lib/NetworkManager/dhclient-eth2.conf eth2
nobody2543  0.0  0.0   5560  3060 ?S09:24   0:00
/usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts
--bind-interfaces
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf
--cache-size=0 --proxy-dnssec
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq
--conf-dir=/etc/NetworkManager/dnsmasq.d
root  3421  0.0  0.0   4692  2100 pts/12   R+   09:43   0:00 grep
--color=auto -i network

root@logic-desktop:~# *ps -aux | grep -i modem*
root   461  0.0  0.1  40016  7840 ?Ssl  08:41   0:03
/usr/sbin/ModemManager
root  3418  0.0  0.0   4692  2076 pts/12   S+   09:43   0:00 grep
--color=auto -i modem

root@logic-desktop:~# *ps -aux | grep -i proxy*
nobody2543  0.0  0.0   5560  3060 ?S09:24   0:00
/usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts
--bind-interfaces
--pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid
--listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf
--cache-size=0 --proxy-dnssec
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq
--conf-dir=/etc/NetworkManager/dnsmasq.d
root  3371  0.0  0.0   4688  2152 pts/12   S+   09:42   0:00 grep
--color=auto -i proxy

root@logic-desktop:~# *dpkg -l | grep -i modem*
ii  libmm-glib0:i386
1.5.992-3+trustyi386 D-Bus
service for managing modems - shared libraries
ii  lrzsz
0.12.21-7   i386 Tools for
zmodem/xmodem/ymodem file transfer
ii  modemmanager
1.5.992-3+trustyi386 D-Bus
service for managing modems

root@logic-desktop:~# *dpkg -l | grep -i qmi*
ii  libqmi-glib0:i386
1.4.0-1 i386 Support
library to use the Qualcomm MSM Interface (QMI) protocol
ii  libqmi-glib5:i386
1.14.2-2+trusty i386 Support
library to use the Qualcomm MSM Interface (QMI) protocol
ii  libqmi-proxy
1.14.2-2+trusty i386 Proxy to
communicate with QMI ports
ii  libqmi-utils
1.14.2-2+trusty i386 Utilities
to use the QMI protocol from the command line
###


What am I missing?

Will be grateful for pointers.


Thanks and Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Basic (Idiotic) questions about ModemManager / mmcli / libqmi / modems / life

[Ajay Garg]

Thanks Thomas.


Question 2 :
=

Let's take a modem working in QMI-mode.

With the "qcserial" and "qmi_wwan" drivers installed, and NO OTHER
VENDOR-SPECIFIC drivers (sierra/zte/huawei/any-other) required or
installed, the modem (after it is inserted in the USB-slot), will have
the following two created ::

* /dev/cdc-... device-identifier
* a wwan network-interface (visible via "ifconfig" command)

Above two will be created, irrespective of whether or not
ModemManager/mmcli is compiled/running with
QMI_DEVICE_OPEN_FLAGS_PROXY set or not.

Is my understanding correct?


Thanks and Regards,
Ajay


On Sat, Aug 13, 2016 at 8:35 PM,  <tschae...@t-online.de> wrote:
> Am 13.08.2016 16:56 schrieb Ajay Garg <ajaygargn...@gmail.com>:
>>
>> Hi All.
>>
>>
>> Question 1 :
>> ==
>>
>> Can mmcli work as a standalone?
>>
>
> No.
>
>> Or mmcli is a front-end app, communicating (exclusively) with
>> ModemManager in the backend (where ModemManager is the real thing that
>> communicates with modems)?
>>
>
> Yes. (But not exclusively, e.g. networkmanager can also control the
> modemmanager)
>
> Thomas



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Basic (Idiotic) questions about ModemManager / mmcli / libqmi / modems / life

[Ajay Garg]

Hi All.

I have rarely felt so frustrated as I have since last week, with my
haed dizzying over how the following different technologies/tools
fit-in.

I intend to start this email-thread as a series-based questions, one at-a-time.
By keeping this one-at-a-time, I can be sure that I will not get lost
in the maze.

So, if anyone can bear with me, here I go ::


Question 1 :
==

Can mmcli work as a standalone?

Or mmcli is a front-end app, communicating (exclusively) with
ModemManager in the backend (where ModemManager is the real thing that
communicates with modems)?


Hoping for someone to play this "game", it might save me tons of
headache-medicines.


Thanks and Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Crash in Modem-Manager on Ubuntu

[Ajay Garg]

Thanks Aleksander... that's a relief :)

Now before I start posting detailed-logs of problems, I have some last queries.

First of all, my requirement is to have network-connectivity via the
modem; and have the ability to read SMSes and run AT-commands WITHOUT
losing the network-connectivity.

I guess mmcli would do the trick, as modem-manager now comes plugged
in with qmi-daemon, while serializes all requests being sent to the
modem-serial-port (thereby having just one process have access to the
serial-port).

So, assuming (please correct me if I am wrong) that I am correct with
my above hypotheses, will the above architecture work for a modem in
DirectIP-mode (I guess not, but please confirm/reject).


Once again, thanks a ton Aleksander, you have been really quick with
your replies, which is helping me a great deal in understanding how
different pieces fit-in.


Thanks and Regards,
Ajay




On Sat, Aug 13, 2016 at 2:55 AM, Aleksander Morgado
 wrote:
>
>>
>> Thanks Aleksander.
>>
>> I updated the modem-manager, but still run into problems.
>>
>> One query, the modem product-code is 1199:68A3, meaning that it is in
>> DirectIP mode.
>> Do modem-managers support DirectIP-mode modems at all? Or will I have
>> to get the OEM-password and unlock its QMI-mode to have it working
>> with modem-manager?
>>
>
> Yes, ModemManager does (should) work with Direct IP mode.



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Crash in Modem-Manager on Ubuntu

[Ajay Garg]

Thanks Aleksander.

I updated the modem-manager, but still run into problems.

One query, the modem product-code is 1199:68A3, meaning that it is in
DirectIP mode.
Do modem-managers support DirectIP-mode modems at all? Or will I have
to get the OEM-password and unlock its QMI-mode to have it working
with modem-manager?



On Wed, Aug 10, 2016 at 1:36 PM, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
> On Wed, Aug 10, 2016 at 7:32 AM, Ajay Garg <ajaygargn...@gmail.com> wrote:
>> I tried on Ubuntu-14 on Linux-Kernel-3.16 and Linux-Kernel-4.2, and
>> behaviour is same.
>>
>> The modemmanager version is 1.0.0-2ubuntu1.1 on both.
>> I tried "apt-get install", but I am told it is the latest-version available.
>
> That is a very very very old ModemManager version...
>
> For Ubuntu Trusty, you may want to try with this PPA, which has a much
> more recent version:
> https://launchpad.net/~aleksander-m/+archive/ubuntu/modemmanager-trusty
>
> If you still get the segfault, please try to gather MM debug logs:
> https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
>
> Or better, install debug symbols and get a proper gdb backtrace.
>
> Also, note there is a ModemManager specific mailing list, here:
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
>
> Cheers!
>
> --
> Aleksander
> https://aleksander.es



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Architectural-Queries on integrating Sierra-MC8090 with Linux

[Ajay Garg]

CCing NM and MM guys.

On Thu, Aug 11, 2016 at 2:23 PM, Ajay Garg <ajaygargn...@gmail.com> wrote:
> Hi All.
>
> Have posted the question on Sierra-forums
> https://forum.sierrawireless.com/viewtopic.php?f=117=9898
> Posting it here as well, as the activity there is relatively low, and
> this is where all the kernel-guys hand :)
>
>
> I am using a Ubuntu interfaced with a Sierra-MC8090 module.
>
> Right now MC8090 is identifed as a network-interface on Linux, made
> possible by the usage of "sierra" (serial-driver) and "sierra_net"
> (direct-ip usb-to-wwan driver) kernel-drivers. This "mostly" works,
> except that we, in the user-application, are not able to access the
> serial-file /dev/ttyUSB3 (this file is in constant usage by
> /usr/sbin/ModemManager).
>
> Now, my question is, if we disable loading the "sierra_net" driver,
> and use just "sierra" driver to communicate on the serial-port, will
> using the Sierra-Linux-QMI-SDK do the job? In particular,
>
> *
> I understand that we will now have exclusive access (please correct me
> if I am wrong) to the serial-port /dev/ttyUSB3.
>
> *
> How to do we create a socket to a particular server-port using the
> QMI-SDK? I can see in the examples that we can start a data-call for a
> profile (ConnectGSM.c), but I am unable to find how to instantiate a
> socket through which we can do regular reads/writes.
>
>
> Will be grateful to hear back from someone.
>
>
> Thanks and Regards,
> Ajay



-- 
Regards,
Ajay
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel