0 Members and 1 Guest are viewing this topic.
So if I use the screenshot settings you have above, I can close the lid, and it'll hibernate and wake up from hibernation without any additional commands, but if I want to manually hibernate it, I'll need to enter at least one of the commands you have listed?
Are you having the same success when you manually hibernate your PC?
sudo pm-hibernate
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate
My Dell Netbook (w/ Intel Graphics) appears to do the similar. Running LL2.2 and same with LL2.6Since its a "laptop" I want to close the lid or after X time have it hibernate after a screen saver. After waking from hibernate , I see the log on screen I can log in then black... Rebooting corrects until the next time. I've read that it could be lightdm (I think how it was referenced) and/or the screen saver..I used the following workaround when I want to hibernate..In terminal (does require root) Code: [Select]sudo pm-hibernateI typically leave a terminal window up just having to up arrow to the last command. If I put into hibernate, I have no issues waking.One of these days I'm going to chase the cause down.... But the above works for the time being.
Quote from: firenice03 on September 04, 2015, 01:00:11 PMMy Dell Netbook (w/ Intel Graphics) appears to do the similar. Running LL2.2 and same with LL2.6Since its a "laptop" I want to close the lid or after X time have it hibernate after a screen saver. After waking from hibernate , I see the log on screen I can log in then black... Rebooting corrects until the next time. I've read that it could be lightdm (I think how it was referenced) and/or the screen saver..I used the following workaround when I want to hibernate..In terminal (does require root) Code: [Select]sudo pm-hibernateI typically leave a terminal window up just having to up arrow to the last command. If I put into hibernate, I have no issues waking.One of these days I'm going to chase the cause down.... But the above works for the time being. On some hardware putting the video card in the suspend state and recovering from it needs some special quirk handling.Read the manual.Code: [Select]man pm-suspendtry running sudo pm-suspend with some of the quirksFor example:Code: [Select]sudo pm-suspend --quirk-vbe-post --quirk-vbemode-restoreorCode: [Select]sudo pm-suspend --quirk-reset-brightnessorCode: [Select]sudo pm-suspend --quirk-dpms-onAll the quirks:Code: [Select] --quirk-dpms-on --quirk-dpms-suspend --quirk-radeon-off --quirk-reset-brightness --quirk-s3-bios --quirk-s3-mode --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore --quirk-vga-mode-3 --quirk-noneThe trick is finding the right combination. It could be just one parameter or several.When you find the right quirk. Test your system to see if all is running OK.From the manual, to save it create a file in /etc/pm/config.d/Name it anyway you like.Code: [Select]gksu leafpad /etc/pm/config.d/my-quirkcontaining Code: [Select]ADD_PARAMETERS="pm-suspend --quirk-vbe-post --quirk-vbemode-restore" to make the quirk stick. Just use the parameters that work for you.Which quirk works depends on your hardware, kernel, driver, KMS settings and the probably the phase of the moon. Save. After reboot it should work.You can put the pc to suspend without sudo with dbus-send.Code: [Select]dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
man pm-suspend
sudo pm-suspend --quirk-vbe-post --quirk-vbemode-restore
sudo pm-suspend --quirk-reset-brightness
sudo pm-suspend --quirk-dpms-on
--quirk-dpms-on --quirk-dpms-suspend --quirk-radeon-off --quirk-reset-brightness --quirk-s3-bios --quirk-s3-mode --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore --quirk-vga-mode-3 --quirk-none
gksu leafpad /etc/pm/config.d/my-quirk
ADD_PARAMETERS="pm-suspend --quirk-vbe-post --quirk-vbemode-restore"
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
Quote from: misko_2083 on September 04, 2015, 02:41:12 PMWhich quirk works depends on your hardware, kernel, driver, KMS settings and the probably the phase of the moon. I hear ya, lol Issue is with Dell Mini with Intel video, my other Dell with SIS all seems to work fine (I don't close a lid but still sleeps/hibernate)..Is there a way to see what fails or doesn't initialize - debug or something, I sometimes wonder if its not the driver too..Just a thought..
Which quirk works depends on your hardware, kernel, driver, KMS settings and the probably the phase of the moon.
Quote from: misko_2083 on September 04, 2015, 02:41:12 PMOn some hardware putting the video card in the suspend state and recovering from it needs some special quirk handling.Read the manual.Code: [Select]man pm-suspendThanks - Didn't know about the manual.. Quotetry running sudo pm-suspend with some of the quirksFor example:Code: [Select]sudo pm-suspend --quirk-reset-brightnessThe trick is finding the right combination. It could be just one parameter or several.When you find the right quirk. Test your system to see if all is running OK.From the manual, to save it create a file in /etc/pm/config.d/Name it anyway you like.Code: [Select]gksu leafpad /etc/pm/config.d/my-quirkcontaining Code: [Select]ADD_PARAMETERS="pm-suspend --quirk-vbe-post --quirk-vbemode-restore" to make the quirk stick. Just use the parameters that work for you.Which quirk works depends on your hardware, kernel, driver, KMS settings and the probably the phase of the moon. Save. After reboot it should work.Testing a quirk seems to work initially but after creating the "my-quirk" file it no longer works.. Does the my-quirk file need referenced in a script or ?? (Like adding to grub to activate the file - just as an example)Can the quirk file have multiple lines of parameters like:Code: [Select]ADD_PARAMETERS=pm-suspend --quirk-reset-brightnessADD_PARAMETERS=pm-hibernate --quirk-reset-brightnessOr should I have a separate my-quirk for each functionI know I can string additional quirks on a lineCode: [Select]sudo pm-suspend --quirk-vbe-post --quirk-vbemode-restoreQuoteYou can put the pc to suspend without sudo with dbus-send.Code: [Select]dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.SuspendIs this another way to suspend the vs pm-suspend? I tested with by closing the lid Thanks again!!
On some hardware putting the video card in the suspend state and recovering from it needs some special quirk handling.Read the manual.Code: [Select]man pm-suspend
try running sudo pm-suspend with some of the quirksFor example:Code: [Select]sudo pm-suspend --quirk-reset-brightnessThe trick is finding the right combination. It could be just one parameter or several.When you find the right quirk. Test your system to see if all is running OK.From the manual, to save it create a file in /etc/pm/config.d/Name it anyway you like.Code: [Select]gksu leafpad /etc/pm/config.d/my-quirkcontaining Code: [Select]ADD_PARAMETERS="pm-suspend --quirk-vbe-post --quirk-vbemode-restore" to make the quirk stick. Just use the parameters that work for you.Which quirk works depends on your hardware, kernel, driver, KMS settings and the probably the phase of the moon. Save. After reboot it should work.
ADD_PARAMETERS=pm-suspend --quirk-reset-brightnessADD_PARAMETERS=pm-hibernate --quirk-reset-brightness
You can put the pc to suspend without sudo with dbus-send.Code: [Select]dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
Quote from: firenice03 on September 08, 2015, 10:41:32 PMQuote from: misko_2083 on September 07, 2015, 03:10:23 PMTryCode: [Select]sudo update-grubRemember to use the quotes " "Just add parameters without the commandShould work with all pm-utilsCode: [Select]ADD_PARAMETERS="--quirk-vbe-post --quirk-vbemode-restore"Code: [Select]dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.SuspendThis is another way, very usefull because it doesn't need sudo.Thought I'd update.....This issue is weird I've tried a few quirks individually... Some "seem" to work but only once...The Code: [Select]dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspendonly suspends the system - which the system doesn't seem to have to a problem waking from - only a lid closed hibernate. I can add a quirk/update grub - close lid the system hibernates no problems - after a few I'll press power to wake, I get GRUB, it "thinks" feather bar, shows a tty screen for a second then the log on prompt. - which.. The big IF.. If I get the "this session is locked - redirecting" screen pop up, which then comes back to same log on = it will work..If it stays on the log on screen and I log on - goes black, needs to be rebooted.- thus far it seems to work the 1st time after a reboot, after a 2nd hibernate goes black.I've disabled light locker was able to wake and go thru "waking" and directly to desktop (no log on prompt)I'm still testing ..FWIW: Intel Mobile 945GSE Express Integrated Graphics ControllerI'll keep updated - not sure but since I'm not running "Asus EEE1025" I can move to a new thread..??...Weird stuff. There is a known issue with lightdm-webkit-greeter that's where the popup window is coming from.We should change a greeter eventualy. Probably with LL 3.0.This command will put the comp to hibernation:Code: [Select]dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.HibernateAs for new thread question, please do so. Opening a new thread would help some folks with the same hardware.This is Asus EEE1025 thread.
Quote from: misko_2083 on September 07, 2015, 03:10:23 PMTryCode: [Select]sudo update-grubRemember to use the quotes " "Just add parameters without the commandShould work with all pm-utilsCode: [Select]ADD_PARAMETERS="--quirk-vbe-post --quirk-vbemode-restore"Code: [Select]dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.SuspendThis is another way, very usefull because it doesn't need sudo.Thought I'd update.....This issue is weird I've tried a few quirks individually... Some "seem" to work but only once...The Code: [Select]dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspendonly suspends the system - which the system doesn't seem to have to a problem waking from - only a lid closed hibernate. I can add a quirk/update grub - close lid the system hibernates no problems - after a few I'll press power to wake, I get GRUB, it "thinks" feather bar, shows a tty screen for a second then the log on prompt. - which.. The big IF.. If I get the "this session is locked - redirecting" screen pop up, which then comes back to same log on = it will work..If it stays on the log on screen and I log on - goes black, needs to be rebooted.- thus far it seems to work the 1st time after a reboot, after a 2nd hibernate goes black.I've disabled light locker was able to wake and go thru "waking" and directly to desktop (no log on prompt)I'm still testing ..FWIW: Intel Mobile 945GSE Express Integrated Graphics ControllerI'll keep updated - not sure but since I'm not running "Asus EEE1025" I can move to a new thread..??...
TryCode: [Select]sudo update-grubRemember to use the quotes " "Just add parameters without the commandShould work with all pm-utilsCode: [Select]ADD_PARAMETERS="--quirk-vbe-post --quirk-vbemode-restore"Code: [Select]dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.SuspendThis is another way, very usefull because it doesn't need sudo.
sudo update-grub
ADD_PARAMETERS="--quirk-vbe-post --quirk-vbemode-restore"