PS: After the first suspend, and then fixing the issue by re-inserting the kernel module, on successive suspends (same session, without rebooting, etc) the network works automatically.
** Description changed: The issue is almost the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/136836 Unlike for some others, for me an Intrepid installation with default settings has networking correctly working. After suspending and resuming, network no longer works. "rmmod forcedeth; modprobe forcedeth msi=0 msix=0" resolves the situation fully. If I add "options forcedeth msi=0 msix=0" to "/etc/modprobe.d/forcedeth" - the networking will still not automatically work after resume, but then - it is enough to run "rmmod forcedeth; modprobe forcedeth" after sleep to - get it working again. + the networking will still not automatically work after first resume, but + then it is enough to run "rmmod forcedeth; modprobe forcedeth" after + sleep to get it working again. After successive suspend+resume + everything works automatically without running commands. Linux 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux So there is a workaround, but the workaround requires root privileges and is manual work, so not good. ** Summary changed: - After sleep (suspend), NVidia MCP55 Ethernet is broken + After sleep (suspend), NVidia MCP55 Ethernet is broken [Intrepid] -- After sleep (suspend), NVidia MCP55 Ethernet is broken [Intrepid] https://bugs.launchpad.net/bugs/312144 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs