On Thu 02. Feb - 20:59:38, Holger Macht wrote:
> On Thu 02. Feb - 18:25:13, Ruben Jenster wrote:
> > Thanks Michael,
> >
> > it was the dbus persmissions that had to be modified.(since I don't use
> > pam,
> > adding the plugdev group was needed)
> >
> > I've allready created my own ebuilds, but yours are more advanced.
> > You should really add them to the bugtracker - this is usually the first
> > place
> > where I search ebuilds :-)
> >
> > Unfortunately the autosuspend feature still doesn't work for me.
> > Does it work for you?
> >
> > Another thing I will try is to modify the powersave scripts to use the
> > hibernate-script for suspending.
>
> Some short hints. Not sure whether it works this way. Maybe there remain
> some small issues, but it should be worth to give it a try:
>
> 1. create a script like that (I call it trigger_hibernate):
>
> #!/bin/bash
>
> . ${0%/*}/helper_functions # `dirname $0`/helper_functions
>
> #
> # Start the suspend via the the hibarnate script here
> # If it fails, return with
> # $SCRIPT_RETURN $EV_ID 1 "hibernate script failed"
>
> # on success...
> $SCRIPT_RETURN $EV_ID 0 "hibernate script finished successfully"
>
> EXIT 0
>
> 2. Change
>
> EVENT_GLOBAL_SUSPEND2DISK="prepare_suspend_to_disk screen_saver
> do_suspend_to_disk"
>
> to
>
> EVENT_GLOBAL_SUSPEND2DISK="trigger_pmsuspend"
The variable exists in /etc/powersave/events (depending on where the
configs got installed)
Regards,
Holger
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel
