wl127x: Unable to associate with a WPA2-PSK AP
Hi,
After solving some initial platform issues, I'm now blocked in two more issues using the wl127x driver with kernel 3.9.9 in a S3C2416 hardware based platform.
The first one is that the command "iw wlan0 scan" does not scan all frequencies. I've seen a patch submitted to fix an issue in the driver for the 5 GHz band (http://permalink.gmane.org/gmane.linux.kernel.wireless.general/107771) but this is not my issue, because I can not see also several APs in the 2.4GHz band after a scan.
The second issue is when I try to associate with an AP using WPA2-PSK with wpa_supplicant (only able to reach this point by setting "scan_freq" in wpa_supplicat.conf file to the frequency used by the AP, because of the inability to perform of a complete scan) I get an error in the driver, as shown in the log bellow:
[root ~]$ wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf Successfully initialized wpa_supplicant
[ 33.915000] wlcore: firmware booted (Rev 6.3.10.0.133) [ 34.280000] cfg80211: Calling CRDA for country: PT [ 34.290000] cfg80211: Regulatory domain changed to country: PT [ 34.290000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 34.305000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 34.320000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 34.320000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 34.330000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 34.340000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[ 34.585000] wlan0: authenticate with 88:43:e1:57:79:c0 A. Guidance' freq=2452 MHz) [ 34.595000] ------------[ cut here ]------------ [ 34.595000] WARNING: at drivers/net/wireless/ti/wlcore/tx.c:1307 wlcore_is_queue_stopped_by_reason_locked+0x98/0xb4 [wlcore]() [ 34.595000] Modules linked in: arc4 wl12xx wlcore mac80211 wlcore_sdio lm70 [ 34.595000] Backtrace: [ 34.595000] [<c000b92c>] (dump_backtrace+0x0/0x10c) from [<c02ed4a4>] (dump_stack+0x18/0x1c) [ 34.595000] r6:bf05ddd8 r5:00000009 r4:00000000 r3:00000000 [ 34.595000] [<c02ed48c>] (dump_stack+0x0/0x1c) from [<c0019ecc>] (warn_slowpath_common+0x54/0x70) [ 34.595000] [<c0019e78>] (warn_slowpath_common+0x0/0x70) from [<c0019f0c>] (warn_slowpath_null+0x24/0x2c) [ 34.595000] r8:c39e2acc r7:00000000 r6:c305b160 r5:bf06ca36 r4:00000002 r3:00000009 [ 34.595000] [<c0019ee8>] (warn_slowpath_null+0x0/0x2c) from [<bf05ddd8>] (wlcore_is_queue_stopped_by_reason_locked+0x98/0xb4 [wlcore]) [ 34.595000] [<bf05dd40>] (wlcore_is_queue_stopped_by_reason_locked+0x0/0xb4 [wlcore]) from [<bf05de38>] (wlcore_is_queue_stopped_by_reason+0x44/0x7c [wlcore]) [ 34.595000] r6:00000000 r5:c305b160 r4:80000013 [ 34.595000] [<bf05ddf4>] (wlcore_is_queue_stopped_by_reason+0x0/0x7c [wlcore]) from [<bf05deb4>] (wl1271_handle_tx_low_watermark+0x44/0x94 [wlcore]) [ 34.595000] r8:c305b160 r7:c39e2acc r6:00000000 r5:c39e2acc r4:00000000 r3:00000000 [ 34.595000] [<bf05de70>] (wl1271_handle_tx_low_watermark+0x0/0x94 [wlcore]) from [<bf05e050>] (wl1271_tx_reset_link_queues+0x14c/0x174 [wlcore]) [ 34.595000] [<bf05df04>] (wl1271_tx_reset_link_queues+0x0/0x174 [wlcore]) from [<bf05970c>] (wl12xx_free_link+0xec/0x150 [wlcore]) [ 34.595000] [<bf059620>] (wl12xx_free_link+0x0/0x150 [wlcore]) from [<bf059b50>] (wl12xx_cmd_role_stop_sta+0x98/0x100 [wlcore]) [ 34.595000] r7:c305b160 r6:00000000 r5:c39e2acc r4:c3a89ac0 [ 34.595000] [<bf059ab8>] (wl12xx_cmd_role_stop_sta+0x0/0x100 [wlcore]) from [<bf0546d8>] (wl1271_bss_info_changed_sta+0x840/0x9a4 [wlcore]) [ 34.595000] r7:c39e2acc r6:c305b160 r5:c39e2a10 r4:000000e0 [ 34.595000] [<bf053e98>] (wl1271_bss_info_changed_sta+0x0/0x9a4 [wlcore]) from [<bf054a0c>] (wl1271_op_bss_info_changed+0x1d0/0x46c [wlcore]) [ 34.595000] [<bf05483c>] (wl1271_op_bss_info_changed+0x0/0x46c [wlcore]) from [<bf009538>] (ieee80211_bss_info_change_notify+0x6c/0x10c [mac80211]) [ 34.595000] [<bf0094cc>] (ieee80211_bss_info_change_notify+0x0/0x10c [mac80211]) from [<bf02bf1c>] (ieee80211_prep_connection+0x2dc/0x76c [mac80211]) [ 34.595000] r7:00000fff r6:c39cfe48 r5:c305b8e4 r4:c39e2440 [ 34.595000] [<bf02bc40>] (ieee80211_prep_connection+0x0/0x76c [mac80211]) from [<bf030d70>] (ieee80211_mgd_auth+0x228/0x29c [mac80211]) [ 34.595000] [<bf030b48>] (ieee80211_mgd_auth+0x0/0x29c [mac80211]) from [<bf01afd4>] (ieee80211_auth+0x18/0x1c [mac80211]) [ 34.595000] [<bf01afbc>] (ieee80211_auth+0x0/0x1c [mac80211]) from [<c02e40a8>] (__cfg80211_mlme_auth+0x170/0x188) [ 34.595000] [<c02e3f38>] (__cfg80211_mlme_auth+0x0/0x188) from [<c02e4154>] (cfg80211_mlme_auth+0x94/0xb8) [ 34.595000] [<c02e40c0>] (cfg80211_mlme_auth+0x0/0xb8) from [<c02dffbc>] (nl80211_authenticate+0x258/0x27c) [ 34.595000] [<c02dfd64>] (nl80211_authenticate+0x0/0x27c) from [<c0260044>] (genl_rcv_msg+0x23c/0x274) [ 34.595000] [<c025fe08>] (genl_rcv_msg+0x0/0x274) from [<c025f458>] (netlink_rcv_skb+0xb4/0xc8) [ 34.595000] [<c025f3a4>] (netlink_rcv_skb+0x0/0xc8) from [<c025fdfc>] (genl_rcv+0x20/0x2c) [ 34.595000] r6:00000048 r5:c3a5b400 r4:c38c4bc0 r3:c025fddc [ 34.595000] [<c025fddc>] (genl_rcv+0x0/0x2c) from [<c025ee40>] (netlink_unicast+0x1b0/0x214) [ 34.595000] r4:c38c5e00 r3:c025fddc [ 34.595000] [<c025ec90>] (netlink_unicast+0x0/0x214) from [<c025f230>] (netlink_sendmsg+0x2e0/0x358) [ 34.595000] [<c025ef50>] (netlink_sendmsg+0x0/0x358) from [<c0230944>] (sock_sendmsg+0x88/0xa8) [ 34.595000] [<c02308bc>] (sock_sendmsg+0x0/0xa8) from [<c0230d64>] (___sys_sendmsg+0x2c8/0x2e0) [ 34.595000] [<c0230a9c>] (___sys_sendmsg+0x0/0x2e0) from [<c0232920>] (__sys_sendmsg+0x44/0x70) [ 34.595000] [<c02328dc>] (__sys_sendmsg+0x0/0x70) from [<c023295c>] (sys_sendmsg+0x10/0x14) [ 34.595000] r6:be94fa8c r5:017940a0 r4:00000000 [ 34.595000] [<c023294c>] (sys_sendmsg+0x0/0x14) from [<c0009400>] (ret_fast_syscall+0x0/0x2c) [ 34.595000] ---[ end trace a2c5f3d5ef286154 ]--- [ 34.605000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3) [ 34.605000] ------------[ cut here ]------------ [ 34.605000] WARNING: at drivers/net/wireless/ti/wlcore/tx.c:1316 wlcore_is_queue_stopped_locked+0x74/0x8c [wlcore]() [ 34.605000] Modules linked in: arc4 wl12xx wlcore mac80211 wlcore_sdio lm70 [ 34.605000] Backtrace: [ 34.605000] [<c000b92c>] (dump_backtrace+0x0/0x10c) from [<c02ed4a4>] (dump_stack+0x18/0x1c) [ 34.605000] r6:bf05f240 r5:00000009 r4:00000000 r3:00000000 [ 34.605000] [<c02ed48c>] (dump_stack+0x0/0x1c) from [<c0019ecc>] (warn_slowpath_common+0x54/0x70) [ 34.605000] [<c0019e78>] (warn_slowpath_common+0x0/0x70) from [<c0019f0c>] (warn_slowpath_null+0x24/0x2c) [ 34.605000] r8:40000013 r7:c305b160 r6:c305b160 r5:bf06ca36 r4:00000000 r3:00000009 [ 34.605000] [<c0019ee8>] (warn_slowpath_null+0x0/0x2c) from [<bf05f240>] (wlcore_is_queue_stopped_locked+0x74/0x8c [wlcore]) [ 34.605000] [<bf05f1cc>] (wlcore_is_queue_stopped_locked+0x0/0x8c [wlcore]) from [<bf05225c>] (wl1271_op_tx+0x104/0x290 [wlcore]) [ 34.605000] r6:c39e2a10 r5:00000001 r4:c38c4a40 r3:00000003 [ 34.605000] [<bf052158>] (wl1271_op_tx+0x0/0x290 [wlcore]) from [<bf023e64>] (__ieee80211_tx+0x134/0x384 [mac80211]) [ 34.605000] [<bf023d30>] (__ieee80211_tx+0x0/0x384 [mac80211]) from [<bf024174>] (ieee80211_tx+0xc0/0xe8 [mac80211]) [ 34.605000] [<bf0240b4>] (ieee80211_tx+0x0/0xe8 [mac80211]) from [<bf02474c>] (ieee80211_xmit+0x80/0x94 [mac80211]) [ 34.605000] [<bf0246cc>] (ieee80211_xmit+0x0/0x94 [mac80211]) from [<bf025698>] (__ieee80211_tx_skb_tid_band+0x58/0x64 [mac80211]) [ 34.605000] r8:00000000 r7:00000001 r6:00000000 r5:c39e2440 r4:c38c4a40 r3:c3ae8000 [ 34.605000] [<bf025640>] (__ieee80211_tx_skb_tid_band+0x0/0x64 [mac80211]) from [<bf0286c4>] (ieee80211_send_auth+0x158/0x1e0 [mac80211]) [ 34.605000] r6:c39e2440 r5:c38c4a40 r4:c3ac8b94 r3:00000000 [ 34.605000] [<bf02856c>] (ieee80211_send_auth+0x0/0x1e0 [mac80211]) from [<bf02c550>] (ieee80211_probe_auth+0x174/0x2c8 [mac80211]) [ 34.605000] [<bf02c3dc>] (ieee80211_probe_auth+0x0/0x2c8 [mac80211]) from [<bf030d80>] (ieee80211_mgd_auth+0x238/0x29c [mac80211]) [ 34.605000] r8:c39e2798 r7:00000000 r6:c39e2440 r5:c3a72c20 r4:c3ae9af8 [ 34.605000] [<bf030b48>] (ieee80211_mgd_auth+0x0/0x29c [mac80211]) from [<bf01afd4>] (ieee80211_auth+0x18/0x1c [mac80211]) [ 34.605000] [<bf01afbc>] (ieee80211_auth+0x0/0x1c [mac80211]) from [<c02e40a8>] (__cfg80211_mlme_auth+0x170/0x188) [ 34.605000] [<c02e3f38>] (__cfg80211_mlme_auth+0x0/0x188) from [<c02e4154>] (cfg80211_mlme_auth+0x94/0xb8) [ 34.605000] [<c02e40c0>] (cfg80211_mlme_auth+0x0/0xb8) from [<c02dffbc>] (nl80211_authenticate+0x258/0x27c) [ 34.605000] [<c02dfd64>] (nl80211_authenticate+0x0/0x27c) from [<c0260044>] (genl_rcv_msg+0x23c/0x274) [ 34.605000] [<c025fe08>] (genl_rcv_msg+0x0/0x274) from [<c025f458>] (netlink_rcv_skb+0xb4/0xc8) [ 34.605000] [<c025f3a4>] (netlink_rcv_skb+0x0/0xc8) from [<c025fdfc>] (genl_rcv+0x20/0x2c) [ 34.605000] r6:00000048 r5:c3a5b400 r4:c38c4bc0 r3:c025fddc [ 34.605000] [<c025fddc>] (genl_rcv+0x0/0x2c) from [<c025ee40>] (netlink_unicast+0x1b0/0x214) [ 34.605000] r4:c38c5e00 r3:c025fddc [ 34.605000] [<c025ec90>] (netlink_unicast+0x0/0x214) from [<c025f230>] (netlink_sendmsg+0x2e0/0x358) [ 34.605000] [<c025ef50>] (netlink_sendmsg+0x0/0x358) from [<c0230944>] (sock_sendmsg+0x88/0xa8) [ 34.605000] [<c02308bc>] (sock_sendmsg+0x0/0xa8) from [<c0230d64>] (___sys_sendmsg+0x2c8/0x2e0) [ 34.605000] [<c0230a9c>] (___sys_sendmsg+0x0/0x2e0) from [<c0232920>] (__sys_sendmsg+0x44/0x70) [ 34.605000] [<c02328dc>] (__sys_sendmsg+0x0/0x70) from [<c023295c>] (sys_sendmsg+0x10/0x14) [ 34.605000] r6:be94fa8c r5:017940a0 r4:00000000 [ 34.605000] [<c023294c>] (sys_sendmsg+0x0/0x14) from [<c0009400>] (ret_fast_syscall+0x0/0x2c) [ 34.605000] ---[ end trace a2c5f3d5ef286155 ]--- [ 34.625000] wlan0: send auth to 88:43:e1:57:79:c0 (try 2/3) [ 34.640000] wlan0: send auth to 88:43:e1:57:79:c0 (try 3/3) [ 34.650000] wlan0: authentication with 88:43:e1:57:79:c0 timed out wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[ 34.875000] wlan0: authenticate with 88:43:e1:57:79:c0 A. Guidance' freq=2452 MHz) [ 34.915000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3) [ 34.920000] wlan0: authenticated wlan0: Trying to associate with 88:43:e1:57:79:c0 (SSID='A. Guidance' freq=2452 MHz) [ 34.995000] wlan0: associate with 88:43:e1:57:79:c0 (try 1/3) [ 35.015000] wlan0: associate with 88:43:e1:57:79:c0 (try 2/3) [ 35.035000] wlan0: associate with 88:43:e1:57:79:c0 (try 3/3) [ 35.060000] wlan0: association with 88:43:e1:57:79:c0 timed out wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[ 35.620000] wlan0: authenticate with 88:43:e1:57:79:c0 A. Guidance' freq=2452 MHz) [ 35.660000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3) [ 35.665000] wlan0: authenticated wlan0: Trying to associate with 88:43:e1:57:79:c0 (SSID='A. Guidance' freq=2452 MHz) [ 35.740000] wlan0: associate with 88:43:e1:57:79:c0 (try 1/3) [ 35.745000] wlan0: RX AssocResp from 88:43:e1:57:79:c0 (capab=0x431 status=0 aid=2) [ 35.765000] wlan0: associated [ 35.770000] cfg80211: Calling CRDA for country: PT [ 35.780000] cfg80211: Regulatory domain changed to country: PT [ 35.780000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 35.790000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 35.790000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 35.800000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 35.800000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 35.810000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) wlan0: Associated with 88:43:e1:57:79:c0 [ 37.585000] wlcore: Beacon loss detected. roles:0xff [ 39.250000] wlcore: Beacon loss detected. roles:0xff [ 40.935000] wlcore: Beacon loss detected. roles:0xff [ 42.400000] wlcore: Connection loss work (role_id: 0). [ 42.400000] wlan0: Connection to AP 88:43:e1:57:79:c0 lost [ 42.475000] cfg80211: Calling CRDA to update world regulatory domain [ 42.485000] cfg80211: World regulatory domain updated: [ 42.485000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 42.500000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.500000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.515000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 42.515000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.525000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.525000] cfg80211: Calling CRDA for country: PT [ 42.540000] cfg80211: Regulatory domain changed to country: PT [ 42.540000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 42.550000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 42.550000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 42.560000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 42.560000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
wlan0: CTRL-EVENT-DISCONNECTED bssid=88:43:e1:57:79:c0 reason=4 l[ 42.575000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
ocally_generated=1
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="A. Guidance" auth_failures=1 duration=10
Any ideas in what could be wrong?
Best regards,
José Gonçalves
Hey,
About the second issue - seems the following patch is missing from your tree:
http://permalink.gmane.org/gmane.linux.kernel.wireless.general/105449
So the warning is bogus. It will happen if you're working on a single processor (UP) system.
To get the latest driver, you can use Luca's tree, which already contains this patch:git://git.kernel.org/pub/scm/linux/kernel/git/luca/wl12xx.git
Arik
Quoted 278 lines · José Miguel Gonçalves
Hi,
After solving some initial platform issues, I'm now blocked in two more issues using the wl127x driver with kernel 3.9.9 in a S3C2416 hardware based platform.
The first one is that the command "iw wlan0 scan" does not scan all frequencies. I've seen a patch submitted to fix an issue in the driver for the 5 GHz band
(http://permalink.gmane.org/gmane.linux.kernel.wireless.general/107771) but this is not my issue, because I can not see also several APs in the 2.4GHz band after a scan.The second issue is when I try to associate with an AP using WPA2-PSK with
wpa_supplicant(only able to reach this point by setting "scan_freq" in wpa_supplicat.conf file to the frequency used by the AP, because of the inability to perform of a complete scan) I get an error in the driver, as shown in the log bellow:[root ~]$
wpa_supplicant-i wlan0 -c/etc/wpa_supplicant.confSuccessfully initializedwpa_supplicant[ 33.915000] wlcore: firmware booted (Rev 6.3.10.0.133) [ 34.280000] cfg80211: Calling CRDA for country: PT [ 34.290000] cfg80211: Regulatory domain changed to country: PT [ 34.290000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 34.305000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 34.320000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 34.320000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 34.330000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 34.340000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz),(N/A, 4000 mBm)
wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[ 34.585000] wlan0: authenticate with 88:43:e1:57:79:c0 A. Guidance' freq=2452 MHz)[ 34.595000] ------------[ cut here ]------------ [ 34.595000] WARNING: at drivers/net/wireless/ti/wlcore/tx.c:1307 wlcore_is_queue_stopped_by_reason_locked+0x98/0xb4 [wlcore]() [ 34.595000] Modules linked in: arc4 wl12xx wlcore mac80211 wlcore_sdio lm70 [ 34.595000] Backtrace: [ 34.595000] [<c000b92c>] (dump_backtrace+0x0/0x10c) from [<c02ed4a4>] (dump_stack+0x18/0x1c) [ 34.595000] r6:bf05ddd8 r5:00000009 r4:00000000 r3:00000000 [ 34.595000] [<c02ed48c>] (dump_stack+0x0/0x1c) from [<c0019ecc>] (warn_slowpath_common+0x54/0x70) [ 34.595000] [<c0019e78>] (warn_slowpath_common+0x0/0x70) from [<c0019f0c>] (warn_slowpath_null+0x24/0x2c) [ 34.595000] r8:c39e2acc r7:00000000 r6:c305b160 r5:bf06ca36 r4:00000002 r3:00000009 [ 34.595000] [<c0019ee8>] (warn_slowpath_null+0x0/0x2c) from [<bf05ddd8>] (wlcore_is_queue_stopped_by_reason_locked+0x98/0xb4 [wlcore]) [ 34.595000] [<bf05dd40>] (wlcore_is_queue_stopped_by_reason_locked+0x0/0xb4 [wlcore]) from [<bf05de38>] (wlcore_is_queue_stopped_by_reason+0x44/0x7c [wlcore]) [ 34.595000] r6:00000000 r5:c305b160 r4:80000013 [ 34.595000] [<bf05ddf4>] (wlcore_is_queue_stopped_by_reason+0x0/0x7c [wlcore]) from [<bf05deb4>] (wl1271_handle_tx_low_watermark+0x44/0x94 [wlcore]) [ 34.595000] r8:c305b160 r7:c39e2acc r6:00000000 r5:c39e2acc r4:00000000 r3:00000000 [ 34.595000] [<bf05de70>] (wl1271_handle_tx_low_watermark+0x0/0x94 [wlcore]) from [<bf05e050>] (wl1271_tx_reset_link_queues+0x14c/0x174 [wlcore]) [ 34.595000] [<bf05df04>] (wl1271_tx_reset_link_queues+0x0/0x174 [wlcore]) from [<bf05970c>] (wl12xx_free_link+0xec/0x150 [wlcore]) [ 34.595000] [<bf059620>] (wl12xx_free_link+0x0/0x150 [wlcore]) from [<bf059b50>] (wl12xx_cmd_role_stop_sta+0x98/0x100 [wlcore]) [ 34.595000] r7:c305b160 r6:00000000 r5:c39e2acc r4:c3a89ac0 [ 34.595000] [<bf059ab8>] (wl12xx_cmd_role_stop_sta+0x0/0x100 [wlcore]) from [<bf0546d8>] (wl1271_bss_info_changed_sta+0x840/0x9a4 [wlcore]) [ 34.595000] r7:c39e2acc r6:c305b160 r5:c39e2a10 r4:000000e0 [ 34.595000] [<bf053e98>] (wl1271_bss_info_changed_sta+0x0/0x9a4 [wlcore]) from [<bf054a0c>] (wl1271_op_bss_info_changed+0x1d0/0x46c [wlcore]) [ 34.595000] [<bf05483c>] (wl1271_op_bss_info_changed+0x0/0x46c [wlcore]) from [<bf009538>] (ieee80211_bss_info_change_notify+0x6c/0x10c [mac80211]) [ 34.595000] [<bf0094cc>] (ieee80211_bss_info_change_notify+0x0/0x10c [mac80211]) from [<bf02bf1c>] (ieee80211_prep_connection+0x2dc/0x76c [mac80211]) [ 34.595000] r7:00000fff r6:c39cfe48 r5:c305b8e4 r4:c39e2440 [ 34.595000] [<bf02bc40>] (ieee80211_prep_connection+0x0/0x76c [mac80211]) from [<bf030d70>] (ieee80211_mgd_auth+0x228/0x29c [mac80211]) [ 34.595000] [<bf030b48>] (ieee80211_mgd_auth+0x0/0x29c [mac80211]) from [<bf01afd4>] (ieee80211_auth+0x18/0x1c [mac80211]) [ 34.595000] [<bf01afbc>] (ieee80211_auth+0x0/0x1c [mac80211]) from [<c02e40a8>] (__cfg80211_mlme_auth+0x170/0x188) [ 34.595000] [<c02e3f38>] (__cfg80211_mlme_auth+0x0/0x188) from [<c02e4154>] (cfg80211_mlme_auth+0x94/0xb8) [ 34.595000] [<c02e40c0>] (cfg80211_mlme_auth+0x0/0xb8) from [<c02dffbc>] (nl80211_authenticate+0x258/0x27c) [ 34.595000] [<c02dfd64>] (nl80211_authenticate+0x0/0x27c) from [<c0260044>] (genl_rcv_msg+0x23c/0x274) [ 34.595000] [<c025fe08>] (genl_rcv_msg+0x0/0x274) from [<c025f458>] (netlink_rcv_skb+0xb4/0xc8) [ 34.595000] [<c025f3a4>] (netlink_rcv_skb+0x0/0xc8) from [<c025fdfc>] (genl_rcv+0x20/0x2c) [ 34.595000] r6:00000048 r5:c3a5b400 r4:c38c4bc0 r3:c025fddc [ 34.595000] [<c025fddc>] (genl_rcv+0x0/0x2c) from [<c025ee40>] (netlink_unicast+0x1b0/0x214) [ 34.595000] r4:c38c5e00 r3:c025fddc [ 34.595000] [<c025ec90>] (netlink_unicast+0x0/0x214) from [<c025f230>] (netlink_sendmsg+0x2e0/0x358) [ 34.595000] [<c025ef50>] (netlink_sendmsg+0x0/0x358) from [<c0230944>] (sock_sendmsg+0x88/0xa8) [ 34.595000] [<c02308bc>] (sock_sendmsg+0x0/0xa8) from [<c0230d64>] (___sys_sendmsg+0x2c8/0x2e0) [ 34.595000] [<c0230a9c>] (___sys_sendmsg+0x0/0x2e0) from [<c0232920>] (__sys_sendmsg+0x44/0x70) [ 34.595000] [<c02328dc>] (__sys_sendmsg+0x0/0x70) from [<c023295c>] (sys_sendmsg+0x10/0x14) [ 34.595000] r6:be94fa8c r5:017940a0 r4:00000000 [ 34.595000] [<c023294c>] (sys_sendmsg+0x0/0x14) from [<c0009400>] (ret_fast_syscall+0x0/0x2c) [ 34.595000] ---[ end trace a2c5f3d5ef286154 ]--- [ 34.605000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3) [ 34.605000] ------------[ cut here ]------------ [ 34.605000] WARNING: at drivers/net/wireless/ti/wlcore/tx.c:1316 wlcore_is_queue_stopped_locked+0x74/0x8c [wlcore]() [ 34.605000] Modules linked in: arc4 wl12xx wlcore mac80211 wlcore_sdio lm70 [ 34.605000] Backtrace: [ 34.605000] [<c000b92c>] (dump_backtrace+0x0/0x10c) from [<c02ed4a4>] (dump_stack+0x18/0x1c) [ 34.605000] r6:bf05f240 r5:00000009 r4:00000000 r3:00000000 [ 34.605000] [<c02ed48c>] (dump_stack+0x0/0x1c) from [<c0019ecc>] (warn_slowpath_common+0x54/0x70) [ 34.605000] [<c0019e78>] (warn_slowpath_common+0x0/0x70) from [<c0019f0c>] (warn_slowpath_null+0x24/0x2c) [ 34.605000] r8:40000013 r7:c305b160 r6:c305b160 r5:bf06ca36 r4:00000000 r3:00000009 [ 34.605000] [<c0019ee8>] (warn_slowpath_null+0x0/0x2c) from [<bf05f240>] (wlcore_is_queue_stopped_locked+0x74/0x8c [wlcore]) [ 34.605000] [<bf05f1cc>] (wlcore_is_queue_stopped_locked+0x0/0x8c [wlcore]) from [<bf05225c>] (wl1271_op_tx+0x104/0x290 [wlcore]) [ 34.605000] r6:c39e2a10 r5:00000001 r4:c38c4a40 r3:00000003 [ 34.605000] [<bf052158>] (wl1271_op_tx+0x0/0x290 [wlcore]) from [<bf023e64>] (__ieee80211_tx+0x134/0x384 [mac80211]) [ 34.605000] [<bf023d30>] (__ieee80211_tx+0x0/0x384 [mac80211]) from [<bf024174>] (ieee80211_tx+0xc0/0xe8 [mac80211]) [ 34.605000] [<bf0240b4>] (ieee80211_tx+0x0/0xe8 [mac80211]) from [<bf02474c>] (ieee80211_xmit+0x80/0x94 [mac80211]) [ 34.605000] [<bf0246cc>] (ieee80211_xmit+0x0/0x94 [mac80211]) from [<bf025698>] (__ieee80211_tx_skb_tid_band+0x58/0x64 [mac80211]) [ 34.605000] r8:00000000 r7:00000001 r6:00000000 r5:c39e2440 r4:c38c4a40 r3:c3ae8000 [ 34.605000] [<bf025640>] (__ieee80211_tx_skb_tid_band+0x0/0x64 [mac80211]) from [<bf0286c4>] (ieee80211_send_auth+0x158/0x1e0 [mac80211]) [ 34.605000] r6:c39e2440 r5:c38c4a40 r4:c3ac8b94 r3:00000000 [ 34.605000] [<bf02856c>] (ieee80211_send_auth+0x0/0x1e0 [mac80211]) from [<bf02c550>] (ieee80211_probe_auth+0x174/0x2c8 [mac80211]) [ 34.605000] [<bf02c3dc>] (ieee80211_probe_auth+0x0/0x2c8 [mac80211]) from [<bf030d80>] (ieee80211_mgd_auth+0x238/0x29c [mac80211]) [ 34.605000] r8:c39e2798 r7:00000000 r6:c39e2440 r5:c3a72c20 r4:c3ae9af8 [ 34.605000] [<bf030b48>] (ieee80211_mgd_auth+0x0/0x29c [mac80211]) from [<bf01afd4>] (ieee80211_auth+0x18/0x1c [mac80211]) [ 34.605000] [<bf01afbc>] (ieee80211_auth+0x0/0x1c [mac80211]) from [<c02e40a8>] (__cfg80211_mlme_auth+0x170/0x188) [ 34.605000] [<c02e3f38>] (__cfg80211_mlme_auth+0x0/0x188) from [<c02e4154>] (cfg80211_mlme_auth+0x94/0xb8) [ 34.605000] [<c02e40c0>] (cfg80211_mlme_auth+0x0/0xb8) from [<c02dffbc>] (nl80211_authenticate+0x258/0x27c) [ 34.605000] [<c02dfd64>] (nl80211_authenticate+0x0/0x27c) from [<c0260044>] (genl_rcv_msg+0x23c/0x274) [ 34.605000] [<c025fe08>] (genl_rcv_msg+0x0/0x274) from [<c025f458>] (netlink_rcv_skb+0xb4/0xc8) [ 34.605000] [<c025f3a4>] (netlink_rcv_skb+0x0/0xc8) from [<c025fdfc>] (genl_rcv+0x20/0x2c) [ 34.605000] r6:00000048 r5:c3a5b400 r4:c38c4bc0 r3:c025fddc [ 34.605000] [<c025fddc>] (genl_rcv+0x0/0x2c) from [<c025ee40>] (netlink_unicast+0x1b0/0x214) [ 34.605000] r4:c38c5e00 r3:c025fddc [ 34.605000] [<c025ec90>] (netlink_unicast+0x0/0x214) from [<c025f230>] (netlink_sendmsg+0x2e0/0x358) [ 34.605000] [<c025ef50>] (netlink_sendmsg+0x0/0x358) from [<c0230944>] (sock_sendmsg+0x88/0xa8) [ 34.605000] [<c02308bc>] (sock_sendmsg+0x0/0xa8) from [<c0230d64>] (___sys_sendmsg+0x2c8/0x2e0) [ 34.605000] [<c0230a9c>] (___sys_sendmsg+0x0/0x2e0) from [<c0232920>] (__sys_sendmsg+0x44/0x70) [ 34.605000] [<c02328dc>] (__sys_sendmsg+0x0/0x70) from [<c023295c>] (sys_sendmsg+0x10/0x14) [ 34.605000] r6:be94fa8c r5:017940a0 r4:00000000 [ 34.605000] [<c023294c>] (sys_sendmsg+0x0/0x14) from [<c0009400>] (ret_fast_syscall+0x0/0x2c) [ 34.605000] ---[ end trace a2c5f3d5ef286155 ]--- [ 34.625000] wlan0: send auth to 88:43:e1:57:79:c0 (try 2/3) [ 34.640000] wlan0: send auth to 88:43:e1:57:79:c0 (try 3/3) [ 34.650000] wlan0: authentication with 88:43:e1:57:79:c0 timed out wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[ 34.875000] wlan0: authenticate with 88:43:e1:57:79:c0 A. Guidance' freq=2452 MHz) [ 34.915000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3) [ 34.920000] wlan0: authenticated wlan0: Trying to associate with 88:43:e1:57:79:c0 (SSID='A. Guidance' freq=2452 MHz) [ 34.995000] wlan0: associate with 88:43:e1:57:79:c0 (try 1/3) [ 35.015000] wlan0: associate with 88:43:e1:57:79:c0 (try 2/3) [ 35.035000] wlan0: associate with 88:43:e1:57:79:c0 (try 3/3) [ 35.060000] wlan0: association with 88:43:e1:57:79:c0 timed out wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[ 35.620000] wlan0: authenticate with 88:43:e1:57:79:c0 A. Guidance' freq=2452 MHz) [ 35.660000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3) [ 35.665000] wlan0: authenticated wlan0: Trying to associate with 88:43:e1:57:79:c0 (SSID='A. Guidance' freq=2452 MHz) [ 35.740000] wlan0: associate with 88:43:e1:57:79:c0 (try 1/3) [ 35.745000] wlan0: RX AssocResp from 88:43:e1:57:79:c0 (capab=0x431 status=0 aid=2) [ 35.765000] wlan0: associated [ 35.770000] cfg80211: Calling CRDA for country: PT [ 35.780000] cfg80211: Regulatory domain changed to country: PT [ 35.780000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 35.790000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 35.790000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 35.800000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 35.800000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 35.810000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) wlan0: Associated with 88:43:e1:57:79:c0 [ 37.585000] wlcore: Beacon loss detected. roles:0xff [ 39.250000] wlcore: Beacon loss detected. roles:0xff [ 40.935000] wlcore: Beacon loss detected. roles:0xff [ 42.400000] wlcore: Connection loss work (role_id: 0). [ 42.400000] wlan0: Connection to AP 88:43:e1:57:79:c0 lost [ 42.475000] cfg80211: Calling CRDA to update world regulatory domain [ 42.485000] cfg80211: World regulatory domain updated: [ 42.485000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 42.500000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.500000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.515000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 42.515000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.525000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.525000] cfg80211: Calling CRDA for country: PT [ 42.540000] cfg80211: Regulatory domain changed to country: PT [ 42.540000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 42.550000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 42.550000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 42.560000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 42.560000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A,2700 mBm)
wlan0: CTRL-EVENT-DISCONNECTED bssid=88:43:e1:57:79:c0 reason=4 l[
42.575000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A,
4000 mBm)
ocally_generated=1
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="A. Guidance" auth_failures=1 duration=10Any ideas in what could be wrong?
Best regards,
José Gonçalves
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Arik,
Yep, that patch solved the kernel warning, but the association with the AP is still lost after 3 warnings;
wlcore: Beacon loss detected. roles:0xff
To use the driver in the Luca's tree I need to do some work to adapt my platform to the latest kernel version, what I would like to avoid for now. Is there any set of patches to put the driver in vanilla kernel 3.9 in a more stable condition?
Best regards,
Jose Gonçalves
Quoted 295 lines · Arik Nemtsov
Hey,
About the second issue - seems the following patch is missing from your tree:
http://permalink.gmane.org/gmane.linux.kernel.wireless.general/105449So the warning is bogus. It will happen if you're working on a single processor (UP) system.
To get the latest driver, you can use Luca's tree, which already contains this patch:
git://git.kernel.org/pub/scm/linux/kernel/git/luca/wl12xx.gitArik
Quoted 278 lines · José Miguel Gonçalves
Hi,
After solving some initial platform issues, I'm now blocked in two more issues using the wl127x driver with kernel 3.9.9 in a S3C2416 hardware based platform.
The first one is that the command "iw wlan0 scan" does not scan all frequencies. I've seen a patch submitted to fix an issue in the driver for the 5 GHz band
(http://permalink.gmane.org/gmane.linux.kernel.wireless.general/107771) but this is not my issue, because I can not see also several APs in the 2.4GHz band after a scan.The second issue is when I try to associate with an AP using WPA2-PSK with
wpa_supplicant(only able to reach this point by setting "scan_freq" in wpa_supplicat.conf file to the frequency used by the AP, because of the inability to perform of a complete scan) I get an error in the driver, as shown in the log bellow:[root ~]$
wpa_supplicant-i wlan0 -c/etc/wpa_supplicant.confSuccessfully initializedwpa_supplicant[ 33.915000] wlcore: firmware booted (Rev 6.3.10.0.133) [ 34.280000] cfg80211: Calling CRDA for country: PT [ 34.290000] cfg80211: Regulatory domain changed to country: PT [ 34.290000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 34.305000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 34.320000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 34.320000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 34.330000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 34.340000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz),(N/A, 4000 mBm)
wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[ 34.585000] wlan0: authenticate with 88:43:e1:57:79:c0 A. Guidance' freq=2452 MHz)[ 34.595000] ------------[ cut here ]------------ [ 34.595000] WARNING: at drivers/net/wireless/ti/wlcore/tx.c:1307 wlcore_is_queue_stopped_by_reason_locked+0x98/0xb4 [wlcore]() [ 34.595000] Modules linked in: arc4 wl12xx wlcore mac80211 wlcore_sdio lm70 [ 34.595000] Backtrace: [ 34.595000] [<c000b92c>] (dump_backtrace+0x0/0x10c) from [<c02ed4a4>] (dump_stack+0x18/0x1c) [ 34.595000] r6:bf05ddd8 r5:00000009 r4:00000000 r3:00000000 [ 34.595000] [<c02ed48c>] (dump_stack+0x0/0x1c) from [<c0019ecc>] (warn_slowpath_common+0x54/0x70) [ 34.595000] [<c0019e78>] (warn_slowpath_common+0x0/0x70) from [<c0019f0c>] (warn_slowpath_null+0x24/0x2c) [ 34.595000] r8:c39e2acc r7:00000000 r6:c305b160 r5:bf06ca36 r4:00000002 r3:00000009 [ 34.595000] [<c0019ee8>] (warn_slowpath_null+0x0/0x2c) from [<bf05ddd8>] (wlcore_is_queue_stopped_by_reason_locked+0x98/0xb4 [wlcore]) [ 34.595000] [<bf05dd40>] (wlcore_is_queue_stopped_by_reason_locked+0x0/0xb4 [wlcore]) from [<bf05de38>] (wlcore_is_queue_stopped_by_reason+0x44/0x7c [wlcore]) [ 34.595000] r6:00000000 r5:c305b160 r4:80000013 [ 34.595000] [<bf05ddf4>] (wlcore_is_queue_stopped_by_reason+0x0/0x7c [wlcore]) from [<bf05deb4>] (wl1271_handle_tx_low_watermark+0x44/0x94 [wlcore]) [ 34.595000] r8:c305b160 r7:c39e2acc r6:00000000 r5:c39e2acc r4:00000000 r3:00000000 [ 34.595000] [<bf05de70>] (wl1271_handle_tx_low_watermark+0x0/0x94 [wlcore]) from [<bf05e050>] (wl1271_tx_reset_link_queues+0x14c/0x174 [wlcore]) [ 34.595000] [<bf05df04>] (wl1271_tx_reset_link_queues+0x0/0x174 [wlcore]) from [<bf05970c>] (wl12xx_free_link+0xec/0x150 [wlcore]) [ 34.595000] [<bf059620>] (wl12xx_free_link+0x0/0x150 [wlcore]) from [<bf059b50>] (wl12xx_cmd_role_stop_sta+0x98/0x100 [wlcore]) [ 34.595000] r7:c305b160 r6:00000000 r5:c39e2acc r4:c3a89ac0 [ 34.595000] [<bf059ab8>] (wl12xx_cmd_role_stop_sta+0x0/0x100 [wlcore]) from [<bf0546d8>] (wl1271_bss_info_changed_sta+0x840/0x9a4 [wlcore]) [ 34.595000] r7:c39e2acc r6:c305b160 r5:c39e2a10 r4:000000e0 [ 34.595000] [<bf053e98>] (wl1271_bss_info_changed_sta+0x0/0x9a4 [wlcore]) from [<bf054a0c>] (wl1271_op_bss_info_changed+0x1d0/0x46c [wlcore]) [ 34.595000] [<bf05483c>] (wl1271_op_bss_info_changed+0x0/0x46c [wlcore]) from [<bf009538>] (ieee80211_bss_info_change_notify+0x6c/0x10c [mac80211]) [ 34.595000] [<bf0094cc>] (ieee80211_bss_info_change_notify+0x0/0x10c [mac80211]) from [<bf02bf1c>] (ieee80211_prep_connection+0x2dc/0x76c [mac80211]) [ 34.595000] r7:00000fff r6:c39cfe48 r5:c305b8e4 r4:c39e2440 [ 34.595000] [<bf02bc40>] (ieee80211_prep_connection+0x0/0x76c [mac80211]) from [<bf030d70>] (ieee80211_mgd_auth+0x228/0x29c [mac80211]) [ 34.595000] [<bf030b48>] (ieee80211_mgd_auth+0x0/0x29c [mac80211]) from [<bf01afd4>] (ieee80211_auth+0x18/0x1c [mac80211]) [ 34.595000] [<bf01afbc>] (ieee80211_auth+0x0/0x1c [mac80211]) from [<c02e40a8>] (__cfg80211_mlme_auth+0x170/0x188) [ 34.595000] [<c02e3f38>] (__cfg80211_mlme_auth+0x0/0x188) from [<c02e4154>] (cfg80211_mlme_auth+0x94/0xb8) [ 34.595000] [<c02e40c0>] (cfg80211_mlme_auth+0x0/0xb8) from [<c02dffbc>] (nl80211_authenticate+0x258/0x27c) [ 34.595000] [<c02dfd64>] (nl80211_authenticate+0x0/0x27c) from [<c0260044>] (genl_rcv_msg+0x23c/0x274) [ 34.595000] [<c025fe08>] (genl_rcv_msg+0x0/0x274) from [<c025f458>] (netlink_rcv_skb+0xb4/0xc8) [ 34.595000] [<c025f3a4>] (netlink_rcv_skb+0x0/0xc8) from [<c025fdfc>] (genl_rcv+0x20/0x2c) [ 34.595000] r6:00000048 r5:c3a5b400 r4:c38c4bc0 r3:c025fddc [ 34.595000] [<c025fddc>] (genl_rcv+0x0/0x2c) from [<c025ee40>] (netlink_unicast+0x1b0/0x214) [ 34.595000] r4:c38c5e00 r3:c025fddc [ 34.595000] [<c025ec90>] (netlink_unicast+0x0/0x214) from [<c025f230>] (netlink_sendmsg+0x2e0/0x358) [ 34.595000] [<c025ef50>] (netlink_sendmsg+0x0/0x358) from [<c0230944>] (sock_sendmsg+0x88/0xa8) [ 34.595000] [<c02308bc>] (sock_sendmsg+0x0/0xa8) from [<c0230d64>] (___sys_sendmsg+0x2c8/0x2e0) [ 34.595000] [<c0230a9c>] (___sys_sendmsg+0x0/0x2e0) from [<c0232920>] (__sys_sendmsg+0x44/0x70) [ 34.595000] [<c02328dc>] (__sys_sendmsg+0x0/0x70) from [<c023295c>] (sys_sendmsg+0x10/0x14) [ 34.595000] r6:be94fa8c r5:017940a0 r4:00000000 [ 34.595000] [<c023294c>] (sys_sendmsg+0x0/0x14) from [<c0009400>] (ret_fast_syscall+0x0/0x2c) [ 34.595000] ---[ end trace a2c5f3d5ef286154 ]--- [ 34.605000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3) [ 34.605000] ------------[ cut here ]------------ [ 34.605000] WARNING: at drivers/net/wireless/ti/wlcore/tx.c:1316 wlcore_is_queue_stopped_locked+0x74/0x8c [wlcore]() [ 34.605000] Modules linked in: arc4 wl12xx wlcore mac80211 wlcore_sdio lm70 [ 34.605000] Backtrace: [ 34.605000] [<c000b92c>] (dump_backtrace+0x0/0x10c) from [<c02ed4a4>] (dump_stack+0x18/0x1c) [ 34.605000] r6:bf05f240 r5:00000009 r4:00000000 r3:00000000 [ 34.605000] [<c02ed48c>] (dump_stack+0x0/0x1c) from [<c0019ecc>] (warn_slowpath_common+0x54/0x70) [ 34.605000] [<c0019e78>] (warn_slowpath_common+0x0/0x70) from [<c0019f0c>] (warn_slowpath_null+0x24/0x2c) [ 34.605000] r8:40000013 r7:c305b160 r6:c305b160 r5:bf06ca36 r4:00000000 r3:00000009 [ 34.605000] [<c0019ee8>] (warn_slowpath_null+0x0/0x2c) from [<bf05f240>] (wlcore_is_queue_stopped_locked+0x74/0x8c [wlcore]) [ 34.605000] [<bf05f1cc>] (wlcore_is_queue_stopped_locked+0x0/0x8c [wlcore]) from [<bf05225c>] (wl1271_op_tx+0x104/0x290 [wlcore]) [ 34.605000] r6:c39e2a10 r5:00000001 r4:c38c4a40 r3:00000003 [ 34.605000] [<bf052158>] (wl1271_op_tx+0x0/0x290 [wlcore]) from [<bf023e64>] (__ieee80211_tx+0x134/0x384 [mac80211]) [ 34.605000] [<bf023d30>] (__ieee80211_tx+0x0/0x384 [mac80211]) from [<bf024174>] (ieee80211_tx+0xc0/0xe8 [mac80211]) [ 34.605000] [<bf0240b4>] (ieee80211_tx+0x0/0xe8 [mac80211]) from [<bf02474c>] (ieee80211_xmit+0x80/0x94 [mac80211]) [ 34.605000] [<bf0246cc>] (ieee80211_xmit+0x0/0x94 [mac80211]) from [<bf025698>] (__ieee80211_tx_skb_tid_band+0x58/0x64 [mac80211]) [ 34.605000] r8:00000000 r7:00000001 r6:00000000 r5:c39e2440 r4:c38c4a40 r3:c3ae8000 [ 34.605000] [<bf025640>] (__ieee80211_tx_skb_tid_band+0x0/0x64 [mac80211]) from [<bf0286c4>] (ieee80211_send_auth+0x158/0x1e0 [mac80211]) [ 34.605000] r6:c39e2440 r5:c38c4a40 r4:c3ac8b94 r3:00000000 [ 34.605000] [<bf02856c>] (ieee80211_send_auth+0x0/0x1e0 [mac80211]) from [<bf02c550>] (ieee80211_probe_auth+0x174/0x2c8 [mac80211]) [ 34.605000] [<bf02c3dc>] (ieee80211_probe_auth+0x0/0x2c8 [mac80211]) from [<bf030d80>] (ieee80211_mgd_auth+0x238/0x29c [mac80211]) [ 34.605000] r8:c39e2798 r7:00000000 r6:c39e2440 r5:c3a72c20 r4:c3ae9af8 [ 34.605000] [<bf030b48>] (ieee80211_mgd_auth+0x0/0x29c [mac80211]) from [<bf01afd4>] (ieee80211_auth+0x18/0x1c [mac80211]) [ 34.605000] [<bf01afbc>] (ieee80211_auth+0x0/0x1c [mac80211]) from [<c02e40a8>] (__cfg80211_mlme_auth+0x170/0x188) [ 34.605000] [<c02e3f38>] (__cfg80211_mlme_auth+0x0/0x188) from [<c02e4154>] (cfg80211_mlme_auth+0x94/0xb8) [ 34.605000] [<c02e40c0>] (cfg80211_mlme_auth+0x0/0xb8) from [<c02dffbc>] (nl80211_authenticate+0x258/0x27c) [ 34.605000] [<c02dfd64>] (nl80211_authenticate+0x0/0x27c) from [<c0260044>] (genl_rcv_msg+0x23c/0x274) [ 34.605000] [<c025fe08>] (genl_rcv_msg+0x0/0x274) from [<c025f458>] (netlink_rcv_skb+0xb4/0xc8) [ 34.605000] [<c025f3a4>] (netlink_rcv_skb+0x0/0xc8) from [<c025fdfc>] (genl_rcv+0x20/0x2c) [ 34.605000] r6:00000048 r5:c3a5b400 r4:c38c4bc0 r3:c025fddc [ 34.605000] [<c025fddc>] (genl_rcv+0x0/0x2c) from [<c025ee40>] (netlink_unicast+0x1b0/0x214) [ 34.605000] r4:c38c5e00 r3:c025fddc [ 34.605000] [<c025ec90>] (netlink_unicast+0x0/0x214) from [<c025f230>] (netlink_sendmsg+0x2e0/0x358) [ 34.605000] [<c025ef50>] (netlink_sendmsg+0x0/0x358) from [<c0230944>] (sock_sendmsg+0x88/0xa8) [ 34.605000] [<c02308bc>] (sock_sendmsg+0x0/0xa8) from [<c0230d64>] (___sys_sendmsg+0x2c8/0x2e0) [ 34.605000] [<c0230a9c>] (___sys_sendmsg+0x0/0x2e0) from [<c0232920>] (__sys_sendmsg+0x44/0x70) [ 34.605000] [<c02328dc>] (__sys_sendmsg+0x0/0x70) from [<c023295c>] (sys_sendmsg+0x10/0x14) [ 34.605000] r6:be94fa8c r5:017940a0 r4:00000000 [ 34.605000] [<c023294c>] (sys_sendmsg+0x0/0x14) from [<c0009400>] (ret_fast_syscall+0x0/0x2c) [ 34.605000] ---[ end trace a2c5f3d5ef286155 ]--- [ 34.625000] wlan0: send auth to 88:43:e1:57:79:c0 (try 2/3) [ 34.640000] wlan0: send auth to 88:43:e1:57:79:c0 (try 3/3) [ 34.650000] wlan0: authentication with 88:43:e1:57:79:c0 timed out wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[ 34.875000] wlan0: authenticate with 88:43:e1:57:79:c0 A. Guidance' freq=2452 MHz) [ 34.915000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3) [ 34.920000] wlan0: authenticated wlan0: Trying to associate with 88:43:e1:57:79:c0 (SSID='A. Guidance' freq=2452 MHz) [ 34.995000] wlan0: associate with 88:43:e1:57:79:c0 (try 1/3) [ 35.015000] wlan0: associate with 88:43:e1:57:79:c0 (try 2/3) [ 35.035000] wlan0: associate with 88:43:e1:57:79:c0 (try 3/3) [ 35.060000] wlan0: association with 88:43:e1:57:79:c0 timed out wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[ 35.620000] wlan0: authenticate with 88:43:e1:57:79:c0 A. Guidance' freq=2452 MHz) [ 35.660000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3) [ 35.665000] wlan0: authenticated wlan0: Trying to associate with 88:43:e1:57:79:c0 (SSID='A. Guidance' freq=2452 MHz) [ 35.740000] wlan0: associate with 88:43:e1:57:79:c0 (try 1/3) [ 35.745000] wlan0: RX AssocResp from 88:43:e1:57:79:c0 (capab=0x431 status=0 aid=2) [ 35.765000] wlan0: associated [ 35.770000] cfg80211: Calling CRDA for country: PT [ 35.780000] cfg80211: Regulatory domain changed to country: PT [ 35.780000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 35.790000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 35.790000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 35.800000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 35.800000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 35.810000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) wlan0: Associated with 88:43:e1:57:79:c0 [ 37.585000] wlcore: Beacon loss detected. roles:0xff [ 39.250000] wlcore: Beacon loss detected. roles:0xff [ 40.935000] wlcore: Beacon loss detected. roles:0xff [ 42.400000] wlcore: Connection loss work (role_id: 0). [ 42.400000] wlan0: Connection to AP 88:43:e1:57:79:c0 lost [ 42.475000] cfg80211: Calling CRDA to update world regulatory domain [ 42.485000] cfg80211: World regulatory domain updated: [ 42.485000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 42.500000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.500000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.515000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 42.515000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.525000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 42.525000] cfg80211: Calling CRDA for country: PT [ 42.540000] cfg80211: Regulatory domain changed to country: PT [ 42.540000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 42.550000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 42.550000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 42.560000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 42.560000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A,2700 mBm)
wlan0: CTRL-EVENT-DISCONNECTED bssid=88:43:e1:57:79:c0 reason=4 l[
42.575000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A,
4000 mBm)
ocally_generated=1
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="A. Guidance" auth_failures=1 duration=10Any ideas in what could be wrong?
Best regards,
José Gonçalves
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 9 lines
____________________________________________________________ José Miguel P. Gonçalves * email: [email protected] * INOV * Tel.(Phone): +351 213 100 474 Av. Duque de Ávila, 23 * 1000-138 Lisboa * PORTUGAL * WWW: http://www.inov.pt ____________________________________________________________
Quoted 7 lines · José Miguel Gonçalves
Hi Arik,
Yep, that patch solved the kernel warning, but the association with the AP is still lost after 3 warnings;
wlcore: Beacon loss detected. roles:0xff
This one is possibly a FW version issue. I'd give it a go with the latest FW in TI's git:
https://github.com/TI-OpenLink/ti-utils/tree/master/hw/firmware
Quoted 5 lines
To use the driver in the Luca's tree I need to do some work to adapt my platform to the latest kernel version, what I would like to avoid for now. Is there any set of patches to put the driver in vanilla kernel 3.9 in a more stable condition?
Well 3.9 is pretty new, so the difference is not that big. A simple cherry pick of all patches done on <root>/drivers/wireless/ti/ would do the trick.
Or you could always used compat-wireless, or in it's new name "driver backports":
https://backports.wiki.kernel.org/index.php/Main_Page
Arik
Thanks Arik, for helping with this.
Quoted 6 lines · Arik Nemtsov
Quoted 4 lines · José Miguel Gonçalves
Hi Arik,
Yep, that patch solved the kernel warning, but the association with the AP is still lost after 3 warnings;
Cool, I have just sent this patch to the stable mailing list, for inclusion on v.3.9.y.
Quoted 5 lines
Quoted 1 line
wlcore: Beacon loss detected. roles:0xff
This one is possibly a FW version issue. I'd give it a go with the latest FW in TI's git:
https://github.com/TI-OpenLink/ti-utils/tree/master/hw/firmware
More specifically, try the hw/firmware/wl127x-fw-4-sr.bin and the hw/firmware/wl127x-fw-4-mr.bin (if you're using multirole). Note that you need to rename them to wl127x-fw-5-sr.bin and wl127x-fw-5-mr.bin, respectively.
What we have in the linux-firmware git at the moment are versions 6.3.10.0.133 (singlerole) and 6.5.7.0.42 (multirole). The new ones in TI's github repo are 6.3.10.0.136 and 6.5.7.0.46.
If the new firmwares solve your problem, please let me know and I'll push them to the linux-firmware git repo.
Quoted 5 lines
Quoted 4 lines
To use the driver in the Luca's tree I need to do some work to adapt my platform to the latest kernel version, what I would like to avoid for now. Is there any set of patches to put the driver in vanilla kernel 3.9 in a more stable condition?
Quoted 7 lines
Well 3.9 is pretty new, so the difference is not that big. A simple cherry pick of all patches done on <root>/drivers/wireless/ti/ would do the trick.
Or you could always used compat-wireless, or in it's new name "driver backports":
https://backports.wiki.kernel.org/index.php/Main_Page
I'd really recommend cherry-picking just what is needed. It should be very few patches. And every time you find a new patch that fixes some real issue you're seeing, let me know and I'll send to stable.
You're so close to the mainline that it would be silly to use compat just for a few patches. ;)
--
Cheers,
Luca.
Hi,
First of all, thanks Arik and Luca for your help.
Quoted 9 lines · Luciano Coelho
Quoted 4 lines
Quoted 1 line
wlcore: Beacon loss detected. roles:0xff
This one is possibly a FW version issue. I'd give it a go with the latest FW in TI's git:
https://github.com/TI-OpenLink/ti-utils/tree/master/hw/firmwareMore specifically, try the hw/firmware/wl127x-fw-4-sr.bin and the hw/firmware/wl127x-fw-4-mr.bin (if you're using multirole). Note that you need to rename them to wl127x-fw-5-sr.bin and wl127x-fw-5-mr.bin, respectively.
Quoted 6 lines
What we have in the linux-firmware git at the moment are versions 6.3.10.0.133 (singlerole) and 6.5.7.0.42 (multirole). The new ones in TI's github repo are 6.3.10.0.136 and 6.5.7.0.46.
If the new firmwares solve your problem, please let me know and I'll push them to the linux-firmware git repo.
Just to clarify. I was using the latest firmware files from linux-firmware and the driver picks the file wl127x-fw-5-sr.bin which is Rev 6.3.10.0.133. So are you saying that I should install the wl127x-fw-4-sr.bin from TI's github repo named as wl127x-fw-5-sr.bin and give it a try?
Quoted 9 lines
Quoted 9 lines
Quoted 5 lines
To use the driver in the Luca's tree I need to do some work to adapt my platform to the latest kernel version, what I would like to avoid for now. Is there any set of patches to put the driver in vanilla kernel 3.9 in a more stable condition?
Well 3.9 is pretty new, so the difference is not that big. A simple cherry pick of all patches done on <root>/drivers/wireless/ti/ would do the trick.
Quoted 5 lines
Quoted 3 lines
Or you could always used compat-wireless, or in it's new name "driver backports":
https://backports.wiki.kernel.org/index.php/Main_PageI'd really recommend cherry-picking just what is needed. It should be very few patches.
I was doing that in this precise moment...
Quoted 2 lines
And every time you find a new patch that fixes some real issue you're seeing, let me know and I'll send to stable.
OK.
José Gonçalves
Quoted 14 lines · José Miguel Gonçalves
Quoted 13 lines · Luciano Coelho
Quoted 4 lines
Quoted 1 line
wlcore: Beacon loss detected. roles:0xff
This one is possibly a FW version issue. I'd give it a go with the latest FW in TI's git:
https://github.com/TI-OpenLink/ti-utils/tree/master/hw/firmwareMore specifically, try the hw/firmware/wl127x-fw-4-sr.bin and the hw/firmware/wl127x-fw-4-mr.bin (if you're using multirole). Note that you need to rename them to wl127x-fw-5-sr.bin and wl127x-fw-5-mr.bin, respectively.
What we have in the linux-firmware git at the moment are versions 6.3.10.0.133 (singlerole) and 6.5.7.0.42 (multirole). The new ones in TI's github repo are 6.3.10.0.136 and 6.5.7.0.46.
Quoted 8 lines
Quoted 2 lines
If the new firmwares solve your problem, please let me know and I'll push them to the linux-firmware git repo.
Just to clarify. I was using the latest firmware files from linux-firmware and the driver picks the file wl127x-fw-5-sr.bin which is Rev 6.3.10.0.133. So are you saying that I should install the wl127x-fw-4-sr.bin from TI's github repo named as wl127x-fw-5-sr.bin and give it a try?
Exactly. The name used with TI's forked kernel hasn't update the version number to 5, so you need to rename it manually. When the firmware boots, you should see Rev. 6.3.10.0.136 printed out.
You may also want to update the mr version, if you'll use P2P, or other multirole scenarios.
--
Cheers,
Luca.
Hi,
I've upgraded the firmware and also backported all patches in Luca's tree which do not break API compatibility in kernel 3.9 and still have no success. Here goes the log:
[root ~]$ wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf Successfully initialized wpa_supplicant
[ 38.295000] wlcore: firmware booted (Rev 6.3.10.0.136) [ 38.655000] cfg80211: Calling CRDA for country: PT [ 38.655000] cfg80211: Regulatory domain changed to country: PT [ 38.665000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 38.665000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 38.675000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 38.675000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 38.685000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 38.685000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[ 38.945000] wlan0: authenticate with 88:43:e1:57:79:c0 A. Guidance' freq=2452 MHz) [ 38.985000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3) [ 38.990000] wlan0: authenticated wlan0: Trying to associate with 88:43:e1:57:79:c0 (SSID='A. Guidance' freq=2452 MHz) [ 39.065000] wlan0: associate with 88:43:e1:57:79:c0 (try 1/3) [ 39.070000] wlan0: RX AssocResp from 88:43:e1:57:79:c0 (capab=0x431 status=0 aid=1) [ 39.095000] wlan0: associated [ 39.095000] cfg80211: Calling CRDA for country: PT [ 39.105000] cfg80211: Regulatory domain changed to country: PT [ 39.105000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 39.110000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 39.125000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 39.125000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 39.140000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 39.140000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) wlan0: Associated with 88:43:e1:57:79:c0 [ 40.925000] wlcore: Beacon loss detected. roles:0xff [ 42.610000] wlcore: Beacon loss detected. roles:0xff [ 44.275000] wlcore: Beacon loss detected. roles:0xff [ 45.740000] wlcore: Connection loss work (role_id: 0). [ 45.740000] wlan0: Connection to AP 88:43:e1:57:79:c0 lost
And I still have the issue of not being able to scan all APs in the vicinity. I can only (briefly) associate with my AP because I restrict the scanning frequencies in wpa_supplicant.conf file;
country=PT
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="A. Guidance"
scan_freq=2452
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP TKIP
group=TKIP
psk="<some_password_in_ascii>"
}Any more ideas on how to debug this? Is there any specific debug_level mask that can apply to the driver to help it?
José Gonçalves
Quoted 2 lines · José Miguel Gonçalves
Any more ideas on how to debug this? Is there any specific
debug_levelmask that can apply to the driver to help it?
You can try the mask 0x63c20 (it's pretty verbose, so I would put it in pastebin).
Perhaps this is a genuine problem with the antenna of the card? Can you verify the RSSI of the AP is ok using iw?
Arik
Quoted 9 lines · Arik Nemtsov
Quoted 2 lines · José Miguel Gonçalves
Any more ideas on how to debug this? Is there any specific
debug_levelmask that can apply to the driver to help it?You can try the mask
0x63c20(it's pretty verbose, so I would put it in pastebin).Perhaps this is a genuine problem with the antenna of the card?
Nope. The AP is 1 meter away form my board (even without antenna in the card it should associate).
Quoted 2 lines
Can
you verify the RSSI of the AP is ok using iw?
The iw output:
The dmesg output with debug mask set to 0x63c20:
Note that with debug activated I did not see the driver's "Beacon loss detected" messages.
José Gonçalves
Quoted 8 lines · José Miguel Gonçalves
The dmesg output with debug mask set to
0x63c20:Note that with debug activated I did not see the driver's "Beacon loss detected" messages.
You have this line in the log:
[ 72.435000] wlan0: deauthenticated from 88:43:e1:57:79:c0 (Reason: 23)
This means:
Association request rejected because the information in the Power Capability element is
unacceptable
In other words the AP is disconnecting you since your Tx power is inadequate (probably too high?). I'd try to limit it using iw, or just set a different regdomain where its limited.
Also I'd try with a different AP.
Arik
Hi Arik,
Quoted 18 lines · Arik Nemtsov
Quoted 8 lines · José Miguel Gonçalves
The dmesg output with debug mask set to
0x63c20:Note that with debug activated I did not see the driver's "Beacon loss detected" messages.
You have this line in the log:
[ 72.435000] wlan0: deauthenticated from 88:43:e1:57:79:c0 (Reason: 23)This means:
Association request rejected because the information in the Power Capability element is
unacceptable
Quoted 4 lines
In other words the AP is disconnecting you since your Tx power is inadequate (probably too high?). I'd try to limit it using iw, or just set a different regdomain where its limited.
Also I'd try with a different AP.
I think that return code is a bogus caused by the driver debug code, because when I remove all the debug I see a different behaviour, i.e., after brief associating with the AP, I see 3 driver messages;
wlcore: Beacon loss detected. roles:0xff
and then receive from wpa_supplicant;
wlan0: CTRL-EVENT-DISCONNECTED bssid=88:43:e1:57:79:c0 reason=4 locally_generated=1
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="A. Guidance" auth_failures=1 duration=10
and I've not make any mistake on the pre-shared key.
Also I've used this AP for tests of different wireless adapters with success. Inclusive have use it with the same hardware platform and same kernel and sysapps (ifconfig, iw, wpa_supplicant, etc...) and a TP-Link TL-WN722N Wi-Fi adapter (ath9k_htc driver) and had no problems in associating that adapter.
Can my problems be related with an inadequate NVS file? I've generated it with the calibrate tool from ti-utils and the INI file TQS_D_1.7.ini with the command "calibrator plt calibrate". Is this the correct INI for my module (Jorjin's WG7350 - wl1273 based)?
Any ideas also why I can not get a complete APs list with the command "iw wlan0 scan"? No one as seen this behaviour before?
José Gonçalves
Quoted 6 lines · José Miguel Gonçalves
Quoted 5 lines · Arik Nemtsov
Quoted 2 lines · José Miguel Gonçalves
Any more ideas on how to debug this? Is there any specific
debug_levelmask that can apply to the driver to help it?
Quoted 7 lines
Quoted 4 lines
You can try the mask
0x63c20(it's pretty verbose, so I would put it in pastebin).Perhaps this is a genuine problem with the antenna of the card?
Nope. The AP is 1 meter away form my board (even without antenna in the card it should associate).
Too strong a signal can also cause problems, because of distortion.
Quoted 6 lines
Quoted 2 lines
Can
you verify the RSSI of the AP is ok using iw?The iw output:
This looks okay, but the RSSI value cannot be trusted blindly. There are other factors that can influence the signal quality, such as the SNR.
Quoted 6 lines
The dmesg output with debug mask set to
0x63c20:Note that with debug activated I did not see the driver's "Beacon loss detected" messages.
There could be some timing issue here. Is it always like that? Do you *always* see the "Beacon loss" messages without debugging and *never* with debugging?
--
Luca.
Quoted 20 lines · José Miguel Gonçalves
Hi Arik,
Quoted 17 lines · Arik Nemtsov
Quoted 8 lines · José Miguel Gonçalves
The dmesg output with debug mask set to
0x63c20:Note that with debug activated I did not see the driver's "Beacon loss detected" messages.
You have this line in the log:
[ 72.435000] wlan0: deauthenticated from 88:43:e1:57:79:c0 (Reason: 23)This means:
Association request rejected because the information in the Power Capability element is
unacceptable
Actually, I think this is "IEEE 802.1X authentication failed". This is the reason_code in the deauth frame. If it were the status_code in the association response, mac80211 would print "denied association instead".
Quoted 8 lines
Quoted 4 lines
In other words the AP is disconnecting you since your Tx power is inadequate (probably too high?). I'd try to limit it using iw, or just set a different regdomain where its limited.
Also I'd try with a different AP.I think that return code is a bogus caused by the driver debug code, because when I remove all the debug I see a different behaviour, i.e., after brief associating with the AP, I see 3 driver messages;
I think this is happening here because of timing. I suspect that the signal is bad so there are probably lots of retransmissions and with debugging, things can become so slow that the authentication times out. IIRC EAP has very strict timing requirements.
Quoted 10 lines
wlcore: Beacon loss detected. roles:0xff
and then receive from
wpa_supplicant;wlan0: CTRL-EVENT-DISCONNECTED bssid=88:43:e1:57:79:c0 reason=4 locally_generated=1
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="A. Guidance" auth_failures=1 duration=10
Quoted 7 lines
and I've not make any mistake on the pre-shared key.
Also I've used this AP for tests of different wireless adapters with success. Inclusive have use it with the same hardware platform and same kernel and sysapps (ifconfig, iw,
wpa_supplicant, etc...) and a TP-Link TL-WN722N Wi-Fi adapter (ath9k_htcdriver) and had no problems in associating that adapter.
Still, there may be some interoperability issue with this AP and the wl127x chip. ;)
I would try with another AP, just to see how things go. Also, I'd try with an open connection to rule out problems with authentication.
Quoted 4 lines
Can my problems be related with an inadequate NVS file? I've generated it with the calibrate tool from ti-utils and the INI file TQS_D_1.7.ini with the command "calibrator plt calibrate". Is this the correct INI for my module (Jorjin's WG7350 - wl1273 based)?
Yes, the problem can be because of a bad NVS file. Try with the "default" NVS file that is provided in linux-firmware.git. That one won't be optimal, but should work okay.
I'm not sure which FEM Jorjin's module use. Can you ask them?
I found this on github (Dick Chiang appears to work for Jorjin):
https://github.com/dickychiang/compat-wireless-r5/blob/master/jorjin/ini_files/TQS_D_1.7_WG7350_NLCP.ini
DISCLAIMER: I have no clue whether this is the correct INI file or not and I'm not claiming it's associated with TI in any way, so use it at your own risk.
Quoted 2 lines
Any ideas also why I can not get a complete APs list with the command "iw wlan0 scan"? No one as seen this behaviour before?
Many people have seen this kind of behavior and it usually indicates bad RF performance. ;)
--
Cheers,
Luca.
Quoted 7 lines · Luciano Coelho
Quoted 4 lines
Can my problems be related with an inadequate NVS file? I've generated it with the calibrate tool from ti-utils and the INI file TQS_D_1.7.ini with the command "calibrator plt calibrate". Is this the correct INI for my module (Jorjin's WG7350 - wl1273 based)?
Yes, the problem can be because of a bad NVS file. Try with the "default" NVS file that is provided in linux-firmware.git. That one won't be optimal, but should work okay.
I have the same problems with the default NVS file.
Quoted 2 lines
I'm not sure which FEM Jorjin's module use. Can you ask them?
I will ask my contact.
Quoted 8 lines
I found this on github (Dick Chiang appears to work for Jorjin):
https://github.com/dickychiang/compat-wireless-r5/blob/master/jorjin/ini_files/TQS_D_1.7_WG7350_NLCP.iniDISCLAIMER: I have no clue whether this is the correct INI file or not and I'm not claiming it's associated with TI in any way, so use it at your own risk.
Same problem after generating a new NVS file from this INI.
I will try a new AP to see how it behaves...
José Gonçalves
Quoted 28 lines · Luciano Coelho
Quoted 4 lines · José Miguel Gonçalves
Quoted 3 lines · Arik Nemtsov
On Tue, Jul 9, 2013 at 2:27 PM, José Miguel Gonçalves <[email protected]> wrote:
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Any more ideas on how to debug this? Is there any specific
debug_levelmask that can apply to the driver to help it?You can try the mask
0x63c20(it's pretty verbose, so I would put it in pastebin).Perhaps this is a genuine problem with the antenna of the card?
Nope. The AP is 1 meter away form my board (even without antenna in the card it should associate).
Too strong a signal can also cause problems, because of distortion.
Quoted 5 lines
Quoted 2 lines
Can
you verify the RSSI of the AP is ok using iw?The iw output:
This looks okay, but the RSSI value cannot be trusted blindly. There are other factors that can influence the signal quality, such as the SNR.
Quoted 2 lines
The dmesg output with debug mask set to
0x63c20:
Quoted 8 lines
Quoted 4 lines
Note that with debug activated I did not see the driver's "Beacon loss detected" messages.
There could be some timing issue here. Is it always like that? Do you *always* see the "Beacon loss" messages without debugging and *never* with debugging?
Yep, is always like that!
José Gonçalves
Quoted 3 lines · José Miguel Gonçalves
I will try a new AP to see how it behaves...
I've tested with my Android smartphone acting as an AP, without authentication, and I'm also unable to associate!
I get from iw the following error message:
wlan0 (phy #0): failed to connect to b4:07:f9:49:cc:65, status: 1: Unspecified failure
Complete log is here:
So, something is definitely wrong with my setup... but what? Hope that log has some useful info for you...
Best regards,
José Gonçalves
Quoted 10 lines · José Miguel Gonçalves
Quoted 3 lines · José Miguel Gonçalves
I will try a new AP to see how it behaves...
I've tested with my Android smartphone acting as an AP, without authentication, and I'm also unable to associate!
I get from iw the following error message:
Quoted 8 lines
wlan0 (phy #0): failed to connect to b4:07:f9:49:cc:65, status: 1: Unspecified failure
Complete log is here:
So, something is definitely wrong with my setup... but what? Hope that log has some useful info for you...
This definitely looks like RF problems. Especially this:
[ 177.575000] wlan0: send auth to b4:07:f9:49:cc:65 (try 1/3) [ 177.595000] wlan0: send auth to b4:07:f9:49:cc:65 (try 2/3) [ 177.605000] wlcore: EVENT on mbox 1 [ 177.605000] wlcore: MBOX vector: 0x100000 [ 177.610000] wlcore: MAX_TX_FAILURE_EVENT_ID [ 177.615000] wlan0: send auth to b4:07:f9:49:cc:65 (try 3/3) [ 177.640000] wlan0: authentication with b4:07:f9:49:cc:65 timed out
You are send auth requests out, but not getting anything back. Apparently you're not even getting ACKs (as pointed out by the MAX_TX_FAILURE_EVENT_ID).
Do you have a sniffer? You could try to use your TP-Link dongle with wireshark to see if it works fine as a sniffer.
My bet is that you'll see lots of retransmissions there. :\
--
Luca.
Quoted 27 lines · Luciano Coelho
Quoted 8 lines · José Miguel Gonçalves
Quoted 2 lines · José Miguel Gonçalves
I will try a new AP to see how it behaves...
I've tested with my Android smartphone acting as an AP, without authentication, and I'm also unable to associate!
I get from iw the following error message:
Quoted 8 lines
wlan0 (phy #0): failed to connect to b4:07:f9:49:cc:65, status: 1: Unspecified failure
Complete log is here:
So, something is definitely wrong with my setup... but what? Hope that log has some useful info for you...
This definitely looks like RF problems. Especially this:
[ 177.575000] wlan0: send auth to b4:07:f9:49:cc:65 (try 1/3) [ 177.595000] wlan0: send auth to b4:07:f9:49:cc:65 (try 2/3) [ 177.605000] wlcore: EVENT on mbox 1 [ 177.605000] wlcore: MBOX vector: 0x100000 [ 177.610000] wlcore: MAX_TX_FAILURE_EVENT_ID [ 177.615000] wlan0: send auth to b4:07:f9:49:cc:65 (try 3/3) [ 177.640000] wlan0: authentication with b4:07:f9:49:cc:65 timed out
Quoted 3 lines
You are send auth requests out, but not getting anything back. Apparently you're not even getting ACKs (as pointed out by the
MAX_TX_FAILURE_EVENT_ID).
Hum. I never considered RF problems because I'm testing this module with a Jorjin's development kit, so I was considering that Jorjin knows how to make PCBs for RF. Also seeing that when I remove the antenna the AP signal strength changes from -51 dBm to -73 dBm was a signal to me that the RF was OK.
Quoted 3 lines
Do you have a sniffer? You could try to use your TP-Link dongle with wireshark to see if it works fine as a sniffer.
I have a text console only system. I could put tcpdump on my system, but I think I can not monitor wireless traffic with it, or can I?
José Gonçalves
Quoted 39 lines · José Miguel Gonçalves
Quoted 28 lines · Luciano Coelho
Quoted 11 lines · José Miguel Gonçalves
Quoted 2 lines · José Miguel Gonçalves
I will try a new AP to see how it behaves...
I've tested with my Android smartphone acting as an AP, without authentication, and I'm also unable to associate!
I get from iw the following error message:
wlan0 (phy #0): failed to connect to b4:07:f9:49:cc:65, status: 1:
Unspecified failureQuoted 6 lines
Complete log is here:
So, something is definitely wrong with my setup... but what? Hope that log has some useful info for you...
This definitely looks like RF problems. Especially this:
[ 177.575000] wlan0: send auth to b4:07:f9:49:cc:65 (try 1/3) [ 177.595000] wlan0: send auth to b4:07:f9:49:cc:65 (try 2/3) [ 177.605000] wlcore: EVENT on mbox 1 [ 177.605000] wlcore: MBOX vector: 0x100000 [ 177.610000] wlcore: MAX_TX_FAILURE_EVENT_ID [ 177.615000] wlan0: send auth to b4:07:f9:49:cc:65 (try 3/3) [ 177.640000] wlan0: authentication with b4:07:f9:49:cc:65 timed outQuoted 3 lines
You are send auth requests out, but not getting anything back. Apparently you're not even getting ACKs (as pointed out by the
MAX_TX_FAILURE_EVENT_ID).Hum. I never considered RF problems because I'm testing this module with a Jorjin's development kit, so I was considering that Jorjin knows how to make PCBs for RF. Also seeing that when I remove the antenna the AP signal strength changes from -51 dBm to -73 dBm was a signal to me that the RF was OK.
Quoted 1 line
Quoted 5 lines
Quoted 2 lines
Do you have a sniffer? You could try to use your TP-Link dongle with wireshark to see if it works fine as a sniffer.
I have a text console only system. I could put tcpdump on my system, but I think I can not monitor wireless traffic with it, or can I?
I use Kismet to monitor the air on a text-only system.
Larry
Quoted 38 lines · José Miguel Gonçalves
Quoted 27 lines · Luciano Coelho
Quoted 8 lines · José Miguel Gonçalves
Quoted 2 lines · José Miguel Gonçalves
I will try a new AP to see how it behaves...
I've tested with my Android smartphone acting as an AP, without authentication, and I'm also unable to associate!
I get from iw the following error message:
Quoted 8 lines
wlan0 (phy #0): failed to connect to b4:07:f9:49:cc:65, status: 1: Unspecified failure
Complete log is here:
So, something is definitely wrong with my setup... but what? Hope that log has some useful info for you...
This definitely looks like RF problems. Especially this:
[ 177.575000] wlan0: send auth to b4:07:f9:49:cc:65 (try 1/3) [ 177.595000] wlan0: send auth to b4:07:f9:49:cc:65 (try 2/3) [ 177.605000] wlcore: EVENT on mbox 1 [ 177.605000] wlcore: MBOX vector: 0x100000 [ 177.610000] wlcore: MAX_TX_FAILURE_EVENT_ID [ 177.615000] wlan0: send auth to b4:07:f9:49:cc:65 (try 3/3) [ 177.640000] wlan0: authentication with b4:07:f9:49:cc:65 timed outQuoted 3 lines
You are send auth requests out, but not getting anything back. Apparently you're not even getting ACKs (as pointed out by the
MAX_TX_FAILURE_EVENT_ID).Hum. I never considered RF problems because I'm testing this module with a Jorjin's development kit, so I was considering that Jorjin knows how to make PCBs for RF. Also seeing that when I remove the antenna the AP signal strength changes from -51 dBm to -73 dBm was a signal to me that the RF was OK.
Quoted 1 line
Quoted 5 lines
Quoted 2 lines
Do you have a sniffer? You could try to use your TP-Link dongle with wireshark to see if it works fine as a sniffer.
I have a text console only system. I could put tcpdump on my system, but I think I can not monitor wireless traffic with it, or can I?
tcpdump will probably not be enough. But since this stuff is *wireless* you can sniff from a different PC. If you have Linux PC, just plug in your TP-Link dongle in it, launch wireshark and you should be able to sniff (unencrypted) connections between other devices easily.
You can also sniff encrypted connections, but it's slightly more difficult. Also, I've had problems when sniffing 802.11n (more specifically BA sessions), but you're not getting that far, so it should be possible to see some good results with simple sniffers.
--
Luca.
Quoted 40 lines · Larry Finger
Quoted 39 lines · José Miguel Gonçalves
Quoted 28 lines · Luciano Coelho
Quoted 11 lines · José Miguel Gonçalves
Quoted 2 lines · José Miguel Gonçalves
I will try a new AP to see how it behaves...
I've tested with my Android smartphone acting as an AP, without authentication, and I'm also unable to associate!
I get from iw the following error message:
wlan0 (phy #0): failed to connect to b4:07:f9:49:cc:65, status: 1:
Unspecified failureQuoted 6 lines
Complete log is here:
So, something is definitely wrong with my setup... but what? Hope that log has some useful info for you...
This definitely looks like RF problems. Especially this:
[ 177.575000] wlan0: send auth to b4:07:f9:49:cc:65 (try 1/3) [ 177.595000] wlan0: send auth to b4:07:f9:49:cc:65 (try 2/3) [ 177.605000] wlcore: EVENT on mbox 1 [ 177.605000] wlcore: MBOX vector: 0x100000 [ 177.610000] wlcore: MAX_TX_FAILURE_EVENT_ID [ 177.615000] wlan0: send auth to b4:07:f9:49:cc:65 (try 3/3) [ 177.640000] wlan0: authentication with b4:07:f9:49:cc:65 timed outQuoted 3 lines
You are send auth requests out, but not getting anything back. Apparently you're not even getting ACKs (as pointed out by the
MAX_TX_FAILURE_EVENT_ID).Hum. I never considered RF problems because I'm testing this module with a Jorjin's development kit, so I was considering that Jorjin knows how to make PCBs for RF. Also seeing that when I remove the antenna the AP signal strength changes from -51 dBm to -73 dBm was a signal to me that the RF was OK.
Quoted 1 line
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
Do you have a sniffer? You could try to use your TP-Link dongle with wireshark to see if it works fine as a sniffer.
I have a text console only system. I could put tcpdump on my system, but I think I can not monitor wireless traffic with it, or can I?
I use Kismet to monitor the air on a text-only system.
This looks pretty cool, I hadn't seen it before. Thanks for sharing! :)
--
Cheers,
Luca.
Hi Luca,
Quoted 7 lines · Luciano Coelho
I have a text console only system. I could put tcpdump on my system, but I think I can not monitor wireless traffic with it, or can I?
tcpdump will probably not be enough. But since this stuff is *wireless* you can sniff from a different PC. If you have Linux PC, just plug in your TP-Link dongle in it, launch wireshark and you should be able to sniff (unencrypted) connections between other devices easily.
I've setup my Linuc PC as a sniffer and yes I see a lot of of authentication frames on the air when I try to associate with my open AP (Android phone).
I've repeated the process with a TP-Link dongle and I see a clean 802.11 association sequence.
What I found strange is that I don't see "probe request" frames on the wl12xx captured frames, it starts directly with an "authentication" frame, when with the TP-Link dongle (ath9k_htc driver) the first frame sent by is a "probe request"!
I can provide the Wirehsark capture files. What is the best way to send them through the mailing list?
Best regards,
José Gonçalves
Quoted 14 lines · José Miguel Gonçalves
Hi Luca,
Quoted 7 lines · Luciano Coelho
I have a text console only system. I could put tcpdump on my system, but I think I can not monitor wireless traffic with it, or can I?
tcpdump will probably not be enough. But since this stuff is *wireless* you can sniff from a different PC. If you have Linux PC, just plug in your TP-Link dongle in it, launch wireshark and you should be able to sniff (unencrypted) connections between other devices easily.I've setup my Linuc PC as a sniffer and yes I see a lot of of authentication frames on the air when I try to associate with my open AP (Android phone).
Quoted 6 lines
I've repeated the process with a TP-Link dongle and I see a clean 802.11 association sequence.
What I found strange is that I don't see "probe request" frames on the wl12xx captured frames, it starts directly with an "authentication" frame, when with the TP-Link dongle (
ath9k_htcdriver) the first frame sent by is a "probe request"!
Usually the connection will start with a probe request, but if there is a response in the cache, we may skip it. In any case, this is probably happening because your sniffer is missing those frames (which again points to problems with RF).
Quoted 2 lines
I can provide the Wirehsark capture files. What is the best way to send them through the mailing list?
Cut only the portion that matters, so the file is small and gzip it. Small files can be sent as attachments to the list.
--
Luca.
Quoted 17 lines · Luciano Coelho
Quoted 10 lines · José Miguel Gonçalves
I've setup my Linuc PC as a sniffer and yes I see a lot of of authentication frames on the air when I try to associate with my open AP (Android phone).
I've repeated the process with a TP-Link dongle and I see a clean 802.11 association sequence.
What I found strange is that I don't see "probe request" frames on the wl12xx captured frames, it starts directly with an "authentication" frame, when with the TP-Link dongle (
ath9k_htcdriver) the first frame sent by is a "probe request"!Usually the connection will start with a probe request, but if there is a response in the cache, we may skip it. In any case, this is probably happening because your sniffer is missing those frames (which again points to problems with RF).
Quoted 5 lines
Quoted 2 lines
I can provide the Wirehsark capture files. What is the best way to send them through the mailing list?
Cut only the portion that matters, so the file is small and gzip it. Small files can be sent as attachments to the list.
Here they go...
José Gonçalves
Quoted 18 lines · José Miguel Gonçalves
Quoted 17 lines · Luciano Coelho
Quoted 10 lines · José Miguel Gonçalves
I've setup my Linuc PC as a sniffer and yes I see a lot of of authentication frames on the air when I try to associate with my open AP (Android phone).
I've repeated the process with a TP-Link dongle and I see a clean 802.11 association sequence.
What I found strange is that I don't see "probe request" frames on the wl12xx captured frames, it starts directly with an "authentication" frame, when with the TP-Link dongle (
ath9k_htcdriver) the first frame sent by is a "probe request"!Usually the connection will start with a probe request, but if there is a response in the cache, we may skip it. In any case, this is probably happening because your sniffer is missing those frames (which again points to problems with RF).
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
I can provide the Wirehsark capture files. What is the best way to send them through the mailing list?
Cut only the portion that matters, so the file is small and gzip it. Small files can be sent as attachments to the list.
Here they go...
It seems that the wl1273 is not receiving the frames correctly. What happens in the first 3 frames is all normal, but we keep retransmitting the auth frame as if the AP hadn't sent us an ACK.
1. wl1273 sends auth to the AP
2. the AP acks the frame
3. the AP sends an auth back to us
4. we should send an ACK and continue, but instead we retransmit And from then on everything is screwed up.
You could try to use the calibrator's RX statistics commands to see if you're getting lots of bad frames and such.
This could be a problem in the firmware, but my hunch is that it's RF. What kind of antenna are you using?
BTW, you should set a proper MAC address in your NVS too (calibrator's set_mac command). You could first try to set it to 00:00:00:00:00:00, which will check if the chip has a MAC in the Fuse ROM and use it from there. If that doesn't work, create your own and set it in the NVS.
The TP-Link log is "too clean", missing some frames, we don't see most of the ACKs and we don't see the auth frame being sent back from the AP.
--
Luca.
Quoted 10 lines · Luciano Coelho
It seems that the wl1273 is not receiving the frames correctly. What happens in the first 3 frames is all normal, but we keep retransmitting the auth frame as if the AP hadn't sent us an ACK.
1. wl1273 sends auth to the AP
2. the AP acks the frame
3. the AP sends an auth back to us
4. we should send an ACK and continue, but instead we retransmit And from then on everything is screwed up.
Quoted 5 lines
You could try to use the calibrator's RX statistics commands to see if you're getting lots of bad frames and such.
This could be a problem in the firmware, but my hunch is that it's RF. What kind of antenna are you using?
A standard omni-directional antenna with a 4dBi gain. After I've read your email I tried to change the antenna and immediately I got associated with the AP! But it was only from a brief period. After that I've made some more tests and I was not able to associate again. So it really seems that I've some kind of RF problem with my module :-( BTW, my module has dual-band and I've tested in both 2.4 GHz and 5 GHz bands (with appropriate antennas), both without success.
Quoted 5 lines
BTW, you should set a proper MAC address in your NVS too (calibrator's
set_maccommand). You could first try to set it to 00:00:00:00:00:00, which will check if the chip has a MAC in the Fuse ROM and use it from there. If that doesn't work, create your own and set it in the NVS.
I've already verified that the module doen not have a MAC built in. So I leaved the "DE:AD:BE:EF:00:00" MAC set, which is as good as another one (for tests), and a good reminder that I must add an EEPROM with a MAC address built in to my design.
Quoted 5 lines
The TP-Link log is "too clean", missing some frames, we don't see most of the ACKs and we don't see the auth frame being sent back from the AP.
I've captured both files with display filter "wlan.addr == <MAC>". For instance, for the log with the wl1273 based module, I used "wlan.addr == DE:AD:BE:EF:00:00". It seemed to me the appropriate filter to extract all the traffic related with that station, don't you agree?
José Gonçalves
Quoted 9 lines · Luciano Coelho
I'm not sure which FEM Jorjin's module use. Can you ask them?
I found this on github (Dick Chiang appears to work for Jorjin):
https://github.com/dickychiang/compat-wireless-r5/blob/master/jorjin/ini_files/TQS_D_1.7_WG7350_NLCP.iniDISCLAIMER: I have no clue whether this is the correct INI file or not and I'm not claiming it's associated with TI in any way, so use it at your own risk.
Just for the record, I got the information from my contact that the indicated INI file is the proper one for Jorjin's WG7350 module.
José Gonçalves