Re: nmcli c does not list modem device - part 2

[matti kaasinen]

Dan,
I managed feeding --with-modem-manager-1 option to configuration and now
modem started fine.

What comes to that usb_modeswitch problem: there I were not careful enough.
Both versions of this distribution had same usb_modeswitch version -
identical installation. So, most likely that problem is related to udev
installation that seems to be different.

Thanks a lot of your help
-Matti

2016-11-14 19:51 GMT+02:00 Dan Williams :

> On Mon, 2016-11-14 at 16:28 +0200, matti kaasinen wrote:
> > 2016-11-11 19:41 GMT+02:00 Dan Williams :
> >
> > >
> > > This should be handled by usb_modeswitch.  Either it's not getting
> > > run
> > > correctly from udev, or there's a bug in usb_modeswitch for your
> > > device.  The fact that you can run it manually probably means
> > > something
> > > udev related, probably the usb_modeswitch udev rules.
> > >
> > I studied this - and did not find proper reason/solution. However, it
> > is
> > clear that usb_modeswitch installation is different between
> > previous/current distribution versions. It seems that previous had
> > more
> > systemd stuff than current one (for instance systemd unit template).
> > I
> > tried to install that stuff manually, but it did not help. However, I
> > noticed that switching started working when I started "udevd monitor"
> > just
> > to get debugging information that I did not get before just enabling
> > logging in usb_modeswitch.conf file. Both logging and switching
> > worked
> > after starting udevd. I suppose I should contact to maintainers of
> > this
> > layer installing usb_modeswitch (meta-openembedded).
> >
> > >
> > >
> > > >
> > > > mmcli -L
> > > > does not see any modems before I run that command and naturally
> > > > nmcli c
> > > > does not see modems, too.
> > >
> > > Yeah, that makes sense; it's not switched yet.
> > >
> >
> > >
> > > >
> > > > Log shows that huawei driver proceeds fine after I run modeswitch
> > > > command
> > > > creating ttyUSB terminals. However, when old version produced
> > > > modem
> > > > (interface type 8) new MM produces generic interface (type 14).
> > > > NM
> > > > reports
> > > > regarding this new interface:
> > > > Nov 11 12:55:20 cpr3 NetworkManager[483]:   (wwan0): 'wwan'
> > > > plugin
> > > > not available; creating generic device
> > > > Nov 11 12:55:20 cpr3 NetworkManager[483]:   (wwan0): new
> > > > Generic
> > > > device (carrier: OFF, driver: 'huawei_cdc_ncm', ifindex: 3)
> > > > Nov 11 12:55:20 cpr3 NetworkManager[483]:   devices added
> > > > (path:
> > > > /sys/devices/platform/ocp/4740.usb/47401c00.usb/musb-
> > > > hdrc.1.auto/usb2/2-1/2-1:1.1/net/wwan0,
> > > > iface: wwan0)
> > > > Nov 11 12:55:20 cpr3 NetworkManager[483]:   device added
> > > > (path:
> > > > /sys/devices/platform/ocp/4740.usb/47401c00.usb/musb-
> > > > hdrc.1.auto/usb2/2-1/2-1:1.1/net/wwan0,
> > > > iface: wwan0): no ifupdown configuration found.
> > >
> > > What do you get for "cat /sys/class/net/wwan0/uevent"?  Do you see
> > > "DEVTYPE=wwan" in there?
> > >
> > Yes that I can see ( I don't remember now is this patched version or
> > not,
> > though)
> >
> > >
> > > If not, then the kernel driver should be
> > > fixed to tag this device as a WWAN device, and then NM will ignore
> > > the
> > > interface and wait for ModemManager to announce the modem.
> > >
> > > If you do see DEVTYPE=wwan, can you run NM with debug logging
> > > enabled
> > > (--log-level=debug) and see what it reports?
> > >
> > > Are you sure you have the NM WWAN plugin installed and recognized
> > > by
> > > NM?  It'll print out something at startup about it:
> > >
> >
> > >
> > > Loaded device plugin: NMWwanFactory
> > > (/usr/lib64/NetworkManager/libnm-
> > > device-plugin-wwan.so)
> > >
> > I'm pretty sure that it is not installed. In fact, I don't see this
> > plugin
> > built in the build directory. I tried study, what configuration
> > options I
> > needed to get it build, but really, I did not find any regarding
> > wwan.
> > Also, I did not find anything from documentation regarding wwan
> > plugin.
> > Would I need configuration option to get wwan pluging loaded (after
> > it gets
> > somehow built)?
>
> NM looks for device plugins in $LIBDIR/NetworkManager/.  If the plugin
> exists there NM will try to load it and report an error if it cannot.
>
> The NM build system will attempt to build the WWAN plugin if you either
> (a) have ModemManager libraries installed in a pkg-config-accessible
> path, or (b) if you pass --with-modem-manager-1 at configure time.
>
> Dan
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device - part 2

