Windows 10 issues during S3 sleep moments Strange behaviors while waking up from S3 sleep
Windows 10 issues during S3 sleep moments Strange behaviors while waking up from S3 sleep
Hi everyone, I recently installed a Ryzen 7000 system and noticed something curious about waking the machine from sleep. After reviewing powercfg, I saw that my motherboard only supports S3 sleep and Hibernate. When I try to wake it using my GMMK Pro keyboard, it doesn’t work, but my Logitech MX 518 mouse does. I remember my old board had PS/2 ports and thought sleep turned off USB devices; now I suspect the issue might be with my current keyboard. Windows labels the device as "USB/PS/2 Mouse" when connected via USB, yet Devices and Printers say it’s working over USB. Could there be a problem with the GMMK Pro? I’d like to run a test to see if the keyboard is disabled in sleep mode. Otherwise, I’m not sure and don’t mind losing my mouse just yet.
the logitech MX518 works with a basic mouse hardware while its unique capabilities are handled by a dedicated device in Windows. your keyboard might not appear as a recognized device after the OS loads, possibly due to BIOS configurations or issues with S3 sleep functionality.
Sleep hasn't always worked as expected for me... at all. The computer sometimes has certain ports that stay active, and you need to know which ones—like the internal keyboard connector on laptops, which is still USB protocol in many cases. In rare situations, it's BIOS settings controlling wake from sleep via USB only through the mouse or keyboard (though usually everything is set under one option). It might also be due to the GMMK keyboard using a special driver that conflicts with Windows sleep states. The original mouse has remained unchanged for two decades. Occasionally, it's just Windows being very slow at stopping background services that don't use much activity, even when not in sleep mode.
I figured that too after checking some sources. It seems PS/2 over USB isn't supported, meaning it's a regular USB mouse in the device tree. Probably depends on which USB controllers are active during sleep and they're linked to separate ones. S3 sleep is definitely faulty, so the issue might just be with that specific sleep mode.
It seems to be a minor observation, but is it accurate? I thought most laptop manufacturers still rely on PS/2, I2C, or their own unique connections for keyboards and mice. Having worked with Hackintosh, I recall VoodoPS2 exists as a kext since many laptops use PS/2 for trackpads. I’m sure lots of machines still depend on USB, though. I just verified with my old Intel Mac that the keyboard and mouse are indeed part of the USB tree, linked through the T2 chip. It appears Apple may have shifted away from PS/2, which could be a notable change. These three possibilities might be behind the issue. I confirmed everything is connected the same way under the main controller, so it likely points to Windows or the GMMK driver. All ports under the main controller stay active during sleep, which could explain the problem. This might be another reason to consider replacing my MX 518.
the controller decides which ports to power down separately. it adjusts wake-up behavior based on each device. my two front panel USB3 ports have one with a bluetooth dongle inside, keeping it active, while the other turns off completely—no matter what you connect. except when you move the dongle into the first port...