Jump to content
  • 0

NetworkManager inactive after hibernation


gnuisance
 Share

Question

7 answers to this question

Recommended Posts

  • 0

I believe I have that issue too.  I rarely use hibernate, so too lazy to fix it.

I do know however, I had an issue with sleep and found that the linux ethernet driver didn't like to sleep for me.  The manufacturer's driver had other issues, but would sleep.  So I would trade them out (I still do this):

# cat /etc/pm/sleep.d/77ethernet
#!/bin/bash 
case $1 in 
   suspend) 
	modprobe -r r8169
	modprobe r8168
	ethtool -s eth0 wol bg
      ;; 
   resume) 
	modprobe -r r8168
	modprobe r8169
	ethtool -s eth0 wol bg
      ;; 
esac

Every new kernel I rebuild the manufacturer driver too. 

So there's some extra confusion if you decide to go after this.

Link to comment
Share on other sites

  • 0

The issue was I want to avoid restarting NetworkManager manually after hibernation.  After a much closer look I realize my computer was not in hibernation but suspended.  The previously posted script allowed for network connectivity without manually restarting NetworkManager, resolving my issue.

Link to comment
Share on other sites

  • 0

Hmm, kinda late, but I just wanted to point out that I did have the problem in hibernate mode and it's definitely hibernation, powered off.  And yeah, the restart in the 77ethernet file does the trick.  So I guess that code executes for suspend and hibernation?  Hope I'm not misleading people here, it was ages ago I hunted that down.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...