Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Screen goes blank (hibernation?) and never resume normal

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
shogun1234
Posts: 156
Joined: 2006-07-13 08:04
Has thanked: 3 times

Screen goes blank (hibernation?) and never resume normal

#1 Post by shogun1234 »

To be honest, I don't know if this problem belongs to this category or not. Apologize if posting to the wrong place.

My hardware is HP 840 G5 with debian buster/sid. And kernel is 4.17.0-3-amd64.

The problem is each time the screen goes blank (when inactivity for a while), it would never resume back to normal. For instance, pressing any key the screen will come display login screen or my working environment. That looks like hibernation problem to me, but I can be sure, and do not know where to check the log. The only error message I find so far is shown dmesg, and I do not find relevant solution on the internet. Any suggestions for this problem or where to check the log?
Thanks

Code: Select all

[    2.625263] ACPI Error: Needed [Buffer/String/Package], found [Integer]         (ptrval) (20180313/exresop-560)
[    2.625267] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20180313/dswexec-427)
[    2.625270] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20180313/psparse-516)
[    2.625275] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20180313/psparse-516)
[    2.625325] input: HP WMI hotkeys as /devices/virtual/input/input22
[    2.630316] ACPI Error: Attempt to CreateField of length zero (20180313/dsopcode-134)
[    2.630320] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPI, AE_AML_OPERAND_VALUE (20180313/psparse-516)
[    2.630328] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_VALUE (20180313/psparse-516)

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Screen goes blank (hibernation?) and never resume normal

#2 Post by stevepusser »

First, you must determine whether your machine is just turning off the display, suspending to RAM, or actually doing a full hibernate (writing RAM to disk and fully shutting down). Most machines will have some special LED flashing to show that they are in the suspend2ram state.
MX Linux packager and developer

shogun1234
Posts: 156
Joined: 2006-07-13 08:04
Has thanked: 3 times

Re: Screen goes blank (hibernation?) and never resume normal

#3 Post by shogun1234 »

Sorry after checking specs

https://support.hp.com/gb-en/document/c05903000

http://www8.hp.com/h20195/v2/GetPDF.aspx/c05868510.pdf

I still don't find any doc mentioning related info (something like LEDs flashing to indicate turning off display, doing full hibernate and so on). Any places I might be missing or I can also check for such info?

Thanks for your help!

shogun1234
Posts: 156
Joined: 2006-07-13 08:04
Has thanked: 3 times

Re: Screen goes blank (hibernation?) and never resume normal

#4 Post by shogun1234 »

https://raspberrypi.stackexchange.com/q ... oing-blank

Not sure. But this one seems to be working.

Adding following commands to .xsessionrc

Code: Select all

# . ~/.profile # source ~/.profile if needed 
xset s off         # don't activate screensaver
xset -dpms         # disable DPMS (Energy Star) features.
xset s noblank     # don't blank the video device


shogun1234
Posts: 156
Joined: 2006-07-13 08:04
Has thanked: 3 times

Re: Screen goes blank (hibernation?) and never resume normal

#5 Post by shogun1234 »

Mmm ... I probably know what goes wrong. It looks like light-locker was activated with blank theme, resulting in my screen completely becomes blank. Will investigate how to configure /etc/lightdm/lightdm-gtk-greeter.conf checking if that fixes my problem. Sorry for creating confusion.

Post Reply