| 8 May 2026 |
sudoforge | so, there's literally nothing going on before your systemctl cancel? | 02:29:36 |
sudoforge | and, can you go into more detail about "not being able to fully sleep" and "not being able to wake up completely from sleep"? what are the symptoms you experience? | 02:30:16 |
Just Some Dude | It doesn't look like it to me but I don't really know how to interpret it | 02:30:35 |
Just Some Dude | When I close it or use systemctl suspend it just turns the screen off but keeps burning battery like crazy, then when I open it back up the network adapter is dead until I use systemctl cancel | 02:31:59 |
Just Some Dude | I can't remember where I got the "fix" of interrupting sleep because it was still ongoing it was a while ago | 02:33:12 |
Just Some Dude | * | 03:31:17 |
sudoforge | Just Some Dude can you share the output of cat /sys/power/mem_sleep? | 05:25:55 |
sudoforge | and what mainboard are you using? | 05:28:43 |
sudoforge | basically... intel and amd have both dropped support for s3 AFAIK, so i don't think the newer chips support it. you should configure hibernation to achieve the low power state that you want. | 05:44:36 |
Marien Zwart | Iirc you'd still see something in dmesg even if it's only suspending to idle (or similar) | 05:46:56 |
Daniel Schaefer (Framework) | Last two generations Intel and AMD don't support S3
But support s0ix/modern standby instead
Hibernate is not normally needed unless you want to have the system consume the absolute minimum power
| 06:22:29 |
Daniel Schaefer (Framework) | Intel core ultra series 1 and 3 | 06:22:50 |
sophronesis | In reply to @michael.zeagler:matrix.org Would this be a good place to troubleshoot my framework 13 not being able to fully sleep and not being able to wake up completely from sleep without using systemctl cancel? https://m.youtube.com/watch?v=SewVWYVeZV4 maybe relevant | 06:45:37 |
| jopejoe1 (4094@eh22) changed their display name from jopejoe1 (4094@epvpn) to jopejoe1. | 08:42:13 |
Marien Zwart | after systemctl suspend, on a framework 13 (7040 series), first thing in dmesg on the way towards suspend is PM: suspend entry (s2idle) and the power led slowly blinks once suspended. Been a while since I debugged something like this, but if you're not seeing those things systemd may not be reaching suspend.target (system journal may have clues) | 10:19:04 |
Just Some Dude | Redacted or Malformed Event | 16:59:25 |
Just Some Dude | * <code>Operating System: NixOS 25.11
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.19.3 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 13th Gen Intel® Core™ i5-1340P
Memory: 64 GiB of RAM (60.5 GiB usable)
Graphics Processor: Intel® Iris® Xe Graphics
Manufacturer: Framework
Product Name: Laptop (13th Gen Intel Core)
System Version: A4</code> | 16:59:36 |
Just Some Dude | Redacted or Malformed Event | 17:00:48 |
Just Some Dude | It's a 13th gen intel i5-1340P | 17:01:42 |
Just Some Dude | [s2idle] deep | 17:02:05 |
Just Some Dude | which apparently means it's the s0ix modern standby? | 17:21:42 |
Just Some Dude | Would the problem be that my generation of processor doesn't support the modern standby? | 17:24:49 |
Just Some Dude | I updated the BIOS but that didn't do it either. | 17:28:16 |
Just Some Dude | I had to uninstall/disable displaylink in order to get fully up to date on the kernel so I'm not sure if it was displaylink or the kernel, but it's working as advertised now. | 20:27:21 |
Just Some Dude | At the bottom of the displaylink page there's an entry about it blocking pre-sleep service 😭 | 20:29:45 |
Just Some Dude | Thanks everyone for all your help | 20:30:02 |
sudoforge | glad you got it sorted! | 22:11:00 |
sudoforge | apologies for being mostly unavailable today | 22:11:13 |
Just Some Dude | Lol now I have to find out how to install newer displaylink versions that might have fixed it. Onward and upward right? | 22:12:52 |
Just Some Dude | No worries! Thanks for helping me find my way through. | 22:13:19 |