A long-term KVM user encountered an issue after replacing an older device and upgrading one of the connected hosts to the latest macOS:
-
Video output worked normally at 4K 60Hz
-
Keyboard and mouse were never recognized by the system
-
Meanwhile, multiple Linux hosts connected to the same KVM operated stably, and hotkey switching worked flawlessly
Identifying the Key Difference
This discrepancy became the starting point for troubleshooting.
Through multiple rounds of communication, we systematically confirmed:
-
Connection methods
-
Docking station models
-
Keyboard and mouse devices
We ruled out cable and port issues, narrowing the problem from a broad “USB path” concern to a compatibility issue between the KVM keyboard/mouse ports and the new macOS version.
Internal testing had previously optimized this scenario via firmware, meaning the issue could be resolved once the upgrade was performed correctly.
New Challenges During the Upgrade
However, practical execution revealed additional hurdles:
-
The upgrade tool only supported Windows
-
The user only had macOS and Linux at their disposal
-
Even after borrowing a Windows laptop, the first upgrade attempt failed
The user carefully documented every action, including jumpers, connection methods, power status, and tool feedback. This information highlighted a gap in the upgrade SOP—critical steps were not clearly described.
Correcting the Procedure
By reconstructing the proper sequence, we confirmed two often-overlooked steps:
-
The jumper must remain in place while the USB-A data cable is connected
-
The firmware file provided in the email must be manually loaded, not just executing the upgrade tool
With these clarified steps, the user successfully completed the upgrade, and keyboard and mouse functionality under macOS was restored.
Broader Improvements Triggered by This Feedback
This single issue prompted multiple enhancements:
-
Product: Reinforced that new-system compatibility issues can be reliably addressed through firmware updates
-
Tools: Highlighted that Windows-only upgrade tools are inconvenient for multi-platform users, prompting development toward cross-platform support
-
Documentation & Service: Based on the user’s detailed operational feedback, upgrade instructions were updated to clearly describe critical steps, reducing the risk of user error in future
Positive User Feedback
After the issue was fully resolved, the user wrote:
“I just wanted to follow up and say how professional and helpful this interaction has been — I wish all customer support were as good as this :-)”
This case demonstrates that a problem arising from real-world usage can not only resolve an individual user’s pain points but also strengthen the overall product and support ecosystem.
