I updated my fedora 29 to fedora 32 recently, It seems I have problem with my laptop waking up from sleep/suspend. Nothing happens no matter which key I press. I have to reboot every time. I went through lot of articles but no help. It would be great if anyone can help, I am wasting time rebooting everyday. System info is as below
Actually I just want to say that I am having the same problem with my Dell Precision 3350 with Quadro Card.
If I let the laptop suspend it will fail to wake up from suspend. I am on Wayland session with nouveau drivers.
However it seems to be it is not Fedora or Gnome Specific, I have been experiencing the same problem since a couple of months, on Mint Cinnamon, Elementary OS, Pop Os 19.10, 20.04, Manjaro KDE, with propriety or free graphics drivers.
It seems to be related to Quadro Card, as I have an old Dell Latidute which only has integrated Intel card, and the problem is not there with neither of above mentioned distros. Same with my wife’s Asus Laptop with MX 930 card (Elementary, Mint Cinnamon and now Manjaro KDE).
It seems to related to some Kernel update (also read about it somewhere) as I was using the same laptop since Setember 2019, and there we no issue. At the moment I was using either Mint or Elementary with 18.04 base, and the problem roughly appeared so when those distros upgraded to Ubuntu’s HWE kernel. And now, I am even having troubles to simply boot to 20.04 series (expect Pop OS and partially Mint, for which I can boot but it always stacks in the middle of install).
Sorry, not much of help, but just to let you know that you are not alone with the problem and some background that hopefully can help to resolve it.
The thing that is common in your issue and that of @milangujarat is that both of you are using an Optimus-based device and with the sub-par okayish nouveau driver. Might be an indicator of what the problem is.
Thanks for the response. The thing is that I have been having the same problem with Pop Os and Mint, where I was using the propriety drives. (and PopOs sort of known for a good Nvidia support in their isos).
Additionally, my perception was that the problem occurred less often with nouveau than with propriety drives. In my earlier attempts, I have also set-up Nvidia Drives from RPM-Fusion Repo and the problem was still there.
P.S. I have distro-hopping because of this issue and also problems with Matlab installation, as I was not getting hardware acceleration in Fedora, but recently I was able to solve the Matlab related issue, so came back.
If you think the problem is really with open nvidia drivers, I am willing “to risk” my installation for another attempt. Overall, I am quite new to Fedora, so I may missed some tricks…
Well, that is true I wrote and realized that was not entirely correct, however to be fair, they also have nice applet to change different Nvidia profiles and (at least for me) it nicely boots and installs, unlike Mint or Ubuntu, that have same base and Nvidia drivers in the iso (at least Mint).
Right, although the main reason sticking with nouveau is wayland and touch-pad gestures on the laptop.
Yes, I will give a try as soon as I got some time and will report back results. Actually, all the distros I have tried and installed were mostly with Gnome or Plasma. I was thinking GDM could be the cull-print, so I was using Manjaro KDE, but the problem occurred also there, as well as with LMDE, which used Slick/LightDM.
So I installed Mint Cinnamon, after found out instructions in their website as to how overcome the issue I was experiencing.
The issue is still there, however I have noticed that when I suspend from GUI, e.g. start menu, I am able to recover, wake up from suspend (with propriety drivers), however, when I suspend with closing lid, then I am not able to recover.
I also set lid closure to locking screen, then closing and opening works just fine.
Furthermore, when lid closure is set to lock screen, and if I suspend from start menu and close the lid, than I can open and resume properly.
So the problemm seems to be to do how Dell handles lid opening (closing?), as in other scenarios I need to press the power button to wake from suspend, but in problematic scenario, it seems lid opening try to toggle power on (and the light on button becomes lit), but for some reason it does not able to properly boot.
So the solution seems to be to set lid close/open to nothing, and let the laptop sleep after some time. I’ll install Gnome back and try if this solution works.
meanwhile @milangujarat, you may try to toggle, OFF “suspend when laptop lid is closed” in Gnome Tweaks.
or edit /etc/systemd/logind.conf and uncomment/add HandleLidSwitch=ignore, option.
That is what I would call a workaround. It is still not a fix. There is a compromise you have to make for the sleep (i.e. disabling the lid closing sleep). Let us keep the thread open so people who have faced issue regarding this can follow through and let you know.
I also have a similar suspend problem with Fedora 32 + NVIDIA driver.
Sometime when I resume a suspended session, X crash and I must re-login and start all my previous open applications
I have fill this bug on Bugzilla and attach to it some logs get from last crashed session.
Someone can help me to resolve this issue? or it’s better I post this problem on Fedora ML?
No, I was not clear. As I was trying different distros (and mostly Gnome) I thought that the reason for the problem could be GDM, so I decided to use Plasma (with SDDM), to see if the login manager is the reason.
I am know one can also change only DM, but I was changing either full distros or DEs.
I am also having similar issues with the Lenovo G50-80 since I upgraded OS from dual boot (Windows + Fedora 23) to single boot Fedora 32.
Following is a summary of the unexpected things I have observed so far:
Almost all the time “sleep/suspend” is not working and I have to go for the forced shutdown of the system. Because when this happens non of the other key responds. No matter what I try the system won’t wake up.
Power issue: A few times when the system is inactive for some time and if there is a sudden interruption in the AC power supply (like I remove AC adaptor) then within a fraction of the second system will show low battery warning and try to go to sleep. If I am quick enough to either reconnect the AC adapter or press any key then the session is saved else it will end up in a frozen state. However, this does not happen if the system is active i.e. external power cut won’t lead to system freeze if I happen to be working on it the system at that moment.
Note on power setting: I have cross-checked the power setting. Options are: Blank screen = Never, Suspend when on battery= Never, Susped when on AC= Never.
Note on battery condition: Battery is in good condition and still provides a backup of about 3 hours under average working load.
Blinking screen: When I try to save the system from a sudden power cut as mentioned in point-2, for a few seconds screen will starting blinking. It is so annoying that a few times user will get locked and I have to log in (unlock) while the screen is still blinking. However, after login, the screen gets stable (i.e. stop blinking) in a few seconds. This happens even when I have reconnected back the AC power quickly.
Boot issue: A few times system won’t boot completely and will be stuck somewhere in between. For this, I have to do a forced reboot using Ctrl+Alt+Delete and just hope that it will reboot properly and won’t freeze again. However, a few of the time, even the Ctrl+Alt+Delete also won’t help to reboot and I have to do a hard reboot by pressing the power button.
Blank screen while booting: A few to times after pressing the power button only the keyboard and WebCam LED response and the screen stay off (blank). This is the most funny part, but, the screen shows some signs of life if I try to close it. (This seems to be a hardware issue, right? But why only a few times?)
Please let me know if you are able to figure out what the problem is. Are these issues related to software or hardware? Also, should I wait for a fix or go for a new laptop because I am sure that a lot of forced shut-downs (with the power button) will lead to the hard-disk crash one day.
The system info is provided below. Kindly let me know if you need any other system information.
H/W path Device Class Description
/0 bus Motherboard
/0/0 memory 12GiB System memory
/0/1 processor Intel(R) Core™ i5-5200U CPU @ 2.20GHz
/0/100 bridge Broadwell-U Host Bridge -OPI
/0/100/2 display HD Graphics 5500
/0/100/3 multimedia Broadwell-U Audio Controller
/0/100/14 bus Wildcat Point-LP USB xHCI Controller
/0/100/16 communication Wildcat Point-LP MEI Controller #1
/0/100/1b multimedia Wildcat Point-LP High Definition Audio Controller
/0/100/1c bridge Wildcat Point-LP PCI Express Root Port #1
/0/100/1c.2 bridge Wildcat Point-LP PCI Express Root Port #3
/0/100/1c.2/0 enp2s0 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
/0/100/1c.3 bridge Wildcat Point-LP PCI Express Root Port #4
/0/100/1c.3/0 wlp3s0 network QCA6164 802.11ac Wireless Network Adapter
/0/100/1f bridge Wildcat Point-LP LPC Controller
/0/100/1f.2 scsi1 storage Wildcat Point-LP SATA Controller [AHCI Mode]
/0/100/1f.2/0.0.0 /dev/cdrom disk DVDRAM GUC0N
/0/100/1f.3 bus Wildcat Point-LP SMBus Controller
/0/2 system PnP device PNP0c02
/0/3 system PnP device PNP0b00
/0/4 generic PnP device INT3f0d
/0/5 input PnP device PNP0303
/0/6 generic PnP device SYN2b37
/0/7 system PnP device PNP0c02
/1 mmc0 bus MMC Host
NO NEED FOR FORCED SHUTDOWN, SYSTEM CAN RESUME FROM A FROZEN STATE (EVEN WHEN KEYBOARD IS ALSO UNRESPONSIVE).
Just found that if I keep pressing keyboard keys (like Enter, spacebar) for some time (like for about a minute), the system eventually responds after some time. This happens even when the system has gone to freeze state and the keyboard appears to be unresponsive (i.e., no change in the state of NumLock, CapsLock key’s led indicator after pressing them). After some time, the system wakes up but with a blinking screen which also gets resolved after few seconds of unlocking the user.
But, I am still wondering what the issue.
Note: This blinking (toggling) screen I first observed when I booted the Fedora32 from a USB stick-drive. Due to some reason, I had to physically close the laptop screen when Fedora32 when I was using it from a USB stick drive. But, after some time, when I opened the laptop screen, it was toggling. That time I thought it may be due to a low data transfer rate between USB stick-drive and laptop. But, right now I am booting Fedora32 from an internal hard disk (Lenovo 1TB). So wondering what can be the reason.
Also, I have a RAM of 12GB and SWAP of 15GB so memory is not a problem I guess.
Let me know if anyone of you has figured out the reason for this issue!
Well the issues typically occurs because Fedora has newer(cutting/bleeding edge) packages, whereas Matlab uses old packages. Officially, Fedora is not one of the supported by Matlab distros.
e.g. this time when I was installing Matlab 2019b on Fedora 32, it was only using software opengl (and apparently this was also case on “supported” distro). The installer of Matlab 2020a would not even start, as there was a conflict with lybcrypt package, and solution was to copy it from debian docker, or so (found in Matlab forums via googling).
At the moment, with 2019b you can install without issues, and if you want hardware opengl in Matlab you can create/edit the matlab.desktop file with the following exec
Fedora keeps applications updated true but also has the stability that you would get to see in any other standard release based distro as discretion is maintained while updating packages and none are pushed to the point where their dependencies are unavailable or too unfit to be compatible.
Sure! thanks for the correction, I always confuse differences in all those edges
My point was that typically packages in Fedora are much newer (or getting faster (version) updates) than in Ubuntu or Debian version (especillay the ones that are supported by Matlab, that also lag at least a Distro release behind).
I was not implying that Fedore is less stable because of newer packages.