Arch Linux

V10lator

Member

Registered: Yesterday

Posts: 9

Wake from USB not working

Sitting on this since days. There is no BIOS option (would attach the ifrextractor result as prove that there's not even a hidden option but can't find a upload function). All my tries to get it to work end in the PC either cutting off USB power or insta-waking (can't tell if there's USB power cause too fast). Tried a lot of things told by AIs but that's just moving in circles, so how to even debug this correctly?

CPU is Ryzen 7 7500F. Chipset is B850. Doesn't matter if the device which should wake (Steam Controller) is connected to a USB port of the chipset or CPU.

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 778

Re: Wake from USB not working

Wake from suspend-to-RAM (S3) or from suspend-to-disk (S4)?

or insta-waking

Can you please show journal entries for such suspend/wake-up attempt?

Tried a lot of things

What things? Let's rule out suggestions you've already tried and they didn't work. 

how to even debug this correctly?

Can you identify your USB device in /sys/bus/usb/devices/ and check corresponding power/wakeup entry?

Doesn't matter if the device which should wake (Steam Controller) is connected to a USB port of the chipset or CPU.

Is "wake from USB" not working with this particular device or with any USB HID device, mouse or keyboard?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,665

Re: Wake from USB not working

Also

cat /proc/acpi/wakeup
lspci -nn
lsusb -tv

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

V10lator

Member

Registered: Yesterday

Posts: 9

Re: Wake from USB not working

Wake from suspend-to-RAM (S3) or from suspend-to-disk (S4)?

Both but I'm trying to get S3 to work.

Can you please show journal entries for such suspend/wake-up attempt?

IIRC there where none. Also IIRC this was when enabling power/wakeup for the USB host even with no device connected as it created spurious wake events (AI asked me to delete the wake event with some pcie register settings, check it was removed, wait 30 seconds and check again, then the wake event was there again for no reason even with no USB devices connected at all). We can check if we recreate this in debugging later.

What things? Let's rule out suggestions you've already tried and they didn't work.

That's the thing with AI: A lot. Much similiar things with equal outcome. Best to start from scratch with human driven suggestions I guess.

Can you identify your USB device in /sys/bus/usb/devices/ and check corresponding power/wakeup entry?

I'm not sure how to do this correctly. Is this of any help?

(root@soyo ~)# cat /sys/bus/usb/devices/*/power/wakeup
enabled
enabled
disabled
disabled
disabled
disabled
disabled
disabled
disabled
disabled
(root@soyo ~)# cat /sys/bus/usb/devices/*/product
Steam Controller Puck
LED Dongle
IBM Model M to USB Adapter
Bluetooth Radio
xHCI Host Controller
xHCI Host Controller
xHCI Host Controller
xHCI Host Controller
xHCI Host Controller
xHCI Host Controller
xHCI Host Controller

Is "wake from USB" not working with this particular device or with any USB HID device, mouse or keyboard?

Any as there doesn't seem to be USB power while in standby.

cat /proc/acpi/wakeup

Device  S-state   Status   Sysfs node
GPP3      S4    *disabled
GPP4      S4    *disabled
GPP5      S4    *disabled
GPP6      S4    *disabled
GP17      S4    *enabled   pci:0000:00:08.1
XHC0      S4    *enabled   pci:0000:0b:00.3
XHC1      S4    *enabled   pci:0000:0b:00.4
SIO1      S3    *disabled
XHC2      S4    *enabled   pci:0000:0c:00.0
GPP0      S4    *enabled   pci:0000:00:01.1
SWUS      S4    *enabled   pci:0000:01:00.0
SWDS      S4    *enabled   pci:0000:02:00.0
GPP1      S4    *disabled
GPP2      S4    *disabled
GPP7      S4    *enabled   pci:0000:00:02.1
UP00      S4    *enabled   pci:0000:04:00.0
DP00      S4    *disabled
NV00      S4    *disabled
DP08      S4    *enabled   pci:0000:05:01.0
EP00      S4    *disabled  pci:0000:06:00.0
DP10      S4    *enabled   pci:0000:05:02.0
WN00      S4    *disabled  pci:0000:07:00.0
DP18      S4    *disabled
LN00      S4    *disabled
DP20      S4    *disabled
NV00      S4    *disabled
DP28      S4    *disabled
EP00      S4    *disabled
DP30      S4    *disabled
EP00      S4    *disabled
DP38      S4    *disabled
EP00      S4    *disabled
DP40      S4    *disabled
EP00      S4    *disabled
DP48      S4    *disabled
EP00      S4    *disabled
DP50      S4    *disabled
EP00      S4    *disabled
DP58      S4    *disabled
EP00      S4    *disabled
DP60      S4    *enabled   pci:0000:05:0c.0
XH00      S4    *enabled   pci:0000:08:00.0
DP68      S4    *enabled   pci:0000:05:0d.0
SA00      S4    *disabled  pci:0000:09:00.0
GPP8      S4    *enabled   pci:0000:00:02.2

