Comment 8 for bug 353035

I'm now running Jaunty final, and suspend/resume now works when forcing use of the vesa driver by using an xorg.conf:

Section "Device"
Identifier "Configured Video Device"
Driver "vesa"
EndSection

Therefore the problem would seem to be in the xserver-xorg-driver-ati package, so I've added this bug to that package.
Perhaps my previous test using the vesa driver was flawed in some way.

I've also confirmed that resume does not work after having booted into X using the radeon driver, even if I switch to a VT, kill gdm and rmmod the radeon and drm modules. I have compared the active modules (lsmod) and running processes (ps aux) in the two cases:

1. Boot into a terminal using text kernel parameter
2. Boot into X, switch to VT, kill gdm, rmmod radeon, rmmod drm

and there is no difference in the modules in use and the processes running, however in case 1, suspend/resume works, and in case 2 resume fails as described above. It seems to my (uninformed) eye that starting X using the radeon driver causes a problem (perhaps putting the display hardware in a particular state) which prevents successful resume until after a reboot, even if X etc is subsequently killed.

I have also tried the packages from https://launchpad.net/~tormodvolden/+archive/ppa and the problem still exists. I hope this additional information is useful.