Re: [opensuse] Suspend issue
- From: Jean-Christophe Baptiste <jc@xxxxxxxxxxx>
- Date: Fri, 05 Dec 2008 23:31:56 +0100
Well, I might have found the culprit : an outdated fdi file in hal.
It is all explained there :
https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/235284
The patch there did not work for me as it is, so I
edited /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi manually.
Anyway the bug reporter has a 6460 model whereas mine is a 7664 one.
What I did :
1 - backup the file
2 - remove all occurrence of 7664 in the file
(prefix_outof="...;7664;...")
3 - add these lines at the end :
<match key="system.hardware.product" prefix_outof="7664">
<merge key="power_management.quirk.s3_bios"
type="bool">false</merge>
<merge key="power_management.quirk.vbemode_restore"
type="bool">true</merge>
</match>
4 - restart hal : "/etc/init.d/haldaemon restart"
5 - test suspend to RAM
I did not change ANY other of the default settings.
If your test is conclusive, I guess it is better to copy the new file in
"/etc/hal/fdi/information", so that it doesn't get overwritten by a
future update.
I hope this will help. Let me know how it goes for you.
JC
Le vendredi 05 décembre 2008 à 22:36 +0100, Jean-Christophe Baptiste a
écrit :
Le vendredi 05 décembre 2008 à 19:12 +0200, Manne Merak a écrit :
Jean-Christophe Baptiste wrote:
Hi,Check the /var/log/pm-suspend.log file when it fails. If you are lucky
I have a Thinkpad T61 laptop and use the Nvidia graphic driver.
I think this configuration is pretty common.
However, resuming after suspending to RAM randomly hang on a blank screen.
Sometimes, it finally resumes after minutes, and sometimes I have to cold
reboot.
I could not find the exact issue reported on the net. Does anyone else have
the same laptop here ?
Best Regards.
it will show you the cause.
Also check out
http://en.opensuse.org/Pm-utils
For my Dell Vostro with NVIDIA I had to add the following files.
cat /etc/pm/config.d/nvidia
DISPLAY_QUIRK_VBE_POST=false
&
cat /etc/pm/config.d/s2ram
S2RAM_OPTS="-f --acpi_sleep 1
Your mileage may vary (try modifying the acpi_sleep value)
Manne
ps. I have this working, but every now and then (every 30 times) it just
reboots (as if it was not set to resume the suspend)?
I tried your tweaks and other combinations, but no luck.
In the log file, the only noticeable message is :
===== 2008-12-05 20:06:13.197708442 running
hook: /usr/lib/pm-utils/sleep.d/10NetworkManager =====
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
I am not sure this is the cause of the hang. Maybe it comes from hal and
its quirks ?
Strangely, when I used Debian on this machine before switching to Suse,
I did not have this issue.
So, there must be a way...
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
- References:
- [opensuse] Suspend issue
- From: Jean-Christophe Baptiste
- Re: [opensuse] Suspend issue
- From: Manne Merak
- Re: [opensuse] Suspend issue
- From: Jean-Christophe Baptiste
- [opensuse] Suspend issue
- Prev by Date: Re: [opensuse] Is RAID1 to RAID5 conversion possible?
- Next by Date: Re: [opensuse] Suspend issue
- Previous by thread: Re: [opensuse] Suspend issue
- Next by thread: Re: [opensuse] Suspend issue
- Index(es):
Relevant Pages
|