Laptop wakes up immidtiately when suspending to ram when monitor con.

znerk · 2022-12-29 13:21:08

When I have a external monitor connected to my laptop connected through HDMI and the lid closed, the pc wakes up immediately when running the sleep(ram) command from KDE. I have tried removing all connected external devices besides the monitor, so I think that narrows it down. Any tips?

seth · 2022-12-29 13:36:58

sleep 10; systemctl suspend

and remove the HDMI before the system enters S3 (increase the sleep if yuo need more than 10s to pull the HDMI plug)
If the problem remains, it's probably the closed lid.
And even if not, what could happen is that the HDMI shuts down, some daemon activates the lid and the lid the acpi wake.

cat /proc/acpi/wakeup

One of those is likely the lid and echoing it's 3/4 letter code into /proc/acpi/wakeup will toggle its wakeup status.

znerk · 2022-12-29 13:45:21

seth wrote:

sleep 10; systemctl suspend
and remove the HDMI before the system enters S3 (increase the sleep if yuo need more than 10s to pull the HDMI plug)
If the problem remains, it's probably the closed lid.
And even if not, what could happen is that the HDMI shuts down, some daemon activates the lid and the lid the acpi wake.
cat /proc/acpi/wakeup
One of those is likely the lid and echoing it's 3/4 letter code into /proc/acpi/wakeup will toggle its wakeup status.

and right after I unplug the HDMI I can ping the machine to see if it wakes up, right? Still wakes up without the hdmi then

cat /proc/acpi/wakeup returns:

Device  S-state   Status   Sysfs node
PEG0      S4    *disabled
PEGP      S4    *disabled
PEG1      S4    *disabled
PEGP      S4    *disabled
PEG2      S4    *disabled
PEGP      S4    *disabled
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    *disabled
PXSX      S4    *disabled
RP06      S4    *disabled
PXSX      S4    *disabled
RP07      S4    *disabled
PXSX      S4    *disabled
RP08      S4    *disabled
PXSX      S4    *disabled
RP09      S4    *enabled   pci:0000:00:1d.0
PXSX      S4    *disabled  pci:0000:55:00.0
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    *enabled   pci:0000:00:0d.2
TDM1      S4    *disabled
TRP0      S4    *enabled   pci:0000:00:07.0
PXSX      S4    *disabled
TRP1      S4    *enabled   pci:0000:00:07.1
PXSX      S4    *disabled
TRP2      S4    *disabled
PXSX      S4    *disabled
TRP3      S4    *disabled
PXSX      S4    *disabled
AWAC      S4    *disabled

Last edited by znerk (2022-12-29 13:54:32)

znerk · 2022-12-29 14:05:17

Update, sorry but I was terribly dumb and didn't test unpluggng all usb devices at the same time. If I do that, the computer does not wake up. Now my question is what alternatives do I have? These are wireless devices, and from reading around I can see that this is a common issue. However, I would like to not be dependent on opening the laptop to wake it from sleep.

Based on this thread it looks like I am out of lucK?
https://bbs.archlinux.org/viewtopic.php?id=257928

I am in fact also using Logitech devices. One receiver for the keyboard, and one for the mouse. I am planning on switching to a usb cabled keyboard real soon again. Could it be a solution to then only enable wakeup from the cabled keyboard, and disable wakeup from the mouse?

Last edited by znerk (2022-12-29 14:13:20)

seth · 2022-12-29 14:31:04

XHCI is usb for sure, if you don't mind not being able to wake the system w/ your keyboard, you could toggle that.

echo XHCI | sudo tee /proc/acpi/wakeup

For the other devices, please also post "lspci".
If there's only one usb acpi device, you'll have a hard time enabling the wakeup from the cabled keyboard but ignoring the wireless mouse dongle on the same bus.

Though maybe:
https://forums.opensuse.org/t/logitech- … y/104001/2
https://archlinux.org/packages/community/any/solaar/

znerk · 2022-12-29 14:32:36

seth wrote:

XHCI is usb for sure, if you don't mind not being able to wake the system w/ your keyboard, you could toggle that.
echo XHCI | sudo tee /proc/acpi/wakeup
For the other devices, please also post "lspci".
If there's only one usb acpi device, you'll have a hard time enabling the wakeup from the cabled keyboard but ignoring the wireless mouse dongle on the same bus.
Though maybe:
https://forums.opensuse.org/t/logitech- … y/104001/2
https://archlinux.org/packages/community/any/solaar/

