----- 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 VaioVGN-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? Hi Michael, I've made some progress on this. I can now reliably suspend/resume by running the following in the command line (as root): pm-suspend --quirk-s3-mode By creating the file /etc/pm/config.d/defaults with the single line: ADD_PARAMETERS="--quirk-s3-mode" I can simply run "pm-suspend" from the command line and everything works. However, if I try to put the computer to sleep by using any "Suspend to RAM" button in KDE, the machine suspends ok but freezes on resume. In the latter case, checking the file /var/log/pm-suspend.log reveals the following line Initial commandline parameters: --quirk-s3-bios When pm-suspend is issued from the command line, the same line in the log file is: Initial commandline parameters: without any parameters. So, when suspend is triggered by clicking on any "Suspend to RAM" button in kde, somehow the --quirk-s3-bios quirk gets appended to the pm-suspend command, and this prevents the machine from resuming successfully. Indeed, if I run "pm-suspend --quirk-s3-bios" from the command line the machine hangs on resuming. So, now I have to find out why the --quirk-s3-bios quirk is being added to pm-suspend command, and how to prevent that. By the way, I wonder if I should contact the guys responsible for the package hal-info and report that the --quirk-s3-mode quirk is necessary for this laptop to suspend/resume successfully. This is what lshal reports: system.hardware.product = 'VGN-NW130D' (string) Thank you, Adriano __________________________________________________________________ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
