Linux Lite Forums

Ok, so the problem is still not solved. (I deleted the mark solved, and the best answer)

There is a definitively a relation between the memory and the waking up. but also with battery power and being plugged in or not.

I sometimes still have the black screen problem. Running low on battery, (around 10%) I had the black screen after logging in. Closing the lid, plugging the machine in on AC, opening the lid, logging in, all fine.
While unplugged, and having the black screen, and then plugging in, no success.

This morning, all night on suspend mode, I had no problem at all waking it up.

I was able to activate sys.log (Thanks for that thread). Is there any output I can post which can shine a light? (the whole sys.log is too private I believe)

Thanks!!

My Dell D610 has got this issue after an upgrade to LL 2.4 from 2.2. I used to open lid and just press the esc button twice and I'd get the login. Now it black screens. Is there a way of going back a version? Meanwhile I fiddled round in power manager and using settings of on ac/hibernate and on battery/suspend I can press menu/logout/suspend and close lid. On opening it goes to login and I can log in no problem. This is with wall power permanently on. I never use the battery alone although there's one in with little charge holding ability.   

well JAS, I was just about to put up a request for help for my machine (eee pc 1000HE) until I saw your message. When I'd put the screen lid down, it would shut the thing off correctly but when I opened it back up, black screen and no control.

In my particular case, I went into the power manager and there were settings "When laptop lid is closed:", that was set to lock screen so that is why I couldn't do anything after I opened it back up. I just selected "Suspend" and now everything is ok.

This is with Linux lite 2.4

I don't know if this will help anyone or not but I wanted to put this up.

Glin22

I have this issue on my older gateway as well. I changed screensaver / power options and no change.
However after I login, the screen is blank/black, If I close the laptop lid again and open it right away the screen returns to normal.
It doesn't bother me that much except at night, just one extra step to do.

Hello!

(04-15-2015, 02:12 PM)jnektar link Wrote:Is there a way of going back a version?

Short of you reinstalling 2.2, no. The updater was designed to go forward only, not back.

I know you don't want to hear this, but that's why backing up everything first is so important. Besides, once one of 'the big guns' steps in, they may know how to fix this issue short of 'nuking it and starting over'...

73 DE N4RPS
Rob

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

(09-04-2015, 05:00 PM)firenice03 link Wrote: [ -> ]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.
try running sudo pm-suspend with some of the quirks
For example:
or
or
All the quirks:
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.
containing 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.

(09-04-2015, 06:41 PM)misko_2083 link Wrote: [ -> ]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..

(09-04-2015, 06:41 PM)misko_2083 link Wrote: [ -> ]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..

Quote: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:
Or should I have a separate my-quirk for each function
I know I can string additional quirks on a line

Quote: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!!

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

This is another way, very usefull because it doesn't need sudo.