Overo Fire WiFi random behaviour - ifconfig -a detects wlan0:avahi and doesnt work

[Elvis Dowson]

Hi,

My WiFi doesn't work when for some reason if at, boot up , the system detects and configures wlan0:avahi.  I'm using the Overo Fire WiFi, with the latest kernel build from last week. 

Here is the output of the ifconfig -a command, showing wlan0:avahi detect. WiFi doesn't work and I have no ip address allocated to wlan0.

wlan0     Link encap:Ethernet  HWaddr 00:19:88:10:F9:9C  

          inet6 addr: fe80::219:88ff:fe10:f99c/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:4 errors:0 dropped:0 overruns:0 frame:0

          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:410 (410.0 b)  TX bytes:2168 (2.1 KiB)

wlan0:avahi Link encap:Ethernet  HWaddr 00:19:88:10:F9:9C  

          inet addr:169.254.9.74  Bcast:169.254.255.255  Mask:255.255.0.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

Now, if I reboot and somehow the system doesn't detect that wlan0:avahi, the ip address gets assigned and I am able to ping. 

Here is the output of the ifconfig -a command:

wlan0     Link encap:Ethernet  HWaddr 00:19:88:10:F9:9C  

          inet addr:87.201.169.254  Bcast:87.201.169.255  Mask:255.255.255.0

          inet6 addr: fe80::219:88ff:fe10:f99c/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:9 errors:0 dropped:0 overruns:0 frame:0

          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:2161 (2.1 KiB)  TX bytes:2530 (2.4 KiB)

root@overo:~# ping www.google.com

PING www.google.com (209.85.229.99): 56 data bytes

64 bytes from 209.85.229.99: seq=0 ttl=238 time=163.269 ms

Anybody else notice this behaviour? 

Best regards,

Elvis

------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

[sonu2die4]

Hi Elvis,
i have the same problem at  my end . It will be great if some one helped us oh this concern.

/Vivek

Elvis Dowson wrote:

Hi,
        My WiFi doesn't work when for some reason if at, boot up , the system  
detects and configures wlan0:avahi.  I'm using the Overo Fire WiFi,  
with the latest kernel build from last week.

Here is the output of the ifconfig -a command, showing wlan0:avahi  
detect. WiFi doesn't work and I have no ip address allocated to wlan0.

wlan0     Link encap:Ethernet  HWaddr 00:19:88:10:F9:9C
           inet6 addr: fe80::219:88ff:fe10:f99c/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:4 errors:0 dropped:0 overruns:0 frame:0
           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:410 (410.0 b)  TX bytes:2168 (2.1 KiB)

wlan0:avahi Link encap:Ethernet  HWaddr 00:19:88:10:F9:9C
           inet addr:169.254.9.74  Bcast:169.254.255.255  Mask:
255.255.0.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1


Now, if I reboot and somehow the system doesn't detect that  
wlan0:avahi, the ip address gets assigned and I am able to ping.

Here is the output of the ifconfig -a command:

wlan0     Link encap:Ethernet  HWaddr 00:19:88:10:F9:9C
           inet addr:87.201.169.254  Bcast:87.201.169.255  Mask:
255.255.255.0
           inet6 addr: fe80::219:88ff:fe10:f99c/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:9 errors:0 dropped:0 overruns:0 frame:0
           TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:2161 (2.1 KiB)  TX bytes:2530 (2.4 KiB)

root@overo:~# ping www.google.com
PING www.google.com (209.85.229.99): 56 data bytes
64 bytes from 209.85.229.99: seq=0 ttl=238 time=163.269 ms


Anybody else notice this behaviour?

Best regards,

Elvis





------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
gumstix-users mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/gumstix-users

[davidvondle]

I'm running into the same problem or a similar one.  

The Overo Fire will not connect to an access point or act as an access point.  When I try iwconfig I get:

IEEE 802.11b/g ESSID:""
Mode: Managed Frequency:2.412 Ghz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-power=13 dBm
Retry short limit:8 RTS thr=2347 B  Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:7382 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:55335 Misses beacon:0

If I try to set up the ESSID through iwconfig, it doesn't take and shows ESSID:"" or doesn't show an essid at all.  Sometimes I have noticed that is will connect for a few seconds, then revert back to the above setup

Anyone have WiFi working on their Overo Fire that can share how they set theirs up?  It was working out of the box, but after loading the new image on it, I'm running into these problems.

Thanks,
Dave

[sparks333]

davidvondle wrote:

I'm running into the same problem or a similar one.  

The Overo Fire will not connect to an access point or act as an access point.  When I try iwconfig I get:

IEEE 802.11b/g ESSID:""
Mode: Managed Frequency:2.412 Ghz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-power=13 dBm
Retry short limit:8 RTS thr=2347 B  Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:7382 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:55335 Misses beacon:0

If I try to set up the ESSID through iwconfig, it doesn't take and shows ESSID:"" or doesn't show an essid at all.  Sometimes I have noticed that is will connect for a few seconds, then revert back to the above setup

Anyone have WiFi working on their Overo Fire that can share how they set theirs up?  It was working out of the box, but after loading the new image on it, I'm running into these problems.

Thanks,
Dave

It sounds a bit like the automated configuration didn't work right - I ran into this issue a while ago.
Try ifup wlan0 - if it says that the connection is already configured, then ifdown wlan0 then ifup wlan0. Check to see if there are any errors when you attempt to connect. This is all assuming that you're using an unsecured wireless signal - if you're using WPA, WPA2 or WEP, you'll need to configure wpa_supplicant as according to this tutorial:
http://www.gumstix.net/wiki/index.php?title=Overo_Wifi

Good luck

Sparks

[davidvondle]

I'm running into the same problem or a similar one.  

The Overo Fire will not connect to an access point or act as an access point.  When I try iwconfig I get:

IEEE 802.11b/g ESSID:""
Mode: Managed Frequency:2.412 Ghz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-power=13 dBm
Retry short limit:8 RTS thr=2347 B  Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:7382 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:55335 Misses beacon:0

If I try to set up the ESSID through iwconfig, it doesn't take and shows ESSID:"" or doesn't show an essid at all.  Sometimes I have noticed that is will connect for a few seconds, then revert back to the above setup

Anyone have WiFi working on their Overo Fire that can share how they set theirs up?  It was working out of the box, but after loading the new image on it, I'm running into these problems.

Thanks,
Dave

[sparks333]

davidvondle wrote:

I'm running into the same problem or a similar one.  

The Overo Fire will not connect to an access point or act as an access point.  When I try iwconfig I get:

IEEE 802.11b/g ESSID:""
Mode: Managed Frequency:2.412 Ghz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-power=13 dBm
Retry short limit:8 RTS thr=2347 B  Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:7382 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:55335 Misses beacon:0

If I try to set up the ESSID through iwconfig, it doesn't take and shows ESSID:"" or doesn't show an essid at all.  Sometimes I have noticed that is will connect for a few seconds, then revert back to the above setup

Anyone have WiFi working on their Overo Fire that can share how they set theirs up?  It was working out of the box, but after loading the new image on it, I'm running into these problems.

Thanks,
Dave

It sounds a bit like the automated configuration didn't work right - I ran into this issue a while ago.
Try ifup wlan0 - if it says that the connection is already configured, then ifdown wlan0 then ifup wlan0. Check to see if there are any errors when you attempt to connect. This is all assuming that you're using an unsecured wireless signal - if you're using WPA, WPA2 or WEP, you'll need to configure wpa_supplicant as according to this tutorial:
http://www.gumstix.net/wiki/index.php?title=Overo_Wifi

Good luck

Sparks

[davidvondle]

I'm running into the same problem or a similar one.  

The Overo Fire will not connect to an access point or act as an access point.  When I try iwconfig I get:

IEEE 802.11b/g ESSID:""
Mode: Managed Frequency:2.412 Ghz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-power=13 dBm
Retry short limit:8 RTS thr=2347 B  Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:7382 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:55335 Misses beacon:0

If I try to set up the ESSID through iwconfig, it doesn't take and shows ESSID:"" or doesn't show an essid at all.  Sometimes I have noticed that is will connect for a few seconds, then revert back to the above setup

Anyone have WiFi working on their Overo Fire that can share how they set theirs up?  It was working out of the box, but after loading the new image on it, I'm running into these problems.

Thanks,
Dave

[davidvondle]

I'm running into the same problem or a similar one.  

The Overo Fire will not connect to an access point or act as an access point.  When I try iwconfig I get:

IEEE 802.11b/g ESSID:""
Mode: Managed Frequency:2.412 Ghz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-power=13 dBm
Retry short limit:8 RTS thr=2347 B  Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:7382 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:55335 Misses beacon:0

If I try to set up the ESSID through iwconfig, it doesn't take and shows ESSID:"" or doesn't show an essid at all.  Sometimes I have noticed that is will connect for a few seconds, then revert back to the above setup

Anyone have WiFi working on their Overo Fire that can share how they set theirs up?  It was working out of the box, but after loading the new image on it, I'm running into these problems.

Thanks,
Dave

[Dirk Behme-2]

davidvondle wrote:

