Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Gagalo Pro: No network after suspend to ram

  1. #1
    Join Date
    Sep 2018
    Beans
    9

    Gagalo Pro: No network after suspend to ram

    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:

    Code:
    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?

  2. #2
    Join Date
    Oct 2013
    Beans
    5

    Re: Gagalo Pro: No network after suspend to ram

    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?

  3. #3
    Join Date
    Sep 2018
    Beans
    9

    Re: Gagalo Pro: No network after suspend to ram

    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.

  4. #4
    Join Date
    Oct 2013
    Beans
    5

    Re: Gagalo Pro: No network after suspend to ram

    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/

  5. #5
    Join Date
    Feb 2008
    Location
    Texas
    Beans
    27,164
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Gagalo Pro: No network after suspend to ram

    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
    Last edited by wildmanne39; October 1st, 2018 at 11:13 PM.

  6. #6
    Join Date
    Oct 2013
    Beans
    5

    Re: Gagalo Pro: No network after suspend to ram

    Quote Originally Posted by wildmanne39 View Post
    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.

  7. #7
    Join Date
    Feb 2008
    Location
    Texas
    Beans
    27,164
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Gagalo Pro: No network after suspend to ram

    Quote Originally Posted by aaronhoneycutt View Post
    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.

  8. #8
    Join Date
    Sep 2018
    Beans
    9

    Re: Gagalo Pro: No network after suspend to ram

    Quote Originally Posted by aaronhoneycutt View Post
    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?
    Last edited by diederick2; October 2nd, 2018 at 07:54 AM.

  9. #9
    Join Date
    Sep 2018
    Beans
    9

    Re: Gagalo Pro: No network after suspend to ram

    Quote Originally Posted by wildmanne39 View Post
    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.
    Last edited by diederick2; October 2nd, 2018 at 09:16 PM.

  10. #10
    Join Date
    Feb 2008
    Location
    Texas
    Beans
    27,164
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Gagalo Pro: No network after suspend to ram

    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.
    Code:
    sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
    Thanks

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •