There is no HDMI signal at BIOS level until the Windows 11 OS is booting if the HDMI port is connected to Dell Latitude 5420 notebook. However, I can get HDMI signal at BIOS level if the KVM switched to use HP ProDesk 600 G4 HDMI port.
Besides, both Dell Latitude 5420 and HP ProDesk 600 G4 have no respond the MOUSE and KEYBOARD they are going to boot the OS. Therefore, I would like to know whether it is normal
The laptop may output the BIOS screen by default to the built-in screen, and basically no way to perform bios control on the laptop
both Dell Latitude 5420 and HP ProDesk 600 G4 have no respond the MOUSE and KEYBOARD they are going to boot the OS Can you describe this in detail?
The keyboard icon shown "Keyboard free, inactive" and Mouse icon shown "Mouse free, inactive". The color of these two icons are orange
try disable virtual media or run below command see if it did any help
run below command in webterminal
tee /etc/kvmd/override.yaml >/dev/null <<'EOF'
otg:
manufacturer: Corsair
product: 'Corsair Gaming RGB '
product_id: 26995
serial: ''
vendor_id: 26944
EOF
And then reboot comet. See if it can work , these line disguise comet as a Corsair device
Hi minmie,
That command is work. Thanks. Do you have another command to disguise comet as a mouse?
Although I provided you with the command, I still don't understand why disguising as another device would make it controllable. This is very strange.
You can find what you want on this website, but remember to convert hexadecimal to decimal for use usbid
Here with V1.3.1R2, the BIOS cannot be called on an HP Prodesk via browser. Once the computer has started, keyboard input sometimes works. The full screen mode reliably deactivates the keyboard input. Mouse doesn't work at all.
After your tip it works a little better, but in full screen mode the keyboard is reliably hung away. Incidentally, I use well as a browser.
some bios only support relative mouse, try it
I think the problem is more of a focus issue in the WebGUI. As soon as you activate full-screen mode with the mouse, the display loses focus and keyboard capturing. Of course, this is no longer visible anywhere. Another mouse click on the displayed full-screen display restores both, and keyboard inputs are accepted again. Very unsightly and confusing behavior. Setting the mouse to relative makes the puzzle even worse, as the mouse pointer is then no longer displayed in a full-screen terminal window. This simply "successfully" disconnects a second display.
Will the Comet's disguise as a Corsair survive a firmware update?
