Dear Dan,
I don't start the D-Bus for WIFI when am running the NM in my embedded
device. I don't know if there is the problem for NM or device driver. But I
can use iwconfig and dhclient to set wifi to connect to Internet. I also
know the device driver may be the problem for iwioctl since there are some
warning as shown in /var/log/message, I also have checked NM is always
calling sys/ioctl.h. My questions, if I don't fix the device driver, Is
there a way to fix this problem through change some codes in NM?, or there
is no way in the NM side. The wifi device is Atheros AR6000,Thanks for
your suggestion.
Wei
The information from /var/log/messages:
[42949383.22] ar6000_init() Got WMI @ 0xccc41c00.
[42949383.47] mac address = 00:21:e8:70:c8:bc
[42949383.47] ar6000_init() WMI is ready
[42949383.49] wmi_control_rx() : Unknown id 0x101e
[42949383.50] AR6000 Reg Code = 0x8348
[42949397.41] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[42949403.94] iwioctl: cmd=0x8b03 not allowed in this mode
[42949403.95] iwioctl: cmd=0x8b1d not allowed in this mode
[42949403.96] iwioctl: cmd=0x8b23 not allowed in this mode
[42949403.97] iwioctl: cmd=0x8b25 not allowed in this mode
[42949404.02] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
[42949404.25] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
[42949406.05] iwioctl: cmd=0x8b03 not allowed in this mode
[42949406.07] iwioctl: cmd=0x8b1d not allowed in this mode
[42949406.08] iwioctl: cmd=0x8b23 not allowed in this mode
[42949406.09] iwioctl: cmd=0x8b25 not allowed in this mode
[42949407.31] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[42949408.54] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
[42949410.13] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
[42949414.77] keyboard.c: can't emulate rawmode for keycode 0
[42949419.57] keyboard.c: can't emulate rawmode for keycode 0
[42949420.84] eth2: no IPv6 routers present
[42949590.19] iwioctl: cmd=0x8b03 not allowed in this mode
[42949590.20] iwioctl: cmd=0x8b1d not allowed in this mode
[42949590.21] iwioctl: cmd=0x8b23 not allowed in this mode
[42949590.22] iwioctl: cmd=0x8b25 not allowed in this mode
[42949591.54] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[42949592.99] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
[42949597.36] iwioctl: cmd=0x8b03 not allowed in this mode
[42949597.38] iwioctl: cmd=0x8b1d not allowed in this mode
[42949597.39] iwioctl: cmd=0x8b23 not allowed in this mode
[42949597.40] iwioctl: cmd=0x8b25 not allowed in this mode
[42949597.92] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
[42949599.05] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[42949600.50] eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
[42949610.99] eth2: no IPv6 routers present
# iwconfig
lono wireless extensions[ 93.67] iwioctl: cmd=0x8b03 not
allowed in this mode
.
sit0 no wireless exten[ 93.69] iwioctl: cmd=0x8b1d not allowed in
this mode
sions.
eth2 no wireless [ 93.70] iwioctl: cmd=0x8b23 not allowed in this
mode
extensions.
[ 93.72] iwioctl: cmd=0x8b25 not allowed in this mode
wlan0 AR6000 802.11g Mode:Managed Bit Rate=1 Mb/s Tx-Power=0 dBm
Sensitivity=0/3
Retry:on
Encryption key:off
Power Management:off
Link Quality:255/94 Signal level:-96 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
According to the documents and your notes, I have setup
/etc/NetworkManager/nm-system-setting.conf in the embedded device
This is as follows
$cat nm-system-setting.conf
[main]
plugins=ifupdown,keyfile
[keyfile]
unmanaged-device=mac:00:21:e8:70:c8:bc
[ifupdown]
managed=false
Then I check the D-BUS for wifi, but the the D-bus for wifi is still not
coming out, which still has informations as follows:
device list is /org/freedesktop/NetworkManager/Devices/0
Device eth2 is activate
No
device list is /org/freedesktop/NetworkManager/Devices/1
Device wlan0 is activate
On Tue, Mar 23, 2010 at 3:17 AM, Dan Williams d...@redhat.com wrote:
On Mon, 2010-03-22 at 09:25 -0700, Bluesky_greenleaf wrote:
Dear Dan,
There are an Ethernet(eth2) and a wifi(wlan0) in an embedded device,
Ethernet and Wifi are both set to connect Internet successful by using
the manually Linux commands such as iwconfig wlan0
After NM is running in the embedded device, the D-Bus for Ethernet
will appear, but the the D-BUS for WIFI is not appeared, which has
shown as follows using the python to test:
Are you running a user or system settings service that can provide the
necessary configuration to NetworkManager for the wifi device? NM will
create a fake DHCP ethernet connection for the wired device
automatically if no other configuration exists, but the wifi device
