tracking down suspend/hibernate bugs?

Paul S paulatgm at
Tue Jan 15 01:17:36 UTC 2008

Matthew Garrett said the following on 01/14/2008 06:42 PM:
> On Mon, Jan 14, 2008 at 11:10:49AM -0800, Matt Price wrote:
>> sudo pm-suspend
> Right, so it sounds more like the issue here is that we're passing 
> quirks that are breaking your system. For reference, the quirks that are 
> used by default on Ubuntu are currently:
> --quirk-dpms-on
> --quirk-vbestate-restore
> --quirk-vbemode-restore
> --quirk-vga-mode3
> --quirk-vbe-post
> --quirk-reset-brightness
> If you pass those, does it fail? If so, can you try to figure out which 
> one is causing it?

I've tried this twice and it succeeded both times:

paul :~$ sudo pm-suspend --quirk-dpms-on --quirk-vga-mode3 
--quirk-reset-brightness --quirk-vbe-post --quirk-vbemode-restore 

I must admit I am surprised because I have an nvidia driver 169.07 and 
always thought it did not support use of vbetools.  In fact the 
nvidia-glx-new README says:

         o Some distributions use a tool called vbetool to save and 
restore VGA
           adapter state. This tool is incompatible with NVIDIA GPUs' Video
           BIOSes and is likely to lead to problems restoring the GPU 
and its
           state. Disabling calls to this tool in your distribution's init
           scripts may improve power management reliability.

But the proof is in the success.

By the way, I don't see --quirk-reset-brightness in the pm-suspend man 

Still no idea why kde-power-manager can't start a suspend....

More information about the Ubuntu-devel-discuss mailing list