public_git
/
pikvm
mirror of https://github.com/pikvm/pikvm.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge remote-tracking branch 'origin' into v4-update

This commit is contained in:
Aleksandr Prokudin 2025-03-12 01:22:40 +01:00
parent 12f6cb5a2d b23fb02985
commit 8848a62d00
2 changed files with 45 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
docs/edid.md
View File

@ -9,7 +9,8 @@ EDID is information about the video modes supported by the video capture device.
In the case of PiKVM, this is an HDMI CSI bridge. Usually, you don't need to change this, since the default configuration is quite flexible,
but sometimes, for example for strange UEFIs/BIOSes, this may be necessary (the [story](https://github.com/pikvm/pikvm/issues/78)).
The EDID is stored on the PiKVM in the file `/etc/kvmd/tc358743-edid.hex`. If you write new data there, it will be applied after rebooting.
The EDID is stored on the PiKVM in the file `/etc/kvmd/tc358743-edid.hex`. If you write new data there, it will be applied after rebooting
or using the command `kvmd-edidconf --apply`.
You can also apply the new EDID without rebooting to make sure it works:
@ -22,14 +23,32 @@ You can also apply the new EDID without rebooting to make sure it works:
-----
## Default EDID
## Adopt real display indentifiers on V4 Plus
PiKVM V4 Plus has a simple way read and adopt display identifiers like model and serial number
from the physical monitor connected to `OUT2` port (it's also used for [HDMI passthrough](pass.md)).
This way, the target host will recognize PiKVM as your display.
To adopt display identifiers, connect the display to `OUT2` port and run these commands:
```console
[root@pikvm ~]# rw
[root@pikvm ~]# kvmd-edidconf --import-display-ids --apply
[root@pikvm ~]# ro
```
The display can be unplugged. PiKVM will remember the new settings.
-----
## Restore default EDID
If you need to restore the default EDID you can easily do this with `kvmd-edidconf`, for example:
```console
[root@pikvm ~]# rw
[root@pikvm ~]# kvmd-edidconf --import-preset=v4plus
[root@pikvm ~]# reboot
[root@pikvm ~]# kvmd-edidconf --import-preset=v4plus --apply
[root@pikvm ~]# ro
```
Available options: `v0`, `v1`, `v2`, `v3`, `v4mini` and `v4plus`.
@ -38,7 +57,7 @@ or in the [kvmd repo](https://github.com/pikvm/kvmd/blob/master/configs/kvmd/edi
-----
## Force 1080p by default on PiKVM V0+
## Force 1080p by default on PiKVM V0-V3
PiKVM V3 (or DIY V0-V2) has a hardware limit of 50Hz for 1080p mode, and this is a less common frequency than 60Hz.
Therefore, on V3, the default mode is 720p. Some OS (like Proxmox) may not work well with 720p,
@ -46,8 +65,8 @@ so you can force 1080p resolution by default:
```console
[root@pikvm ~]# rw
[root@pikvm ~]# kvmd-edidconf --import-preset=v3.1080p-by-default # Or, for example, v1.1080p-by-default
[root@pikvm ~]# reboot
[root@pikvm ~]# kvmd-edidconf --import-preset=v3.1080p-by-default --apply # Or, for example, v1.1080p-by-default
[root@pikvm ~]# ro
```
@ -60,8 +79,8 @@ you can easily disable it and use only 1920x1080:
```console
[root@pikvm ~]# rw
[root@pikvm ~]# kvmd-edidconf --import-preset=v4plus.no-1920x1200 # Or v4mini.no-1920x1200
[root@pikvm ~]# reboot
[root@pikvm ~]# kvmd-edidconf --import-preset=v4plus.no-1920x1200 --apply # Or v4mini.no-1920x1200
[root@pikvm ~]# ro
```
@ -244,8 +263,7 @@ So, to tune EDID on PiKVM, use the following steps:
The `kvmd-edidconfig` utility has the ability to change some simple parameters without using an external editor. For example you can change the vendor, model name and enable [HDMI audio](audio.md) on the PiKVM virtual display:
```console
[root@pikvm ~]# kvmd-edidconf --set-mfc-id=LNX --set-monitor-name=PiKVM --set-audio=1
[root@pikvm ~]# reboot
[root@pikvm ~]# kvmd-edidconf --set-mfc-id=LNX --set-monitor-name=PiKVM --set-audio=1 --apply
```
!!! note

40
docs/flashing_os.md
View File

@ -4,14 +4,6 @@
Minimum **32 Gb, Class 10** recommended.
!!! info "PiKVM OS 64-bit images"
Since 2025.02.18, PiKVM OS was moved to 64-bit images for all devices except DIY based on Raspberry Pi 2.
If you have previously used PiKVM OS and want to upgrade to 64-bit,
then you need to reinstall the OS completely with the new image from links below.
PiKVMs previously installed using 32-bit images will continue to be supported and updated as before.
-----
## Download the image
@ -22,13 +14,13 @@ Download the appropriate SD card image. Select it based on the board, platform,
These images are not suitable for DIY and are intended only for our branded devices.
* **PiKVM V4**
* **PiKVM V4** <sub>*64-bit*</sub>
* [PiKVM V4 Mini](https://files.pikvm.org/images/v4mini-hdmi-rpi4/aarch64/v4mini-hdmi-rpi4-aarch64-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v4mini-hdmi-rpi4/aarch64/v4mini-hdmi-rpi4-aarch64-latest.img.xz.sha1)
* [PiKVM V4 Plus](https://files.pikvm.org/images/v4plus-hdmi-rpi4/aarch64/v4plus-hdmi-rpi4-aarch64-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v4plus-hdmi-rpi4/aarch64/v4plus-hdmi-rpi4-aarch64-latest.img.xz.sha1)
* **PiKVM V3**
* **PiKVM V3** <sub>*64-bit*</sub>
* [PiKVM V3 HAT BOX Image, OLED/FAN preactivated](https://files.pikvm.org/images/v3-hdmi-rpi4/aarch64/v3-hdmi-rpi4-aarch64-box-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v3-hdmi-rpi4/aarch64/v3-hdmi-rpi4-aarch64-box-latest.img.xz.sha1)
* [PiKVM V3 HAT DIY Assembly](https://files.pikvm.org/images/v3-hdmi-rpi4/aarch64/v3-hdmi-rpi4-aarch64-latest.img.xz)
@ -36,23 +28,23 @@ Download the appropriate SD card image. Select it based on the board, platform,
!!! abstract "DIY PiKVM V2 Platform"
* **Raspberry Pi 4**
* **Raspberry Pi 4** <sub>*64-bit*</sub>
* [For HDMI-CSI bridge](https://files.pikvm.org/images/v2-hdmi-rpi4/aarch64/v2-hdmi-rpi4-aarch64-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v2-hdmi-rpi4/aarch64/v2-hdmi-rpi4-aarch64-latest.img.xz.sha1)</sub>
* [For HDMI-USB dongle](https://files.pikvm.org/images/v2-hdmiusb-rpi4/aarch64/v2-hdmiusb-rpi4-aarch64-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v2-hdmiusb-rpi4/aarch64/v2-hdmiusb-rpi4-aarch64-latest.img.xz.sha1)</sub>
* **Raspberry Pi Zero 2 W**
* [For HDMI-CSI bridge](https://files.pikvm.org/images/v2-hdmi-zero2w/aarch64/v2-hdmi-zero2w-aarch64-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v2-hdmi-zero2w/aarch64/v2-hdmi-zero2w-aarch64-latest.img.xz.sha1)</sub>
* **Raspberry Pi Zero 2 W** <sub>*32-bit*</sub>
* [For HDMI-CSI bridge](https://files.pikvm.org/images/v2-hdmi-zero2w/arm/v2-hdmi-zero2w-arm-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v2-hdmi-zero2w/arm/v2-hdmi-zero2w-arm-latest.img.xz.sha1)</sub>
!!! abstract "DIY PiKVM V1 Platform"
* **Raspberry Pi 3**
* [For HDMI-CSI bridge](https://files.pikvm.org/images/v1-hdmi-rpi3/aarch64/v1-hdmi-rpi3-aarch64-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v1-hdmi-rpi3/aarch64/v1-hdmi-rpi3-aarch64-latest.img.xz.sha1)</sub>
* [For HDMI-USB dongle](https://files.pikvm.org/images/v1-hdmiusb-rpi3/aarch64/v1-hdmiusb-rpi3-aarch64-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v1-hdmiusb-rpi3/aarch64/v1-hdmiusb-rpi3-aarch64-latest.img.xz.sha1)</sub>
* **Raspberry Pi 3** <sub>*32-bit*</sub>
* [For HDMI-CSI bridge](https://files.pikvm.org/images/v1-hdmi-rpi3/arm/v1-hdmi-rpi3-arm-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v1-hdmi-rpi3/arm/v1-hdmi-rpi3-arm-latest.img.xz.sha1)</sub>
* [For HDMI-USB dongle](https://files.pikvm.org/images/v1-hdmiusb-rpi3/arm/v1-hdmiusb-rpi3-arm-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v1-hdmiusb-rpi3/arm/v1-hdmiusb-rpi3-arm-latest.img.xz.sha1)</sub>
* **Raspberry Pi 2** <sub>*32-bit*</sub>
* [For HDMI-CSI bridge](https://files.pikvm.org/images/v1-hdmi-rpi2/arm/v1-hdmi-rpi2-arm-latest.img.xz)
@ -60,11 +52,11 @@ Download the appropriate SD card image. Select it based on the board, platform,
* [For HDMI-USB dongle](https://files.pikvm.org/images/v1-hdmiusb-rpi2/arm/v1-hdmiusb-rpi2-arm-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v1-hdmiusb-rpi2/arm/v1-hdmiusb-rpi2-arm-latest.img.xz.sha1)</sub>
* **Raspberry Pi Zero 2 W**
* [For HDMI-CSI bridge](https://files.pikvm.org/images/v1-hdmi-zero2w/aarch64/v1-hdmi-zero2w-aarch64-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v1-hdmi-zero2w/aarch64/v1-hdmi-zero2w-aarch64-latest.img.xz.sha1)</sub>
* [For HDMI-USB dongle](https://files.pikvm.org/images/v1-hdmiusb-zero2w/aarch64/v1-hdmiusb-zero2w-aarch64-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v1-hdmiusb-zero2w/aarch64/v1-hdmiusb-zero2w-aarch64-latest.img.xz.sha1)</sub>
* **Raspberry Pi Zero 2 W** <sub>*32-bit*</sub>
* [For HDMI-CSI bridge](https://files.pikvm.org/images/v1-hdmi-zero2w/arm/v1-hdmi-zero2w-arm-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v1-hdmi-zero2w/arm/v1-hdmi-zero2w-arm-latest.img.xz.sha1)</sub>
* [For HDMI-USB dongle](https://files.pikvm.org/images/v1-hdmiusb-zero2w/arm/v1-hdmiusb-zero2w-arm-latest.img.xz)
<sub>- [*sha1*](https://files.pikvm.org/images/v1-hdmiusb-zero2w/arm/v1-hdmiusb-zero2w-arm-latest.img.xz.sha1)</sub>
!!! abstract "Any other combinations for advanced users"
Please check the [file archives](https://files.pikvm.org/images/) for ready-made image or [build the image yourself](building_os.md).