Suspend hibernate on T41p not working

[ckeller]

Binary package hint: linux-image-2.6.15-21-686

Hello,
since linux-image-2.6.15-19-686 suspend and hibernate is not working anymore.
System resumes and the screen is messed up. (Perhaps this is a fglrx bug?)
Can´t tell whats going wrong. Perhaps someone has an idea.

Thanks Christoph

[Angelo Lisco (angystardust-gmail)]

Hi Christoph! What happens if you boot with 2.6.15-21-386? Can you reproduce with it?

[ckeller (christoph-keller)]

Tried kernel 2.6.15-21-386,2.6.15-22-386, and 2.6.15-22-686.
No difference, system tries to resume but xserver is not resuming.
Sometimes resume is working, sometimes not. Rigth now I try it with
ACPI S1 sleep. This seems to be more reliable.

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[ckeller (christoph-keller)]

Sorry running feisty now. So don't have the 2.6.15 kernel anymore.

[Brian Murray (brian-murray)]

Is suspend working in Feisty then?

[Brian Murray (brian-murray)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.