My computer cannor resume form standby or hibernate

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include 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 "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 [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Yixiel:
In addition to the above can you also include your /etc/X11/xorg.conf file here please?

uname -a produces:

Linux ORION 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux

also here i atached lspci-vvnn.log

also here i attached xorg.conf

Ok thank you, the kernel team will take care of this.

Hi there,

I had the same issue on my ASUS A6JM and i "fixed" it by choosing the linux-image-2.6.20-generic.

Linux asus 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

I accidentaly put the dmesg.log as well as the uname -r of the other kernel here. sorry..

My Clevo D400 in also not able to resume after apparently proper suspend or hibernate.

I followed the method described in wiki about DebuggingKernelSuspend. I removed five devices by adding them to the MODULES line in /etc/default/acpi-support file: MODULES="ptya4 ptys5 ptyz8 ptywb ttybf", one after one... No effect!!!

Attached you'll find the files asked for.

Thanks in advanced.

More files ...

... and more ...

... the last one!

Hi All,

This bug was opened a while ago but there hasn't been any recent activity. The symptom of this particular bug, failure to Suspend or Hibernate, is specific to the hardware used. So while many of you may have the same symptom they really should be different bugs. It would be helpful if everyone were to test with a Hardy Alpha build, http://www.ubuntu.com/testing/ , and open a separate bug report for their hardware using "linux" as the package. The bug report should contain the information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Additionally, it would be great if you made the titles of a new bug report contain information about your system. I apologize for any inconvenience this might cause but appreciate your cooperation.

Yixiel, since you are the original bug reporter, care to comment if this is still an issue for you on the latest Hardy Alpha release? You should be able to test using the LiveCD. However, please note you can only test Suspend using the LiveCD, not Hibernate. Thanks.

Can this be somewhat similar to <a href="https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/140892">bug #140892</a>?
Try changing 'splash' to 'nosplash' in your /boot/grub/menu.1st file. Also, if you remove the 'quiet' option you would at least see whats going on when it fails.

Closing for now until further feedback from original bug reporter.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.