quite hard in a laptop to do that.
And my hardware is Intel's (e1000e driver), not exotic at all.
I may be wrong, but imho it's clearly a kernel issue.
I do not know if an Ubuntu bug report is already done ? It is a critical issue.
quite hard in a laptop to do that.
And my hardware is Intel's (e1000e driver), not exotic at all.
I may be wrong, but imho it's clearly a kernel issue.
I do not know if an Ubuntu bug report is already done ? It is a critical issue.
Last edited by ft_; January 26th, 2013 at 04:53 PM.
Get new issues with nvidia driver:
https://bugs.launchpad.net/ubuntu/+s...x/+bug/1106117
Mine is an Intel 1000T. It's not exotic either, but...
That controller is going on 12 years-old, and I *think* the Linux maintainers clear out the cruft, from time-to-time.
My DEC "Tulip" card is equally non-exotic and old (I see them all the time at Goodwill for $4.99 USD), but...
There are zillions of DEC chipsets still being used in enterprise servers, et cetera. If they quit supporting "Tulip" chipsets, everything would come crashing down like a house of cards. So, it's a safe bet, "they" aren't going to strip support any time soon.
If it was me, I'd replace network-manager with WiCD, and see it that gets you back online...![]()
Intel ® P4 Extreme Edition 3.4 (Gallatin) || DFI ® LanParty PRO875B rev B1
Crucial ® Ballistix Tracer PC4000 1GB || Mountain Mods U2-UFO Opti-1203
XFX 7600GT 560M AGP (PV-T73A-UDF3) || Corsair HX520W Modular PSU
Somebody here wrote a workaround that I quote here.
So :
1- do ato note the ethernet controller pci numberCode:lspci
2- go towhere xx is the above numberCode:/sys/devices/pci0000:00/0000:00:xx.0/power
3- edit thefile and putCode:controlinstead ofCode:onThis operation needs to be done again back from suspend.Code:auto
Is there a bug report about that ?
Bookmarks