On Mon, Oct 30, 2006 at 10:42:25AM +0100, Thomas Maier wrote: > Hi David, > > thought nobody's going to look at this, it's almost a year :).
swsusp bugs are low priority and there is still lots of work going on upstream to make it more stable driver wise. > Last week I switched to Edgy (Ubuntu). While I was still with Debian, > I stopped using suspend to RAM (months ago) and used suspend to disk > instead. The in-kernel implementation is quite stable on my notebook > but sucks in all other aspects (e.g. it is _annoyingly_ slow). Being > extra careful when hibernating (old habit from the days when things > tended to freeze), my last uptime was 72 days. As a side note I'd > suggest (or, rather _beg_) offering suspend2-enabled kernels (see > suspend2.net), which works amazingly fast and has a couple of other nice > characteristics (better concept, nice community, nice developer > (especially in contrast to the in-kernel suspend), etc.). In short: > in-kernel suspend works but sucks, suspend2 works and is nice. Easy > choice, I'd think :). Should I file a wishlist-bug? suspend2 adds a gif decoder and is not even included in the bloated ubuntu kernel, see the debian kernel policy the only sucess of suspend2 is to unload a bunch of drivers and reoload them, that's most of the difference for the user. you really want to use uswsusp as it has the advantages of suspend2, while not having akward not mergeable code. so no your wishlist bug is not welcome, but would be useless see http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines as you didn't tell if you tested the 2.6.18 linux-images and switched distribution the bug can most probably be closed. > Good luck with the release, Thomas. > -- > Thomas Maier - Research Assistant - University of Kassel, Germany thanks + best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
