----- Original Message ----
From: Michael Biebl <[email protected]>
To: Adriano Vilela Barbosa <[email protected]>; [email protected]
Sent: Sun, December 20, 2009 3:31:03 PM
Subject: Re: Bug#561877: pm-utils: Resume from suspend stopped working on Sony
Vaio laptop
Adriano Vilela Barbosa wrote:
> Resume from suspend stopped working on my Sony Vaio VGN-NW130D laptop.
> Apparently, what caused the problem was an upgrade of the pm-utils
> package from version 1.2.6.1-1 to 1.2.6.1-3. After trying all sorts
> of things with no success, I decided to uninstall pm-utils and install
> uswsusp (which I got from sid, as there's no version currently available
> in testing). Using the command s2ram from the uswsusp package, the machine
> suspends/resumes with no problems. I would like to downgrade pm-utils to
> its previous version to see if that fixes the problem, but I don't know
> where I can get the old version from. I'm willing to do some testing in
> order to pin this problem down.
I've put the old version online at [1]. It would be great if you could test that
version.
Please describe exactly what is happening on resume.
You can run
PM_DEBUG=true pm-suspend
as root to get a more verbose log file at /var/log/pm-suspend.log
Michael
[1] http://debs.michaelbiebl.de/pm-utils_1.2.6.1-1_all.deb
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Ok, problem solved. The problem was that I had "quirk.s3_bios" enabled
by default. Doing "lshal | grep quirk" produced:
power_management.quirk.s3_bios = true (bool)
In order to have suspend/resume working correctly, I needed to disable
"quirk.s3_bios" and enable "quirk.s3_mode". I did that by creating the
file /etc/hal/fdi/information/99local-pm-utils-quirks.fdi with the
following contents:
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<!-- Created by pm-utils -->
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="Sony Corporation">
<match key="system.hardware.product" string="VGN-NW130D">
<match key="system.firmware.version" string="R0170Y4">
<match key="system.hardware.primary_video.vendor" int="0x1002">
<match key="system.hardware.primary_video.product" int="0x9553">
<merge key="power_management.quirk.s3_bios"
type="bool">false</merge>
<merge key="power_management.quirk.s3_mode"
type="bool">true</merge>
</match>
</match>
</match>
</match>
</match>
</device>
</deviceinfo>
The file was created by running (as root):
pm-suspend --quirk-s3-mode --store-quirks-as-fdi
and later editing it (as the original file enabled "quirk-s3-mode" but
didn't disable "quirk-s3-bios"). After restarting the hal daemon,
"lshal | grep quirk" produces
power_management.quirk.s3_bios = false (bool)
power_management.quirk.s3_mode = true (bool)
As I said before, I suspect some package upgrade broke things up,
as everything was working fine until about two weeks ago. Here
are some suspects:
adri...@vaio:/var/log$ less dpkg.log | grep upgrade | grep hal
2009-12-05 09:47:24 upgrade libkephal4 4:4.3.1-1 4:4.3.2-2
2009-12-07 06:46:47 upgrade libhal1 0.5.13-4 0.5.13-6
2009-12-07 06:46:47 upgrade libhal-storage1 0.5.13-4 0.5.13-6
2009-12-07 06:46:47 upgrade hal 0.5.13-4 0.5.13-6
2009-12-11 20:46:12 upgrade hal-info 20090716-1 20091130-1
adri...@vaio:/var/log$ less dpkg.log | grep upgrade | grep udev
2009-12-14 06:58:30 upgrade udev 146-5 149-1
2009-12-14 06:58:31 upgrade libudev0 146-5 149-1
2009-12-14 06:58:38 upgrade libgudev-1.0-0 146-5 149-1
So, I guess you can close this bug. Should I report this
to the hal-info maintainers so that they can update their
database with my laptop model (Sony Vaio VGN-NW130D)?
Thanks,
Adriano
__________________________________________________________________
Ask a question on any topic and get answers from real people. Go to Yahoo!
Answers and share what you know at http://ca.answers.yahoo.com
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
