suspend to ram & beryl AiGLX ? [solved]

[Ron.W]

Hello,

I have a laptop here, working great with Sabayon-Linux (3.2)

Suspend worked fine for me, after resume I get the unlock-message allways, and after typing the password the desktop appears.

This was true until I enabled Beryl. Beryl itself also works great really, using AiGLX on a Nvidia 6600 go. It is a pure pleasure to work with this.

But I have problems with the resume from suspend-to-ram when Beryl is active:

The laptop resumes as it should, background-light in the tft-display switches on and the mouse-pointer comes up. But the screen itself stays black. There is no unlock-message displayed. Sometimes there is displayed a small multicolored square of maybe 20x20 pixel somewhere on the Screen. I can unlock typing the password blind, but even then the screen stays black. I can use Alt-F1 to get the Console which is displayed fine, and also I can switch back to the black screen where my desktop should have been, using Alt-F7. The only way I found to get the screen back working is to use ctrl-alt-backspace in order to restart the X-session completely. Then I get the normal login-screen. Also it is possible to shut down the computer properly by simply pushing the shutdown/power-switch. Imediately the Login-Message is displayed for a second, before the normal sutdown procedure is executed -- all visible with normal graphics again.

Any Ideas, how I can perform a resume from suspend to ram while using beryl?

Greetings
Ron.

[Ron.W]

Just noticed that this probably isn't a problem of beryl, but maybe one of knnetworkmanager, network driver, or kwallet in interaction with beryl:
After I had deactivated knetworkmanger and the networkmanager deamon (so also kwallet is no longer needed to keep the password) and employed wpa_gui for a test, the notebook recovered right now twice from suspend to ram properly and gave me the unlock-screen, although beryl was active.

I'am working on this further. Any sugesstions appreciated.

greetings
Ron.

[Ron.W]

Probably solved. Will keep watching this, since the problem was only sometimes present, and sometimes it displayed the unlock-message after recovering from suspend perfectly.

Here is what I did:

1.) file: /etc/modules.d/nvidia
add the line: options nvidia NVreg_SoftEDIDs=0

2.) Then: Beryl Settings Manager (from K-Menu), Section "General Options". Uncheck the "Sync to VBlank" box.

3.) restart X or reboot.

After adjusting these settings as described I was able to recover about 8 times already from suspend-to-ram without any problems. Looks auspicious.

More information: http://wiki.beryl-project.org/wiki/Trou ... a#Suspend2 This is where I found it.


Ron.

[Ron.W]

Definitvely solved. Didn't have any problems while resuming from suspend since I made the changes described above.

Ron.

[andu]

great u ask and u answer also

dude u own!
mwhahahaha