[Bug 616984] Re: e1000e cannot connect on Lucid, Maverick (regression)

2010-11-17 Thread panther_d
Affects my box as well, Intel DG965OT mainboard. Between about 20 reboot cycles (warm and cold), I managed to get a connection exactly once. I played with network settings, fixed IP addresses, but wasn't able to get the nic to transfer any data at all. Had to revert to Karmic because this is my

[Bug 619841] Re: [REGRESSION] e1000e doesnt work on 2.6.35.

2010-11-17 Thread panther_d
Affects my box as well, Intel DG965OT mainboard. Between about 20 reboot cycles (warm and cold), I managed to get a connection exactly once. I played with network settings, fixed IP addresses, but wasn't able to get the nic to transfer any data at all. Had to revert to Karmic because this is my

[Bug 1212199] Re: 10ec:8168 [MSI P35 Neo] Network not working after resume from suspend

2013-10-18 Thread panther_d
Same problem here, since update to 13.10 All three supposed workarounds don't help - set if to promisc mode on resume (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/771857) - reload module on resume (http://superuser.com/questions/180103/ubuntu-cant-connect-to-the-internet-restart-require

[Bug 1212199] Re: 10ec:8168 [MSI P35 Neo] Network not working after resume from suspend

2013-10-18 Thread panther_d
Hm, correction: the issue is with the NetworkManager hanging upon resume - no matter which eth hardware is used (I just removed the realtec card and use a intel NIC (e1000e), same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1027202] Re: Does not connect (to wired network) after suspend

2013-10-18 Thread panther_d
Got the same issue after updating to Saucy yesterday. Restarting NetworkManager helps, but that's not a real option especially for non-computer-literate users... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.n

[Bug 1027202] Re: Does not connect (to wired network) after suspend

2013-10-19 Thread panther_d
I have a workaround that isn't particularly elegant but does the trick for me: have the NetworkManager automatically restart at resume. 1. add file to /etc/pm/sleep.d/ , e.g. call it 99_restart-network-manager, and make it executable 2. in the file, put #!/bin/bash case "${1}" in resume|th

[Bug 1232454] Re: Often automatic suspend dialog when I unlock

2013-10-29 Thread panther_d
Agree, and am also very interested in any way to get rid of this dialog. I'm sorry to have to say that this dialog is one of the stupidest UI design ideas I've ever come across... :-\ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. ht

[Bug 619841] Re: [REGRESSION] e1000e doesnt work on 2.6.35.

2011-03-07 Thread panther_d
Agree; if nics weren't 5 bucks a piece I'd have moved away from Ubuntu thanks to this bug and the fact it's still open. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/619841 Title: [REGRESSION] e1000