Issue facing in WI-FI enabling (wlan0: link is not ready)

2,911 views
Skip to first unread message

Sandeep sp

unread,
Feb 5, 2012, 10:18:06 PM2/5/12
to android-porting
Hi

I has been trying to set up the Wi-Fi on our board.
The configuration options which i had chosen are Android Private
socket and WIFI drivers are loaded as Kernel modules. It's able to
properly load the Wi-Fi driver and firmware also.

We are trying to test the WI-FI functionality through command
prompt ( As we are not yet started working on LCD).

Through adb shell we are executing this command
$svc wifi enable

On execution of this command, It throws an message saying
"ADDRCONF(NETDEV_UP): wlan0: link is not ready "

The log messages are:
D/NetdConnector( 103): RCV <- {600 Iface linkstate wlan0 down}
D/NetdConnector( 103): RCV <- {600 Iface linkstate wlan0 down}

On the closer look, the wpa_supplicant service has been already
started and running, and "wlan0" entry has been added. (crosschecked
with $cat /proc/net/dev)

I Collected the logs from the "network daemon connector" module
(SND-->sendCommandLocked(), RCV-->listenToSocket() and RSP--
>doCommandLocked() )

Can anyone me know, why the "wlan0" is down ?


D/NetdConnector( 94): SND -> {interface ipv6 wlan0 disable} {null}
D/NetdConnector( 94): SND -> {interface setthrottle rmnet0 -1 -1}
{null}
D/NetdConnector( 94): SND -> {interface setthrottle rmnet0 -1 -1}
{null}
D/NetdConnector( 94): SND -> {softap fwreload wlan0 STA} {null}
D/NetdConnector( 94): SND -> {interface getcfg wlan0} {null}
D/NetdConnector( 94): SND -> {interface setcfg wlan0 0.0.0.0 0 [down
broadcast multicast]} {null}
D/NetdConnector( 94): SND -> {interface ipv6privacyextensions wlan0
enable} {null}


D/NetdConnector( 94): RSP <- {400 Failed to change IPv6 state (No
such file or directory)}
D/NetdConnector( 94): RSP <- {200 Interface throttling set}
D/NetdConnector( 94): RSP <- {200 Interface throttling set}
D/NetdConnector( 94): RSP <- {200 Softap operation succeeded}
D/NetdConnector( 94): RSP <- {213 de:ad:be:ef:00:00 0.0.0.0 0 [down
broadcast multicast]}
D/NetdConnector( 94): RSP <- {200 Interface configuration set}
D/NetdConnector( 94): RSP <- {200 IPv6 privacy extensions changed}


D/NetdConnector( 94): RCV <- {400 Failed to change IPv6 state (No
such file or directory)}
D/NetdConnector( 94): RCV <- {200 Interface throttling set}
D/NetdConnector( 94): RCV <- {200 Interface throttling set}
D/NetdConnector( 94): RCV <- {600 Iface linkstate wlan0 down}
D/NetdConnector( 94): RCV <- {600 Iface added wlan0}
D/NetdConnector( 94): RCV <- {600 Iface removed wlan0}
D/NetdConnector( 94): RCV <- {600 Iface linkstate wlan0 down}
D/NetdConnector( 94): RCV <- {600 Iface added wlan0}
D/NetdConnector( 94): RCV <- {200 Softap operation succeeded}
D/NetdConnector( 94): RCV <- {213 de:ad:be:ef:00:00 0.0.0.0 0 [down
broadcast multicast]}
D/NetdConnector( 94): RCV <- {200 Interface configuration set}
D/NetdConnector( 94): RCV <- {200 IPv6 privacy extensions changed}
D/NetdConnector( 94): RCV <- {600 Iface linkstate wlan0 down}
D/NetdConnector( 94): RCV <- {600 Iface linkstate wlan0 down}
D/NetdConnector( 94): RCV <- {600 Iface linkstate wlan0 down}



Regards
Sandeep S.P

Alvin Wong

unread,
Feb 7, 2012, 6:36:06 AM2/7/12
to android-porting
Hi there,

How about checking `ifconfig wlan0` or getting tools like `iwconfig`?
Have you also checked `dmesg` (alternatively `cat /proc/kmsg`) for any
extra kernel messages?

Is it fine if you manually `insmod` the WiFi module? Or is the driver
working normally? If you have a standard Linux distribution, you may
want to check whether WiFi is really working in the kernel level
before enabling in Linux.

Or perhaps your interface is eth0 instead of wlan0? (Though the
possibility is low)

Good luck,
Alvin Wong

Sandeep sp

unread,
Feb 10, 2012, 4:24:08 AM2/10/12
to android-porting
Hi Alvin,

Now, i am able to bring up the WI-FI on the board.

The previous error was of that it's not able to get the MACADDR ,
to resolve that error i applied the patch from this location.
(Basically it's not able to scan the networks around)

https://gitorious.org/picopc-android-gingerbread/external-wpa_supplicant_6/commit/5f5c50d722eedaedd75c1698b79f464310ce6478?format=patch

After that WI-FI driver is able to scan and with DHCPD it's able to
get the IP address along with that it's able to connect through other
networks also.

Thanks for the Suggestions.

Regards
Sandeep S.P

On Feb 7, 4:36 pm, Alvin Wong <alvinhoc...@gmail.com> wrote:
> Hi there,
>
> How about checking `ifconfig wlan0` or getting tools like `iwconfig`?
> Have you also checked `dmesg` (alternatively `cat /proc/kmsg`) for any
> extra kernel messages?
>
> Is it fine if you manually `insmod` theWiFimodule? Or is thedriver
> working normally? If you have a standard Linux distribution, you may
> want to check whetherWiFiis really working in the kernel level
> before enabling in Linux.
>
> Or perhaps your interface is eth0 instead of wlan0? (Though the
> possibility is low)
>
> Good luck,
> Alvin Wong
>
> On 2月6日, 上午11時18分, Sandeep sp <sandeep.palaksha...@wipro.com> wrote:
>
>
>
>
>
>
>
> > Hi
>
> >     I has been trying to set up the Wi-Fi on our board.
> >     The configuration options which i had chosen are Android Private
> > socket andWIFIdrivers are loaded as Kernel modules. It's able to
> > properly load the Wi-Fidriverand firmware also.

Ranganath TM

unread,
May 22, 2012, 4:47:36 AM5/22/12
to android...@googlegroups.com
Hi Sandeep,

I am also facing the same issue,

can you give some more information to solve the issue.

Thanks,
Ranga 
Reply all
Reply to author
Forward
0 new messages