Black Screen after hibernate - Intel Graphics

[firenice03]

Moving my posts from the ASUS thread to a new.
Referenced https://www.linuxliteos.com/forums/video...ee1025/15/

My issue is that I received a blank screen after closing the lid (hibernating) of my netbook.
This 1st post will be lengthy as I wanted to capture the majority of the original thread - lots of good info from misko_2083..

My Dell Netbook (w/ Intel Graphics) appears to do the similar.  Running LL2.2 and same with LL2.6

Since 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:

sudo pm-hibernate

I 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 author=firenice03 link=topic=1723.msg16884#msg16884 date=1441386011]
My Dell Netbook (w/ Intel Graphics) appears to do the similar.  Running LL2.2 and same with LL2.6

Since 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:

sudo pm-hibernate

I 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:

man pm-suspend

try running sudo pm-suspend with some of the quirks
For example:

Code:

sudo pm-suspend --quirk-vbe-post --quirk-vbemode-restore

or

Code:

sudo pm-suspend --quirk-reset-brightness

or

Code:

sudo pm-suspend --quirk-dpms-on

All the quirks:

Code:

  --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

The 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:

gksu leafpad /etc/pm/config.d/my-quirk

containing

Code:

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:

dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend

[/quote]

[quote author=misko_2083 link=topic=1723.msg16885#msg16885 date=1441392072]
Which quirk works depends on your hardware, kernel, driver, KMS settings and the probably the phase of the moon.

I hear ya, lol  ;D
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..
[/quote]

[quote author=misko_2083 link=topic=1723.msg16885#msg16885 date=1441392072]
On some hardware putting the video card in the suspend state and recovering from it needs some special quirk handling.
Read the manual.

Code:

man pm-suspend

Thanks - Didn't know about the manual..

try running sudo pm-suspend with some of the quirks
For example:

Code:

sudo pm-suspend --quirk-reset-brightness

The 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:

gksu leafpad /etc/pm/config.d/my-quirk

containing

Code:

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:

ADD_PARAMETERS=pm-suspend --quirk-reset-brightness
ADD_PARAMETERS=pm-hibernate --quirk-reset-brightness

Or should I have a separate my-quirk for each function
I know I can string additional quirks on a line

Code:

sudo pm-suspend --quirk-vbe-post --quirk-vbemode-restore

You can put the pc to suspend without sudo with dbus-send.

Code:

dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend

Is this another way to suspend the vs pm-suspend? I tested with by closing the lid

Thanks again!!
[/quote]

[quote author=firenice03 link=topic=1723.msg17025#msg17025 date=1441766492]
[quote author=misko_2083 link=topic=1723.msg16982#msg16982 date=1441653023]
Try

Code:

sudo update-grub

Remember to use the quotes " "
Just add parameters without the command
Should work with all pm-utils

Code:

ADD_PARAMETERS="--quirk-vbe-post --quirk-vbemode-restore"

Code:

dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend

This 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:

dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend

only 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  8) ..

FWIW: Intel Mobile 945GSE Express Integrated Graphics Controller
I'll keep updated - not sure but since I'm not running "Asus EEE1025" I can move to a new thread..??...
[/quote]
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:

dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate

As 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]

Again hoping this captures the essence of the information - trying not to duplicate too many of the quotes...