Re: Specifying ip-type in UCI

2018-10-29 Thread Nick B 
Hey Aleksander,

Done that, and added support to luci-proto-modemmanager as well. 

ModemManager-openwrt:
https://bitbucket.org/mips171/modemmanager-openwrt/commits/c31ae39192ecb58b5fd60dd8c3641f976cf789c9
 

 

Changes seen in action in luci-proto-modemmanager
https://bitbucket.org/mips171/luci-proto-modemmanager/commits/57028e0ed50d26735804225094a2ac105781f826


Best,
Nicholas___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: TOBY-L210 does not detected by ModemManager deamon at boot time

2018-10-29 Thread Dan Williams 
On Mon, 2018-10-29 at 17:27 +0100, Aleksander Morgado wrote:
> Hey,
> 
> > > -Original Message-
> > > From: Aleksander Morgado 
> > > Sent: Monday, October 29, 2018 9:48 AM
> > > To: Baryshnikov, Maxim (Digiteq Automotive)
> > > ; modemmanager-
> > > de...@lists.freedesktop.org
> > > Subject: Re: TOBY-L210 does not detected by ModemManager deamon
> > > at boot
> > > time
> > > 
> > > On 10/23/18 8:19 PM, Baryshnikov, Maxim (Digiteq Automotive)
> > > wrote:
> > > > Hello all,
> > > > I'm struggling with the following issue. On my
> > > > system, the
> > > 
> > > ModemManager (1.8.2) cannot detect TOBY-L2 modem at boot time. I
> > > have
> > > allowed all "filter rules", but the situation is the same as for
> > > the default rules set.
> > > However, if I manually reset the modem with detaching it from the
> > > system (send
> > > AT+CFUN=16 to it), the ModemManager successfully detects it.
> > > > ModemManager is compiled with --without-mbim and
> > > > -without-qmi, but
> > > 
> > > there should be no influence on detection, I guess..
> > > > Do you have any ideas what to check to solve this?
> > > > Is there something
> > > 
> > > wrong with udev? Thank you in advance for any piece of
> > > information..
> > > > Kind regards,
> > > 
> > > How are you sending AT+CFUN=16 to the modem while ModemManager is
> > > running? Please understand that no other program can be using the
> > > TTY port if you
> > > expect ModemManager to use it. Maybe you have a minicom session
> > > open while
> > > MM should be probing the port at the same time?
> > 
> > I don't think that this is happenning at the boot time. I've found
> > a workaround - to retrigger udev event on my device right after the
> > ModemManager service starts.
> > 
> > ExecStart=@sbindir@/ModemManager
> > ExecStartPost=/bin/udevadm trigger
> > /sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2
> > 
> > 
> > > Without looking at the ModemManager debug log it's hard to say
> > > what's really
> > > happening. Could you get it?
> > > https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
> > 
> > I've found nothing much interesting there, it just does not probe
> > ttyACM ports without having an udev event detected first..
> > 
> > Oct 29 09:30:54 zynq7 ModemManager[179]: 
> > [1540805454.220980] (tty/ttyACM0): adding device at sysfs path:
> > /sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-
> > 1.2:1.2/tty/ttyACM0
> > Oct 29 09:30:54 zynq7 ModemManager[179]: 
> > [1540805454.221302] (tty/ttyACM0): port not candidate
> > Oct 29 09:30:54 zynq7 ModemManager[179]: 
> > [1540805454.221565] (tty/ttyACM1): adding device at sysfs path:
> > /sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-
> > 1.2:1.2/tty/ttyACM1
> > Oct 29 09:30:54 zynq7 ModemManager[179]: 
> > [1540805454.221874] (tty/ttyACM1): port not candidate
> > Oct 29 09:30:54 zynq7 ModemManager[179]: 
> > [1540805454.222126] (tty/ttyACM2): adding device at sysfs path:
> > /sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-
> > 1.2:1.2/tty/ttyACM2
> > Oct 29 09:30:54 zynq7 ModemManager[179]: 
> > [1540805454.222410] (tty/ttyACM2): port not candidate
> > 
> > That is probably a problem in udev on my system. It behaves wierd..
> > 
> 
> That totally looks like some udev related issue indeed. The "port not
> candidate" logs will happen if the ttyACM ports aren't flagged with
> ID_MM_CANDIDATE, which is one of the tags added by the ModemManager
> udev rules in /lib/udev/rules.d/. When the system boots and udev
> detects the devices, the rules should be executed and the tag added,
> and for some reason that is not happening in this setup.

