DKS202-M24 wakes Mac displays with keyboard and receivers unplugged

Jeff Steinbok

30. Oktober 2026 07:22

My DKS202-M24 appears to generate USB HID activity that wakes my Mac’s displays, even with the physical keyboard and wireless keyboard/mouse receivers unplugged.

Setup:

• M4 MacBook Air running macOS
• Dell SD25TB4 Thunderbolt dock
• TESmart DKS202-M24 connected through the dock

I checked the macOS kernel logs. During the latest occurrence, the Mac woke in the background for network activity, then the KVM’s keyboard HID interface requested user activity and turned the displays on:

2026-10-29 22:00:40.456 PMRD: requestUserActive from AppleUserUSBHostHIDDevice (0x100135b4f) for kIOHIDSystemActivityTickle NX_HARDWARE_TICKLE

That registry ID maps to the DKS202-M24 keyboard interface, USB VID/PID 1a86:e010.

Disconnecting the KVM’s USB uplink stops the unwanted screen wakes. Disconnecting only the keyboard and wireless receivers does not.

Is this a known macOS compatibility issue? Is there firmware or a setting that prevents the KVM’s keyboard interface from generating activity during resume? Can that interface be disabled while retaining ordinary USB peripheral switching?

Please let me know what hardware revision or firmware information you need and how to retrieve it.

0

• Offizieller Kommentar

  

  TESmart.01

  30. Oktober 2026 08:47

  Hi Jeff,

  Thanks for reporting this issue and for sharing the details.

  Our engineering team has been investigating this behavior and has been able to reproduce a similar issue during internal testing.

  Based on our initial findings, switching between computers may cause USB devices or hubs to be re-detected, which can potentially trigger a sleeping Mac to wake up, even when the keyboard and wireless receivers are disconnected.

  We've also observed similar behavior in other test configurations, so we're still investigating whether this is related to USB device re-enumeration, macOS wake behavior, or the KVM switching process.

  We don't have a confirmed fix at this point, but we've documented the issue and will share any verified findings or workarounds as they become available.

  Thanks again for bringing this to our attention!

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.