Re:Ubuntu 10.10 (Maverick Meerkat) Release Candidate
by FooBarWidget on Thursday September 30, 2010 @03:31PM
(#1744501)
Suspend/resume has been broken in various ways on various hardware for years. This makes me wonder whether they're bugs in Linux or bugs in hardware for which each one requires a different workaround. In case of the latter I can imagine why things stay broken for such a long time.
[ Parent
| on HN ]
Re:Ubuntu 10.10 (Maverick Meerkat) Release Candidate
by loire280 on Thursday September 30, 2010 @04:44PM
(#1744763)
In my experience, suspend/resume breaks because of device drivers failing to put their components to sleep properly. The biggest culprit is wireless drivers.
It may be that as they improve wireless support by including more drivers and making it easier to use proprietary ones, they're making the suspend/resume problem harder and harder.
I've fixed several problems like this on a per-machine basis, but the fixes are specific to each piece of hardware (read: "this obviously would break something for someone else if included in the distro").