(issue is also present on the latest 6.18, I tried downgrading to fix it to no avail)
Which BIOS version are you using?
3.0.5
Which Framework Laptop 13 model are you using?
AMD Ryzen™ AI 300 Series
So everytime the laptop goes to sleep (s2idle) since actual deep is not available. I get a black screen when I try to wake it up.
I have exhausted all options I can think of. Nothing can wake the laptop up. Dumping the logs into an llm tells me it is the gpu driving failing to resume
Please help, this is super annoying. I tried turning sleep off but that nearly cooked my laptop when I put it in my backpack and it started overheating.
+1 on this, and it’s a recent software update that caused it. I run Silverblue and so was able to test an older version of my OS, and the older version suspends and resumes how I would expect. That indicates to me that the change that caused this was made with a package or driver (I’m running 6.18 and it sounds like from your description that it wasn’t a kernel issue). Are you also using the AX210 wifi card? I’ve had suspend issues with it before, maybe the problem is an issue with the package that manages the wifi card. This is also driving me up a wall though, suspend is pretty important.
Same problem with Fedora 43 on fw13, AI 340, with AX210 wifi card. My kernel version is 6.18.16-200.fc43.x86_64.
Here is the log towards the end of the boot:
Mar 08 15:18:34 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Mar 08 15:18:34 kernel: rfkill: input handler disabled
Mar 08 15:18:35 kernel: usb 1-1: reset full-speed USB device number 2 using xhci_hcd
Mar 08 15:18:37 kernel: usb 1-1: reset full-speed USB device number 2 using xhci_hcd
Mar 08 15:18:40 systemd-journald[632]: File /var/log/journal/555cd8bf26f04ac1928bc523bf184451/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
Mar 08 15:18:40 kernel: rfkill: input handler enabled
Mar 08 15:18:40 kernel: input: xremap as /devices/virtual/input/input16
Mar 08 15:18:41 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Mar 08 15:18:41 kernel: rfkill: input handler disabled
Mar 08 15:18:42 kernel: input: vicinae-snippet-virtual-keyboard as /devices/virtual/input/input17
Mar 08 15:18:44 kernel: hid-generic 0003:32AC:0002.0005: hiddev96,hidraw0: USB HID v1.11 Device [Framework HDMI Expansion Card] on usb-0000:c3:00.0-2/input1
Mar 08 15:18:53 kernel: input: xremap as /devices/virtual/input/input18
Mar 08 15:20:18 kernel: usb 1-1: reset full-speed USB device number 2 using xhci_hcd
Mar 08 15:20:18 kernel: usb 1-1: reset full-speed USB device number 2 using xhci_hcd
Mar 08 15:24:35 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Mar 08 15:24:38 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Mar 08 15:24:38 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Mar 08 15:24:38 kernel: wlp192s0: deauthenticating from 00:40:9d:e0:d1:49 by local choice (Reason: 3=DEAUTH_LEAVING)
Mar 08 15:24:39 kernel: PM: suspend entry (s2idle)
Mar 08 15:24:39 kernel: Filesystems sync: 0.030 seconds
Not that helpful. The only error reported previously had something to do with amdxdna:
Mar 08 15:18:16 kernel: amdxdna 0000:c2:00.1: [drm] *ERROR* aie2_check_protocol: Incompatible firmware protocol major 7 minor 2
Mar 08 15:18:16 kernel: amdxdna 0000:c2:00.1: [drm] *ERROR* aie2_hw_start: firmware is not alive
...
Mar 08 15:18:16 kernel: amdxdna 0000:c2:00.1: [drm] *ERROR* aie2_smu_exec: smu cmd 4 failed, 0xff
Mar 08 15:18:16 kernel: amdxdna 0000:c2:00.1: [drm] *ERROR* aie2_smu_fini: Power off failed, ret -22
Mar 08 15:18:16 kernel: amdxdna 0000:c2:00.1: [drm] *ERROR* aie2_init: start npu failed, ret -22
Mar 08 15:18:16 kernel: amdxdna 0000:c2:00.1: [drm] *ERROR* amdxdna_probe: Hardware init failed, ret -22
Mar 08 15:18:16 kernel: amdxdna 0000:c2:00.1: probe with driver amdxdna failed with error -22
The solution there worked for me as well! Definitely annoying that a pretty useless part of the computer broke suspend like that. If you do for whatever reason use the NPU in your machine this will break its functionality until you un-blacklist it