[Dan Williams]

On Mon, 2016-11-14 at 16:28 +0200, matti kaasinen wrote:
> 2016-11-11 19:41 GMT+02:00 Dan Williams :
> 
> > 
> > This should be handled by usb_modeswitch.  Either it's not getting
> > run
> > correctly from udev, or there's a bug in usb_modeswitch for your
> > device.  The fact that you can run it manually probably means
> > something
> > udev related, probably the usb_modeswitch udev rules.
> > 
> I studied this - and did not find proper reason/solution. However, it
> is
> clear that usb_modeswitch installation is different between
> previous/current distribution versions. It seems that previous had
> more
> systemd stuff than current one (for instance systemd unit template).
> I
> tried to install that stuff manually, but it did not help. However, I
> noticed that switching started working when I started "udevd monitor"
> just
> to get debugging information that I did not get before just enabling
> logging in usb_modeswitch.conf file. Both logging and switching
> worked
> after starting udevd. I suppose I should contact to maintainers of
> this
> layer installing usb_modeswitch (meta-openembedded).
> 
> > 
> > 
> > > 
> > > mmcli -L
> > > does not see any modems before I run that command and naturally
> > > nmcli c
> > > does not see modems, too.
> > 
> > Yeah, that makes sense; it's not switched yet.
> > 
> 
> > 
> > > 
> > > Log shows that huawei driver proceeds fine after I run modeswitch
> > > command
> > > creating ttyUSB terminals. However, when old version produced
> > > modem
> > > (interface type 8) new MM produces generic interface (type 14).
> > > NM
> > > reports
> > > regarding this new interface:
> > > Nov 11 12:55:20 cpr3 NetworkManager[483]:   (wwan0): 'wwan'
> > > plugin
> > > not available; creating generic device
> > > Nov 11 12:55:20 cpr3 NetworkManager[483]:   (wwan0): new
> > > Generic
> > > device (carrier: OFF, driver: 'huawei_cdc_ncm', ifindex: 3)
> > > Nov 11 12:55:20 cpr3 NetworkManager[483]:   devices added
> > > (path:
> > > /sys/devices/platform/ocp/4740.usb/47401c00.usb/musb-
> > > hdrc.1.auto/usb2/2-1/2-1:1.1/net/wwan0,
> > > iface: wwan0)
> > > Nov 11 12:55:20 cpr3 NetworkManager[483]:   device added
> > > (path:
> > > /sys/devices/platform/ocp/4740.usb/47401c00.usb/musb-
> > > hdrc.1.auto/usb2/2-1/2-1:1.1/net/wwan0,
> > > iface: wwan0): no ifupdown configuration found.
> > 
> > What do you get for "cat /sys/class/net/wwan0/uevent"?  Do you see
> > "DEVTYPE=wwan" in there?
> > 
> Yes that I can see ( I don't remember now is this patched version or
> not,
> though)
> 
> > 
> > If not, then the kernel driver should be
> > fixed to tag this device as a WWAN device, and then NM will ignore
> > the
> > interface and wait for ModemManager to announce the modem.
> > 
> > If you do see DEVTYPE=wwan, can you run NM with debug logging
> > enabled
> > (--log-level=debug) and see what it reports?
> > 
> > Are you sure you have the NM WWAN plugin installed and recognized
> > by
> > NM?  It'll print out something at startup about it:
> > 
> 
> > 
> > Loaded device plugin: NMWwanFactory
> > (/usr/lib64/NetworkManager/libnm-
> > device-plugin-wwan.so)
> > 
> I'm pretty sure that it is not installed. In fact, I don't see this
> plugin
> built in the build directory. I tried study, what configuration
> options I
> needed to get it build, but really, I did not find any regarding
> wwan.
> Also, I did not find anything from documentation regarding wwan
> plugin.
> Would I need configuration option to get wwan pluging loaded (after
> it gets
> somehow built)?

