Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote power cycle JetKVM? #103

Open
nickwebcouk opened this issue Jan 27, 2025 · 7 comments
Open

Remote power cycle JetKVM? #103

nickwebcouk opened this issue Jan 27, 2025 · 7 comments

Comments

@nickwebcouk
Copy link

I've just had my JetKVM stop responding to mouse inputs while trying to debug a mouse offset (Which I've discovered has been raised as issue 21 - possible the same but I'm still checking). I can't seem to find anywhere to remotely power cycle the device. Can this option be enabled in software?

@Nevexo
Copy link
Contributor

Nevexo commented Jan 27, 2025

remotely power cycle the device

That's not possible at all without having control over the power supply, but if you just want to reboot it, you can do that with SSH.

There's some discussion around adding a reboot button, and it'll probably happen, but my argument against it is trying to solve the problems that are causing the need for people to reboot the device.

@sidick
Copy link

sidick commented Jan 27, 2025

remotely power cycle the device

That's not possible at all without having control over the power supply, but if you just want to reboot it, you can do that with SSH.

There's some discussion around adding a reboot button, and it'll probably happen, but my argument against it is trying to solve the problems that are causing the need for people to reboot the device.

Is there any capability of setting up a watchdog timer to auto reboot on hangs? Not sure if the hardware supports it.

@Nevexo
Copy link
Contributor

Nevexo commented Jan 27, 2025

Is there any capability of setting up a watchdog timer to auto reboot on hangs? Not sure if the hardware supports it.

There's a kernel-level watchdog enabled that is reset by jetkvm_app (https://github.com/jetkvm/kvm/blob/main/hw.go#L54)

But since it's not a hardware-level, if the whole thing hangs it won't help there, it might be possible to enable a hardware-level watchdog on the Rockchip, though?

@geerlingguy
Copy link

For my use case, I had a JetKVM I had turned on, then later I wanted to update the DHCP settings for it on my router and reboot it. I didn't have any way to reboot it (short of a firmware update... but it was already up to date!).

It would be nice to have a 'reboot' option somewhere in the settings for that.

@Nevexo
Copy link
Contributor

Nevexo commented Jan 30, 2025

Image

Added in https://github.com/Nevexo/jetkvm-kvm/releases/tag/next-7 - as noted in there, I haven't raised a PR for it as it's not very graceful, the Web UI just freezes until the device has rebooted. Before opening a PR I'll probably add a "reboot in progress" screen.

@skipfire
Copy link

skipfire commented Feb 1, 2025

@Nevexo that's fantastic, but don't let perfection get in the way of progress. If someone clicks the reboot button, they should expect it to stop responding for a moment, just as if they had the page open and pulled the power as we have to do without the button. Forcing us to pull the plug to reboot, especially for those of us with a mounted device, is probably more likely to cause physical damage on the device (or human damage as I cut my arm trying to get to the back of my mounted JetKVM) than the potential and self-resolving confusion of not having the reboot in progress message as the JetKVM does boot quickly and the web UI has recovered perfectly every time in my experience.

@PeterFalken
Copy link

I agree with @skipfire, adding a small notification stating that the device/UI will become unresponsive for a moment while it reboots should be enough (a modal confirmation would take care of this, from a UX perspective).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants