Could not connect to wpa_supplicant: wlan0 - re-trying

Bartlomiej Grzeskowiak bartlomiej.grzeskowiak at
Tue Dec 15 04:00:41 PST 2015

Great it works now.

(I test the module on reference design board)
After issuing "strace wpa_cli -i wlan0" the problem with /tmp folder
was reported:
bind(3, {sa_family=AF_FILE, path="/tmp/wpa_ctrl_1095-5"}, 110) = -1
EROFS (Read-only file system)

After mounting tmpfs:
mount -t tmpfs -o size=12m tmpfs /tmp/

everything works fine.

Thank you

2015-12-15 9:07 GMT+01:00 Michal Kazior <michal.kazior at>:
> On 15 December 2015 at 08:59, Bartlomiej Grzeskowiak
> <bartlomiej.grzeskowiak at> wrote:
>> I work on embedded device and I am configuring the WLAN module
>> (QCA6174 - ath10k driver) with wpa_supplicant.
>> I load the driver modules (backports-20151120):
>> insmod /lib/modules/3.10.65-b2196-h301/wlan/compat.ko;
>> insmod lib/modules/3.10.65-b2196-h301/wlan/cfg80211.ko;
>> insmod /lib/modules/3.10.65-b2196-h301/wlan/mac80211.ko;
>> insmod /lib/modules/3.10.65-b2196-h301/wlan/ath.ko;
>> insmod /lib/modules/3.10.65-b2196-h301/wlan/ath10k_core.ko skip_otp=y;
>> insmod /lib/modules/3.10.65-b2196-h301/wlan/ath10k_pci.ko
>> I start the wpa_supplicant (default wpa_supplicant.conf):
>> wpa_supplicant -dd -Dwext -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -B
>> [  182.257304] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
>> everything seems to work fine. I see the wlan0 interface,I can scan
>> with iwlist, /var/run/wpa_supplicant/wlan0 exist.
>> But I can not use wpa_cli interface:
>>  #wpa_cli
>>  wpa_cli v2.4
>>  Copyright (c) 2004-2015, Jouni Malinen <j at> and contributors
>>  Selected interface 'wlan0'
>> Interactive mode
>> Could not connect to wpa_supplicant: wlan0 - re-trying
>> Do you have any hints how can I track down the problem ?
> I remember having trouble when I had /tmp mounted via 9p in my VM
> which didn't work quite well with unix sockets. Mounting tmpfs on /tmp
> helped.
> Perhaps you're having a similar problem, i.e. something gets in the
> way of creating a wpa_cli socket in /tmp? Or maybe it's a
> permission/ownership problem?
> I suggest you check wpa_supplicant logs (-dddd) to check if there are
> any suspicious messages and run `strace wpa_cli -i wlan0` or `strace
> wpa_cli -i wlan0 stat` to see if there's any syscall failing
> (typically bind, sendto or recvfrom).
> Michał

More information about the Hostap mailing list