> I'm running into the same problem or a similar one.  
>
> The Overo Fire will not connect to an access point or act as an access
> point.  When I try iwconfig I get:
>
> IEEE 802.11b/g ESSID:""
> Mode: Managed Frequency:2.412 Ghz Access Point: Not-Associated
> Bit Rate:0 kb/s Tx-power=13 dBm
> Retry short limit:8 RTS thr=2347 B  Fragment thr=2346 B
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:7382 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:55335 Misses beacon:0
>
> If I try to set up the ESSID through iwconfig, it doesn't take and shows
> ESSID:"" or doesn't show an essid at all.  Sometimes I have noticed that is
> will connect for a few seconds, then revert back to the above setup
>
> Anyone have WiFi working on their Overo Fire that can share how they set
> theirs up?  It was working out of the box, but after loading the new image
> on it, I'm running into these problems.

I can't get it to work, too :(

ifup wlan0 results in

wlan0     Link encap:Ethernet  HWaddr 00:19:88:20:FA:20
           UP BROADCAST MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0:avahi Link encap:Ethernet  HWaddr 00:19:88:20:FA:20
           inet addr:169.254.7.18  Bcast:169.254.255.255  Mask:255.255.0.0
           UP BROADCAST MULTICAST  MTU:1500  Metric:1

udhcpc fails with this, then.

iwconfig reports

wlan0     IEEE 802.11b/g  ESSID:""
           Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
           Bit Rate:0 kb/s   Tx-Power=16 dBm
           Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B
           Encryption key:off
           Power Management:off
           Link Quality:0  Signal level:0  Noise level:0
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

And yes, I remember with older images I had it already working.
Currently I'm using omap3-desktop-image-overo-200910121635

Best regards

Dirk

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

[Dirk Behme-2]

Dirk Behme wrote:

> davidvondle wrote:
>> I'm running into the same problem or a similar one.
>> The Overo Fire will not connect to an access point or act as an access
>> point.  When I try iwconfig I get:
>>
>> IEEE 802.11b/g ESSID:""
>> Mode: Managed Frequency:2.412 Ghz Access Point: Not-Associated
>> Bit Rate:0 kb/s Tx-power=13 dBm
>> Retry short limit:8 RTS thr=2347 B  Fragment thr=2346 B
>> Encryption key:off
>> Power Management:off
>> Link Quality:0 Signal level:0 Noise level:0
>> Rx invalid nwid:0 Rx invalid crypt:7382 Rx invalid frag:0
>> Tx excessive retries:0 Invalid misc:55335 Misses beacon:0
>>
>> If I try to set up the ESSID through iwconfig, it doesn't take and shows
>> ESSID:"" or doesn't show an essid at all.  Sometimes I have noticed
>> that is
>> will connect for a few seconds, then revert back to the above setup
>>
>> Anyone have WiFi working on their Overo Fire that can share how they set
>> theirs up?  It was working out of the box, but after loading the new
>> image
>> on it, I'm running into these problems.
>
> I can't get it to work, too :(
>
> ifup wlan0 results in
>
> wlan0     Link encap:Ethernet  HWaddr 00:19:88:20:FA:20
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> wlan0:avahi Link encap:Ethernet  HWaddr 00:19:88:20:FA:20
>           inet addr:169.254.7.18  Bcast:169.254.255.255  Mask:255.255.0.0
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>
> udhcpc fails with this, then.
>
> iwconfig reports
>
> wlan0     IEEE 802.11b/g  ESSID:""
>           Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
>           Bit Rate:0 kb/s   Tx-Power=16 dBm
>           Retry short limit:8   RTS thr=2347 B   Fragment thr=2346 B
>           Encryption key:off
>           Power Management:off
>           Link Quality:0  Signal level:0  Noise level:0
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
> And yes, I remember with older images I had it already working.
> Currently I'm using omap3-desktop-image-overo-200910121635

With help of hostap mailing list I'm currently looking into this:

At the moment it seems that wpa_supplicant v0.6.9 is doing something
strange (timeout too short?):

http://lists.shmoo.com/pipermail/hostap/2009-November/020564.html

See complete thread, too.

Is anybody with OE able to quickly recompile wpa_supplicant v0.6.9 with

http://cvs.fedoraproject.org/viewvc/F-12/wpa_supplicant/wpa_supplicant-assoc-timeout.patch?view=markup

?

And just in case somebody has an (older?) kernel and rootfs running on
Overo where WPA2 is working, would be nice to get a hint which version
(still?) does work.

Many thanks and best regards

Dirk

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

[colinfp]

Has there been any solution found to this problem?  I just set up the 11/29 distribuion of the desktop-nand and am having the same troubles.  Thanks!

Colin