Gagalo Pro: No network after suspend to ram

[diederick2]

Hi,

About half of the times I wake up my Galago Pro from standby (suspend to ram) I have no network, even though it was working fine before. The wifi icon isn't there, and plugging a cable doesn't do anything either. I have tried restarting NetworkManager, but the system log show me it won't:

Sep 29 19:30:09 m3lvin systemd[1]: Failed to start Network Manager.
Sep 29 19:30:09 m3lvin systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart.
Sep 29 19:30:09 m3lvin systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2.
Sep 29 19:30:09 m3lvin systemd[1]: Stopped Network Manager.
Sep 29 19:30:09 m3lvin systemd[1]: Starting Network Manager...
Sep 29 19:30:24 m3lvin sudo[14162]: pam_unix(sudo:session): session closed for user root
Sep 29 19:30:29 m3lvin sudo[14198]: diederick : TTY=pts/1 ; PWD=/home/diederick ; USER=root ; COMMAND=/bin/systemctl restart NetworkManager
Sep 29 19:30:29 m3lvin sudo[14198]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 29 19:30:29 m3lvin systemd[1]: Stopped Network Manager.
Sep 29 19:30:29 m3lvin systemd[1]: Starting Network Manager...
Sep 29 19:31:59 m3lvin systemd[1]: NetworkManager.service: Start operation timed out. Terminating.
Sep 29 19:31:59 m3lvin systemd[1]: NetworkManager.service: Failed with result 'timeout'.
Sep 29 19:31:59 m3lvin systemd[1]: Failed to start Network Manager.
Sep 29 19:31:59 m3lvin sudo[14198]: pam_unix(sudo:session): session closed for user root
Sep 29 19:32:00 m3lvin systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart.
Sep 29 19:32:00 m3lvin systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1.
Sep 29 19:32:00 m3lvin systemd[1]: Stopped Network Manager.
Sep 29 19:32:00 m3lvin systemd[1]: Starting Network Manager...
Sep 29 19:33:30 m3lvin systemd[1]: NetworkManager.service: Start operation timed out. Terminating.
Sep 29 19:33:30 m3lvin systemd[1]: NetworkManager.service: Failed with result 'timeout'.
Sep 29 19:33:30 m3lvin systemd[1]: Failed to start Network Manager.
Sep 29 19:33:30 m3lvin systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart.
Sep 29 19:33:30 m3lvin systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2.
Sep 29 19:33:30 m3lvin systemd[1]: Stopped Network Manager.
Sep 29 19:33:30 m3lvin systemd[1]: Starting Network Manager...
Sep 29 19:35:00 m3lvin systemd[1]: NetworkManager.service: Start operation timed out. Terminating.
Sep 29 19:35:00 m3lvin systemd[1]: NetworkManager.service: Failed with result 'timeout'.
Sep 29 19:35:00 m3lvin systemd[1]: Failed to start Network Manager.
Sep 29 19:35:01 m3lvin systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart.
Sep 29 19:35:01 m3lvin systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 3.
Sep 29 19:35:01 m3lvin systemd[1]: Stopped Network Manager.
Sep 29 19:35:01 m3lvin systemd[1]: Starting Network Manager...
Sep 29 19:36:31 m3lvin systemd[1]: NetworkManager.service: Start operation timed out. Terminating.
Sep 29 19:36:31 m3lvin systemd[1]: NetworkManager.service: Failed with result 'timeout'.
Sep 29 19:36:31 m3lvin systemd[1]: Failed to start Network Manager.
Sep 29 19:36:31 m3lvin systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart.
Sep 29 19:36:31 m3lvin systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 4.
Sep 29 19:36:31 m3lvin systemd[1]: Stopped Network Manager.
Sep 29 19:36:31 m3lvin systemd[1]: Starting Network Manager...

Why is NetworkManager having trouble restarting?

[aaronhoneycutt]

Hello,

What happens if you issue this command in a terminal?:

sudo systemctl restart NetworkManager.service

Is this on Ubuntu 16.04 or Ubuntu 18.04?

[diederick2]

Hi, thanks for the reply. You can see in the log that I posted what happened after that command (see 19:30:29): NetworkManager tries to restart but fails repeatedly. I see these in the logs.

My About window shows Pop!_OS 18.04 LTS.

[aaronhoneycutt]

Let's reinstall the NetworkManager:

sudo apt install --reinstall NetworkManager

We also have an article for wireless we may want to look at as well:

https://support.system76.com/articles/wireless/

[wildmanne39]

Hello, I do not know much about Pop!_OS except it is based on Ubuntu but it may help people to diagnose your wifi issue if you click on the wireless script in my signature and post the results for review.

Thanks

[aaronhoneycutt]

Hello, I do not know much about Pop!_OS except it is based on Ubuntu but it may help people to diagnose your wifi issue if you click on the wireless script in my signature and post the results for review.

Thanks

You should update that script as it uses gksudo and kdesudo which are both packages that are old and I think both are not in the Ubuntu repository any longer.

[wildmanne39]

You should update that script as it uses gksudo and kdesudo which are both packages that are old and I think both are not in the Ubuntu repository any longer.

Thanks aaronhoneycutt, I am in the process of updating it right now with a few new commands so I will make those changes as well.

[diederick2]

Let's reinstall the NetworkManager:

sudo apt install --reinstall NetworkManager

We also have an article for wireless we may want to look at as well:

https://support.system76.com/articles/wireless/

This is a brand new Galago Pro, so I can you tell me what reinstalling NetworkManager would accomplish?

[diederick2]

Thanks aaronhoneycutt, I am in the process of updating it right now with a few new commands so I will make those changes as well.

The script ran without problem, recognised everything. The wifi card is a Intel Corporation Wireless 8265 / 8275, which I didn't find in the list of supported cards, but I can't believe System76 would build a Linux laptop with a WiFi card that is not supported.

What do I look for in that output? It said its too big to paste here, but you can find it here.

And here is the output of the script when the problem occurred,just in case that is relevant.

[wildmanne39]

There are a few things that I see that can be tweaked but lets see if turning off power management will help fix the issue.

sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

Thanks