Hi, a while back there was an update to openSUSE, sorry but it’s to long ago so I can’t remember which one it was, that totally broke my suspend to ram function. Well sort of anyway. It used to work perfect out of the box but now I have to fiddle around with s2ram to make it work at all.
I have read and tested all the options at the page about suse-s2ram and pm-utils but I can’t get it back to be as perfect as it was. What I have managed is to make it work great at first suspend (when closing my laptop lid that is) and first resume, but then it won’t go back into suspend. If I do it manually by clicking the suspend icon in kick-off menu it works great at both suspend and resume. It’s just as if the lid button doesn’t get resumed after first suspend.
Sometimes when I run suspend manually and let it sit in suspend mode for hours it freezes up on me at resume. I can normally get the log in screen up and I write my pass but then after that it just won’t go any further.
I would be very greatful for any type of suggestions what to try next.
openSUSE 11.2 x64
Packard Bell EasyNote MX52, 3GB RAM, ATI
s2ram should work fine all the time, but if the system in the interim starts using Power Management features (not s2ram) then the conflicts caused by Power Management and the stuff it doesn’t like will kick in.
Elsewhere on the boards I described how I got s2ram to bind to an Fkey via visudo and metacity gconf editor apps/metacity
But then to avoid the stuff you are describing I also had to turn off the laptop Power Management features.
Stakhanov suggested some powermanagement alternatives (in addition to s2ram but instead of gnome power management which I have yet to explore)
I finally worked this out, at least I think so. If anyone see any downside with this solution please tell me.
Like I said in first post suspend when closing my laptop lid would only work first time after a reboot. Suspending manually was working good every time. Resume was fine most of the time except for some occasional freezing.
I found this text in /usr/share/doc/packages/pm-utils/README.smart-suspend-to-RAM, it’s not mentioned in either Suspend to RAM - openSUSE or Pm-utils - openSUSE as far as I can see.
Just create a file in /etc/pm/config.d/, e.g. named “suspend”:
/etc/pm/config.d/suspend
Write:
S2RAM_QUIRKS_SOURCE=“hal”
in the file to use hal instead of s2ram. Nothing else modified. I’m not sure if I’m losing anything from using hal instead but so far it seems to be the best option for my laptop. It now suspends everytime I shut the lid and resumes just fine, no freezes so far but I’m still testing.
I found this text in /usr/share/doc/packages/pm-utils/README.smart-suspend-to-RAM, it’s not mentioned in either Suspend to RAM - openSUSE or Pm-utils - openSUSE as far as I can see.
Just create a file in /etc/pm/config.d/, e.g. named “suspend”:
/etc/pm/config.d/suspend
Write:
S2RAM_QUIRKS_SOURCE=“hal”
Thats interesting. I’m not familiar with developments here as far as openSUSE 11.2 is concerned. Hopefully, it will be of help to others.
Unfortunately I’ve had some locking/freezing on resume even with this configuration, but I believe it’s more rare than before.
However I’ve continued to read some more about this and I’ve encountered some contradictive information. Thing is I have an ATI RS690M [Radeon X1200 Series] GPU. Some people claims that using the proprietary driver will solve the locking/freezing problem on resume and some says the driver causes it and that the open driver is best. It’s of course easy enough to try but if anyone could share some experience from this card I’d be most grateful.
Hmm, might be off by a bit, but I just fixed a similar problem on my NB305. Try adding “nomodeset nohz=off highres=off” or some combination of the three to the kernel command on boot.
Just wanted to say that I never got s2ram working properly with KDE 4.3.5 no matter what I tried. I’ve now updated to 4.4.4 (still on 11.2) and at first I had some trouble with NetworkManager not resuming. That was easily fixed by just unloading the modules related to ath, so now I unload: ath cfg80211 rfkill ath5k and run s2ram with: S2RAM_OPTS="-f -p -m" and everything works just perfect.
In case someone else has problem with network resume, my network device is a Atheros AR5007EG with ath5k driver.