- Famework Desktop w. Ryzen AI Max 395+
- OS: Fedora 44 Workstation KDE, Clean Install
- latest bios 3.05
I’ve been losing my mind trying to get my Framework desktop to only wake up:
- if I use my keyboard or mouse (via a logitech unifying receiver, so not bluetooth but USB)
- if I send it a WWOL (wake on wireless lan) packet from another machine on the same wifi network
- there is nothing else plugged in except the Logitech Unifying Receiver
I’ve enabled Wake on Lan in BIOS, and Wireless Wake on Lan in the OS
Now I randomly get my PC woken up from sleep, it wakes up is the LED suddenly and stays ON and I hear the fans coming on.
The weird part is the video out is not working, although fans are working.
To fully enable video out I have to try to wake it up again using mouse/kb.
There’s no possibility that the mouse and kb have triggered it since I turn them both off right after sleep and I checked and the unifying receiver is only paired with these 2 devices that I turn off.
I tried everything, I created some custom scripts and wake override scripts with chatgpt
for dev in GPP0 GPP1 GPP3 GPP5 GPP7 NHI0 NHI1; do
ifgrep -q "^$dev.*enabled"/proc/acpi/wakeup; then
echo "$dev"> /proc/acpi/wakeup
fi
done
If it helps here’s the output from cat /proc/acpi/wakeup
Device S-state Status Sysfs node
GPP0 S4 *enabled pci:0000:00:01.1
SWUS S4 *disabled
GPP1 S4 *enabled pci:0000:00:01.2
SWUS S4 *disabled
GPP3 S4 *enabled pci:0000:00:02.1
GPP5 S4 *enabled pci:0000:00:02.3
GPP7 S4 *enabled pci:0000:00:02.5
GPP9 S4 *disabled
XHC1 S4 *enabled pci:0000:c2:00.4
XHC0 S4 *enabled pci:0000:c4:00.0
XHC3 S4 *enabled pci:0000:c4:00.3
XHC4 S4 *enabled pci:0000:c4:00.4
NHI0 S4 *enabled pci:0000:c4:00.5
NHI1 S4 *enabled pci:0000:c4:00.6
This is what journalctl tells me
f44 kernel: PM: suspend devices took 0.165 seconds
f44 kernel: ACPI: EC: interrupt blocked
f44 kernel: ACPI: EC: interrupt unblocked
f44 kernel: amdgpu 0000:c2:00.0: [drm] PCIE GART of 512M enabled (table at 0x00>
f44 kernel: amdgpu 0000:c2:00.0: SMU is resuming...
f44 kernel: amdgpu 0000:c2:00.0: SMU is resumed successfully!
f44 kernel: nvme nvme0: 8/0/0 default/read/poll queues
f44 kernel: amdgpu 0000:c2:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring comp_1.2.0 uses VM inv eng 6 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring comp_1.3.0 uses VM inv eng 7 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring comp_1.0.1 uses VM inv eng 8 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring comp_1.1.1 uses VM inv eng 9 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring comp_1.2.1 uses VM inv eng 10 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring comp_1.3.1 uses VM inv eng 11 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring sdma0 uses VM inv eng 12 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring vcn_unified_0 uses VM inv eng 0 on hub 8
f44 kernel: amdgpu 0000:c2:00.0: ring vcn_unified_1 uses VM inv eng 1 on hub 8
f44 kernel: amdgpu 0000:c2:00.0: ring jpeg_dec_0 uses VM inv eng 4 on hub 8
f44 kernel: amdgpu 0000:c2:00.0: ring jpeg_dec_1 uses VM inv eng 6 on hub 8
f44 kernel: amdgpu 0000:c2:00.0: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
f44 kernel: amdgpu 0000:c2:00.0: ring vpe uses VM inv eng 7 on hub 8
f44 kernel: PM: resume devices took 0.303 seconds
f44 kernel: OOM killer enabled.
f44 kernel: Restarting tasks: Starting
f44 kernel: Restarting tasks: Done
f44 kernel: efivarfs: resyncing variable state
f44 kernel: efivarfs: finished resyncing variable state
f44 kernel: random: crng reseeded on system resumption
f44 kernel: PM: suspend exit
f44 systemd-sleep[3264]: System returned from sleep operation 'suspend'.
f44 bluetoothd[1100]: Controller resume with wake event 0x0
f44 kwin_wayland[1893]: The main thread was hanging temporarily!
f44 systemd[1]: user.slice: Unit now thawed.
f44 systemd[1]: user-1000.slice: Unit now thawed.
f44 systemd[1]: session-1.scope: Unit now thawed.
f44 systemd-sleep[3264]: Successfully thawed unit 'user.slice'.
f44 systemd[1]: user@1000.service: Unit now thawed.
f44 systemd[1]: systemd-suspend.service: Deactivated successfully.
f44 systemd[1]: Finished systemd-suspend.service - System Suspend.
f44 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=sys>
f44 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=syst>
f44 systemd[1]: Stopped target sleep.target - Sleep.
f44 systemd[1]: Reached target suspend.target - Suspend.
f44 systemd-logind[1155]: Operation 'suspend' finished.
f44 systemd[1]: Stopped target suspend.target - Suspend.
f44 systemd-resolved[869]: Closing all remaining TCP connections.
f44 systemd-resolved[869]: Resetting learnt feature levels on all servers.
f44 ModemManager[1230]: [sleep-monitor-systemd] system is resuming
f44 NetworkManager[1104]: [1785064459.7629] manager: sleep: wake reques>
f44 NetworkManager[1104]: [1785064459.7630] device (wlp192s0): state ch>
f44 NetworkManager[1104]: [1785064459.7632] dhcp4 (wlp192s0): canceled >
f44 NetworkManager[1104]: [1785064459.7632] dhcp4 (wlp192s0): activatio>
f44 NetworkManager[1104]: [1785064459.7632] dhcp4 (wlp192s0): state cha>
f44 NetworkManager[1104]: [1785064459.7633] dhcp6 (wlp192s0): canceled >
f44 NetworkManager[1104]: [1785064459.7633] dhcp6 (wlp192s0): activatio>
f44 NetworkManager[1104]: [1785064459.7633] dhcp6 (wlp192s0): state cha>
Note that after I noticed the fans spinning up and LED staying on, I then gave it KB and mouse input to wake it for video out and try to troubleshoot.