←back to thread

My sixth year as a bootstrapped founder

(mtlynch.io)
1071 points mtlynch | 2 comments | 16 Feb 24 15:07 UTC | HN request time: 0.542s | source
Show context
JonChesterfield ◴[16 Feb 24 18:43 UTC] No.39401208[source]▶
Their tinypilot kvm works. It's in the category of boring infrastructure - I leave it plugged into whatever machine is currently in need of attention and `https://tinypilot/` connects to it. Little box hanging off the PoE switch, much less bother than plugging a keyboard and monitor in. Especially so when I'm away from the office.

Recommended. Saved me a lot of hassle. Thanks for the product!

I'd like to be able to power cycle the attached machine but that seems inherently messy to implement.

replies(2): >>39401343 #>>39401735 #
1. mtlynch ◴[16 Feb 24 19:22 UTC] No.39401735[source]▶
Thanks for the kind words!

Yeah, power cycling is one of our top requests and a feature I'd like to have personally.

If we just plugged into the ATX pins on the motherboard, that would be technically pretty straightforward, but it increases the work and expertise that end-users have to have. I've looked into something like a smart plug, but then users need to configure their BIOS to always power on when power is available.

Definitely on my list of considerations for Voyager 3.

replies(1): >>39402349 #
2. JonChesterfield ◴[16 Feb 24 20:13 UTC] No.39402349[source]▶
The two ATX pins you short to turn the box on connected to the general purpose IO on the pi is probably the obvious play. The pikvm people suggest running all the ATX pins over another ethernet connection which is probably as neat as it'll get, though I'd inevitably connect the ATX-over-RJ45 thing to the switch PoE at some point and that's probably bad with all 8 wires connected.

Plus you'd want a ATX header to RJ45-or-whatever port per machine. Workable but not very elegant.