# Help with KVM keyboard port issue?

**URL:** <https://community.keyboard.io/t/help-with-kvm-keyboard-port-issue/3290>\
**Category:** Help and Getting Started\
**Created:** [October 23, 2019, 9:32am UTC](https://community.keyboard.io/t/help-with-kvm-keyboard-port-issue/3290 "2019-10-23T09:32:33Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\
**Post date:** [December 4, 2019, 2:19am UTC](https://community.keyboard.io/t/help-with-kvm-keyboard-port-issue/3290/7 "2019-12-04T02:19:24Z")

</div>

How exactly did you try to hack the library?

During my tests, the following two lines _at the top_ of `setup()` in my own sketch made the keyboard come up as 6KRO by default:

```auto
BootKeyboard.default_protocol = HID_BOOT_PROTOCOL;
BootKeyboard.setProtocol(HID_BOOT_PROTOCOL);

```

Mind you, I do not have a KVM switch to test if this works, the best I can do at the moment is to test if this puts the keyboard into boot mode by default, which, for me, it does.

This will still present two HID descriptors, one for a 6KRO and one for an NKRO keyboard, but will default to the former. The KVM switch might be confused by this, so in this case, the best course of action would be to completely remove the NKRO parts. That is currently not easily possible, but you can hack up `Kaleidoscope-HIDAdaptor-KeyboardioHID` and remove or comment out all references to `Keyboard`.

---

_[View the full topic](https://community.keyboard.io/t/help-with-kvm-keyboard-port-issue/3290)._