Description of problem: Blank screen after resume from suspend on ASUS U36SG notebook. How reproducible: Close notebook lid. System will turn off into suspend state. Push spacebar to resume. System will turn on (not hangs) but screen is still blank. After than I can change TTY using Ctrl+Alt+F2 (but still screen is blank - no letters nor cursor), log in as root and type "poweoff". Additional info: lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce 610M] (rev a1) uname -r 3.7.2-204.fc18.x86_64
Similar issue is on Fedora 18 Live (notebook running from LiveCD) but system hangs during resume. There is no that problem with resume on Fedora 17 Live (notebook running from LiveCD). Only brightness of screen isn't saved and after resume is set to max.
I decided to install Fedora 17. After installation I updated all packages to the newest version. Then I tried to suspend laptop (close lid). It went to suspend mode but immediately woke up. I noticed in dmesg that there was a problem with "nouveau" driver for nvidia. After removing module (#rmmod nouveau) suspending works like a charm.
Similar problem using Fedora 18 on a Toshiba Portege - started happening after a recent kernel update. Only affects the laptop screen: when operating with another screen attached only the laptop screen remains blank on resume.
I have same problem on hp elitebook 8440p, Fedora 17, driver Gallium 0.4 on NVA8
I have the same issue on Asus N56D 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Device 9900 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Chelsea LP [Radeon HD 7730M] (rev ff) Has dual AMD GPU's. One on CPU and dedicated. I have the dedicated turned off. Tried suspend with both GPU's on and it did the same thing.
Same issues on Fedora 19 beta. Had the same issue with F18.
I'm getting the same issue on my ASUS series (AMD 6480G) with Fedora 18 kernel version 3.9.4-200.fc18.x86_64; I can close the lid and power it down but the screen doesn't power-on with the rest of the PC anyway.
The same is on HP elitebook 8440p, Fedora 18. The last working kernel is kernel-PAE-3.7.9-205.fc18.i686, newer kernels (tested up to kernel-PAE-3.9.6-200.fc18.i686) have suspend/resume blank screen issue.
Same issue on MacBook Pro booting EFI on Fedora 19. But only when I have powered down the IGD. If the IGD is powered on, laptop resumes normally. Pawel, Can you try to verify that the intel vga is on by issuing a "cat /sys/kernel/debug/vgaswitcheroo/switch" and verify that beside IGD is "PWR"? If it says "OFF", issue the following command: "echo ON > /sys/kernel/debug/vgaswitcheroo/switch" then try suspend and resume. lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 330M] (rev a2) uname -r 3.10.4-300.fc19.x86_64 cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD: :Pwr:0000:00:02.0 1:DIS:+:Pwr:0000:01:00.0 2:DIS-Audio: :Pwr:0000:01:00.1
By default I've blacklisted NVidia modules (and therefore /sys/kernel/debug/vgaswitcheroo/switch no exists): /etc/modprobe.d/blacklist-nvidia.conf blacklist nouveau blacklist nvidia But after loading driver: modprobe nouveau I have /sys/kernel/debug/vgaswitcheroo/switch: 0:IGD:+:Pwr:0000:00:02.0 1:DIS: :Pwr:0000:01:00.0 After then suspend and resume causes black screen. Strictly speaking after resume appears "desktop" for a while and after that screen goes black. Then only one way is hard rebooting system. lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [GeForce 610M] (rev a1) uname -r 3.10.4-300.fc19.x86_64
Hi, I have a similar issue - Fedora 19 on an Asus X201e. Fresh install from live USB On resume from suspend, The blue Time/Date screen appears for ~1 second, then screen goes black. I can recover the screen with Fn+F6 (increase screen brightness) or Fn+F5 (decrease screen brightness). In normal system usage, increase/decrease brightness keys have semi-erratic behavior. I'll describe approximate behavior on a brightness scale of -10 - 10 (-10 is off). Pressing increase brightness button swaps brightness from current level to inverse about the 1 (ie, 8 to -6, -6 to 8, or -5 to 7). Pressing the decrease brightness button swaps brightness to inverse about -1 (ie, 8 to -10, -10 to 8, or -5 to 3). So with screen black (-10), increase jumps brightness to full (10), and decrease jumps brightness to almost full (8). Values are approximate based on visual inspection of the on-screen brightness indicator.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
Problem is still present in 3.11.4-101.fc18.x86_64, hp elitebook 8440p, Gallium 0.4 on NVA8
Still have it with kernel-PAE-3.11.10-301.fc20.i686 on hp elitebook 8440p. Workaround is to install nvidia driver.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Still happening on F20, Asus X200CA-HCL1104G.
Created attachment 899978 [details] lspci
Is kernel the right component, or should be re-assigned to xorg-something?
Has there been any progress in fixing this? I have an Acer Aspire One 722 with AMD C50 processor that is experiencing this. It began with the 3.15.x kernels. It works fine with the 3.14.x kernels. Unfortunately, I forgot to freeze the last 3.14 kernel, so the last update deleted it. I am stuck with a system that will not resume from suspend properly. The current kernel installed is kernel-3.15.8-200.fc20.x86_64. Please change the severity to high as this definitely impacts the use of the system. I am used to suspending and resuming with work in progress. Since only a hard reboot seems to fix this, it means a significant disruption when this happens.
I think I found something significant. The Xfce Power Manager has an option under the "Extended" tab, there is an option for "Lock screen on suspend." I think that this problem is associated with that option. I unchecked the option, and suspend and restore now works. i do not know if xscreensaver figures into this or not.
I get no screen's with 3.15 kernel and using the 3.14 kernel. I only get a kernel dump and says it needs to reset. Come up no issues with 3.14 kernel.
My previous comment about Xfce Power Manager is invalid. It continued regardless. I completely uninstalled xfce-power-manager and still have the problem. I modified the /etc/acpi/events/videoconf to uncomment the event=video.* and action=/usr/sbin/vbetool dpms on lines. The problem is is something that changed between the 3.14 and 3.15 kernels. I need to get a 3.14 kernel as the last updates deleted it before I remembered to freeze it so that it would not update.
Attempted removal of acpi components and xfce4-power-manager and uncommented /etc/systemd/logind.conf items to let systemd handle events. results: no difference. Someimes, I can get one or two resumes before getting the blank screen. It seems to depend on how long it was suspended. I have reinstalled acpi and xfce4-power-manager and recommented most of logind.conf execept to ignore power button and lid switch events. I just uninstalled xscreensaver-base to see if that has anything to do with this problem.
Removed acpi. Changed SysRq to enable all functions. Executing ALT-SysRq-k, which does work when first booted to end the stop programs in the current VT and restart X does nothing with this problem. Two files attached to see if someone can figure out what is happening. 1. dmesg_good.txt: executed dmesg on a fresh boot to see what the state of things was. 2. dmesg_bad.txt: When the screen failed to restore on resume, hit CTRL-ALT-F2 to open another VT. In the blind, logged in as root. Executed dmesg > dmesg_bad.txt. I don't know what else to try. I need a 3.14 kernel back so I can use this netbook. Not having a working suspend/resume is a major problem.
Created attachment 929694 [details] Capture of dmesg output
Created attachment 929695 [details] Capture of dmesg output during failure
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This issue still exists with kernel-3.17.2-200.fc20.x86_64. I have been following up on this issue in bug # 1149233. The bottom line is that suspending via the menu option or via the lid switch leads to failure. The computer will have a blank screen on resume. What does work: Suspend via "pm-suspend" or suspend via "systemctl suspend." both options will result in a system that resumes properly. I have been using "systemctl suspend" successfully for multiple suspend/resume operations over the course of more than a day.
Fedora 21 using MATE works Fedora 21 using Xfce does not work Fedora 21 using Enlightenment does not work. Please change the version to Fedora 21. kernel-3.17.7-300.fc21.x86_64
Fix that worked for me: Open /etc/UPower/UPower.conf and change IgnoreLid=false to true. Reboot and then check if it worked for you.