[rendaw]

I was looking into this and there were reports of e.g. connection delays making it impossible to access bios on a booting machine. This is a huge issue - rebooting and power management are big ip kvm use cases, and it isn't even touched on in the review.

I'm trying to make sense of this test. It seems like basically a listicle with "this is great" and a copy/paste of the datasheet specs. Most of the observations are things you'd spot instantly looking at it on amazon. The most critical comment is "it didn't work with ubuntu" (why, how, what went wrong). I was expecting a list of facets that were tested, with insight you can only get from having the hardware in front of you...

[geerlingguy]

If you only have 1s to hit Del for BIOS it can be a problem, especially if you're powering the IP KVM off of the computer being controlled.

But otherwise, I've tested BIOS access on every one of these and it works on the PCs I've tested. Mounting ISO's can be tricky sometimes but mostly "just works" now.

[rendaw]

Why didn't you include that stuff in your writeup? BIOS is only mentioned in the introduction, latency isn't mentioned at all...

Also did you test this stuff from within the lab, or remotely from somewhere else? I think e.g. JetKVM BIOS issues may be when accessed via Tailscale while on the road, or at a hotel, etc.

[yencabulator]

FWIW in the world of UEFI most firmware provides a way to boot into the firmware setup without needing to win that race. systemd-boot calls it "Reboot Into Firmware Interface", and you can do systemctl reboot --firmware-setup from a running linux.