NetworkManager flakey after sleep/wakeup

[Kurtbw]

I've found that after a sleep/wakeup cycle, NetworkManager sometimes can't find a previously used wireless network.

A "sudo killall NetworkManager" followed by "sudo NetworkManager" fixes things.

Just wondering if that's a Linux or KDE issue.

[leszek]

This might be a hardware limitation/bug in the driver.
Which wifi chip is it?

[Kurtbw]

Looks like the machine has a Qualcomm Atheros AR9285...

...isn't that one with issues running under Linux?

[leszek]

This one should be fully supported by the ath9k driver which is one of the best in linux.
So I wonder what could be wrong there.

Do you have an Intel or AMD based CPU. I know that Intel based systems are a little bit faster turning everything on again after a suspend.
AMD systems tend to use a little bit more time (up to 30 seconds) to get everything going.

[AJSlye]

Could this bug report be related to your issue?
https://bugs.launchpad.net/ubuntu/+sourc...ug/1574347

[rocky7x]

I am experiencing the same behavior. A better way for restarting the Network Manager is:

sudo service network-manager restart

My wifi chip is Intel Corporation Wireless 7260 (rev 6b)

[leszek]

Very strange as according to the bug it should be fixed. Though others on that bug report still seem to have the same issue.
So maybe comment on that bug to have it reopened.

[Kurtbw]

This one should be fully supported by the ath9k driver which is one of the best in linux.
So I wonder what could be wrong there.

Do you have an Intel or AMD based CPU. I know that Intel based systems are a little bit faster turning everything on again after a suspend.
AMD systems tend to use a little bit more time (up to 30 seconds) to get everything going.

Indeed, I checked.  Maui 1 has the ath9k driver loading, so it doesn't appear to be a generic driver issue.

I'm on an Intel-based system.  Could be related to the system firing up quickly after a suspend, as you indicated.

Part of the bug is -- it's intermittent.  Things would be easier to diagnose if the daggum code simply caused the wifi to conk out completely.

I'll take a look at the bug AJSlye posted.

[Kurtbw]

Could this bug report be related to your issue?
https://bugs.launchpad.net/ubuntu/+sourc...ug/1574347

Ummm... not sure, but could be.

I'll have to do some checking when it happens again.  Whatever it is, this bug certainly isn't happening enough for me to draw conclusions at this point.

I can say Maui 1 behaves a lot better than Netrunner 17 in this regard.