severity 500794 whishlist tags 500794 +willnotfix thanks First of all, if you know what command-line arguments you need to suspend you can use those with --force. If you use hal (via gnome-power-manager) you can create a .fdi file that will by-pass the white-list.
Bastian Blank schreef: > On Wed, Oct 01, 2008 at 07:54:54PM +0200, Sven Joachim wrote: >> But it does not know whether the machine will come up again, and even if >> that's the case, the screen may remain blank forever. Such is the case >> on my desktop. :-( > > Each kernel driver is allowed to veto suspension. The video card in a machine and its driver is of course of great influence on the ability of the machine to supsend and resume, but the not the only factor. There is also for example the BIOS. >> There's little point in suspending a machine that won't resume >> correctly afterwards. > > Do you have a number which amount of machines have problems? The number of machines that didn't came up by itself always used to be much bigger than the number that did. I must confess that I'm not following that number that well at the moment. Also there are some maior changes in very new kernels (.27 ?) that will change that number dramatically. The reasoning always was: better safe than sorry. Let users first figure out what is safe consciously, before trying to suspend without knowing resume will succeed (and risking data-loss). grts Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