NM looks for device plugins in $LIBDIR/NetworkManager/.  If the plugin
exists there NM will try to load it and report an error if it cannot.

The NM build system will attempt to build the WWAN plugin if you either
(a) have ModemManager libraries installed in a pkg-config-accessible
path, or (b) if you pass --with-modem-manager-1 at configure time.

Dan
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device - part 2

[matti kaasinen]

2016-11-11 19:41 GMT+02:00 Dan Williams :

> This should be handled by usb_modeswitch.  Either it's not getting run
> correctly from udev, or there's a bug in usb_modeswitch for your
> device.  The fact that you can run it manually probably means something
> udev related, probably the usb_modeswitch udev rules.
>
I studied this - and did not find proper reason/solution. However, it is
clear that usb_modeswitch installation is different between
previous/current distribution versions. It seems that previous had more
systemd stuff than current one (for instance systemd unit template). I
tried to install that stuff manually, but it did not help. However, I
noticed that switching started working when I started "udevd monitor" just
to get debugging information that I did not get before just enabling
logging in usb_modeswitch.conf file. Both logging and switching worked
after starting udevd. I suppose I should contact to maintainers of this
layer installing usb_modeswitch (meta-openembedded).

>
> > mmcli -L
> > does not see any modems before I run that command and naturally
> > nmcli c
> > does not see modems, too.
>
> Yeah, that makes sense; it's not switched yet.
>

> > Log shows that huawei driver proceeds fine after I run modeswitch
> > command
> > creating ttyUSB terminals. However, when old version produced modem
> > (interface type 8) new MM produces generic interface (type 14). NM
> > reports
> > regarding this new interface:
> > Nov 11 12:55:20 cpr3 NetworkManager[483]:   (wwan0): 'wwan'
> > plugin
> > not available; creating generic device
> > Nov 11 12:55:20 cpr3 NetworkManager[483]:   (wwan0): new
> > Generic
> > device (carrier: OFF, driver: 'huawei_cdc_ncm', ifindex: 3)
> > Nov 11 12:55:20 cpr3 NetworkManager[483]:   devices added
> > (path:
> > /sys/devices/platform/ocp/4740.usb/47401c00.usb/musb-
> > hdrc.1.auto/usb2/2-1/2-1:1.1/net/wwan0,
> > iface: wwan0)
> > Nov 11 12:55:20 cpr3 NetworkManager[483]:   device added (path:
> > /sys/devices/platform/ocp/4740.usb/47401c00.usb/musb-
> > hdrc.1.auto/usb2/2-1/2-1:1.1/net/wwan0,
> > iface: wwan0): no ifupdown configuration found.
>
> What do you get for "cat /sys/class/net/wwan0/uevent"?  Do you see
> "DEVTYPE=wwan" in there?
>
Yes that I can see ( I don't remember now is this patched version or not,
though)

> If not, then the kernel driver should be
> fixed to tag this device as a WWAN device, and then NM will ignore the
> interface and wait for ModemManager to announce the modem.
>
> If you do see DEVTYPE=wwan, can you run NM with debug logging enabled
> (--log-level=debug) and see what it reports?
>
> Are you sure you have the NM WWAN plugin installed and recognized by
> NM?  It'll print out something at startup about it:
>

> Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-
> device-plugin-wwan.so)
>
I'm pretty sure that it is not installed. In fact, I don't see this plugin
built in the build directory. I tried study, what configuration options I
needed to get it build, but really, I did not find any regarding wwan.
Also, I did not find anything from documentation regarding wwan plugin.
Would I need configuration option to get wwan pluging loaded (after it gets
somehow built)?