You mean when I get the wired keyboard I can run the xhci command to enable only waking it up from the keyboard?

If I connect the keyboard through USB-c that should automatically put it on a separate bus, shouldn't it?

Last edited by znerk (2022-12-29 14:35:31)

seth · 2022-12-29 14:43:56

You mean when I get the wired keyboard I can run the xhci command to enable only waking it up from the keyboard?

No. toggling xhci will disable the only obvious USB ACPI entry.

If I connect the keyboard through USB-c that should automatically put it on a separate bus, shouldn't it?

Not necessarily, please post the output of "lspci", but in general "different jack and form factor" doesn't mean it's a different bus or that the ACPI differentiates them.

znerk · 2022-12-29 14:44:44

seth wrote:

You mean when I get the wired keyboard I can run the xhci command to enable only waking it up from the keyboard?
No. toggling xhci will disable the only obvious USB ACPI entry.
If I connect the keyboard through USB-c that should automatically put it on a separate bus, shouldn't it?
Not necessarily, please post the output of "lspci", but in general "different jack and form factor" doesn't mean it's a different bus or that the ACPI differentiates them.

lspci output·

00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 01)
00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 01)
00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #0 (rev 01)
00:07.1 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #1 (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01)
00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller (rev 01)
00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0 (rev 01)
00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller
00:12.0 Serial controller: Intel Corporation Tiger Lake-LP Integrated Sensor Hub (rev 20)
00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)
00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)
00:15.0 Serial bus controller: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 (rev 20)
00:16.0 Communication controller: Intel Corporation Tiger Lake-LP Management Engine Interface (rev 20)
00:1d.0 PCI bridge: Intel Corporation Tiger Lake-LP PCI Express Root Port #9 (rev 20)
00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)
00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
00:1f.5 Serial bus controller: Intel Corporation Tiger Lake-LP SPI Controller (rev 20)
55:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller BG4

No. toggling xhci will disable the only obvious USB ACPI entry.

Sorry, I am not sure I comprehend this?

Last edited by znerk (2022-12-29 14:45:59)

seth · 2022-12-29 14:48:25

00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller (rev 01)
00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0 (rev 01)
00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)

XHCI      S3    *enabled   pci:0000:00:14.0
TXHC      S4    *enabled   pci:0000:00:0d.0
TDM0      S4    *enabled   pci:0000:00:0d.2

You can try to disable each of them and check the impact on your attached devices capacity to wake the system.
However maybe also check the SuSE thread and solaar.

znerk · 2022-12-29 14:49:07

seth wrote:

00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller (rev 01)
00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0 (rev 01)
00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)

XHCI      S3    *enabled   pci:0000:00:14.0
TXHC      S4    *enabled   pci:0000:00:0d.0
TDM0      S4    *enabled   pci:0000:00:0d.2

You can try to disable each of them and check the impact on your attached devices capacity to wake the system.
However maybe also check the SuSE thread and solaar.

Will do. Will wait until I have the cabled keyboard though I guess.

seth · 2022-12-29 15:27:47

If you have a usb key, pulling and plugging that into the target usb slot should™ do.

Arch Linux

#1 2022-12-29 13:21:08

Laptop wakes up immidtiately when suspending to ram when monitor con.

#2 2022-12-29 13:36:58

Re: Laptop wakes up immidtiately when suspending to ram when monitor con.

#3 2022-12-29 13:45:21

Re: Laptop wakes up immidtiately when suspending to ram when monitor con.

#4 2022-12-29 14:05:17

Re: Laptop wakes up immidtiately when suspending to ram when monitor con.

#5 2022-12-29 14:31:04

Re: Laptop wakes up immidtiately when suspending to ram when monitor con.

#6 2022-12-29 14:32:36

Re: Laptop wakes up immidtiately when suspending to ram when monitor con.

#7 2022-12-29 14:43:56

Re: Laptop wakes up immidtiately when suspending to ram when monitor con.

#8 2022-12-29 14:44:44

Re: Laptop wakes up immidtiately when suspending to ram when monitor con.

#9 2022-12-29 14:48:25

Re: Laptop wakes up immidtiately when suspending to ram when monitor con.

#10 2022-12-29 14:49:07

Re: Laptop wakes up immidtiately when suspending to ram when monitor con.

#11 2022-12-29 15:27:47

Re: Laptop wakes up immidtiately when suspending to ram when monitor con.

Board footer