[ SOLVED ] Black Screen after hibernate - Intel Graphics

[paul1149]

Same issue here on a friend's LL 2.6 x32 Dell 1545 laptop, originally Vista. Unit was set to lock the screen when the lid was closed. I changed it to Sleep and the problem was solved.

[torreydale]

Good tip, stop0x0000000a. 

I have Light Locker disabled, but I do see "Screen Locker (Launch screen locker program)" running in Application Autostart (under the Session and Startup utility).  I'll consider unchecking it here before uninstalling it altogether.

[stop0x0000000a]

Hello All,

Had the same issue about light-locker for my ordinary desktop (not a laptop),  it could not wake up after Suspend.
Black screen, Ctrl+Alt+F1 gave text mode but could not returned to X.

In GUI Light-Locker was disabled so I did not pay much attention on those posts on XUbuntu forums.
But turned out it was still alive via ~/.config/autostart, a bit strange.

Anyway, I've uninstalled the locker completely and my Desktop is happy again

[torreydale]

firenice03,

I have hibernate working on my Dell Latitude e6430 laptop with specs listed in my forum profile, and with my HP a6110n Pavilion desktop with 8GB of RAM. 

It would be cool if the Hibernate button in the Log Out dialogue would trigger these Hibernate settings of the Power Manager.

[firenice03]

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?

As tested on my hardware.. Yes, disabling Light Locker corrected the wake from hibernate when closing lid... I removed any other additional settings/quirks.
If you have a hibernate button and configure within Power Manager - I assume this should work as well...
For me closing the lid is the easiest way to force a hibernate.

You could allow it to go to hibernate after an X amount of time. I have this configured on my 2nd PC (SIS graphics) and it works fine (Light Lock is disabled on this system too) thou its a desktop - no lid to close, and do not recall any issues as I only suspended it before.

Light Locker displays a log on screen (along with other options) but with default settings the log on - by disabling you will loose its lock (although fixing the waking from hibernation). If you need a lock, the other 2 applications have a lock prompt as well - it just looks different.

You should only have to set 2 options
Power Manager: Hibernate when lid is closed
Light Locker: Set "Enable Light-locker" under "Locking" to OFF

The others options are screensaver and other customization's based on duration. Feel free to mimic.

Since these are simple GUI changes - I'd say doesn't hurt to try, worst case it doesn't correct and you have to hard boot.

Curious if it does correct and what hardware you're running 

[torreydale]

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?

[firenice03]

Are you having the same success when you manually hibernate your PC?

The hibernating itself seemed to work great it was waking from it would I get the black screen; unless I manually forced a hibernate from terminal prior to closing the lid, using

Code: [Select]

sudo pm-hibernate
My initial
So, I closed lid tried to wake = black screen... If I manually hibernated (above code) then closed = woke normally
After disabling light locker
I close lid = wakes normally; manually hibernating either with above code or with below code - still wakes normally...

Code: [Select]

dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate
In both instances I had Power Manager set to hibernate when lid closed...

Hope this clarifies

[torreydale]

Are you having the same success when you manually hibernate your PC? 

[Jerry]

Nice share, thank you

[firenice03]

So for an update...
Waking from hibernating (closing of lid or otherwise) is working normally

Tested - All quirks removed, updated grub. Moved quirk file from default location updated grub and rebooted...

Disabling Light Locker - after switching "Enable" to off... This remedied the black screen when waking.


Other setting used on system: Screen Saver and Power Manager

Yes I'm using the Matrix
The Lock after X could be used at this time to lock the system on wake using the XScreensaver prompt
*If making changes --  File - Restart Daemon

Under Advanced - I left blank as I have the screensaver run then hibernate - but Power Mgmt options seem to work - that and using Power Manager


Power Manager

AC/Battery about the same except for duration..

Monitor: Adjustable


Extended: could use Lock feature - same XScreenSaver lock feature

[firenice03]

To update:
Since disabling Light-Locker waking from hibernate (closing the lid) has seemed to work each time. I want to test more as I do have quirks enabled, I'll try with out to see if anything changes.

For info..
I use Screensaver and Power Manager (for hibernation), Light-Locker was set to "do nothing" except for under "Enable Light-Locker" was on (now off)

Thus far the only thing I've noticed is that I'm not prompted for log on after waking (not a big deal for me) I'll test other options and report. I believe there is an option to lock under the settings of either Screensaver or Power Manager.

@misko_2083 Thanks again for the info!! 

[firenice03]

Moving my posts from the ASUS thread to a new.
Referenced https://www.linuxliteos.com/forums/video-cards/%28solved%29-black-screen-after-sleep-asus-eee1025/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: [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.

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: [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 quirks
For example:

Code: [Select]

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

Code: [Select]

sudo pm-suspend --quirk-reset-brightnessor

Code: [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-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: [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

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

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

Thanks - Didn't know about the manual..

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

Code: [Select]

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: [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-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: [Select]

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


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

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

Thanks again!!

Try

Code: [Select]

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

Code: [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 Controller
I'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.

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