The bug occurs in windows 7 on the same hardware so I am likely to believe this still indicates a firmware issue... -- Kristian Erik Hermansen
On May 12, 2010 6:05 AM, "Robert Hollencamp" <rhollenc...@gmail.com> wrote: This bug also affects me, and is highly annoying. I experienced it with 9.04 (i386), 9.10 (i386), and 10.04 (amd64). Some mornings, a single 'sudo dhclient eth0' will immediately work, and some mornings (like this one) I spend about 10 minutes trying to get on the network. Vista does not have a problem with the card (I dual boot), and immediately gets an IP - its a pretty safe bet that the cable / switch / DHCP server etc are not to blame. My steps to get on the network in the morning: * try 'sudo dhclient eth0' and pray * if that fails, 'ifconfig eth0 down && ifconfig eth0 up && dhclient eth0' a few times * if that fails, 'rmmod e1000e && modprobe e1000e' and repeat ifconfig / dhclient stuff above * if all else fails, unplug the networking cable and plug it back in; repeat steps above As I mentioned earlier, I don't always have to do all of these steps; it is completely random which one will fix it first (and how long it takes). If I can provide any additional information, please let me know. -- DHCP and ping failure on e1000e https://bugs.launchpad.net/bugs/382671 You received this bug no... -- DHCP and ping failure on e1000e https://bugs.launchpad.net/bugs/382671 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
