eth0 does not work after shutdown/start, but works when restart
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
eth0 does not work after shutdown/start, but works when restart
When I shutdown computer and start it up, eth0 doesn't seem to show up (though lspci sees ethernet card and modules are loaded).
When i reboot (which is exactly the same, in my opinion), it works good.
I'm using Sabayon GNU/Linux, Gnome Network Manager applet.
Reboot is not the same in all cases as shutdown. Reboot may be considered a warm boot in some instances rather than a full cold boot. So that leaves us to question what is being saved in the warm boot and not the cold boot. Bios setting, router issue, apm/acpi issue? Someone else may have better idea.
Firstly, thanks for reply!
Though I don't think it is bios or router issue, since everything worked extremely well couple of days ago (and I usually keep updated every day).
I think it is either new kernel bug, or new gnome-network-manager bug. But I'm not sure, cause I have no proof.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.