![]() | |||||||||||||
Messages in this thread |
On Sun, 29 Feb 2004 18:32:21 +0100, Måns Rullgård <mru@kth.se> wrote: > Pavel Machek <pavel@ucw.cz> writes: > >> Hi! >> >>> > Would there be any major screaming if I tried to drop CONFIG_PM_DISK? >>> > It seems noone is maintaining it, equivalent functionality is provided >>> > by swsusp, and it is confusing users... >>> >>> It may be ugly, it may be unmaintained, but I get the impression that it >>> works for some people for whom swsusp doesn't. So unless swsusp works for >>> everyone or Nigel's swsusp2 is merged, I'd suggest leaving that in. >> >> Do you have example when pmdisk works and swsusp does not? I'm not >> aware of any in recent history... > > For me, none of them (pmdisk, swsusp and swsusp2) work. I did manage > to get pmdisk to resume once, and swsusp2 makes it half-way through > the resume. Hate to hear this - 2.0 is said to work _flawlessly_ on 2.4.24 and on 2.6.2 within the bounds of more complex PM/driver issues. 2.4.25 and 2.6.3 patches are undergoing testing. If you like to try again, please have a look at http://swsusp.sf.net. There is also comprehensive FAQ and Howto on the site. You also will find a lot of user support wrt specific HW. Myself is running 2.0 on 2.4.2[345] without any stability issues whatsoever this year. In short, I am confident we can make it work for you! Regards Michael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:01 [from the cache] ©2003-2008 | |||||||||||||