Http://www.cnblogs.com/jcli/archive/2012/04/09/2439674.html
Today, I forgot to plug in the power cord on my laptop. After a trip, I came back and found that I had no power to shut down. After restarting, the system finds that the network cannot be connected. The system prompts "Disable the network" and searches the Internet:
Http://ubuntuforums.org/showthread.php? T = 1505217
The reason is as follows:
Have you had a failed hibernate that locked up and you had to do a hard reboot?
Apparently, the problem is that the network manager marks network interfaces disabled during the hibernate, and re-enables them on suspend. when hibernate fails and the user has to reboot, the second step never executes, and the interfaces remain disabled, as far as nm is concerned.
See http://osdir.com/ml/debian-bugs-dist.../msg07864.html (or Launchpad bug #524565) for details and a fix (which worked for me ):
Code:
service network-manager stop rm /var/lib/NetworkManager/NetworkManager.state service network-manager start
The possible cause is that the network manager disables the network when the computer is not powered or sleep, and then restarts the network when it is suspended. However, when the computer is not powered or sleep, the second step is not executed, so the system settings are always in the stopped state. Run the command in the red font above. Thanks to the omnipotent Google.
Original article. Please indicate the source for reprinting. Thank you!
Today, I forgot to plug in the power cord on my laptop. After a trip, I came back and found that I had no power to shut down. After restarting, the system finds that the network cannot be connected. The system prompts "Disable the network" and searches the Internet:
Http://ubuntuforums.org/showthread.php? T = 1505217
The reason is as follows:
Have you had a failed hibernate that locked up and you had to do a hard reboot?
Apparently, the problem is that the network manager marks network interfaces disabled during the hibernate, and re-enables them on suspend. when hibernate fails and the user has to reboot, the second step never executes, and the interfaces remain disabled, as far as nm is concerned.
See http://osdir.com/ml/debian-bugs-dist.../msg07864.html (or Launchpad bug #524565) for details and a fix (which worked for me ):
Code:
service network-manager stop rm /var/lib/NetworkManager/NetworkManager.state service network-manager start
The possible cause is that the network manager disables the network when the computer is not powered or sleep, and then restarts the network when it is suspended. However, when the computer is not powered or sleep, the second step is not executed, so the system settings are always in the stopped state. Run the command in the red font above. Thanks to the omnipotent Google.