On Mon, 2009-05-18 at 00:15 -0700, Stephen Rothwell wrote: > Add cc's > > On Fri, 15 May 2009 12:26:21 +0200 Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx> wrote: > > > > Kernel is not authenticating it against the AP anymore with > > messages like: > > > > [16907.701634] wlan0: associate with AP 00:03:52:4e:f3:d1 > > [16907.703669] wlan0: RX AssocResp from 00:03:52:4e:f3:d1 (capab=0x421 status=0 aid=5) > > [16907.703672] wlan0: associated > > [16907.729958] wlan0: disassociating by local choice (reason=3) This is usually printed when your user application (wpa_supplicant, network manager, etc.) goes down or disassociates. > > [16907.852112] wlan0: direct probe to AP 00:03:52:1b:f8:31 try 1 > > [16908.052086] wlan0: direct probe to AP 00:03:52:1b:f8:31 try 2 > > [16908.055331] wlan0 direct probe responded > > [16908.055335] wlan0: authenticate with AP 00:03:52:1b:f8:31 > > [16908.256065] wlan0: authenticate with AP 00:03:52:1b:f8:31 > > [16908.453689] wlan0: authenticate with AP 00:03:52:1b:f8:31 > > [16908.656037] wlan0: authentication with AP 00:03:52:1b:f8:31 timed out Don't know what is going on here. Could your AP be out of reach or not responding? > > > > Also wpa_supplicant is not happy: > > > > + wpa_supplicant -B -Dwext -iwlan0 -c /home/user/nico/ethz/wlan/wpa_supplicant.conf > > ioctl[SIOCSIWENCODEEXT]: No such file or directory > > ioctl[SIOCSIWENCODEEXT]: No such file or directory > > ioctl[SIOCSIWENCODEEXT]: No such file or directory > > ioctl[SIOCSIWENCODEEXT]: No such file or directory > > There were some changes recently to this ioctl, but I am not familiar with details. Johannes will know. Reinette -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
