I lost the ability to use my Steetek KVM switch 8 port with keyboard or mouse emulation after upgrading my GL-RM1 Comet to firmware 1.10.1, only downgrading back to 1.9.2 fixed the issue. I spent time troubleshooting the issue with Google Gemini Flash Extended, which suggested a possible reason for the issue and a potential solution so I can go back to using the newest firmware. It wrote the message below detailing its findings:
Summary of Issue: After upgrading to 1.10.1, the Comet's emulated keyboard and mouse stop working when connected to hardware KVM switches that use integrated USB microcontrollers (specifically switches built on the ASIX AX68002 SoC).
Troubleshooting & Verification:
-
Direct Host Connection: The Comet works normally when connected directly to a PC/Mac USB port.
-
Through KVM Switch: The KVM controller drops enumeration completely; no keyboard or mouse packets reach the downstream host.
-
Custom Device Spoofing: Changing the Vendor ID, Product ID, and device strings in the new "Custom Device" modal does not resolve the issue, confirming this is a low-level descriptor/endpoint conflict rather than a VID/PID whitelist issue.
-
Firmware Rollback: Rolling back to firmware 1.10.0 / 1.9.2 immediately restores full keyboard and mouse functionality through the KVM switch.
Root Cause: The updated composite gadget configuration in 1.10.1 bundles endpoints and descriptors in a way that strict, hardware-level KVM host parsers reject. The embedded MCU expects standard USB Boot-Protocol descriptors (Subclass 1, 6KRO) and fails to enumerate the new composite tree.
Requested Fix: Please add a "Legacy / KVM Compatibility Mode" toggle in the Web UI under the USB Device Manager. When enabled, this should force the USB gadget stack to output a strict, standard Boot-Protocol keyboard/mouse descriptor (Subclass 1, 8-byte 6KRO reports) and strip auxiliary endpoints (virtual media, audio/mic) to ensure compatibility with hardware KVM microcontrollers.