I've tried ubuntu, kubuntu, fedora and linux mint. all 64 bit versions.

I've also tried to suspend through applications like acpitool. But nothing works.
When I click on Suspend, the screen goes blank but the computer is still running. The wireless network adaptor gets disabled for a second and then comes back on. All I have to do is press a key and I get the unlock screen prompt. Basically, suspend works like 'Lock Screen'.

I have a HP Pavillion laptop. Core 2 Duo @ 2 GHz and 4 GB RAM.

Can anyone help me please?

ayush,

In my experience this has been driver-related. When I installed the proprietary driver for my graphics card on my old tablet to get the performance I wanted I noticed this happened to my suspend features...

Did you install the proprietary gfx drivers? Any other kinds of system modifications made?

Which Distribution are you running currently and which model of pavilion are you running?

I found a great ref on the pavilion, but I don't know if it's your model... Here's the link: http://www.linlap.com/wiki/hp+pavilion+dv5-1000+series

Also, there is a notice regarding suspend/hibernate:

Thanks for replying

How can I do that?

I'm running Ubuntu 10.04 64 bit on HP Pavillion dv4-1125nr.
The website you mentioned does not have an entry for this laptop.

In windows, if I go to Device Manager(control panel) and look in "System devices", I see something called "ACPI Sleep Button". Also, sleep/suspend mode works fine on Windows Vista 64 bit.

Does anyone have a clue as to what the problem might be?

Hi Ayush,

Let's eyeball Ubuntu for a sec. I know typically these settings are pre-set and working fine, but let's just make sure there isn't something funky with this hardware and Ubuntu...

Check here https://wiki.ubuntu.com/PowerManagement for the info about the packages. Let's just make sure you've got all the acpi packages. I know, the kernel is supposed to be handling it all, but let's make sure you have the /etc/acpi... stuff to handle everything.

Please have a read at that and make sure it's all set (settings as well as packages).

Also, in your BIOS, is the ACPI section listed? Any chance you could publish those settings?

Anyone else have specific experience with Ubuntu and this kind of hardware/issue?

Does this article look like an accurate description of your problem?

https://bugs.launchpad.net/ubuntu/+s...ux/+bug/605133

From what I see, they are using fglrx drivers. Are you using the fglrx gfx drivers as well?

Thanks lylemwood. But suspend now works on linux. I did three things :-

1. Updated the BIOS to the latest version
2. Switched to 32-bit even though my the processor is 64-bit
3. Switched to Linux Mint (I doubt this would have made any difference as Mint is based on Ubuntu)
4. Installed proprietary drivers for my wireless adapter instead of a free one

Any idea which one of these could have done the trick?

it is a simple script that does it seems linux mint has worked on the generic scripts and has pre-setup power modes just a simple script. then it is up to your power settings for resume.

I've fought a similar problem and most of my success came after I moved to 32-bit with PAE instead of a 64-bit distro. I still have troubles with all sorts of suspend.

One of the things that troubles(sic) me most is the lack of information about how these features work, how to enable logging of the spin-down processing, how to enable logging of the wake-up processing, how to see what is going on, how to configure details like where "suspend" writes its details. Note: It seems that you must have a properly sized (whatever that means) swap partition. A swap file does not seem to work.

Wishing & Hoping for help,
~~~ 0;-/ Dan

SaintDanBert,

The issue with the logging component comes from the fact that the system is disabling critical resources during the spin-down and hasn't got them all up during the spin-up...

Logging depends on having a drive available to store, but if you've just powered that drive off you're screwed for logging.

Note to those working on code for this (if they actually read this): It would be nice if the logging could be cached to RAM during the spin-down and then appended during the spin-up and dumped to the log file after reload, but that would only work if the system actually recovered... If you have a faulty process, which is pretty much the only reason you'd consult the logs, you'd never have the logs committed so it's a waste of time (I guess that's why they don't bother)...

Regarding the SWAP partition, I usually make it equal to or 1.5x my RAM. This allows for suspend and for the (occasional) overrun in app processing.

I've never heard of a Linux distro that uses a SWAP FILE, only partitions.

I'd recommend using something like System Rescue CD or Knoppix to resize the partitions and give yourself a fairly nice SWAP (1-1.5x RAM) and see if your issues go away...

Any other issues?

Well, now I've installed 64 bit Linux Mint and suspend is still working fine. So it was either the BIOS update or the switch to Linux Mint from Ubuntu, that made it work.

In short a swap file is like any other file that just happens to be dedicated to swap (paging) data. Unlike ordinary files, swap files must be contiguous -- all of the segments of the file must be adjacent without any gaps or skips.

Take a look at this

• http://www.cyberciti.biz/faq/linux-a...ap-file-howto/
• http://www.linux.com/news/software/a...nux-swap-space

to learn about swap files.

Suspend Logging
Suspend must write the system state somewhere. This situation is similar to the dmesg and related kernel logging. Logging details could be part of that data. (This might be a good place to "require" a swap file ... to be used for suspend logging details.) I'm even willing to stipulate that suspend logging write to a serial port as raw text or similar.

Enjoy,
~~~ 0;-Dan

Suspend-to-disk (hibernate) and suspend-to-ram (sleep) still do not work for me. I have two, almost identical Thinkpad laptops (model 7764-CTO). One runs Jaunty (v9.04) and one runs Lucid (v10.04 LTS). Neither laptop will sleep or hibernate. A laptop without some sort of suspend is a real bear to take walk-about.

I have heard stories about causes:

• video hardware
• video drivers
• network hardware
• network drivers
• other configuration -- swap space vs. ram size, etc
• applications

Does anyone have a clue how to sort this out? I really need to get suspend to work.

Merci d'avance,
~~~ 0;-Dan