>
> Dan
>
-Matti
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device - part 2

[Dan Williams]

On Fri, 2016-11-11 at 15:22 +0200, matti kaasinen wrote:
> Hi (again)!
> 
> I discussed this problem originally in
> https://mail.gnome.org/archives/networkmanager-list/2016-March/msg000
> 79.html
> 
> I had to upgrade my set-up that is currently as follows:
> I am using Huawei 3131 modem whose ID should switch from 14fe to 1506
> Platform is yocto based am335x board running on Linux 4.4, NM version
> 1.0.10, MM version 1.4.12. I have tried to patch MM with commit
> number
> 359ec84671f9fc0869443b9f0b9555324a0fff78 to fix Huawei AT^NDISDUP
> problem
> but in fact I do not see any difference to opera the version without
> patching.
> 
> I changed from dhclient to internal dhcp client in order to get rid
> of IP
> address change immediately after boot. That seems working.
> 
> 
> Problems:
> 
> Modem mode does not change from Mass Storage/SD Storage to Modem.
> However, mode switches quite fine if I run manually command:
> usb_modeswitch -I -W -c /usr/share/usb_modeswitch/12d1\:14fe
> --default-vendor 12d1 --default-product 14fe --target-product 1506
> 
> I don't know, if this is something that modemmanager should bring for
> udev
> to make switching or should it come directly from usb_modeswitch set-
> up.
> Anyhow, that command uses the usb_modeswitch database.

This should be handled by usb_modeswitch.  Either it's not getting run
correctly from udev, or there's a bug in usb_modeswitch for your
device.  The fact that you can run it manually probably means something
udev related, probably the usb_modeswitch udev rules.

> mmcli -L
> does not see any modems before I run that command and naturally
> nmcli c
> does not see modems, too.

Yeah, that makes sense; it's not switched yet.

> Log shows that huawei driver proceeds fine after I run modeswitch
> command
> creating ttyUSB terminals. However, when old version produced modem
> (interface type 8) new MM produces generic interface (type 14). NM
> reports
> regarding this new interface:
> Nov 11 12:55:20 cpr3 NetworkManager[483]:   (wwan0): 'wwan'
> plugin
> not available; creating generic device
> Nov 11 12:55:20 cpr3 NetworkManager[483]:   (wwan0): new
> Generic
> device (carrier: OFF, driver: 'huawei_cdc_ncm', ifindex: 3)
> Nov 11 12:55:20 cpr3 NetworkManager[483]:   devices added
> (path:
> /sys/devices/platform/ocp/4740.usb/47401c00.usb/musb-
> hdrc.1.auto/usb2/2-1/2-1:1.1/net/wwan0,
> iface: wwan0)
> Nov 11 12:55:20 cpr3 NetworkManager[483]:   device added (path:
> /sys/devices/platform/ocp/4740.usb/47401c00.usb/musb-
> hdrc.1.auto/usb2/2-1/2-1:1.1/net/wwan0,
> iface: wwan0): no ifupdown configuration found.

What do you get for "cat /sys/class/net/wwan0/uevent"?  Do you see
"DEVTYPE=wwan" in there?  If not, then the kernel driver should be
fixed to tag this device as a WWAN device, and then NM will ignore the
interface and wait for ModemManager to announce the modem.

If you do see DEVTYPE=wwan, can you run NM with debug logging enabled
(--log-level=debug) and see what it reports?

Are you sure you have the NM WWAN plugin installed and recognized by
NM?  It'll print out something at startup about it:

Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-
device-plugin-wwan.so)

Dan

> Can anyone say how to proceed or is more profound debugging needed or
> any
> other information?
> 
> Thanks,
> Matti
> ___
> networkmanager-list mailing list
> networkmanager-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/networkmanager-list
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device - part 2

[matti kaasinen]

Some more information:
nmcli d
DEVICE  TYPE  STATE  CONNECTION
eth0ethernet  connected  eth0
lo  loopback  unmanaged  --
wwan0   wwan  unmanaged  --


mmcli -m 0

