Yes but the only officially supported version is the v3Pre-AssembledorHAT's, v2 we will attempt best effort but ultimatly we do not support CSI modules or USB.
54
+
Yes but the only officially supported version is the PiKVMV3+devices, V2 we will attempt best effort but ultimatly we do not support CSI modules or USB.
55
55
56
56
57
57
??? question "Can I power the Pi via PoE?"
skipped 1 lines
59
59
60
60
61
61
??? question "Do I need a power splitter? Why do I need one?"
62
-
* Yes for RPi4 - Please see the main readme for splitter types listed under V2 Hardware
62
+
* Yes for RPi4 - Please see the main readme for splitter types listed under V2 hardware
63
63
* Yes for Zero W and Zero W 2, if using dedicated power you still need to split the power from the data towards the target. If using the target for power, this is not needed.
64
-
* This is not needed if you have a v3HAT, as the HAT splits power and signal on the board.
64
+
* This is not needed if you have a PiKVMV3, as the HAT splits power and signal on the board.
65
65
66
66
67
67
??? question "Can I use PiKVM with non-Raspberry Pi boards (Orange, Nano, etc)?"
skipped 188 lines
256
256
* Set the timezone with `timedatectl set-timezone <YourTimeZoneHere>` e.g. `timedatectl set-timezone Australia/Victoria`.
257
257
* Stop the time syncing service with `systemctl stop systemd-timesyncd` as this will prevent the next step if running.
258
258
* Set the time and date with `timedatectl set-time 'YYYY-MM-DD HH:MM:SS'` e.g. `timedatectl set-time '2023-02-26 14:50:10'`.
259
-
* If you have hardware clock e.g. V3&V4HAT, update it with `hwclock --systohc` , then check it with `hwclock --show`.
259
+
* If you have hardware clock e.g. V3+, update it with `hwclock --systohc` , then check it with `hwclock --show`.
260
260
* Switch filesystem to RO-mode with the command `ro`.
261
261
262
262
skipped 73 lines
336
336
## Video problems
337
337
338
338
??? question "I can see the video but I can't see the WebRTC switch"
339
-
WebRTC is an alternative mode for the default MJPEG and it's only supported on v2+ platforms with the CSI video capture device. See [this](webrtc.md) page to solve any problems with WebRTC.
339
+
WebRTC is an alternative mode for the default MJPEG and it's only supported on V2+ platforms with the CSI video capture device. See [this](webrtc.md) page to solve any problems with WebRTC.
340
340
341
341
342
342
??? question "PiKVM does not show the video from the computer at all"
skipped 51 lines
394
394
395
395
## USB problems (keyboard, mouse, mass storage, etc)
396
396
397
-
??? question "My computer does not recognize USB of PiKVM v2+ at all"
397
+
??? question "My computer does not recognize USB of PiKVM V2+ at all"
398
398
* Make sure that you have used the correct USB cable with DATA lines to connect the OTG port for the Raspberry to the computer. You may have decided to use a USB hub instead of a Y-cable and **it won't work**. Use good cables and follow the instructions :)
399
399
* In rare cases, some very buggy BIOSes do not like HID and Mass Storage in one USB device. You can either [disable Mass Storage](msd.md#disable-msd), or use an [Arduino HID](arduino_hid.md) to physically separate them.
400
400
401
401
402
-
??? question "BIOS/UEFI does not recognize USB of v2+, but computer does"
402
+
??? question "BIOS/UEFI does not recognize USB of V2+, but computer does"
403
403
If you are using a USB hub or USB PCI controller, this may not be handled by your BIOS. Try to use another USB port. Some ports may have a built-in hub on the motherboard and a buggy BIOS that can't handle it.
404
404
405
405
skipped 1 lines
407
407
The BIOS does not support absolute mouse mode, which is preferred by PiKVM. In this case, [you can enable relative or dual positioning mode](mouse.md).
408
408
409
409
410
-
??? question "I can't wake up suspended computer on v2+"
410
+
??? question "I can't wake up suspended computer on V2+"
411
411
This feature is experimental and requires manual activation. Perform a full system update, edit `/etc/kvmd/override.yaml`, and reboot. After that, you can use remote wakeup by pressing any keyboard key or mouse button.
412
412
413
413
```yaml
skipped 1 lines
415
415
remote_wakeup: true
416
416
```
417
417
418
+
For V4, you don't need to add this option as it is enabled by default.
418
419
419
-
??? question "My mass storage drive works (I can boot an image from PiKVM v2+), but my keyboard/mouse does not"
420
+
If something doesn't work, please report about the problem [here](https://discord.gg/bpmXfz5) (preferred) or [here](https://github.com/pikvm/pikvm/issues).
421
+
422
+
423
+
??? question "My mass storage drive works (I can boot an image from PiKVM V2+), but my keyboard/mouse does not"
420
424
In rare cases, some very buggy BIOSes does not like HID and Mass Storage in one USB device. You can either [disable Mass Storage](msd.md#disable-msd), or use an [Arduino HID](arduino_hid.md) to physically separate them.
421
425
422
426
423
427
??? question "Buggy absolute mouse on Windows 98 as managed server"
??? question "The mouse does not work with NVR/DVR CCTV"
435
+
Often these devices have a buggy USB driver that does not understand an absolute mouse and/or a mouse with horizontal scrolling. In this case, the following configuration for `/etc/kvmd/override.yaml` will help you:
436
+
437
+
```yaml
438
+
kvmd:
439
+
hid:
440
+
mouse:
441
+
absolute: false
442
+
horizontal_wheel: false
443
+
mouse_alt:
444
+
device: ""
445
+
```
446
+
447
+
It will make the relative mouse without horizontal scrolling the only mice.
428
448
429
449
430
450
??? question "There's big mouse latency on another Raspberry Pi as managed server"
Maxim Devaev
committed
12 months ago
1 parent 9cb12a4d