> On Thu, 2020-08-27 at 07:32 +0000, laolux laolux wrote: > > Do you have different suspend options in the BIOS (or UEFI)? It could > be that you can change a setting so that the laptop still provides > enough power to its RAM during suspend that it can resume. > > Hibernation could be a problem if you don't have a large enough swap > partition, or swap file, or don't have a kernel options specifying > which swap to resume from. Well, I do not think that lock screen should invoke any power saving options as programs are expected to keep running. Yet, locking the screen freezes my system. I actually investigated further and found that locking the screen crashes my fedora 32 for any kernel from 5.4 to 5.8. About 20 seconds after locking the screen the computer is dead and even breaks existing ssh connections. Funnily enough suspend works up to kernel 5.7.5, I just need to make sure to immediately enter my password. From 5.7.6 onward everything is broken. However, I think I tracked the problem to the i915 kernel module. Setting `i915.modeset=0` in grub lets my computer lock the screen and continue working. Also suspend works on all kernels, including wakeup. Only issue with `i915.modeset=0` is that once the srceen turns black it will stay that way until reboot. But I can enter my password to unlock the desktop and issue commands, just need to remember to do everything without seeing -> no typos please ;-) So I reported it upstream as bug in the intel linux driver: https://gitlab.freedesktop.org/drm/intel/-/issues/2404 Let's see if anything comes from that. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