/org/freedesktop/ModemManager1/Modem/0 (device id
'ec133b2df3dde8169aba5cddabc251e62f4601ec')
  -
  Hardware |   manufacturer: 'huawei'
   |  model: 'E3131'
   |   revision: '21.157.14.00.78'
   |  supported: 'gsm-umts'
   |current: 'gsm-umts'
   |   equipment id: '866715019103353'
  -
  System   | device:
'/sys/devices/platform/ocp/4740.usb/47401c00.usb/musb-hdrc.1.auto/usb2/2-1'
   |drivers: 'huawei_cdc_ncm, option1'
   | plugin: 'Huawei'
   |   primary port: 'ttyUSB2'
   |  ports: 'ttyUSB0 (at), ttyUSB2 (at), cdc-wdm0 (at),
wwan0 (net)'
  -
  Numbers  |   own : 'unknown'
  -
  Status   |   lock: 'none'
   | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10),
sim-puk2 (10)'
   |  state: 'disabled'
   |power state: 'on'
   |access tech: 'unknown'
   | signal quality: '0' (cached)
  -
  Modes|  supported: 'allowed: 2g, 3g; preferred: none
   |  allowed: 2g, 3g; preferred: 2g
   |  allowed: 2g, 3g; preferred: 3g
   |  allowed: 2g; preferred: none
   |  allowed: 3g; preferred: none'
   |current: 'allowed: 2g, 3g; preferred: 3g'
  -
  Bands|  supported: 'unknown'
   |current: 'unknown'
  -
  IP   |  supported: 'ipv4, ipv6, ipv4v6'
  -
  3GPP |   imei: '866715019103353'
   |  enabled locks: 'none'
   |operator id: 'unknown'
   |  operator name: 'unknown'
   |   subscription: 'unknown'
   |   registration: 'unknown'
  -
  SIM  |   path: '/org/freedesktop/ModemManager1/SIM/0'

  -
  Bearers  |  paths: 'none'




2016-11-11 15:22 GMT+02:00 matti kaasinen :

> Hi (again)!
>
> I discussed this problem originally in https://mail.gnome.org/
> archives/networkmanager-list/2016-March/msg00079.html
>
> I had to upgrade my set-up that is currently as follows:
> I am using Huawei 3131 modem whose ID should switch from 14fe to 1506
> Platform is yocto based am335x board running on Linux 4.4, NM version
> 1.0.10, MM version 1.4.12. I have tried to patch MM with commit number
> 359ec84671f9fc0869443b9f0b9555324a0fff78 to fix Huawei AT^NDISDUP problem
> but in fact I do not see any difference to opera the version without
> patching.
>
> I changed from dhclient to internal dhcp client in order to get rid of IP
> address change immediately after boot. That seems working.
>
> 
> Problems:
> 
> Modem mode does not change from Mass Storage/SD Storage to Modem.
> However, mode switches quite fine if I run manually command:
> usb_modeswitch -I -W -c /usr/share/usb_modeswitch/12d1\:14fe
> --default-vendor 12d1 --default-product 14fe --target-product 1506
>
> I don't know, if this is something that modemmanager should bring for udev
> to make switching or should it come directly from usb_modeswitch set-up.
> Anyhow, that command uses the usb_modeswitch database.
>
> mmcli -L
> does not see any modems before I run that command and naturally
> nmcli c
> does not see modems, too.
>
> Log shows that huawei driver proceeds fine after I run modeswitch command
> creating ttyUSB terminals. However, when old version produced modem
> (interface type 8) new MM produces generic interface (type 14). NM reports
> regarding this new interface:
> Nov 11 12:55:20 cpr3 NetworkManager[483]:   (wwan0): 'wwan' plugin
> not available; creating generic device
> Nov 11 12:55:20 cpr3 NetworkManager[483]:   (wwan0): new Generic
> device (carrier: OFF, driver: 'huawei_cdc_ncm', ifindex: 3)
> Nov 11 12:55:20 cpr3 NetworkManager[483]:   devices added (path:
> /sys/devices/platform/ocp/4740.usb/47401c00.usb/
> musb-hdrc.1.auto/usb2/2-1/2-1:1.1/net/wwan0, iface: wwan0)
> Nov 11 12:55:20 cpr3 NetworkManager[483]:   device added (path:
> /sys/devices/platform/ocp/4740.usb/47401c00.usb/
> musb-hdrc.1.auto/usb2/2-1/2-1:1.1/net/wwan0, iface: wwan0): no ifupdown
> configuration found.
>
> Can anyone say how to proceed or is more profound debugging needed or any
> other information?
>
> Thanks,
> Matti
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device