lspci -nn

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Root Complex [1022:14d8]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge [1022:14da]
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge [1022:14db]
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge [1022:14da]
00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge [1022:14db]
00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge [1022:14db]
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge [1022:14da]
00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge [1022:14da]
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge [1022:14da]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] [1022:14dd]
00:08.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] [1022:14dd]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 71)
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 0 [1022:14e0]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 1 [1022:14e1]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 2 [1022:14e2]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 3 [1022:14e3]
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 4 [1022:14e4]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 5 [1022:14e5]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 6 [1022:14e6]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 7 [1022:14e7]
01:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch [1002:1478] (rev 25)
02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch [1002:1479] (rev 25)
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 44 [Radeon RX 9060 XT] [1002:7590] (rev c0)
03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 48 HDMI/DP Audio Controller [1002:ab40]
04:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Upstream Port [1022:43f4] (rev 01)
05:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port [1022:43f5] (rev 01)
05:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port [1022:43f5] (rev 01)
05:0c.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port [1022:43f5] (rev 01)
05:0d.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port [1022:43f5] (rev 01)
06:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller [10ec:b852]
07:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
08:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 800 Series Chipset USB 3.x XHCI Controller [1022:43fc] (rev 01)
09:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset SATA Controller [1022:43f6] (rev 01)
0a:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology T500 NVMe PCIe SSD [c0a9:5415] (rev 01)
0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge PCIe Dummy Function [1022:14de]
0b:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 19h PSP/CCP [1022:1649]
0b:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 3.1 xHCI [1022:15b6]
0b:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 3.1 xHCI [1022:15b7]
0b:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Audio Coprocessor [1022:15e2] (rev 62)
0b:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Ryzen HD Audio Controller [1022:15e3]
0c:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 2.0 xHCI [1022:15b8]

lsusb -tv

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 001: Dev 002, If 0, Class=Communications, Driver=cdc_acm, 12M
        ID 28de:1304 Valve Software 
    |__ Port 001: Dev 002, If 1, Class=CDC Data, Driver=cdc_acm, 12M
        ID 28de:1304 Valve Software 
    |__ Port 001: Dev 002, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        ID 28de:1304 Valve Software 
    |__ Port 001: Dev 002, If 3, Class=Human Interface Device, Driver=usbhid, 12M
        ID 28de:1304 Valve Software 
    |__ Port 001: Dev 002, If 4, Class=Human Interface Device, Driver=usbhid, 12M
        ID 28de:1304 Valve Software 
    |__ Port 001: Dev 002, If 5, Class=Human Interface Device, Driver=usbhid, 12M
        ID 28de:1304 Valve Software 
    |__ Port 001: Dev 002, If 6, Class=Human Interface Device, Driver=usbhid, 12M
        ID 28de:1304 Valve Software 
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 0416:0125 Winbond Electronics Corp. 
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci-pci-prom21/12p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 009: Dev 002, If 0, Class=Wireless, Driver=btusb, 12M
        ID 0bda:b85b Realtek Semiconductor Corp. 
    |__ Port 009: Dev 002, If 1, Class=Wireless, Driver=btusb, 12M
        ID 0bda:b85b Realtek Semiconductor Corp. 
    |__ Port 012: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 1337:1337  
    |__ Port 012: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        ID 1337:1337  
/:  Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci-pci-prom21/6p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,665

Re: Wake from USB not working

