Messages in this thread | | | Date | Tue, 07 Apr 2009 12:29:27 +0200 | From | "Markus Koßmann" <> | Subject | Re: 2.6.29+ ath5k connect disconnect cycles? |
| |
> On Mon, 2009-04-06 at 21:55 +0200, Tulio Magno Quites Machado Filho > wrote: > > On Apr 06 09 10:55, Soeren Sonnenburg wrote: > > > does anyone else observer strange connect disconnect cycles with > ath5k? > > > I have two different notebooks here one with an AR5414 and one with > some > > > 2424 (?) chipset both having the same problems to connect... > > > > Hello Soeren, > > > > Is there any information from dmesg? > > I am seeing cycles of > > airport: deauthenticated (Reason: 2) > airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1 > airport direct probe responded > airport: authenticate with AP XX:XX:XX:XX:XX:XX > airport: authenticated > airport: associate with AP XX:XX:XX:XX:XX:XX > airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0 > aid=79) > airport: associated > airport: deauthenticated (Reason: 2) > airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1 > airport direct probe responded > airport: authenticate with AP XX:XX:XX:XX:XX:XX > airport: authenticated > airport: associate with AP XX:XX:XX:XX:XX:XX > airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0 > aid=81) > airport: associated > airport: deauthenticated (Reason: 2) > airport: direct probe to AP XX:XX:XX:XX:XX:XX try 1 > airport direct probe responded > airport: authenticate with AP XX:XX:XX:XX:XX:XX > airport: authenticated > airport: associate with AP XX:XX:XX:XX:XX:XX > airport: RX ReassocResp from XX:XX:XX:XX:XX:XX (capab=0x421 status=0 > aid=82) > airport: associated > airport: deauthenticated (Reason: 2) > ... > > Not sure about the involvement of network-manager here... but I see that > the device gets a valid IP via dhcp. > I've seen such cycles also with intel ipw5300 WLAN and using ifconfig to start the network. To get WLAN working again, I have to ifdown wlan0 , unload and reload the driver module and finally ifup wlan0. So it's probably neither a ath5k nor a network-manager problem.
| |