[matti kaasinen]

Thanks Aleksander. I checked build logs and indeed, configure log said:
  modemmanager-1: no
I re-run networkmanager recipe and it switched to "yes". I don't know how
this can happen.

There is no explicit "--with-modem-manager-1" in the networkmanager recipe
(meta-openembedded layer), so most likely this information has been taken
from ModemManager libraries. I do have my own overlay recipe for
networkmanager that just makes one patch that edit dhclient.conf file for
providing mac address for client identification. So, that recipe overlay
just feeds one patch and does not touch to configuration at all.

Anyhow, now I re-built the image and it seems now working. Thank you for
your help.

Best regards,
Matti

2016-03-14 22:11 GMT+02:00 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:
> >
> > src/nm-udev-manager.c:568] handle_uevent(): UDEV event: action 'add'
> subsys
> > 'net' device 'wwan0'
> > src/nm-udev-manager.c:477] net_add(): (wwan0): ignoring interface with
> > devtype 'wwan'
> > src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to
> > (re)launch modem-manager...
> > src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to
> > (re)launch modem-manager...
> > src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to
> > (re)launch modem-manager...
>
> That is trying to launch the old ModemManager, which has a different bus
> name.
>
> You need to configure NetworkManager explicitly with
> "--with-modem-manager-1", or explicitly add ModemManager libraries as
> build dependency on your yocto recipe, so that the requirement of
> "--with-modem-manager-1" is detected automatically.
>
> --
> Aleksander
> https://aleksander.es
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device

[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:
>
> src/nm-udev-manager.c:568] handle_uevent(): UDEV event: action 'add' subsys
> 'net' device 'wwan0'
> src/nm-udev-manager.c:477] net_add(): (wwan0): ignoring interface with
> devtype 'wwan'
> src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to
> (re)launch modem-manager...
> src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to
> (re)launch modem-manager...
> src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to
> (re)launch modem-manager...

That is trying to launch the old ModemManager, which has a different bus name.

You need to configure NetworkManager explicitly with
"--with-modem-manager-1", or explicitly add ModemManager libraries as
build dependency on your yocto recipe, so that the requirement of
"--with-modem-manager-1" is detected automatically.

-- 
Aleksander
https://aleksander.es
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device

[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 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'
> > src/nm-udev-manager.c:477] net_add(): (wwan0): ignoring interface
> > with
> > devtype 'wwan'
> > src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting
> > to
> > (re)launch modem-manager...
> > src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting
> > to
> > (re)launch modem-manager...
> > src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting
> > to
> > (re)launch modem-manager...
> >
>
> This means that NetworkManager cannot see ModemManager on D-Bus.  Does
> 'mmcli -L' produce any output?
>
> Dan
>
>
> > 
> > -Matti
> >
> >
> > 2016-03-14 15:39 GMT+02:00 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 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  > > > der.es>:
> > > >
> > > > >
> > > > > 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 traffic (dbus-monitor --system)
> > > > > > and it
> > > > > seems that
> > > > > >
> > > > > > all the information received by mmcli is seen from this
> > > > > > monitorin
> > > > > session.
> > > > >
> > > > >
> > > > > Did you try to run NetworkManager with debug logging? IIRC, the
> > > > > modem
> > > > > management code in NM does print several debug logs when
> > > > > watching MM
> > > > > in the bus.
> > > > >
> > > > > --
> > > > > Aleksander
> > > > > https://aleksander.es
> > > > >
> > > >
> > ___
> > networkmanager-list mailing list
> > networkmanager-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/networkmanager-list
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device

