On 15 March 2015 at 00:35, Paul Sokolovsky email@example.com wrote:
As was noted in recent messages on the list, recent Debian builds (e.g. #118, #124) has WiFi working. However, I had troubles connecting to my Internet access point, with wpa_supplicant (or kernel while running it) throwing timeout errors waiting for AP authentication response.
After fiddling with it, I remembered that the AP is 802.11g, grabbed a 802.11n mobile router, and the HiKey connected to it without issues.
I guess I know what do you mean. When I changed my AP from 11n to 11g (by limiting the channel speed up to 54Mbps/11g instead of 300Mbps/11n), it got much more harder to associate with the AP. In the log, I can see a lot of beacon loss/ reassociation messages, repetitively. But that's not any software issue. My guess that's due to weak signals. 11n got more antennas and new algorithm. So in 11n's case, the physical link quality gets better.
Try echo: echo 0x3C01 > /sys/module/wlcore/parameters/debug_level to see my messages from wlcore. Ref: http://processors.wiki.ti.com/index.php/WL18xx_Driver_Debug
I tried to play with few seemingly related wpa_supplication config params,
wpa_supplicant -B -iwlan0 -c/etc/wpa_supplicant.conf -Dnl80211 That's mine and it works. And my AP is configured to use WPA2-PSK [AES].
but nothing had an effect (btw, it's a bit of chore, because on stop, wpa_supplicant brings wlan0 down, and it's broken after that, not up'able again; "reboot" doesn't work, and there's no hardware reset button, so disconnecting power jack is the only choice). So, I figure the problem is in driver.
It's easy to reproduce this error when you run 'iw wlan0 disconnect', then run 'iw wlan0 scan' repeatedly. But I don't think this is a driver problem. Since,
In my tests, I found so far: all problems can be grouped into two categories: 1) wlcore: ERROR SW watchdog interrupt received! That's a firmware watchdog timer interrupt and reported from FW to the host. 2) wlcore: Scan completed due to error. That's a scan timeout error. By changing the timeout value from 30 seconds to longer does'n help. And again, here I didn't see any SDIO or wlcore driver side errors. The only thing noticeable is just a firmware side timeout.
I'm currently reading TI's docs on WL1835MOD (http://processors.wiki.ti.com/index.php/WL18xx) to see if there's anything related, but if someone may have any hints, that would be appreciated.
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ Dev mailing list Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev