starred/kvm

Fork 0

mirror of https://github.com/jetkvm/kvm.git synced 2026-03-02 22:58:00 -05:00

Keyboard not registered before OS boot #148

New issue

Open

opened 2026-02-20 08:20:45 -05:00 by deekerman · 13 comments

deekerman commented

2026-02-20 08:20:45 -05:00

Owner

Originally created by @whytf on GitHub (Mar 7, 2025).

Hello,

There have been some tries of getting this fixed https://github.com/Nevexo/jetkvm-kvm/releases/tag/usb-potential-fix-1 however for me it still shows usb state as "addressed", same when system is in grub menu and registers no input, only works after the OS boots up.

I am running app version 0.3.7 and system 0.2.3, i have also tried tagged release above however it doesn't work as well.

Host machine:

HP prodesk 600 g4
HP elitedesk 800 g2

I tried this on older asus system and keyboard input works in bios and grub, so this has to be HP specific

Originally created by @whytf on GitHub (Mar 7, 2025). Hello, There have been some tries of getting this fixed https://github.com/Nevexo/jetkvm-kvm/releases/tag/usb-potential-fix-1 however for me it still shows usb state as "addressed", same when system is in grub menu and registers no input, only works after the OS boots up. I am running app version 0.3.7 and system 0.2.3, i have also tried tagged release above however it doesn't work as well. Host machine: - HP prodesk 600 g4 - HP elitedesk 800 g2 I tried this on older asus system and keyboard input works in bios and grub, so this has to be HP specific

deekerman added the

component: usb

label

2026-02-20 08:20:45 -05:00

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@Marvin-D-Martian commented on GitHub (Mar 7, 2025):

Same here. HP ProDesk 600 G2 Mini

UI shows USB as Connected, but KB input or Virtual KB input doesn't work, either while booting to interrupt and go to UEFI/BIOS settings or in BOOT menu. When entering BIOS by restarting from Windows (Reset PC -> Advanced-> Firmware Settings) and entering HP BIOS, still no input working.

Using latest BIOS (2024 release), Secureboot off. The Mounted ISO is not detected as a boot option either.

@Marvin-D-Martian commented on GitHub (Mar 7, 2025): Same here. HP ProDesk 600 G2 Mini UI shows USB as Connected, but KB input or Virtual KB input doesn't work, either while booting to interrupt and go to UEFI/BIOS settings or in BOOT menu. When entering BIOS by restarting from Windows (Reset PC -> Advanced-> Firmware Settings) and entering HP BIOS, still no input working. Using latest BIOS (2024 release), Secureboot off. The Mounted ISO is not detected as a boot option either.

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@bufanda commented on GitHub (May 6, 2025):

On my EliteDesk 800 G3 mini I have it that when rebooting and hiting F10 too often that the keyboard wouldn't work at all event after the OS comes up until I unplug and plugin in USB again and then the jetkvm sends all keystrokes that were done while it got stuck.

@bufanda commented on GitHub (May 6, 2025): On my EliteDesk 800 G3 mini I have it that when rebooting and hiting F10 too often that the keyboard wouldn't work at all event after the OS comes up until I unplug and plugin in USB again and then the jetkvm sends all keystrokes that were done while it got stuck.

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@Schueni1 commented on GitHub (May 7, 2025):

I am facing the same issue with an HP Elitedesk 800 G4.
Setting the JetKVM to "Keyboard only" fixes the issue.
Installing an operating system with mass storage is of course not possible with this workaround.

@Schueni1 commented on GitHub (May 7, 2025): I am facing the same issue with an HP Elitedesk 800 G4. Setting the JetKVM to "Keyboard only" fixes the issue. Installing an operating system with mass storage is of course not possible with this workaround.

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@Marvin-D-Martian commented on GitHub (May 7, 2025):

This is a major issue. It makes the KVM completely useless with a major poertion of existing hardware made by HP. I really like the device, but I am forced to use piKvm as jetKVM is essentially a remote monitor at best at the moment. Doesn't work with most of my HP hardware. I really hope this will be resolved soon, but the delay in addressing this issue makes me wonder.

@Marvin-D-Martian commented on GitHub (May 7, 2025): This is a major issue. It makes the KVM completely useless with a major poertion of existing hardware made by HP. I really like the device, but I am forced to use piKvm as jetKVM is essentially a remote monitor at best at the moment. Doesn't work with most of my HP hardware. I really hope this will be resolved soon, but the delay in addressing this issue makes me wonder.

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@dirtyb1rd commented on GitHub (Jul 13, 2025):

I am having this issue as well. I cannot consistently boot to BIOS when needed.

@dirtyb1rd commented on GitHub (Jul 13, 2025): I am having this issue as well. I cannot consistently boot to BIOS when needed.

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@pgoff commented on GitHub (Aug 26, 2025):

I have the same issue on my HP Mini ProDesk 600 G2 when using the JetKVM.
I would say this applies to more than just the JetKVM though as my AVOCENT MPU2016DAC is having the same issue. Their current firwmare is from I believe March 2025 and still having the issue.
This make me believe it is something to do with how HP implements things. Still I would like to believe there is a solution out there either by a firmware update to the JetKVM, changing settings in the HP, or both.