XHC0      S4    *enabled   pci:0000:0b:00.3
XHC1      S4    *enabled   pci:0000:0b:00.4
XHC2      S4    *enabled   pci:0000:0c:00.0
XH00      S4    *enabled   pci:0000:08:00.0

All enabled for S4 and below - do you have a $5 office supply keyboard?

IIRC there where none.

That's not a thing, sleep cycles get logged.
Please post your complete system journal for the boot:

sudo journalctl -b | nc termbin.com 9999

after some spurious wakeup.

even with no device connected as it created spurious wake events

What is this:

ID 0416:0125 Winbond Electronics Corp. 

radio (wifi/bluetooth)?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

V10lator

Member

Registered: Yesterday

Posts: 9

Re: Wake from USB not working

do you have a $5 office supply keyboard?

No. There are various reports of people waking their PCs with Steam Controllers and it's even a feature of the Steam Machine through.

Please post your complete system journal for the boot:

sudo journalctl -b | nc termbin.com 9999

after some spurious wakeup.

For this we have to get spurious wakeups first. We're still at "PC sleeps but can't wake cause of no VCC on USB" through.

What is this:

ID 0416:0125 Winbond Electronics Corp. 

radio (wifi/bluetooth)?

( https://gitlab.com/CalcProgrammer1/Open … AzfQ%3D%3D )

Last edited by V10lator (Yesterday 20:58:25)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,665

Re: Wake from USB not working

There are various reports of people…

I don't care.
The point is to isolate the problem - is it w/ the usb controller or the steam device.
Can you get a regular keyboard? Some chips won't even respond to random input (but the space bar)

For this we have to get spurious wakeups first.

Idk who "we" is but

or insta-waking

Did you get "insta-waking" w/o that dongle (and the steam controller) as well?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

V10lator

Member

Registered: Yesterday

Posts: 9

Re: Wake from USB not working

I don't care.

So you probably also don't care about the udev rules beeing copied from SteamOS which advertises wake on USB from steam controllers? Also waking my steam deck works fine with the very same controller but yea, you don't care.

Idk who "we" is

You, me and whoever else participates in this thread?

Did you get "insta-waking" w/o that dongle (and the steam controller) as well?

Yes. as already told. Anyway, these insta-wakes might have been caused by the AI doing stupid things which is why I also said it would probably be best to start debugging from scratch. This brings us to the situation that there are no insta-wakes in our current debugging session. We're at the step of wake from USB not working at all, PC sleeping until power button pressed and no USB VCC to the controllers puck.

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 778

Re: Wake from USB not working

]Both but I'm trying to get S3 to work.

I assume it's real S3, not S2idle. For sanity, let's check

$ cat /sys/power/mem_sleep

--

I'm not sure how to do this correctly. Is this of any help?

Not really. It's unclear which entry is for which device.

$ for d in /sys/bus/usb/devices/*/product; do echo $(<$d): $(<$(dirname $d)/power/wakeup); done

--

Any as there doesn't seem to be USB power while in standby.

Did you check Vbus on USB port pins?

What motherboard is this? Some boards can supply power in sleep modes only to specific USB ports, not to any.
Do you have a sort of "ErP Ready" or "Power Share" option in BIOS? Actually a link to User's Manual for motherboard would be helpful.

V10lator

Member

Registered: Yesterday

Posts: 9

Re: Wake from USB not working

I assume it's real S3, not S2idle. For sanity, let's check

$ cat /sys/power/mem_sleep

$ cat /sys/power/mem_sleep 
s2idle [deep]

$ for d in /sys/bus/usb/devices/*/product; do echo $(<$d): $(<$(dirname $d)/power/wakeup); done

