You are not logged in.
Greetings,
It's been two weeks since i got my very first Thinkpad, an L13 yoga gen 2 (i5 1135g7 16/256), with arch linux obviously.
since the beginning i've been having issues with the resume from Sleep.
--- the issue ---
The issue occours when the computer is put to sleep by closing the lid, if i try to put to sleep the computer in any other way (like by using "systemctl sleep", or using the DE gui or shortcut ctrl+4) this issue is absent.
The sleep option on the bios is currently set to S3-Linux and only with that option i can resume the laptop with the "Fn" key, otherwise power button or any other clickable thing does nothing.
s2idle (Windows sleep on bios) makes things worse as the Fn key does absolutely nothing and i can't resume the laptop in any way.
--- Troubleshooting steps i already tried ---
- Switching from [deep/s3 linux] to [Windows/s2idle] sleep
- Disabling TPM module in bios
- Using the kernel boot parameter "intel_iommu=off"
- i915 driver related stuff ( im using the Xe driver but even with the i915 one, the issue is still there)
- updating kernel (currently using linux 7.2.9-2-cachyos-bore-lto)
- updating firmware with fwupd [bios and IntelManagementEngine is on latest version available)
-------
any help would be appreciated, thanks!
Offline
issue occours when the computer is put to sleep by closing the lid … currently set to S3-Linux … can resume the laptop with the "Fn" key
You kinda forgot to describe the symptoms of the issue that's occurring when sleeping via lid.
grep -i lid /etc/systemd/logind.conf
cat /proc/acpi/wakeupand if you can please post a journal of the boot after waking from lid-induced sleep.
sudo journalctl -b | nc termbin.com 9999or
sudo journalctl -b -1 | nc termbin.com 9999for the previous (-1) one.
Edit: ceterum censeo, in case there's a parallel windows installation see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Last edited by seth (2026-10-16 14:57:57)
Offline
Here is the journalctl log of a boot were i put the Laptop to sleep by closing the lid and then waking it up by opening the lid and pressing "Fn":
here is also the output of the first two commands:
❯ grep -i lid /etc/systemd/logind.conf
cat /proc/acpi/wakeup
36:HandleLidSwitch=suspend
37:#HandleLidSwitchExternalPower=suspend
38:#HandleLidSwitchDocked=ignore
43:#LidSwitchIgnoreInhibited=yes
Device S-state Status Sysfs node
PEG0 S4 *enabled pci:0000:00:06.0
PEGP S4 *disabled pci:0000:04:00.0
PEG1 S4 *disabled
PEGP S4 *disabled
PEG2 S4 *disabled
PEGP S4 *disabled
GLAN S4 *enabled pci:0000:00:1f.6
XHCI S3 *enabled pci:0000:00:14.0
XDCI S4 *disabled
HDAS S4 *disabled pci:0000:00:1f.3
RP01 S4 *disabled
PXSX S4 *disabled
RP02 S4 *disabled
PXSX S4 *disabled
RP03 S4 *disabled
PXSX S4 *disabled
RP04 S4 *disabled
PXSX S4 *disabled
RP05 S4 *enabled pci:0000:00:1c.0
PXSX S4 *disabled pci:0000:0c:00.0
*disabled platform:rtsx_pci_sdmmc.0
RP06 S4 *disabled
PXSX S4 *disabled
RP07 S4 *disabled
PXSX S4 *disabled
RP08 S4 *disabled
PXSX S4 *disabled
RP09 S4 *disabled
PXSX S4 *disabled
RP10 S4 *disabled
PXSX S4 *disabled
RP11 S4 *disabled
PXSX S4 *disabled
RP12 S4 *disabled
PXSX S4 *disabled
RP13 S4 *disabled
PXSX S4 *disabled
RP14 S4 *disabled
PXSX S4 *disabled
RP15 S4 *disabled
PXSX S4 *disabled
RP16 S4 *disabled
PXSX S4 *disabled
RP17 S4 *disabled
PXSX S4 *disabled
RP18 S4 *disabled
PXSX S4 *disabled
RP19 S4 *disabled
PXSX S4 *disabled
RP20 S4 *disabled
PXSX S4 *disabled
RP21 S4 *disabled
PXSX S4 *disabled
RP22 S4 *disabled
PXSX S4 *disabled
RP23 S4 *disabled
PXSX S4 *disabled
RP24 S4 *disabled
PXSX S4 *disabled
CNVW S4 *disabled pci:0000:00:14.3
TXHC S4 *enabled pci:0000:00:0d.0
TDM0 S4 *disabled
TDM1 S4 *enabled pci:0000:00:0d.3
TRP0 S4 *disabled
PXSX S4 *disabled
TRP1 S4 *disabled
PXSX S4 *disabled
TRP2 S4 *enabled pci:0000:00:07.0
PXSX S4 *disabled
TRP3 S4 *disabled
PXSX S4 *disabled
AWAC S4 *enabled platform:ACPI000E:00
SLPB S3 *enabled platform:PNP0C0E:00
LID S4 *enabled platform:PNP0C0D:00When putting the pc to sleep by closing the lid, the power button, keystrokes (except Fn), touchpad/trackpoint movement, Touch screen, repeated lid open/close simply doesnt wake up the pc. Only "Fn" key wakes it up.
Offline
Oct 16 17:18:18 ThinkingRock systemd-logind[1105]: Lid closed.
Oct 16 17:18:18 ThinkingRock NetworkManager[1099]: <info> [1792163898.2418] manager: sleep: sleep requested (sleeping: no enabled: yes)
Oct 16 17:18:30 ThinkingRock systemd-logind[1105]: Lid opened.
Oct 16 17:18:31 ThinkingRock niri[1797]: libinput error: event1 - Lid Switch: client bug: event processing lagging behind by 1323ms, your system is too slowIs this also the case when only booting and sleeping from/waking to the multi-user.target (2nd link below)?
Offline
In the previews log i was still in the graphical target ( i didn't specify it before but it is Niri + DMS-shell )
Here, is journalctl with the multi-user.target:
Offline
The idea was to test whether you can wake the system w/ the lid this way (since it's enabled for wakeup and the previous journal looks like that's what woke the system - hypothesis being that niri keeps DPMS and only activates the monitor on keypress, though even then Fn out of all keys is strange)
Offline
since it's enabled for wakeup and the previous journal looks like that's what woke the system - hypothesis being that niri keeps DPMS and only activates the monitor on keypress, though even then Fn out of all keys is strange
I think that the "Fn" key to wake up is a thinkpad thing and apparently that's working how it's supposed to.
also it is not just the monitor that's off, it's the entire pc because:
- LEDs on the keyboard are off
- power button / "i" on the thinkpad lid logo is still breathing slowly (so pc is still asleep)
- Fan doesnt power on (usually when it resumes from sleeps, the fan briefly spins up)
It's a strange behavoir that the lid switch has, because i cant find an explaination to what is different from putting the pc to sleep by command or by the switch.
Offline
I think that the "Fn" key to wake up is a thinkpad thing and apparently that's working how it's supposed to.
:colbertemoji:
Have/can you test the behavior on some random live distro?
Is this maybe related to whether the notbook is attached to a dock/external power?
Offline
The preoblem persists with both the laptop connected to the charger and also while on a live iso (i tested with a CachyOs iso i had on a usb drive)
Offline