udevadm control --log-priority=debug

and replug the device will let you see what udev is doing and why
certain ports may/may not be getting tagged correctly.

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

Re: TOBY-L210 does not detected by ModemManager deamon at boot time

2018-10-29 Thread Aleksander Morgado 
Hey,

> > -Original Message-
> > From: Aleksander Morgado 
> > Sent: Monday, October 29, 2018 9:48 AM
> > To: Baryshnikov, Maxim (Digiteq Automotive)
> > ; modemmanager-
> > de...@lists.freedesktop.org
> > Subject: Re: TOBY-L210 does not detected by ModemManager deamon at boot
> > time
> >
> > On 10/23/18 8:19 PM, Baryshnikov, Maxim (Digiteq Automotive) wrote:
> > > Hello all,
> > > I'm struggling with the following issue. On my system, the
> > ModemManager (1.8.2) cannot detect TOBY-L2 modem at boot time. I have
> > allowed all "filter rules", but the situation is the same as for the 
> > default rules set.
> > However, if I manually reset the modem with detaching it from the system 
> > (send
> > AT+CFUN=16 to it), the ModemManager successfully detects it.
> > > ModemManager is compiled with --without-mbim and 
> > > -without-qmi, but
> > there should be no influence on detection, I guess..
> > > Do you have any ideas what to check to solve this? Is there 
> > > something
> > wrong with udev? Thank you in advance for any piece of information..
> > > Kind regards,
> >
> > How are you sending AT+CFUN=16 to the modem while ModemManager is
> > running? Please understand that no other program can be using the TTY port 
> > if you
> > expect ModemManager to use it. Maybe you have a minicom session open while
> > MM should be probing the port at the same time?
>
> I don't think that this is happenning at the boot time. I've found a 
> workaround - to retrigger udev event on my device right after the 
> ModemManager service starts.
>
> ExecStart=@sbindir@/ModemManager
> ExecStartPost=/bin/udevadm trigger 
> /sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2
>
>
> > Without looking at the ModemManager debug log it's hard to say what's really
> > happening. Could you get it?
> > https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
>
> I've found nothing much interesting there, it just does not probe ttyACM 
> ports without having an udev event detected first..
>
> Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.220980] 
> (tty/ttyACM0): adding device at sysfs path: 
> /sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-1.2:1.2/tty/ttyACM0
> Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.221302] 
> (tty/ttyACM0): port not candidate
> Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.221565] 
> (tty/ttyACM1): adding device at sysfs path: 
> /sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-1.2:1.2/tty/ttyACM1
> Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.221874] 
> (tty/ttyACM1): port not candidate
> Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.222126] 
> (tty/ttyACM2): adding device at sysfs path: 
> /sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-1.2:1.2/tty/ttyACM2
> Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.222410] 
> (tty/ttyACM2): port not candidate
>
> That is probably a problem in udev on my system. It behaves wierd..
>

That totally looks like some udev related issue indeed. The "port not
candidate" logs will happen if the ttyACM ports aren't flagged with
ID_MM_CANDIDATE, which is one of the tags added by the ModemManager
udev rules in /lib/udev/rules.d/. When the system boots and udev
detects the devices, the rules should be executed and the tag added,
and for some reason that is not happening in this setup.

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

RE: TOBY-L210 does not detected by ModemManager deamon at boot time

2018-10-29 Thread Baryshnikov, Maxim (Digiteq Automotive) 


