在arm embedded-linux上的tiwi-r2 wl1271上安装软点:身份验证超时

Question

我有一个嵌入式的arm linux设备正在运行。

kernel 2.6.39.4 
hostapd 2.0
wl1271 and wl1271_sdio modules loaded (no compat drivers)

这个设备是一个TI的TiWi-R2模块。Adhoc和Infrastructure模式可以工作，但当我尝试设置软抽头时，会遇到问题:通过将hostapd.conf的内容设置为：

interface=wlan0
driver=nl80211
channel=1
hw_mode=g
ssid=mya

正在引导的固件：

[ 6486.330000] wl1271: wlan power up
[ 6486.660000] booting firmware ti-connectivity/wl1271-fw-ap.bin
[ 6486.810000] wl1271: firmware booted (Rev 6.2.1.0.54)

SSID正在广播，其他设备可以看到它，但不能关联。在Ubuntu笔记本电脑上，在尝试连接失败后，我从dmesg获得以下信息：

[  548.289020] wlan0: authenticate with 00:xx:yy:zz:ww:qq
[  548.300588] wlan0: send auth to 00:xx:yy:zz:ww:qq (try 1/3)
[  548.504059] wlan0: send auth to 00:xx:yy:zz:ww:qq (try 2/3)
[  548.708059] wlan0: send auth to 00:xx:yy:zz:ww:qq (try 3/3)
[  548.912056] wlan0: authentication with 00:xx:yy:zz:ww:qq timed out

在关联失败后，该膝上型计算机连接到另一个先前配置的访问点。使用嵌入式设备上的-dd选项启动hostapd，我可以获得一些调试消息，但我不太了解它们。这是笔记本电脑连接时主机端的输出：

wlan0: Event RX_MGMT (20) received
mgmt::auth
authentication: STA=aa:bb:cc:dd:ee:ff auth_alg=0 auth_transaction=1 status_code=0 wep=0
  New STA
ap_sta_add: register ap_handle_timer timeout for aa:bb:cc:dd:ee:ff (300 seconds - ap_max_inactivity)
wlan0: STA aa:bb:cc:dd:ee:ff IEEE 802.11: authentication OK (open system)
wlan0: STA aa:bb:cc:dd:ee:ff MLME: MLME-AUTHENTICATE.indication(aa:bb:cc:dd:ee:ff, OPEN_SYSTEM)
wlan0: STA aa:bb:cc:dd:ee:ff MLME: MLME-DELETEKEYS.request(aa:bb:cc:dd:ee:ff)
authentication reply: STA=aa:bb:cc:dd:ee:ff auth_alg=0 auth_transaction=2 resp=0 (IE len=0)
wlan0: Event RX_MGMT (20) received
mgmt::auth
authentication: STA=aa:bb:cc:dd:ee:ff auth_alg=0 auth_transaction=1 status_code=0 wep=0
wlan0: STA aa:bb:cc:dd:ee:ff IEEE 802.11: authentication OK (open system)
wlan0: STA aa:bb:cc:dd:ee:ff MLME: MLME-AUTHENTICATE.indication(aa:bb:cc:dd:ee:ff, OPEN_SYSTEM)
wlan0: STA aa:bb:cc:dd:ee:ff MLME: MLME-DELETEKEYS.request(aa:bb:cc:dd:ee:ff)
authentication reply: STA=aa:bb:cc:dd:ee:ff auth_alg=0 auth_transaction=2 resp=0 (IE len=0)
wlan0: Event RX_MGMT (20) received
mgmt::auth
authentication: STA=aa:bb:cc:dd:ee:ff auth_alg=0 auth_transaction=1 status_code=0 wep=0
wlan0: STA aa:bb:cc:dd:ee:ff IEEE 802.11: authentication OK (open system)
wlan0: STA aa:bb:cc:dd:ee:ff MLME: MLME-AUTHENTICATE.indication(aa:bb:cc:dd:ee:ff, OPEN_SYSTEM)
wlan0: STA aa:bb:cc:dd:ee:ff MLME: MLME-DELETEKEYS.request(aa:bb:cc:dd:ee:ff)
authentication reply: STA=aa:bb:cc:dd:ee:ff auth_alg=0 auth_transaction=2 resp=0 (IE len=0)

过了一段时间，系统似乎因为不活动而使笔记本电脑脱离了联系：

ap_handle_timer: aa:bb:cc:dd:ee:ff flags=0x1 timeout_next=0
wlan0: Timeout, sending disassociation info to STA aa:bb:cc:dd:ee:ff
ap_handle_timer: register ap_handle_timer timeout for aa:bb:cc:dd:ee:ff (1 seconds - AP_DISASSOC_DELAY)
ap_handle_timer: aa:bb:cc:dd:ee:ff flags=0x1 timeout_next=1
wlan0: Timeout, sending disassociation info to STA aa:bb:cc:dd:ee:ff
wlan0: STA aa:bb:cc:dd:ee:ff IEEE 802.11: disassociated due to inactivity
ap_handle_timer: register ap_handle_timer timeout for aa:bb:cc:dd:ee:ff (1 seconds - AP_DEAUTH_DELAY)
wlan0: STA aa:bb:cc:dd:ee:ff MLME: MLME-DISASSOCIATE.indication(aa:bb:cc:dd:ee:ff, 4)
wlan0: STA aa:bb:cc:dd:ee:ff MLME: MLME-DELETEKEYS.request(aa:bb:cc:dd:ee:ff)
ap_handle_timer: aa:bb:cc:dd:ee:ff flags=0x1 timeout_next=2
wlan0: Timeout, sending deauthentication info to STA aa:bb:cc:dd:ee:ff
wlan0: STA aa:bb:cc:dd:ee:ff IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
wlan0: STA aa:bb:cc:dd:ee:ff MLME: MLME-DEAUTHENTICATE.indication(aa:bb:cc:dd:ee:ff, 2)
wlan0: STA aa:bb:cc:dd:ee:ff MLME: MLME-DELETEKEYS.request(aa:bb:cc:dd:ee:ff)
ap_free_sta: cancel ap_handle_timer for aa:bb:cc:dd:ee:ff

我在布奇拉中看到了类似的帖子，但这篇文章很老，属于wpa_supplicant (版本0.6.0)，笔记本电脑上有Ubuntu13.04和wpa_supplicant 1.0。这让我认为hostapd并没有通知客户机关联是成功的。

我也不能连接到任何其他设备的软开关。我尝试了Android4.4和iOS 7.0.4

我还尝试了wpa2配置和标准的开放来自TI的配置文件，但是没有任何效果。

编辑：我不知道我会把整个社区都搞砸.我已经升级到TiWi模块，这是TiWi-R2的官方继承者，但是没有得到任何进展。

我发现了一个同样的问题，但没有一个解决方案的这里。

编辑：我通过使用内核3.12.0解决了这个问题，这里没有出现这个问题。在我看来，问题就在内核上。我会暂时不回答这个问题，以防有人看到它。

Answer 1

我换了一个更新的内核。当时它是3.13.0-next，一个没有正式发布版本的内核，但是由于它工作得很好，所以我就把它保存在这个位置上。