Syntax error at do. Removed the ";" chars, now a new error:
```
ash: $d: Mehrdeutige Umlenkung
dirname: fehlender Operand
„dirname --help“ liefert weitere Informationen.
bash: /power/wakeup: Datei oder Verzeichnis nicht gefunden
bash: $: Kommando nicht gefunden

Did you check Vbus on USB port pins?

I think I did this at some point but can't find the cable needed to recreate that experiment right now, so better take it as unconfirmed.
A hint of no VCC is the controller not shutting off but completely loosing connection to the puck instead and also it stopping to charge. A 5V FAN connected to another USB ports VCC stops spinning, too.

What motherboard is this? Some boards can supply power in sleep modes only to specific USB ports, not to any.

Soyo B850 ITX

Do you have a sort of "ErP Ready" or "Power Share" option in BIOS?

No. All BIOS options (even hidden ones, from ifrextractor) : https://pastebin.com/HzXQCX6x

Actually a link to User's Manual for motherboard would be helpful.

https://www.soyocn.net/2025/1106/2923.html - You need a baidu account to download it through, which I don't have.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,665

Re: Wake from USB not working

Syntax error at do.

What syntax error? This is a valid bash script, removing the semicolons will certainly not help.

So you probably also don't care about the udev rules beeing copied from SteamOS

No. I want to check whether you can wake the system via USB when you attach a bog-standard keyboard.

The point is to isolate the problem - is it w/ the usb controller or the steam device.

If you want to fix a problem you first need to isolate the cause.

You, me and whoever else participates in this thread?

I don't get spurious wakeups at all… but

This brings us to the situation that there are no insta-wakes in our current debugging session

You can access older journals,

sudo journalctl -b -δ

increasing δ (0 being the current boot) will get you older journals.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

V10lator

Member

Registered: Yesterday

Posts: 9

Re: Wake from USB not working

What syntax error? This is a valid bash script, removing the semicolons will certainly not help.

managed to get it to work - mostly:

Steam Controller Puck: enabled
bash: /sys/bus/usb/devices/5-1/power/wakeup: Datei oder Verzeichnis nicht gefunden
LED Dongle:
IBM Model M to USB Adapter: enabled
Bluetooth Radio: disabled
xHCI Host Controller: disabled
xHCI Host Controller: disabled
xHCI Host Controller: disabled
xHCI Host Controller: disabled
xHCI Host Controller: disabled
xHCI Host Controller: disabled
xHCI Host Controller: disabled

If you want to fix a problem you first need to isolate the cause.

How does it help finding the cause if you ignore that the controller can wake my steam deck and my laptop just fine? Also you ignore that there are clear hints of no VCC to the puck while in standby, like the controller loosing connection (the puck should shut it down instead) and the puck no longer being able to charge the controller.
If you choose to ignore this it's up to you to prove that it's a different cause, no?

//EDIT:

I don't get spurious wakeups at all… but

Again: We = The people participating in this debugging session. If you don't want to be part of us that's fine, just leave the thread then.

//EDIT²: Measured the VCC line of the RPI Pico (IBM Model M to USB Adapter) with a multimeter while in standby and yea: 0 V.

Last edited by V10lator (Today 09:46:06)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,665

Re: Wake from USB not working

How does it help finding the cause if you ignore that the controller can wake my steam deck and my laptop just fine?

Because *we* don't know whether the behavior of *your* system is caused by something  that's specific to the controller or the board?
Wtf is the problem of just *testing* how a keyboard behaves?

Measured the VCC line of the RPI Pico (IBM Model M to USB Adapter) with a multimeter while in standby

The USB port or the RJ45 behind the adapter?

Speaking of ports: "not all are created equally" - have you check whether all of them fail?

--
Off topic and fwiw, *I* simply don't like people using a beyond obvious arrogant self-referential pluralis majestatis.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

V10lator

Member

Registered: Yesterday

Posts: 9

Re: Wake from USB not working

Wtf is the problem of just *testing* how a keyboard behaves?

As long as you don't care that I told you I don't have any? None. I'll just ignore you from now on, just as you do through.

The USB port or the RJ45 behind the adapter?

The USB ofc.

Off topic and fwiw, *I* simply don't like people using a beyond obvious arrogant self-referential pluralis majestatis.

Okay, from now on I'll say "everyone in this thread except seth", hope that's better for your self-health.

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 778

Re: Wake from USB not working

Steam Controller Puck: enabled

Ok, good. Sorry, forgot to mention that the command should be executed in bash.

it stopping to charge. A 5V FAN connected to another USB ports VCC stops spinning, too.

Charge? Fan? USB device should not draw more than 2.5 mA in sleep mode.
To draw more, both motherboard and device have to support one of USB charging protocols. Usually such feature is for laptops, so I doubt your motherboard implements it. 

How does it help finding the cause if you ignore that the controller can wake my steam deck and my laptop just fine?

Itfp we have to figure out whether your motherboard can provide USB power in S3 and wake up with USB HID at all.
If it can, then we can investigate why it won't with Steam Controller specifically.
It it can not, then only thing you can try is to switch from [deep] to [s2idle] in /sys/power/mem_sleep. In this mode PC will consume a number of times more power than in real S3.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,665

Re: Wake from USB not working

Can you get a regular keyboard?

Like borrowing one or getting one from amazon?
How did you even install archlinux on that system w/o a keyboard?

Either way and as @dimich also pointed out:
If the the puck needs 5V to communicate w/ the controller (and is eg. able to charge it on your laptop), that's the most likely problem.
Some boards provide a setting to allow a dedicated port (eg. lenovo calls it "always on" or sth. like that) to feed 5V (to charge your phone or other devices) during sleep (and/or only on AC) but this is absolutely not standard.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

V10lator

Member

Registered: Yesterday

Posts: 9

Re: Wake from USB not working

Some progress: I injected 5 V into the pucks USB VCC line and with this we got a insta-wake. This gives us two things:
1) The AI must somehow have activated VCC on USB in the past. Would be good if people finally realize that VCC is preventing from waking and tell me how to enable it correctly without that BIOS option...
2) People in this thread except seth have a log of a insta-wake event:

Sep 03 20:46:24 soyo systemd-sleep[6753]: Successfully froze unit 'user.slice'.
Sep 03 20:46:24 soyo systemd-sleep[6753]: Performing sleep operation 'suspend'...
Sep 03 20:46:24 soyo kernel: PM: suspend entry (deep)
Sep 03 20:46:24 soyo kernel: Filesystems sync: 0.007 seconds
Sep 03 20:46:30 soyo kernel: Freezing user space processes
Sep 03 20:46:30 soyo kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Sep 03 20:46:30 soyo kernel: OOM killer disabled.
Sep 03 20:46:30 soyo kernel: Freezing remaining freezable tasks
Sep 03 20:46:30 soyo kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Sep 03 20:46:30 soyo kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/ldac
Sep 03 20:46:30 soyo kernel: serial 00:00: disabled
Sep 03 20:46:30 soyo lact[976]: 2026-09-03T18:46:30.405361Z  INFO lact_daemon: got kernel drm subsystem event, queueing GPU reload
Sep 03 20:46:30 soyo lact[976]: 2026-09-03T18:46:30.405373Z  INFO lact_daemon: got kernel drm subsystem event, queueing GPU reload
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx_hd
Sep 03 20:46:30 soyo kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_hd
Sep 03 20:46:30 soyo kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx
Sep 03 20:46:30 soyo dbus-broker[495]: A security policy denied :1.4 to send method call /midi/profile:org.bluez.GattProfile1.Release to :1.34.
Sep 03 20:46:30 soyo kernel: ata2.00: Entering standby power mode
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: MODE1 reset
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aac
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: GPU mode1 reset
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aac
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: GPU smu mode1 reset
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink/opus_g
Sep 03 20:46:30 soyo kernel: ACPI: PM: Preparing to enter system sleep state S3
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_g
Sep 03 20:46:30 soyo kernel: ACPI: PM: Saving platform NVS memory
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbc
Sep 03 20:46:30 soyo kernel: Disabling non-boot CPUs ...
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbc
Sep 03 20:46:30 soyo kernel: smpboot: CPU 11 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Sep 03 20:46:30 soyo kernel: smpboot: CPU 10 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Sep 03 20:46:30 soyo kernel: smpboot: CPU 9 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Sep 03 20:46:30 soyo kernel: smpboot: CPU 8 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Sep 03 20:46:30 soyo kernel: smpboot: CPU 7 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream
Sep 03 20:46:30 soyo kernel: smpboot: CPU 6 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream_duplex
Sep 03 20:46:30 soyo kernel: smpboot: CPU 5 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink/opus_05
Sep 03 20:46:30 soyo kernel: smpboot: CPU 4 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05
Sep 03 20:46:30 soyo kernel: smpboot: CPU 3 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Sep 03 20:46:30 soyo kernel: smpboot: CPU 2 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Endpoint unregistered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Sep 03 20:46:30 soyo kernel: smpboot: CPU 1 is now offline
Sep 03 20:46:30 soyo bluetoothd[498]: Battery Provider Manager destroyed
Sep 03 20:46:30 soyo kernel: ACPI: PM: Low-level resume complete
Sep 03 20:46:30 soyo kernel: ACPI: PM: Restoring platform NVS memory
Sep 03 20:46:30 soyo kernel: LVT offset 0 assigned for vector 0x400
Sep 03 20:46:30 soyo kernel: Enabling non-boot CPUs ...
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Sep 03 20:46:30 soyo kernel: CPU1 is up
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Sep 03 20:46:30 soyo kernel: CPU2 is up
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Sep 03 20:46:30 soyo kernel: CPU3 is up
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Sep 03 20:46:30 soyo kernel: CPU4 is up
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Sep 03 20:46:30 soyo kernel: CPU5 is up
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Sep 03 20:46:30 soyo kernel: CPU6 is up
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Sep 03 20:46:30 soyo kernel: Spurious APIC interrupt (vector 0xFF) on CPU#7, should never happen.
Sep 03 20:46:30 soyo kernel: CPU7 is up
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Sep 03 20:46:30 soyo kernel: Spurious APIC interrupt (vector 0xFF) on CPU#8, should never happen.
Sep 03 20:46:30 soyo kernel: CPU8 is up
Sep 03 20:46:30 soyo systemd-sleep[6753]: System returned from sleep operation 'suspend'.
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Sep 03 20:46:30 soyo kernel: Spurious APIC interrupt (vector 0xFF) on CPU#9, should never happen.
Sep 03 20:46:30 soyo kernel: CPU9 is up
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Sep 03 20:46:30 soyo kernel: Spurious APIC interrupt (vector 0xFF) on CPU#10, should never happen.
Sep 03 20:46:30 soyo kernel: CPU10 is up
Sep 03 20:46:30 soyo kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Sep 03 20:46:30 soyo kernel: Spurious APIC interrupt (vector 0xFF) on CPU#11, should never happen.
Sep 03 20:46:30 soyo kernel: CPU11 is up
Sep 03 20:46:30 soyo kernel: ACPI: PM: Waking up from system sleep state S3
Sep 03 20:46:30 soyo kernel: xhci-pci-prom21 0000:08:00.0: xHC error in resume, USBSTS 0x401, Reinit
Sep 03 20:46:30 soyo kernel: usb usb6: root hub lost power or was reset
Sep 03 20:46:30 soyo kernel: usb usb7: root hub lost power or was reset
Sep 03 20:46:30 soyo kernel: serial 00:00: activated
Sep 03 20:46:30 soyo kernel: nvme nvme0: 12/0/0 default/read/poll queues
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: [drm] PCIE GART of 512M enabled (table at 0x00000083DAB00000).
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: PSP is resuming...
Sep 03 20:46:30 soyo kernel: usb 6-12: WARN: invalid context state for evaluate context command.
Sep 03 20:46:30 soyo kernel: usb 5-1: reset full-speed USB device number 2 using xhci_hcd
Sep 03 20:46:30 soyo kernel: usb 1-1.4: reset full-speed USB device number 11 using xhci_hcd
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: RAS: optional ras ta ucode is not available
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: RAP: optional rap ta ucode is not available
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: SECUREDISPLAY: optional securedisplay ta ucode is not available
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: SMU is resuming...
Sep 03 20:46:30 soyo kernel: ata4: SATA link down (SStatus 0 SControl 300)
Sep 03 20:46:30 soyo kernel: ata3: SATA link down (SStatus 0 SControl 300)
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: SMU is resumed successfully!
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: program CP_MES_CNTL : 0x4000000
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: program CP_MES_CNTL : 0xc000000
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: [drm] DMUB hardware initialized: version=0x0A000C00
Sep 03 20:46:30 soyo kernel: usb 6-12: reset full-speed USB device number 5 using xhci-pci-prom21
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: ring sdma0 uses VM inv eng 9 on hub 0
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: ring sdma1 uses VM inv eng 10 on hub 0
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Sep 03 20:46:30 soyo kernel: amdgpu 0000:03:00.0: ring jpeg_dec uses VM inv eng 1 on hub 8
Sep 03 20:46:30 soyo kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 03 20:46:30 soyo kernel: ata2.00: supports DRM functions and may not be fully accessible
Sep 03 20:46:30 soyo kernel: sd 1:0:0:0: [sdb] Starting disk
Sep 03 20:46:30 soyo kernel: ata2.00: supports DRM functions and may not be fully accessible
Sep 03 20:46:30 soyo kernel: ata2.00: configured for UDMA/133
Sep 03 20:46:30 soyo kernel: ahci 0000:09:00.0: port does not support device sleep
Sep 03 20:46:30 soyo kernel: ata2.00: Enabling discard_zeroes_data
Sep 03 20:46:30 soyo kernel: usb 6-9: WARN: invalid context state for evaluate context command.
Sep 03 20:46:30 soyo kernel: usb 6-9: reset full-speed USB device number 2 using xhci-pci-prom21
Sep 03 20:46:30 soyo systemd-sleep[6753]: Successfully thawed unit 'user.slice'.
Sep 03 20:46:30 soyo kernel: OOM killer enabled.
Sep 03 20:46:30 soyo kernel: Restarting tasks: Starting
Sep 03 20:46:30 soyo kernel: Restarting tasks: Done
Sep 03 20:46:30 soyo kernel: efivarfs: resyncing variable state
Sep 03 20:46:30 soyo kernel: efivarfs: finished resyncing variable state
Sep 03 20:46:30 soyo kernel: random: crng reseeded on system resumption
Sep 03 20:46:30 soyo kernel: PM: suspend exit
Sep 03 20:46:30 soyo kernel: Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
Sep 03 20:46:30 soyo kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Sep 03 20:46:30 soyo kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
Sep 03 20:46:30 soyo kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
Sep 03 20:46:30 soyo kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
Sep 03 20:46:30 soyo kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 62539
Sep 03 20:46:30 soyo systemd-logind[500]: Operation 'suspend' finished.

( https://termbin.com/fu2q0 )

//EDIT:

How did you even install archlinux on that system w/o a keyboard?

IBM Model M to USB Adapter

//EDIT²:

If the the puck needs 5V to communicate w/ the controller (and is eg. able to charge it on your laptop), that's the most likely problem.

Okay, so only USB devices who don't need 5V VCC are able to wake the PC? WTF are you even talking? Did you check what a steam controller and a puck is? Hint: Charging the controller is completely optional: https://store.steampowered.com/sale/steamcontroller

Last edited by V10lator (Today 19:11:52)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,665

Re: Wake from USB not working

Yeah, just saw that there's an actual keyboard behind that rj45 adapter (I had assumed this  was for an external ethernet dongle)

You power the puck up externally and it triggers the XHC* wakeup entry, so far so unsurprising.
Does it stay active when connected to the other hosts and those sleep?
Does the board feed full power to the ports during s2idle?
https://wiki.archlinux.org/title/Power_ … end_method

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

V10lator

Member

Registered: Yesterday

Posts: 9

Re: Wake from USB not working

You power the puck up externally and it triggers the XHC* wakeup entry, so far so unsurprising.

Shouldn't it only wake when I press the STEAM button on the controller?

Does it stay active when connected to the other hosts and those sleep?

On the other host the puck shuts the controller down when host goes to sleep. When you power the controller back on (by pressing the STEAM button) it wakes the PC.

Does the board feed full power to the ports during s2idle?

Yes and I'm able to wake with the controller correctly. s2idle is not really what I want to use through as CPU fan still spins, for example.

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 778

Re: Wake from USB not working

1) The AI must somehow have activated VCC on USB in the past.

Or self-powered USB device back-powers some part of motherboard's chipset via Vbus. This would be out of any spec.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,665

Re: Wake from USB not working

Depends on how the OP fed the voltage into the puck… there's probably no proper external power supply and just tapping in a wire there will get you funny results.
There're powered USB adapters (ie. you plug the adapter into the system and a power chord into a wall outlet) that **may** help you out here if that wasn't how you externally powered the puck itfp.

Also are you using S3 or s2idle on the other systems? What's the laptop specifically?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc