Re: Doesn't reconnect to wifi after resuming from suspend

[Ferry Toth <ftoth telfort nl>]

poma wrote:

> On 05.02.2015 22:00, Ferry Toth wrote:
> > poma wrote:
> >
> > > On 05.02.2015 20:12, Ferry Toth wrote:
> > >
> > > > Would that be after a certain kernel? But I used 14.04 with kernel 3.17
> > > > (no problem) and 14.10 with 3.17 (and now 3.18)
> > >
> > > See if it can help
> > > https://wireless.wiki.kernel.org/en/users/drivers/ath9k/bugs
> >
> > Thanks by I don't find my case there.
>
> /etc/systemd/system/ath9k-reload.service
> [Unit]
> Description=Reload Atheros 802.11n wireless LAN cards driver
> After=hibernate.target suspend.target hybrid-sleep.target
>
> [Service]
> Type=oneshot
> ExecStart=/usr/sbin/modprobe -r ath9k
> ExecStart=/usr/sbin/modprobe ath9k
>
> [Install]
> WantedBy=hibernate.target suspend.target hybrid-sleep.target
>
>
> # systemctl enable ath9k-reload.service
>
> # systemctl suspend
>           & RESUME
>
> # systemctl hibernate
>           & THAW
>
> # systemctl hybrid-sleep
>           & RESUME||THAW
>
>
> Does it work?

Actually no, it doesn't. I already suspected that as I tried other similar 
(non-systemd) scripts that restart stuff on resume.

With this script, it doesn't even autoreconnect on boot (which did work 
before).

I am starting to believe that after the drivers go up, an event scan is 
started, and the ath9k incorrectly reports that it is done (but might not 
be, as I have 2.4G and 5G and am trying to reconnect to the 5G).

Just restarting drivers won't fix this (if it is indeed so).

I need a delay after resume and scan, and before the autoconnect starts.


BTW when I do:
lsmod | grep ath

ath9k                 162133  0 
ath9k_common           25638  1 ath9k
ath9k_hw              460416  2 ath9k_common,ath9k
ath                    29397  3 ath9k_common,ath9k,ath9k_hw
mac80211              697212  1 ath9k
ath3k                  13381  0 
cfg80211              520257  4 ath,ath9k_common,ath9k,mac80211
bluetooth             486890  7 bnep,ath3k,btusb,rfcomm