Could not find "pppd" binary

2016-03-14 Thread Ali Nematollahi
Hi guys I finally got MM 1.4.12 and 1.0.10 working and talking to each other...after a long battle. I got NM to a point that it detects MM and after all MM set up is done, it tries to bring up the connection I have up but it fails saying pppd binary not found. I compiled the NM with the option

Re: nmcli c does not list modem device

2016-03-14 Thread Aleksander Morgado
On Mon, Mar 14, 2016 at 2:55 PM, matti kaasinen wrote: > In fact there are two more messages preceding those ones I mentioned before, > but I guess they have nothing to do with this problem. I'll get following > messages, if I have MM running from boot: > >

Re: NetworkManager 1.1.90 : nm-exported-object.c:293:nm_exported_object_class_add_interface: assertion failed: (object_property != NULL)

2016-03-14 Thread Dan Williams
On Mon, 2016-03-14 at 10:51 -0700, Ali Nematollahi wrote: > Hello Dan > Ok, some progress > One of my colleagues suggested sending an "AT" at the same time as > "AT^SCFG": AT^SCFG\r\AT"...So I changed the plugin that sends SCFG > and it > actually worked. The modem responds to SCFG immediately

Re: nmcli c does not list modem device

2016-03-14 Thread matti kaasinen
Yes, mmcli seems workin quite nicely - no problems at all. 2016-03-14 16:27 GMT+02:00 Dan Williams : > On Mon, 2016-03-14 at 15:55 +0200, matti kaasinen wrote: > > In fact there are two more messages preceding those ones I mentioned > > before, but I guess they have nothing to

Re: nmcli radio off connected to ModemManager power state low

2016-03-14 Thread Carlo Lobrano
> I'm not entirely sure what you mean with "power off" and "shut down the > radio", but here are the definitions I'm using: > power off: the entire modem is powered off not just the radio. The > device does not communicate with the host because it is unpowered. > > radio off: the radio is powered

Re: nmcli radio off connected to ModemManager power state low

2016-03-14 Thread Dan Williams
On Mon, 2016-03-14 at 09:40 -0500, Dan Williams wrote: > On Sun, 2016-03-13 at 18:23 +0100, c.lobr...@gmail.com wrote: > > > > I'm sorry, I think I explained myself wrong. > > > > CFUN=4 is ok for radio off, I wanted to say that some plugins might > > not  > > use CFUN=4 for "power low". > > In

Re: nmcli radio off connected to ModemManager power state low

2016-03-14 Thread Dan Williams
On Sun, 2016-03-13 at 18:23 +0100, c.lobr...@gmail.com wrote: > I'm sorry, I think I explained myself wrong. > > CFUN=4 is ok for radio off, I wanted to say that some plugins might > not  > use CFUN=4 for "power low". > In Telit modem, as example, I might use CFUN=5 "mobile full  > functionality

Re: nmcli radio off connected to ModemManager power state low

2016-03-14 Thread Dan Williams
On Sun, 2016-03-13 at 12:26 +0100, Aleksander Morgado wrote: > On Sun, Mar 13, 2016 at 10:28 AM, Carlo Lobrano > wrote: > > > > > > thank you, it is more clear now. I will check in my system for > > rfkill. > > One more question, do you think it will be feasible for NM to

Re: nmcli c does not list modem device

2016-03-14 Thread Dan Williams
On Mon, 2016-03-14 at 15:55 +0200, matti kaasinen wrote: > In fact there are two more messages preceding those ones I mentioned > before, but I guess they have nothing to do with this problem. I'll > get > following messages, if I have MM running from boot: > > src/nm-udev-manager.c:568]

Re: nmcli c does not list modem device

2016-03-14 Thread matti kaasinen
In fact there are two more messages preceding those ones I mentioned before, but I guess they have nothing to do with this problem. I'll get following messages, if I have MM running from boot: src/nm-udev-manager.c:568] handle_uevent(): UDEV event: action 'add' subsys 'net' device 'wwan0'

Re: nmcli c does not list modem device

2016-03-14 Thread matti kaasinen
There was also other one besides these (re)launch messages. The first message was: modem_manager_disappeared(): trying to start the modem manager... then repeating gradually: Requesting to (re)launch modem-manager... 2016-03-14 15:35 GMT+02:00 matti kaasinen : > I

Re: nmcli c does not list modem device

2016-03-14 Thread matti kaasinen
I tried it now: NM can't communicate with MM. There is only one type of message related to modem-manager: src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to (re)launch modem-manager... -Matti 2016-03-14 15:01 GMT+02:00 Aleksander Morgado : > On

Re: nmcli c does not list modem device

2016-03-14 Thread Aleksander Morgado
On Mon, Mar 14, 2016 at 1:57 PM, matti kaasinen wrote: > 2016-03-14 14:53 GMT+02:00 Thomas Haller : >> >> > I can't get modem device listed with >> > nmcli c >> >> do you mean `nmcli d` (for [d]evice)? > > > > Yes, indeed. > BTW, I just monitored dbus

Re: nmcli c does not list modem device

2016-03-14 Thread matti kaasinen
2016-03-14 14:53 GMT+02:00 Thomas Haller : > > I can't get modem device listed with > > nmcli c > > do you mean `nmcli d` (for [d]evice)? > Yes, indeed. BTW, I just monitored dbus traffic (dbus-monitor --system) and it seems that all the information received by mmcli is seen

Re: nmcli c does not list modem device

2016-03-14 Thread Thomas Haller
On Mon, 2016-03-14 at 13:48 +0200, matti kaasinen wrote: > Hi! > > I can't get modem device listed with  > nmcli c do you mean `nmcli d` (for [d]evice)? > command. So, NM does not see it and therefore it can't start > connection with NM. > Last week it worked fine. I wrote python code for

nmcli c does not list modem device

2016-03-14 Thread matti kaasinen
Hi! I can't get modem device listed with nmcli c command. So, NM does not see it and therefore it can't start connection with NM. Last week it worked fine. I wrote python code for bringing gathering up data from from modem interfrace for NM. Then NM could identify this modem and I got