mirror of https://github.com/pikvm/pikvm.git
Update v3.md (#975)
Reverts one change for following reason: Always use 'Web Interface' and 'Web Terminal' in order to make sure it is not mistaken as only *a* terminal (the SSH terminal) as in other files. That makes clear that to a PiKVM feature is referred.
This commit is contained in:
parent
0a8555280e
commit
2bd2b51cf7
|
|
@ -87,7 +87,7 @@ If you have a kit without a metal case, you can use our free 3D printing case dr
|
|||
7. !!! danger "Just reminding again: CHANGE THE PASSWORDS! :)"
|
||||
How to do this was written in [the "First steps" guide](first_steps.md){target=_blank}
|
||||
|
||||
8. **Try to manage the computer using PiKVM with the web interface.** Make sure that you get an image and both keyboard and mouse are working. If something doesn't work, check out our [FAQ](faq.md) (it's really useful). If nothing helped, you can get support in our [Discord chat](https://discord.gg/bpmXfz5).
|
||||
8. **Try to manage the computer using PiKVM with the Web Interface.** Make sure that you get an image and both keyboard and mouse are working. If something doesn't work, check out our [FAQ](faq.md) (it's really useful). If nothing helped, you can get support in our [Discord chat](https://discord.gg/bpmXfz5).
|
||||
|
||||
9. ??? note "Check the HDMI backpowering problem. ONLY applicable under specific circumstances. NOT getting NO SIGNAL."
|
||||
Try restarting PiKVM using the `reboot` command executed in the terminal. If PiKVM hangs during boot (you can't get the Web Interface for a long time), then you are faced with this rare problem. **Don't worry, it's easy to fix.** Turn off the PiKVM, disconnect all cables from it, take a close look at the [diagram of its ports and jumpers](#io-ports-and-jumpers), and **remove jumper #14** (it is to the right of the CSI connector). Then you can connect and power up PiKVM again. Now everything will be fine.
|
||||
|
|
|
|||
Loading…
Reference in New Issue