Here's my problem, openSUSE 10.3 will not suspend my laptop when I close the lid. But if I issue an "echo mem > /sys/power/state", it suspends perfectly.
This seems to be an issue I run into with openSUSE that gets worse with each successive version. Having used four different laptops since 9.3, all of which are capable of suspending in linux, I have had to work harder and harder to make suspend work on a laptop that will normally suspend (ie. in other distros). In the past, I would simply use ACPI scripts to suspend on lid close, then I had to start working around the "improved" infrastructure, hacking scripts etc. With 10.3, I'm at a loss. s2ram won't suspend regardless of the settings I use, and even disabling all of the scripts in /usr/lib/pm-utils doesn't help. I close my lid in KDE and it doesn't suspend, when I open it back up, there's an error message about being unable to suspend. I can appreciate the effort the devs put into making suspend work for laptops that may not otherwise suspend well, but it's frustrating when you know your laptop suspends well, but openSUSE prevents it, and you can't find why. /var/log/pm-suspend.log doesn't help, either. It seems like it suspended correctly. Furthermore, I know from participation in the forums that users with 10.3 have found suspend to be broken, although it worked in 10.2. We try and coach them, but there's only so much we can do... ;) What's the relation between kpowersave and s2ram/pm-utils ? Were there any major changes in 10.3 that could have broken the way the built-in suspend infrastructure works? And can I disable openSUSE from intercepting acpi calls, and just go back to running a script on lid close? Making matters worse, *buntu suspends properly when I close my lid, so I'm not sure what we've done differently. Anyways, just wondering if there's any documentation on this kind of thing. I've worked through the scripts, and gone through the wiki page etc., and it's really little help. So, help ? If I'm missing something obvious, I'll gladly accept a slap to the head. But this is becoming frustrating. My laptop has succeeded with >16 days of uptime since my last boot, by frequently suspending via echo mem > ... at least 4 times a day, so stability is not an issue, then what do I need to do to get it working "natively" ? Thanks in advance, KV -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
