pavelmachek (![[info]](http://p-stat.livejournal.com/img/userinfo.gif){kind=small} pavelmachek) wrote,@ 2008-03-03 19:20:00 |
|
suspend to RAM in Fedora
...does not work too well. One of reasons is that, well, Fedora does not ship s2ram.
Fedora relies on pm-utils restoring video state by hand. That unfortunately means you need to be running HAL to test suspend (no easy testing from init=/bin/bash). It also relies on external utilities, so if your disk fails to wake up, you'll not read anything on screen.
s2ram has integral whitelist... which means easier testing. (It also appears to be what Fedora people dislike -- they fell in love with HAL, apparently). Anyway, you don't have to use internal whitelist. Just pass the whitelist parameters on command line to s2ram.
Pretty please, package s2ram for Fedora. It is not easy to compile s2ram, because its dependencies are lacking, and s2ram is realy vital for suspend debugging. (You can get s2ram sources at suspend.sf.net, it is GPLed).
...does not work too well. One of reasons is that, well, Fedora does not ship s2ram.
Fedora relies on pm-utils restoring video state by hand. That unfortunately means you need to be running HAL to test suspend (no easy testing from init=/bin/bash). It also relies on external utilities, so if your disk fails to wake up, you'll not read anything on screen.
s2ram has integral whitelist... which means easier testing. (It also appears to be what Fedora people dislike -- they fell in love with HAL, apparently). Anyway, you don't have to use internal whitelist. Just pass the whitelist parameters on command line to s2ram.
Pretty please, package s2ram for Fedora. It is not easy to compile s2ram, because its dependencies are lacking, and s2ram is realy vital for suspend debugging. (You can get s2ram sources at suspend.sf.net, it is GPLed).