> -Original Message-
> From: Aleksander Morgado 
> Sent: Monday, October 29, 2018 9:48 AM
> To: Baryshnikov, Maxim (Digiteq Automotive)
> ; modemmanager-
> de...@lists.freedesktop.org
> Subject: Re: TOBY-L210 does not detected by ModemManager deamon at boot
> time
> 
> On 10/23/18 8:19 PM, Baryshnikov, Maxim (Digiteq Automotive) wrote:
> > Hello all,
> > I'm struggling with the following issue. On my system, the
> ModemManager (1.8.2) cannot detect TOBY-L2 modem at boot time. I have
> allowed all "filter rules", but the situation is the same as for the default 
> rules set.
> However, if I manually reset the modem with detaching it from the system (send
> AT+CFUN=16 to it), the ModemManager successfully detects it.
> > ModemManager is compiled with --without-mbim and -without-qmi, 
> > but
> there should be no influence on detection, I guess..
> > Do you have any ideas what to check to solve this? Is there 
> > something
> wrong with udev? Thank you in advance for any piece of information..
> > Kind regards,
> 
> How are you sending AT+CFUN=16 to the modem while ModemManager is
> running? Please understand that no other program can be using the TTY port if 
> you
> expect ModemManager to use it. Maybe you have a minicom session open while
> MM should be probing the port at the same time?

I don't think that this is happenning at the boot time. I've found a workaround 
- to retrigger udev event on my device right after the ModemManager service 
starts.

ExecStart=@sbindir@/ModemManager
ExecStartPost=/bin/udevadm trigger 
/sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2 

 
> Without looking at the ModemManager debug log it's hard to say what's really
> happening. Could you get it?
> https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/

I've found nothing much interesting there, it just does not probe ttyACM ports 
without having an udev event detected first..

Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.220980] 
(tty/ttyACM0): adding device at sysfs path: 
/sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-1.2:1.2/tty/ttyACM0
Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.221302] 
(tty/ttyACM0): port not candidate
Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.221565] 
(tty/ttyACM1): adding device at sysfs path: 
/sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-1.2:1.2/tty/ttyACM1
Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.221874] 
(tty/ttyACM1): port not candidate
Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.222126] 
(tty/ttyACM2): adding device at sysfs path: 
/sys/devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-1.2:1.2/tty/ttyACM2
Oct 29 09:30:54 zynq7 ModemManager[179]:  [1540805454.222410] 
(tty/ttyACM2): port not candidate

That is probably a problem in udev on my system. It behaves wierd..
 
> 
> --
> Aleksander
> https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: luci-proto-modemmanager

2018-10-29 Thread Aleksander Morgado 
Hey!

> I have made a LuCI protocol that works with Aleksander0m’s 
> ModemManager-openwrt package.  It is able to set up and configure basic 
> options of a modem.  Unsure if this is an appropriate place to post this.  I 
> posted it on OpenWrt Forum also.
>
> https://bitbucket.org/mips171/luci-proto-modemmanager/wiki/Home
>

Nice thing! Do you want to integrate this in the ModemManager-openwrt
repo directly?

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

luci-proto-modemmanager

2018-10-29 Thread Nick 
Good day,

I have made a LuCI protocol that works with Aleksander0m’s ModemManager-openwrt 
package.  It is able to set up and configure basic options of a modem.  Unsure 
if this is an appropriate place to post this.  I posted it on OpenWrt Forum 
also.

https://bitbucket.org/mips171/luci-proto-modemmanager/wiki/Home


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

Re: Specifying ip-type in UCI

2018-10-29 Thread Aleksander Morgado 
On 10/27/18 1:58 PM, Nick B wrote:
> In the OpenWrt integration is it possible to specify the ip-type for a 
> connection operation in the OpenWrt config file?  I could be doing something 
> wrong but I seem to be hitting an issue related to the hyphen (-) character 
> in that option's identifier which may be causing a UCI or LuCI parsing error. 
>  I am trying to make the option configurable via LuCI.  Is it specified 
> another way?

Don't think ip-type is expected in the config file, you may need to implement 
that support.

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel