Skip to content

Latest commit

 

History

History
52 lines (36 loc) · 4.6 KB

troubleshooting.md

File metadata and controls

52 lines (36 loc) · 4.6 KB
Raw

Troubleshooting Pi-KVM / FAQ

As a first step we recommend carefully reading our documentation on GitHub. Most steps to successfully set up your Pi-KVM are already described there. If you run into any issues you can check this Troubleshooting guide which will list common errors. If that still doesn't help you you're welcome to raise an issue ticket or join our Discord for further help

Hardware

LEDs / Switches do not work in ATX control.

  • Double check your wiring as per the documentation. Make sure you placed the relays (G3VM-61A1) in the correct orientation. The relays for switches (Power, Reset) have a different orientation than the ones for LEDs.

Pi-KVM does not show any image from the connected computer.

  • Double check if you connected the HDMI-CSI-2 bridge cable correctly. Check the documentation for details A red LED will light up on the bridge if it is connected properly.
  • Some laptops do not output any signal until you switched the ouput (usually via the FN + and an F5 key on the keyboard).

HDMI-CSI bridge not working with official RPi PoE HAT

Details here. The reason is that the HAT has a built-in fan controller that conflicts with the TC358743 chip. The solution is to disable the fan control and connect it to the power line so that it works continuously. To turn off the controller you need to add the line disable_poe_fan=1 to /boot/config.txt.

Software

How do I update Pi-KVM with the latest software?

  • Connect to your Pi-KVM via ssh and run 
    rw
pacman -Syu
reboot

Glitchy/wrong BIOS resolution

  • On some motherboards, the BIOS may be displayed at a lower resolution, or with some rendering issues/glitches, specially on newer ASUS ones. Like this:

    ASUS BIOS glitch

    This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options.

    If you can't or don't want to enable the CSM, you can try connecting a DisplayPort monitor, or a dummy plug. If you remove the DP cable/adapter the bug will reappear.

    If none of this works, try connecting the DP cable first, boot into the BIOS, disable the CSM and shutdown (do not restart) your PC. Then, boot into the BIOS and enable the CSM before shutting down your PC. Then connect the HDMI and turn your PC on again.

Awesome WM video output

  • Sometimes Awesome WM on Linux can't recognize a video output change on a cable. That is, if the cable was first inserted into the monitor, and then you reconnected it to Pi-KVM - it may happen that you will not see the image. It seems that the problem is Awesome WM, since for example with KDE it does not reproducing. If you turn on your workstation with Pi-KVM already connected, everything will work fine.

Unexpected interruption while loading the image for Mass Storage Drive.

  • If problems occur when uploading even a small disk image it may be due to unstable network operation or antivirus software. It is well known that Kaspersky antivirus cuts off Pi-KVM connections during uploading, so you should add the Pi-KVM website to Kaspersky's list of exceptions or not filter web requests with the antivirus. Antivirus programs can also affect the performance of certain interface elements, for example the quality slider. For Kaspersky, the steps to add the network address of Pi-KVM's website to the exclusion list is: Protection -> Private browsing -> Categories and exclusions -> Exclusions

The Pi-KVM web interface does not work correctly in Mozilla Firefox while it works fine in Google Chrome.

I can't copy clipboard contents from the server (the machine controlled via Pi-KVM) to the client.

  • The clipboard only works from the client to the server not vice versa. There is currently no way to do it.

Big mouse latency on RPi as managed server

  • Unusual case: RPi4 is used as a Pi-KVM to control RPi3. In this case, the mouse delay may be several seconds. To fix it, just add line usbhid.mousepoll=0 to /boot/config.txt to the server (i.e. RPI3 in our case) and reboot it.