how to disable wlan and wwan at startup

2010-12-10 Thread pritam.ghang...@gmail.com
Hi

I want only wired networking from NetworkManager.

Can I disable wlan and wwan with some configuratoion option in
nm-system-settings.conf. So that it doesn't even load the corresponding
code/modules.
runtime memory consumption is important to me.

I tried looking for help on configuration but couldn't find much.

-- 
pritam
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: how to disable wlan and wwan at startup

2010-12-10 Thread pritam.ghang...@gmail.com
On Fri, Dec 10, 2010 at 7:21 PM, pritam.ghang...@gmail.com 
pritam.ghang...@gmail.com wrote:

 Hi

 I want only wired networking from NetworkManager.

 Can I disable wlan and wwan with some configuratoion option in
 nm-system-settings.conf. So that it doesn't even load the corresponding
 code/modules.
 runtime memory consumption is important to me.

 I tried looking for help on configuration but couldn't find much.

 --
 pritam


Even if it doesnt reduce memory footprint I dont want network manager to
look for
modems and wlan devices or load any configuration of that kind.

-- 
pritam
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


NM isn't working on embedded linux, ignoring interface.

2010-12-02 Thread pritam.ghang...@gmail.com
Hi

I am trying to get network manager working on a embedded Linux platform.
The setup has a custom SOC with network controller on board.
Vendor has provided us BSP that contains Linux kernel with network driver
built into it.

Kernel version is 2.6.22.19 and its running busy box.

When I try to run NetworkManager it gives out following output:

$ ./NetworkManager --no-daemon
--config=/etc/NetworkManager/nm-system-settings.conf
NetworkManager[909]: info NetworkManager (version 0.8.1) is starting...
NetworkManager[909]: info Read config file
/tmp/nm/etc/NetworkManager/nm-system-settings.conf
NetworkManager[909]: info trying to start the modem manager...
NetworkManager[909]:SCPlugin-Ifupdown: init!
NetworkManager[909]:SCPlugin-Ifupdown: update_system_hostname
NetworkManager[909]:SCPluginIfupdown: guessed connection type (eth0) =
802-3-ethernet
NetworkManager[909]:SCPlugin-Ifupdown:
update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet,
id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e
NetworkManager[909]:SCPlugin-Ifupdown: autoconnect
NetworkManager[909]:SCPluginIfupdown: management mode: managed
NetworkManager[909]:SCPlugin-Ifupdown: devices added (path:
/sys/devices/virtual/net/eth0, iface: eth0)
NetworkManager[909]:SCPluginIfupdown: locking wired connection setting
NetworkManager[909]:SCPlugin-Ifupdown: devices added (path:
/sys/devices/virtual/net/eth1, iface: eth1)
NetworkManager[909]:SCPlugin-Ifupdown: device added (path:
/sys/devices/virtual/net/eth1, iface: eth1): no ifupdown configuration
found.
NetworkManager[909]:SCPlugin-Ifupdown: devices added (path:
/sys/devices/virtual/net/lo, iface: lo)
NetworkManager[909]:SCPlugin-Ifupdown: device added (path:
/sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
NetworkManager[909]:SCPlugin-Ifupdown: end _init.
NetworkManager[909]: info Loaded plugin ifupdown: (C) 2008 Canonical Ltd.
To report bugs please use the NetworkManager mailing list.
NetworkManager[909]: info Loaded plugin keyfile: (c) 2007 - 2008 Red Hat,
Inc.  To report bugs please use the NetworkManager mailing list.
NetworkManager[909]:SCPlugin-Ifupdown: (5082904) ... get_connections.
NetworkManager[909]:SCPlugin-Ifupdown: (5082904) connections count: 1
NetworkManager[909]: info WiFi enabled by radio killswitch; enabled by
state file
NetworkManager[909]: info WWAN enabled by radio killswitch; enabled by
state file
NetworkManager[909]: info WiMAX enabled by radio killswitch; enabled by
state file
NetworkManager[909]: info Networking is enabled by state file
NetworkManager[909]: info Setting system hostname to 'tango3' (from system
configuration)
NetworkManager[909]: info Updating /etc/hosts with new system hostname
NetworkManager[909]: warn /sys/devices/virtual/net/eth0: couldn't
determine device driver; ignoring...
NetworkManager[909]: warn /sys/devices/virtual/net/eth1: couldn't
determine device driver; ignoring...
ifup: interface lo already configured
NetworkManager[909]: warn bluez error getting default adapter: The name
org.bluez was not provided by any .service files

As we can see in log it has started but ignored both the network interfaces
saying :
NetworkManager[909]: warn /sys/devices/virtual/net/eth0: couldn't
determine device driver; ignoring...
NetworkManager[909]: warn /sys/devices/virtual/net/eth1: couldn't
determine device driver; ignoring...


I found a thread with the same issue(
http://mail.gnome.org/archives/networkmanager-list/2010-July/msg00015.html),
but it doesn't have any pointers to solution.

Here is my output of ls -la /sys/class/net

$ ls -la /sys/class/net/
drwxr-xr-x2 root root0 Dec 31 16:00 ./
drwxr-xr-x   18 root root0 Dec 31 16:00 ../
lrwxrwxrwx1 root root0 Jan  1 07:33 eth0 -
../../devices/virtual/net/eth0/
lrwxrwxrwx1 root root0 Jan  1 07:33 eth1 -
../../devices/virtual/net/eth1/
lrwxrwxrwx1 root root0 Jan  1 07:33 lo -
../../devices/virtual/net/lo/

$ ls -la /sys/class/net/eth0/
drwxr-xr-x3 root root0 Dec 31 16:00 ./
drwxr-xr-x5 root root0 Dec 31 16:00 ../
-r--r--r--1 root root16384 Jan  1 07:33 addr_len
-r--r--r--1 root root16384 Jan  1 07:33 address
-r--r--r--1 root root16384 Jan  1 07:33 broadcast
-r--r--r--1 root root16384 Jan  1 07:33 carrier
-r--r--r--1 root root16384 Jan  1 07:33 dormant
-r--r--r--1 root root16384 Jan  1 07:33 features
-rw-r--r--1 root root16384 Jan  1 07:33 flags
-r--r--r--1 root root16384 Jan  1 07:33 ifindex
-r--r--r--1 root root16384 Jan  1 07:33 iflink
-r--r--r--1 root root16384 Jan  1 07:33 link_mode
-rw-r--r--1 root root16384 Jan  1 07:33 mtu
-r--r--r--1 root root16384 Jan  1 07:33 operstate