Ask Your Question

Laptop screen not recovering from suspend

asked 2013-03-05 01:50:15 -0500

yanglifu90 gravatar image

Closing the lid or hitting Fn + F1 will put my laptop to sleep. It is just blank screen after recovering, the system resumed, I can even shutdown or reboot in terminal. What can I do?

edit retag flag offensive close merge delete


The description is not clear. If you get a blank screen, how do you shutdown or reboot using a terminal? What do you mean by blank screen? Does the monitor come on at all? How do you access the terminal? Please provide more information.

FranciscoD_ gravatar imageFranciscoD_ ( 2013-03-05 02:40:37 -0500 )edit

By terminal I mean ttyx, I can log in and run "su -c 'reboot'", and you can do this with the screen totally blank. By blank I mean it is blank like the machine is turned off.

yanglifu90 gravatar imageyanglifu90 ( 2013-03-05 22:35:33 -0500 )edit

If you can access a ttyx (I assume you're referring to a virtual terminal that can be accessed using ctrl alt f3 etc), it implies that the monitor did resume from suspend and is ON. Before rebooting, please take a look at /var/log/messages, dmesg, /var/log/pm-suspend.log and check for any errors. What fedora version are you running? Is your system up to date? What desktop are you using?

FranciscoD_ gravatar imageFranciscoD_ ( 2013-03-18 21:50:40 -0500 )edit

@FranciscoD_ The operating system is Fedora 18 and it is up-to-date, the desktop is GNOME. The file /var/log/messages is 1.7 MB in size and it can't be opened in gedit; I do not know what is dmesg, there is no /var/log/pm-suspend.log.

yanglifu90 gravatar imageyanglifu90 ( 2013-03-22 13:51:47 -0500 )edit

Well, not enough information then :(

Anything in /var/log/Xorg.0.log? It could be a video driver issue. I'm afraid I'm still not very clear on the issue though. Possible to post a picture somewhere with the terminal access and blank screen? dmesg is a command you run in the terminal. You don't need all of /var/log/messages. Have a look at the last 50 lines: tail -50 /var/log/messages. You need to have root permissions to access the file.

FranciscoD_ gravatar imageFranciscoD_ ( 2013-03-22 18:36:56 -0500 )edit

5 Answers

Sort by » oldest newest most voted

answered 2013-04-07 21:31:05 -0500

yanglifu90 gravatar image

The problem is solved in kernel 3.8.5-201.fc18.x86_64

edit flag offensive delete link more

answered 2013-12-30 20:08:58 -0500

I have the same problem with fedora 19. Do I need upgrade something?

edit flag offensive delete link more

answered 2014-03-07 08:47:34 -0500

reish gravatar image

It's a bug in kenrel 3.13. You can keep using kernel 3.11 until it's resolved.

edit flag offensive delete link more


That doesn't work for me. I suspect this is actually multiple bugs, which affect different hardware differently.

Robin Green gravatar imageRobin Green ( 2014-07-26 11:21:01 -0500 )edit

answered 2014-02-19 20:08:22 -0500

grayghost gravatar image

updated 2014-02-20 08:06:16 -0500

I am on Fedora / Korora 20 gnome 3 3.10.3

edit flag offensive delete link more


I am on Fedora / Korora 20 gnome 3 3.10.3 ... I close cover and reopen and it will resume .. I can tell the system back and running pidgin beeps when it logs on each server ... the cap light goes on and off with a press of the key . But the screen is blank like the computer is off ... sometimes the back light is on ...sometimes off .
It appears to me that the video driver is not getting initialised properly .

Gallium 0.4 on AMD RS880

AMD Phenom(tm) II P960 Quad-Core Processor × 4 64-bit

grayghost gravatar imagegrayghost ( 2014-02-20 08:06:45 -0500 )edit

answered 2014-01-19 14:29:28 -0500

VPR gravatar image

Same problem with fedora 20! Any solutions?

edit flag offensive delete link more


@VPR, you're using the answer box to ask questions. Look for the "comment" box instead.

randomuser gravatar imagerandomuser ( 2014-01-19 17:20:30 -0500 )edit

Question Tools



Asked: 2013-03-05 01:50:15 -0500

Seen: 4,854 times

Last updated: Mar 07 '14