You are not logged in.
Pages: 1
I installed arch on my ssd with full disk encryption and with removable header and /boot.
Everything went fine, but when I suspend and try to wake up my laptop, it gets a black screen (actually the screen doesn't even turn on), the caps lock button doesn't light up, and the only way to turn it off is to hard reset.
I have another arch installed on another hd, this arch has KDE(Wayland) installed and the suspend works normally, so I think the problem is with some configuration or driver, but I am not sure.
Comparing the journals of the two systems, I think my system can't finish the processes for suspend because it hangs on
PM: suspend entry (deep) and on my other system it continues with:
Apr 27 05:36:39 darkArch-OS kernel: PM: suspend entry (deep)
Apr 27 05:36:40 darkArch-OS kernel: Filesystems sync: 0.743 seconds
Apr 27 05:36:48 darkArch-OS kernel: Freezing user space processes
Apr 27 05:36:48 darkArch-OS kernel: Freezing user space processes completed (elapsed 0.004 seconds)
Apr 27 05:36:48 darkArch-OS kernel: OOM killer disabled.
Apr 27 05:36:48 darkArch-OS kernel: Freezing remaining freezable tasks
Apr 27 05:36:48 darkArch-OS kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) May help:
cat /sys/power/mem_sleep
s2idle [deep]
cat /etc/systemd/sleep.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation; either version 2.1 of the License, or (at your option)
# any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the sleep.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# See systemd-sleep.conf(5) for details.
[Sleep]
#AllowSuspend=yes
#AllowHibernation=yes
#AllowSuspendThenHibernate=yes
#AllowHybridSleep=yes
#SuspendMode=
#SuspendState=mem standby freeze
#HibernateMode=platform shutdown
#HibernateState=disk
#HybridSleepMode=suspend platform shutdown
#HybridSleepState=disk
#HibernateDelaySec=
#SuspendEstimationSec=60minHave looked at other threads but got nothing.
I use Hyprland(Wayland) and i don't have nvidia gpu.
My journalctl
Offline
Can you suspend and resume from and when only booting the multi-user.target?
(2nd link below)
The more interesting question is what the other OS does differently ahead.
Are both encrypted?
Why do you explcitly set "mem_sleep_default=deep", does the other OS only sleep shallow?
Also
darkarch/darkArch-OS
Is this the darkarch distro/live-os?
Offline
Can you suspend and resume from and when only booting the multi-user.target?
No
Are both encrypted?
Yes, but the other system has a partition on the disk for /boot, and it is not a removable(detached?) header.
Why do you explcitly set "mem_sleep_default=deep", does the other OS only sleep shallow?
It's just that I was trying solutions in other threads and forgot to remove them. But on my other OS the configuration is the same.
My other OS:
cat /sys/power/mem_sleep
s2idle [deep]Is this the darkarch distro/live-os?
No, it's just that when I was installing it, I got the names mixed up and it ended up like this.
Basically the only differences between them is that this new installation has no KDE installed, the /boot partition and the LUKS header are on my PenDrive and the new OS is on an SSD.
Both have wayland. So I guess when I installed KDE, it also installed some package that made the suspension work.
I have also tried with "linux-lts" but nothing changed.
I forgot to mention that both use Unified kernel image and systemd-boot. If this helps at all.
Last edited by JupiterRing (2023-04-29 10:39:27)
Offline
I guess when I installed KDE, it also installed some package that made the suspension work.
Possible but not very likely. Although there's some other thread where suspending from iirc gnome failed, but from KDE worked.
But I'd rather put that down as an issue w/ gnome.
Can you wake from sleep from the multi-user.target on the KDE system?
Offline
Can you wake from sleep from the multi-user.target on the KDE system?
Yes, i can.
When I have more time I will try to take a closer look at it.
Or maybe I just wait and see if some kernel update will magically fix this. ;P
Offline
You can try to install plasma on the system, reboot and see whether that indeed changed anything.
If so, that's gonna be an interesting pacman log…
Offline
I will test this later, and post here
Offline
Unfortunately it didn't work.
But I'll wait and see if an update will fix it. If I need to suspend my laptop I will boot my KDE OS.
PS: Do I mark the topic as solved or something like that?
Offline
There's no solution, so that would be wrong.
You can just leave it open and return later.
Do you mount the drive of the "bad" installation when you boot the "good" one?
Offline
Do you mount the drive of the "bad" installation when you boot the "good" one?
Nop
Offline
The implication would be to test that (and ideally open some files on it) to see whether it's the device that won't play ball.
Offline
Hey https://bbs.archlinux.org/profile.php?id=150652 JupiterRing! Have you found any cause of the bad wake up from deep-sleep? I am facing exactly the same issue and haven't found any way to fix it. The only sleeping mode that works for me is s2idle which is obviously not ideal.
Offline
Pages: 1