Michael Lynch

Logs are available via ```bash sudo journalctl -u tinypilot ```

@WarheadsSE - Did you have to change the HID initialization part? I bought the same KVM, and it only works if I change the `init-usb-gadget` script to [this version](https://raw.githubusercontent.com/mtlynch/ansible-role-tinypilot/dca65cf58e48c1ab399825aba783116e5e09b2dd/files/init-usb-gadget) that's...

I've added a page to the wiki to track compatible/incompatible KVMs: https://github.com/mtlynch/tinypilot/wiki/KVM-compatibility

@glendady - It's unfortunately unlikely to work with that KVM switch. I added more detail in #697.

The MacroSilicon dongles capture up to 1080p. 640x480 is super small. Does your target system allow you to adjust the resolution up any more or does it only show 640x480p...

Thanks for filing this! I thought the current behavior was to pause video capture when no clients are connected, but I just tested it and was able to verify that...

>First question: (cc @jdeanwallace, @mtlynch) is anyone still using these remote scripts? No, I never ended up using these. I don't think I move code to devices enough to have...

Which port of the CKLau KVM are you inserting the TinyPilot's USB into? The USB 2.0 port or one of the keyboard/mouse ports? If it's helpful, I wrote this quick...

We recently discovered that the HID report length for the mouse was incorrect: https://github.com/mtlynch/ansible-role-tinypilot/pull/134 Is that potentially related?

Thanks for sharing these findings, @WarheadsSE. This is very helpful. Just to make sure I understand: * TinyPilot keyboard and mouse works when you connect directly to the target system....