We're closing this bug since it is has been some time with no response
from the original reporter. However, if the issue still exists please
feel free to reopen with the requested information.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
Network won't re-connect after su
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please try the workaround in bug 288281 . If it works, then your problem
is a duplicate of that bug - please unsubscribe from this bug and click
the "Affects Me Too" link on bug 288281 .
If the workaround does not
I also have a similar problem with Interpid. My motherboard is Biostar
using nvidia chipset. The network works if you unload forcedeth before
suspend and reload it again after resume.
before suspend
sudo modprobe -r forcedeth
after resume
sudo modprobe forcedeth
I dont know how to do this automa
I don't think this is a duplicate...they're similar but in my case the
forcedeth module is loaded after resume.
I just tried manually unloading forcedeth after resume and then re-
loading it. When I do so the system claims to have detected a link but
NetworkManager can't get an IP address.
--
Ne
For me networking fails after hibernation (suspend to disk), haven't
tried suspending to RAM yet (which worked not at all before anyway).
I've filed bug 283462 about this and wanted to notify you, since this
bug sounds like a duplicate.
--
Network won't re-connect after suspend to RAM
https://bu