[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] handle_uevent(): UDEV event: action 'add'
> subsys
> 'net' device 'wwan0'
> src/nm-udev-manager.c:477] net_add(): (wwan0): ignoring interface
> with
> devtype 'wwan'
> src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting
> to
> (re)launch modem-manager...
> src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting
> to
> (re)launch modem-manager...
> src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting
> to
> (re)launch modem-manager...
> 

This means that NetworkManager cannot see ModemManager on D-Bus.  Does
'mmcli -L' produce any output?

Dan


> 
> -Matti
> 
> 
> 2016-03-14 15:39 GMT+02:00 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 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  > > der.es>:
> > > 
> > > > 
> > > > 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 traffic (dbus-monitor --system)
> > > > > and it
> > > > seems that
> > > > > 
> > > > > all the information received by mmcli is seen from this
> > > > > monitorin
> > > > session.
> > > > 
> > > > 
> > > > Did you try to run NetworkManager with debug logging? IIRC, the
> > > > modem
> > > > management code in NM does print several debug logs when
> > > > watching MM
> > > > in the bus.
> > > > 
> > > > --
> > > > Aleksander
> > > > https://aleksander.es
> > > > 
> > > 
> ___
> networkmanager-list mailing list
> networkmanager-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/networkmanager-list
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device

[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'
src/nm-udev-manager.c:477] net_add(): (wwan0): ignoring interface with
devtype 'wwan'
src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to
(re)launch modem-manager...
src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to
(re)launch modem-manager...
src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to
(re)launch modem-manager...

-Matti


2016-03-14 15:39 GMT+02:00 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 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 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 traffic (dbus-monitor --system) and it
>>> seems that
>>> > all the information received by mmcli is seen from this monitorin
>>> session.
>>>
>>>
>>> Did you try to run NetworkManager with debug logging? IIRC, the modem
>>> management code in NM does print several debug logs when watching MM
>>> in the bus.
>>>
>>> --
>>> Aleksander
>>> https://aleksander.es
>>>
>>
>>
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device

[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 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 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 traffic (dbus-monitor --system) and it seems
>> that
>> > all the information received by mmcli is seen from this monitorin
>> session.
>>
>>
>> Did you try to run NetworkManager with debug logging? IIRC, the modem
>> management code in NM does print several debug logs when watching MM
>> in the bus.
>>
>> --
>> Aleksander
>> https://aleksander.es
>>
>
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device

[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 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 traffic (dbus-monitor --system) and it seems
> that
> > all the information received by mmcli is seen from this monitorin
> session.
>
>
> Did you try to run NetworkManager with debug logging? IIRC, the modem
> management code in NM does print several debug logs when watching MM
> in the bus.
>
> --
> Aleksander
> https://aleksander.es
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device

[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 traffic (dbus-monitor --system) and it seems that
> all the information received by mmcli is seen from this monitorin session.


Did you try to run NetworkManager with debug logging? IIRC, the modem
management code in NM does print several debug logs when watching MM
in the bus.

-- 
Aleksander
https://aleksander.es
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device

[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 from this monitorin
session.

-Matti
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nmcli c does not list modem device

[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 bringing gathering
> up data from from modem interfrace for NM. Then NM could identify
> this modem and I got 'DeviceAdded' signal. Now NM can't detect modem
> and I don't get this signal.
> 
> Modem manager procedes up to:
> export_modem(): (/org/freedesktop/ModemManager1/Modem/4): 'Huawei'
> modem, VID 0x12D1 PID 0x1506 (usb)
> 
> Device is quite well accessible with mmclient.
> 
> Platform is yocto based am335x board running on Linux 4.1, NM version
> 0.9.8.10, MM version 1.4.2. I have patched MM with commit number
> 359ec84671f9fc0869443b9f0b9555324a0fff78 to fix Huawei AT^NDISDUP
> problem. Last week it worked fine.
> 
> Aren't NM and MM discussing through dbus? Only difference that I can
> figure out is that now I have built python-networkmanager into image.
> Could that disturb somehow?
> What could prevent NM from seeing modem devices?
> 
> Cheers,
> Matti
> ___
> networkmanager-list mailing list
> networkmanager-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/networkmanager-list

signature.asc
Description: This is a digitally signed message part
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list