Ok, I've finished celebrating the first successful suspend/resume with g-p-m since I switched to Linux... :-)
a) /root/pm-suspend.log is empty when using your (quite elegant) pm-suspend script
b) with the original pm-suspend symlink, suspend AND resume work just fine!
So as far as I am concerned, everything is fine. Perhaps just the "negative logic" lines of the patch should be cancelled with the "sensible" rest being left in place? Will your changes propagate to Ubuntu? Can I do anything?
Concerning the fdi file for my computer, matching vendor, product ID and "linux.driver.info" is no problem - but my setup doesn't need any quirks and even if I explicitly switch off all of them (see above), the dbus-suspend-call seems to apply some of them... Furthermore, I suspect that there are several more people affected by this bug. However, most fglrx-users are used to broken suspends and likely to blame ati, the kernel or X - but suffer from a simple case of "well-meant patch syndrome".
Attached: pm-suspend.log (not from the diagnostic script) from suspending/resuming with g-p-m!
@awen
Ok, I've finished celebrating the first successful suspend/resume with g-p-m since I switched to Linux... :-) suspend. log is empty when using your (quite elegant) pm-suspend script
a) /root/pm-
b) with the original pm-suspend symlink, suspend AND resume work just fine!
So as far as I am concerned, everything is fine. Perhaps just the "negative logic" lines of the patch should be cancelled with the "sensible" rest being left in place? Will your changes propagate to Ubuntu? Can I do anything?
Concerning the fdi file for my computer, matching vendor, product ID and "linux.driver.info" is no problem - but my setup doesn't need any quirks and even if I explicitly switch off all of them (see above), the dbus-suspend-call seems to apply some of them... Furthermore, I suspect that there are several more people affected by this bug. However, most fglrx-users are used to broken suspends and likely to blame ati, the kernel or X - but suffer from a simple case of "well-meant patch syndrome".
Attached: pm-suspend.log (not from the diagnostic script) from suspending/resuming with g-p-m!