Plamen Dimitrov <plamen.dimitrov@xxxxxxxxxxx> wrote: > On 4/23/24 10:49, Ping-Ke Shih wrote: > > Plamen Dimitrov<plamen.dimitrov@xxxxxxxxxxx> wrote: > >>> Another try is to disable power save by 'iw' command right after booting, like > >>> sudo iw wlan0 set power_save off > >> I had to take a while to make sure that this indeed worked and so far it took some days without any failure > >> which makes me guess that this has actually helped. I even tried rebooting again and the problem is still > >> likely fixed. I will monitor the situation but for the sake of sustainable solution, I guess the above > >> does set a setting that we could not set in any other way? It seems to work and that's great, I just > wonder > >> if running `sudo iw wlan0 set power_save off` upon each reboot or kernel update can be replaced with > something > >> more long lasting. > >> > > If you use network manager as WiFi controller, set 'wifi.powersave = 2' in config file [1]. > > > > [1]https://gist.github.com/jcberthon/ea8cfe278998968ba7c5a95344bc8b55 > > So I applied this with the wifi card failing again with the above errors. Then I tried the same NetworkManager > config > but with a full reboot and the wifi crashed again. I reissued the previous `iw` comment to set this but > then the wifi > crashed again before and after additional cold reboot. I am really not sure what is going on here. Should > I look for > more logs once this happens again despite the powersave mode? Using 'sudo iw wlan0 get power_save' to check power save status expected.