@pgoff commented on GitHub (Aug 26, 2025): I have the same issue on my HP Mini ProDesk 600 G2 when using the JetKVM. I would say this applies to more than just the JetKVM though as my AVOCENT MPU2016DAC is having the same issue. Their current firwmare is from I believe March 2025 and still having the issue. This make me believe it is something to do with how HP implements things. Still I would like to believe there is a solution out there either by a firmware update to the JetKVM, changing settings in the HP, or both.

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@MichaelTrip commented on GitHub (Sep 3, 2025):

I am also having the same issue with a few HP Elitedesks.

@MichaelTrip commented on GitHub (Sep 3, 2025): I am also having the same issue with a few HP Elitedesks.

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@BombusAlpinus commented on GitHub (Sep 8, 2025):

same here with an hp prodesk 600 g4 mini, no bios/boot menue call possible... will have to go in the cellar equipped with a good old usb stick, monitor.. mouse and keyboard ...

@BombusAlpinus commented on GitHub (Sep 8, 2025): same here with an hp prodesk 600 g4 mini, no bios/boot menue call possible... will have to go in the cellar equipped with a good old usb stick, monitor.. mouse and keyboard ...

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@elvtechnology commented on GitHub (Oct 26, 2025):

Just ran into this exact issue. HP ProDesk 600 G4 with latest BIOS and latest JetKVM firmware.

With virtual media enabled the BIOS does not configure the USB interface at all and not even keyboard works.

Disabling virtual media restores the keyboard but that doesn't exactly help as that defeats the sole purpose of what I needed to achieve.

To top it off I have no physical access to the remote system either so I guess I have to organise a trip across the city.

Definitely not a great first experience. 🤣

@elvtechnology commented on GitHub (Oct 26, 2025): Just ran into this exact issue. HP ProDesk 600 G4 with latest BIOS and latest JetKVM firmware. With virtual media enabled the BIOS does not configure the USB interface at all and not even keyboard works. Disabling virtual media restores the keyboard but that doesn't exactly help as that defeats the sole purpose of what I needed to achieve. To top it off I have no physical access to the remote system either so I guess I have to organise a trip across the city. Definitely not a great first experience. 🤣

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@pgoff commented on GitHub (Oct 26, 2025):

I would say this is not a problem soley with JetKVM though. None of my KVM's are working properly with the HP line of mini computers. I don't have any HP servers right now so I couldn't say if they work with those or not.

@pgoff commented on GitHub (Oct 26, 2025): I would say this is not a problem soley with JetKVM though. None of my KVM's are working properly with the HP line of mini computers. I don't have any HP servers right now so I couldn't say if they work with those or not.

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@Schueni1 commented on GitHub (Oct 26, 2025):

I can attest that. I also do not think, that this is a JetKVM issue.
My NanoKVM has the exact same issue on my HP EliteDesk as well as on my H2 Odroid.

@Schueni1 commented on GitHub (Oct 26, 2025): I can attest that. I also do not think, that this is a JetKVM issue. My NanoKVM has the exact same issue on my HP EliteDesk as well as on my H2 Odroid.

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@Marvin-D-Martian commented on GitHub (Oct 27, 2025):

I can attest that. I also do not think, that this is a JetKVM issue. My NanoKVM has the exact same issue on my HP EliteDesk as well as on my H2 Odroid.

Well it works with piKVM, so I'd say it's about Jet handling the connection differently

@Marvin-D-Martian commented on GitHub (Oct 27, 2025): > I can attest that. I also do not think, that this is a JetKVM issue. My NanoKVM has the exact same issue on my HP EliteDesk as well as on my H2 Odroid. Well it works with piKVM, so I'd say it's about Jet handling the connection differently

deekerman commented

2026-02-20 08:20:46 -05:00

Author

Owner

@dirtyb1rd commented on GitHub (Oct 27, 2025):

Thought someone else might find these useful... here are two workarounds I have found:

To get to BIOS without USB (requires ATX Power ext.): Some bios have a feature that allow you to hold power button for 10 seconds to boot into the BIOS, this works very well for me on my MSI MOBO and holding the button in web GUI for the 10 seconds.
when the USB connection is failing altogether, you can open Settings < Advanced, Check the box next to troubleshooting, then click the button that says 'Disable USB Emulation'; wait 10 seconds; click the button that now says 'Enable USB Emulation', uncheck troubleshooting mode, back out of settings. (this does not always work on first try)

@dirtyb1rd commented on GitHub (Oct 27, 2025): Thought someone else might find these useful... here are two workarounds I have found: - To get to BIOS without USB (requires ATX Power ext.): Some bios have a feature that allow you to hold power button for 10 seconds to boot into the BIOS, this works very well for me on my MSI MOBO and holding the button in web GUI for the 10 seconds. - when the USB connection is failing altogether, you can open Settings < Advanced, Check the box next to troubleshooting, then click the button that says 'Disable USB Emulation'; wait 10 seconds; click the button that now says 'Enable USB Emulation', uncheck troubleshooting mode, back out of settings. (this does not always work on first try)