Solved for me, installing the nvidia-graphics-drivers -275.09.07-0ubuntu1~edgers~natty from xorg-edgers PPA. I didn't need any other packages, so I used a pin on that PPA, forcing only the nvidia-graphics-driver version.
"May interfere", because I think that this bug is related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604094 (chvt breaks resume with binary nvidia driver), since I never could resume properly from console (using single). So, another console mode, could interfere, I don't know...
My overall impression is that this bug is fixed with the new nvidia driver.
Now the '/usr/share/checkbox/scripts/suspend_test --full' completes ok, except for the first test "suspend triggered via dbus message": "SUSPEND FAILED, did not go to sleep".
Solved for me, installing the nvidia- graphics- drivers -275.09. 07-0ubuntu1~ edgers~ natty from xorg-edgers PPA. I didn't need any other packages, so I used a pin on that PPA, forcing only the nvidia- graphics- driver version.
But I did another thing that may interfere: http:// paolobernardi. wordpress. com/2011/ 05/01/fix- plymouth- on-ubuntu- after-installin g-nvidia- or-ati- proprietary- drivers- for-ubuntu- 11-04-natty/, which installs uvesafb and configures grub to pass mode_option= 1024x768- 24 to linux.
"May interfere", because I think that this bug is related to http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 604094 (chvt breaks resume with binary nvidia driver), since I never could resume properly from console (using single). So, another console mode, could interfere, I don't know...
My overall impression is that this bug is fixed with the new nvidia driver.
Now the '/usr/share/ checkbox/ scripts/ suspend_ test --full' completes ok, except for the first test "suspend triggered via dbus message": "SUSPEND FAILED, did not go to sleep".