[ath9k-devel] ath9k not connecting to one particular network..

[Peter Stuge <peter@stuge.se>]

Me and other ath9k users have experienced various similar problems
for years, across different ath9k hardware. NM was usually not part
of the picture, at least never in my case, my problems were always
with only wpa_supplicant, if that.

ath9k has improved, but I still have "soft" issues that nobody at QCA
will spend time on, because I'm not significant enough for remote
debugging, because QCA doesn't talk about hardware details with
users, and because problems (obviously) can't be reproduced in
their lab.

Ironic that when you have an issue and get attention, it seems to lie
outside ath9k. (It may still be the driver's fault, just that the
problem isn't triggered when starting wpa_supplicant manually.)


Linus Torvalds wrote:
> I did not reboot or force systemd/dbusd to
> reload their files (if that is even possible).

systemctl [--system] daemon-reload


I hate to say this, but part of me hopes that you'll have some more
problems with the Pixel wifi. :\


//Peter