diff --git a/docs/en/https.md b/docs/en/https.md index 0121ecf3..13a2df89 100644 --- a/docs/en/https.md +++ b/docs/en/https.md @@ -1,4 +1,4 @@ -# Encryption Certificate +# **Encryption Certificate** From version v1.4.9, blikvm defaults to HTTPS. Even if you access via HTTP, it will automatically redirect to HTTPS: ``` sudo -s @@ -11,4 +11,84 @@ Find the following configuration content. The key and cert are located in the pa "key": "./lib/https/key.pem", "cert": "./lib/https/cert.pem" } -``` \ No newline at end of file +``` + +# **Let's Encrypt** +!!! info + You need a publicly valid domain name to use Let's Encrypt. This example uses the domain blikvm.space. +1. Start applying for the certificate +Run the following command to start applying for the certificate: +``` +certbot certonly --manual --preferred-challenges dns -d example.com +``` +2. Add a DNS record in the domain console. +``` +Saving debug log to /var/log/letsencrypt/letsencrypt.log +Plugins selected: Authenticator manual, Installer None +Requesting a certificate for blikvm.space +Performing the following challenges: +dns-01 challenge for blikvm.space + +- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +Please deploy a DNS TXT record under the name +_acme-challenge.blikvm.space with the following value: + +UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc + +Before continuing, verify the record is deployed. +- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +Press Enter to Continue +``` +After executing the above command, you will see similar output. Follow the prompts to log in to the domain backend (such as Amazon Cloud, Alibaba Cloud, Tencent Cloud, etc.), add a TXT record named _acme-challenge.example.com, and use UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc as the record value. + +3. When the DNS record takes effect, press Enter to continue. +!!! warn + - DNS records do not take effect immediately, so press Enter later. + - Use the command nslookup -type=TXT _acme-challenge.blikvm.space to verify if the DNS is effective, as shown below: + ``` + root@blikvm(rw):/mnt/tmp# nslookup -type=TXT _acme-challenge.blikvm.space + Server: 192.168.8.1 + Address: 192.168.8.1#53 + + Non-authoritative answer: + _acme-challenge.blikvm.space text = "UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc" + Authoritative answers can be found from: + ``` +You will receive a certificate application success prompt (similar to the following content): +``` +Waiting for verification... +Cleaning up challenges +Subscribe to the EFF mailing list (email: info@blicube.com). + +IMPORTANT NOTES: + - Congratulations! Your certificate and chain have been saved at: + /etc/letsencrypt/live/blikvm.space/fullchain.pem + Your key file has been saved at: + /etc/letsencrypt/live/blikvm.space/privkey.pem + Your certificate will expire on 2025-03-04. To obtain a new or + tweaked version of this certificate in the future, simply run + certbot again. To non-interactively renew *all* of your + certificates, run "certbot renew" + - If you like Certbot, please consider supporting our work by: + + Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate + Donating to EFF: https://eff.org/donate-le +``` +4. Use the certificate +According to step 3, you can see that the certificate path is in /etc/letsencrypt/live/blikvm.space/. Modify the configuration file: +``` +vim /mnt/exec/release/config/app.json +Replace the following key and cert with +"server": { + "ssl": { + "key": "/etc/letsencrypt/live/blikvm.space/privkey.pem", + "cert": "/etc/letsencrypt/live/blikvm.space/fullchain.pem" +} +``` +5. Set the local domain name for blikvm. Open /etc/hosts on the PC, and add the following line. The IP and domain name here depend on your actual situation. +``` +192.168.8.16 blikvm.space +``` + +6. Then you can directly access blikvm using the domain name. +![](assets/images/https/letsencrypt.png){width="400"} diff --git a/docs/en/static_ip.md b/docs/en/static_ip.md index 741bab88..c137d6e4 100644 --- a/docs/en/static_ip.md +++ b/docs/en/static_ip.md @@ -60,10 +60,10 @@ To configure a static IP address on a BliKVM image, you can follow these steps: Adjust the values according to your network configuration. 5. Save the changes. -6. Restart the BliKVM for the changes to take effect: +6. Restart the NetworkManager for the changes to take effect: ```bash - sudo reboot + sudo systemctl restart NetworkManager ``` After the reboot, your BliKVM will use the configured static IP address instead of obtaining one dynamically from a DHCP server. Make sure the static IP address you choose is not already assigned to another device on the network and is within the same subnet. diff --git a/docs/zh/https.md b/docs/zh/https.md index bc8287ba..e674951c 100644 --- a/docs/zh/https.md +++ b/docs/zh/https.md @@ -1,4 +1,4 @@ -# 加密证书 +# **加密证书** blikvm v1.4.9版本后,默认为https启动，即使访问http也会自动被重定向到https: ``` @@ -12,4 +12,84 @@ vim /mnt/exec/release/config/app.json "key": "./lib/https/key.pem", "cert": "./lib/https/cert.pem" } -``` \ No newline at end of file +``` + +# Let's Encrypt申请合法证书: +!!! info + 你需要有一个公网合法的域名才能使用Let's Encrypt,本说明以blikvm.space域名为例 +1. 开始申请证书 +执行如下命令开始申请证书： +``` +certbot certonly --manual --preferred-challenges dns -d example.com +``` +2. 在域名控制台中添加解析记录. +``` +Saving debug log to /var/log/letsencrypt/letsencrypt.log +Plugins selected: Authenticator manual, Installer None +Requesting a certificate for blikvm.space +Performing the following challenges: +dns-01 challenge for blikvm.space + +- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +Please deploy a DNS TXT record under the name +_acme-challenge.blikvm.space with the following value: + +UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc + +Before continuing, verify the record is deployed. +- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +Press Enter to Continue +``` +执行完上面命令后,会有如上类似输出，根据上面提示，登录域名后台（比如亚马逊云，阿里云、腾讯云等等），添加名为 _acme-challenge.example.com 的 TXT 记录，并使用 UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc 作为记录值。 + +3. 当DNS记录生效后，点击回车继续 +!!! warn + - 由于 DNS 记录不会马上生效，所以稍后再按回车键。 + - 使用 nslookup -type=TXT _acme-challenge.blikvm.space 命令验证 DNS 是否生效，生效如下: + ``` + root@blikvm(rw):/mnt/tmp# nslookup -type=TXT _acme-challenge.blikvm.space + Server: 192.168.8.1 + Address: 192.168.8.1#53 + + Non-authoritative answer: + _acme-challenge.blikvm.space text = "UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc" + Authoritative answers can be found from: + ``` +将会收到证书申请成功的提示（类似如下内容）： +``` +Waiting for verification... +Cleaning up challenges +Subscribe to the EFF mailing list (email: info@blicube.com). + +IMPORTANT NOTES: + - Congratulations! Your certificate and chain have been saved at: + /etc/letsencrypt/live/blikvm.space/fullchain.pem + Your key file has been saved at: + /etc/letsencrypt/live/blikvm.space/privkey.pem + Your certificate will expire on 2025-03-04. To obtain a new or + tweaked version of this certificate in the future, simply run + certbot again. To non-interactively renew *all* of your + certificates, run "certbot renew" + - If you like Certbot, please consider supporting our work by: + + Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate + Donating to EFF: https://eff.org/donate-le +``` +4. 使用证书 +根据步骤3可以看到证书路径在/etc/letsencrypt/live/blikvm.space/，修改配置文件： +``` +vim /mnt/exec/release/config/app.json +将下面key和cert替换为 +"server": { + "ssl": { + "key": "/etc/letsencrypt/live/blikvm.space/privkey.pem", + "cert": "/etc/letsencrypt/live/blikvm.space/fullchain.pem" +} +``` +5. 设置blikvm的局域网域名，在pc上打开/etc/hosts,如可以增加下面这一行，这里的ip和域名根据你的实际情况而定 +``` +192.168.8.16 blikvm.space +``` + +6. 然后你就可以直接用域名访问blikvm。 +![](assets/images/https/letsencrypt.png){width="400"} \ No newline at end of file diff --git a/docs/zh/static_ip.md b/docs/zh/static_ip.md index f7999666..f02c7a65 100644 --- a/docs/zh/static_ip.md +++ b/docs/zh/static_ip.md @@ -38,10 +38,10 @@ dns-nameservers 192.168.0.1 ``` 注意：根据您的网络设置，可能需要修改上述示例中的IP地址、网关和DNS服务器的值。 -4. 保存文件并退出编辑器。 -5. 重新启动BliKVM以使静态IP设置生效： +4. 保存文件并退出编辑器, +5. 重新启动NetworkManager以使静态IP设置生效： ``` - sudo reboot + sudo systemctl restart NetworkManager ``` 根据您的网络环境和需求，您可以根据上述步骤自定义配置静态IP地址。请确保IP地址、网关和DNS服务器的设置与您的网络设置相匹配。 \ No newline at end of file diff --git a/generated/en/assets/images/https/letsencrypt.png b/generated/en/assets/images/https/letsencrypt.png new file mode 100644 index 00000000..c78a1782 Binary files /dev/null and b/generated/en/assets/images/https/letsencrypt.png differ diff --git a/generated/en/https/index.html b/generated/en/https/index.html index fa3651d0..814ef04e 100644 --- a/generated/en/https/index.html +++ b/generated/en/https/index.html @@ -446,7 +446,7 @@ -

Encryption Certificate

+

Encryption Certificate

From version v1.4.9, blikvm defaults to HTTPS. Even if you access via HTTP, it will automatically redirect to HTTPS: 

sudo -s
 vim /mnt/exec/release/config/app.json
@@ -458,6 +458,91 @@ 
Encryption Certificate

     "cert": "./lib/https/cert.pem"
 }

+

Let's Encrypt

+
+

Info

+

You need a publicly valid domain name to use Let's Encrypt. This example uses the domain blikvm.space.

+
+
    +
  1. Start applying for the certificate +Run the following command to start applying for the certificate: +
    certbot certonly --manual --preferred-challenges dns -d example.com
+
    2. +
  2. +

    Add a DNS record in the domain console. +

    Saving debug log to /var/log/letsencrypt/letsencrypt.log
+Plugins selected: Authenticator manual, Installer None
+Requesting a certificate for blikvm.space
+Performing the following challenges:
+dns-01 challenge for blikvm.space
+
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+Please deploy a DNS TXT record under the name
+_acme-challenge.blikvm.space with the following value:
+
+UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc
+
+Before continuing, verify the record is deployed.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+Press Enter to Continue
+
    +After executing the above command, you will see similar output. Follow the prompts to log in to the domain backend (such as Amazon Cloud, Alibaba Cloud, Tencent Cloud, etc.), add a TXT record named _acme-challenge.example.com, and use UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc as the record value.

    +
    3. +
  3. +

    When the DNS record takes effect, press Enter to continue.

    +
    4. +
+
+

Warn

+ +
+

You will receive a certificate application success prompt (similar to the following content): +

Waiting for verification...
+Cleaning up challenges
+Subscribe to the EFF mailing list (email: info@blicube.com).
+
+IMPORTANT NOTES:
+ - Congratulations! Your certificate and chain have been saved at:
+   /etc/letsencrypt/live/blikvm.space/fullchain.pem
+   Your key file has been saved at:
+   /etc/letsencrypt/live/blikvm.space/privkey.pem
+   Your certificate will expire on 2025-03-04. To obtain a new or
+   tweaked version of this certificate in the future, simply run
+   certbot again. To non-interactively renew *all* of your
+   certificates, run "certbot renew"
+ - If you like Certbot, please consider supporting our work by:
+
+   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
+   Donating to EFF:                    https://eff.org/donate-le
+
+4. Use the certificate +According to step 3, you can see that the certificate path is in /etc/letsencrypt/live/blikvm.space/. Modify the configuration file: +
vim /mnt/exec/release/config/app.json
+Replace the following key and cert with
+"server": {
+    "ssl": {
+    "key": "/etc/letsencrypt/live/blikvm.space/privkey.pem",
+    "cert": "/etc/letsencrypt/live/blikvm.space/fullchain.pem"
+}
+
+5. Set the local domain name for blikvm. Open /etc/hosts on the PC, and add the following line. The IP and domain name here depend on your actual situation. +
192.168.8.16 blikvm.space
+

+
    +
  1. Then you can directly access blikvm using the domain name. +
    2. +
diff --git a/generated/en/make-image/index.html b/generated/en/make-image/index.html index b3e0f067..926c3746 100644 --- a/generated/en/make-image/index.html +++ b/generated/en/make-image/index.html @@ -477,7 +477,7 @@

Make your own image

Last update: - August 15, 2024 + November 28, 2024
Created: November 13, 2022 diff --git a/generated/en/search/search_index.json b/generated/en/search/search_index.json index 0971c773..01642050 100644 --- a/generated/en/search/search_index.json +++ b/generated/en/search/search_index.json @@ -1 +1 @@ -{"config":{"indexing":"full","lang":["en","ja","ru"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"BLIKVM Overview BLIKVM is an open-source KVM, it has four versions: v1 CM4, v2 PCIe, v3 HAT and the v4 Allwinner. This device helps to manage servers or workstations remotely, regardless of the health of the operating system or whether one is installed. You can fix any problem, configure the BIOS, and even reinstall the OS using the virtual CD-ROM or Flash Drive. Unlike software-based remote management, you don't need to install any software on the controlled computer, providing non-intrusive control. Here you will find comprehensive information about all aspects of the operation of BLIKVM. Join our BLIKVM Discord Community for Support, FAQ & News! FEATURE BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 /H313 SOC Raspberry CM4 Raspberry CM4 Raspberry 4B Allwinner H616/H313 Supported resolutions 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI Capture TC358743 TC358743 TC358743 MS2131 HDMI Loop Through No No No Yes POE No Yes Yes Yes DC-IN No No No Yes USB-C Power Yes Yes Yes Yes USB Power/Data Splitter Yes Yes(external) Yes Yes Serial Console No Yes Yes Yes ATX controls Yes Yes Yes Yes BIOS controls Yes Yes Yes Yes Open source system Yes Yes Yes Yes Reinstall the controlled computer system Yes Yes Yes Yes FAN Yes(Not support PWM controls) Yes Yes Optional(default with heat sink) Display Module OLED 128x64 white OLED 128x32 white OLED 128x64 white LCD 240x240 color Real Time Clock Yes(DS1307) Yes(PCF8563) Yes(PCF8563) Yes(PCF8563) Case Metallic Black No Metallic Black White Blue Orange(1U rack compatible) Metallic Black(1U rack compatible) Buzzer No No No Yes Custom button No No No Yes Software update Yes Yes Yes Yes 32GB SD Card Yes (OS included) Yes (OS included) Yes (OS included) Yes (OS included) HDMI backpower mitigation No Yes Yes Yes Professional technical support Yes Yes Yes Yes Features Video capture (1080P 60Hz) Keyboard forwarding Mouse forwarding ATX Fan Control Fullscreen mode Paste text from clipboard VPN support Mass Storage Drive (emulate a CD-ROM or Flash Drive) Multiport KVM over IP OLED to display system info, like temp, uptime, IP Password authentication Support multiple languages Wake-on-LAN Guides 1. BLIKVM v1 CM4 version 2. BLIKVM v2 PCIE version 3. BLIKVM v3 HAT version 4. BliKVM v4 Allwinner version","title":"BLIKVM Overview"},{"location":"#blikvm-overview","text":"BLIKVM is an open-source KVM, it has four versions: v1 CM4, v2 PCIe, v3 HAT and the v4 Allwinner. This device helps to manage servers or workstations remotely, regardless of the health of the operating system or whether one is installed. You can fix any problem, configure the BIOS, and even reinstall the OS using the virtual CD-ROM or Flash Drive. Unlike software-based remote management, you don't need to install any software on the controlled computer, providing non-intrusive control. Here you will find comprehensive information about all aspects of the operation of BLIKVM. Join our BLIKVM Discord Community for Support, FAQ & News! FEATURE BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 /H313 SOC Raspberry CM4 Raspberry CM4 Raspberry 4B Allwinner H616/H313 Supported resolutions 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI Capture TC358743 TC358743 TC358743 MS2131 HDMI Loop Through No No No Yes POE No Yes Yes Yes DC-IN No No No Yes USB-C Power Yes Yes Yes Yes USB Power/Data Splitter Yes Yes(external) Yes Yes Serial Console No Yes Yes Yes ATX controls Yes Yes Yes Yes BIOS controls Yes Yes Yes Yes Open source system Yes Yes Yes Yes Reinstall the controlled computer system Yes Yes Yes Yes FAN Yes(Not support PWM controls) Yes Yes Optional(default with heat sink) Display Module OLED 128x64 white OLED 128x32 white OLED 128x64 white LCD 240x240 color Real Time Clock Yes(DS1307) Yes(PCF8563) Yes(PCF8563) Yes(PCF8563) Case Metallic Black No Metallic Black White Blue Orange(1U rack compatible) Metallic Black(1U rack compatible) Buzzer No No No Yes Custom button No No No Yes Software update Yes Yes Yes Yes 32GB SD Card Yes (OS included) Yes (OS included) Yes (OS included) Yes (OS included) HDMI backpower mitigation No Yes Yes Yes Professional technical support Yes Yes Yes Yes","title":"BLIKVM Overview"},{"location":"#features","text":"Video capture (1080P 60Hz) Keyboard forwarding Mouse forwarding ATX Fan Control Fullscreen mode Paste text from clipboard VPN support Mass Storage Drive (emulate a CD-ROM or Flash Drive) Multiport KVM over IP OLED to display system info, like temp, uptime, IP Password authentication Support multiple languages Wake-on-LAN","title":"Features"},{"location":"#guides","text":"1. BLIKVM v1 CM4 version 2. BLIKVM v2 PCIE version 3. BLIKVM v3 HAT version 4. BliKVM v4 Allwinner version","title":"Guides"},{"location":"BLIHAT-Installation/","text":"BLIHAT Installation Guide 1. Unpack and take out the devices Open the protective bag 2. Install the main device Flip to back Open the case Flip to back, unscrew the two screws on the back Open the protective bag and take out the parts Install Micro SD card Install the FFC cable Install the HAT on the Raspberry Pi 4 Install the four Hex Spacers Install the C790 module, use the long screws you just removed Install the audio cable Stick a heat conductive sheet on the back of the Raspberry Pi 4, tear off the protective film of the sheet Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"v3 HAT Illustrated Instructions"},{"location":"BLIHAT-Installation/#blihat-installation-guide","text":"","title":"BLIHAT Installation Guide"},{"location":"BLIHAT-Installation/#1-unpack-and-take-out-the-devices","text":"Open the protective bag","title":"1. Unpack and take out the devices"},{"location":"BLIHAT-Installation/#2-install-the-main-device","text":"Flip to back Open the case Flip to back, unscrew the two screws on the back Open the protective bag and take out the parts Install Micro SD card Install the FFC cable Install the HAT on the Raspberry Pi 4 Install the four Hex Spacers Install the C790 module, use the long screws you just removed Install the audio cable Stick a heat conductive sheet on the back of the Raspberry Pi 4, tear off the protective film of the sheet Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"2. Install the main device"},{"location":"BLIKVM-CM4-guide/","text":"BLIKVM-CM4 version guide Geerling: Engineering Test video BliKVM v1 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM v1 Datasheet Features Video capture (HDMI, support 1080P@60Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Serial console port OLED display Real Time Clock (RTC) FAN Installation requirements If you have an assembly kit, you will need the following things Raspberry CM4 with 1Gb RAM or more. USB-C to USB-A cable. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit (5.1V 3A USB-C, recommended by the Raspberry Pi). Power supply You must use a USB-C to USB-A cable. Using a USB-C to USB-C cable will not work. This is an incompatibility in the hardware design and will be fixed in a later version. Basic setup 1. The SD card preloaded with the factory default image does not require burning. If you need to reflash the system or for DIY purposes, you can follow Flash the memory card or eMMC 2. If you have a non-plug version, refer to the video and instructions below for device installation: Use the provided screwdriver to open the metal casing and remove the PCB motherboard. Install the CM4 onto the PCB motherboard, ensuring that the two rows of card slots are aligned. Apply the thermal conductive silicone pad onto the CM4 main chip to facilitate heat dissipation using the metal casing. The fan is not connected by default as the metal casing provides sufficient heat dissipation. Depending on your CM4 version, selectively install the Wi-Fi antenna. Reassemble the PCB motherboard and the metal casing to complete the installation. Please note that translations might vary depending on context and specific terminology used in technical instructions. Video Guide: Metal case step by step Ortimo: BLIKVM with Raspberry PI CM4 16GB EMMC setup 3. Connect BLIKVM to the computer according to the diagram below: HDMI IN and otg port must be connected to the computer. ATX too, but it\u2019s optional, read below. There should be no USB hub between BLIKVM and the computer, as some UEFI/BIOS cannot detect them at the boot stage. BLIKVM supports 1080p60Hz or lower about HDMI source. Connect Ethernet to the network and PWR IN to the BLIKVM power supply. 4. ATX connection To manage the power of your computer, you will connect CN-ATX port to the computer.The user can use the ATX cable provided with the product to connect the product and the motherboard ATX switch of the controlled computer. The length of the ATX cable is 60CM, you can also use the double female Dupont cables. To accommodate ATX control boards with Ethernet ports, v1 has a dedicated ATX expansion kit available. This kit enables customers to connect the ATX board installed on the chassis panel directly using an Ethernet cable. 5. After all the connecting cables are properly set up, power on the BliKVM until the display screen shows an image, indicating that the device has successfully started. 6. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. As BliKVM v1 also supports PiKVM OS, if your v1 comes with PiKVM as the factory OS, please refer to the documentation for web usage instructions . 7. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 8. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience! Wi-Fi Antenna Connection If your CM4 has Wi-Fi functionality, open the metal casing of v1 and attach the Wi-Fi antenna from the package to the IPX interface on the CM4, as shown by the red box in the diagram below; the installation location on the casing for the antenna is defined as position 11 in the interface layout diagram. Support 1080p60hz HDMI input First in V2.2 version, there is CSI channel switch. This switch is switch 2 csi channels or 4 csi channels. In other versions, the switch is obsolete. Newer keeps the factory state, ignore this switch. Only flip the switch when the device is powered off, otherwise it may cause permanent damage! The four small switches should be up or down at the same time. Product List BLIKVM v1 excluding CM4 Case 1 PCB 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 OLED 1 BLIKVM v1 including CM4102000 Case 1 PCB 1 CM4102000 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 OLED 1 WiFi antenna 1 BLIKVM v1 including CM4002000 Case 1 PCB 1 CM4002000 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 WiFi antenna 1 Buy link Buy v1","title":"BliKVM v1 CM4 Guide"},{"location":"BLIKVM-CM4-guide/#blikvm-cm4-version-guide","text":"Geerling: Engineering Test video BliKVM v1 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM v1 Datasheet","title":"BLIKVM-CM4 version guide"},{"location":"BLIKVM-CM4-guide/#features","text":"Video capture (HDMI, support 1080P@60Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Serial console port OLED display Real Time Clock (RTC) FAN","title":"Features"},{"location":"BLIKVM-CM4-guide/#installation-requirements","text":"If you have an assembly kit, you will need the following things Raspberry CM4 with 1Gb RAM or more. USB-C to USB-A cable. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit (5.1V 3A USB-C, recommended by the Raspberry Pi). Power supply You must use a USB-C to USB-A cable. Using a USB-C to USB-C cable will not work. This is an incompatibility in the hardware design and will be fixed in a later version.","title":"Installation requirements"},{"location":"BLIKVM-CM4-guide/#basic-setup","text":"1. The SD card preloaded with the factory default image does not require burning. If you need to reflash the system or for DIY purposes, you can follow Flash the memory card or eMMC 2. If you have a non-plug version, refer to the video and instructions below for device installation: Use the provided screwdriver to open the metal casing and remove the PCB motherboard. Install the CM4 onto the PCB motherboard, ensuring that the two rows of card slots are aligned. Apply the thermal conductive silicone pad onto the CM4 main chip to facilitate heat dissipation using the metal casing. The fan is not connected by default as the metal casing provides sufficient heat dissipation. Depending on your CM4 version, selectively install the Wi-Fi antenna. Reassemble the PCB motherboard and the metal casing to complete the installation. Please note that translations might vary depending on context and specific terminology used in technical instructions. Video Guide: Metal case step by step Ortimo: BLIKVM with Raspberry PI CM4 16GB EMMC setup 3. Connect BLIKVM to the computer according to the diagram below: HDMI IN and otg port must be connected to the computer. ATX too, but it\u2019s optional, read below. There should be no USB hub between BLIKVM and the computer, as some UEFI/BIOS cannot detect them at the boot stage. BLIKVM supports 1080p60Hz or lower about HDMI source. Connect Ethernet to the network and PWR IN to the BLIKVM power supply. 4. ATX connection To manage the power of your computer, you will connect CN-ATX port to the computer.The user can use the ATX cable provided with the product to connect the product and the motherboard ATX switch of the controlled computer. The length of the ATX cable is 60CM, you can also use the double female Dupont cables. To accommodate ATX control boards with Ethernet ports, v1 has a dedicated ATX expansion kit available. This kit enables customers to connect the ATX board installed on the chassis panel directly using an Ethernet cable. 5. After all the connecting cables are properly set up, power on the BliKVM until the display screen shows an image, indicating that the device has successfully started. 6. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. As BliKVM v1 also supports PiKVM OS, if your v1 comes with PiKVM as the factory OS, please refer to the documentation for web usage instructions . 7. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 8. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience!","title":"Basic setup"},{"location":"BLIKVM-CM4-guide/#wi-fi-antenna-connection","text":"If your CM4 has Wi-Fi functionality, open the metal casing of v1 and attach the Wi-Fi antenna from the package to the IPX interface on the CM4, as shown by the red box in the diagram below; the installation location on the casing for the antenna is defined as position 11 in the interface layout diagram.","title":"Wi-Fi Antenna Connection"},{"location":"BLIKVM-CM4-guide/#support-1080p60hz-hdmi-input","text":"First in V2.2 version, there is CSI channel switch. This switch is switch 2 csi channels or 4 csi channels. In other versions, the switch is obsolete. Newer keeps the factory state, ignore this switch. Only flip the switch when the device is powered off, otherwise it may cause permanent damage! The four small switches should be up or down at the same time.","title":"Support 1080p60hz HDMI input"},{"location":"BLIKVM-CM4-guide/#product-list","text":"BLIKVM v1 excluding CM4 Case 1 PCB 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 OLED 1 BLIKVM v1 including CM4102000 Case 1 PCB 1 CM4102000 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 OLED 1 WiFi antenna 1 BLIKVM v1 including CM4002000 Case 1 PCB 1 CM4002000 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 WiFi antenna 1","title":"Product List"},{"location":"BLIKVM-CM4-guide/#buy-link","text":"Buy v1","title":"Buy link"},{"location":"BLIKVM-HAT-guide/","text":"BLIKVM HAT version guide Introduction BLIKVM hat Video The Raspberry Pi IPKVM HAT is an add-on board for Raspberry Pi 4, made especially for KVM Over IP. The BLIKVM-RPI4 is a Raspberry Pi 4 PoE KVM HAT. This product\u2019s key features include video capture, ATX adapter, PoE, OLED and RTC. The product has a customized metal case to dissipate heat and provide protection for the HAT. The product can be easily installed on a standard 1U rack. The product is currently perfectly compatible with BliKVM image and PiKVM image. Features Video capture (HDMI, support 1080P@50Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Adapter : Control the server power using ATX functions Fullscreen mode Access via Web UI Multi Language switching support PoE support Serial console port OLED display Real Time Clock (RTC) PWM FAN Interface HAT part: HDMI IN ATX Port OLED PoE jumper Raspberry 4B part: SD CARD ACT LED PWR LED USB-PC HDMI 0 HDMI 1 A/V ETH(1000M) & PoE 2x USB 2.0 Ports & 2x USB 3.0 Ports Installation requirements If you have an assembly kit, you will need the following things Raspberry Pi 4B with 1Gb RAM or more. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit & cable(5.1V 3A USB-C, recommended by the Raspberry Pi). Basic setup 1. Flash the memory card or eMMC 2. Build BLIKVM according to the video instructions or review the illustrated instructions : Video Guide: Metal case step by step 3. Install the ATX adapter board The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. Choose one as needed Use Dupont cables to connect ATX adapter board to motherboard and chassis panel. There are clear pin definitions on the board for easy wiring. Mount the ATX adapter board to the case shell Use a RJ45 network cable to connect the board to the CN-ATX interface of the HAT 4. Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the HAT with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 5. Install the USB cable Connect the RPI4 port to the Raspberry Pi 4 Connect the USB port to the controlled computer When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. 6. Test Powered by PoE, the HAT is connected to the router via the network cable The screen displays the current status of the device, including the machine's IP address Access the IP address of the HAT in the browser. Enjoy! Specification HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@50fps. Fixed HDMI back power issue. CN-ATX The CN-ATX interface is connected to the ATX adapter board (an accessory for the HAT) through a network cable, which can turn on, off, and restart the controlled computer. Display A white OLED display with a resolution of 128x32, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. PoE Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A Plug in the PoE jumper cap to enable PoE power supply FAN The IPKVM HAT is fitted with a small fan that is controlled by your Raspberry Pi via GPIO12. Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi via I2C. The coin cell battery is installed under the HDMI IN module. Accessories ATX adapter board This board is connected to the switch port on the motherboard of the controlled computer with DuPont cables. The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. USB/PWR splitter Connect the RPI4 port to your Raspberry Pi 4. Connect the USB port to the controlled computer. When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. Metal case The metal case protects the HAT and improve heat dissipation. There are clear port markings on the case. The case can be easily installed on a standard 1U rack. List Product List Raspberry Pi IPKVM HAT 1 ATX adapter board 1 USB/PWR splitter 1 HDMI pass-through EDID emulator 1 Metal case 1 32G TF card 1 USB Type-C to USB Type-C Cable 30cm 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 List of items prepared by the user Raspberry Pi 4 1 RJ45 network cable 2 USB Type-A to USB Type-C Cable 2 HDMI cable 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1 Buy link Buy v3","title":"BliKVM v3 HAT Guide"},{"location":"BLIKVM-HAT-guide/#blikvm-hat-version-guide","text":"","title":"BLIKVM HAT version guide"},{"location":"BLIKVM-HAT-guide/#introduction","text":"BLIKVM hat Video The Raspberry Pi IPKVM HAT is an add-on board for Raspberry Pi 4, made especially for KVM Over IP. The BLIKVM-RPI4 is a Raspberry Pi 4 PoE KVM HAT. This product\u2019s key features include video capture, ATX adapter, PoE, OLED and RTC. The product has a customized metal case to dissipate heat and provide protection for the HAT. The product can be easily installed on a standard 1U rack. The product is currently perfectly compatible with BliKVM image and PiKVM image.","title":"Introduction"},{"location":"BLIKVM-HAT-guide/#features","text":"Video capture (HDMI, support 1080P@50Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Adapter : Control the server power using ATX functions Fullscreen mode Access via Web UI Multi Language switching support PoE support Serial console port OLED display Real Time Clock (RTC) PWM FAN","title":"Features"},{"location":"BLIKVM-HAT-guide/#interface","text":"HAT part: HDMI IN ATX Port OLED PoE jumper Raspberry 4B part: SD CARD ACT LED PWR LED USB-PC HDMI 0 HDMI 1 A/V ETH(1000M) & PoE 2x USB 2.0 Ports & 2x USB 3.0 Ports","title":"Interface"},{"location":"BLIKVM-HAT-guide/#installation-requirements","text":"If you have an assembly kit, you will need the following things Raspberry Pi 4B with 1Gb RAM or more. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit & cable(5.1V 3A USB-C, recommended by the Raspberry Pi).","title":"Installation requirements"},{"location":"BLIKVM-HAT-guide/#basic-setup","text":"1. Flash the memory card or eMMC 2. Build BLIKVM according to the video instructions or review the illustrated instructions : Video Guide: Metal case step by step 3. Install the ATX adapter board The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. Choose one as needed Use Dupont cables to connect ATX adapter board to motherboard and chassis panel. There are clear pin definitions on the board for easy wiring. Mount the ATX adapter board to the case shell Use a RJ45 network cable to connect the board to the CN-ATX interface of the HAT 4. Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the HAT with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 5. Install the USB cable Connect the RPI4 port to the Raspberry Pi 4 Connect the USB port to the controlled computer When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. 6. Test Powered by PoE, the HAT is connected to the router via the network cable The screen displays the current status of the device, including the machine's IP address Access the IP address of the HAT in the browser. Enjoy!","title":"Basic setup"},{"location":"BLIKVM-HAT-guide/#specification","text":"HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@50fps. Fixed HDMI back power issue. CN-ATX The CN-ATX interface is connected to the ATX adapter board (an accessory for the HAT) through a network cable, which can turn on, off, and restart the controlled computer. Display A white OLED display with a resolution of 128x32, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. PoE Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A Plug in the PoE jumper cap to enable PoE power supply FAN The IPKVM HAT is fitted with a small fan that is controlled by your Raspberry Pi via GPIO12. Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi via I2C. The coin cell battery is installed under the HDMI IN module.","title":"Specification"},{"location":"BLIKVM-HAT-guide/#accessories","text":"","title":"Accessories"},{"location":"BLIKVM-HAT-guide/#atx-adapter-board","text":"This board is connected to the switch port on the motherboard of the controlled computer with DuPont cables. The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket.","title":"ATX adapter board"},{"location":"BLIKVM-HAT-guide/#usbpwr-splitter","text":"Connect the RPI4 port to your Raspberry Pi 4. Connect the USB port to the controlled computer. When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply.","title":"USB/PWR splitter"},{"location":"BLIKVM-HAT-guide/#hdmi-pass-through-edid-emulator","text":"If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer.","title":"HDMI pass-through EDID emulator"},{"location":"BLIKVM-HAT-guide/#metal-case","text":"The metal case protects the HAT and improve heat dissipation. There are clear port markings on the case. The case can be easily installed on a standard 1U rack.","title":"Metal case"},{"location":"BLIKVM-HAT-guide/#list","text":"","title":"List"},{"location":"BLIKVM-HAT-guide/#product-list","text":"Raspberry Pi IPKVM HAT 1 ATX adapter board 1 USB/PWR splitter 1 HDMI pass-through EDID emulator 1 Metal case 1 32G TF card 1 USB Type-C to USB Type-C Cable 30cm 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Phillips screwdriver 1 Cross Wrench Sleeve 1","title":"Product List"},{"location":"BLIKVM-HAT-guide/#list-of-items-prepared-by-the-user","text":"Raspberry Pi 4 1 RJ45 network cable 2 USB Type-A to USB Type-C Cable 2 HDMI cable 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"List of items prepared by the user"},{"location":"BLIKVM-HAT-guide/#buy-link","text":"Buy v3","title":"Buy link"},{"location":"BLIKVM-PCIE-guide/","text":"BLIKVM PCIe Introduction BLIKVM PCIe is a PCIe add-in card based on Raspberry Pi CM4 for KVM Over IP. This product\u2019s key features include video capture, ATX controller, PoE, OLED , UART and RTC. The card has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. The product is currently perfectly compatible with blikvm image and pikvm image. Installation requirements You will need the following things Raspberry Pi CM4(if you order PCIe card only). PoE-sourcing equipment or 5V/3A USB adapter. CR1220 coin cell battery. Features Video capture (HDMI, support 1080P@60Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE Serial console port OLED display Real Time Clock (RTC) PWM Fan Basic setup 1. If you have an assembly kit, Flash the memory card or eMMC 2.Build BLIKVM according to the illustrated instructions : Geerling: Engineering Test video Craft Computing: Never Pay For IPMI Again - BliKVM Review Specification hardware feature list 1 HDMI in 2 USB-PC port 3 Power Input 5V 3A 4 RJ45 100M Ethernet port & PoE 5 ATX control port 6 OLED Display 7 PWM FAN 8 BOOT 9 REAL TIME CLOCK(RTC) 10 UART port 11 USB-PC port HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@60fps. Fixed HDMI back power issue. USB-PC The BLIKVM PCIe card provides two USB interfaces, one is PC-IN (type c interface) and the other is USB-PC2 (pin interface). The purpose of these two interfaces is to connect to the USB of the controlled computer, used to control the mouse and keyboard. At the same time, only one interface can be used. The purpose of designing two interfaces is to directly use USB PC2 when the user's PC host has a row pin USB interface, which will make the wiring more concise. POWER-IN When using PoE power supply, there is no need to connect the PWR-IN port. When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. ETHERNET-PoE Gigabit Ethernet port Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A ATX-Connecter Connect to power control interface on the motherboard of the controlled computer with DuPont cables. It can turn on, off, and restart the controlled computer. The pin is defined on the printing of the PCIe board, BTN means button. According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the PCIe board. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and PCIe. See the following figure for the connection relationship\uff1a OLED Display A white OLED display with a resolution of 128x64, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. FAN The Card HAT is fitted with a small fan that is controlled by your Raspberry Pi CM4 via GPIO12. BOOT Fit jumper to disable eMMC Boot Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi CM4 via I2C. The CR1220 battery is installed under the HDMI IN module. UART Connect the serial port to debug your Raspberry Pi CM4. The uart of Raspberry Pi CM4. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. Connect serial cable wires to G T R connectors on the PCIe board. NOTE: black wire = Ground, whiTe = Tx, and gReen = Rx; For specific methods, please refer to this document . Accessories HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. VGA-HDMI module When your device does not have an HDMI output interface, you can use a VGA to HDMI module. USB to TTL module Connect your computer usb interface with the serial port of BLIKVM to debug your Raspberry Pi CM4. Fan Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card. Dimensions Test Video BLIKVM hardware PCIe version is tested wonderful based on pikvm software. Notes To prevent the CM4 module from contacting the SD card holder, do not remove the insulating tape List Product List BLIKVM PCIe card version 1 BLIKVM PCIe add-in card 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 BLIKVM PCIe plug-n-play version 1 BLIKVM PCIe add-in card 1 CM4 102000 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 List of items prepared by the user Raspberry Pi CM4(if you order PCIe card only) 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1 Buy link Buy v2 3D printable case A simple snap fit case for the PCIe. Download file","title":"BliKVM v2 PCIe Guide"},{"location":"BLIKVM-PCIE-guide/#blikvm-pcie","text":"","title":"BLIKVM PCIe"},{"location":"BLIKVM-PCIE-guide/#introduction","text":"BLIKVM PCIe is a PCIe add-in card based on Raspberry Pi CM4 for KVM Over IP. This product\u2019s key features include video capture, ATX controller, PoE, OLED , UART and RTC. The card has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. The product is currently perfectly compatible with blikvm image and pikvm image.","title":"Introduction"},{"location":"BLIKVM-PCIE-guide/#installation-requirements","text":"You will need the following things Raspberry Pi CM4(if you order PCIe card only). PoE-sourcing equipment or 5V/3A USB adapter. CR1220 coin cell battery.","title":"Installation requirements"},{"location":"BLIKVM-PCIE-guide/#features","text":"Video capture (HDMI, support 1080P@60Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE Serial console port OLED display Real Time Clock (RTC) PWM Fan","title":"Features"},{"location":"BLIKVM-PCIE-guide/#basic-setup","text":"1. If you have an assembly kit, Flash the memory card or eMMC 2.Build BLIKVM according to the illustrated instructions : Geerling: Engineering Test video Craft Computing: Never Pay For IPMI Again - BliKVM Review","title":"Basic setup"},{"location":"BLIKVM-PCIE-guide/#specification","text":"hardware feature list 1 HDMI in 2 USB-PC port 3 Power Input 5V 3A 4 RJ45 100M Ethernet port & PoE 5 ATX control port 6 OLED Display 7 PWM FAN 8 BOOT 9 REAL TIME CLOCK(RTC) 10 UART port 11 USB-PC port HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@60fps. Fixed HDMI back power issue. USB-PC The BLIKVM PCIe card provides two USB interfaces, one is PC-IN (type c interface) and the other is USB-PC2 (pin interface). The purpose of these two interfaces is to connect to the USB of the controlled computer, used to control the mouse and keyboard. At the same time, only one interface can be used. The purpose of designing two interfaces is to directly use USB PC2 when the user's PC host has a row pin USB interface, which will make the wiring more concise. POWER-IN When using PoE power supply, there is no need to connect the PWR-IN port. When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. ETHERNET-PoE Gigabit Ethernet port Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A ATX-Connecter Connect to power control interface on the motherboard of the controlled computer with DuPont cables. It can turn on, off, and restart the controlled computer. The pin is defined on the printing of the PCIe board, BTN means button. According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the PCIe board. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and PCIe. See the following figure for the connection relationship\uff1a OLED Display A white OLED display with a resolution of 128x64, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. FAN The Card HAT is fitted with a small fan that is controlled by your Raspberry Pi CM4 via GPIO12. BOOT Fit jumper to disable eMMC Boot Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi CM4 via I2C. The CR1220 battery is installed under the HDMI IN module. UART Connect the serial port to debug your Raspberry Pi CM4. The uart of Raspberry Pi CM4. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. Connect serial cable wires to G T R connectors on the PCIe board. NOTE: black wire = Ground, whiTe = Tx, and gReen = Rx; For specific methods, please refer to this document .","title":"Specification"},{"location":"BLIKVM-PCIE-guide/#accessories","text":"HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. VGA-HDMI module When your device does not have an HDMI output interface, you can use a VGA to HDMI module. USB to TTL module Connect your computer usb interface with the serial port of BLIKVM to debug your Raspberry Pi CM4. Fan Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card.","title":"Accessories"},{"location":"BLIKVM-PCIE-guide/#dimensions","text":"","title":"Dimensions"},{"location":"BLIKVM-PCIE-guide/#test-video","text":"BLIKVM hardware PCIe version is tested wonderful based on pikvm software.","title":"Test Video"},{"location":"BLIKVM-PCIE-guide/#notes","text":"To prevent the CM4 module from contacting the SD card holder, do not remove the insulating tape","title":"Notes"},{"location":"BLIKVM-PCIE-guide/#list","text":"","title":"List"},{"location":"BLIKVM-PCIE-guide/#product-list","text":"BLIKVM PCIe card version 1 BLIKVM PCIe add-in card 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 BLIKVM PCIe plug-n-play version 1 BLIKVM PCIe add-in card 1 CM4 102000 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1","title":"Product List"},{"location":"BLIKVM-PCIE-guide/#list-of-items-prepared-by-the-user","text":"Raspberry Pi CM4(if you order PCIe card only) 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"List of items prepared by the user"},{"location":"BLIKVM-PCIE-guide/#buy-link","text":"Buy v2","title":"Buy link"},{"location":"BLIKVM-PCIE-guide/#3d-printable-case","text":"A simple snap fit case for the PCIe. Download file","title":"3D printable case"},{"location":"BLIKVM-PCIe-installation/","text":"BLIKVM PCIe CM4 Installation Guide 1. Unpack and take out the devices Product List 2. Install the main device Install CM4 and 4 Hex spacers (This article takes CM4 lite as an example, using the image in the Micro SD card, CM4 eMMC user need to burn the image by yourself.)Stick a heat conductive sheet on the top of CM4 , tear off the protective film of the sheet. The main device installation is complete. 3. Connect USB and ATX The motherboard used in this article is Asus H520M-E, the interface definition of different motherboards may be different, please refer to your motherboard manual. 4. Connect OLED The OLED you received does not have a bracket installed. Please refer to the picture for installation. In addition, OLED support is made of acrylic material, which needs to be used after removing the protective film on the surface. The above is the installation steps, and the effect of not tearing the film is as follows. In actual use, please remove the protective film. 5. Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the product with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 6. Connect the network cable Gigabit Ethernet port standard: IEEE 802.3af PoE input voltage:37v-57v. When using PoE power supply, there is no need to connect the PWR-IN port. 7. Connect PWR-IN When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. 8. Test OLED screen showing device IP and other information. Access the IP address in browser. After passing the test, install the product into the computer case. 9. Install the product into the computer case Disconnect power and wiring, install the product on the motherboard, and reconnect the cables after installation is complete. The color of ATX cable received in different batches may be different. Please directly refer to the pin definition for connection Enjoy! Appendix 1. Install a low profile PCIe I/O bracket Note Appendix 2. Install the cooling fan Usually the metal heatsink is sufficient, the cooling fan is not necessary. The cooling fan is controlled by CM4 via GPIO12. Appendix 3. Install wifi antenna Note","title":"v2 PCIe Illustrated Instructions"},{"location":"BLIKVM-PCIe-installation/#blikvm-pcie-cm4-installation-guide","text":"","title":"BLIKVM PCIe CM4 Installation Guide"},{"location":"BLIKVM-PCIe-installation/#1-unpack-and-take-out-the-devices","text":"Product List","title":"1. Unpack and take out the devices"},{"location":"BLIKVM-PCIe-installation/#2-install-the-main-device","text":"Install CM4 and 4 Hex spacers (This article takes CM4 lite as an example, using the image in the Micro SD card, CM4 eMMC user need to burn the image by yourself.)Stick a heat conductive sheet on the top of CM4 , tear off the protective film of the sheet. The main device installation is complete.","title":"2. Install the main device"},{"location":"BLIKVM-PCIe-installation/#3-connect-usb-and-atx","text":"The motherboard used in this article is Asus H520M-E, the interface definition of different motherboards may be different, please refer to your motherboard manual.","title":"3. Connect USB and ATX"},{"location":"BLIKVM-PCIe-installation/#4-connect-oled","text":"The OLED you received does not have a bracket installed. Please refer to the picture for installation. In addition, OLED support is made of acrylic material, which needs to be used after removing the protective film on the surface. The above is the installation steps, and the effect of not tearing the film is as follows. In actual use, please remove the protective film.","title":"4. Connect OLED"},{"location":"BLIKVM-PCIe-installation/#5-connect-the-hdmi-cable","text":"Connect the HDMI output port of the computer directly to the HDMI IN port of the product with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer.","title":"5. Connect the HDMI cable"},{"location":"BLIKVM-PCIe-installation/#6-connect-the-network-cable","text":"Gigabit Ethernet port standard: IEEE 802.3af PoE input voltage:37v-57v. When using PoE power supply, there is no need to connect the PWR-IN port.","title":"6. Connect the network cable"},{"location":"BLIKVM-PCIe-installation/#7-connect-pwr-in","text":"When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply.","title":"7. Connect PWR-IN"},{"location":"BLIKVM-PCIe-installation/#8-test","text":"OLED screen showing device IP and other information. Access the IP address in browser. After passing the test, install the product into the computer case.","title":"8. Test"},{"location":"BLIKVM-PCIe-installation/#9-install-the-product-into-the-computer-case","text":"Disconnect power and wiring, install the product on the motherboard, and reconnect the cables after installation is complete. The color of ATX cable received in different batches may be different. Please directly refer to the pin definition for connection Enjoy!","title":"9. Install the product into the computer case"},{"location":"BLIKVM-PCIe-installation/#appendix-1-install-a-low-profile-pcie-io-bracket","text":"Note","title":"Appendix 1. Install a low profile PCIe I/O bracket"},{"location":"BLIKVM-PCIe-installation/#appendix-2-install-the-cooling-fan","text":"Usually the metal heatsink is sufficient, the cooling fan is not necessary. The cooling fan is controlled by CM4 via GPIO12.","title":"Appendix 2. Install the cooling fan"},{"location":"BLIKVM-PCIe-installation/#appendix-3-install-wifi-antenna","text":"Note","title":"Appendix 3. Install wifi antenna"},{"location":"BliKVM-v4-guide/","text":"BliKVM v4 Allwinner BliKVM v4 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM V4 Datasheet Craft Computing: Goodbye IPMI - Blicube BliKVM V4 Review Lawrence Systems: Blicube BliKVM V4: Is This the Best Linux IP KVM Yet? RainCat: How to install PiKVM on BliKVM v4 Allwinner Features Video capture (HDMI, support 4K@30Hz input) Keyboard forwarding Mouse forwarding HDMI video loop through ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE & DC Support WiFi Serial console port 1.33 inch color display Real Time Clock (RTC) HDMI input supported resolution types Installation Requirements In addition to the v4 kit, you will need the following equipment: Power adapter (5V 3A, USB-C port, or 12V 2A DC port). If you plan to use PoE (Power over Ethernet) or if the USB ports on your controlled computers provide sufficient power, a separate power adapter is not required. HDMI cables (at least one). If you also need to use the HDMI loop-out interface, you will need two cables. Ethernet cable(s) (provide based on your requirements). One cable is required for using the ATX power switch function, and one cable is required for using the Ethernet connection. USB-C to USB-A cable (for mouse and keyboard data transmission). Terminal Upgrade Notice! Before upgrading, execute the following command, otherwise, after running apt-get update and apt-get upgrade, the image will fail to start. apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64 Video Guide: Unpacking and connecting case step by step Installation Steps 1. Open the v4 kit package and connect the BliKVM to the controlled computer according to the connection diagram shown below: ATX Connection Please refer to the ATX Connection Guide . 2. Once all the cables are connected, power on the BliKVM. Wait until the display shows the interface, indicating that the device has started up successfully. 3. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. 4. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 5. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience! Video Mode v4 supports a maximum video input of 4K30Hz, and the default transmission resolution is 1920x1080. Packing List BLIKVM v4 1 WiFi Antenna 1 ATX adapter board 1 ATX Dupont Cables 8pin Male to Male 60cm 1 ATX Dupont Cables 8pin Male to Female 60cm 1 1U Rack Mounting Ears 2 M2.5x5 Screws 8 Silicone Bumper Pellets 1 Serial Console Access via the 5V Port The 5V port can be used both for power supply and serial console access at the same time. The default baud rate is 115200. There is an onboard CH341-based USB to UART converter present inside BliKVM v4 which is connected to UART0 of the mCore-H616 SoC , so you can connect a USB port of a PC to the 5V port without an external UART and a USB-C to dupont adapter. PC USB port current output Be careful when trying to use the 5V port because a PC USB port alone may not be able to provide 3A (5V) which is a documented requirement for the board to work. Either use a 12V 2A DC port at the same time as using the 5V port for serial communication without a USB Splitter board, or use the splitter board to split out the VCC pin and use a separate 5V 3A power supply to provide power to the 5V port's VCC pin. Likewise, when disconnecting a cable from the 12V 2A DC port while BliKVM is powered on, make sure to disconnect the cable from the 5V port first (because that will become the power source for BliKVM v4 after the 12V 2A source is disconnected unless a splitter is used). You should see something like this in your host kernel log (if you are using a Linux-based OS) when attaching a USB cable to the 5V port of BliKVM v4: usb 1-1.2: new full-speed USB device number 12 using xhci_hcd usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34 usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.2: Product: USB Serial ch341 1-1.2:1.0: ch341-uart converter detected usb 1-1.2: ch341-uart converter now attached to ttyUSB0 Accessing this port can then be done using GNU screen or TIO : tio /dev/ttyUSB0 mangopimcore login: blikvm # ... If you need to check how much data is received over UART0 you can do this by looking at the counters exposed via proc as follows (the rx counter should increase when the data is sent from an external host if the built-in USB to UART converter is working properly): root@mangopimcore:~# grep '0: uart' /proc/tty/driver/serial 0: uart:16550A mmio:0x05000000 irq:284 tx:20306 rx:40 pe:1 RTS|DTR Dev If you want to develop or port software on v4 hardware yourself, you can refer to this hardware resource description . Buy link Buy v4","title":"BliKVM v4 Allwinner Guide"},{"location":"BliKVM-v4-guide/#blikvm-v4-allwinner","text":"BliKVM v4 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM V4 Datasheet Craft Computing: Goodbye IPMI - Blicube BliKVM V4 Review Lawrence Systems: Blicube BliKVM V4: Is This the Best Linux IP KVM Yet? RainCat: How to install PiKVM on BliKVM v4 Allwinner","title":"BliKVM v4 Allwinner"},{"location":"BliKVM-v4-guide/#features","text":"Video capture (HDMI, support 4K@30Hz input) Keyboard forwarding Mouse forwarding HDMI video loop through ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE & DC Support WiFi Serial console port 1.33 inch color display Real Time Clock (RTC) HDMI input supported resolution types","title":"Features"},{"location":"BliKVM-v4-guide/#installation-requirements","text":"In addition to the v4 kit, you will need the following equipment: Power adapter (5V 3A, USB-C port, or 12V 2A DC port). If you plan to use PoE (Power over Ethernet) or if the USB ports on your controlled computers provide sufficient power, a separate power adapter is not required. HDMI cables (at least one). If you also need to use the HDMI loop-out interface, you will need two cables. Ethernet cable(s) (provide based on your requirements). One cable is required for using the ATX power switch function, and one cable is required for using the Ethernet connection. USB-C to USB-A cable (for mouse and keyboard data transmission). Terminal Upgrade Notice! Before upgrading, execute the following command, otherwise, after running apt-get update and apt-get upgrade, the image will fail to start. apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64 Video Guide: Unpacking and connecting case step by step","title":"Installation Requirements"},{"location":"BliKVM-v4-guide/#installation-steps","text":"1. Open the v4 kit package and connect the BliKVM to the controlled computer according to the connection diagram shown below: ATX Connection Please refer to the ATX Connection Guide . 2. Once all the cables are connected, power on the BliKVM. Wait until the display shows the interface, indicating that the device has started up successfully. 3. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. 4. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 5. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience!","title":"Installation Steps"},{"location":"BliKVM-v4-guide/#video-mode","text":"v4 supports a maximum video input of 4K30Hz, and the default transmission resolution is 1920x1080.","title":"Video Mode"},{"location":"BliKVM-v4-guide/#packing-list","text":"BLIKVM v4 1 WiFi Antenna 1 ATX adapter board 1 ATX Dupont Cables 8pin Male to Male 60cm 1 ATX Dupont Cables 8pin Male to Female 60cm 1 1U Rack Mounting Ears 2 M2.5x5 Screws 8 Silicone Bumper Pellets 1","title":"Packing List"},{"location":"BliKVM-v4-guide/#serial-console-access-via-the-5v-port","text":"The 5V port can be used both for power supply and serial console access at the same time. The default baud rate is 115200. There is an onboard CH341-based USB to UART converter present inside BliKVM v4 which is connected to UART0 of the mCore-H616 SoC , so you can connect a USB port of a PC to the 5V port without an external UART and a USB-C to dupont adapter. PC USB port current output Be careful when trying to use the 5V port because a PC USB port alone may not be able to provide 3A (5V) which is a documented requirement for the board to work. Either use a 12V 2A DC port at the same time as using the 5V port for serial communication without a USB Splitter board, or use the splitter board to split out the VCC pin and use a separate 5V 3A power supply to provide power to the 5V port's VCC pin. Likewise, when disconnecting a cable from the 12V 2A DC port while BliKVM is powered on, make sure to disconnect the cable from the 5V port first (because that will become the power source for BliKVM v4 after the 12V 2A source is disconnected unless a splitter is used). You should see something like this in your host kernel log (if you are using a Linux-based OS) when attaching a USB cable to the 5V port of BliKVM v4: usb 1-1.2: new full-speed USB device number 12 using xhci_hcd usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34 usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.2: Product: USB Serial ch341 1-1.2:1.0: ch341-uart converter detected usb 1-1.2: ch341-uart converter now attached to ttyUSB0 Accessing this port can then be done using GNU screen or TIO : tio /dev/ttyUSB0 mangopimcore login: blikvm # ... If you need to check how much data is received over UART0 you can do this by looking at the counters exposed via proc as follows (the rx counter should increase when the data is sent from an external host if the built-in USB to UART converter is working properly): root@mangopimcore:~# grep '0: uart' /proc/tty/driver/serial 0: uart:16550A mmio:0x05000000 irq:284 tx:20306 rx:40 pe:1 RTS|DTR","title":"Serial Console Access via the 5V Port"},{"location":"BliKVM-v4-guide/#dev","text":"If you want to develop or port software on v4 hardware yourself, you can refer to this hardware resource description .","title":"Dev"},{"location":"BliKVM-v4-guide/#buy-link","text":"Buy v4","title":"Buy link"},{"location":"Datasheet-BliKVM-v4/","text":"BliKVM v4 Allwinner (H616/H313 SOC) BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! Connectivity Diagram 1 USB 2.0 port 10 Antenna interface 2 Power Input 5V 3A & UART 11 RJ45 100M Ethernet port & PoE 3 RJ45 ATX control port 12 Display 1.33 inch LCD 4 HDMI video loop through port 13 Power LED (red) 5 USB-PC port 14 User defined button SW1 6 Power Input 12V 2A 5.5*2.1mm 15 ACT LED (green) 7 HDMI video input port 16 Display ON/OFF button 8 HDMI input status LED (green) 17 Micro SD card slot 9 HDMI output status LED (yellow) Specifications Parameter name Characteristics Power 5V 3A 5V port, USB-PC port 12V 2A 12V port PoE Power over Ethernet (IEEE802.3af compliant) 48V DC Connectivity/Interfaces HDMI-IN HDMI video input port HDMI-OUT HDMI video loop through port USB-PC Keyboard, mouse, mass storage, and other external device emulation) ATX Turn on/off or restart the controlled computer WiFi & Bluetooth IEEE802.11 b/g/n + BLE4.2 Micro SD card slot Persistent storage for OS and your data 5V port 5V 3A power or serial console management port Displays and indicators LED indicators Power LED, ACT LED, HDMI input status LED (green)\uff0c HDMI output status LED (yellow) LCD display LCD 240x240 1.33 inch User defined button SW1 Buzzer Find me Video Supported resolutions Up to 4k@30Hz Video compression methods MJPEG Core Chip ALLWINNER H616/H313 RAM 1GB Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 100 (L) x 134 (W) x 44.4 (H) mm Weight 0.45 kg BLIKVM CM4 version OLED display The product comes standard with a monochrome OLED display with a resolution of 128x64, and the chip is SSD1306. The user connects the display to the product with the wiring of the display. The module is connected to CM4 through the I^2^C interface. The wiring definition is shown in the following table. This is a library for the monochrome OLEDs based on SSD1306 drivers. Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C) Dimensions Schematic Diagram","title":"BliKVM v4 Allwinner (H616/H313 SOC)"},{"location":"Datasheet-BliKVM-v4/#blikvm-v4-allwinner-h616h313-soc","text":"BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals!","title":"BliKVM v4 Allwinner (H616/H313 SOC)"},{"location":"Datasheet-BliKVM-v4/#connectivity-diagram","text":"1 USB 2.0 port 10 Antenna interface 2 Power Input 5V 3A & UART 11 RJ45 100M Ethernet port & PoE 3 RJ45 ATX control port 12 Display 1.33 inch LCD 4 HDMI video loop through port 13 Power LED (red) 5 USB-PC port 14 User defined button SW1 6 Power Input 12V 2A 5.5*2.1mm 15 ACT LED (green) 7 HDMI video input port 16 Display ON/OFF button 8 HDMI input status LED (green) 17 Micro SD card slot 9 HDMI output status LED (yellow)","title":"Connectivity Diagram"},{"location":"Datasheet-BliKVM-v4/#specifications","text":"Parameter name Characteristics Power 5V 3A 5V port, USB-PC port 12V 2A 12V port PoE Power over Ethernet (IEEE802.3af compliant) 48V DC Connectivity/Interfaces HDMI-IN HDMI video input port HDMI-OUT HDMI video loop through port USB-PC Keyboard, mouse, mass storage, and other external device emulation) ATX Turn on/off or restart the controlled computer WiFi & Bluetooth IEEE802.11 b/g/n + BLE4.2 Micro SD card slot Persistent storage for OS and your data 5V port 5V 3A power or serial console management port Displays and indicators LED indicators Power LED, ACT LED, HDMI input status LED (green)\uff0c HDMI output status LED (yellow) LCD display LCD 240x240 1.33 inch User defined button SW1 Buzzer Find me Video Supported resolutions Up to 4k@30Hz Video compression methods MJPEG Core Chip ALLWINNER H616/H313 RAM 1GB Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 100 (L) x 134 (W) x 44.4 (H) mm Weight 0.45 kg BLIKVM CM4 version OLED display The product comes standard with a monochrome OLED display with a resolution of 128x64, and the chip is SSD1306. The user connects the display to the product with the wiring of the display. The module is connected to CM4 through the I^2^C interface. The wiring definition is shown in the following table. This is a library for the monochrome OLEDs based on SSD1306 drivers. Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C)","title":"Specifications"},{"location":"Datasheet-BliKVM-v4/#dimensions-schematic-diagram","text":"","title":"Dimensions Schematic Diagram"},{"location":"Dev-BliKVM-v4-Allwinner/","text":"Dev BliKVM v4 Allwinner (H616/H313 SOC) BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! System Block Diagram Functional Module Panel Function Pin Description Button SW1 GPIOI1(257) Press for high level Button SW1 GPIOI2(258) Press for high level LED ACT GPIOI5(261) Low level enable LED LED PWR 3V3 PWR LED is always on after power on ATX Function Pin Description LED-PWR GPIOH10(234) Light on for high level LED-HDD GPIOH9(233) Light on for high level SW-PWR GPIOH4(228) High level enable SW-RST GPIOI16(272) High level enable BUZZER Function Pin Description Buzzer GPIOI15(271) High level enable FAN Function Pin Description Fan GPIOI13(269) High level enable LCD Display 1.33-inch LCD display module, driver chip ST7789, resolution 240x240. Function Pin Description LCD_EN GPIOI4(260) Backlight high level enable LCD_RST GPIOI6(262) Reset Low level enable LCD_DC GPIOI3(259) Data/command control pin SPI1_CS GPIOH5 SPI1_CLK GPIOH6 SPI1_MOSI GPIOH7 GND GND 3V3 3V3","title":"v4 Allwinner Dev Guide"},{"location":"Dev-BliKVM-v4-Allwinner/#dev-blikvm-v4-allwinner-h616h313-soc","text":"BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals!","title":"Dev BliKVM v4 Allwinner (H616/H313 SOC)"},{"location":"Dev-BliKVM-v4-Allwinner/#system-block-diagram","text":"","title":"System Block Diagram"},{"location":"Dev-BliKVM-v4-Allwinner/#functional-module","text":"","title":"Functional Module"},{"location":"Dev-BliKVM-v4-Allwinner/#panel","text":"Function Pin Description Button SW1 GPIOI1(257) Press for high level Button SW1 GPIOI2(258) Press for high level LED ACT GPIOI5(261) Low level enable LED LED PWR 3V3 PWR LED is always on after power on","title":"Panel"},{"location":"Dev-BliKVM-v4-Allwinner/#atx","text":"Function Pin Description LED-PWR GPIOH10(234) Light on for high level LED-HDD GPIOH9(233) Light on for high level SW-PWR GPIOH4(228) High level enable SW-RST GPIOI16(272) High level enable","title":"ATX"},{"location":"Dev-BliKVM-v4-Allwinner/#buzzer","text":"Function Pin Description Buzzer GPIOI15(271) High level enable","title":"BUZZER"},{"location":"Dev-BliKVM-v4-Allwinner/#fan","text":"Function Pin Description Fan GPIOI13(269) High level enable","title":"FAN"},{"location":"Dev-BliKVM-v4-Allwinner/#lcd-display","text":"1.33-inch LCD display module, driver chip ST7789, resolution 240x240. Function Pin Description LCD_EN GPIOI4(260) Backlight high level enable LCD_RST GPIOI6(262) Reset Low level enable LCD_DC GPIOI3(259) Data/command control pin SPI1_CS GPIOH5 SPI1_CLK GPIOH6 SPI1_MOSI GPIOH7 GND GND 3V3 3V3","title":"LCD Display"},{"location":"Expand_Filesystem/","text":"Expand Filesystem If you find that the free space of the raspberry pi SD card or eMMC is smaller than the capacity of the actual SD card or eMMC, you need to do the following to expand the raspberry pi. If you find that the system does not have the raspi config tool, you can use Method 2 (use the GParted partition tool). Method 1: Use raspi-config tool If you are using a mirror after June 2023 and have added a third read-write partition, this method is no longer applicable. Please refer to method 2 and method 3. 1. Open raspi-config. sudo raspi-config 2. Choose Advancd Options\uff1a 3. Choose Expand Filesystem\uff1a 4. Ok: 5. Execute the command resize2fs /dev/mmcblk0p2 in the terminal to see that the SD card has been successfully expanded. Method 2: Use GParted tool 1. Connect the SD card or EMMc that has burned the image to the computer through USB. Take the GParted partition tool on Linux as an example. Other platforms also have similar partition tools. Open GParted software and select SD card: 2. By observing the partition of the SD card in the above figure, we can find that 2.01GB and 21.87GB of space are unused before and after the sdb3 partition, which is the space we want to expand. Select the sdb3 partition and click Resize. 3. You can drag the white partition of sdb3 to the leftmost and rightmost, or fill in 25958 with \"Previous Free Space\" as \"0\" and \"New Size\" as \"Maximum Size\", and then click Resize in the lower right corner. Then click OK to see that all unused space of sd has been used. 4. Insert the SD card into the device and start it. Method 3: Use script If you are using a BliKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand.sh on any path, and write the following content to expand.sh. If your hardware is v1 , v2 or v3 , use: #!/bin/bash set -x resize_mmcblk0p3 () { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100 % resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" If your hardware is v4 , use: #!/bin/bash set -x resize_mmcblk0p1 () { echo \"Resizing mmcblk0p1 partition...\" parted /dev/mmcblk0 resizepart 1 100 % resize2fs /dev/mmcblk0p1 echo \"mmcblk0p1 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p1 echo \"Partition resizing completed.\" If you are using a PiKVM image, you can run the script below on the KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand.sh on any path, and write the following content to expand.sh #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab ; then part = $( grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}' ) # shellcheck disable=SC2206 splitted =( ${ part //=/ } ) if [ \" ${ splitted [0] } \" == LABEL ] ; then label = ${ splitted [1] } part = $( blkid -c /dev/null -L \" $label \" ) else label = PIMSD fi unset splitted disk = /dev/ $( lsblk -no pkname \" $part \" ) npart = $( cat \"/sys/class/block/ ${ part // \\/ dev \\/ / } /partition\" ) umount \" $part \" parted \" $disk \" -a optimal -s resizepart \" $npart \" 100 % yes | mkfs.ext4 -L \" $label \" -F -m 0 \" $part \" mount \" $part \" unset disk part npart label fi 2. Execute bash expand.sh on the terminal and wait for the execution to complete.","title":"Expand Filesystem"},{"location":"Expand_Filesystem/#expand-filesystem","text":"If you find that the free space of the raspberry pi SD card or eMMC is smaller than the capacity of the actual SD card or eMMC, you need to do the following to expand the raspberry pi. If you find that the system does not have the raspi config tool, you can use Method 2 (use the GParted partition tool).","title":"Expand Filesystem"},{"location":"Expand_Filesystem/#method-1-use-raspi-config-tool","text":"If you are using a mirror after June 2023 and have added a third read-write partition, this method is no longer applicable. Please refer to method 2 and method 3. 1. Open raspi-config. sudo raspi-config 2. Choose Advancd Options\uff1a 3. Choose Expand Filesystem\uff1a 4. Ok: 5. Execute the command resize2fs /dev/mmcblk0p2 in the terminal to see that the SD card has been successfully expanded.","title":"Method 1: Use raspi-config tool"},{"location":"Expand_Filesystem/#method-2-use-gparted-tool","text":"1. Connect the SD card or EMMc that has burned the image to the computer through USB. Take the GParted partition tool on Linux as an example. Other platforms also have similar partition tools. Open GParted software and select SD card: 2. By observing the partition of the SD card in the above figure, we can find that 2.01GB and 21.87GB of space are unused before and after the sdb3 partition, which is the space we want to expand. Select the sdb3 partition and click Resize. 3. You can drag the white partition of sdb3 to the leftmost and rightmost, or fill in 25958 with \"Previous Free Space\" as \"0\" and \"New Size\" as \"Maximum Size\", and then click Resize in the lower right corner. Then click OK to see that all unused space of sd has been used. 4. Insert the SD card into the device and start it.","title":"Method 2: Use GParted tool"},{"location":"Expand_Filesystem/#method-3-use-script","text":"If you are using a BliKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand.sh on any path, and write the following content to expand.sh. If your hardware is v1 , v2 or v3 , use: #!/bin/bash set -x resize_mmcblk0p3 () { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100 % resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" If your hardware is v4 , use: #!/bin/bash set -x resize_mmcblk0p1 () { echo \"Resizing mmcblk0p1 partition...\" parted /dev/mmcblk0 resizepart 1 100 % resize2fs /dev/mmcblk0p1 echo \"mmcblk0p1 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p1 echo \"Partition resizing completed.\" If you are using a PiKVM image, you can run the script below on the KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand.sh on any path, and write the following content to expand.sh #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab ; then part = $( grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}' ) # shellcheck disable=SC2206 splitted =( ${ part //=/ } ) if [ \" ${ splitted [0] } \" == LABEL ] ; then label = ${ splitted [1] } part = $( blkid -c /dev/null -L \" $label \" ) else label = PIMSD fi unset splitted disk = /dev/ $( lsblk -no pkname \" $part \" ) npart = $( cat \"/sys/class/block/ ${ part // \\/ dev \\/ / } /partition\" ) umount \" $part \" parted \" $disk \" -a optimal -s resizepart \" $npart \" 100 % yes | mkfs.ext4 -L \" $label \" -F -m 0 \" $part \" mount \" $part \" unset disk part npart label fi 2. Execute bash expand.sh on the terminal and wait for the execution to complete.","title":"Method 3: Use script"},{"location":"OLED-display/","text":"Principle After v1.5.0 version, to avoid OLED/LCD display burn-in the display's on-time is only turned on according to its configuration. Configuration // All time-parameters are in seconds, and are required to be integer multiples of 5. // This json file is on /mnt/exec/release/config/app.json \"Display\":{ \"isActive\": true, \"mode\": 1, \"onBootTime\": 3600, \"cycleInterval\": 300, \"displayTime\": 30, } Use isActive to activate the display :rotating_light: . While \"isActive\": \"false\" , the display will not function. All BliKVM versions mode 0 always on, doesn't care about any of the paramters 1 Display remains on for onBootTime seconds, after which the display turns off. Depends on \"onBootTime\" 2 Every period of cycleInterval , the display turns on for displayTime seconds`, then turns off. :rotating_light: Depends on \"cycleInterval\"and \"displayTime\" Only BliKVM v4 Allwinner Since v4 has the sw1 buttons, if set mode to 1. Behavior: On Boot: the display turns on for onBootTime seconds, then automatically turns off. On Button Press (sw1): Pressing sw1 turns on the display for displayTime seconds. If the display is already on, pressing sw1 will have no impact at all.","title":"OLED Display"},{"location":"OLED-display/#principle","text":"After v1.5.0 version, to avoid OLED/LCD display burn-in the display's on-time is only turned on according to its configuration.","title":"Principle"},{"location":"OLED-display/#configuration","text":"// All time-parameters are in seconds, and are required to be integer multiples of 5. // This json file is on /mnt/exec/release/config/app.json \"Display\":{ \"isActive\": true, \"mode\": 1, \"onBootTime\": 3600, \"cycleInterval\": 300, \"displayTime\": 30, } Use isActive to activate the display :rotating_light: . While \"isActive\": \"false\" , the display will not function.","title":"Configuration"},{"location":"OLED-display/#all-blikvm-versions","text":"mode 0 always on, doesn't care about any of the paramters 1 Display remains on for onBootTime seconds, after which the display turns off. Depends on \"onBootTime\" 2 Every period of cycleInterval , the display turns on for displayTime seconds`, then turns off. :rotating_light: Depends on \"cycleInterval\"and \"displayTime\"","title":"All BliKVM versions"},{"location":"OLED-display/#only-blikvm-v4-allwinner","text":"Since v4 has the sw1 buttons, if set mode to 1. Behavior: On Boot: the display turns on for onBootTime seconds, then automatically turns off. On Button Press (sw1): Pressing sw1 turns on the display for displayTime seconds. If the display is already on, pressing sw1 will have no impact at all.","title":"Only BliKVM v4 Allwinner"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4/","text":"BliKVM v1 (RPI CM4) BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! Connectivity diagram 1 OTG port 7 Micro SD card slot 2 USB3.0 x2 8 ACT LED (green) 3 ATX control port 9 Ethernet port 4 HDMI video input port 10 OLED Display 5 PWR IN port 11 Antenna mounting hole 6 Power LED (red) Specifications Parameter name Characteristics Power 5V 3A PWR IN port Connectivity/Interfaces HDMI IN HDMI video input port OTG Keyboard, mouse, mass storage, and other external device emulation CN-ATX Turn on/off or restart the controlled computer Micro SD card slot Persistent storage for OS and your data PWR IN port 5V 3A power port Displays and indicators LED indicators Power LED (red), ACT LED (green) OLED display OLED 128x64 0.96 inch Video Supported resolutions Up to 1920x1200@60Hz Video compression methods H.264, MJPEG Core Chip Raspberry Pi Compute Module 4 Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 120(L) x 70W) x 37(H) mm Weight 0.45 kg Dimensions Schematic Diagram","title":"BliKVM v1 (RPI CM4)"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4/#blikvm-v1-rpi-cm4","text":"BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals!","title":"BliKVM v1 (RPI CM4)"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4/#connectivity-diagram","text":"1 OTG port 7 Micro SD card slot 2 USB3.0 x2 8 ACT LED (green) 3 ATX control port 9 Ethernet port 4 HDMI video input port 10 OLED Display 5 PWR IN port 11 Antenna mounting hole 6 Power LED (red)","title":"Connectivity diagram"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4/#specifications","text":"Parameter name Characteristics Power 5V 3A PWR IN port Connectivity/Interfaces HDMI IN HDMI video input port OTG Keyboard, mouse, mass storage, and other external device emulation CN-ATX Turn on/off or restart the controlled computer Micro SD card slot Persistent storage for OS and your data PWR IN port 5V 3A power port Displays and indicators LED indicators Power LED (red), ACT LED (green) OLED display OLED 128x64 0.96 inch Video Supported resolutions Up to 1920x1200@60Hz Video compression methods H.264, MJPEG Core Chip Raspberry Pi Compute Module 4 Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 120(L) x 70W) x 37(H) mm Weight 0.45 kg","title":"Specifications"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4/#dimensions-schematic-diagram","text":"","title":"Dimensions Schematic Diagram"},{"location":"atx-guide/","text":"ATXA guide 1. Introduction ATXA is an ATX adapter board to manage the power of your computer. The product includes two modules; A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable. Join the Discord Community Chat for news, questions and support! ATXA_A ATXA_B 2. A-board A-board is connected to the Raspberry Pi. The following table is a typical connection method in PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed 3. B-board The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B Instructions for connecting to the computer motherboard According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the ATXA-B motherboard. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and ATXA-B. See the following figure for the connection relationship\uff1a 4.Mechanical Diagram 5. Test video YouTube: ATX 6. Purchase Purchase\uff1a ATX","title":"ATX Guide"},{"location":"atx-guide/#atxa-guide","text":"","title":"ATXA guide"},{"location":"atx-guide/#1-introduction","text":"ATXA is an ATX adapter board to manage the power of your computer. The product includes two modules; A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable. Join the Discord Community Chat for news, questions and support! ATXA_A ATXA_B","title":"1. Introduction"},{"location":"atx-guide/#2-a-board","text":"A-board is connected to the Raspberry Pi. The following table is a typical connection method in PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed","title":"2. A-board"},{"location":"atx-guide/#3-b-board","text":"The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B Instructions for connecting to the computer motherboard According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the ATXA-B motherboard. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and ATXA-B. See the following figure for the connection relationship\uff1a","title":"3. B-board"},{"location":"atx-guide/#4mechanical-diagram","text":"","title":"4.Mechanical Diagram"},{"location":"atx-guide/#5-test-video","text":"YouTube: ATX","title":"5. Test video"},{"location":"atx-guide/#6-purchase","text":"Purchase\uff1a ATX","title":"6. Purchase"},{"location":"atx/","text":"ATX Control Board To manage the power of your computer, you need to install an ATX control board inside the chassis and connect it to the motherboard (to enable KVM control of power on/off via the ATX switch). There is a female-to-female cable that connects from the motherboard to the ATX control board and a male-to-female cable that connects from the ATX control board to the front panel (to keep the power on/off button on the chassis functional). The interface on the ATX control board has two ports (TO CASE, TO MB), and both ports have the same functionality, so they can be used interchangeably. ATX compatibility Laptops are not compatible with ATX as they lack the required ATX pins. This method is only applicable to Desktop PC's and servers. Detailed Instructions 1. Connect the two cables to the ATX control board. To secure the ATX control board inside the chassis, you can choose to mount it on a bracket attached to a PCIe slot. Example 2. Locate the motherboard pins responsible for connecting the front panel buttons and LEDs and disconnect them. Usually, the cables and connectors on the motherboard are labeled. If you're unsure, you can refer to your motherboard's documentation. Example 3. Connect the DuPont male connector from the front panel to the DuPont female connector on the ATX cable, following the pin definitions and paying attention to the labels and polarity (+ or -). Example 4. Using the same method, connect the female pins from the ATX board to the corresponding connector on the motherboard. Refer to your motherboard's documentation to determine which pins on the motherboard connect to which pins on the ATX control board. Sometimes, this information is printed on the motherboard. Example 5. Install the ATX board into a PCI slot on the chassis and secure it with screws or use alternative mounting methods according to your preference. Example 6. Arrange the cables neatly and secure them as needed. Make sure the cables do not come into contact with any fans inside the chassis. Use an Ethernet cable to connect the ATX board to the ATX interface of the BliKVM. With this, the hardware connection of the ATX control board is complete.","title":"ATX Control Board"},{"location":"atx/#atx-control-board","text":"To manage the power of your computer, you need to install an ATX control board inside the chassis and connect it to the motherboard (to enable KVM control of power on/off via the ATX switch). There is a female-to-female cable that connects from the motherboard to the ATX control board and a male-to-female cable that connects from the ATX control board to the front panel (to keep the power on/off button on the chassis functional). The interface on the ATX control board has two ports (TO CASE, TO MB), and both ports have the same functionality, so they can be used interchangeably. ATX compatibility Laptops are not compatible with ATX as they lack the required ATX pins. This method is only applicable to Desktop PC's and servers.","title":"ATX Control Board"},{"location":"atx/#detailed-instructions","text":"1. Connect the two cables to the ATX control board. To secure the ATX control board inside the chassis, you can choose to mount it on a bracket attached to a PCIe slot. Example 2. Locate the motherboard pins responsible for connecting the front panel buttons and LEDs and disconnect them. Usually, the cables and connectors on the motherboard are labeled. If you're unsure, you can refer to your motherboard's documentation. Example 3. Connect the DuPont male connector from the front panel to the DuPont female connector on the ATX cable, following the pin definitions and paying attention to the labels and polarity (+ or -). Example 4. Using the same method, connect the female pins from the ATX board to the corresponding connector on the motherboard. Refer to your motherboard's documentation to determine which pins on the motherboard connect to which pins on the ATX control board. Sometimes, this information is printed on the motherboard. Example 5. Install the ATX board into a PCI slot on the chassis and secure it with screws or use alternative mounting methods according to your preference. Example 6. Arrange the cables neatly and secure them as needed. Make sure the cables do not come into contact with any fans inside the chassis. Use an Ethernet cable to connect the ATX board to the ATX interface of the BliKVM. With this, the hardware connection of the ATX control board is complete.","title":"Detailed Instructions"},{"location":"bliswitch-v1-guide/","text":"BliSwitch v1 4-port KVM switch BliKVM-Switch-V1.0 uses and tests video, supporting BliKVM and PiKVM Introduction BliKVM-Switch-V1.0 is a four channel HDMI+USB switch, which supports panel button, desktop controller and KVM remote to switch between computers. Maximum support of the switch itself 4K@60HZ Plug and play, driver free. BliKVM-Switch-V1.0 uses the same hardware solution as XH-HK4401, AG7210 HDMI switching chip supports up to 4K@60Hz, CH444G USB switching chip supports USB2.0. The difference is that BliKVM-Switch-V1.0 is equipped with KVM USB cable, which can realize KVM port selection. BliKVM-Switch-V1.0 is compatible with BliKVM and PiKVM. points for attention The switch can be powered directly from the USB input to the computer, that is, the switch can work normally without power supply. If the USB power supply of the controlled computer cannot make the switch work, the switch can be powered independently. The switch package only provides a USB power cable, but does not provide a power adapter. The customer needs to configure a power adapter (5V). Desktop controller can control HDMI switch with USB cable. For customers who do not use KVM, this is another way of switching for easy cable management. HDMI input support up to 4096x2160/60Hz resolution 4K 60Hz input, the power is about 200 mW. Interface Diagram There must be 2 USB cables from KVM to BliKVM, one for controller, and second from USB on KVM to USB-PC on BliKVM. Front and back interface diagram, the control interface in the right figure is the remote control interface.A cable with one end being USB-A and the other end being micro USB, labeled with the word \"KVM,\" serves as the control cable. The micro USB end is connected to the control interface of the switch, while the USB-A end is connected to the USB port of the KVM. Schematic Diagram of Side Interface. Equipment connection diagram. Software Configuration If you are using BliKVM software and have powered on the switch and connected the cables before starting BliKVM, no additional configuration is needed. BliKVM will automatically detect the switch when it starts. If automatic detection fails, you can manually specify the switch device: Confirm the device descriptor name of the switch by using the terminal, such as /dev/ttyUSB0 . Edit the switch_handle field in /usr/bin/blikvm/package.json . Set switch_enable to 1 and switch_path to /dev/ttyUSB0 in the configuration. Restart BliKVM. Click MORE in the lower left corner, find the BliKVM switch column, and then switch. Note that the flashing blue dot of the corresponding channel indicates that the switch insertion is recognized and is in the current channel. If there is no blue dot, the switch insertion is not recognized. If you use PiKVM software, please configure it according to the following instructions. Log in to PiKVM through SSH. The user name and password are root; Uses the rw command on the terminal to change the system to a read-write system; Edit /etc/kvmd/override.yaml . After the original content, add: kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] The above configuration is based on the 2022 PiKVM image. If you are using the latest PiKVM image or latest software version, edit /etc/kvmd/override.yaml and add the line: protocol: 2 . Example: kvmd: gpio: drivers: hk: type: xh_hk4401 protocol: 2 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk ... Use the ro command on the terminal to reset the system to a read-only system; Use systemctl restart kvmd on the terminal to restart the service; Enter the PiKVM web interface and click the \"GPIO\" menu. You should see 4 inputs, one of which has a green circle to indicate that it is currently selected. Click a different input to change the selected host. Control Protocol If you want to use the blicube switch on other platforms, please refer to the following protocol The communication baud rate is 19200 The message to switch to channel 1 is SW1\\r\\nG01gA The message to switch to channel 2 is SW2\\r\\nG02gA The message to switch to channel 3 is SW3\\r\\nG03gA The message to switch to channel 4 is SW4\\r\\nG04gA The message returned by the switch for the current channel is: G01gA , G02gA , G03gA , G04gA Packing List product quantity note HDMI KVM Switch(4-channel) 1 110mm * 60mm * 33mm Desktop controller 1 USB cable of Desktop controller 4 length: 1.2m HDMI(Standard) cable 5 length: 1.5m USB power cable 1 length: 0.8m USB cable of KVM 1 length: 1.5m USB cable of Desktop controller 1 length: 1m","title":"Multiport BliSwitch v1 (4-port)"},{"location":"bliswitch-v1-guide/#bliswitch-v1-4-port-kvm-switch","text":"BliKVM-Switch-V1.0 uses and tests video, supporting BliKVM and PiKVM","title":"BliSwitch v1 4-port KVM switch"},{"location":"bliswitch-v1-guide/#introduction","text":"BliKVM-Switch-V1.0 is a four channel HDMI+USB switch, which supports panel button, desktop controller and KVM remote to switch between computers. Maximum support of the switch itself 4K@60HZ Plug and play, driver free. BliKVM-Switch-V1.0 uses the same hardware solution as XH-HK4401, AG7210 HDMI switching chip supports up to 4K@60Hz, CH444G USB switching chip supports USB2.0. The difference is that BliKVM-Switch-V1.0 is equipped with KVM USB cable, which can realize KVM port selection. BliKVM-Switch-V1.0 is compatible with BliKVM and PiKVM. points for attention The switch can be powered directly from the USB input to the computer, that is, the switch can work normally without power supply. If the USB power supply of the controlled computer cannot make the switch work, the switch can be powered independently. The switch package only provides a USB power cable, but does not provide a power adapter. The customer needs to configure a power adapter (5V). Desktop controller can control HDMI switch with USB cable. For customers who do not use KVM, this is another way of switching for easy cable management. HDMI input support up to 4096x2160/60Hz resolution 4K 60Hz input, the power is about 200 mW.","title":"Introduction"},{"location":"bliswitch-v1-guide/#interface-diagram","text":"There must be 2 USB cables from KVM to BliKVM, one for controller, and second from USB on KVM to USB-PC on BliKVM. Front and back interface diagram, the control interface in the right figure is the remote control interface.A cable with one end being USB-A and the other end being micro USB, labeled with the word \"KVM,\" serves as the control cable. The micro USB end is connected to the control interface of the switch, while the USB-A end is connected to the USB port of the KVM. Schematic Diagram of Side Interface. Equipment connection diagram.","title":"Interface Diagram"},{"location":"bliswitch-v1-guide/#software-configuration","text":"If you are using BliKVM software and have powered on the switch and connected the cables before starting BliKVM, no additional configuration is needed. BliKVM will automatically detect the switch when it starts. If automatic detection fails, you can manually specify the switch device: Confirm the device descriptor name of the switch by using the terminal, such as /dev/ttyUSB0 . Edit the switch_handle field in /usr/bin/blikvm/package.json . Set switch_enable to 1 and switch_path to /dev/ttyUSB0 in the configuration. Restart BliKVM. Click MORE in the lower left corner, find the BliKVM switch column, and then switch. Note that the flashing blue dot of the corresponding channel indicates that the switch insertion is recognized and is in the current channel. If there is no blue dot, the switch insertion is not recognized. If you use PiKVM software, please configure it according to the following instructions. Log in to PiKVM through SSH. The user name and password are root; Uses the rw command on the terminal to change the system to a read-write system; Edit /etc/kvmd/override.yaml . After the original content, add: kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] The above configuration is based on the 2022 PiKVM image. If you are using the latest PiKVM image or latest software version, edit /etc/kvmd/override.yaml and add the line: protocol: 2 . Example: kvmd: gpio: drivers: hk: type: xh_hk4401 protocol: 2 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk ... Use the ro command on the terminal to reset the system to a read-only system; Use systemctl restart kvmd on the terminal to restart the service; Enter the PiKVM web interface and click the \"GPIO\" menu. You should see 4 inputs, one of which has a green circle to indicate that it is currently selected. Click a different input to change the selected host.","title":"Software Configuration"},{"location":"bliswitch-v1-guide/#control-protocol","text":"If you want to use the blicube switch on other platforms, please refer to the following protocol The communication baud rate is 19200 The message to switch to channel 1 is SW1\\r\\nG01gA The message to switch to channel 2 is SW2\\r\\nG02gA The message to switch to channel 3 is SW3\\r\\nG03gA The message to switch to channel 4 is SW4\\r\\nG04gA The message returned by the switch for the current channel is: G01gA , G02gA , G03gA , G04gA","title":"Control Protocol"},{"location":"bliswitch-v1-guide/#packing-list","text":"product quantity note HDMI KVM Switch(4-channel) 1 110mm * 60mm * 33mm Desktop controller 1 USB cable of Desktop controller 4 length: 1.2m HDMI(Standard) cable 5 length: 1.5m USB power cable 1 length: 0.8m USB cable of KVM 1 length: 1.5m USB cable of Desktop controller 1 length: 1m","title":"Packing List"},{"location":"bliswitch-v2-guide/","text":"BliSwitch v2 8-port KVM+ATX switch The BliSwitch v2 is an 8-channel KVM+ATX switch for 8 hosts to share input and power. Function: 8 hosts share a keyboard, mouse, and display, with power control for all. Switch Method: Button or USB control. Features ATX on each port(support button and remote control) Full control via web ui Compatible with BLIKVM V1, V2, V3 V4 and PikVM hardware. Port Definition Product Parameters Brand BLI Name 8-port KVM+ATX switcher Model BliSwitch v2 Function Eight hosts share a set of keyboard, mouse, and display, power control of 8 hosts Material All metal Resolution 1080P60Hz Switching Method Button switching or USB control module switching Power Supply 5V1A Control Protocol If you want to use Blicube's switch on other platforms, please refer to the following protocol Communication baud rate is 19200 The message to switch to channel 1 is SW1\\r\\nG01gA The message to switch to channel 2 is SW2\\r\\nG02gA The message to switch to channel 3 is SW3\\r\\nG03gA The message to switch to channel 4 is SW4\\r\\nG04gA The message to switch to channel 5 is SW5\\r\\nG05gA The message to switch to channel 6 is SW6\\r\\nG06gA The message to switch to channel 7 is SW7\\r\\nG07gA The message to switch to channel 8 is SW8\\r\\nG08gigA The message returned by the switch for the current channel is: G01gA, G02gA, G03gA, G04gA, G05gA, G06gA, G07gA, G08gA Connection Reference Dimensions Shipping List Product Quantity Remarks BliSwitch v4 switcher 1 Mounting ears 2 ATX cable male end 8 ATX cable female end 8 Full-height PCIe bracket 8 Half-height PCIe bracket 8 ATX board 8 Control cable 1 USB cable 1 Rubber pads 4 M2.5x5 countersunk screws 10 Buy link Buy Bliswitch v2","title":"Multiport BliSwitch v2 (8-port)"},{"location":"bliswitch-v2-guide/#bliswitch-v2-8-port-kvmatx-switch","text":"The BliSwitch v2 is an 8-channel KVM+ATX switch for 8 hosts to share input and power. Function: 8 hosts share a keyboard, mouse, and display, with power control for all. Switch Method: Button or USB control.","title":"BliSwitch v2 8-port KVM+ATX switch"},{"location":"bliswitch-v2-guide/#features","text":"ATX on each port(support button and remote control) Full control via web ui Compatible with BLIKVM V1, V2, V3 V4 and PikVM hardware.","title":"Features"},{"location":"bliswitch-v2-guide/#port-definition","text":"","title":"Port Definition"},{"location":"bliswitch-v2-guide/#product-parameters","text":"Brand BLI Name 8-port KVM+ATX switcher Model BliSwitch v2 Function Eight hosts share a set of keyboard, mouse, and display, power control of 8 hosts Material All metal Resolution 1080P60Hz Switching Method Button switching or USB control module switching Power Supply 5V1A","title":"Product Parameters"},{"location":"bliswitch-v2-guide/#control-protocol","text":"If you want to use Blicube's switch on other platforms, please refer to the following protocol Communication baud rate is 19200 The message to switch to channel 1 is SW1\\r\\nG01gA The message to switch to channel 2 is SW2\\r\\nG02gA The message to switch to channel 3 is SW3\\r\\nG03gA The message to switch to channel 4 is SW4\\r\\nG04gA The message to switch to channel 5 is SW5\\r\\nG05gA The message to switch to channel 6 is SW6\\r\\nG06gA The message to switch to channel 7 is SW7\\r\\nG07gA The message to switch to channel 8 is SW8\\r\\nG08gigA The message returned by the switch for the current channel is: G01gA, G02gA, G03gA, G04gA, G05gA, G06gA, G07gA, G08gA","title":"Control Protocol"},{"location":"bliswitch-v2-guide/#connection-reference","text":"","title":"Connection Reference"},{"location":"bliswitch-v2-guide/#dimensions","text":"","title":"Dimensions"},{"location":"bliswitch-v2-guide/#shipping-list","text":"Product Quantity Remarks BliSwitch v4 switcher 1 Mounting ears 2 ATX cable male end 8 ATX cable female end 8 Full-height PCIe bracket 8 Half-height PCIe bracket 8 ATX board 8 Control cable 1 USB cable 1 Rubber pads 4 M2.5x5 countersunk screws 10","title":"Shipping List"},{"location":"bliswitch-v2-guide/#buy-link","text":"Buy Bliswitch v2","title":"Buy link"},{"location":"dev_api/","text":"API DISCLAIMER: This API is experimental and subject to change at any moment! This document is only valid for v1.4.0 and earlier versions, and will be updated soon This document is the HTTP API development manual for BLIKVM OS. If you have new API requirements not covered in this document, you can submit a pull request on GitHub to seek support. Please replace the kvmip in the request URL with the actual IP address of your KVM. Authentication This API is used for user login and returns an access token. Some APIs within the system require a valid token for access. Request URL: http://kvmip/login_api Request Method: GET Request Body: JSON format, for example: { \"username\": \"admin\", \"password\": \"admin\" } The response is as follows; if the status is not 1, the authentication has failed. { \"status\": 1, \"info\": \"login success\", \"data\": { \"token\": \"2sscdada6a97a774fcd4714c\" } } MJPEG Video This API is used to obtain the MJPEG video stream when the image mode is set to MJPEG. Request URL: http://kvmip:8008/stream This API is used to capture a frame of MJPEG in image mode. Request URL: http://kvmip:8008/snapshot Request Method: GET Keyboard For specific keyboard encoding, please refer to the following: \"KeyA\"=> 4, \"KeyB\"=> 5, \"KeyC\"=> 6, \"KeyD\"=> 7, \"KeyE\"=> 8, \"KeyF\"=> 9, \"KeyG\"=> 10, \"KeyH\"=> 11, \"KeyI\"=> 12, \"KeyJ\"=> 13, \"KeyK\"=> 14, \"KeyL\"=> 15, \"KeyM\"=> 16, \"KeyN\"=> 17, \"KeyO\"=> 18, \"KeyP\"=> 19, \"KeyQ\"=> 20, \"KeyR\"=> 21, \"KeyS\"=> 22, \"KeyT\"=> 23, \"KeyU\"=> 24, \"KeyV\"=> 25, \"KeyW\"=> 26, \"KeyX\"=> 27, \"KeyY\"=> 28, \"KeyZ\"=> 29, \"Digit1\"=> 30, \"Digit2\"=> 31, \"Digit3\"=> 32, \"Digit4\"=> 33, \"Digit5\"=> 34, \"Digit6\"=> 35, \"Digit7\"=> 36, \"Digit8\"=> 37, \"Digit9\"=> 38, \"Digit0\"=> 39, \"Enter\"=> 40, \"Escape\"=> 41, \"Backspace\"=> 42, \"Tab\"=> 43, \"Space\"=> 44, \"Minus\"=> 45, \"Equal\"=> 46, \"BracketLeft\"=> 47, \"BracketRight\"=> 48, \"Backslash\"=> 49, \"Semicolon\"=> 51, \"Quote\"=> 52, \"Backquote\"=> 53, \"Comma\"=> 54, \"Period\"=> 55, \"Slash\"=> 56, \"CapsLock\"=> 57, \"F1\"=> 58, \"F2\"=> 59, \"F3\"=> 60, \"F4\"=> 61, \"F5\"=> 62, \"F6\"=> 63, \"F7\"=> 64, \"F8\"=> 65, \"F9\"=> 66, \"F10\"=> 67, \"F11\"=> 68, \"F12\"=> 69, \"PrtSc\"=> 70, \"ScrollLock\"=> 71, \"Pause\"=> 72, \"Insert\"=> 73, \"Home\"=> 74, \"PageUp\"=> 75, \"Delete\"=> 76, \"End\"=> 77, \"PageDown\"=> 78, \"ArrowRight\"=> 79, \"ArrowLeft\"=> 80, \"ArrowDown\"=> 81, \"ArrowUp\"=> 82, \"NumLock\"=> 83, \"NumpadDivide\"=> 84, \"NumpadMultiply\"=> 85, \"NumpadSubtract\"=> 86, \"NumpadAdd\"=> 87, \"NumpadEnter\"=> 88, \"Numpad1\"=> 89, \"Numpad2\"=> 90, \"Numpad3\"=> 91, \"Numpad4\"=> 92, \"Numpad5\"=> 93, \"Numpad6\"=> 94, \"Numpad7\"=> 95, \"Numpad8\"=> 96, \"Numpad9\"=> 97, \"Numpad0\"=> 98, \"NumpadDecimal\"=> 99 Request URL: http://kvmip/keyboard Request Method: GET Request Body: JSON format, where \"keycodes\" is a string array supporting multiple inputs at once. For example: { \"keycodes\": [\"Digit1\"] } The response result is as follows: { \"status\": 1, \"info\": \"key input success\", \"data\": [] }","title":"HTTP API"},{"location":"dev_api/#api","text":"DISCLAIMER: This API is experimental and subject to change at any moment! This document is only valid for v1.4.0 and earlier versions, and will be updated soon This document is the HTTP API development manual for BLIKVM OS. If you have new API requirements not covered in this document, you can submit a pull request on GitHub to seek support. Please replace the kvmip in the request URL with the actual IP address of your KVM.","title":"API"},{"location":"dev_api/#authentication","text":"This API is used for user login and returns an access token. Some APIs within the system require a valid token for access. Request URL: http://kvmip/login_api Request Method: GET Request Body: JSON format, for example: { \"username\": \"admin\", \"password\": \"admin\" } The response is as follows; if the status is not 1, the authentication has failed. { \"status\": 1, \"info\": \"login success\", \"data\": { \"token\": \"2sscdada6a97a774fcd4714c\" } }","title":"Authentication"},{"location":"dev_api/#mjpeg-video","text":"This API is used to obtain the MJPEG video stream when the image mode is set to MJPEG. Request URL: http://kvmip:8008/stream This API is used to capture a frame of MJPEG in image mode. Request URL: http://kvmip:8008/snapshot Request Method: GET","title":"MJPEG Video"},{"location":"dev_api/#keyboard","text":"For specific keyboard encoding, please refer to the following: \"KeyA\"=> 4, \"KeyB\"=> 5, \"KeyC\"=> 6, \"KeyD\"=> 7, \"KeyE\"=> 8, \"KeyF\"=> 9, \"KeyG\"=> 10, \"KeyH\"=> 11, \"KeyI\"=> 12, \"KeyJ\"=> 13, \"KeyK\"=> 14, \"KeyL\"=> 15, \"KeyM\"=> 16, \"KeyN\"=> 17, \"KeyO\"=> 18, \"KeyP\"=> 19, \"KeyQ\"=> 20, \"KeyR\"=> 21, \"KeyS\"=> 22, \"KeyT\"=> 23, \"KeyU\"=> 24, \"KeyV\"=> 25, \"KeyW\"=> 26, \"KeyX\"=> 27, \"KeyY\"=> 28, \"KeyZ\"=> 29, \"Digit1\"=> 30, \"Digit2\"=> 31, \"Digit3\"=> 32, \"Digit4\"=> 33, \"Digit5\"=> 34, \"Digit6\"=> 35, \"Digit7\"=> 36, \"Digit8\"=> 37, \"Digit9\"=> 38, \"Digit0\"=> 39, \"Enter\"=> 40, \"Escape\"=> 41, \"Backspace\"=> 42, \"Tab\"=> 43, \"Space\"=> 44, \"Minus\"=> 45, \"Equal\"=> 46, \"BracketLeft\"=> 47, \"BracketRight\"=> 48, \"Backslash\"=> 49, \"Semicolon\"=> 51, \"Quote\"=> 52, \"Backquote\"=> 53, \"Comma\"=> 54, \"Period\"=> 55, \"Slash\"=> 56, \"CapsLock\"=> 57, \"F1\"=> 58, \"F2\"=> 59, \"F3\"=> 60, \"F4\"=> 61, \"F5\"=> 62, \"F6\"=> 63, \"F7\"=> 64, \"F8\"=> 65, \"F9\"=> 66, \"F10\"=> 67, \"F11\"=> 68, \"F12\"=> 69, \"PrtSc\"=> 70, \"ScrollLock\"=> 71, \"Pause\"=> 72, \"Insert\"=> 73, \"Home\"=> 74, \"PageUp\"=> 75, \"Delete\"=> 76, \"End\"=> 77, \"PageDown\"=> 78, \"ArrowRight\"=> 79, \"ArrowLeft\"=> 80, \"ArrowDown\"=> 81, \"ArrowUp\"=> 82, \"NumLock\"=> 83, \"NumpadDivide\"=> 84, \"NumpadMultiply\"=> 85, \"NumpadSubtract\"=> 86, \"NumpadAdd\"=> 87, \"NumpadEnter\"=> 88, \"Numpad1\"=> 89, \"Numpad2\"=> 90, \"Numpad3\"=> 91, \"Numpad4\"=> 92, \"Numpad5\"=> 93, \"Numpad6\"=> 94, \"Numpad7\"=> 95, \"Numpad8\"=> 96, \"Numpad9\"=> 97, \"Numpad0\"=> 98, \"NumpadDecimal\"=> 99 Request URL: http://kvmip/keyboard Request Method: GET Request Body: JSON format, where \"keycodes\" is a string array supporting multiple inputs at once. For example: { \"keycodes\": [\"Digit1\"] } The response result is as follows: { \"status\": 1, \"info\": \"key input success\", \"data\": [] }","title":"Keyboard"},{"location":"edid/","text":"EDID The EDID file in BliKVM serves the purpose of informing the controlled computer about the expected HDMI output resolution. For example, if the EDID is set to 1080P60Hz, and the controlled computer supports this resolution, it will output at 1080P60Hz. Additionally, EDID can be used to disable audio, modify the display model, name, manufacturer, and other information. In most cases, you don't need to change it, but sometimes, especially with strange UEFI/BIOS behavior, it may be necessary. Note BliKVM v1, v2, and v3 use the CSI video capture scheme, which supports EDID settings. However, BliKVM v4 uses the USB video capture scheme, which does not support EDID settings. For v3 HAT, there is a limitation of two CSI channels on the Raspberry Pi 4B, which means it can only capture video input with a maximum resolution of 1080P50Hz. Therefore, if you set 1080P60Hz EDID for v3, it will not be able to capture the image. If you are using PiKVM OS, you can refer to this link for modification instructions. If you are using BliKVM OS, the EDID file is located at /usr/bin/blikvm/edid.txt . Open this file, and replace the EDID contents with the desired resolution's EDID. EDID Examples for 1080P60Hz The following EDID is suitable for v1 and v2 hardware. 1920x1080 60Hz, with audio 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C EDID Examples for 1080P50Hz The following EDID is suitable for v1, v2, and v3 hardware, especially when you want v3 HAT to capture 1080P resolution. 1920x1080 50Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028 EDID Examples for 720P60Hz The following EDID is suitable for v1, v2, and v3 hardware. 1280x720 60Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 Custom EDID To customize the EDID, it is best to use third-party utilities, such as the recommended advanced AW EDID Editor (works well in Windows and can be used in wine) or wxEDID . Both editors work with the binary EDID format. Using these tools, you can modify the EDID information like editing a file, similar to changing the information on an identity card. By editing the EDID, you can adjust the parameters and characteristics of the display to suit different usage requirements, and thus achieve better display performance.","title":"HDMI EDID"},{"location":"edid/#edid","text":"The EDID file in BliKVM serves the purpose of informing the controlled computer about the expected HDMI output resolution. For example, if the EDID is set to 1080P60Hz, and the controlled computer supports this resolution, it will output at 1080P60Hz. Additionally, EDID can be used to disable audio, modify the display model, name, manufacturer, and other information. In most cases, you don't need to change it, but sometimes, especially with strange UEFI/BIOS behavior, it may be necessary. Note BliKVM v1, v2, and v3 use the CSI video capture scheme, which supports EDID settings. However, BliKVM v4 uses the USB video capture scheme, which does not support EDID settings. For v3 HAT, there is a limitation of two CSI channels on the Raspberry Pi 4B, which means it can only capture video input with a maximum resolution of 1080P50Hz. Therefore, if you set 1080P60Hz EDID for v3, it will not be able to capture the image. If you are using PiKVM OS, you can refer to this link for modification instructions. If you are using BliKVM OS, the EDID file is located at /usr/bin/blikvm/edid.txt . Open this file, and replace the EDID contents with the desired resolution's EDID.","title":"EDID"},{"location":"edid/#edid-examples-for-1080p60hz","text":"The following EDID is suitable for v1 and v2 hardware. 1920x1080 60Hz, with audio 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C","title":"EDID Examples for 1080P60Hz"},{"location":"edid/#edid-examples-for-1080p50hz","text":"The following EDID is suitable for v1, v2, and v3 hardware, especially when you want v3 HAT to capture 1080P resolution. 1920x1080 50Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028","title":"EDID Examples for 1080P50Hz"},{"location":"edid/#edid-examples-for-720p60hz","text":"The following EDID is suitable for v1, v2, and v3 hardware. 1280x720 60Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000","title":"EDID Examples for 720P60Hz"},{"location":"edid/#custom-edid","text":"To customize the EDID, it is best to use third-party utilities, such as the recommended advanced AW EDID Editor (works well in Windows and can be used in wine) or wxEDID . Both editors work with the binary EDID format. Using these tools, you can modify the EDID information like editing a file, similar to changing the information on an identity card. By editing the EDID, you can adjust the parameters and characteristics of the display to suit different usage requirements, and thus achieve better display performance.","title":"Custom EDID"},{"location":"faq/","text":"FAQ & Troubleshooting As a first step, we recommend carefully reading our documentation. Most steps to successfully set up your BLIKVM are already described there. If you run into any issues you can check this page 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. Common Questions Can I connect multiple servers to a single BLIKVM? Yes, but it requires additional work to set up. See this page . How can I get the access to PiKVM in my local network over Internet? If your router has an external IP address, you can use port forwarding to forward port 80 (Web), port 8008 (mjpeg), and port 8188 (webrtc) In all other cases, you can use the excellent free VPN service Tailscale. Which BLiKVM hardware version should I choose, such as BLiKVM V1 CM4, BLiKVM V2 PCIe, and BLiKVM V3 Hat? First, please refer to this page for a comparison of the main parameters of each version. V1 and V3 are external solutions, while V2 is an internal chassis solution. If you have a chassis and there is space inside, choosing the V2 PCIe version would be a better option. So how do you choose between the external solutions V1 and V3? V1 is based on the CM4 platform, with higher integration and ready-to-use versions available. V3 is based on the Raspberry Pi 4B platform, with all IO ports exposed and greater expandability. Another key difference is that V1 supports up to 1080P60Hz input, while V3 supports up to 1080P50Hz input. Of course, you also need to consider whether you already have a CM4 or 4B, as purchasing the corresponding baseboard would offer better cost-effectiveness. Can I use BLIKVM for gaming? No, because: For HDMI-CSI bridge, bus bandwidth is not enough to transmit more than 1080p60. For HDMI-USB dongle, high latency and low video quality. General hardware video capture differs from software streaming and introduces additional latency. Can BLIKVM do 4K video? For HDMI-CSI bridge, no. There is not enough bandwidth in the CSI bus for that much data. 1080p60 will max out the bandwidth. For the USB capture devices: technically yes, they will downsample to something smaller to meet the USB 2.0 bandwidth limitations, so the source may be 4k, but the stream will not. The 4K real-time video will not fit through the network anyway. Where does the cursor/video latency come from? Here is the chain of transferring an image to your browser or VNC client. Capture device -> Compression -> Network -> Decompression -> Rendering 100-200ms is very, very fast for this. But we are working to speed things up even more. Does BLIKVM support sound? BliKVM v1 CM4, v2 PCIe, v3 HAT version supported\uff0c v4 Allwinner not support now. Can I power the Pi via PoE? Yes! Hat and PCIe version supported. First Steps What is the default password? How do I change it? If you use PiKVM, there are two types of accounts: OS and PiKVM (web interface) accounts. The system account blikvm can be used for SSH/UART access and has the password blikvm . The web interface account is called admin and has the password admin . The PiKVM account cannot be used for SSH access and vice versa. To change passwords, use the following commands (become the root user): su - # If you're in the webterm rw # Switch filesystem to read-write mode passwd blikvm # Change blikvm user password kvmd-htpasswd set admin # Change web ui admin password ro # Back to read-only How do I add another user? If you use PiKVM software, as stated above you need to make 2 accounts, 1 for the shell, the other for the PiKVM Web UI. If you require additional users for PiKVM UI, you can use the following: # su - # rw # kvmd-htpasswd set # Adds a new user # kvmd-htpasswd set # Sets the password as long as the user exists # kvmd-htpasswd del # Removes/deletes a user To add a shell/terminal account: # su - # rw # adduser # passwd Keep in mind that the more users that are added and accessing the screen stream at the same time, the FPS will drop. Video Problems BLIKVM does not show the video from the computer at all If the output of dmesg | grep tc358743 does not show something similar as tc358743 found @ ... , then this means that the TC358743 HDMI input bridge is not detected. Verify that the flex flat cable (ffc) is correctly connected. Double-check that the video capture device is connected correctly. For the CSI bridge, this should be exactly the camera port. Some laptops do not output any signal until you switch the output (usually via the FN + and an F5 key on the keyboard). Your computer may have turned on sleep mode for the monitor. Move the mouse to turn it off. For windows you might need to check for the active signal resolution. To change the active signal resolution you have to go to Settings>System>Display>Advanced display settings>Display adapter properties then, click \"List All Models\" and choose the one you want. Keep trying different Hz settings. The video works in the booted OS, but not in the BIOS/UEFI This problem appears on Intel NUC, GA-H77-DS3H, and some other devices when using a CSI bridge. All you need to do is change the EDID data. This is the information about supported resolutions that the CSI bridge reports to your computer. Glitchy or wrong BIOS/UEFI 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: 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 (DP) 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. There is no video in GRUB2, but there is before and after Sometimes this can be caused by the specifics of the BIOS/UEFI and how GRUB2 works with video. This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. The video mode will be located in the same section. Switch the Video mode from UEFI to Legacy . No image from computer with Linux + Awesome WM 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 BLIKVM - it may happen that you will not see the image. It seems that the problem is Awesome WM, since for example with KDE, it is not reproducable. If you turn on your workstation with BLIKVM already connected, everything will work fine. USB Problems (keyboard, mouse, mass storage, etc) What speed is the USB OTG port? Per the official RPI documentation, this is a limitation of the SoC. The OTG port is only USB2.0, so is limited to 455 Mbit/s. Why can't some keyboard shortcuts of physical keyboards be captured while virtual keyboards can? For example, the F11 key on a Mac computer cannot be captured. This is because some shortcuts are already in use by the system, such as in macOS, where F11 is assigned to the \"Show Desktop\" function by default. When you press F11 in a web interface, the KeyboardEvent is first captured by the system, and if a callback is registered in the system, the event will not be passed to the application. To solve this issue, you can disable the system's assigned shortcut or use a virtual keyboard. Hardware Problems (Wi-Fi, ATX, etc) If you use PiKVM software, the web UI show FAN error! Because the fan model used by BLIKVM hardware is different from that of PIKVM hardware, viewing the fan status through the web interface may fail in the latest system of pikvm. However, this will not affect the normal operation of BLIKVM fan. Therefore, when using the PIKVM image, as long as you ensure that the install script displays OK, it means that the update of the kvmd fan program is successful. The threshold temperature set by the default program is 60 degrees Celsius. When the CPU temperature is detected to exceed 60 degrees Celsius, the fan will start rotating at 85% speed. If you want to modify the threshold temperature and speed, you can modify the kvmd-fan.py script, and then re-execute install.sh. I can't connect to Wi-Fi at all! If your device is unable to connect to the Wi-Fi network that you have set up, check the 2.4 GHz Wi-Fi channel used by your Wi-Fi access point. If channels 12 to 14 are used (some countries have banned these channels) try to use a channel between 1 and 11. BLIKVM complains about low power warnings Are you using a \"proper\" power supply? Not one you hacked together? Some USB power bricks advertise 5V 2.1A or higher, but can't deliver consistent 5V. Best to use Raspberry Pi Foundation recommended power supplies. It should be 5.1v and 3A DC output. When I use the PoE, do I still need to use the power OTG splitter to prevent back power on the machine usb? Only HAT version you need to use power OTG splitter to prevent back power. Generally, most hosts computer are protected back power, you do not need to usr power OTG splitter in this case. BLIKVM-CM4-V2.2 and BLIKVM-PCIe version don't need. In some board like BLIKVM-PCIe or BLIKVM-CM4-V2.2 has boot pin, how do I connect? If you short them, CM4 will not start normally, but will enter the burning image mode. If your hardware version of boot has only two pins, use the jumper cap to connect the two pins as a short circuit. If you do not use the jumper cap or plug it into one pin, CM4 will start normally. If you use three boot pins of the hardware version, use the jumper cap to connect GND and another non-GND pin to indicate short circuit, and plug the jumper cap on the two GND pins or do not use it, CM4 will start normally. Web Problems What ports does BliKVM OS occupy, and how should it be forwarded when using a public server? The web interface uses the HTTP protocol and occupies port 80. If you are using hardware versions V1, V2, or V3 with web-rtc transmission, the port is 8188. If you are using hardware version V4 with MJPEG transmission, the port is 8008. Please note that the ports cannot be modified; only port forwarding can be configured. Raspberry Problems Can I use both the CM4 version with EMMC and the SD card at the same time? No, you can't, When designing the CM4 hardware, several pins of the SD card are only valid in the lite version. You can find instructions on the official website of Raspberry Pi.","title":"FAQ"},{"location":"faq/#faq-troubleshooting","text":"As a first step, we recommend carefully reading our documentation. Most steps to successfully set up your BLIKVM are already described there. If you run into any issues you can check this page 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.","title":"FAQ & Troubleshooting"},{"location":"faq/#common-questions","text":"Can I connect multiple servers to a single BLIKVM? Yes, but it requires additional work to set up. See this page . How can I get the access to PiKVM in my local network over Internet? If your router has an external IP address, you can use port forwarding to forward port 80 (Web), port 8008 (mjpeg), and port 8188 (webrtc) In all other cases, you can use the excellent free VPN service Tailscale. Which BLiKVM hardware version should I choose, such as BLiKVM V1 CM4, BLiKVM V2 PCIe, and BLiKVM V3 Hat? First, please refer to this page for a comparison of the main parameters of each version. V1 and V3 are external solutions, while V2 is an internal chassis solution. If you have a chassis and there is space inside, choosing the V2 PCIe version would be a better option. So how do you choose between the external solutions V1 and V3? V1 is based on the CM4 platform, with higher integration and ready-to-use versions available. V3 is based on the Raspberry Pi 4B platform, with all IO ports exposed and greater expandability. Another key difference is that V1 supports up to 1080P60Hz input, while V3 supports up to 1080P50Hz input. Of course, you also need to consider whether you already have a CM4 or 4B, as purchasing the corresponding baseboard would offer better cost-effectiveness. Can I use BLIKVM for gaming? No, because: For HDMI-CSI bridge, bus bandwidth is not enough to transmit more than 1080p60. For HDMI-USB dongle, high latency and low video quality. General hardware video capture differs from software streaming and introduces additional latency. Can BLIKVM do 4K video? For HDMI-CSI bridge, no. There is not enough bandwidth in the CSI bus for that much data. 1080p60 will max out the bandwidth. For the USB capture devices: technically yes, they will downsample to something smaller to meet the USB 2.0 bandwidth limitations, so the source may be 4k, but the stream will not. The 4K real-time video will not fit through the network anyway. Where does the cursor/video latency come from? Here is the chain of transferring an image to your browser or VNC client. Capture device -> Compression -> Network -> Decompression -> Rendering 100-200ms is very, very fast for this. But we are working to speed things up even more. Does BLIKVM support sound? BliKVM v1 CM4, v2 PCIe, v3 HAT version supported\uff0c v4 Allwinner not support now. Can I power the Pi via PoE? Yes! Hat and PCIe version supported.","title":"Common Questions"},{"location":"faq/#first-steps","text":"What is the default password? How do I change it? If you use PiKVM, there are two types of accounts: OS and PiKVM (web interface) accounts. The system account blikvm can be used for SSH/UART access and has the password blikvm . The web interface account is called admin and has the password admin . The PiKVM account cannot be used for SSH access and vice versa. To change passwords, use the following commands (become the root user): su - # If you're in the webterm rw # Switch filesystem to read-write mode passwd blikvm # Change blikvm user password kvmd-htpasswd set admin # Change web ui admin password ro # Back to read-only How do I add another user? If you use PiKVM software, as stated above you need to make 2 accounts, 1 for the shell, the other for the PiKVM Web UI. If you require additional users for PiKVM UI, you can use the following: # su - # rw # kvmd-htpasswd set # Adds a new user # kvmd-htpasswd set # Sets the password as long as the user exists # kvmd-htpasswd del # Removes/deletes a user To add a shell/terminal account: # su - # rw # adduser # passwd Keep in mind that the more users that are added and accessing the screen stream at the same time, the FPS will drop.","title":"First Steps"},{"location":"faq/#video-problems","text":"BLIKVM does not show the video from the computer at all If the output of dmesg | grep tc358743 does not show something similar as tc358743 found @ ... , then this means that the TC358743 HDMI input bridge is not detected. Verify that the flex flat cable (ffc) is correctly connected. Double-check that the video capture device is connected correctly. For the CSI bridge, this should be exactly the camera port. Some laptops do not output any signal until you switch the output (usually via the FN + and an F5 key on the keyboard). Your computer may have turned on sleep mode for the monitor. Move the mouse to turn it off. For windows you might need to check for the active signal resolution. To change the active signal resolution you have to go to Settings>System>Display>Advanced display settings>Display adapter properties then, click \"List All Models\" and choose the one you want. Keep trying different Hz settings. The video works in the booted OS, but not in the BIOS/UEFI This problem appears on Intel NUC, GA-H77-DS3H, and some other devices when using a CSI bridge. All you need to do is change the EDID data. This is the information about supported resolutions that the CSI bridge reports to your computer. Glitchy or wrong BIOS/UEFI 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: 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 (DP) 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. There is no video in GRUB2, but there is before and after Sometimes this can be caused by the specifics of the BIOS/UEFI and how GRUB2 works with video. This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. The video mode will be located in the same section. Switch the Video mode from UEFI to Legacy . No image from computer with Linux + Awesome WM 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 BLIKVM - it may happen that you will not see the image. It seems that the problem is Awesome WM, since for example with KDE, it is not reproducable. If you turn on your workstation with BLIKVM already connected, everything will work fine.","title":"Video Problems"},{"location":"faq/#usb-problems-keyboard-mouse-mass-storage-etc","text":"What speed is the USB OTG port? Per the official RPI documentation, this is a limitation of the SoC. The OTG port is only USB2.0, so is limited to 455 Mbit/s. Why can't some keyboard shortcuts of physical keyboards be captured while virtual keyboards can? For example, the F11 key on a Mac computer cannot be captured. This is because some shortcuts are already in use by the system, such as in macOS, where F11 is assigned to the \"Show Desktop\" function by default. When you press F11 in a web interface, the KeyboardEvent is first captured by the system, and if a callback is registered in the system, the event will not be passed to the application. To solve this issue, you can disable the system's assigned shortcut or use a virtual keyboard.","title":"USB Problems (keyboard, mouse, mass storage, etc)"},{"location":"faq/#hardware-problems-wi-fi-atx-etc","text":"If you use PiKVM software, the web UI show FAN error! Because the fan model used by BLIKVM hardware is different from that of PIKVM hardware, viewing the fan status through the web interface may fail in the latest system of pikvm. However, this will not affect the normal operation of BLIKVM fan. Therefore, when using the PIKVM image, as long as you ensure that the install script displays OK, it means that the update of the kvmd fan program is successful. The threshold temperature set by the default program is 60 degrees Celsius. When the CPU temperature is detected to exceed 60 degrees Celsius, the fan will start rotating at 85% speed. If you want to modify the threshold temperature and speed, you can modify the kvmd-fan.py script, and then re-execute install.sh. I can't connect to Wi-Fi at all! If your device is unable to connect to the Wi-Fi network that you have set up, check the 2.4 GHz Wi-Fi channel used by your Wi-Fi access point. If channels 12 to 14 are used (some countries have banned these channels) try to use a channel between 1 and 11. BLIKVM complains about low power warnings Are you using a \"proper\" power supply? Not one you hacked together? Some USB power bricks advertise 5V 2.1A or higher, but can't deliver consistent 5V. Best to use Raspberry Pi Foundation recommended power supplies. It should be 5.1v and 3A DC output. When I use the PoE, do I still need to use the power OTG splitter to prevent back power on the machine usb? Only HAT version you need to use power OTG splitter to prevent back power. Generally, most hosts computer are protected back power, you do not need to usr power OTG splitter in this case. BLIKVM-CM4-V2.2 and BLIKVM-PCIe version don't need. In some board like BLIKVM-PCIe or BLIKVM-CM4-V2.2 has boot pin, how do I connect? If you short them, CM4 will not start normally, but will enter the burning image mode. If your hardware version of boot has only two pins, use the jumper cap to connect the two pins as a short circuit. If you do not use the jumper cap or plug it into one pin, CM4 will start normally. If you use three boot pins of the hardware version, use the jumper cap to connect GND and another non-GND pin to indicate short circuit, and plug the jumper cap on the two GND pins or do not use it, CM4 will start normally.","title":"Hardware Problems (Wi-Fi, ATX, etc)"},{"location":"faq/#web-problems","text":"What ports does BliKVM OS occupy, and how should it be forwarded when using a public server? The web interface uses the HTTP protocol and occupies port 80. If you are using hardware versions V1, V2, or V3 with web-rtc transmission, the port is 8188. If you are using hardware version V4 with MJPEG transmission, the port is 8008. Please note that the ports cannot be modified; only port forwarding can be configured.","title":"Web Problems"},{"location":"faq/#raspberry-problems","text":"Can I use both the CM4 version with EMMC and the SD card at the same time? No, you can't, When designing the CM4 hardware, several pins of the SD card are only valid in the lite version. You can find instructions on the official website of Raspberry Pi.","title":"Raspberry Problems"},{"location":"first_steps/","text":"First steps First power on Power up the device. Do not turn off the device until it's fully booted for the first time After turning on the power, BLIKVM OS will perform the necessary operations on the memory card. Getting access to BLIKVM By default, BliKVM receives a dynamic IP address via DHCP. The IP address will be displayed on the BliKVM monitor. If you are using DIY hardware without a monitor, use the following tips: Finding BliKVM in the network You can determine the IP address of BliKVM using the following methods: Common Method: Access the web interface of your router and look for the allocated IP address list. The specific method depends on the router model. Linux Only: Use the command arp-scan --localnet . Linux, macOS, Windows: Download and run Angry IP Scanner . Windows PowerShell: Use the command arp -a . In the example below, let's assume your BliKVM has obtained the address 192.168.0.100 , and you have successfully found that address using the instructions above. Accessing BliKVM Web Interface In most networks, you can access BliKVM in any browser using the following URL: http://192.168.0.100/ . Google Chrome (Chromium), Firefox, and Safari work best with no extensions enabled. If one works and the other does not, it may be an issue with the browser or extensions. It is recommended to use a private browsing window or incognito mode. Internet Explorer and early versions of Microsoft Edge (non-Chromium version) are not supported. The default username is admin , and the password is also admin . Once logged in, you will have access to the main menu with essential functions. You can change system settings and passwords using the web interface's account management feature. Note: The BliKVM Web interface should be accessed via http, not https Accessing BliKVM via SSH SSH is the most common method for remote access in the Linux world. You can access BliKVM via SSH. This method is used for managing the device: Linux, macOS: Open any terminal application and run: ssh blikvm@192.168.0.100 . Windows: Use PuTTY for the operation. The default blikvm user password is blikvm . You can use sudo -i to obtain root privileges. Optional: Updating BliKVM Software This section is not mandatory and should only be performed if you have physical access to the BliKVM for recovery purposes. Refer to the Software Update Guide for instructions. Note on BliKVM OS Terminal Usage Some configuration changes must be made under the root user (i.e., administrator). Obtaining Root Privileges If you are logged in via SSH, use sudo -i to obtain root privileges. BliKVM storage cards in versions v1 , v2 , and v3 are mounted in read-only mode . This protects the file system from being corrupted in the event of a sudden power outage. To edit any files and make changes, you need to remount the file system in read-write mode. You can determine the current mode by checking if ro or rw is displayed in the terminal. Enabling Write Mode To enable write mode, run the command rw . To disable write mode, run the command ro . If you receive a \"Device is busy\" message, execute the reboot command. What's next? Set up internet access using Port Forwarding or Tailscale VPN . Explore BLIKVM features using the table of contents on the left. Join our Discord to connect with the community and developers. Check out the GitHub - BLIKVM is a Open Source project! FAQ and Troubleshooting If you have any questions or run into problems, take a look at the FAQ . Seriously, it's really useful! We've probably already found a solution for it :) For any other help and support, you can contact us via the Discord chat .","title":"First Steps"},{"location":"first_steps/#first-steps","text":"","title":"First steps"},{"location":"first_steps/#first-power-on","text":"Power up the device. Do not turn off the device until it's fully booted for the first time After turning on the power, BLIKVM OS will perform the necessary operations on the memory card.","title":"First power on"},{"location":"first_steps/#getting-access-to-blikvm","text":"By default, BliKVM receives a dynamic IP address via DHCP. The IP address will be displayed on the BliKVM monitor. If you are using DIY hardware without a monitor, use the following tips: Finding BliKVM in the network You can determine the IP address of BliKVM using the following methods: Common Method: Access the web interface of your router and look for the allocated IP address list. The specific method depends on the router model. Linux Only: Use the command arp-scan --localnet . Linux, macOS, Windows: Download and run Angry IP Scanner . Windows PowerShell: Use the command arp -a . In the example below, let's assume your BliKVM has obtained the address 192.168.0.100 , and you have successfully found that address using the instructions above. Accessing BliKVM Web Interface In most networks, you can access BliKVM in any browser using the following URL: http://192.168.0.100/ . Google Chrome (Chromium), Firefox, and Safari work best with no extensions enabled. If one works and the other does not, it may be an issue with the browser or extensions. It is recommended to use a private browsing window or incognito mode. Internet Explorer and early versions of Microsoft Edge (non-Chromium version) are not supported. The default username is admin , and the password is also admin . Once logged in, you will have access to the main menu with essential functions. You can change system settings and passwords using the web interface's account management feature. Note: The BliKVM Web interface should be accessed via http, not https Accessing BliKVM via SSH SSH is the most common method for remote access in the Linux world. You can access BliKVM via SSH. This method is used for managing the device: Linux, macOS: Open any terminal application and run: ssh blikvm@192.168.0.100 . Windows: Use PuTTY for the operation. The default blikvm user password is blikvm . You can use sudo -i to obtain root privileges. Optional: Updating BliKVM Software This section is not mandatory and should only be performed if you have physical access to the BliKVM for recovery purposes. Refer to the Software Update Guide for instructions.","title":"Getting access to BLIKVM"},{"location":"first_steps/#note-on-blikvm-os-terminal-usage","text":"Some configuration changes must be made under the root user (i.e., administrator). Obtaining Root Privileges If you are logged in via SSH, use sudo -i to obtain root privileges. BliKVM storage cards in versions v1 , v2 , and v3 are mounted in read-only mode . This protects the file system from being corrupted in the event of a sudden power outage. To edit any files and make changes, you need to remount the file system in read-write mode. You can determine the current mode by checking if ro or rw is displayed in the terminal. Enabling Write Mode To enable write mode, run the command rw . To disable write mode, run the command ro . If you receive a \"Device is busy\" message, execute the reboot command.","title":"Note on BliKVM OS Terminal Usage"},{"location":"first_steps/#whats-next","text":"Set up internet access using Port Forwarding or Tailscale VPN . Explore BLIKVM features using the table of contents on the left. Join our Discord to connect with the community and developers. Check out the GitHub - BLIKVM is a Open Source project!","title":"What's next?"},{"location":"first_steps/#faq-and-troubleshooting","text":"If you have any questions or run into problems, take a look at the FAQ . Seriously, it's really useful! We've probably already found a solution for it :) For any other help and support, you can contact us via the Discord chat .","title":"FAQ and Troubleshooting"},{"location":"flashing_os/","text":"Flasing the OS image Micro-SD Card Requirements Minimum 16 Gb Class 10 is strongly recommended Why are there two versions of software, BLIKVM and PiKVM? What is the difference between the two versions? Which one should I choose? Can I use the official image of PiKVM? At the beginning of the BLIKVM project, the hardware was developed, and the software directly used PiKVM. With the continuous progress of the project, BLIKVM has developed its own software version of new architecture, which also lays the foundation for deeper cooperation with its own hardware; The core functions of BLIKVM and PiKVM are the same for users. Some subdivision functions are not the same. For example, BLIKVM supports multiple languages; Select according to your own use experience; You can use the PiKVM official image, but you need to make some adaptations according to the different hardware, mainly involving screens, fans, etc. Since the PiKVM official image is always updated, the specific adaptations need to be seen according to the specific situation you encounter at that time; Download the image Users who need to run PiKVM on v4 by yourself can refer to this doc . BliKVM Versions and Software Image Compatibility The following BliKVM versions use the same BliKVM v1-3 software image: BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 Allwinner, uses a separate Allwinner BliKVM image. BliKVM v4 Web UI The web UI is consistent across all supported versions for easy remote administration. Base on PiKVM software Raspberry 4B and CM4 board use different PiKVM software image. After entering the link, you can see the image named with each hardware version (HAT CM4 PCIe) PiKVM image Flash the image Tip Ignore request to format your sd card, this step is not nessessary. Choose the most suitable method for you. How to flash the eMMC on a Raspberry Pi Compute Module 4 Board Link If you use a CM4 with eMMC (like the CM4102016). You can use the v1 or v2 board to flash the eMMC. If your CM4 doesn't have eMMC, your device can just use a SD card to boot from. You don't need to look into this any further. Just flash to the SD card instead. First, use the jumper cap to short the boot pin (allowing you flash the EMMC memory). If you use BLIKVM CM4 version Then connect the data cable to the USB OTG interface. Power on blikvm and observe the act light, the green light is always on. If you use BLIKVM PCIe version Then connect the data cable to the USB-PC interface. Power on blikvm and observe the ACT and PWR LED isn't light. After initialize EMMC through the usbboot/rpiboot, the ACT and PWR LED light is always on. EMMC knowledge If you use Raspberry Pi compute modules such as CM3 eMMC or CM4 eMMC version\uff0cyou can initialize eMMC through the usbboot project. Note that the eMMC board version cannot use the SD card to boot the image. Instead, you need to flash the eMMC storage by using the usbboot project that emulates USB Mass Storage Device (MSD). From this video you can learn how-to flash the image quickly. How to flash the eMMC on a Raspberry Pi Compute Module 4 video Taking Ubuntu system as an example: Linux usbboot If you use an Micro-SD Card, you can skip the following steps and go to the next chapter down below. sudo apt install git libusb-1.0-0-dev pkg-config build-essential git clone --depth = 1 https://github.com/raspberrypi/usbboot cd usbboot make sudo ./rpiboot If the content in the image below appears, that indicates that the eMMC initialization was successful. The next step is to flash the image to your eMMC chip. Flash the Image (Linux, MacOS and Windows) Please do not make any additional settings to the image in RPi Imager, as this will most likely cause the image to fail to boot or repeatedly restart. We are using the \"RPi Imager\" application to flash the image in this example. Download and install the latest version of RPi Imager . Run RPi Imager: Press CHOOSE OS and select Use custom image at bottom of the list: After clicking on this item, select the image file ( .img.xz ), then click CHOOSE STORAGE : Insert the memory card into the card reader. Choose the card reader from this list (or eMMC flash storage, in case you are using a Raspberry Pi Compute module with a eMMC chip). Be careful and choose the right device: After choosing the memory card, press the WRITE button. Confirm the operation when you are asked about it: Wait for the process to finish. Get yourself a coffee or do some stretching :) Tip The process may hang at 99% for a long time, this is okay, just wait for it to complete 8.Remove the memory card after successful completion: Tip If an error occurs during flashing or booting PiKVM, repeat the process.","title":"Flashing OS"},{"location":"flashing_os/#flasing-the-os-image","text":"Micro-SD Card Requirements Minimum 16 Gb Class 10 is strongly recommended Why are there two versions of software, BLIKVM and PiKVM? What is the difference between the two versions? Which one should I choose? Can I use the official image of PiKVM? At the beginning of the BLIKVM project, the hardware was developed, and the software directly used PiKVM. With the continuous progress of the project, BLIKVM has developed its own software version of new architecture, which also lays the foundation for deeper cooperation with its own hardware; The core functions of BLIKVM and PiKVM are the same for users. Some subdivision functions are not the same. For example, BLIKVM supports multiple languages; Select according to your own use experience; You can use the PiKVM official image, but you need to make some adaptations according to the different hardware, mainly involving screens, fans, etc. Since the PiKVM official image is always updated, the specific adaptations need to be seen according to the specific situation you encounter at that time;","title":"Flasing the OS image"},{"location":"flashing_os/#download-the-image","text":"Users who need to run PiKVM on v4 by yourself can refer to this doc .","title":"Download the image"},{"location":"flashing_os/#blikvm-versions-and-software-image-compatibility","text":"The following BliKVM versions use the same BliKVM v1-3 software image: BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 Allwinner, uses a separate Allwinner BliKVM image. BliKVM v4 Web UI The web UI is consistent across all supported versions for easy remote administration.","title":"BliKVM Versions and Software Image Compatibility"},{"location":"flashing_os/#base-on-pikvm-software","text":"Raspberry 4B and CM4 board use different PiKVM software image. After entering the link, you can see the image named with each hardware version (HAT CM4 PCIe) PiKVM image","title":"Base on PiKVM software"},{"location":"flashing_os/#flash-the-image","text":"Tip Ignore request to format your sd card, this step is not nessessary. Choose the most suitable method for you. How to flash the eMMC on a Raspberry Pi Compute Module 4","title":"Flash the image"},{"location":"flashing_os/#board-link","text":"If you use a CM4 with eMMC (like the CM4102016). You can use the v1 or v2 board to flash the eMMC. If your CM4 doesn't have eMMC, your device can just use a SD card to boot from. You don't need to look into this any further. Just flash to the SD card instead. First, use the jumper cap to short the boot pin (allowing you flash the EMMC memory). If you use BLIKVM CM4 version Then connect the data cable to the USB OTG interface. Power on blikvm and observe the act light, the green light is always on. If you use BLIKVM PCIe version Then connect the data cable to the USB-PC interface. Power on blikvm and observe the ACT and PWR LED isn't light. After initialize EMMC through the usbboot/rpiboot, the ACT and PWR LED light is always on. EMMC knowledge If you use Raspberry Pi compute modules such as CM3 eMMC or CM4 eMMC version\uff0cyou can initialize eMMC through the usbboot project. Note that the eMMC board version cannot use the SD card to boot the image. Instead, you need to flash the eMMC storage by using the usbboot project that emulates USB Mass Storage Device (MSD). From this video you can learn how-to flash the image quickly. How to flash the eMMC on a Raspberry Pi Compute Module 4 video Taking Ubuntu system as an example:","title":"Board Link"},{"location":"flashing_os/#linux-usbboot","text":"If you use an Micro-SD Card, you can skip the following steps and go to the next chapter down below. sudo apt install git libusb-1.0-0-dev pkg-config build-essential git clone --depth = 1 https://github.com/raspberrypi/usbboot cd usbboot make sudo ./rpiboot If the content in the image below appears, that indicates that the eMMC initialization was successful. The next step is to flash the image to your eMMC chip.","title":"Linux usbboot"},{"location":"flashing_os/#flash-the-image-linux-macos-and-windows","text":"Please do not make any additional settings to the image in RPi Imager, as this will most likely cause the image to fail to boot or repeatedly restart. We are using the \"RPi Imager\" application to flash the image in this example. Download and install the latest version of RPi Imager . Run RPi Imager: Press CHOOSE OS and select Use custom image at bottom of the list: After clicking on this item, select the image file ( .img.xz ), then click CHOOSE STORAGE : Insert the memory card into the card reader. Choose the card reader from this list (or eMMC flash storage, in case you are using a Raspberry Pi Compute module with a eMMC chip). Be careful and choose the right device: After choosing the memory card, press the WRITE button. Confirm the operation when you are asked about it: Wait for the process to finish. Get yourself a coffee or do some stretching :) Tip The process may hang at 99% for a long time, this is okay, just wait for it to complete 8.Remove the memory card after successful completion: Tip If an error occurs during flashing or booting PiKVM, repeat the process.","title":"Flash the Image (Linux, MacOS and Windows)"},{"location":"hdmi-csi-i2s/","text":"HDMI to CSI&I2S bridge guide Convert HDMI signal acquisition into CSI signal and I2S audio signal. Currently, all platforms are supported (Zero, Pi3B, Pi4B, CM4, Pi5B), and the maximum capture resolution not only depends on the HDMI to CSI converter board you are using but also on the Raspberry Pi hardware version you have. Raspberry Pi hardware versions are primarily divided into two series, one supporting a maximum of 1080P60Hz and the other supporting a maximum of 1080P50Hz. The Raspberry Pi versions that support a maximum of 1080P60Hz are CM3, CM4, and Pi5B. The Raspberry Pi versions that support a maximum of 1080P50Hz are Zero, Zero 2, Pi3B, Pi4B, and so on. Introduction This module takes the incoming HDMI signal and converts it into a separate CSI signal and I2S audio signal. HDMI input supports up to 1080P60Hz. It works well on Raspberry Pi, there are three versions of this module in history (C779, C780, C790). C790 is the latest version. C790 has mitigated HDMI backpowering, and also has two csi channels and four csi channels at the same time. Features C790 Hardware Parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 4 CSI-2 channels & clock The CSI-2 interface, with 15 pin FPC seat, spacing 1.0 mm, is located on the front of the C790 module. The CSI-2 interface, with 22 pin FPC seat, spacing 0.5 mm, is located on the back of the C790 module. Size: 30 x 45 mm Install: 4 x M2.5 Power supply: 3.3V Weight: 10g Pi 4B only support 1080P50Hz, limited by the number of CSI-2 channels. CM4 support 1080P60HZ, So if you must use 1080P60Hz input, please use CM4 and C790 together. Interface C790 has two CSI output interfaces. In front of C790, the CSI-2 interface is 15 pin FPC seat, spacing 1.0 mm. In back of C790, the CSI-2 interface is 22 pin FPC seat, spacing 0.5 mm. Size Install C790 on Raspberry Pi for reference C780 C780A Hardware Parameters HDMI input: supports up to 1080P50Hz on Raspberry Pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install: 6 x M2.5 Power supply: 3.3V Weight: 10g C780B Hardware Parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 4 CSI-2 channels & clock CSI-2 interface: 22 pin FPC seat, spacing 0.5 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install: 6 x M2.5 Power supply: 3.3V Weight: 10g Interface The wiring of audio part is shown in Figure. Size The size of C780 is shown in the image below. There are 6 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. As shown in the image below, the user can directly fix the module on the Raspberry Pi Zero. C780 is designed to be broken, and the hole spacing before breaking can be perfectly installed with most series of Raspberry Pi. C779 Hardware Parameters HDMI input: supports up to 1080P50Hz on Raspberry Pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 35 x 50 mm Install: 4 x M2.5 Power supply: 3.3V Weight: 10g Size The size of C779 is shown in Figure. There are 4 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. CSI Interface Definitions The CSI (Camera Serial Interface) interfaces C779 and C780A have 15 pins each, while the C780B interface has 22 pins. The C790 interface is unique as it supports both 15 and 22 PIN configurations. Software Demo The use guide of C790/C780/C779 depends on the official Raspberry Pi OS version you are using. Different versions have different usage methods. If you have some questions, Join our BLIKVM Discord Community for Support, FAQ & News! To use the kernel drivers, please update your system. There are a few things that have changed with the 5.4 kernel, so these instructions are for 5.4 or later. If uname -a reports anything less, then fix this before proceeding. pi@raspberrypi:~ $ uname -a Linux raspberrypi 5 .10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. Update & upgrade the Raspberry Pi system (It will take a long time depend on the different country) sudo apt-get update sudo apt-get upgrade 2. Enable camera module (the camera is enabled by default in Raspberry pi Bullseys OS) sudo raspi-config sudo reboot Navigate to \u2018Interfacing Options\u2019 and hit Enter. Now select the \u2018Camera\u2019 option, and hit the Enter key to enable it. Select \u201cFinish\u201d and select to reboot your Raspberry Pi. reboot is important!! Due to the absence of hardware encoding on the Pi5B, the software usage instructions for Pi platforms are currently divided into two sections: Pi5B configuration and configuration for other Pi platforms. In platforms such as Zero, Zero 2, Pi3B, Pi4B, etc., there is a reference for testing HDMI to CSI module demo. Edit /boot/config.txt (that will need sudo) sudo nano /boot/config.txt Add the line: dtoverlay=tc358743 Add the line if your shield support audio like C780 or C790. dtoverlay=tc358743-audio If (and only if) you have a device such as the C780 or C790 that supports the 22pin connector with all 4 lanes wired out, and are using a Compute Module with the CAM1 connector that also has all 4 lanes wired up, you can use: dtoverlay=tc358743,4lane=1 Check the amount of memory assigned to the CMA heap with \u201cdmesg | grep cma\u201d. The first line should be along the lines of: pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 If it reports less than 96MB assigned to CMA, then edit /boot/cmdline.txt and add to the start of the line. Do NOT add any carriage returns. cma=96M Reboot. If all is well you should get a /dev/video0 device, and \u201cv4l2-ctl \u2013list-devices\u201d will tell you that it is provided by Unicam. After connecting all the cables, power on the Raspberry Pi, the C790 indicator light is normally green, and after opening the Raspberry Pi terminal, enter the following command: pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 This driver puts all the control in the hands of the user, or the user\u2019s application. By default there is no EDID loaded into the chip to allow it to tell the HDMI source what resolutions are supported. There are EDID editors around. If you create a file edid.txt, then you can push this to the device using the comment of edid.txt file: 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt #copy the above commend in edid.txt, save&exit; pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan The driver does NOT automatically switch to the resolution detected. Use the command: pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: You MUST set the timings via \u201cv4l2-ctl \u2013set-dv-bt-timings\u201d. You can pass in an index to the detected mode, or use: v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. The chip supports two formats \u2013 BGR3 (the default) and UYVY. BGR3 is 24bpp, and UYVY is YUV4:2:2 16bpp. Over the normal 2 CSI-2 lanes the data rate is such that BGR3 can run at a maximum of 1080p30, whilst UYVY will go up to 1080p50. Use the following command to select UYVY, however your application may override that. v4l2-ctl -v pixelformat=UYVY Check that the audio drivers / card is available to ALSA. pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1 means that the card number for the TC358743XBG is \u201c1\u201d and it might be different. Install GStreamer tool. sudo apt install gstreamer1.0-tools Check gstreamer tool version: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note: Different versions have different command line parameters, which is very annoying. Use gstreamer to record video and audio #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. foo.mkv is the output file. If your gstreamer is version 1.8 or above, you can try the following test command. In addition, alsasrc device=hw:1 represents the sound card of TC358743, you can use \u201carecord -l\u201d to query. #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: We recommend that you modify the above framerate parameter to the actual frame rate of your HDMI signal, the actual frame rate value is from the result of \u2018v4l2-ctl \u2013query-dv-timings\u2019 command. For the above HDMI device, because the frame rate is 60, so we modify the framerate parameter to 60 like the followint command. Record the video only: gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Record the video and audio: (if your shield supports audio also) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9) Pi5B platforms HDMI to CSI module test demo reference. In the following test, the CAM1 channel is used, and the input resolution is 1080P24Hz. During the Raspberry Pi 5B test, it was found that the EDID settings were invalid, so an HDMI emulator needs to be added to force the target to output HDMI. Otherwise, the Raspberry Pi 5B may not receive any input. Due to the lack of corresponding hardware encoding on the Raspberry Pi 5B, the image capture performance of the Raspberry Pi 5B + C790 is generally inferior to that of the Raspberry Pi 4B. Edit /boot/config.txt (sudo permission required). sudo nano /boot/config.txt Add the following content: dtoverlay=tc358743 If your modules (C780 and C790) support audio, add the following content to enable audio support. dtoverlay=tc358743-audio Reboot the Raspberry Pi and execute the following command to find the media node corresponding to the CSI as media0, under the rp1-cfe (platform: 1f00128000.csi) field: blikvm@blikvm:~ $ v4l2-ctl --list-devices pispbe (platform:1000880000.pisp_be): /dev/video20 /dev/video21 /dev/video22 /dev/video23 /dev/video24 /dev/video25 /dev/video26 /dev/video27 /dev/video28 /dev/video29 /dev/video30 /dev/video31 /dev/video32 /dev/video33 /dev/video34 /dev/video35 /dev/video36 /dev/video37 /dev/media1 /dev/media2 rp1-cfe (platform:1f00128000.csi): /dev/video0 /dev/video1 /dev/video2 /dev/video3 /dev/video4 /dev/video5 /dev/video6 /dev/video7 /dev/media0 rpivid (platform:rpivid): /dev/video19 /dev/media3 Locate the node corresponding to tc358743 as v4l-subdev2, and the pad0 of rp1-cfe-csi2_ch0 as video0: blikvm@blikvm:~ $ media-ctl -d /dev/media0 -p Media controller API version 6.1.63 Media device information ------------------------ driver rp1-cfe model rp1-cfe serial bus info platform:1f00128000.csi hw revision 0x114666 driver version 6.1.63 Device topology - entity 1: csi2 (8 pads, 8 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"tc358743 4-000f\":0 [ENABLED,IMMUTABLE] pad1: Sink [fmt:unknown/8192x1 field:none] pad2: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad3: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad4: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch0\":0 [] -> \"pisp-fe\":0 [] pad5: Source [fmt:unknown/8192x1 field:none] -> \"rp1-cfe-embedded\":0 [] pad6: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch2\":0 [] -> \"pisp-fe\":0 [] pad7: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch3\":0 [] -> \"pisp-fe\":0 [] - entity 10: pisp-fe (5 pads, 7 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: Sink [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"csi2\":4 [] <- \"csi2\":6 [] <- \"csi2\":7 [] pad1: Sink [fmt:FIXED/8192x1 field:none] <- \"rp1-cfe-fe_config\":0 [] pad2: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image0\":0 [] pad3: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image1\":0 [] pad4: Source [fmt:FIXED/8192x1 field:none] -> \"rp1-cfe-fe_stats\":0 [] - entity 16: tc358743 4-000f (1 pad, 1 link) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev2 pad0: Source [fmt:RGB888_1X24/640x480 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:640x350@13000000 max:1920x1200@165000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom] [dv.detect:BT.656/1120 1920x1080p24 (2750x1125) stds: flags:] [dv.current:BT.656/1120 640x480p59 (800x525) stds:CEA-861,DMT flags:has-cea861-vic] -> \"csi2\":0 [ENABLED,IMMUTABLE] - entity 18: rp1-cfe-csi2_ch0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 pad0: Sink <- \"csi2\":4 [] - entity 22: rp1-cfe-embedded (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- \"csi2\":5 [] - entity 26: rp1-cfe-csi2_ch2 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: Sink <- \"csi2\":6 [] - entity 30: rp1-cfe-csi2_ch3 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video3 pad0: Sink <- \"csi2\":7 [] - entity 34: rp1-cfe-fe_image0 (1 pad, 1 link) type Node subtype V4L flags 1 device node name /dev/video4 pad0: Sink <- \"pisp-fe\":2 [] - entity 38: rp1-cfe-fe_image1 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video5 pad0: Sink <- \"pisp-fe\":3 [] - entity 42: rp1-cfe-fe_stats (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video6 pad0: Sink <- \"pisp-fe\":4 [] - entity 46: rp1-cfe-fe_config (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video7 pad0: Source -> \"pisp-fe\":1 [] To query the current input source information, if the resolution displays as 0, it indicates that no input source signal has been detected. In this case, you should check the hardware connections and follow the steps mentioned above to troubleshoot. blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --query-dv-timings Active width: 1920 Active height: 1080 Total width: 2750 Total height: 1125 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (24.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 830 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 45 Vertical backporch: 0 Standards: Flags: Confirm the current input source information. blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --set-dv-bt-timings query BT timings set Initialize media0. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -r Connect CSI2's pad4 to rp1-cfe-csi2_ch0's pad0. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -l ''\\''csi2'\\'':4 -> '\\''rp1-cfe-csi2_ch0'\\'':0 [1]' Configure the media node. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':0 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':4 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' Set the output format. v4l2-ctl -v width=1920,height=1080,pixelformat=RGB3 Capture two frames for testing to verify if tc358743 is functioning properly. Other methods, such as using GStreamer, are not currently available. v4l2-ctl --verbose -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat='RGB3' --stream-mmap=4 --stream-skip=3 --stream-count=2 --stream-to=hdmiin.yuv --stream-poll If you have installed a desktop version of Raspberry Pi, you can use ffplay to directly play YUV files. ffplay -f rawvideo -video_size 1920x1080 -pixel_format bgr24 hdmiin.yuv On a Windows computer, you can use software like 7yuv to view .yuv files. For the tutorial with an input format of 1920 1080, you should select BGR888 in the top right corner of 7yuv and set the resolution to 1920 1080 to view the two frames you just captured. Chip Docs TC358743 Documentation Packing List C790 Test Video C780A Test C780B Test Purchase Link Purchase C780 & C790 Purchase C779","title":"HDMI to CSI & Audio"},{"location":"hdmi-csi-i2s/#hdmi-to-csii2s-bridge-guide","text":"Convert HDMI signal acquisition into CSI signal and I2S audio signal. Currently, all platforms are supported (Zero, Pi3B, Pi4B, CM4, Pi5B), and the maximum capture resolution not only depends on the HDMI to CSI converter board you are using but also on the Raspberry Pi hardware version you have. Raspberry Pi hardware versions are primarily divided into two series, one supporting a maximum of 1080P60Hz and the other supporting a maximum of 1080P50Hz. The Raspberry Pi versions that support a maximum of 1080P60Hz are CM3, CM4, and Pi5B. The Raspberry Pi versions that support a maximum of 1080P50Hz are Zero, Zero 2, Pi3B, Pi4B, and so on.","title":"HDMI to CSI&I2S bridge guide"},{"location":"hdmi-csi-i2s/#introduction","text":"This module takes the incoming HDMI signal and converts it into a separate CSI signal and I2S audio signal. HDMI input supports up to 1080P60Hz. It works well on Raspberry Pi, there are three versions of this module in history (C779, C780, C790). C790 is the latest version. C790 has mitigated HDMI backpowering, and also has two csi channels and four csi channels at the same time.","title":"Introduction"},{"location":"hdmi-csi-i2s/#features","text":"","title":"Features"},{"location":"hdmi-csi-i2s/#c790","text":"Hardware Parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 4 CSI-2 channels & clock The CSI-2 interface, with 15 pin FPC seat, spacing 1.0 mm, is located on the front of the C790 module. The CSI-2 interface, with 22 pin FPC seat, spacing 0.5 mm, is located on the back of the C790 module. Size: 30 x 45 mm Install: 4 x M2.5 Power supply: 3.3V Weight: 10g Pi 4B only support 1080P50Hz, limited by the number of CSI-2 channels. CM4 support 1080P60HZ, So if you must use 1080P60Hz input, please use CM4 and C790 together. Interface C790 has two CSI output interfaces. In front of C790, the CSI-2 interface is 15 pin FPC seat, spacing 1.0 mm. In back of C790, the CSI-2 interface is 22 pin FPC seat, spacing 0.5 mm. Size Install C790 on Raspberry Pi for reference","title":"C790"},{"location":"hdmi-csi-i2s/#c780","text":"C780A Hardware Parameters HDMI input: supports up to 1080P50Hz on Raspberry Pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install: 6 x M2.5 Power supply: 3.3V Weight: 10g C780B Hardware Parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 4 CSI-2 channels & clock CSI-2 interface: 22 pin FPC seat, spacing 0.5 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install: 6 x M2.5 Power supply: 3.3V Weight: 10g Interface The wiring of audio part is shown in Figure. Size The size of C780 is shown in the image below. There are 6 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. As shown in the image below, the user can directly fix the module on the Raspberry Pi Zero. C780 is designed to be broken, and the hole spacing before breaking can be perfectly installed with most series of Raspberry Pi.","title":"C780"},{"location":"hdmi-csi-i2s/#c779","text":"Hardware Parameters HDMI input: supports up to 1080P50Hz on Raspberry Pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 35 x 50 mm Install: 4 x M2.5 Power supply: 3.3V Weight: 10g Size The size of C779 is shown in Figure. There are 4 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws.","title":"C779"},{"location":"hdmi-csi-i2s/#csi-interface-definitions","text":"The CSI (Camera Serial Interface) interfaces C779 and C780A have 15 pins each, while the C780B interface has 22 pins. The C790 interface is unique as it supports both 15 and 22 PIN configurations.","title":"CSI Interface Definitions"},{"location":"hdmi-csi-i2s/#software-demo","text":"The use guide of C790/C780/C779 depends on the official Raspberry Pi OS version you are using. Different versions have different usage methods. If you have some questions, Join our BLIKVM Discord Community for Support, FAQ & News! To use the kernel drivers, please update your system. There are a few things that have changed with the 5.4 kernel, so these instructions are for 5.4 or later. If uname -a reports anything less, then fix this before proceeding. pi@raspberrypi:~ $ uname -a Linux raspberrypi 5 .10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. Update & upgrade the Raspberry Pi system (It will take a long time depend on the different country) sudo apt-get update sudo apt-get upgrade 2. Enable camera module (the camera is enabled by default in Raspberry pi Bullseys OS) sudo raspi-config sudo reboot Navigate to \u2018Interfacing Options\u2019 and hit Enter. Now select the \u2018Camera\u2019 option, and hit the Enter key to enable it. Select \u201cFinish\u201d and select to reboot your Raspberry Pi. reboot is important!! Due to the absence of hardware encoding on the Pi5B, the software usage instructions for Pi platforms are currently divided into two sections: Pi5B configuration and configuration for other Pi platforms. In platforms such as Zero, Zero 2, Pi3B, Pi4B, etc., there is a reference for testing HDMI to CSI module demo. Edit /boot/config.txt (that will need sudo) sudo nano /boot/config.txt Add the line: dtoverlay=tc358743 Add the line if your shield support audio like C780 or C790. dtoverlay=tc358743-audio If (and only if) you have a device such as the C780 or C790 that supports the 22pin connector with all 4 lanes wired out, and are using a Compute Module with the CAM1 connector that also has all 4 lanes wired up, you can use: dtoverlay=tc358743,4lane=1 Check the amount of memory assigned to the CMA heap with \u201cdmesg | grep cma\u201d. The first line should be along the lines of: pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 If it reports less than 96MB assigned to CMA, then edit /boot/cmdline.txt and add to the start of the line. Do NOT add any carriage returns. cma=96M Reboot. If all is well you should get a /dev/video0 device, and \u201cv4l2-ctl \u2013list-devices\u201d will tell you that it is provided by Unicam. After connecting all the cables, power on the Raspberry Pi, the C790 indicator light is normally green, and after opening the Raspberry Pi terminal, enter the following command: pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 This driver puts all the control in the hands of the user, or the user\u2019s application. By default there is no EDID loaded into the chip to allow it to tell the HDMI source what resolutions are supported. There are EDID editors around. If you create a file edid.txt, then you can push this to the device using the comment of edid.txt file: 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt #copy the above commend in edid.txt, save&exit; pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan The driver does NOT automatically switch to the resolution detected. Use the command: pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: You MUST set the timings via \u201cv4l2-ctl \u2013set-dv-bt-timings\u201d. You can pass in an index to the detected mode, or use: v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. The chip supports two formats \u2013 BGR3 (the default) and UYVY. BGR3 is 24bpp, and UYVY is YUV4:2:2 16bpp. Over the normal 2 CSI-2 lanes the data rate is such that BGR3 can run at a maximum of 1080p30, whilst UYVY will go up to 1080p50. Use the following command to select UYVY, however your application may override that. v4l2-ctl -v pixelformat=UYVY Check that the audio drivers / card is available to ALSA. pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1 means that the card number for the TC358743XBG is \u201c1\u201d and it might be different. Install GStreamer tool. sudo apt install gstreamer1.0-tools Check gstreamer tool version: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note: Different versions have different command line parameters, which is very annoying. Use gstreamer to record video and audio #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. foo.mkv is the output file. If your gstreamer is version 1.8 or above, you can try the following test command. In addition, alsasrc device=hw:1 represents the sound card of TC358743, you can use \u201carecord -l\u201d to query. #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: We recommend that you modify the above framerate parameter to the actual frame rate of your HDMI signal, the actual frame rate value is from the result of \u2018v4l2-ctl \u2013query-dv-timings\u2019 command. For the above HDMI device, because the frame rate is 60, so we modify the framerate parameter to 60 like the followint command. Record the video only: gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Record the video and audio: (if your shield supports audio also) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9) Pi5B platforms HDMI to CSI module test demo reference. In the following test, the CAM1 channel is used, and the input resolution is 1080P24Hz. During the Raspberry Pi 5B test, it was found that the EDID settings were invalid, so an HDMI emulator needs to be added to force the target to output HDMI. Otherwise, the Raspberry Pi 5B may not receive any input. Due to the lack of corresponding hardware encoding on the Raspberry Pi 5B, the image capture performance of the Raspberry Pi 5B + C790 is generally inferior to that of the Raspberry Pi 4B. Edit /boot/config.txt (sudo permission required). sudo nano /boot/config.txt Add the following content: dtoverlay=tc358743 If your modules (C780 and C790) support audio, add the following content to enable audio support. dtoverlay=tc358743-audio Reboot the Raspberry Pi and execute the following command to find the media node corresponding to the CSI as media0, under the rp1-cfe (platform: 1f00128000.csi) field: blikvm@blikvm:~ $ v4l2-ctl --list-devices pispbe (platform:1000880000.pisp_be): /dev/video20 /dev/video21 /dev/video22 /dev/video23 /dev/video24 /dev/video25 /dev/video26 /dev/video27 /dev/video28 /dev/video29 /dev/video30 /dev/video31 /dev/video32 /dev/video33 /dev/video34 /dev/video35 /dev/video36 /dev/video37 /dev/media1 /dev/media2 rp1-cfe (platform:1f00128000.csi): /dev/video0 /dev/video1 /dev/video2 /dev/video3 /dev/video4 /dev/video5 /dev/video6 /dev/video7 /dev/media0 rpivid (platform:rpivid): /dev/video19 /dev/media3 Locate the node corresponding to tc358743 as v4l-subdev2, and the pad0 of rp1-cfe-csi2_ch0 as video0: blikvm@blikvm:~ $ media-ctl -d /dev/media0 -p Media controller API version 6.1.63 Media device information ------------------------ driver rp1-cfe model rp1-cfe serial bus info platform:1f00128000.csi hw revision 0x114666 driver version 6.1.63 Device topology - entity 1: csi2 (8 pads, 8 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"tc358743 4-000f\":0 [ENABLED,IMMUTABLE] pad1: Sink [fmt:unknown/8192x1 field:none] pad2: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad3: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad4: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch0\":0 [] -> \"pisp-fe\":0 [] pad5: Source [fmt:unknown/8192x1 field:none] -> \"rp1-cfe-embedded\":0 [] pad6: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch2\":0 [] -> \"pisp-fe\":0 [] pad7: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch3\":0 [] -> \"pisp-fe\":0 [] - entity 10: pisp-fe (5 pads, 7 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: Sink [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"csi2\":4 [] <- \"csi2\":6 [] <- \"csi2\":7 [] pad1: Sink [fmt:FIXED/8192x1 field:none] <- \"rp1-cfe-fe_config\":0 [] pad2: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image0\":0 [] pad3: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image1\":0 [] pad4: Source [fmt:FIXED/8192x1 field:none] -> \"rp1-cfe-fe_stats\":0 [] - entity 16: tc358743 4-000f (1 pad, 1 link) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev2 pad0: Source [fmt:RGB888_1X24/640x480 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:640x350@13000000 max:1920x1200@165000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom] [dv.detect:BT.656/1120 1920x1080p24 (2750x1125) stds: flags:] [dv.current:BT.656/1120 640x480p59 (800x525) stds:CEA-861,DMT flags:has-cea861-vic] -> \"csi2\":0 [ENABLED,IMMUTABLE] - entity 18: rp1-cfe-csi2_ch0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 pad0: Sink <- \"csi2\":4 [] - entity 22: rp1-cfe-embedded (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- \"csi2\":5 [] - entity 26: rp1-cfe-csi2_ch2 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: Sink <- \"csi2\":6 [] - entity 30: rp1-cfe-csi2_ch3 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video3 pad0: Sink <- \"csi2\":7 [] - entity 34: rp1-cfe-fe_image0 (1 pad, 1 link) type Node subtype V4L flags 1 device node name /dev/video4 pad0: Sink <- \"pisp-fe\":2 [] - entity 38: rp1-cfe-fe_image1 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video5 pad0: Sink <- \"pisp-fe\":3 [] - entity 42: rp1-cfe-fe_stats (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video6 pad0: Sink <- \"pisp-fe\":4 [] - entity 46: rp1-cfe-fe_config (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video7 pad0: Source -> \"pisp-fe\":1 [] To query the current input source information, if the resolution displays as 0, it indicates that no input source signal has been detected. In this case, you should check the hardware connections and follow the steps mentioned above to troubleshoot. blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --query-dv-timings Active width: 1920 Active height: 1080 Total width: 2750 Total height: 1125 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (24.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 830 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 45 Vertical backporch: 0 Standards: Flags: Confirm the current input source information. blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --set-dv-bt-timings query BT timings set Initialize media0. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -r Connect CSI2's pad4 to rp1-cfe-csi2_ch0's pad0. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -l ''\\''csi2'\\'':4 -> '\\''rp1-cfe-csi2_ch0'\\'':0 [1]' Configure the media node. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':0 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':4 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' Set the output format. v4l2-ctl -v width=1920,height=1080,pixelformat=RGB3 Capture two frames for testing to verify if tc358743 is functioning properly. Other methods, such as using GStreamer, are not currently available. v4l2-ctl --verbose -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat='RGB3' --stream-mmap=4 --stream-skip=3 --stream-count=2 --stream-to=hdmiin.yuv --stream-poll If you have installed a desktop version of Raspberry Pi, you can use ffplay to directly play YUV files. ffplay -f rawvideo -video_size 1920x1080 -pixel_format bgr24 hdmiin.yuv On a Windows computer, you can use software like 7yuv to view .yuv files. For the tutorial with an input format of 1920 1080, you should select BGR888 in the top right corner of 7yuv and set the resolution to 1920 1080 to view the two frames you just captured.","title":"Software Demo"},{"location":"hdmi-csi-i2s/#chip-docs","text":"TC358743 Documentation","title":"Chip Docs"},{"location":"hdmi-csi-i2s/#packing-list","text":"C790","title":"Packing List"},{"location":"hdmi-csi-i2s/#test-video","text":"C780A Test C780B Test","title":"Test Video"},{"location":"hdmi-csi-i2s/#purchase-link","text":"Purchase C780 & C790 Purchase C779","title":"Purchase Link"},{"location":"hid/","text":"Video Mouse Keyboard Shortcuts After v1.4.5, custom shortcut keys are supported. Find the shortcuts configuration item, where key is the button name on the web UI and value is the specific button. sudo -s vim /mnt/exec/release/config/app.json ## default config\uff1a \"shortcuts\": { \"Ctrl+Alt+Del\": [\"ControlLeft\",\"AltLeft\",\"Delete\"], \"Alt+Tab\": [\"AltLeft\",\"Tab\"], \"Alt+F4\": [\"AltLeft\",\"F4\"], \"Alt+Enter\": [\"AltLeft\",\"Enter\"], \"Ctrl+W\": [\"ControlLeft\",\"KeyW\"] } The key names have uniqueness, and the specific key names are provided below \"{backspace}\": \"Backspace\", \"{tab}\": \"Tab\", \"{enter}\": \"Enter\", \"{shiftleft}\": \"ShiftLeft\", \"{shiftright}\": \"ShiftRight\", \"{altleft}\": \"AltLeft\", \"{altright}\": \"AltRight\", \"{prtscr}\": \"PrtScr\", \"{pause}\": \"Pause\", \"{scrolllock}\": \"ScrollLock\", \"{controlleft}\": \"ControlLeft\", \"{controlright}\": \"ControlRight\", \"{metaleft}\": \"MetaLeft\", \"{metaright}\": \"MetaRight\", \"{capslock}\": \"CapsLock\", \"{escape}\": \"Escape\", \"{space}\": \"Space\", \"{pageup}\": \"PageUp\", \"{pagedown}\": \"PageDown\", \"{end}\": \"End\", \"{home}\": \"Home\", \"{arrowleft}\": \"ArrowLeft\", \"{arrowup}\": \"ArrowUp\", \"{arrowright}\": \"ArrowRight\", \"{arrowdown}\": \"ArrowDown\", \"{insert}\": \"Insert\", \"{delete}\": \"Delete\", // Digits keys 1: \"Digit1\", 2: \"Digit2\", 3: \"Digit3\", 4: \"Digit4\", 5: \"Digit5\", 6: \"Digit6\", 7: \"Digit7\", 8: \"Digit8\", 9: \"Digit9\", 0: \"Digit0\", // \"!\": \"Digit1\", // ! maps to the '1' key \"@\": \"Digit2\", // @ maps to the '2' key \"#\": \"Digit3\", // # maps to the '3' key $: \"Digit4\", // $ maps to the '4' key \"%\": \"Digit5\", // % maps to the '5' key \"^\": \"Digit6\", // ^ maps to the '6' key \"&\": \"Digit7\", // & maps to the '7' key \"*\": \"Digit8\", // * maps to the '8' key \"(\": \"Digit9\", // ( maps to the '9' key \")\": \"Digit0\", // ) maps to the '0' key a: \"KeyA\", b: \"KeyB\", c: \"KeyC\", d: \"KeyD\", e: \"KeyE\", f: \"KeyF\", g: \"KeyG\", h: \"KeyH\", i: \"KeyI\", j: \"KeyJ\", k: \"KeyK\", l: \"KeyL\", m: \"KeyM\", n: \"KeyN\", o: \"KeyO\", p: \"KeyP\", q: \"KeyQ\", r: \"KeyR\", s: \"KeyS\", t: \"KeyT\", u: \"KeyU\", v: \"KeyV\", w: \"KeyW\", x: \"KeyX\", y: \"KeyY\", z: \"KeyZ\", // A: \"KeyA\", B: \"KeyB\", C: \"KeyC\", D: \"KeyD\", E: \"KeyE\", F: \"KeyF\", G: \"KeyG\", H: \"KeyH\", I: \"KeyI\", J: \"KeyJ\", K: \"KeyK\", L: \"KeyL\", M: \"KeyM\", N: \"KeyN\", O: \"KeyO\", P: \"KeyP\", Q: \"KeyQ\", R: \"KeyR\", S: \"KeyS\", T: \"KeyT\", U: \"KeyU\", V: \"KeyV\", W: \"KeyW\", X: \"KeyX\", Y: \"KeyY\", Z: \"KeyZ\", \"-\": \"Minus\", _: \"Minus\", \"=\": \"Equal\", \"+\": \"Equal\", \"[\": \"BracketLeft\", \"{\": \"BracketLeft\", \"]\": \"BracketRight\", \"}\": \"BracketRight\", \"|\": \"Backslash\", \"\\\\\": \"Backslash\", \"`\": \"Backquote\", \"~\": \"Backquote\", \";\": \"Semicolon\", \":\": \"Semicolon\", \"'\": \"Quote\", '\"': \"Quote\", \",\": \"Comma\", \"<\": \"Comma\", \".\": \"Period\", \">\": \"Period\", \"/\": \"Slash\", \"?\": \"Slash\", // Numpad keys \"{numpad0}\": \"Numpad0\", \"{numpad1}\": \"Numpad1\", \"{numpad2}\": \"Numpad2\", \"{numpad3}\": \"Numpad3\", \"{numpad4}\": \"Numpad4\", \"{numpad5}\": \"Numpad5\", \"{numpad6}\": \"Numpad6\", \"{numpad7}\": \"Numpad7\", \"{numpad8}\": \"Numpad8\", \"{numpad9}\": \"Numpad9\", \"{numlock}\": \"numlock\", \"{numpadmultiply}\": \"NumpadMultiply\", \"{numpadadd}\": \"NumpadAdd\", \"{numpadsubtract}\": \"NumpadSubtract\", \"{numpaddecimal}\": \"NumpadDecimal\", \"{numpaddivide}\": \"NumpadDivide\", \"{numpadenter}\": \"NumpadEnter\", // Function keys \"{f1}\": \"F1\", \"{f2}\": \"F2\", \"{f3}\": \"F3\", \"{f4}\": \"F4\", \"{f5}\": \"F5\", \"{f6}\": \"F6\", \"{f7}\": \"F7\", \"{f8}\": \"F8\", \"{f9}\": \"F9\", \"{f10}\": \"F10\", \"{f11}\": \"F11\", \"{f12}\": \"F12\"","title":"Keyboard"},{"location":"hid/#video-mouse-keyboard","text":"","title":"Video Mouse Keyboard"},{"location":"hid/#shortcuts","text":"After v1.4.5, custom shortcut keys are supported. Find the shortcuts configuration item, where key is the button name on the web UI and value is the specific button. sudo -s vim /mnt/exec/release/config/app.json ## default config\uff1a \"shortcuts\": { \"Ctrl+Alt+Del\": [\"ControlLeft\",\"AltLeft\",\"Delete\"], \"Alt+Tab\": [\"AltLeft\",\"Tab\"], \"Alt+F4\": [\"AltLeft\",\"F4\"], \"Alt+Enter\": [\"AltLeft\",\"Enter\"], \"Ctrl+W\": [\"ControlLeft\",\"KeyW\"] } The key names have uniqueness, and the specific key names are provided below \"{backspace}\": \"Backspace\", \"{tab}\": \"Tab\", \"{enter}\": \"Enter\", \"{shiftleft}\": \"ShiftLeft\", \"{shiftright}\": \"ShiftRight\", \"{altleft}\": \"AltLeft\", \"{altright}\": \"AltRight\", \"{prtscr}\": \"PrtScr\", \"{pause}\": \"Pause\", \"{scrolllock}\": \"ScrollLock\", \"{controlleft}\": \"ControlLeft\", \"{controlright}\": \"ControlRight\", \"{metaleft}\": \"MetaLeft\", \"{metaright}\": \"MetaRight\", \"{capslock}\": \"CapsLock\", \"{escape}\": \"Escape\", \"{space}\": \"Space\", \"{pageup}\": \"PageUp\", \"{pagedown}\": \"PageDown\", \"{end}\": \"End\", \"{home}\": \"Home\", \"{arrowleft}\": \"ArrowLeft\", \"{arrowup}\": \"ArrowUp\", \"{arrowright}\": \"ArrowRight\", \"{arrowdown}\": \"ArrowDown\", \"{insert}\": \"Insert\", \"{delete}\": \"Delete\", // Digits keys 1: \"Digit1\", 2: \"Digit2\", 3: \"Digit3\", 4: \"Digit4\", 5: \"Digit5\", 6: \"Digit6\", 7: \"Digit7\", 8: \"Digit8\", 9: \"Digit9\", 0: \"Digit0\", // \"!\": \"Digit1\", // ! maps to the '1' key \"@\": \"Digit2\", // @ maps to the '2' key \"#\": \"Digit3\", // # maps to the '3' key $: \"Digit4\", // $ maps to the '4' key \"%\": \"Digit5\", // % maps to the '5' key \"^\": \"Digit6\", // ^ maps to the '6' key \"&\": \"Digit7\", // & maps to the '7' key \"*\": \"Digit8\", // * maps to the '8' key \"(\": \"Digit9\", // ( maps to the '9' key \")\": \"Digit0\", // ) maps to the '0' key a: \"KeyA\", b: \"KeyB\", c: \"KeyC\", d: \"KeyD\", e: \"KeyE\", f: \"KeyF\", g: \"KeyG\", h: \"KeyH\", i: \"KeyI\", j: \"KeyJ\", k: \"KeyK\", l: \"KeyL\", m: \"KeyM\", n: \"KeyN\", o: \"KeyO\", p: \"KeyP\", q: \"KeyQ\", r: \"KeyR\", s: \"KeyS\", t: \"KeyT\", u: \"KeyU\", v: \"KeyV\", w: \"KeyW\", x: \"KeyX\", y: \"KeyY\", z: \"KeyZ\", // A: \"KeyA\", B: \"KeyB\", C: \"KeyC\", D: \"KeyD\", E: \"KeyE\", F: \"KeyF\", G: \"KeyG\", H: \"KeyH\", I: \"KeyI\", J: \"KeyJ\", K: \"KeyK\", L: \"KeyL\", M: \"KeyM\", N: \"KeyN\", O: \"KeyO\", P: \"KeyP\", Q: \"KeyQ\", R: \"KeyR\", S: \"KeyS\", T: \"KeyT\", U: \"KeyU\", V: \"KeyV\", W: \"KeyW\", X: \"KeyX\", Y: \"KeyY\", Z: \"KeyZ\", \"-\": \"Minus\", _: \"Minus\", \"=\": \"Equal\", \"+\": \"Equal\", \"[\": \"BracketLeft\", \"{\": \"BracketLeft\", \"]\": \"BracketRight\", \"}\": \"BracketRight\", \"|\": \"Backslash\", \"\\\\\": \"Backslash\", \"`\": \"Backquote\", \"~\": \"Backquote\", \";\": \"Semicolon\", \":\": \"Semicolon\", \"'\": \"Quote\", '\"': \"Quote\", \",\": \"Comma\", \"<\": \"Comma\", \".\": \"Period\", \">\": \"Period\", \"/\": \"Slash\", \"?\": \"Slash\", // Numpad keys \"{numpad0}\": \"Numpad0\", \"{numpad1}\": \"Numpad1\", \"{numpad2}\": \"Numpad2\", \"{numpad3}\": \"Numpad3\", \"{numpad4}\": \"Numpad4\", \"{numpad5}\": \"Numpad5\", \"{numpad6}\": \"Numpad6\", \"{numpad7}\": \"Numpad7\", \"{numpad8}\": \"Numpad8\", \"{numpad9}\": \"Numpad9\", \"{numlock}\": \"numlock\", \"{numpadmultiply}\": \"NumpadMultiply\", \"{numpadadd}\": \"NumpadAdd\", \"{numpadsubtract}\": \"NumpadSubtract\", \"{numpaddecimal}\": \"NumpadDecimal\", \"{numpaddivide}\": \"NumpadDivide\", \"{numpadenter}\": \"NumpadEnter\", // Function keys \"{f1}\": \"F1\", \"{f2}\": \"F2\", \"{f3}\": \"F3\", \"{f4}\": \"F4\", \"{f5}\": \"F5\", \"{f6}\": \"F6\", \"{f7}\": \"F7\", \"{f8}\": \"F8\", \"{f9}\": \"F9\", \"{f10}\": \"F10\", \"{f11}\": \"F11\", \"{f12}\": \"F12\"","title":"Shortcuts"},{"location":"https/","text":"Encryption Certificate From version v1.4.9, blikvm defaults to HTTPS. Even if you access via HTTP, it will automatically redirect to HTTPS: sudo -s vim /mnt/exec/release/config/app.json Find the following configuration content. The key and cert are located in the path /mnt/exec/release/lib/https/. Users can replace them as needed. \"server\": { \"ssl\": { \"key\": \"./lib/https/key.pem\", \"cert\": \"./lib/https/cert.pem\" }","title":"Encrypt certificates"},{"location":"https/#encryption-certificate","text":"From version v1.4.9, blikvm defaults to HTTPS. Even if you access via HTTP, it will automatically redirect to HTTPS: sudo -s vim /mnt/exec/release/config/app.json Find the following configuration content. The key and cert are located in the path /mnt/exec/release/lib/https/. Users can replace them as needed. \"server\": { \"ssl\": { \"key\": \"./lib/https/key.pem\", \"cert\": \"./lib/https/cert.pem\" }","title":"Encryption Certificate"},{"location":"make-image/","text":"Make your own image When you have made modifications to an image and want to create your own image, you can follow the steps below on Linux to create a minimal image. touch /mnt/tmp/firstboot > ~/.bash_history Firstly, use the gparted software to open the SD card of the image you want to create. Use gparted to partition the unused space and set it as unallocated. This ensures that this portion of empty space without any valid content is not included in the image creation. Next, use the fdisk command to view the size of the available space, as shown in the following image, which is 10151935. Then, use the dd command to write to an empty img file. Set the count value to be greater than the size of the volume end obtained from fdisk by at least 1. touch blikvm-armbian-v4-20230623.img sudo dd if = /dev/sdb of = ./blikvm-armbian-v4-20230623.img bs = 512 count = 10151936 Wait for the dd command to finish executing.","title":"Make Image"},{"location":"make-image/#make-your-own-image","text":"When you have made modifications to an image and want to create your own image, you can follow the steps below on Linux to create a minimal image. touch /mnt/tmp/firstboot > ~/.bash_history Firstly, use the gparted software to open the SD card of the image you want to create. Use gparted to partition the unused space and set it as unallocated. This ensures that this portion of empty space without any valid content is not included in the image creation. Next, use the fdisk command to view the size of the available space, as shown in the following image, which is 10151935. Then, use the dd command to write to an empty img file. Set the count value to be greater than the size of the volume end obtained from fdisk by at least 1. touch blikvm-armbian-v4-20230623.img sudo dd if = /dev/sdb of = ./blikvm-armbian-v4-20230623.img bs = 512 count = 10151936 Wait for the dd command to finish executing.","title":"Make your own image"},{"location":"modify_pikvm_image/","text":"Modifying PiKVM image to work with BliKVM hardware Because the blikvm hardware implementation scheme and PiKVM hardware implementation scheme are not exactly the same, you need to modify some errors through the following configuration for the official image of PiKVM. Of course, you can use the configured image . Fan config Since BliKVM's fan hardware is different to PiKVM's, you need to replace the control fan script first. The following default starting fan temperature is 40 degrees Celsius su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro Edit the /etc/kvmd/override.yaml file and add the following content to remove the web UI error warning about fans. kvmd: info: fan: unix: '' Check EDID file for 1080P60Hz input The function of the EDID file is to set the controlled computer to input according to the expected resolution. Since the image EDID file of PiKVM in different periods does not necessarily meet 1080P60Hz, when you use the CM4 version of hardware, it is found that the default output of the controlled computer is not 1080P60Hz, you can modify /etc/kvmd/tc358743-edid.hex to the following contents 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 make sure /boot/config.txt has the 4lane=1 entry in it for 1080p60hz support # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio If you use webrtc can't get audio, try to edit /etc/kvmd/janus/janus.plugin.ustreamer.jcfg to add audio support. audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" } OLED Follow the method below to enable OLED. If you use PiKVM official image, log in to PiKVM and run these commands: # rw # systemctl enable --now kvmd-oled //Enable OLED # ro If the oled still can't work, you need to check whether there has \"dtparam=i2c_arm=on\" in \"/boot/config.txt\" file, and whether there has \"i2c-dev\" in \"/etc/modules-load.d/i2c.conf\" file. If not, please create and add them. If it still does not work after the above configuration, please burn the image provided by blikvm for testing to check whether the OLED hardware is damaged. Config about v4mini image If you want to PiKVM v4mini image for blikvm v1 and v2, because v4mini image uses different gpio pins for ATX controls, so you will need the following override if you want to run v4mini image on your blikvm v1 or v2 version and be able to use ATX controls; if you don't make this change, ATX controls won't work properly (the led pins are different); Edit the /etc/kvmd/override.yaml file and add the following: kvmd: ### disable fan socket check ### info: fan: unix: '' atx: hdd_led_pin: 22 power_led_pin: 24 power_switch_pin: 23 reset_switch_pin: 27 type: gpio gpio: scheme: __v3_usb_breaker__: pin: 5 mode: output initial: false pulse: delay: 0","title":"Config for PiKVM OS"},{"location":"modify_pikvm_image/#modifying-pikvm-image-to-work-with-blikvm-hardware","text":"Because the blikvm hardware implementation scheme and PiKVM hardware implementation scheme are not exactly the same, you need to modify some errors through the following configuration for the official image of PiKVM. Of course, you can use the configured image .","title":"Modifying PiKVM image to work with BliKVM hardware"},{"location":"modify_pikvm_image/#fan-config","text":"Since BliKVM's fan hardware is different to PiKVM's, you need to replace the control fan script first. The following default starting fan temperature is 40 degrees Celsius su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro Edit the /etc/kvmd/override.yaml file and add the following content to remove the web UI error warning about fans. kvmd: info: fan: unix: ''","title":"Fan config"},{"location":"modify_pikvm_image/#check-edid-file-for-1080p60hz-input","text":"The function of the EDID file is to set the controlled computer to input according to the expected resolution. Since the image EDID file of PiKVM in different periods does not necessarily meet 1080P60Hz, when you use the CM4 version of hardware, it is found that the default output of the controlled computer is not 1080P60Hz, you can modify /etc/kvmd/tc358743-edid.hex to the following contents 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 make sure /boot/config.txt has the 4lane=1 entry in it for 1080p60hz support # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio If you use webrtc can't get audio, try to edit /etc/kvmd/janus/janus.plugin.ustreamer.jcfg to add audio support. audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" }","title":"Check EDID file for 1080P60Hz input"},{"location":"modify_pikvm_image/#oled","text":"Follow the method below to enable OLED. If you use PiKVM official image, log in to PiKVM and run these commands: # rw # systemctl enable --now kvmd-oled //Enable OLED # ro If the oled still can't work, you need to check whether there has \"dtparam=i2c_arm=on\" in \"/boot/config.txt\" file, and whether there has \"i2c-dev\" in \"/etc/modules-load.d/i2c.conf\" file. If not, please create and add them. If it still does not work after the above configuration, please burn the image provided by blikvm for testing to check whether the OLED hardware is damaged.","title":"OLED"},{"location":"modify_pikvm_image/#config-about-v4mini-image","text":"If you want to PiKVM v4mini image for blikvm v1 and v2, because v4mini image uses different gpio pins for ATX controls, so you will need the following override if you want to run v4mini image on your blikvm v1 or v2 version and be able to use ATX controls; if you don't make this change, ATX controls won't work properly (the led pins are different); Edit the /etc/kvmd/override.yaml file and add the following: kvmd: ### disable fan socket check ### info: fan: unix: '' atx: hdd_led_pin: 22 power_led_pin: 24 power_switch_pin: 23 reset_switch_pin: 27 type: gpio gpio: scheme: __v3_usb_breaker__: pin: 5 mode: output initial: false pulse: delay: 0","title":"Config about v4mini image"},{"location":"msd/","text":"Mass Storage Drive Reinstall the system Video BliKVM's USB device simulation feature allows you to remotely mount images on the virtual machine's mass storage drive, making it easy to install or reinstall operating systems and other software. This can be a useful feature for system administrators who need to manage multiple virtual machines remotely. By mounting an image on the mass storage drive, you can quickly and easily set up or configure a new virtual machine without having to physically connect a USB drive or other external storage device. Note: the size of the MSD is limited by the size of your sd card or eMMC module. Web UI The entrance to the MSD virtual USB drive is as follows: Using the web to upload images and create bootable drives are both synchronous processes. If you exit the MSD UI interface after uploading an image, you can resume the upload from where it left off the next time you select the same image. However, once you exit the bootable drive creation process, you cannot resume it; you will need to start over. The default upload path for images is /mnt/upload . If an upload fails, you can manually delete the cache files that were not successfully uploaded. Due to the large size of some image files, image uploads are divided into slices and then merged. The merging process cannot be resumed, so please ensure you wait for the merge to complete (which may take some time) before proceeding to the next step. Creating a bootable drive involves two steps: creating a virtual USB drive and copying the selected ISO image into the created virtual USB drive. Both steps have progress indicators. Please wait until both steps show 100% progress before clicking Next. Upload images manually (without Web UI) Confirm that the following four paths exist. If you are using the official latest image of blikvm, and it is fully configured, there is no need to check. /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy SSH logs in to blikvm, executes the rw command, and changes the system permission to writable. rw In your PC ,use scp cmd send iso file to kvm board. scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ excute msd cmd.wait until excute end. If you don't use option paramter\uff1a The default size of the USB flash disk is 5GB. The default filename is scan /mnt/msd/user dir. The default msd name is ventoy. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make If your iso is large than 5GB.You can specify the optional parameter - s xxx, xxx is the Size. If you need specify iso ,you can use -f xxx.iso. If you want to specify the msd name, you can use -n xxx. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso Tips: cp progresses slowly, please be patient. If you want to excute other cmd, you can use other option. c option contains : make/conn/disconn/clean Connect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn Disconnect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn Clean msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean Through the WebUI restart PC, enter BIOS, modify boot priority, set BliKVM USB first. According to the steps, select operating system, format partition and install.","title":"MSD"},{"location":"msd/#mass-storage-drive","text":"Reinstall the system Video BliKVM's USB device simulation feature allows you to remotely mount images on the virtual machine's mass storage drive, making it easy to install or reinstall operating systems and other software. This can be a useful feature for system administrators who need to manage multiple virtual machines remotely. By mounting an image on the mass storage drive, you can quickly and easily set up or configure a new virtual machine without having to physically connect a USB drive or other external storage device. Note: the size of the MSD is limited by the size of your sd card or eMMC module.","title":"Mass Storage Drive"},{"location":"msd/#web-ui","text":"The entrance to the MSD virtual USB drive is as follows: Using the web to upload images and create bootable drives are both synchronous processes. If you exit the MSD UI interface after uploading an image, you can resume the upload from where it left off the next time you select the same image. However, once you exit the bootable drive creation process, you cannot resume it; you will need to start over. The default upload path for images is /mnt/upload . If an upload fails, you can manually delete the cache files that were not successfully uploaded. Due to the large size of some image files, image uploads are divided into slices and then merged. The merging process cannot be resumed, so please ensure you wait for the merge to complete (which may take some time) before proceeding to the next step. Creating a bootable drive involves two steps: creating a virtual USB drive and copying the selected ISO image into the created virtual USB drive. Both steps have progress indicators. Please wait until both steps show 100% progress before clicking Next.","title":"Web UI"},{"location":"msd/#upload-images-manually-without-web-ui","text":"Confirm that the following four paths exist. If you are using the official latest image of blikvm, and it is fully configured, there is no need to check. /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy SSH logs in to blikvm, executes the rw command, and changes the system permission to writable. rw In your PC ,use scp cmd send iso file to kvm board. scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ excute msd cmd.wait until excute end. If you don't use option paramter\uff1a The default size of the USB flash disk is 5GB. The default filename is scan /mnt/msd/user dir. The default msd name is ventoy. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make If your iso is large than 5GB.You can specify the optional parameter - s xxx, xxx is the Size. If you need specify iso ,you can use -f xxx.iso. If you want to specify the msd name, you can use -n xxx. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso Tips: cp progresses slowly, please be patient. If you want to excute other cmd, you can use other option. c option contains : make/conn/disconn/clean Connect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn Disconnect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn Clean msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean Through the WebUI restart PC, enter BIOS, modify boot priority, set BliKVM USB first. According to the steps, select operating system, format partition and install.","title":"Upload images manually (without Web UI)"},{"location":"port-forwarding/","text":"Port forwarding After v1.4.7 version If your ISP provides an external IP address for the router, you can configure Port forwarding to access BliKVM: If the web interface uses the HTTP protocol and occupies port 80; If the web interface uses the HTTPS protocol and occupies port 443; If you do not have an external IP address, we suggest trying to use Tailscale VPN \u3002","title":"Port Forwarding"},{"location":"port-forwarding/#port-forwarding","text":"After v1.4.7 version If your ISP provides an external IP address for the router, you can configure Port forwarding to access BliKVM: If the web interface uses the HTTP protocol and occupies port 80; If the web interface uses the HTTPS protocol and occupies port 443; If you do not have an external IP address, we suggest trying to use Tailscale VPN \u3002","title":"Port forwarding"},{"location":"rtc/","text":"RTC Clock The purpose of an RTC (Real-Time Clock) is to provide real-time information about the current date and time for a device or system. It is an independent clock chip or module that has its own power source, allowing it to maintain accurate time even when the device is powered off or experiences a power outage. Due to shipping restrictions on international deliveries, the RTC hardware is shipped without a battery, and users need to purchase a CR1220 button cell battery themselves. The specific RTC clock model used in different versions of BliKVM may vary, and the usage methods may differ slightly. BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563 1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc0 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30 BliKVM V4 - pcf8563 1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc1 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"RTC clock"},{"location":"rtc/#rtc-clock","text":"The purpose of an RTC (Real-Time Clock) is to provide real-time information about the current date and time for a device or system. It is an independent clock chip or module that has its own power source, allowing it to maintain accurate time even when the device is powered off or experiences a power outage. Due to shipping restrictions on international deliveries, the RTC hardware is shipped without a battery, and users need to purchase a CR1220 button cell battery themselves. The specific RTC clock model used in different versions of BliKVM may vary, and the usage methods may differ slightly.","title":"RTC Clock"},{"location":"rtc/#blikvm-v2-pcie-and-blikvm-v3-hat-pcf8563","text":"1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc0 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563"},{"location":"rtc/#blikvm-v4-pcf8563","text":"1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc1 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V4 - pcf8563"},{"location":"serial_over_usb/","text":"Serial-over-USB connection The BliKVM device can be accessed through the serial port terminal. 1. For hardware connection, you should use the USB to TTL module to connect the USB of the computer to the uart of BliKVM. If you are using the Hat version, please connect the serial ports GPIO14 and GPIO15. If you are using the PCIe version, connect the GTR pin marked by the PCB 2. Install terminal login tools on the computer. For example, Putty for Windows 3. Use the Putty instructions. Enter the correct COM port. The default baud rate is 115200 . Select serial as the connection method, and then click Open\uff08Use PiKVM firmware as an example If your computer cannot correctly recognize the USB to TTL module, please follow the steps below to install the driver for your computer Connect the USB-A connector to your admin host (in this example, it's on a Windows host). As a result, Device Manager will show a new USB Serial device in Other Devices. Download and extract/run drivers. In this example, I downloaded and extracted the ZIP file. https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all Update driver for the new USB Serial device, point it to where you extracted the files, and click Next then Close. If done right, the new USB serial device should now show up under Ports as USB-SERIAL CH340 (COMX).","title":"Serial-over-USB"},{"location":"serial_over_usb/#serial-over-usb-connection","text":"The BliKVM device can be accessed through the serial port terminal. 1. For hardware connection, you should use the USB to TTL module to connect the USB of the computer to the uart of BliKVM. If you are using the Hat version, please connect the serial ports GPIO14 and GPIO15. If you are using the PCIe version, connect the GTR pin marked by the PCB 2. Install terminal login tools on the computer. For example, Putty for Windows 3. Use the Putty instructions. Enter the correct COM port. The default baud rate is 115200 . Select serial as the connection method, and then click Open\uff08Use PiKVM firmware as an example If your computer cannot correctly recognize the USB to TTL module, please follow the steps below to install the driver for your computer Connect the USB-A connector to your admin host (in this example, it's on a Windows host). As a result, Device Manager will show a new USB Serial device in Other Devices. Download and extract/run drivers. In this example, I downloaded and extracted the ZIP file. https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all Update driver for the new USB Serial device, point it to where you extracted the files, and click Next then Close. If done right, the new USB serial device should now show up under Ports as USB-SERIAL CH340 (COMX).","title":"Serial-over-USB connection"},{"location":"ssh/","text":"SSH Config Starting from version 1.4.7, the web interface supports direct access to the blikvm SSH terminal. The default username and password to access the terminal are blikvm/blikvm. If you have changed the password for this user, you will need to update the corresponding username and password in the app.json file. sudo -s vim /mnt/exec/release/config/app.json # Locate the following configuration and update it with your new credentials. \"sshUser\": \"blikvm\", \"sshPassword\": \"blikvm\"","title":"SSH Terminal"},{"location":"ssh/#ssh-config","text":"Starting from version 1.4.7, the web interface supports direct access to the blikvm SSH terminal. The default username and password to access the terminal are blikvm/blikvm. If you have changed the password for this user, you will need to update the corresponding username and password in the app.json file. sudo -s vim /mnt/exec/release/config/app.json # Locate the following configuration and update it with your new credentials. \"sshUser\": \"blikvm\", \"sshPassword\": \"blikvm\"","title":"SSH Config"},{"location":"static_ip/","text":"Set static IP To configure a static IP address on a BliKVM image, you can follow these steps: v1 v2 v3 versions - Debian SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/dhcpcd.conf Within the file, locate the section that starts with # Example static IP configuration . Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: interface eth0 static ip_address = 192 .168.1.100/24 static routers = 192 .168.1.1 static domain_name_servers = 192 .168.1.1 Adjust the values according to your network configuration. Save the changes. Restart the BliKVM for the changes to take effect: sudo reboot v4 version - armbian SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/network/interfaces Within the file, locate the section that starts with # Example static IP configuration . Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: source /etc/network/interfaces.d/* auto eth0 allow-hotplug eth0 iface eth0 inet static address 192 .168.0.100 netmask 255 .255.255.0 gateway 192 .168.0.1 dns-nameservers 192 .168.0.1 Adjust the values according to your network configuration. Save the changes. Restart the BliKVM for the changes to take effect: sudo reboot After the reboot, your BliKVM will use the configured static IP address instead of obtaining one dynamically from a DHCP server. Make sure the static IP address you choose is not already assigned to another device on the network and is within the same subnet.","title":"Set Static IP "},{"location":"static_ip/#set-static-ip","text":"To configure a static IP address on a BliKVM image, you can follow these steps:","title":"Set static IP"},{"location":"static_ip/#v1-v2-v3-versions-debian","text":"SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/dhcpcd.conf Within the file, locate the section that starts with # Example static IP configuration . Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: interface eth0 static ip_address = 192 .168.1.100/24 static routers = 192 .168.1.1 static domain_name_servers = 192 .168.1.1 Adjust the values according to your network configuration. Save the changes. Restart the BliKVM for the changes to take effect: sudo reboot","title":"v1 v2 v3 versions - Debian"},{"location":"static_ip/#v4-version-armbian","text":"SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/network/interfaces Within the file, locate the section that starts with # Example static IP configuration . Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: source /etc/network/interfaces.d/* auto eth0 allow-hotplug eth0 iface eth0 inet static address 192 .168.0.100 netmask 255 .255.255.0 gateway 192 .168.0.1 dns-nameservers 192 .168.0.1 Adjust the values according to your network configuration. Save the changes. Restart the BliKVM for the changes to take effect: sudo reboot After the reboot, your BliKVM will use the configured static IP address instead of obtaining one dynamically from a DHCP server. Make sure the static IP address you choose is not already assigned to another device on the network and is within the same subnet.","title":"v4 version - armbian"},{"location":"tailscale/","text":"Tailscale VPN Tailscale can be used to access your BliKVM from the public internet. It is a convenient and free networking tool for setting up a small VPN network. This document provides an example for accessing your BliKVM over the internet, but you can also use Zerotier or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the Tailscale documentation. BliKVM Installation First, make sure that your system has read-write access. If it's a read-only system, use the rw command to make it writable. Then, proceed with the Tailscale installation by running the following command: curl -fsSL https://tailscale.com/install.sh | sh Note that in some regions, such as China, downloading Tailscale directly might be problematic due to network restrictions. Please configure your network accordingly. Adding BliKVM to your Tailscale Network Register an account on the Tailscale website and generate your own keys in the settings. On the BliKVM terminal, use the following command to add BliKVM to your Tailscale network: sudo tailscale up --authkey = your-auth-key --accept-routes If everything goes well, you can run ip addr show tailscale0 on the BliKVM terminal to view the IP address assigned by Tailscale for the virtual network. Here's an example output: 3 : tailscale0: mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100 .126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever The IP address, such as 100.126.223.28 , can be used to access the BliKVM web interface from your host machine. Host Installation Download and install Tailscale from the Tailscale website on your controlling host machine. Log in with your Tailscale account, and then you can check the Tailscale admin page to verify if both your machines are online. Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://","title":"Tailscale VPN"},{"location":"tailscale/#tailscale-vpn","text":"Tailscale can be used to access your BliKVM from the public internet. It is a convenient and free networking tool for setting up a small VPN network. This document provides an example for accessing your BliKVM over the internet, but you can also use Zerotier or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the Tailscale documentation.","title":"Tailscale VPN"},{"location":"tailscale/#blikvm-installation","text":"First, make sure that your system has read-write access. If it's a read-only system, use the rw command to make it writable. Then, proceed with the Tailscale installation by running the following command: curl -fsSL https://tailscale.com/install.sh | sh Note that in some regions, such as China, downloading Tailscale directly might be problematic due to network restrictions. Please configure your network accordingly.","title":"BliKVM Installation"},{"location":"tailscale/#adding-blikvm-to-your-tailscale-network","text":"Register an account on the Tailscale website and generate your own keys in the settings. On the BliKVM terminal, use the following command to add BliKVM to your Tailscale network: sudo tailscale up --authkey = your-auth-key --accept-routes If everything goes well, you can run ip addr show tailscale0 on the BliKVM terminal to view the IP address assigned by Tailscale for the virtual network. Here's an example output: 3 : tailscale0: mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100 .126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever The IP address, such as 100.126.223.28 , can be used to access the BliKVM web interface from your host machine.","title":"Adding BliKVM to your Tailscale Network"},{"location":"tailscale/#host-installation","text":"Download and install Tailscale from the Tailscale website on your controlling host machine. Log in with your Tailscale account, and then you can check the Tailscale admin page to verify if both your machines are online. Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://","title":"Host Installation"},{"location":"update/","text":"Software update introduction If you are running an older version then we recommend first reflashing and subsequently running the update process, while you are next to your BliKVM device. Introduction The currently available versions of the BLIKVM project are hosted in the release package of the GitHub. The update software function needs to keep the device connected. There are currently two ways to update the software. Method 1: Click the update button through the web interface, and the program will be updated automatically. A restart is required after the update. Method 2: Manually run the script on the KVM terminal to update, and restart after the update. Common causes of upgrade errors The device is not connected to the network; Network access to GitHub is limited; We strongly recommend performing the update while you are in close proximity to the BliKVM hardware you are upgrading. This way if anything goes wrong you can intervene. If you are familiar with command-line operations, we recommend manually updating so that you can monitor the command-line status in real time. If the update is abnormal and the web interface cannot exit the update status, use ssh to get you a terminal and reboot to recover. Manually run the script to update In the terminal\uff0cif the system terminal shows the ro keyword that means your system is currently in read-only, it is necessary to use the rw command to make the system writable. sudo -i curl -L https://raw.githubusercontent.com/ThomasVon2021/blikvm/master/script/update.py -o /tmp/update.py && python3 /tmp/update.py Observe the output of the terminal. When you see the message of a successful upgrade, enter in the terminal the: reboot command and the reboot should take effect. If you are unable to update successfully due to network issues, you can download the latest release.tar.gz package on another PC with a stable network connection and follow the instructions below for installation. Download Address: https://github.com/ThomasVon2021/blikvm/releases v1 v2 v3 hardware use release.tar.gz v4 hardware use release-h616-v4.tar.gz SSH into the device terminal and use tar -zxvf release.tar.gz to extract the release.tar.gz file. sudo -i cd /your release path/ python3 install_release.py --releasepath=./ You can compare the versions before and after in /usr/bin/blikvm/package.json . If you have upgraded to the specified version, the installation is successful, and you can reboot for the changes to take effect.","title":"Upgrade"},{"location":"update/#software-update-introduction","text":"If you are running an older version then we recommend first reflashing and subsequently running the update process, while you are next to your BliKVM device.","title":"Software update introduction"},{"location":"update/#introduction","text":"The currently available versions of the BLIKVM project are hosted in the release package of the GitHub. The update software function needs to keep the device connected. There are currently two ways to update the software. Method 1: Click the update button through the web interface, and the program will be updated automatically. A restart is required after the update. Method 2: Manually run the script on the KVM terminal to update, and restart after the update. Common causes of upgrade errors The device is not connected to the network; Network access to GitHub is limited; We strongly recommend performing the update while you are in close proximity to the BliKVM hardware you are upgrading. This way if anything goes wrong you can intervene. If you are familiar with command-line operations, we recommend manually updating so that you can monitor the command-line status in real time. If the update is abnormal and the web interface cannot exit the update status, use ssh to get you a terminal and reboot to recover.","title":"Introduction"},{"location":"update/#manually-run-the-script-to-update","text":"In the terminal\uff0cif the system terminal shows the ro keyword that means your system is currently in read-only, it is necessary to use the rw command to make the system writable. sudo -i curl -L https://raw.githubusercontent.com/ThomasVon2021/blikvm/master/script/update.py -o /tmp/update.py && python3 /tmp/update.py Observe the output of the terminal. When you see the message of a successful upgrade, enter in the terminal the: reboot command and the reboot should take effect. If you are unable to update successfully due to network issues, you can download the latest release.tar.gz package on another PC with a stable network connection and follow the instructions below for installation. Download Address: https://github.com/ThomasVon2021/blikvm/releases v1 v2 v3 hardware use release.tar.gz v4 hardware use release-h616-v4.tar.gz SSH into the device terminal and use tar -zxvf release.tar.gz to extract the release.tar.gz file. sudo -i cd /your release path/ python3 install_release.py --releasepath=./ You can compare the versions before and after in /usr/bin/blikvm/package.json . If you have upgraded to the specified version, the installation is successful, and you can reboot for the changes to take effect.","title":"Manually run the script to update"},{"location":"usb-splitter-guide/","text":"USB/PWR Splitter guide 1. Introduction The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage. 2.Mechanical Diagram 3.Test video USB splitter Video 4.3D printable case A simple snap fit case for the USB splitter. Download file","title":"USB Splitter"},{"location":"usb-splitter-guide/#usbpwr-splitter-guide","text":"","title":"USB/PWR Splitter guide"},{"location":"usb-splitter-guide/#1-introduction","text":"The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage.","title":"1. Introduction"},{"location":"usb-splitter-guide/#2mechanical-diagram","text":"","title":"2.Mechanical Diagram"},{"location":"usb-splitter-guide/#3test-video","text":"USB splitter Video","title":"3.Test video"},{"location":"usb-splitter-guide/#43d-printable-case","text":"A simple snap fit case for the USB splitter. Download file","title":"4.3D printable case"},{"location":"wake-on-lan/","text":"Wake-on-LAN Introduction Wake-on-LAN, abbreviated as WOL or WoL, is a feature that allows a computer that is in sleep or shutdown state to be powered on remotely by KVM through a local network by sending a specific message. WoL requires support from the controlled computer; otherwise, the feature won't work. Additionally, it needs to be ensured that WoL is enabled and configured correctly. With this feature, you can power on the computer without needing to use the ATX function. If users encounter anomalies when using KVM's WoL, they can try testing it using software that supports WoL. How to Use","title":"Wake-on-LAN"},{"location":"wake-on-lan/#wake-on-lan","text":"","title":"Wake-on-LAN"},{"location":"wake-on-lan/#introduction","text":"Wake-on-LAN, abbreviated as WOL or WoL, is a feature that allows a computer that is in sleep or shutdown state to be powered on remotely by KVM through a local network by sending a specific message. WoL requires support from the controlled computer; otherwise, the feature won't work. Additionally, it needs to be ensured that WoL is enabled and configured correctly. With this feature, you can power on the computer without needing to use the ATX function. If users encounter anomalies when using KVM's WoL, they can try testing it using software that supports WoL.","title":"Introduction"},{"location":"wake-on-lan/#how-to-use","text":"","title":"How to Use"},{"location":"wifi/","text":"Wifi Configure Because BLIKVM has many kinds of hardware and supports different OS, such as BLIKVM OS and PiKVM OS, different OS confifure wifi methods may not be the same. Please confirm the hardware and OS usage before using the method in this document. Please confirm that the hardware you use supports wifi function, for example, the CM400200 version does not have wifi function; If the SOC of KVM hardware is CM4, please confirm whether wifi antenna is connected; PiKVM OS is arch linux; BLIKVM OS raspberry pi series is debian system, and v4 series is armbian system; v1 v2 v3 Use raspi-config for Wi-Fi config on Raspberry Pi Debian systems Log in to SSH. Command: ssh blikvm@ip Mount the system as writable. Command: rw Start raspi-config. Command: sudo raspi-config Select System Options Select Wireless LAN Select the country where Wi-Fi is located, and China will select CN. If it has been set before, this step will skip to 7 Enter the Wi-Fi SSID (name) Enter the Wi-Fi password. If there is no password, press Enter directly At this time, you will return to the interface in Step 4, press the tab key to select Finish , then press Enter Check whether to connect to wifi. Command: ifconfig wlan0. If you see the ip obtained, you are connected Mount the system as read-only. Command: ro v4 Hardware using Armbian System with armbian-config Log in via SSH using the command: ssh blikvm@ip to access the Armbian system. Enter the following command to launch the armbian-config tool: sudo armbian-config In the armbian-config menu, navigate and select options using the arrow keys and press Enter . Scroll down to the \"Network\" option using the arrow keys and press Enter to enter the submenu. In the \"Network\" submenu, select the \"Wireless\" option and press Enter to enter the Wi-Fi configuration menu. In the Wi-Fi configuration menu, select the \"Connect to Wi-Fi\" option and press Enter to enter the Wi-Fi connection setup. armbian-config will list the available wireless interfaces and already configured networks. Select the wireless interface you want to connect to and press Enter . armbian-config will display the list of available Wi-Fi networks. Use the arrow keys to select the Wi-Fi network you want to connect to and press Enter . If the Wi-Fi network is password-protected, armbian-config will prompt you to enter the Wi-Fi password. Enter the password and press Enter . Wait for a moment while the Armbian system attempts to connect to the specified Wi-Fi network. If the connection is successful, you will see a corresponding message on the screen. Exit the armbian-config tool. Please note that the menu options and configurations mentioned above may vary slightly depending on the specific version of the Armbian system. Make sure to follow the appropriate steps based on your system version and configuration.","title":"Wifi Config"},{"location":"wifi/#wifi-configure","text":"Because BLIKVM has many kinds of hardware and supports different OS, such as BLIKVM OS and PiKVM OS, different OS confifure wifi methods may not be the same. Please confirm the hardware and OS usage before using the method in this document. Please confirm that the hardware you use supports wifi function, for example, the CM400200 version does not have wifi function; If the SOC of KVM hardware is CM4, please confirm whether wifi antenna is connected; PiKVM OS is arch linux; BLIKVM OS raspberry pi series is debian system, and v4 series is armbian system;","title":"Wifi Configure"},{"location":"wifi/#v1-v2-v3-use-raspi-config-for-wi-fi-config-on-raspberry-pi-debian-systems","text":"Log in to SSH. Command: ssh blikvm@ip Mount the system as writable. Command: rw Start raspi-config. Command: sudo raspi-config Select System Options Select Wireless LAN Select the country where Wi-Fi is located, and China will select CN. If it has been set before, this step will skip to 7 Enter the Wi-Fi SSID (name) Enter the Wi-Fi password. If there is no password, press Enter directly At this time, you will return to the interface in Step 4, press the tab key to select Finish , then press Enter Check whether to connect to wifi. Command: ifconfig wlan0. If you see the ip obtained, you are connected Mount the system as read-only. Command: ro","title":"v1 v2 v3 Use raspi-config for Wi-Fi config on Raspberry Pi Debian systems"},{"location":"wifi/#v4-hardware-using-armbian-system-with-armbian-config","text":"Log in via SSH using the command: ssh blikvm@ip to access the Armbian system. Enter the following command to launch the armbian-config tool: sudo armbian-config In the armbian-config menu, navigate and select options using the arrow keys and press Enter . Scroll down to the \"Network\" option using the arrow keys and press Enter to enter the submenu. In the \"Network\" submenu, select the \"Wireless\" option and press Enter to enter the Wi-Fi configuration menu. In the Wi-Fi configuration menu, select the \"Connect to Wi-Fi\" option and press Enter to enter the Wi-Fi connection setup. armbian-config will list the available wireless interfaces and already configured networks. Select the wireless interface you want to connect to and press Enter . armbian-config will display the list of available Wi-Fi networks. Use the arrow keys to select the Wi-Fi network you want to connect to and press Enter . If the Wi-Fi network is password-protected, armbian-config will prompt you to enter the Wi-Fi password. Enter the password and press Enter . Wait for a moment while the Armbian system attempts to connect to the specified Wi-Fi network. If the connection is successful, you will see a corresponding message on the screen. Exit the armbian-config tool. Please note that the menu options and configurations mentioned above may vary slightly depending on the specific version of the Armbian system. Make sure to follow the appropriate steps based on your system version and configuration.","title":"v4 Hardware using Armbian System with armbian-config"},{"location":"zerotier/","text":"ZeroTier VPN ZeroTier allows secure access to your BliKVM even throught NAT on both sides. It lets you build modern, secure multi-point virtualized networks of almost any type. This document provides an example for accessing your BliKVM over the internet, but you can also use Tailscale or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the ZeroTier documentation . Installing ZeroTier on BliKVM First of all, prepare account and VPN network at ZeroTier with instructions here: Create a Network , save Network ID for later usage. Next, connect with BliKVM terminal using SSH protocol, and check for read-write access. If it's a read-only system, use the rw command to make it writable. Now install ZeroTier client using the command below: curl -s https://install.zerotier.com | sudo bash Note that in some regions, such as China, downloading ZeroTier directly might be problematic due to network restrictions. Please configure your network accordingly. Adding BliKVM to your ZeroTier Network On the BliKVM terminal, use the following command to add BliKVM to your ZeroTier network (using your ZeoroTier Network ID, for example d5e04297a16fa690): sudo zerotier-cli join d5e04297a16fa690 If everything goes well, you can run ip addr show zerotier network device (name is starting with zt) on the BliKVM terminal to view the IP address assigned by ZeroTier for the virtual network. Here's an example output: 3 : zt6ovrlscs: mtu 2800 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether d6:e4:eb:ae:db:64 brd ff:ff:ff:ff:ff:ff inet 172 .25.96.75/16 brd 172 .25.255.255 scope global zt6ovrlscs valid_lft forever preferred_lft forever inet6 fe80::d4e4:ebff:feae:db64/64 scope link valid_lft forever preferred_lft forever The IP address, such as 172.25.96.75 , can be used to access the BliKVM web interface from your host machine. Installing ZeroTier on client computer Go to Download section at ZeroTier website and install ZeroTier on your controlling host machine. Join your ZeroTier Network ID, and then you can check your network page to verify if both your machines are online. Check if they are authorzied to connect to network there (Auth? column). Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://","title":"ZeroTier VPN"},{"location":"zerotier/#zerotier-vpn","text":"ZeroTier allows secure access to your BliKVM even throught NAT on both sides. It lets you build modern, secure multi-point virtualized networks of almost any type. This document provides an example for accessing your BliKVM over the internet, but you can also use Tailscale or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the ZeroTier documentation .","title":"ZeroTier VPN"},{"location":"zerotier/#installing-zerotier-on-blikvm","text":"First of all, prepare account and VPN network at ZeroTier with instructions here: Create a Network , save Network ID for later usage. Next, connect with BliKVM terminal using SSH protocol, and check for read-write access. If it's a read-only system, use the rw command to make it writable. Now install ZeroTier client using the command below: curl -s https://install.zerotier.com | sudo bash Note that in some regions, such as China, downloading ZeroTier directly might be problematic due to network restrictions. Please configure your network accordingly.","title":"Installing ZeroTier on BliKVM"},{"location":"zerotier/#adding-blikvm-to-your-zerotier-network","text":"On the BliKVM terminal, use the following command to add BliKVM to your ZeroTier network (using your ZeoroTier Network ID, for example d5e04297a16fa690): sudo zerotier-cli join d5e04297a16fa690 If everything goes well, you can run ip addr show zerotier network device (name is starting with zt) on the BliKVM terminal to view the IP address assigned by ZeroTier for the virtual network. Here's an example output: 3 : zt6ovrlscs: mtu 2800 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether d6:e4:eb:ae:db:64 brd ff:ff:ff:ff:ff:ff inet 172 .25.96.75/16 brd 172 .25.255.255 scope global zt6ovrlscs valid_lft forever preferred_lft forever inet6 fe80::d4e4:ebff:feae:db64/64 scope link valid_lft forever preferred_lft forever The IP address, such as 172.25.96.75 , can be used to access the BliKVM web interface from your host machine.","title":"Adding BliKVM to your ZeroTier Network"},{"location":"zerotier/#installing-zerotier-on-client-computer","text":"Go to Download section at ZeroTier website and install ZeroTier on your controlling host machine. Join your ZeroTier Network ID, and then you can check your network page to verify if both your machines are online. Check if they are authorzied to connect to network there (Auth? column). Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://","title":"Installing ZeroTier on client computer"}]} \ No newline at end of file +{"config":{"indexing":"full","lang":["en","ja","ru"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"BLIKVM Overview BLIKVM is an open-source KVM, it has four versions: v1 CM4, v2 PCIe, v3 HAT and the v4 Allwinner. This device helps to manage servers or workstations remotely, regardless of the health of the operating system or whether one is installed. You can fix any problem, configure the BIOS, and even reinstall the OS using the virtual CD-ROM or Flash Drive. Unlike software-based remote management, you don't need to install any software on the controlled computer, providing non-intrusive control. Here you will find comprehensive information about all aspects of the operation of BLIKVM. Join our BLIKVM Discord Community for Support, FAQ & News! FEATURE BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 /H313 SOC Raspberry CM4 Raspberry CM4 Raspberry 4B Allwinner H616/H313 Supported resolutions 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI Capture TC358743 TC358743 TC358743 MS2131 HDMI Loop Through No No No Yes POE No Yes Yes Yes DC-IN No No No Yes USB-C Power Yes Yes Yes Yes USB Power/Data Splitter Yes Yes(external) Yes Yes Serial Console No Yes Yes Yes ATX controls Yes Yes Yes Yes BIOS controls Yes Yes Yes Yes Open source system Yes Yes Yes Yes Reinstall the controlled computer system Yes Yes Yes Yes FAN Yes(Not support PWM controls) Yes Yes Optional(default with heat sink) Display Module OLED 128x64 white OLED 128x32 white OLED 128x64 white LCD 240x240 color Real Time Clock Yes(DS1307) Yes(PCF8563) Yes(PCF8563) Yes(PCF8563) Case Metallic Black No Metallic Black White Blue Orange(1U rack compatible) Metallic Black(1U rack compatible) Buzzer No No No Yes Custom button No No No Yes Software update Yes Yes Yes Yes 32GB SD Card Yes (OS included) Yes (OS included) Yes (OS included) Yes (OS included) HDMI backpower mitigation No Yes Yes Yes Professional technical support Yes Yes Yes Yes Features Video capture (1080P 60Hz) Keyboard forwarding Mouse forwarding ATX Fan Control Fullscreen mode Paste text from clipboard VPN support Mass Storage Drive (emulate a CD-ROM or Flash Drive) Multiport KVM over IP OLED to display system info, like temp, uptime, IP Password authentication Support multiple languages Wake-on-LAN Guides 1. BLIKVM v1 CM4 version 2. BLIKVM v2 PCIE version 3. BLIKVM v3 HAT version 4. BliKVM v4 Allwinner version","title":"BLIKVM Overview"},{"location":"#blikvm-overview","text":"BLIKVM is an open-source KVM, it has four versions: v1 CM4, v2 PCIe, v3 HAT and the v4 Allwinner. This device helps to manage servers or workstations remotely, regardless of the health of the operating system or whether one is installed. You can fix any problem, configure the BIOS, and even reinstall the OS using the virtual CD-ROM or Flash Drive. Unlike software-based remote management, you don't need to install any software on the controlled computer, providing non-intrusive control. Here you will find comprehensive information about all aspects of the operation of BLIKVM. Join our BLIKVM Discord Community for Support, FAQ & News! FEATURE BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 /H313 SOC Raspberry CM4 Raspberry CM4 Raspberry 4B Allwinner H616/H313 Supported resolutions 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI Capture TC358743 TC358743 TC358743 MS2131 HDMI Loop Through No No No Yes POE No Yes Yes Yes DC-IN No No No Yes USB-C Power Yes Yes Yes Yes USB Power/Data Splitter Yes Yes(external) Yes Yes Serial Console No Yes Yes Yes ATX controls Yes Yes Yes Yes BIOS controls Yes Yes Yes Yes Open source system Yes Yes Yes Yes Reinstall the controlled computer system Yes Yes Yes Yes FAN Yes(Not support PWM controls) Yes Yes Optional(default with heat sink) Display Module OLED 128x64 white OLED 128x32 white OLED 128x64 white LCD 240x240 color Real Time Clock Yes(DS1307) Yes(PCF8563) Yes(PCF8563) Yes(PCF8563) Case Metallic Black No Metallic Black White Blue Orange(1U rack compatible) Metallic Black(1U rack compatible) Buzzer No No No Yes Custom button No No No Yes Software update Yes Yes Yes Yes 32GB SD Card Yes (OS included) Yes (OS included) Yes (OS included) Yes (OS included) HDMI backpower mitigation No Yes Yes Yes Professional technical support Yes Yes Yes Yes","title":"BLIKVM Overview"},{"location":"#features","text":"Video capture (1080P 60Hz) Keyboard forwarding Mouse forwarding ATX Fan Control Fullscreen mode Paste text from clipboard VPN support Mass Storage Drive (emulate a CD-ROM or Flash Drive) Multiport KVM over IP OLED to display system info, like temp, uptime, IP Password authentication Support multiple languages Wake-on-LAN","title":"Features"},{"location":"#guides","text":"1. BLIKVM v1 CM4 version 2. BLIKVM v2 PCIE version 3. BLIKVM v3 HAT version 4. BliKVM v4 Allwinner version","title":"Guides"},{"location":"BLIHAT-Installation/","text":"BLIHAT Installation Guide 1. Unpack and take out the devices Open the protective bag 2. Install the main device Flip to back Open the case Flip to back, unscrew the two screws on the back Open the protective bag and take out the parts Install Micro SD card Install the FFC cable Install the HAT on the Raspberry Pi 4 Install the four Hex Spacers Install the C790 module, use the long screws you just removed Install the audio cable Stick a heat conductive sheet on the back of the Raspberry Pi 4, tear off the protective film of the sheet Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"v3 HAT Illustrated Instructions"},{"location":"BLIHAT-Installation/#blihat-installation-guide","text":"","title":"BLIHAT Installation Guide"},{"location":"BLIHAT-Installation/#1-unpack-and-take-out-the-devices","text":"Open the protective bag","title":"1. Unpack and take out the devices"},{"location":"BLIHAT-Installation/#2-install-the-main-device","text":"Flip to back Open the case Flip to back, unscrew the two screws on the back Open the protective bag and take out the parts Install Micro SD card Install the FFC cable Install the HAT on the Raspberry Pi 4 Install the four Hex Spacers Install the C790 module, use the long screws you just removed Install the audio cable Stick a heat conductive sheet on the back of the Raspberry Pi 4, tear off the protective film of the sheet Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"2. Install the main device"},{"location":"BLIKVM-CM4-guide/","text":"BLIKVM-CM4 version guide Geerling: Engineering Test video BliKVM v1 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM v1 Datasheet Features Video capture (HDMI, support 1080P@60Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Serial console port OLED display Real Time Clock (RTC) FAN Installation requirements If you have an assembly kit, you will need the following things Raspberry CM4 with 1Gb RAM or more. USB-C to USB-A cable. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit (5.1V 3A USB-C, recommended by the Raspberry Pi). Power supply You must use a USB-C to USB-A cable. Using a USB-C to USB-C cable will not work. This is an incompatibility in the hardware design and will be fixed in a later version. Basic setup 1. The SD card preloaded with the factory default image does not require burning. If you need to reflash the system or for DIY purposes, you can follow Flash the memory card or eMMC 2. If you have a non-plug version, refer to the video and instructions below for device installation: Use the provided screwdriver to open the metal casing and remove the PCB motherboard. Install the CM4 onto the PCB motherboard, ensuring that the two rows of card slots are aligned. Apply the thermal conductive silicone pad onto the CM4 main chip to facilitate heat dissipation using the metal casing. The fan is not connected by default as the metal casing provides sufficient heat dissipation. Depending on your CM4 version, selectively install the Wi-Fi antenna. Reassemble the PCB motherboard and the metal casing to complete the installation. Please note that translations might vary depending on context and specific terminology used in technical instructions. Video Guide: Metal case step by step Ortimo: BLIKVM with Raspberry PI CM4 16GB EMMC setup 3. Connect BLIKVM to the computer according to the diagram below: HDMI IN and otg port must be connected to the computer. ATX too, but it\u2019s optional, read below. There should be no USB hub between BLIKVM and the computer, as some UEFI/BIOS cannot detect them at the boot stage. BLIKVM supports 1080p60Hz or lower about HDMI source. Connect Ethernet to the network and PWR IN to the BLIKVM power supply. 4. ATX connection To manage the power of your computer, you will connect CN-ATX port to the computer.The user can use the ATX cable provided with the product to connect the product and the motherboard ATX switch of the controlled computer. The length of the ATX cable is 60CM, you can also use the double female Dupont cables. To accommodate ATX control boards with Ethernet ports, v1 has a dedicated ATX expansion kit available. This kit enables customers to connect the ATX board installed on the chassis panel directly using an Ethernet cable. 5. After all the connecting cables are properly set up, power on the BliKVM until the display screen shows an image, indicating that the device has successfully started. 6. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. As BliKVM v1 also supports PiKVM OS, if your v1 comes with PiKVM as the factory OS, please refer to the documentation for web usage instructions . 7. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 8. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience! Wi-Fi Antenna Connection If your CM4 has Wi-Fi functionality, open the metal casing of v1 and attach the Wi-Fi antenna from the package to the IPX interface on the CM4, as shown by the red box in the diagram below; the installation location on the casing for the antenna is defined as position 11 in the interface layout diagram. Support 1080p60hz HDMI input First in V2.2 version, there is CSI channel switch. This switch is switch 2 csi channels or 4 csi channels. In other versions, the switch is obsolete. Newer keeps the factory state, ignore this switch. Only flip the switch when the device is powered off, otherwise it may cause permanent damage! The four small switches should be up or down at the same time. Product List BLIKVM v1 excluding CM4 Case 1 PCB 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 OLED 1 BLIKVM v1 including CM4102000 Case 1 PCB 1 CM4102000 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 OLED 1 WiFi antenna 1 BLIKVM v1 including CM4002000 Case 1 PCB 1 CM4002000 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 WiFi antenna 1 Buy link Buy v1","title":"BliKVM v1 CM4 Guide"},{"location":"BLIKVM-CM4-guide/#blikvm-cm4-version-guide","text":"Geerling: Engineering Test video BliKVM v1 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM v1 Datasheet","title":"BLIKVM-CM4 version guide"},{"location":"BLIKVM-CM4-guide/#features","text":"Video capture (HDMI, support 1080P@60Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Serial console port OLED display Real Time Clock (RTC) FAN","title":"Features"},{"location":"BLIKVM-CM4-guide/#installation-requirements","text":"If you have an assembly kit, you will need the following things Raspberry CM4 with 1Gb RAM or more. USB-C to USB-A cable. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit (5.1V 3A USB-C, recommended by the Raspberry Pi). Power supply You must use a USB-C to USB-A cable. Using a USB-C to USB-C cable will not work. This is an incompatibility in the hardware design and will be fixed in a later version.","title":"Installation requirements"},{"location":"BLIKVM-CM4-guide/#basic-setup","text":"1. The SD card preloaded with the factory default image does not require burning. If you need to reflash the system or for DIY purposes, you can follow Flash the memory card or eMMC 2. If you have a non-plug version, refer to the video and instructions below for device installation: Use the provided screwdriver to open the metal casing and remove the PCB motherboard. Install the CM4 onto the PCB motherboard, ensuring that the two rows of card slots are aligned. Apply the thermal conductive silicone pad onto the CM4 main chip to facilitate heat dissipation using the metal casing. The fan is not connected by default as the metal casing provides sufficient heat dissipation. Depending on your CM4 version, selectively install the Wi-Fi antenna. Reassemble the PCB motherboard and the metal casing to complete the installation. Please note that translations might vary depending on context and specific terminology used in technical instructions. Video Guide: Metal case step by step Ortimo: BLIKVM with Raspberry PI CM4 16GB EMMC setup 3. Connect BLIKVM to the computer according to the diagram below: HDMI IN and otg port must be connected to the computer. ATX too, but it\u2019s optional, read below. There should be no USB hub between BLIKVM and the computer, as some UEFI/BIOS cannot detect them at the boot stage. BLIKVM supports 1080p60Hz or lower about HDMI source. Connect Ethernet to the network and PWR IN to the BLIKVM power supply. 4. ATX connection To manage the power of your computer, you will connect CN-ATX port to the computer.The user can use the ATX cable provided with the product to connect the product and the motherboard ATX switch of the controlled computer. The length of the ATX cable is 60CM, you can also use the double female Dupont cables. To accommodate ATX control boards with Ethernet ports, v1 has a dedicated ATX expansion kit available. This kit enables customers to connect the ATX board installed on the chassis panel directly using an Ethernet cable. 5. After all the connecting cables are properly set up, power on the BliKVM until the display screen shows an image, indicating that the device has successfully started. 6. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. As BliKVM v1 also supports PiKVM OS, if your v1 comes with PiKVM as the factory OS, please refer to the documentation for web usage instructions . 7. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 8. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience!","title":"Basic setup"},{"location":"BLIKVM-CM4-guide/#wi-fi-antenna-connection","text":"If your CM4 has Wi-Fi functionality, open the metal casing of v1 and attach the Wi-Fi antenna from the package to the IPX interface on the CM4, as shown by the red box in the diagram below; the installation location on the casing for the antenna is defined as position 11 in the interface layout diagram.","title":"Wi-Fi Antenna Connection"},{"location":"BLIKVM-CM4-guide/#support-1080p60hz-hdmi-input","text":"First in V2.2 version, there is CSI channel switch. This switch is switch 2 csi channels or 4 csi channels. In other versions, the switch is obsolete. Newer keeps the factory state, ignore this switch. Only flip the switch when the device is powered off, otherwise it may cause permanent damage! The four small switches should be up or down at the same time.","title":"Support 1080p60hz HDMI input"},{"location":"BLIKVM-CM4-guide/#product-list","text":"BLIKVM v1 excluding CM4 Case 1 PCB 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 OLED 1 BLIKVM v1 including CM4102000 Case 1 PCB 1 CM4102000 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 OLED 1 WiFi antenna 1 BLIKVM v1 including CM4002000 Case 1 PCB 1 CM4002000 1 Fan 1 SD card 32G 1 ATX Dupont Cables 1 WiFi antenna 1","title":"Product List"},{"location":"BLIKVM-CM4-guide/#buy-link","text":"Buy v1","title":"Buy link"},{"location":"BLIKVM-HAT-guide/","text":"BLIKVM HAT version guide Introduction BLIKVM hat Video The Raspberry Pi IPKVM HAT is an add-on board for Raspberry Pi 4, made especially for KVM Over IP. The BLIKVM-RPI4 is a Raspberry Pi 4 PoE KVM HAT. This product\u2019s key features include video capture, ATX adapter, PoE, OLED and RTC. The product has a customized metal case to dissipate heat and provide protection for the HAT. The product can be easily installed on a standard 1U rack. The product is currently perfectly compatible with BliKVM image and PiKVM image. Features Video capture (HDMI, support 1080P@50Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Adapter : Control the server power using ATX functions Fullscreen mode Access via Web UI Multi Language switching support PoE support Serial console port OLED display Real Time Clock (RTC) PWM FAN Interface HAT part: HDMI IN ATX Port OLED PoE jumper Raspberry 4B part: SD CARD ACT LED PWR LED USB-PC HDMI 0 HDMI 1 A/V ETH(1000M) & PoE 2x USB 2.0 Ports & 2x USB 3.0 Ports Installation requirements If you have an assembly kit, you will need the following things Raspberry Pi 4B with 1Gb RAM or more. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit & cable(5.1V 3A USB-C, recommended by the Raspberry Pi). Basic setup 1. Flash the memory card or eMMC 2. Build BLIKVM according to the video instructions or review the illustrated instructions : Video Guide: Metal case step by step 3. Install the ATX adapter board The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. Choose one as needed Use Dupont cables to connect ATX adapter board to motherboard and chassis panel. There are clear pin definitions on the board for easy wiring. Mount the ATX adapter board to the case shell Use a RJ45 network cable to connect the board to the CN-ATX interface of the HAT 4. Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the HAT with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 5. Install the USB cable Connect the RPI4 port to the Raspberry Pi 4 Connect the USB port to the controlled computer When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. 6. Test Powered by PoE, the HAT is connected to the router via the network cable The screen displays the current status of the device, including the machine's IP address Access the IP address of the HAT in the browser. Enjoy! Specification HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@50fps. Fixed HDMI back power issue. CN-ATX The CN-ATX interface is connected to the ATX adapter board (an accessory for the HAT) through a network cable, which can turn on, off, and restart the controlled computer. Display A white OLED display with a resolution of 128x32, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. PoE Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A Plug in the PoE jumper cap to enable PoE power supply FAN The IPKVM HAT is fitted with a small fan that is controlled by your Raspberry Pi via GPIO12. Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi via I2C. The coin cell battery is installed under the HDMI IN module. Accessories ATX adapter board This board is connected to the switch port on the motherboard of the controlled computer with DuPont cables. The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. USB/PWR splitter Connect the RPI4 port to your Raspberry Pi 4. Connect the USB port to the controlled computer. When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. Metal case The metal case protects the HAT and improve heat dissipation. There are clear port markings on the case. The case can be easily installed on a standard 1U rack. List Product List Raspberry Pi IPKVM HAT 1 ATX adapter board 1 USB/PWR splitter 1 HDMI pass-through EDID emulator 1 Metal case 1 32G TF card 1 USB Type-C to USB Type-C Cable 30cm 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 List of items prepared by the user Raspberry Pi 4 1 RJ45 network cable 2 USB Type-A to USB Type-C Cable 2 HDMI cable 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1 Buy link Buy v3","title":"BliKVM v3 HAT Guide"},{"location":"BLIKVM-HAT-guide/#blikvm-hat-version-guide","text":"","title":"BLIKVM HAT version guide"},{"location":"BLIKVM-HAT-guide/#introduction","text":"BLIKVM hat Video The Raspberry Pi IPKVM HAT is an add-on board for Raspberry Pi 4, made especially for KVM Over IP. The BLIKVM-RPI4 is a Raspberry Pi 4 PoE KVM HAT. This product\u2019s key features include video capture, ATX adapter, PoE, OLED and RTC. The product has a customized metal case to dissipate heat and provide protection for the HAT. The product can be easily installed on a standard 1U rack. The product is currently perfectly compatible with BliKVM image and PiKVM image.","title":"Introduction"},{"location":"BLIKVM-HAT-guide/#features","text":"Video capture (HDMI, support 1080P@50Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Adapter : Control the server power using ATX functions Fullscreen mode Access via Web UI Multi Language switching support PoE support Serial console port OLED display Real Time Clock (RTC) PWM FAN","title":"Features"},{"location":"BLIKVM-HAT-guide/#interface","text":"HAT part: HDMI IN ATX Port OLED PoE jumper Raspberry 4B part: SD CARD ACT LED PWR LED USB-PC HDMI 0 HDMI 1 A/V ETH(1000M) & PoE 2x USB 2.0 Ports & 2x USB 3.0 Ports","title":"Interface"},{"location":"BLIKVM-HAT-guide/#installation-requirements","text":"If you have an assembly kit, you will need the following things Raspberry Pi 4B with 1Gb RAM or more. HDMI cable. Straight Ethernet cable (for the ATX board connection). Power supply unit & cable(5.1V 3A USB-C, recommended by the Raspberry Pi).","title":"Installation requirements"},{"location":"BLIKVM-HAT-guide/#basic-setup","text":"1. Flash the memory card or eMMC 2. Build BLIKVM according to the video instructions or review the illustrated instructions : Video Guide: Metal case step by step 3. Install the ATX adapter board The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. Choose one as needed Use Dupont cables to connect ATX adapter board to motherboard and chassis panel. There are clear pin definitions on the board for easy wiring. Mount the ATX adapter board to the case shell Use a RJ45 network cable to connect the board to the CN-ATX interface of the HAT 4. Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the HAT with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 5. Install the USB cable Connect the RPI4 port to the Raspberry Pi 4 Connect the USB port to the controlled computer When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply. 6. Test Powered by PoE, the HAT is connected to the router via the network cable The screen displays the current status of the device, including the machine's IP address Access the IP address of the HAT in the browser. Enjoy!","title":"Basic setup"},{"location":"BLIKVM-HAT-guide/#specification","text":"HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@50fps. Fixed HDMI back power issue. CN-ATX The CN-ATX interface is connected to the ATX adapter board (an accessory for the HAT) through a network cable, which can turn on, off, and restart the controlled computer. Display A white OLED display with a resolution of 128x32, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. PoE Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A Plug in the PoE jumper cap to enable PoE power supply FAN The IPKVM HAT is fitted with a small fan that is controlled by your Raspberry Pi via GPIO12. Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi via I2C. The coin cell battery is installed under the HDMI IN module.","title":"Specification"},{"location":"BLIKVM-HAT-guide/#accessories","text":"","title":"Accessories"},{"location":"BLIKVM-HAT-guide/#atx-adapter-board","text":"This board is connected to the switch port on the motherboard of the controlled computer with DuPont cables. The board has a standard PCIe I/O bracket and a low profile PCIe I/O bracket.","title":"ATX adapter board"},{"location":"BLIKVM-HAT-guide/#usbpwr-splitter","text":"Connect the RPI4 port to your Raspberry Pi 4. Connect the USB port to the controlled computer. When using PoE power supply, there is no need to connect the PWR port. When not using PoE power supply, connect the PWR port to a standard 5V/3A USB power supply.","title":"USB/PWR splitter"},{"location":"BLIKVM-HAT-guide/#hdmi-pass-through-edid-emulator","text":"If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer.","title":"HDMI pass-through EDID emulator"},{"location":"BLIKVM-HAT-guide/#metal-case","text":"The metal case protects the HAT and improve heat dissipation. There are clear port markings on the case. The case can be easily installed on a standard 1U rack.","title":"Metal case"},{"location":"BLIKVM-HAT-guide/#list","text":"","title":"List"},{"location":"BLIKVM-HAT-guide/#product-list","text":"Raspberry Pi IPKVM HAT 1 ATX adapter board 1 USB/PWR splitter 1 HDMI pass-through EDID emulator 1 Metal case 1 32G TF card 1 USB Type-C to USB Type-C Cable 30cm 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Phillips screwdriver 1 Cross Wrench Sleeve 1","title":"Product List"},{"location":"BLIKVM-HAT-guide/#list-of-items-prepared-by-the-user","text":"Raspberry Pi 4 1 RJ45 network cable 2 USB Type-A to USB Type-C Cable 2 HDMI cable 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"List of items prepared by the user"},{"location":"BLIKVM-HAT-guide/#buy-link","text":"Buy v3","title":"Buy link"},{"location":"BLIKVM-PCIE-guide/","text":"BLIKVM PCIe Introduction BLIKVM PCIe is a PCIe add-in card based on Raspberry Pi CM4 for KVM Over IP. This product\u2019s key features include video capture, ATX controller, PoE, OLED , UART and RTC. The card has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. The product is currently perfectly compatible with blikvm image and pikvm image. Installation requirements You will need the following things Raspberry Pi CM4(if you order PCIe card only). PoE-sourcing equipment or 5V/3A USB adapter. CR1220 coin cell battery. Features Video capture (HDMI, support 1080P@60Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE Serial console port OLED display Real Time Clock (RTC) PWM Fan Basic setup 1. If you have an assembly kit, Flash the memory card or eMMC 2.Build BLIKVM according to the illustrated instructions : Geerling: Engineering Test video Craft Computing: Never Pay For IPMI Again - BliKVM Review Specification hardware feature list 1 HDMI in 2 USB-PC port 3 Power Input 5V 3A 4 RJ45 100M Ethernet port & PoE 5 ATX control port 6 OLED Display 7 PWM FAN 8 BOOT 9 REAL TIME CLOCK(RTC) 10 UART port 11 USB-PC port HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@60fps. Fixed HDMI back power issue. USB-PC The BLIKVM PCIe card provides two USB interfaces, one is PC-IN (type c interface) and the other is USB-PC2 (pin interface). The purpose of these two interfaces is to connect to the USB of the controlled computer, used to control the mouse and keyboard. At the same time, only one interface can be used. The purpose of designing two interfaces is to directly use USB PC2 when the user's PC host has a row pin USB interface, which will make the wiring more concise. POWER-IN When using PoE power supply, there is no need to connect the PWR-IN port. When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. ETHERNET-PoE Gigabit Ethernet port Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A ATX-Connecter Connect to power control interface on the motherboard of the controlled computer with DuPont cables. It can turn on, off, and restart the controlled computer. The pin is defined on the printing of the PCIe board, BTN means button. According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the PCIe board. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and PCIe. See the following figure for the connection relationship\uff1a OLED Display A white OLED display with a resolution of 128x64, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. FAN The Card HAT is fitted with a small fan that is controlled by your Raspberry Pi CM4 via GPIO12. BOOT Fit jumper to disable eMMC Boot Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi CM4 via I2C. The CR1220 battery is installed under the HDMI IN module. UART Connect the serial port to debug your Raspberry Pi CM4. The uart of Raspberry Pi CM4. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. Connect serial cable wires to G T R connectors on the PCIe board. NOTE: black wire = Ground, whiTe = Tx, and gReen = Rx; For specific methods, please refer to this document . Accessories HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. VGA-HDMI module When your device does not have an HDMI output interface, you can use a VGA to HDMI module. USB to TTL module Connect your computer usb interface with the serial port of BLIKVM to debug your Raspberry Pi CM4. Fan Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card. Dimensions Test Video BLIKVM hardware PCIe version is tested wonderful based on pikvm software. Notes To prevent the CM4 module from contacting the SD card holder, do not remove the insulating tape List Product List BLIKVM PCIe card version 1 BLIKVM PCIe add-in card 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 BLIKVM PCIe plug-n-play version 1 BLIKVM PCIe add-in card 1 CM4 102000 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 List of items prepared by the user Raspberry Pi CM4(if you order PCIe card only) 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1 Buy link Buy v2 3D printable case A simple snap fit case for the PCIe. Download file","title":"BliKVM v2 PCIe Guide"},{"location":"BLIKVM-PCIE-guide/#blikvm-pcie","text":"","title":"BLIKVM PCIe"},{"location":"BLIKVM-PCIE-guide/#introduction","text":"BLIKVM PCIe is a PCIe add-in card based on Raspberry Pi CM4 for KVM Over IP. This product\u2019s key features include video capture, ATX controller, PoE, OLED , UART and RTC. The card has a standard PCIe I/O bracket and a low profile PCIe I/O bracket. The product is currently perfectly compatible with blikvm image and pikvm image.","title":"Introduction"},{"location":"BLIKVM-PCIE-guide/#installation-requirements","text":"You will need the following things Raspberry Pi CM4(if you order PCIe card only). PoE-sourcing equipment or 5V/3A USB adapter. CR1220 coin cell battery.","title":"Installation requirements"},{"location":"BLIKVM-PCIE-guide/#features","text":"Video capture (HDMI, support 1080P@60Hz input) Keyboard forwarding Mouse forwarding Mass Storage Drive ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE Serial console port OLED display Real Time Clock (RTC) PWM Fan","title":"Features"},{"location":"BLIKVM-PCIE-guide/#basic-setup","text":"1. If you have an assembly kit, Flash the memory card or eMMC 2.Build BLIKVM according to the illustrated instructions : Geerling: Engineering Test video Craft Computing: Never Pay For IPMI Again - BliKVM Review","title":"Basic setup"},{"location":"BLIKVM-PCIE-guide/#specification","text":"hardware feature list 1 HDMI in 2 USB-PC port 3 Power Input 5V 3A 4 RJ45 100M Ethernet port & PoE 5 ATX control port 6 OLED Display 7 PWM FAN 8 BOOT 9 REAL TIME CLOCK(RTC) 10 UART port 11 USB-PC port HDMI IN The bridge chip is Toshiba TC358743, which supports both video and audio(I2S), and the highest input resolution is 1080p@60fps. Fixed HDMI back power issue. USB-PC The BLIKVM PCIe card provides two USB interfaces, one is PC-IN (type c interface) and the other is USB-PC2 (pin interface). The purpose of these two interfaces is to connect to the USB of the controlled computer, used to control the mouse and keyboard. At the same time, only one interface can be used. The purpose of designing two interfaces is to directly use USB PC2 when the user's PC host has a row pin USB interface, which will make the wiring more concise. POWER-IN When using PoE power supply, there is no need to connect the PWR-IN port. When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. ETHERNET-PoE Gigabit Ethernet port Standard: IEEE 802.3af PoE Input voltage: 37-57 V DC Output power: 5 V DC/2.4 A ATX-Connecter Connect to power control interface on the motherboard of the controlled computer with DuPont cables. It can turn on, off, and restart the controlled computer. The pin is defined on the printing of the PCIe board, BTN means button. According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the PCIe board. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and PCIe. See the following figure for the connection relationship\uff1a OLED Display A white OLED display with a resolution of 128x64, and the chip is SSD1306. This display can show the temperature, IP address and other information of the Raspberry Pi. FAN The Card HAT is fitted with a small fan that is controlled by your Raspberry Pi CM4 via GPIO12. BOOT Fit jumper to disable eMMC Boot Real Time Clock (RTC) The clock chip is PCF8563 that is controlled by your Raspberry Pi CM4 via I2C. The CR1220 battery is installed under the HDMI IN module. UART Connect the serial port to debug your Raspberry Pi CM4. The uart of Raspberry Pi CM4. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. Connect serial cable wires to G T R connectors on the PCIe board. NOTE: black wire = Ground, whiTe = Tx, and gReen = Rx; For specific methods, please refer to this document .","title":"Specification"},{"location":"BLIKVM-PCIE-guide/#accessories","text":"HDMI pass-through EDID emulator If the controlled computer does not output HDMI images correctly, please use this accessory. Connect the Source port to the controlled computer, connect the Sink port to the HAT. Then you can set the correct HDMI output on the controlled computer. VGA-HDMI module When your device does not have an HDMI output interface, you can use a VGA to HDMI module. USB to TTL module Connect your computer usb interface with the serial port of BLIKVM to debug your Raspberry Pi CM4. Fan Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card.","title":"Accessories"},{"location":"BLIKVM-PCIE-guide/#dimensions","text":"","title":"Dimensions"},{"location":"BLIKVM-PCIE-guide/#test-video","text":"BLIKVM hardware PCIe version is tested wonderful based on pikvm software.","title":"Test Video"},{"location":"BLIKVM-PCIE-guide/#notes","text":"To prevent the CM4 module from contacting the SD card holder, do not remove the insulating tape","title":"Notes"},{"location":"BLIKVM-PCIE-guide/#list","text":"","title":"List"},{"location":"BLIKVM-PCIE-guide/#product-list","text":"BLIKVM PCIe card version 1 BLIKVM PCIe add-in card 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1 BLIKVM PCIe plug-n-play version 1 BLIKVM PCIe add-in card 1 CM4 102000 1 Cooling fan 1 OLED display 1 USB to TTL module 1 HDMI pass-through EDID emulator 1 VGA-HDMI module 1 32G Micro SD card 1 HDMI cable 0.5m 1 HDMI Coupler 1 Network cable 1m 1 USB-A to USB-C cable 1m 2 Dupont USB cable 0.4m 1 WiFi antenna 1 Dupont Cables 8pin Male to Male 40cm 1 Dupont Cables 8pin Male to Female 40cm 1 Metal heatsink 1 Phillips screwdriver 1 Cross Wrench Sleeve 1","title":"Product List"},{"location":"BLIKVM-PCIE-guide/#list-of-items-prepared-by-the-user","text":"Raspberry Pi CM4(if you order PCIe card only) 1 PoE-sourcing equipment or 5V/3A USB adapter 1 CR1220 coin cell battery 1","title":"List of items prepared by the user"},{"location":"BLIKVM-PCIE-guide/#buy-link","text":"Buy v2","title":"Buy link"},{"location":"BLIKVM-PCIE-guide/#3d-printable-case","text":"A simple snap fit case for the PCIe. Download file","title":"3D printable case"},{"location":"BLIKVM-PCIe-installation/","text":"BLIKVM PCIe CM4 Installation Guide 1. Unpack and take out the devices Product List 2. Install the main device Install CM4 and 4 Hex spacers (This article takes CM4 lite as an example, using the image in the Micro SD card, CM4 eMMC user need to burn the image by yourself.)Stick a heat conductive sheet on the top of CM4 , tear off the protective film of the sheet. The main device installation is complete. 3. Connect USB and ATX The motherboard used in this article is Asus H520M-E, the interface definition of different motherboards may be different, please refer to your motherboard manual. 4. Connect OLED The OLED you received does not have a bracket installed. Please refer to the picture for installation. In addition, OLED support is made of acrylic material, which needs to be used after removing the protective film on the surface. The above is the installation steps, and the effect of not tearing the film is as follows. In actual use, please remove the protective film. 5. Connect the HDMI cable Connect the HDMI output port of the computer directly to the HDMI IN port of the product with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer. 6. Connect the network cable Gigabit Ethernet port standard: IEEE 802.3af PoE input voltage:37v-57v. When using PoE power supply, there is no need to connect the PWR-IN port. 7. Connect PWR-IN When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply. 8. Test OLED screen showing device IP and other information. Access the IP address in browser. After passing the test, install the product into the computer case. 9. Install the product into the computer case Disconnect power and wiring, install the product on the motherboard, and reconnect the cables after installation is complete. The color of ATX cable received in different batches may be different. Please directly refer to the pin definition for connection Enjoy! Appendix 1. Install a low profile PCIe I/O bracket Note Appendix 2. Install the cooling fan Usually the metal heatsink is sufficient, the cooling fan is not necessary. The cooling fan is controlled by CM4 via GPIO12. Appendix 3. Install wifi antenna Note","title":"v2 PCIe Illustrated Instructions"},{"location":"BLIKVM-PCIe-installation/#blikvm-pcie-cm4-installation-guide","text":"","title":"BLIKVM PCIe CM4 Installation Guide"},{"location":"BLIKVM-PCIe-installation/#1-unpack-and-take-out-the-devices","text":"Product List","title":"1. Unpack and take out the devices"},{"location":"BLIKVM-PCIe-installation/#2-install-the-main-device","text":"Install CM4 and 4 Hex spacers (This article takes CM4 lite as an example, using the image in the Micro SD card, CM4 eMMC user need to burn the image by yourself.)Stick a heat conductive sheet on the top of CM4 , tear off the protective film of the sheet. The main device installation is complete.","title":"2. Install the main device"},{"location":"BLIKVM-PCIe-installation/#3-connect-usb-and-atx","text":"The motherboard used in this article is Asus H520M-E, the interface definition of different motherboards may be different, please refer to your motherboard manual.","title":"3. Connect USB and ATX"},{"location":"BLIKVM-PCIe-installation/#4-connect-oled","text":"The OLED you received does not have a bracket installed. Please refer to the picture for installation. In addition, OLED support is made of acrylic material, which needs to be used after removing the protective film on the surface. The above is the installation steps, and the effect of not tearing the film is as follows. In actual use, please remove the protective film.","title":"4. Connect OLED"},{"location":"BLIKVM-PCIe-installation/#5-connect-the-hdmi-cable","text":"Connect the HDMI output port of the computer directly to the HDMI IN port of the product with an HDMI cable. The HDMI pass-through EDID emulator is not necessary! If your computer does not output the correct HDMI format, plug the HDMI pass-through EDID emulator into the HDMI output port of the computer. This allows you to configure a fixed HDMI output format on your computer.","title":"5. Connect the HDMI cable"},{"location":"BLIKVM-PCIe-installation/#6-connect-the-network-cable","text":"Gigabit Ethernet port standard: IEEE 802.3af PoE input voltage:37v-57v. When using PoE power supply, there is no need to connect the PWR-IN port.","title":"6. Connect the network cable"},{"location":"BLIKVM-PCIe-installation/#7-connect-pwr-in","text":"When not using PoE power supply, connect the PWR-IN port to a standard 5V/3A USB power supply.","title":"7. Connect PWR-IN"},{"location":"BLIKVM-PCIe-installation/#8-test","text":"OLED screen showing device IP and other information. Access the IP address in browser. After passing the test, install the product into the computer case.","title":"8. Test"},{"location":"BLIKVM-PCIe-installation/#9-install-the-product-into-the-computer-case","text":"Disconnect power and wiring, install the product on the motherboard, and reconnect the cables after installation is complete. The color of ATX cable received in different batches may be different. Please directly refer to the pin definition for connection Enjoy!","title":"9. Install the product into the computer case"},{"location":"BLIKVM-PCIe-installation/#appendix-1-install-a-low-profile-pcie-io-bracket","text":"Note","title":"Appendix 1. Install a low profile PCIe I/O bracket"},{"location":"BLIKVM-PCIe-installation/#appendix-2-install-the-cooling-fan","text":"Usually the metal heatsink is sufficient, the cooling fan is not necessary. The cooling fan is controlled by CM4 via GPIO12.","title":"Appendix 2. Install the cooling fan"},{"location":"BLIKVM-PCIe-installation/#appendix-3-install-wifi-antenna","text":"Note","title":"Appendix 3. Install wifi antenna"},{"location":"BliKVM-v4-guide/","text":"BliKVM v4 Allwinner BliKVM v4 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM V4 Datasheet Craft Computing: Goodbye IPMI - Blicube BliKVM V4 Review Lawrence Systems: Blicube BliKVM V4: Is This the Best Linux IP KVM Yet? RainCat: How to install PiKVM on BliKVM v4 Allwinner Features Video capture (HDMI, support 4K@30Hz input) Keyboard forwarding Mouse forwarding HDMI video loop through ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE & DC Support WiFi Serial console port 1.33 inch color display Real Time Clock (RTC) HDMI input supported resolution types Installation Requirements In addition to the v4 kit, you will need the following equipment: Power adapter (5V 3A, USB-C port, or 12V 2A DC port). If you plan to use PoE (Power over Ethernet) or if the USB ports on your controlled computers provide sufficient power, a separate power adapter is not required. HDMI cables (at least one). If you also need to use the HDMI loop-out interface, you will need two cables. Ethernet cable(s) (provide based on your requirements). One cable is required for using the ATX power switch function, and one cable is required for using the Ethernet connection. USB-C to USB-A cable (for mouse and keyboard data transmission). Terminal Upgrade Notice! Before upgrading, execute the following command, otherwise, after running apt-get update and apt-get upgrade, the image will fail to start. apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64 Video Guide: Unpacking and connecting case step by step Installation Steps 1. Open the v4 kit package and connect the BliKVM to the controlled computer according to the connection diagram shown below: ATX Connection Please refer to the ATX Connection Guide . 2. Once all the cables are connected, power on the BliKVM. Wait until the display shows the interface, indicating that the device has started up successfully. 3. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. 4. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 5. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience! Video Mode v4 supports a maximum video input of 4K30Hz, and the default transmission resolution is 1920x1080. Packing List BLIKVM v4 1 WiFi Antenna 1 ATX adapter board 1 ATX Dupont Cables 8pin Male to Male 60cm 1 ATX Dupont Cables 8pin Male to Female 60cm 1 1U Rack Mounting Ears 2 M2.5x5 Screws 8 Silicone Bumper Pellets 1 Serial Console Access via the 5V Port The 5V port can be used both for power supply and serial console access at the same time. The default baud rate is 115200. There is an onboard CH341-based USB to UART converter present inside BliKVM v4 which is connected to UART0 of the mCore-H616 SoC , so you can connect a USB port of a PC to the 5V port without an external UART and a USB-C to dupont adapter. PC USB port current output Be careful when trying to use the 5V port because a PC USB port alone may not be able to provide 3A (5V) which is a documented requirement for the board to work. Either use a 12V 2A DC port at the same time as using the 5V port for serial communication without a USB Splitter board, or use the splitter board to split out the VCC pin and use a separate 5V 3A power supply to provide power to the 5V port's VCC pin. Likewise, when disconnecting a cable from the 12V 2A DC port while BliKVM is powered on, make sure to disconnect the cable from the 5V port first (because that will become the power source for BliKVM v4 after the 12V 2A source is disconnected unless a splitter is used). You should see something like this in your host kernel log (if you are using a Linux-based OS) when attaching a USB cable to the 5V port of BliKVM v4: usb 1-1.2: new full-speed USB device number 12 using xhci_hcd usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34 usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.2: Product: USB Serial ch341 1-1.2:1.0: ch341-uart converter detected usb 1-1.2: ch341-uart converter now attached to ttyUSB0 Accessing this port can then be done using GNU screen or TIO : tio /dev/ttyUSB0 mangopimcore login: blikvm # ... If you need to check how much data is received over UART0 you can do this by looking at the counters exposed via proc as follows (the rx counter should increase when the data is sent from an external host if the built-in USB to UART converter is working properly): root@mangopimcore:~# grep '0: uart' /proc/tty/driver/serial 0: uart:16550A mmio:0x05000000 irq:284 tx:20306 rx:40 pe:1 RTS|DTR Dev If you want to develop or port software on v4 hardware yourself, you can refer to this hardware resource description . Buy link Buy v4","title":"BliKVM v4 Allwinner Guide"},{"location":"BliKVM-v4-guide/#blikvm-v4-allwinner","text":"BliKVM v4 is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! BliKVM V4 Datasheet Craft Computing: Goodbye IPMI - Blicube BliKVM V4 Review Lawrence Systems: Blicube BliKVM V4: Is This the Best Linux IP KVM Yet? RainCat: How to install PiKVM on BliKVM v4 Allwinner","title":"BliKVM v4 Allwinner"},{"location":"BliKVM-v4-guide/#features","text":"Video capture (HDMI, support 4K@30Hz input) Keyboard forwarding Mouse forwarding HDMI video loop through ATX Control the server power using ATX functions Fullscreen mode Access via Web UI Support multi language switching Support PoE & DC Support WiFi Serial console port 1.33 inch color display Real Time Clock (RTC) HDMI input supported resolution types","title":"Features"},{"location":"BliKVM-v4-guide/#installation-requirements","text":"In addition to the v4 kit, you will need the following equipment: Power adapter (5V 3A, USB-C port, or 12V 2A DC port). If you plan to use PoE (Power over Ethernet) or if the USB ports on your controlled computers provide sufficient power, a separate power adapter is not required. HDMI cables (at least one). If you also need to use the HDMI loop-out interface, you will need two cables. Ethernet cable(s) (provide based on your requirements). One cable is required for using the ATX power switch function, and one cable is required for using the Ethernet connection. USB-C to USB-A cable (for mouse and keyboard data transmission). Terminal Upgrade Notice! Before upgrading, execute the following command, otherwise, after running apt-get update and apt-get upgrade, the image will fail to start. apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64 Video Guide: Unpacking and connecting case step by step","title":"Installation Requirements"},{"location":"BliKVM-v4-guide/#installation-steps","text":"1. Open the v4 kit package and connect the BliKVM to the controlled computer according to the connection diagram shown below: ATX Connection Please refer to the ATX Connection Guide . 2. Once all the cables are connected, power on the BliKVM. Wait until the display shows the interface, indicating that the device has started up successfully. 3. Read the \"First Steps\" guide carefully. It provides instructions on how to find the device on the network, how to log in, change passwords, and more. Follow the steps described there and then return to this page. 4. Try managing your computer using the BliKVM web interface. Make sure you can see the image and that the keyboard and mouse are working properly. If you encounter any issues, check out our FAQ (it's very helpful). If you find no solution there, seek support in our Discord chat room . 5. You can explore other pages in the wiki to discover more features of BliKVM. Enjoy your experience!","title":"Installation Steps"},{"location":"BliKVM-v4-guide/#video-mode","text":"v4 supports a maximum video input of 4K30Hz, and the default transmission resolution is 1920x1080.","title":"Video Mode"},{"location":"BliKVM-v4-guide/#packing-list","text":"BLIKVM v4 1 WiFi Antenna 1 ATX adapter board 1 ATX Dupont Cables 8pin Male to Male 60cm 1 ATX Dupont Cables 8pin Male to Female 60cm 1 1U Rack Mounting Ears 2 M2.5x5 Screws 8 Silicone Bumper Pellets 1","title":"Packing List"},{"location":"BliKVM-v4-guide/#serial-console-access-via-the-5v-port","text":"The 5V port can be used both for power supply and serial console access at the same time. The default baud rate is 115200. There is an onboard CH341-based USB to UART converter present inside BliKVM v4 which is connected to UART0 of the mCore-H616 SoC , so you can connect a USB port of a PC to the 5V port without an external UART and a USB-C to dupont adapter. PC USB port current output Be careful when trying to use the 5V port because a PC USB port alone may not be able to provide 3A (5V) which is a documented requirement for the board to work. Either use a 12V 2A DC port at the same time as using the 5V port for serial communication without a USB Splitter board, or use the splitter board to split out the VCC pin and use a separate 5V 3A power supply to provide power to the 5V port's VCC pin. Likewise, when disconnecting a cable from the 12V 2A DC port while BliKVM is powered on, make sure to disconnect the cable from the 5V port first (because that will become the power source for BliKVM v4 after the 12V 2A source is disconnected unless a splitter is used). You should see something like this in your host kernel log (if you are using a Linux-based OS) when attaching a USB cable to the 5V port of BliKVM v4: usb 1-1.2: new full-speed USB device number 12 using xhci_hcd usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34 usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.2: Product: USB Serial ch341 1-1.2:1.0: ch341-uart converter detected usb 1-1.2: ch341-uart converter now attached to ttyUSB0 Accessing this port can then be done using GNU screen or TIO : tio /dev/ttyUSB0 mangopimcore login: blikvm # ... If you need to check how much data is received over UART0 you can do this by looking at the counters exposed via proc as follows (the rx counter should increase when the data is sent from an external host if the built-in USB to UART converter is working properly): root@mangopimcore:~# grep '0: uart' /proc/tty/driver/serial 0: uart:16550A mmio:0x05000000 irq:284 tx:20306 rx:40 pe:1 RTS|DTR","title":"Serial Console Access via the 5V Port"},{"location":"BliKVM-v4-guide/#dev","text":"If you want to develop or port software on v4 hardware yourself, you can refer to this hardware resource description .","title":"Dev"},{"location":"BliKVM-v4-guide/#buy-link","text":"Buy v4","title":"Buy link"},{"location":"Datasheet-BliKVM-v4/","text":"BliKVM v4 Allwinner (H616/H313 SOC) BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! Connectivity Diagram 1 USB 2.0 port 10 Antenna interface 2 Power Input 5V 3A & UART 11 RJ45 100M Ethernet port & PoE 3 RJ45 ATX control port 12 Display 1.33 inch LCD 4 HDMI video loop through port 13 Power LED (red) 5 USB-PC port 14 User defined button SW1 6 Power Input 12V 2A 5.5*2.1mm 15 ACT LED (green) 7 HDMI video input port 16 Display ON/OFF button 8 HDMI input status LED (green) 17 Micro SD card slot 9 HDMI output status LED (yellow) Specifications Parameter name Characteristics Power 5V 3A 5V port, USB-PC port 12V 2A 12V port PoE Power over Ethernet (IEEE802.3af compliant) 48V DC Connectivity/Interfaces HDMI-IN HDMI video input port HDMI-OUT HDMI video loop through port USB-PC Keyboard, mouse, mass storage, and other external device emulation) ATX Turn on/off or restart the controlled computer WiFi & Bluetooth IEEE802.11 b/g/n + BLE4.2 Micro SD card slot Persistent storage for OS and your data 5V port 5V 3A power or serial console management port Displays and indicators LED indicators Power LED, ACT LED, HDMI input status LED (green)\uff0c HDMI output status LED (yellow) LCD display LCD 240x240 1.33 inch User defined button SW1 Buzzer Find me Video Supported resolutions Up to 4k@30Hz Video compression methods MJPEG Core Chip ALLWINNER H616/H313 RAM 1GB Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 100 (L) x 134 (W) x 44.4 (H) mm Weight 0.45 kg BLIKVM CM4 version OLED display The product comes standard with a monochrome OLED display with a resolution of 128x64, and the chip is SSD1306. The user connects the display to the product with the wiring of the display. The module is connected to CM4 through the I^2^C interface. The wiring definition is shown in the following table. This is a library for the monochrome OLEDs based on SSD1306 drivers. Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C) Dimensions Schematic Diagram","title":"BliKVM v4 Allwinner (H616/H313 SOC)"},{"location":"Datasheet-BliKVM-v4/#blikvm-v4-allwinner-h616h313-soc","text":"BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals!","title":"BliKVM v4 Allwinner (H616/H313 SOC)"},{"location":"Datasheet-BliKVM-v4/#connectivity-diagram","text":"1 USB 2.0 port 10 Antenna interface 2 Power Input 5V 3A & UART 11 RJ45 100M Ethernet port & PoE 3 RJ45 ATX control port 12 Display 1.33 inch LCD 4 HDMI video loop through port 13 Power LED (red) 5 USB-PC port 14 User defined button SW1 6 Power Input 12V 2A 5.5*2.1mm 15 ACT LED (green) 7 HDMI video input port 16 Display ON/OFF button 8 HDMI input status LED (green) 17 Micro SD card slot 9 HDMI output status LED (yellow)","title":"Connectivity Diagram"},{"location":"Datasheet-BliKVM-v4/#specifications","text":"Parameter name Characteristics Power 5V 3A 5V port, USB-PC port 12V 2A 12V port PoE Power over Ethernet (IEEE802.3af compliant) 48V DC Connectivity/Interfaces HDMI-IN HDMI video input port HDMI-OUT HDMI video loop through port USB-PC Keyboard, mouse, mass storage, and other external device emulation) ATX Turn on/off or restart the controlled computer WiFi & Bluetooth IEEE802.11 b/g/n + BLE4.2 Micro SD card slot Persistent storage for OS and your data 5V port 5V 3A power or serial console management port Displays and indicators LED indicators Power LED, ACT LED, HDMI input status LED (green)\uff0c HDMI output status LED (yellow) LCD display LCD 240x240 1.33 inch User defined button SW1 Buzzer Find me Video Supported resolutions Up to 4k@30Hz Video compression methods MJPEG Core Chip ALLWINNER H616/H313 RAM 1GB Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 100 (L) x 134 (W) x 44.4 (H) mm Weight 0.45 kg BLIKVM CM4 version OLED display The product comes standard with a monochrome OLED display with a resolution of 128x64, and the chip is SSD1306. The user connects the display to the product with the wiring of the display. The module is connected to CM4 through the I^2^C interface. The wiring definition is shown in the following table. This is a library for the monochrome OLEDs based on SSD1306 drivers. Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C)","title":"Specifications"},{"location":"Datasheet-BliKVM-v4/#dimensions-schematic-diagram","text":"","title":"Dimensions Schematic Diagram"},{"location":"Dev-BliKVM-v4-Allwinner/","text":"Dev BliKVM v4 Allwinner (H616/H313 SOC) BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! System Block Diagram Functional Module Panel Function Pin Description Button SW1 GPIOI1(257) Press for high level Button SW1 GPIOI2(258) Press for high level LED ACT GPIOI5(261) Low level enable LED LED PWR 3V3 PWR LED is always on after power on ATX Function Pin Description LED-PWR GPIOH10(234) Light on for high level LED-HDD GPIOH9(233) Light on for high level SW-PWR GPIOH4(228) High level enable SW-RST GPIOI16(272) High level enable BUZZER Function Pin Description Buzzer GPIOI15(271) High level enable FAN Function Pin Description Fan GPIOI13(269) High level enable LCD Display 1.33-inch LCD display module, driver chip ST7789, resolution 240x240. Function Pin Description LCD_EN GPIOI4(260) Backlight high level enable LCD_RST GPIOI6(262) Reset Low level enable LCD_DC GPIOI3(259) Data/command control pin SPI1_CS GPIOH5 SPI1_CLK GPIOH6 SPI1_MOSI GPIOH7 GND GND 3V3 3V3","title":"v4 Allwinner Dev Guide"},{"location":"Dev-BliKVM-v4-Allwinner/#dev-blikvm-v4-allwinner-h616h313-soc","text":"BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals!","title":"Dev BliKVM v4 Allwinner (H616/H313 SOC)"},{"location":"Dev-BliKVM-v4-Allwinner/#system-block-diagram","text":"","title":"System Block Diagram"},{"location":"Dev-BliKVM-v4-Allwinner/#functional-module","text":"","title":"Functional Module"},{"location":"Dev-BliKVM-v4-Allwinner/#panel","text":"Function Pin Description Button SW1 GPIOI1(257) Press for high level Button SW1 GPIOI2(258) Press for high level LED ACT GPIOI5(261) Low level enable LED LED PWR 3V3 PWR LED is always on after power on","title":"Panel"},{"location":"Dev-BliKVM-v4-Allwinner/#atx","text":"Function Pin Description LED-PWR GPIOH10(234) Light on for high level LED-HDD GPIOH9(233) Light on for high level SW-PWR GPIOH4(228) High level enable SW-RST GPIOI16(272) High level enable","title":"ATX"},{"location":"Dev-BliKVM-v4-Allwinner/#buzzer","text":"Function Pin Description Buzzer GPIOI15(271) High level enable","title":"BUZZER"},{"location":"Dev-BliKVM-v4-Allwinner/#fan","text":"Function Pin Description Fan GPIOI13(269) High level enable","title":"FAN"},{"location":"Dev-BliKVM-v4-Allwinner/#lcd-display","text":"1.33-inch LCD display module, driver chip ST7789, resolution 240x240. Function Pin Description LCD_EN GPIOI4(260) Backlight high level enable LCD_RST GPIOI6(262) Reset Low level enable LCD_DC GPIOI3(259) Data/command control pin SPI1_CS GPIOH5 SPI1_CLK GPIOH6 SPI1_MOSI GPIOH7 GND GND 3V3 3V3","title":"LCD Display"},{"location":"Expand_Filesystem/","text":"Expand Filesystem If you find that the free space of the raspberry pi SD card or eMMC is smaller than the capacity of the actual SD card or eMMC, you need to do the following to expand the raspberry pi. If you find that the system does not have the raspi config tool, you can use Method 2 (use the GParted partition tool). Method 1: Use raspi-config tool If you are using a mirror after June 2023 and have added a third read-write partition, this method is no longer applicable. Please refer to method 2 and method 3. 1. Open raspi-config. sudo raspi-config 2. Choose Advancd Options\uff1a 3. Choose Expand Filesystem\uff1a 4. Ok: 5. Execute the command resize2fs /dev/mmcblk0p2 in the terminal to see that the SD card has been successfully expanded. Method 2: Use GParted tool 1. Connect the SD card or EMMc that has burned the image to the computer through USB. Take the GParted partition tool on Linux as an example. Other platforms also have similar partition tools. Open GParted software and select SD card: 2. By observing the partition of the SD card in the above figure, we can find that 2.01GB and 21.87GB of space are unused before and after the sdb3 partition, which is the space we want to expand. Select the sdb3 partition and click Resize. 3. You can drag the white partition of sdb3 to the leftmost and rightmost, or fill in 25958 with \"Previous Free Space\" as \"0\" and \"New Size\" as \"Maximum Size\", and then click Resize in the lower right corner. Then click OK to see that all unused space of sd has been used. 4. Insert the SD card into the device and start it. Method 3: Use script If you are using a BliKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand.sh on any path, and write the following content to expand.sh. If your hardware is v1 , v2 or v3 , use: #!/bin/bash set -x resize_mmcblk0p3 () { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100 % resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" If your hardware is v4 , use: #!/bin/bash set -x resize_mmcblk0p1 () { echo \"Resizing mmcblk0p1 partition...\" parted /dev/mmcblk0 resizepart 1 100 % resize2fs /dev/mmcblk0p1 echo \"mmcblk0p1 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p1 echo \"Partition resizing completed.\" If you are using a PiKVM image, you can run the script below on the KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand.sh on any path, and write the following content to expand.sh #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab ; then part = $( grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}' ) # shellcheck disable=SC2206 splitted =( ${ part //=/ } ) if [ \" ${ splitted [0] } \" == LABEL ] ; then label = ${ splitted [1] } part = $( blkid -c /dev/null -L \" $label \" ) else label = PIMSD fi unset splitted disk = /dev/ $( lsblk -no pkname \" $part \" ) npart = $( cat \"/sys/class/block/ ${ part // \\/ dev \\/ / } /partition\" ) umount \" $part \" parted \" $disk \" -a optimal -s resizepart \" $npart \" 100 % yes | mkfs.ext4 -L \" $label \" -F -m 0 \" $part \" mount \" $part \" unset disk part npart label fi 2. Execute bash expand.sh on the terminal and wait for the execution to complete.","title":"Expand Filesystem"},{"location":"Expand_Filesystem/#expand-filesystem","text":"If you find that the free space of the raspberry pi SD card or eMMC is smaller than the capacity of the actual SD card or eMMC, you need to do the following to expand the raspberry pi. If you find that the system does not have the raspi config tool, you can use Method 2 (use the GParted partition tool).","title":"Expand Filesystem"},{"location":"Expand_Filesystem/#method-1-use-raspi-config-tool","text":"If you are using a mirror after June 2023 and have added a third read-write partition, this method is no longer applicable. Please refer to method 2 and method 3. 1. Open raspi-config. sudo raspi-config 2. Choose Advancd Options\uff1a 3. Choose Expand Filesystem\uff1a 4. Ok: 5. Execute the command resize2fs /dev/mmcblk0p2 in the terminal to see that the SD card has been successfully expanded.","title":"Method 1: Use raspi-config tool"},{"location":"Expand_Filesystem/#method-2-use-gparted-tool","text":"1. Connect the SD card or EMMc that has burned the image to the computer through USB. Take the GParted partition tool on Linux as an example. Other platforms also have similar partition tools. Open GParted software and select SD card: 2. By observing the partition of the SD card in the above figure, we can find that 2.01GB and 21.87GB of space are unused before and after the sdb3 partition, which is the space we want to expand. Select the sdb3 partition and click Resize. 3. You can drag the white partition of sdb3 to the leftmost and rightmost, or fill in 25958 with \"Previous Free Space\" as \"0\" and \"New Size\" as \"Maximum Size\", and then click Resize in the lower right corner. Then click OK to see that all unused space of sd has been used. 4. Insert the SD card into the device and start it.","title":"Method 2: Use GParted tool"},{"location":"Expand_Filesystem/#method-3-use-script","text":"If you are using a BliKVM image, you can run the following script on KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand.sh on any path, and write the following content to expand.sh. If your hardware is v1 , v2 or v3 , use: #!/bin/bash set -x resize_mmcblk0p3 () { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100 % resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" If your hardware is v4 , use: #!/bin/bash set -x resize_mmcblk0p1 () { echo \"Resizing mmcblk0p1 partition...\" parted /dev/mmcblk0 resizepart 1 100 % resize2fs /dev/mmcblk0p1 echo \"mmcblk0p1 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p1 echo \"Partition resizing completed.\" If you are using a PiKVM image, you can run the script below on the KVM to automatically expand the space. 1. Log in to the KVM terminal, confirm that the system has read and write permissions, run vim expand.sh on any path, and write the following content to expand.sh #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab ; then part = $( grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}' ) # shellcheck disable=SC2206 splitted =( ${ part //=/ } ) if [ \" ${ splitted [0] } \" == LABEL ] ; then label = ${ splitted [1] } part = $( blkid -c /dev/null -L \" $label \" ) else label = PIMSD fi unset splitted disk = /dev/ $( lsblk -no pkname \" $part \" ) npart = $( cat \"/sys/class/block/ ${ part // \\/ dev \\/ / } /partition\" ) umount \" $part \" parted \" $disk \" -a optimal -s resizepart \" $npart \" 100 % yes | mkfs.ext4 -L \" $label \" -F -m 0 \" $part \" mount \" $part \" unset disk part npart label fi 2. Execute bash expand.sh on the terminal and wait for the execution to complete.","title":"Method 3: Use script"},{"location":"OLED-display/","text":"Principle After v1.5.0 version, to avoid OLED/LCD display burn-in the display's on-time is only turned on according to its configuration. Configuration // All time-parameters are in seconds, and are required to be integer multiples of 5. // This json file is on /mnt/exec/release/config/app.json \"Display\":{ \"isActive\": true, \"mode\": 1, \"onBootTime\": 3600, \"cycleInterval\": 300, \"displayTime\": 30, } Use isActive to activate the display :rotating_light: . While \"isActive\": \"false\" , the display will not function. All BliKVM versions mode 0 always on, doesn't care about any of the paramters 1 Display remains on for onBootTime seconds, after which the display turns off. Depends on \"onBootTime\" 2 Every period of cycleInterval , the display turns on for displayTime seconds`, then turns off. :rotating_light: Depends on \"cycleInterval\"and \"displayTime\" Only BliKVM v4 Allwinner Since v4 has the sw1 buttons, if set mode to 1. Behavior: On Boot: the display turns on for onBootTime seconds, then automatically turns off. On Button Press (sw1): Pressing sw1 turns on the display for displayTime seconds. If the display is already on, pressing sw1 will have no impact at all.","title":"OLED Display"},{"location":"OLED-display/#principle","text":"After v1.5.0 version, to avoid OLED/LCD display burn-in the display's on-time is only turned on according to its configuration.","title":"Principle"},{"location":"OLED-display/#configuration","text":"// All time-parameters are in seconds, and are required to be integer multiples of 5. // This json file is on /mnt/exec/release/config/app.json \"Display\":{ \"isActive\": true, \"mode\": 1, \"onBootTime\": 3600, \"cycleInterval\": 300, \"displayTime\": 30, } Use isActive to activate the display :rotating_light: . While \"isActive\": \"false\" , the display will not function.","title":"Configuration"},{"location":"OLED-display/#all-blikvm-versions","text":"mode 0 always on, doesn't care about any of the paramters 1 Display remains on for onBootTime seconds, after which the display turns off. Depends on \"onBootTime\" 2 Every period of cycleInterval , the display turns on for displayTime seconds`, then turns off. :rotating_light: Depends on \"cycleInterval\"and \"displayTime\"","title":"All BliKVM versions"},{"location":"OLED-display/#only-blikvm-v4-allwinner","text":"Since v4 has the sw1 buttons, if set mode to 1. Behavior: On Boot: the display turns on for onBootTime seconds, then automatically turns off. On Button Press (sw1): Pressing sw1 turns on the display for displayTime seconds. If the display is already on, pressing sw1 will have no impact at all.","title":"Only BliKVM v4 Allwinner"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4/","text":"BliKVM v1 (RPI CM4) BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals! Connectivity diagram 1 OTG port 7 Micro SD card slot 2 USB3.0 x2 8 ACT LED (green) 3 ATX control port 9 Ethernet port 4 HDMI video input port 10 OLED Display 5 PWR IN port 11 Antenna mounting hole 6 Power LED (red) Specifications Parameter name Characteristics Power 5V 3A PWR IN port Connectivity/Interfaces HDMI IN HDMI video input port OTG Keyboard, mouse, mass storage, and other external device emulation CN-ATX Turn on/off or restart the controlled computer Micro SD card slot Persistent storage for OS and your data PWR IN port 5V 3A power port Displays and indicators LED indicators Power LED (red), ACT LED (green) OLED display OLED 128x64 0.96 inch Video Supported resolutions Up to 1920x1200@60Hz Video compression methods H.264, MJPEG Core Chip Raspberry Pi Compute Module 4 Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 120(L) x 70W) x 37(H) mm Weight 0.45 kg Dimensions Schematic Diagram","title":"BliKVM v1 (RPI CM4)"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4/#blikvm-v1-rpi-cm4","text":"BliKVM is a production-ready, plug and play KVM-over-IP device that offers professional users a convenient solution for remote server or workstation management . It is based on Linux and fully open source. With BliKVM, you can easily power on/off, restart your computer, configure UEFI/BIOS settings, and perform OS reinstallation using an emulated Mass Storage Device . BliKVM simulates a keyboard, mouse, and monitor, all accessible through a web browser, ensuring a seamless user experience. Its hardware-level access guarantees independence from specific remote ports, protocols, or services , making it a highly flexible and reliable remote management solution for professionals!","title":"BliKVM v1 (RPI CM4)"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4/#connectivity-diagram","text":"1 OTG port 7 Micro SD card slot 2 USB3.0 x2 8 ACT LED (green) 3 ATX control port 9 Ethernet port 4 HDMI video input port 10 OLED Display 5 PWR IN port 11 Antenna mounting hole 6 Power LED (red)","title":"Connectivity diagram"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4/#specifications","text":"Parameter name Characteristics Power 5V 3A PWR IN port Connectivity/Interfaces HDMI IN HDMI video input port OTG Keyboard, mouse, mass storage, and other external device emulation CN-ATX Turn on/off or restart the controlled computer Micro SD card slot Persistent storage for OS and your data PWR IN port 5V 3A power port Displays and indicators LED indicators Power LED (red), ACT LED (green) OLED display OLED 128x64 0.96 inch Video Supported resolutions Up to 1920x1200@60Hz Video compression methods H.264, MJPEG Core Chip Raspberry Pi Compute Module 4 Power consumption Up to 15W Environmental Operating temperature 0\u00b0C to 70\u00b0C Storage temperature -20\u00b0C to 60\u00b0C Dimensions and weight Size 120(L) x 70W) x 37(H) mm Weight 0.45 kg","title":"Specifications"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4/#dimensions-schematic-diagram","text":"","title":"Dimensions Schematic Diagram"},{"location":"atx-guide/","text":"ATXA guide 1. Introduction ATXA is an ATX adapter board to manage the power of your computer. The product includes two modules; A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable. Join the Discord Community Chat for news, questions and support! ATXA_A ATXA_B 2. A-board A-board is connected to the Raspberry Pi. The following table is a typical connection method in PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed 3. B-board The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B Instructions for connecting to the computer motherboard According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the ATXA-B motherboard. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and ATXA-B. See the following figure for the connection relationship\uff1a 4.Mechanical Diagram 5. Test video YouTube: ATX 6. Purchase Purchase\uff1a ATX","title":"ATX Guide"},{"location":"atx-guide/#atxa-guide","text":"","title":"ATXA guide"},{"location":"atx-guide/#1-introduction","text":"ATXA is an ATX adapter board to manage the power of your computer. The product includes two modules; A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable. Join the Discord Community Chat for news, questions and support! ATXA_A ATXA_B","title":"1. Introduction"},{"location":"atx-guide/#2-a-board","text":"A-board is connected to the Raspberry Pi. The following table is a typical connection method in PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed","title":"2. A-board"},{"location":"atx-guide/#3-b-board","text":"The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B Instructions for connecting to the computer motherboard According to the instructions of the computer motherboard, first find the position of the ATX function related pins on the motherboard, and then unplug the ATX ray that has been connected to the motherboard. After unplugging, the power button of the computer will lose its function. There are two rows of 8PIN pins on the ATXA-B motherboard. It is unnecessary to distinguish between the two rows of pins when they are used with the same functions. One row of pins is used for KVM to control ATX-related functions, and the other row of pins is connected to the ATX DuPont head unplugged from the main board to maintain the original chassis power button function. Connect each wire according to the specific pin definitions on the motherboard and ATXA-B. See the following figure for the connection relationship\uff1a","title":"3. B-board"},{"location":"atx-guide/#4mechanical-diagram","text":"","title":"4.Mechanical Diagram"},{"location":"atx-guide/#5-test-video","text":"YouTube: ATX","title":"5. Test video"},{"location":"atx-guide/#6-purchase","text":"Purchase\uff1a ATX","title":"6. Purchase"},{"location":"atx/","text":"ATX Control Board To manage the power of your computer, you need to install an ATX control board inside the chassis and connect it to the motherboard (to enable KVM control of power on/off via the ATX switch). There is a female-to-female cable that connects from the motherboard to the ATX control board and a male-to-female cable that connects from the ATX control board to the front panel (to keep the power on/off button on the chassis functional). The interface on the ATX control board has two ports (TO CASE, TO MB), and both ports have the same functionality, so they can be used interchangeably. ATX compatibility Laptops are not compatible with ATX as they lack the required ATX pins. This method is only applicable to Desktop PC's and servers. Detailed Instructions 1. Connect the two cables to the ATX control board. To secure the ATX control board inside the chassis, you can choose to mount it on a bracket attached to a PCIe slot. Example 2. Locate the motherboard pins responsible for connecting the front panel buttons and LEDs and disconnect them. Usually, the cables and connectors on the motherboard are labeled. If you're unsure, you can refer to your motherboard's documentation. Example 3. Connect the DuPont male connector from the front panel to the DuPont female connector on the ATX cable, following the pin definitions and paying attention to the labels and polarity (+ or -). Example 4. Using the same method, connect the female pins from the ATX board to the corresponding connector on the motherboard. Refer to your motherboard's documentation to determine which pins on the motherboard connect to which pins on the ATX control board. Sometimes, this information is printed on the motherboard. Example 5. Install the ATX board into a PCI slot on the chassis and secure it with screws or use alternative mounting methods according to your preference. Example 6. Arrange the cables neatly and secure them as needed. Make sure the cables do not come into contact with any fans inside the chassis. Use an Ethernet cable to connect the ATX board to the ATX interface of the BliKVM. With this, the hardware connection of the ATX control board is complete.","title":"ATX Control Board"},{"location":"atx/#atx-control-board","text":"To manage the power of your computer, you need to install an ATX control board inside the chassis and connect it to the motherboard (to enable KVM control of power on/off via the ATX switch). There is a female-to-female cable that connects from the motherboard to the ATX control board and a male-to-female cable that connects from the ATX control board to the front panel (to keep the power on/off button on the chassis functional). The interface on the ATX control board has two ports (TO CASE, TO MB), and both ports have the same functionality, so they can be used interchangeably. ATX compatibility Laptops are not compatible with ATX as they lack the required ATX pins. This method is only applicable to Desktop PC's and servers.","title":"ATX Control Board"},{"location":"atx/#detailed-instructions","text":"1. Connect the two cables to the ATX control board. To secure the ATX control board inside the chassis, you can choose to mount it on a bracket attached to a PCIe slot. Example 2. Locate the motherboard pins responsible for connecting the front panel buttons and LEDs and disconnect them. Usually, the cables and connectors on the motherboard are labeled. If you're unsure, you can refer to your motherboard's documentation. Example 3. Connect the DuPont male connector from the front panel to the DuPont female connector on the ATX cable, following the pin definitions and paying attention to the labels and polarity (+ or -). Example 4. Using the same method, connect the female pins from the ATX board to the corresponding connector on the motherboard. Refer to your motherboard's documentation to determine which pins on the motherboard connect to which pins on the ATX control board. Sometimes, this information is printed on the motherboard. Example 5. Install the ATX board into a PCI slot on the chassis and secure it with screws or use alternative mounting methods according to your preference. Example 6. Arrange the cables neatly and secure them as needed. Make sure the cables do not come into contact with any fans inside the chassis. Use an Ethernet cable to connect the ATX board to the ATX interface of the BliKVM. With this, the hardware connection of the ATX control board is complete.","title":"Detailed Instructions"},{"location":"bliswitch-v1-guide/","text":"BliSwitch v1 4-port KVM switch BliKVM-Switch-V1.0 uses and tests video, supporting BliKVM and PiKVM Introduction BliKVM-Switch-V1.0 is a four channel HDMI+USB switch, which supports panel button, desktop controller and KVM remote to switch between computers. Maximum support of the switch itself 4K@60HZ Plug and play, driver free. BliKVM-Switch-V1.0 uses the same hardware solution as XH-HK4401, AG7210 HDMI switching chip supports up to 4K@60Hz, CH444G USB switching chip supports USB2.0. The difference is that BliKVM-Switch-V1.0 is equipped with KVM USB cable, which can realize KVM port selection. BliKVM-Switch-V1.0 is compatible with BliKVM and PiKVM. points for attention The switch can be powered directly from the USB input to the computer, that is, the switch can work normally without power supply. If the USB power supply of the controlled computer cannot make the switch work, the switch can be powered independently. The switch package only provides a USB power cable, but does not provide a power adapter. The customer needs to configure a power adapter (5V). Desktop controller can control HDMI switch with USB cable. For customers who do not use KVM, this is another way of switching for easy cable management. HDMI input support up to 4096x2160/60Hz resolution 4K 60Hz input, the power is about 200 mW. Interface Diagram There must be 2 USB cables from KVM to BliKVM, one for controller, and second from USB on KVM to USB-PC on BliKVM. Front and back interface diagram, the control interface in the right figure is the remote control interface.A cable with one end being USB-A and the other end being micro USB, labeled with the word \"KVM,\" serves as the control cable. The micro USB end is connected to the control interface of the switch, while the USB-A end is connected to the USB port of the KVM. Schematic Diagram of Side Interface. Equipment connection diagram. Software Configuration If you are using BliKVM software and have powered on the switch and connected the cables before starting BliKVM, no additional configuration is needed. BliKVM will automatically detect the switch when it starts. If automatic detection fails, you can manually specify the switch device: Confirm the device descriptor name of the switch by using the terminal, such as /dev/ttyUSB0 . Edit the switch_handle field in /usr/bin/blikvm/package.json . Set switch_enable to 1 and switch_path to /dev/ttyUSB0 in the configuration. Restart BliKVM. Click MORE in the lower left corner, find the BliKVM switch column, and then switch. Note that the flashing blue dot of the corresponding channel indicates that the switch insertion is recognized and is in the current channel. If there is no blue dot, the switch insertion is not recognized. If you use PiKVM software, please configure it according to the following instructions. Log in to PiKVM through SSH. The user name and password are root; Uses the rw command on the terminal to change the system to a read-write system; Edit /etc/kvmd/override.yaml . After the original content, add: kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] The above configuration is based on the 2022 PiKVM image. If you are using the latest PiKVM image or latest software version, edit /etc/kvmd/override.yaml and add the line: protocol: 2 . Example: kvmd: gpio: drivers: hk: type: xh_hk4401 protocol: 2 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk ... Use the ro command on the terminal to reset the system to a read-only system; Use systemctl restart kvmd on the terminal to restart the service; Enter the PiKVM web interface and click the \"GPIO\" menu. You should see 4 inputs, one of which has a green circle to indicate that it is currently selected. Click a different input to change the selected host. Control Protocol If you want to use the blicube switch on other platforms, please refer to the following protocol The communication baud rate is 19200 The message to switch to channel 1 is SW1\\r\\nG01gA The message to switch to channel 2 is SW2\\r\\nG02gA The message to switch to channel 3 is SW3\\r\\nG03gA The message to switch to channel 4 is SW4\\r\\nG04gA The message returned by the switch for the current channel is: G01gA , G02gA , G03gA , G04gA Packing List product quantity note HDMI KVM Switch(4-channel) 1 110mm * 60mm * 33mm Desktop controller 1 USB cable of Desktop controller 4 length: 1.2m HDMI(Standard) cable 5 length: 1.5m USB power cable 1 length: 0.8m USB cable of KVM 1 length: 1.5m USB cable of Desktop controller 1 length: 1m","title":"Multiport BliSwitch v1 (4-port)"},{"location":"bliswitch-v1-guide/#bliswitch-v1-4-port-kvm-switch","text":"BliKVM-Switch-V1.0 uses and tests video, supporting BliKVM and PiKVM","title":"BliSwitch v1 4-port KVM switch"},{"location":"bliswitch-v1-guide/#introduction","text":"BliKVM-Switch-V1.0 is a four channel HDMI+USB switch, which supports panel button, desktop controller and KVM remote to switch between computers. Maximum support of the switch itself 4K@60HZ Plug and play, driver free. BliKVM-Switch-V1.0 uses the same hardware solution as XH-HK4401, AG7210 HDMI switching chip supports up to 4K@60Hz, CH444G USB switching chip supports USB2.0. The difference is that BliKVM-Switch-V1.0 is equipped with KVM USB cable, which can realize KVM port selection. BliKVM-Switch-V1.0 is compatible with BliKVM and PiKVM. points for attention The switch can be powered directly from the USB input to the computer, that is, the switch can work normally without power supply. If the USB power supply of the controlled computer cannot make the switch work, the switch can be powered independently. The switch package only provides a USB power cable, but does not provide a power adapter. The customer needs to configure a power adapter (5V). Desktop controller can control HDMI switch with USB cable. For customers who do not use KVM, this is another way of switching for easy cable management. HDMI input support up to 4096x2160/60Hz resolution 4K 60Hz input, the power is about 200 mW.","title":"Introduction"},{"location":"bliswitch-v1-guide/#interface-diagram","text":"There must be 2 USB cables from KVM to BliKVM, one for controller, and second from USB on KVM to USB-PC on BliKVM. Front and back interface diagram, the control interface in the right figure is the remote control interface.A cable with one end being USB-A and the other end being micro USB, labeled with the word \"KVM,\" serves as the control cable. The micro USB end is connected to the control interface of the switch, while the USB-A end is connected to the USB port of the KVM. Schematic Diagram of Side Interface. Equipment connection diagram.","title":"Interface Diagram"},{"location":"bliswitch-v1-guide/#software-configuration","text":"If you are using BliKVM software and have powered on the switch and connected the cables before starting BliKVM, no additional configuration is needed. BliKVM will automatically detect the switch when it starts. If automatic detection fails, you can manually specify the switch device: Confirm the device descriptor name of the switch by using the terminal, such as /dev/ttyUSB0 . Edit the switch_handle field in /usr/bin/blikvm/package.json . Set switch_enable to 1 and switch_path to /dev/ttyUSB0 in the configuration. Restart BliKVM. Click MORE in the lower left corner, find the BliKVM switch column, and then switch. Note that the flashing blue dot of the corresponding channel indicates that the switch insertion is recognized and is in the current channel. If there is no blue dot, the switch insertion is not recognized. If you use PiKVM software, please configure it according to the following instructions. Log in to PiKVM through SSH. The user name and password are root; Uses the rw command on the terminal to change the system to a read-write system; Edit /etc/kvmd/override.yaml . After the original content, add: kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] The above configuration is based on the 2022 PiKVM image. If you are using the latest PiKVM image or latest software version, edit /etc/kvmd/override.yaml and add the line: protocol: 2 . Example: kvmd: gpio: drivers: hk: type: xh_hk4401 protocol: 2 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk ... Use the ro command on the terminal to reset the system to a read-only system; Use systemctl restart kvmd on the terminal to restart the service; Enter the PiKVM web interface and click the \"GPIO\" menu. You should see 4 inputs, one of which has a green circle to indicate that it is currently selected. Click a different input to change the selected host.","title":"Software Configuration"},{"location":"bliswitch-v1-guide/#control-protocol","text":"If you want to use the blicube switch on other platforms, please refer to the following protocol The communication baud rate is 19200 The message to switch to channel 1 is SW1\\r\\nG01gA The message to switch to channel 2 is SW2\\r\\nG02gA The message to switch to channel 3 is SW3\\r\\nG03gA The message to switch to channel 4 is SW4\\r\\nG04gA The message returned by the switch for the current channel is: G01gA , G02gA , G03gA , G04gA","title":"Control Protocol"},{"location":"bliswitch-v1-guide/#packing-list","text":"product quantity note HDMI KVM Switch(4-channel) 1 110mm * 60mm * 33mm Desktop controller 1 USB cable of Desktop controller 4 length: 1.2m HDMI(Standard) cable 5 length: 1.5m USB power cable 1 length: 0.8m USB cable of KVM 1 length: 1.5m USB cable of Desktop controller 1 length: 1m","title":"Packing List"},{"location":"bliswitch-v2-guide/","text":"BliSwitch v2 8-port KVM+ATX switch The BliSwitch v2 is an 8-channel KVM+ATX switch for 8 hosts to share input and power. Function: 8 hosts share a keyboard, mouse, and display, with power control for all. Switch Method: Button or USB control. Features ATX on each port(support button and remote control) Full control via web ui Compatible with BLIKVM V1, V2, V3 V4 and PikVM hardware. Port Definition Product Parameters Brand BLI Name 8-port KVM+ATX switcher Model BliSwitch v2 Function Eight hosts share a set of keyboard, mouse, and display, power control of 8 hosts Material All metal Resolution 1080P60Hz Switching Method Button switching or USB control module switching Power Supply 5V1A Control Protocol If you want to use Blicube's switch on other platforms, please refer to the following protocol Communication baud rate is 19200 The message to switch to channel 1 is SW1\\r\\nG01gA The message to switch to channel 2 is SW2\\r\\nG02gA The message to switch to channel 3 is SW3\\r\\nG03gA The message to switch to channel 4 is SW4\\r\\nG04gA The message to switch to channel 5 is SW5\\r\\nG05gA The message to switch to channel 6 is SW6\\r\\nG06gA The message to switch to channel 7 is SW7\\r\\nG07gA The message to switch to channel 8 is SW8\\r\\nG08gigA The message returned by the switch for the current channel is: G01gA, G02gA, G03gA, G04gA, G05gA, G06gA, G07gA, G08gA Connection Reference Dimensions Shipping List Product Quantity Remarks BliSwitch v4 switcher 1 Mounting ears 2 ATX cable male end 8 ATX cable female end 8 Full-height PCIe bracket 8 Half-height PCIe bracket 8 ATX board 8 Control cable 1 USB cable 1 Rubber pads 4 M2.5x5 countersunk screws 10 Buy link Buy Bliswitch v2","title":"Multiport BliSwitch v2 (8-port)"},{"location":"bliswitch-v2-guide/#bliswitch-v2-8-port-kvmatx-switch","text":"The BliSwitch v2 is an 8-channel KVM+ATX switch for 8 hosts to share input and power. Function: 8 hosts share a keyboard, mouse, and display, with power control for all. Switch Method: Button or USB control.","title":"BliSwitch v2 8-port KVM+ATX switch"},{"location":"bliswitch-v2-guide/#features","text":"ATX on each port(support button and remote control) Full control via web ui Compatible with BLIKVM V1, V2, V3 V4 and PikVM hardware.","title":"Features"},{"location":"bliswitch-v2-guide/#port-definition","text":"","title":"Port Definition"},{"location":"bliswitch-v2-guide/#product-parameters","text":"Brand BLI Name 8-port KVM+ATX switcher Model BliSwitch v2 Function Eight hosts share a set of keyboard, mouse, and display, power control of 8 hosts Material All metal Resolution 1080P60Hz Switching Method Button switching or USB control module switching Power Supply 5V1A","title":"Product Parameters"},{"location":"bliswitch-v2-guide/#control-protocol","text":"If you want to use Blicube's switch on other platforms, please refer to the following protocol Communication baud rate is 19200 The message to switch to channel 1 is SW1\\r\\nG01gA The message to switch to channel 2 is SW2\\r\\nG02gA The message to switch to channel 3 is SW3\\r\\nG03gA The message to switch to channel 4 is SW4\\r\\nG04gA The message to switch to channel 5 is SW5\\r\\nG05gA The message to switch to channel 6 is SW6\\r\\nG06gA The message to switch to channel 7 is SW7\\r\\nG07gA The message to switch to channel 8 is SW8\\r\\nG08gigA The message returned by the switch for the current channel is: G01gA, G02gA, G03gA, G04gA, G05gA, G06gA, G07gA, G08gA","title":"Control Protocol"},{"location":"bliswitch-v2-guide/#connection-reference","text":"","title":"Connection Reference"},{"location":"bliswitch-v2-guide/#dimensions","text":"","title":"Dimensions"},{"location":"bliswitch-v2-guide/#shipping-list","text":"Product Quantity Remarks BliSwitch v4 switcher 1 Mounting ears 2 ATX cable male end 8 ATX cable female end 8 Full-height PCIe bracket 8 Half-height PCIe bracket 8 ATX board 8 Control cable 1 USB cable 1 Rubber pads 4 M2.5x5 countersunk screws 10","title":"Shipping List"},{"location":"bliswitch-v2-guide/#buy-link","text":"Buy Bliswitch v2","title":"Buy link"},{"location":"dev_api/","text":"API DISCLAIMER: This API is experimental and subject to change at any moment! This document is only valid for v1.4.0 and earlier versions, and will be updated soon This document is the HTTP API development manual for BLIKVM OS. If you have new API requirements not covered in this document, you can submit a pull request on GitHub to seek support. Please replace the kvmip in the request URL with the actual IP address of your KVM. Authentication This API is used for user login and returns an access token. Some APIs within the system require a valid token for access. Request URL: http://kvmip/login_api Request Method: GET Request Body: JSON format, for example: { \"username\": \"admin\", \"password\": \"admin\" } The response is as follows; if the status is not 1, the authentication has failed. { \"status\": 1, \"info\": \"login success\", \"data\": { \"token\": \"2sscdada6a97a774fcd4714c\" } } MJPEG Video This API is used to obtain the MJPEG video stream when the image mode is set to MJPEG. Request URL: http://kvmip:8008/stream This API is used to capture a frame of MJPEG in image mode. Request URL: http://kvmip:8008/snapshot Request Method: GET Keyboard For specific keyboard encoding, please refer to the following: \"KeyA\"=> 4, \"KeyB\"=> 5, \"KeyC\"=> 6, \"KeyD\"=> 7, \"KeyE\"=> 8, \"KeyF\"=> 9, \"KeyG\"=> 10, \"KeyH\"=> 11, \"KeyI\"=> 12, \"KeyJ\"=> 13, \"KeyK\"=> 14, \"KeyL\"=> 15, \"KeyM\"=> 16, \"KeyN\"=> 17, \"KeyO\"=> 18, \"KeyP\"=> 19, \"KeyQ\"=> 20, \"KeyR\"=> 21, \"KeyS\"=> 22, \"KeyT\"=> 23, \"KeyU\"=> 24, \"KeyV\"=> 25, \"KeyW\"=> 26, \"KeyX\"=> 27, \"KeyY\"=> 28, \"KeyZ\"=> 29, \"Digit1\"=> 30, \"Digit2\"=> 31, \"Digit3\"=> 32, \"Digit4\"=> 33, \"Digit5\"=> 34, \"Digit6\"=> 35, \"Digit7\"=> 36, \"Digit8\"=> 37, \"Digit9\"=> 38, \"Digit0\"=> 39, \"Enter\"=> 40, \"Escape\"=> 41, \"Backspace\"=> 42, \"Tab\"=> 43, \"Space\"=> 44, \"Minus\"=> 45, \"Equal\"=> 46, \"BracketLeft\"=> 47, \"BracketRight\"=> 48, \"Backslash\"=> 49, \"Semicolon\"=> 51, \"Quote\"=> 52, \"Backquote\"=> 53, \"Comma\"=> 54, \"Period\"=> 55, \"Slash\"=> 56, \"CapsLock\"=> 57, \"F1\"=> 58, \"F2\"=> 59, \"F3\"=> 60, \"F4\"=> 61, \"F5\"=> 62, \"F6\"=> 63, \"F7\"=> 64, \"F8\"=> 65, \"F9\"=> 66, \"F10\"=> 67, \"F11\"=> 68, \"F12\"=> 69, \"PrtSc\"=> 70, \"ScrollLock\"=> 71, \"Pause\"=> 72, \"Insert\"=> 73, \"Home\"=> 74, \"PageUp\"=> 75, \"Delete\"=> 76, \"End\"=> 77, \"PageDown\"=> 78, \"ArrowRight\"=> 79, \"ArrowLeft\"=> 80, \"ArrowDown\"=> 81, \"ArrowUp\"=> 82, \"NumLock\"=> 83, \"NumpadDivide\"=> 84, \"NumpadMultiply\"=> 85, \"NumpadSubtract\"=> 86, \"NumpadAdd\"=> 87, \"NumpadEnter\"=> 88, \"Numpad1\"=> 89, \"Numpad2\"=> 90, \"Numpad3\"=> 91, \"Numpad4\"=> 92, \"Numpad5\"=> 93, \"Numpad6\"=> 94, \"Numpad7\"=> 95, \"Numpad8\"=> 96, \"Numpad9\"=> 97, \"Numpad0\"=> 98, \"NumpadDecimal\"=> 99 Request URL: http://kvmip/keyboard Request Method: GET Request Body: JSON format, where \"keycodes\" is a string array supporting multiple inputs at once. For example: { \"keycodes\": [\"Digit1\"] } The response result is as follows: { \"status\": 1, \"info\": \"key input success\", \"data\": [] }","title":"HTTP API"},{"location":"dev_api/#api","text":"DISCLAIMER: This API is experimental and subject to change at any moment! This document is only valid for v1.4.0 and earlier versions, and will be updated soon This document is the HTTP API development manual for BLIKVM OS. If you have new API requirements not covered in this document, you can submit a pull request on GitHub to seek support. Please replace the kvmip in the request URL with the actual IP address of your KVM.","title":"API"},{"location":"dev_api/#authentication","text":"This API is used for user login and returns an access token. Some APIs within the system require a valid token for access. Request URL: http://kvmip/login_api Request Method: GET Request Body: JSON format, for example: { \"username\": \"admin\", \"password\": \"admin\" } The response is as follows; if the status is not 1, the authentication has failed. { \"status\": 1, \"info\": \"login success\", \"data\": { \"token\": \"2sscdada6a97a774fcd4714c\" } }","title":"Authentication"},{"location":"dev_api/#mjpeg-video","text":"This API is used to obtain the MJPEG video stream when the image mode is set to MJPEG. Request URL: http://kvmip:8008/stream This API is used to capture a frame of MJPEG in image mode. Request URL: http://kvmip:8008/snapshot Request Method: GET","title":"MJPEG Video"},{"location":"dev_api/#keyboard","text":"For specific keyboard encoding, please refer to the following: \"KeyA\"=> 4, \"KeyB\"=> 5, \"KeyC\"=> 6, \"KeyD\"=> 7, \"KeyE\"=> 8, \"KeyF\"=> 9, \"KeyG\"=> 10, \"KeyH\"=> 11, \"KeyI\"=> 12, \"KeyJ\"=> 13, \"KeyK\"=> 14, \"KeyL\"=> 15, \"KeyM\"=> 16, \"KeyN\"=> 17, \"KeyO\"=> 18, \"KeyP\"=> 19, \"KeyQ\"=> 20, \"KeyR\"=> 21, \"KeyS\"=> 22, \"KeyT\"=> 23, \"KeyU\"=> 24, \"KeyV\"=> 25, \"KeyW\"=> 26, \"KeyX\"=> 27, \"KeyY\"=> 28, \"KeyZ\"=> 29, \"Digit1\"=> 30, \"Digit2\"=> 31, \"Digit3\"=> 32, \"Digit4\"=> 33, \"Digit5\"=> 34, \"Digit6\"=> 35, \"Digit7\"=> 36, \"Digit8\"=> 37, \"Digit9\"=> 38, \"Digit0\"=> 39, \"Enter\"=> 40, \"Escape\"=> 41, \"Backspace\"=> 42, \"Tab\"=> 43, \"Space\"=> 44, \"Minus\"=> 45, \"Equal\"=> 46, \"BracketLeft\"=> 47, \"BracketRight\"=> 48, \"Backslash\"=> 49, \"Semicolon\"=> 51, \"Quote\"=> 52, \"Backquote\"=> 53, \"Comma\"=> 54, \"Period\"=> 55, \"Slash\"=> 56, \"CapsLock\"=> 57, \"F1\"=> 58, \"F2\"=> 59, \"F3\"=> 60, \"F4\"=> 61, \"F5\"=> 62, \"F6\"=> 63, \"F7\"=> 64, \"F8\"=> 65, \"F9\"=> 66, \"F10\"=> 67, \"F11\"=> 68, \"F12\"=> 69, \"PrtSc\"=> 70, \"ScrollLock\"=> 71, \"Pause\"=> 72, \"Insert\"=> 73, \"Home\"=> 74, \"PageUp\"=> 75, \"Delete\"=> 76, \"End\"=> 77, \"PageDown\"=> 78, \"ArrowRight\"=> 79, \"ArrowLeft\"=> 80, \"ArrowDown\"=> 81, \"ArrowUp\"=> 82, \"NumLock\"=> 83, \"NumpadDivide\"=> 84, \"NumpadMultiply\"=> 85, \"NumpadSubtract\"=> 86, \"NumpadAdd\"=> 87, \"NumpadEnter\"=> 88, \"Numpad1\"=> 89, \"Numpad2\"=> 90, \"Numpad3\"=> 91, \"Numpad4\"=> 92, \"Numpad5\"=> 93, \"Numpad6\"=> 94, \"Numpad7\"=> 95, \"Numpad8\"=> 96, \"Numpad9\"=> 97, \"Numpad0\"=> 98, \"NumpadDecimal\"=> 99 Request URL: http://kvmip/keyboard Request Method: GET Request Body: JSON format, where \"keycodes\" is a string array supporting multiple inputs at once. For example: { \"keycodes\": [\"Digit1\"] } The response result is as follows: { \"status\": 1, \"info\": \"key input success\", \"data\": [] }","title":"Keyboard"},{"location":"edid/","text":"EDID The EDID file in BliKVM serves the purpose of informing the controlled computer about the expected HDMI output resolution. For example, if the EDID is set to 1080P60Hz, and the controlled computer supports this resolution, it will output at 1080P60Hz. Additionally, EDID can be used to disable audio, modify the display model, name, manufacturer, and other information. In most cases, you don't need to change it, but sometimes, especially with strange UEFI/BIOS behavior, it may be necessary. Note BliKVM v1, v2, and v3 use the CSI video capture scheme, which supports EDID settings. However, BliKVM v4 uses the USB video capture scheme, which does not support EDID settings. For v3 HAT, there is a limitation of two CSI channels on the Raspberry Pi 4B, which means it can only capture video input with a maximum resolution of 1080P50Hz. Therefore, if you set 1080P60Hz EDID for v3, it will not be able to capture the image. If you are using PiKVM OS, you can refer to this link for modification instructions. If you are using BliKVM OS, the EDID file is located at /usr/bin/blikvm/edid.txt . Open this file, and replace the EDID contents with the desired resolution's EDID. EDID Examples for 1080P60Hz The following EDID is suitable for v1 and v2 hardware. 1920x1080 60Hz, with audio 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C EDID Examples for 1080P50Hz The following EDID is suitable for v1, v2, and v3 hardware, especially when you want v3 HAT to capture 1080P resolution. 1920x1080 50Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028 EDID Examples for 720P60Hz The following EDID is suitable for v1, v2, and v3 hardware. 1280x720 60Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 Custom EDID To customize the EDID, it is best to use third-party utilities, such as the recommended advanced AW EDID Editor (works well in Windows and can be used in wine) or wxEDID . Both editors work with the binary EDID format. Using these tools, you can modify the EDID information like editing a file, similar to changing the information on an identity card. By editing the EDID, you can adjust the parameters and characteristics of the display to suit different usage requirements, and thus achieve better display performance.","title":"HDMI EDID"},{"location":"edid/#edid","text":"The EDID file in BliKVM serves the purpose of informing the controlled computer about the expected HDMI output resolution. For example, if the EDID is set to 1080P60Hz, and the controlled computer supports this resolution, it will output at 1080P60Hz. Additionally, EDID can be used to disable audio, modify the display model, name, manufacturer, and other information. In most cases, you don't need to change it, but sometimes, especially with strange UEFI/BIOS behavior, it may be necessary. Note BliKVM v1, v2, and v3 use the CSI video capture scheme, which supports EDID settings. However, BliKVM v4 uses the USB video capture scheme, which does not support EDID settings. For v3 HAT, there is a limitation of two CSI channels on the Raspberry Pi 4B, which means it can only capture video input with a maximum resolution of 1080P50Hz. Therefore, if you set 1080P60Hz EDID for v3, it will not be able to capture the image. If you are using PiKVM OS, you can refer to this link for modification instructions. If you are using BliKVM OS, the EDID file is located at /usr/bin/blikvm/edid.txt . Open this file, and replace the EDID contents with the desired resolution's EDID.","title":"EDID"},{"location":"edid/#edid-examples-for-1080p60hz","text":"The following EDID is suitable for v1 and v2 hardware. 1920x1080 60Hz, with audio 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C","title":"EDID Examples for 1080P60Hz"},{"location":"edid/#edid-examples-for-1080p50hz","text":"The following EDID is suitable for v1, v2, and v3 hardware, especially when you want v3 HAT to capture 1080P resolution. 1920x1080 50Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028","title":"EDID Examples for 1080P50Hz"},{"location":"edid/#edid-examples-for-720p60hz","text":"The following EDID is suitable for v1, v2, and v3 hardware. 1280x720 60Hz, with audio 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000","title":"EDID Examples for 720P60Hz"},{"location":"edid/#custom-edid","text":"To customize the EDID, it is best to use third-party utilities, such as the recommended advanced AW EDID Editor (works well in Windows and can be used in wine) or wxEDID . Both editors work with the binary EDID format. Using these tools, you can modify the EDID information like editing a file, similar to changing the information on an identity card. By editing the EDID, you can adjust the parameters and characteristics of the display to suit different usage requirements, and thus achieve better display performance.","title":"Custom EDID"},{"location":"faq/","text":"FAQ & Troubleshooting As a first step, we recommend carefully reading our documentation. Most steps to successfully set up your BLIKVM are already described there. If you run into any issues you can check this page 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. Common Questions Can I connect multiple servers to a single BLIKVM? Yes, but it requires additional work to set up. See this page . How can I get the access to PiKVM in my local network over Internet? If your router has an external IP address, you can use port forwarding to forward port 80 (Web), port 8008 (mjpeg), and port 8188 (webrtc) In all other cases, you can use the excellent free VPN service Tailscale. Which BLiKVM hardware version should I choose, such as BLiKVM V1 CM4, BLiKVM V2 PCIe, and BLiKVM V3 Hat? First, please refer to this page for a comparison of the main parameters of each version. V1 and V3 are external solutions, while V2 is an internal chassis solution. If you have a chassis and there is space inside, choosing the V2 PCIe version would be a better option. So how do you choose between the external solutions V1 and V3? V1 is based on the CM4 platform, with higher integration and ready-to-use versions available. V3 is based on the Raspberry Pi 4B platform, with all IO ports exposed and greater expandability. Another key difference is that V1 supports up to 1080P60Hz input, while V3 supports up to 1080P50Hz input. Of course, you also need to consider whether you already have a CM4 or 4B, as purchasing the corresponding baseboard would offer better cost-effectiveness. Can I use BLIKVM for gaming? No, because: For HDMI-CSI bridge, bus bandwidth is not enough to transmit more than 1080p60. For HDMI-USB dongle, high latency and low video quality. General hardware video capture differs from software streaming and introduces additional latency. Can BLIKVM do 4K video? For HDMI-CSI bridge, no. There is not enough bandwidth in the CSI bus for that much data. 1080p60 will max out the bandwidth. For the USB capture devices: technically yes, they will downsample to something smaller to meet the USB 2.0 bandwidth limitations, so the source may be 4k, but the stream will not. The 4K real-time video will not fit through the network anyway. Where does the cursor/video latency come from? Here is the chain of transferring an image to your browser or VNC client. Capture device -> Compression -> Network -> Decompression -> Rendering 100-200ms is very, very fast for this. But we are working to speed things up even more. Does BLIKVM support sound? BliKVM v1 CM4, v2 PCIe, v3 HAT version supported\uff0c v4 Allwinner not support now. Can I power the Pi via PoE? Yes! Hat and PCIe version supported. First Steps What is the default password? How do I change it? If you use PiKVM, there are two types of accounts: OS and PiKVM (web interface) accounts. The system account blikvm can be used for SSH/UART access and has the password blikvm . The web interface account is called admin and has the password admin . The PiKVM account cannot be used for SSH access and vice versa. To change passwords, use the following commands (become the root user): su - # If you're in the webterm rw # Switch filesystem to read-write mode passwd blikvm # Change blikvm user password kvmd-htpasswd set admin # Change web ui admin password ro # Back to read-only How do I add another user? If you use PiKVM software, as stated above you need to make 2 accounts, 1 for the shell, the other for the PiKVM Web UI. If you require additional users for PiKVM UI, you can use the following: # su - # rw # kvmd-htpasswd set # Adds a new user # kvmd-htpasswd set # Sets the password as long as the user exists # kvmd-htpasswd del # Removes/deletes a user To add a shell/terminal account: # su - # rw # adduser # passwd Keep in mind that the more users that are added and accessing the screen stream at the same time, the FPS will drop. Video Problems BLIKVM does not show the video from the computer at all If the output of dmesg | grep tc358743 does not show something similar as tc358743 found @ ... , then this means that the TC358743 HDMI input bridge is not detected. Verify that the flex flat cable (ffc) is correctly connected. Double-check that the video capture device is connected correctly. For the CSI bridge, this should be exactly the camera port. Some laptops do not output any signal until you switch the output (usually via the FN + and an F5 key on the keyboard). Your computer may have turned on sleep mode for the monitor. Move the mouse to turn it off. For windows you might need to check for the active signal resolution. To change the active signal resolution you have to go to Settings>System>Display>Advanced display settings>Display adapter properties then, click \"List All Models\" and choose the one you want. Keep trying different Hz settings. The video works in the booted OS, but not in the BIOS/UEFI This problem appears on Intel NUC, GA-H77-DS3H, and some other devices when using a CSI bridge. All you need to do is change the EDID data. This is the information about supported resolutions that the CSI bridge reports to your computer. Glitchy or wrong BIOS/UEFI 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: 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 (DP) 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. There is no video in GRUB2, but there is before and after Sometimes this can be caused by the specifics of the BIOS/UEFI and how GRUB2 works with video. This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. The video mode will be located in the same section. Switch the Video mode from UEFI to Legacy . No image from computer with Linux + Awesome WM 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 BLIKVM - it may happen that you will not see the image. It seems that the problem is Awesome WM, since for example with KDE, it is not reproducable. If you turn on your workstation with BLIKVM already connected, everything will work fine. USB Problems (keyboard, mouse, mass storage, etc) What speed is the USB OTG port? Per the official RPI documentation, this is a limitation of the SoC. The OTG port is only USB2.0, so is limited to 455 Mbit/s. Why can't some keyboard shortcuts of physical keyboards be captured while virtual keyboards can? For example, the F11 key on a Mac computer cannot be captured. This is because some shortcuts are already in use by the system, such as in macOS, where F11 is assigned to the \"Show Desktop\" function by default. When you press F11 in a web interface, the KeyboardEvent is first captured by the system, and if a callback is registered in the system, the event will not be passed to the application. To solve this issue, you can disable the system's assigned shortcut or use a virtual keyboard. Hardware Problems (Wi-Fi, ATX, etc) If you use PiKVM software, the web UI show FAN error! Because the fan model used by BLIKVM hardware is different from that of PIKVM hardware, viewing the fan status through the web interface may fail in the latest system of pikvm. However, this will not affect the normal operation of BLIKVM fan. Therefore, when using the PIKVM image, as long as you ensure that the install script displays OK, it means that the update of the kvmd fan program is successful. The threshold temperature set by the default program is 60 degrees Celsius. When the CPU temperature is detected to exceed 60 degrees Celsius, the fan will start rotating at 85% speed. If you want to modify the threshold temperature and speed, you can modify the kvmd-fan.py script, and then re-execute install.sh. I can't connect to Wi-Fi at all! If your device is unable to connect to the Wi-Fi network that you have set up, check the 2.4 GHz Wi-Fi channel used by your Wi-Fi access point. If channels 12 to 14 are used (some countries have banned these channels) try to use a channel between 1 and 11. BLIKVM complains about low power warnings Are you using a \"proper\" power supply? Not one you hacked together? Some USB power bricks advertise 5V 2.1A or higher, but can't deliver consistent 5V. Best to use Raspberry Pi Foundation recommended power supplies. It should be 5.1v and 3A DC output. When I use the PoE, do I still need to use the power OTG splitter to prevent back power on the machine usb? Only HAT version you need to use power OTG splitter to prevent back power. Generally, most hosts computer are protected back power, you do not need to usr power OTG splitter in this case. BLIKVM-CM4-V2.2 and BLIKVM-PCIe version don't need. In some board like BLIKVM-PCIe or BLIKVM-CM4-V2.2 has boot pin, how do I connect? If you short them, CM4 will not start normally, but will enter the burning image mode. If your hardware version of boot has only two pins, use the jumper cap to connect the two pins as a short circuit. If you do not use the jumper cap or plug it into one pin, CM4 will start normally. If you use three boot pins of the hardware version, use the jumper cap to connect GND and another non-GND pin to indicate short circuit, and plug the jumper cap on the two GND pins or do not use it, CM4 will start normally. Web Problems What ports does BliKVM OS occupy, and how should it be forwarded when using a public server? The web interface uses the HTTP protocol and occupies port 80. If you are using hardware versions V1, V2, or V3 with web-rtc transmission, the port is 8188. If you are using hardware version V4 with MJPEG transmission, the port is 8008. Please note that the ports cannot be modified; only port forwarding can be configured. Raspberry Problems Can I use both the CM4 version with EMMC and the SD card at the same time? No, you can't, When designing the CM4 hardware, several pins of the SD card are only valid in the lite version. You can find instructions on the official website of Raspberry Pi.","title":"FAQ"},{"location":"faq/#faq-troubleshooting","text":"As a first step, we recommend carefully reading our documentation. Most steps to successfully set up your BLIKVM are already described there. If you run into any issues you can check this page 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.","title":"FAQ & Troubleshooting"},{"location":"faq/#common-questions","text":"Can I connect multiple servers to a single BLIKVM? Yes, but it requires additional work to set up. See this page . How can I get the access to PiKVM in my local network over Internet? If your router has an external IP address, you can use port forwarding to forward port 80 (Web), port 8008 (mjpeg), and port 8188 (webrtc) In all other cases, you can use the excellent free VPN service Tailscale. Which BLiKVM hardware version should I choose, such as BLiKVM V1 CM4, BLiKVM V2 PCIe, and BLiKVM V3 Hat? First, please refer to this page for a comparison of the main parameters of each version. V1 and V3 are external solutions, while V2 is an internal chassis solution. If you have a chassis and there is space inside, choosing the V2 PCIe version would be a better option. So how do you choose between the external solutions V1 and V3? V1 is based on the CM4 platform, with higher integration and ready-to-use versions available. V3 is based on the Raspberry Pi 4B platform, with all IO ports exposed and greater expandability. Another key difference is that V1 supports up to 1080P60Hz input, while V3 supports up to 1080P50Hz input. Of course, you also need to consider whether you already have a CM4 or 4B, as purchasing the corresponding baseboard would offer better cost-effectiveness. Can I use BLIKVM for gaming? No, because: For HDMI-CSI bridge, bus bandwidth is not enough to transmit more than 1080p60. For HDMI-USB dongle, high latency and low video quality. General hardware video capture differs from software streaming and introduces additional latency. Can BLIKVM do 4K video? For HDMI-CSI bridge, no. There is not enough bandwidth in the CSI bus for that much data. 1080p60 will max out the bandwidth. For the USB capture devices: technically yes, they will downsample to something smaller to meet the USB 2.0 bandwidth limitations, so the source may be 4k, but the stream will not. The 4K real-time video will not fit through the network anyway. Where does the cursor/video latency come from? Here is the chain of transferring an image to your browser or VNC client. Capture device -> Compression -> Network -> Decompression -> Rendering 100-200ms is very, very fast for this. But we are working to speed things up even more. Does BLIKVM support sound? BliKVM v1 CM4, v2 PCIe, v3 HAT version supported\uff0c v4 Allwinner not support now. Can I power the Pi via PoE? Yes! Hat and PCIe version supported.","title":"Common Questions"},{"location":"faq/#first-steps","text":"What is the default password? How do I change it? If you use PiKVM, there are two types of accounts: OS and PiKVM (web interface) accounts. The system account blikvm can be used for SSH/UART access and has the password blikvm . The web interface account is called admin and has the password admin . The PiKVM account cannot be used for SSH access and vice versa. To change passwords, use the following commands (become the root user): su - # If you're in the webterm rw # Switch filesystem to read-write mode passwd blikvm # Change blikvm user password kvmd-htpasswd set admin # Change web ui admin password ro # Back to read-only How do I add another user? If you use PiKVM software, as stated above you need to make 2 accounts, 1 for the shell, the other for the PiKVM Web UI. If you require additional users for PiKVM UI, you can use the following: # su - # rw # kvmd-htpasswd set # Adds a new user # kvmd-htpasswd set # Sets the password as long as the user exists # kvmd-htpasswd del # Removes/deletes a user To add a shell/terminal account: # su - # rw # adduser # passwd Keep in mind that the more users that are added and accessing the screen stream at the same time, the FPS will drop.","title":"First Steps"},{"location":"faq/#video-problems","text":"BLIKVM does not show the video from the computer at all If the output of dmesg | grep tc358743 does not show something similar as tc358743 found @ ... , then this means that the TC358743 HDMI input bridge is not detected. Verify that the flex flat cable (ffc) is correctly connected. Double-check that the video capture device is connected correctly. For the CSI bridge, this should be exactly the camera port. Some laptops do not output any signal until you switch the output (usually via the FN + and an F5 key on the keyboard). Your computer may have turned on sleep mode for the monitor. Move the mouse to turn it off. For windows you might need to check for the active signal resolution. To change the active signal resolution you have to go to Settings>System>Display>Advanced display settings>Display adapter properties then, click \"List All Models\" and choose the one you want. Keep trying different Hz settings. The video works in the booted OS, but not in the BIOS/UEFI This problem appears on Intel NUC, GA-H77-DS3H, and some other devices when using a CSI bridge. All you need to do is change the EDID data. This is the information about supported resolutions that the CSI bridge reports to your computer. Glitchy or wrong BIOS/UEFI 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: 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 (DP) 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. There is no video in GRUB2, but there is before and after Sometimes this can be caused by the specifics of the BIOS/UEFI and how GRUB2 works with video. This can be solved by enabling the Compatibility Support Module (CSM) in your BIOS, usually under the Boot options. The video mode will be located in the same section. Switch the Video mode from UEFI to Legacy . No image from computer with Linux + Awesome WM 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 BLIKVM - it may happen that you will not see the image. It seems that the problem is Awesome WM, since for example with KDE, it is not reproducable. If you turn on your workstation with BLIKVM already connected, everything will work fine.","title":"Video Problems"},{"location":"faq/#usb-problems-keyboard-mouse-mass-storage-etc","text":"What speed is the USB OTG port? Per the official RPI documentation, this is a limitation of the SoC. The OTG port is only USB2.0, so is limited to 455 Mbit/s. Why can't some keyboard shortcuts of physical keyboards be captured while virtual keyboards can? For example, the F11 key on a Mac computer cannot be captured. This is because some shortcuts are already in use by the system, such as in macOS, where F11 is assigned to the \"Show Desktop\" function by default. When you press F11 in a web interface, the KeyboardEvent is first captured by the system, and if a callback is registered in the system, the event will not be passed to the application. To solve this issue, you can disable the system's assigned shortcut or use a virtual keyboard.","title":"USB Problems (keyboard, mouse, mass storage, etc)"},{"location":"faq/#hardware-problems-wi-fi-atx-etc","text":"If you use PiKVM software, the web UI show FAN error! Because the fan model used by BLIKVM hardware is different from that of PIKVM hardware, viewing the fan status through the web interface may fail in the latest system of pikvm. However, this will not affect the normal operation of BLIKVM fan. Therefore, when using the PIKVM image, as long as you ensure that the install script displays OK, it means that the update of the kvmd fan program is successful. The threshold temperature set by the default program is 60 degrees Celsius. When the CPU temperature is detected to exceed 60 degrees Celsius, the fan will start rotating at 85% speed. If you want to modify the threshold temperature and speed, you can modify the kvmd-fan.py script, and then re-execute install.sh. I can't connect to Wi-Fi at all! If your device is unable to connect to the Wi-Fi network that you have set up, check the 2.4 GHz Wi-Fi channel used by your Wi-Fi access point. If channels 12 to 14 are used (some countries have banned these channels) try to use a channel between 1 and 11. BLIKVM complains about low power warnings Are you using a \"proper\" power supply? Not one you hacked together? Some USB power bricks advertise 5V 2.1A or higher, but can't deliver consistent 5V. Best to use Raspberry Pi Foundation recommended power supplies. It should be 5.1v and 3A DC output. When I use the PoE, do I still need to use the power OTG splitter to prevent back power on the machine usb? Only HAT version you need to use power OTG splitter to prevent back power. Generally, most hosts computer are protected back power, you do not need to usr power OTG splitter in this case. BLIKVM-CM4-V2.2 and BLIKVM-PCIe version don't need. In some board like BLIKVM-PCIe or BLIKVM-CM4-V2.2 has boot pin, how do I connect? If you short them, CM4 will not start normally, but will enter the burning image mode. If your hardware version of boot has only two pins, use the jumper cap to connect the two pins as a short circuit. If you do not use the jumper cap or plug it into one pin, CM4 will start normally. If you use three boot pins of the hardware version, use the jumper cap to connect GND and another non-GND pin to indicate short circuit, and plug the jumper cap on the two GND pins or do not use it, CM4 will start normally.","title":"Hardware Problems (Wi-Fi, ATX, etc)"},{"location":"faq/#web-problems","text":"What ports does BliKVM OS occupy, and how should it be forwarded when using a public server? The web interface uses the HTTP protocol and occupies port 80. If you are using hardware versions V1, V2, or V3 with web-rtc transmission, the port is 8188. If you are using hardware version V4 with MJPEG transmission, the port is 8008. Please note that the ports cannot be modified; only port forwarding can be configured.","title":"Web Problems"},{"location":"faq/#raspberry-problems","text":"Can I use both the CM4 version with EMMC and the SD card at the same time? No, you can't, When designing the CM4 hardware, several pins of the SD card are only valid in the lite version. You can find instructions on the official website of Raspberry Pi.","title":"Raspberry Problems"},{"location":"first_steps/","text":"First steps First power on Power up the device. Do not turn off the device until it's fully booted for the first time After turning on the power, BLIKVM OS will perform the necessary operations on the memory card. Getting access to BLIKVM By default, BliKVM receives a dynamic IP address via DHCP. The IP address will be displayed on the BliKVM monitor. If you are using DIY hardware without a monitor, use the following tips: Finding BliKVM in the network You can determine the IP address of BliKVM using the following methods: Common Method: Access the web interface of your router and look for the allocated IP address list. The specific method depends on the router model. Linux Only: Use the command arp-scan --localnet . Linux, macOS, Windows: Download and run Angry IP Scanner . Windows PowerShell: Use the command arp -a . In the example below, let's assume your BliKVM has obtained the address 192.168.0.100 , and you have successfully found that address using the instructions above. Accessing BliKVM Web Interface In most networks, you can access BliKVM in any browser using the following URL: http://192.168.0.100/ . Google Chrome (Chromium), Firefox, and Safari work best with no extensions enabled. If one works and the other does not, it may be an issue with the browser or extensions. It is recommended to use a private browsing window or incognito mode. Internet Explorer and early versions of Microsoft Edge (non-Chromium version) are not supported. The default username is admin , and the password is also admin . Once logged in, you will have access to the main menu with essential functions. You can change system settings and passwords using the web interface's account management feature. Note: The BliKVM Web interface should be accessed via http, not https Accessing BliKVM via SSH SSH is the most common method for remote access in the Linux world. You can access BliKVM via SSH. This method is used for managing the device: Linux, macOS: Open any terminal application and run: ssh blikvm@192.168.0.100 . Windows: Use PuTTY for the operation. The default blikvm user password is blikvm . You can use sudo -i to obtain root privileges. Optional: Updating BliKVM Software This section is not mandatory and should only be performed if you have physical access to the BliKVM for recovery purposes. Refer to the Software Update Guide for instructions. Note on BliKVM OS Terminal Usage Some configuration changes must be made under the root user (i.e., administrator). Obtaining Root Privileges If you are logged in via SSH, use sudo -i to obtain root privileges. BliKVM storage cards in versions v1 , v2 , and v3 are mounted in read-only mode . This protects the file system from being corrupted in the event of a sudden power outage. To edit any files and make changes, you need to remount the file system in read-write mode. You can determine the current mode by checking if ro or rw is displayed in the terminal. Enabling Write Mode To enable write mode, run the command rw . To disable write mode, run the command ro . If you receive a \"Device is busy\" message, execute the reboot command. What's next? Set up internet access using Port Forwarding or Tailscale VPN . Explore BLIKVM features using the table of contents on the left. Join our Discord to connect with the community and developers. Check out the GitHub - BLIKVM is a Open Source project! FAQ and Troubleshooting If you have any questions or run into problems, take a look at the FAQ . Seriously, it's really useful! We've probably already found a solution for it :) For any other help and support, you can contact us via the Discord chat .","title":"First Steps"},{"location":"first_steps/#first-steps","text":"","title":"First steps"},{"location":"first_steps/#first-power-on","text":"Power up the device. Do not turn off the device until it's fully booted for the first time After turning on the power, BLIKVM OS will perform the necessary operations on the memory card.","title":"First power on"},{"location":"first_steps/#getting-access-to-blikvm","text":"By default, BliKVM receives a dynamic IP address via DHCP. The IP address will be displayed on the BliKVM monitor. If you are using DIY hardware without a monitor, use the following tips: Finding BliKVM in the network You can determine the IP address of BliKVM using the following methods: Common Method: Access the web interface of your router and look for the allocated IP address list. The specific method depends on the router model. Linux Only: Use the command arp-scan --localnet . Linux, macOS, Windows: Download and run Angry IP Scanner . Windows PowerShell: Use the command arp -a . In the example below, let's assume your BliKVM has obtained the address 192.168.0.100 , and you have successfully found that address using the instructions above. Accessing BliKVM Web Interface In most networks, you can access BliKVM in any browser using the following URL: http://192.168.0.100/ . Google Chrome (Chromium), Firefox, and Safari work best with no extensions enabled. If one works and the other does not, it may be an issue with the browser or extensions. It is recommended to use a private browsing window or incognito mode. Internet Explorer and early versions of Microsoft Edge (non-Chromium version) are not supported. The default username is admin , and the password is also admin . Once logged in, you will have access to the main menu with essential functions. You can change system settings and passwords using the web interface's account management feature. Note: The BliKVM Web interface should be accessed via http, not https Accessing BliKVM via SSH SSH is the most common method for remote access in the Linux world. You can access BliKVM via SSH. This method is used for managing the device: Linux, macOS: Open any terminal application and run: ssh blikvm@192.168.0.100 . Windows: Use PuTTY for the operation. The default blikvm user password is blikvm . You can use sudo -i to obtain root privileges. Optional: Updating BliKVM Software This section is not mandatory and should only be performed if you have physical access to the BliKVM for recovery purposes. Refer to the Software Update Guide for instructions.","title":"Getting access to BLIKVM"},{"location":"first_steps/#note-on-blikvm-os-terminal-usage","text":"Some configuration changes must be made under the root user (i.e., administrator). Obtaining Root Privileges If you are logged in via SSH, use sudo -i to obtain root privileges. BliKVM storage cards in versions v1 , v2 , and v3 are mounted in read-only mode . This protects the file system from being corrupted in the event of a sudden power outage. To edit any files and make changes, you need to remount the file system in read-write mode. You can determine the current mode by checking if ro or rw is displayed in the terminal. Enabling Write Mode To enable write mode, run the command rw . To disable write mode, run the command ro . If you receive a \"Device is busy\" message, execute the reboot command.","title":"Note on BliKVM OS Terminal Usage"},{"location":"first_steps/#whats-next","text":"Set up internet access using Port Forwarding or Tailscale VPN . Explore BLIKVM features using the table of contents on the left. Join our Discord to connect with the community and developers. Check out the GitHub - BLIKVM is a Open Source project!","title":"What's next?"},{"location":"first_steps/#faq-and-troubleshooting","text":"If you have any questions or run into problems, take a look at the FAQ . Seriously, it's really useful! We've probably already found a solution for it :) For any other help and support, you can contact us via the Discord chat .","title":"FAQ and Troubleshooting"},{"location":"flashing_os/","text":"Flasing the OS image Micro-SD Card Requirements Minimum 16 Gb Class 10 is strongly recommended Why are there two versions of software, BLIKVM and PiKVM? What is the difference between the two versions? Which one should I choose? Can I use the official image of PiKVM? At the beginning of the BLIKVM project, the hardware was developed, and the software directly used PiKVM. With the continuous progress of the project, BLIKVM has developed its own software version of new architecture, which also lays the foundation for deeper cooperation with its own hardware; The core functions of BLIKVM and PiKVM are the same for users. Some subdivision functions are not the same. For example, BLIKVM supports multiple languages; Select according to your own use experience; You can use the PiKVM official image, but you need to make some adaptations according to the different hardware, mainly involving screens, fans, etc. Since the PiKVM official image is always updated, the specific adaptations need to be seen according to the specific situation you encounter at that time; Download the image Users who need to run PiKVM on v4 by yourself can refer to this doc . BliKVM Versions and Software Image Compatibility The following BliKVM versions use the same BliKVM v1-3 software image: BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 Allwinner, uses a separate Allwinner BliKVM image. BliKVM v4 Web UI The web UI is consistent across all supported versions for easy remote administration. Base on PiKVM software Raspberry 4B and CM4 board use different PiKVM software image. After entering the link, you can see the image named with each hardware version (HAT CM4 PCIe) PiKVM image Flash the image Tip Ignore request to format your sd card, this step is not nessessary. Choose the most suitable method for you. How to flash the eMMC on a Raspberry Pi Compute Module 4 Board Link If you use a CM4 with eMMC (like the CM4102016). You can use the v1 or v2 board to flash the eMMC. If your CM4 doesn't have eMMC, your device can just use a SD card to boot from. You don't need to look into this any further. Just flash to the SD card instead. First, use the jumper cap to short the boot pin (allowing you flash the EMMC memory). If you use BLIKVM CM4 version Then connect the data cable to the USB OTG interface. Power on blikvm and observe the act light, the green light is always on. If you use BLIKVM PCIe version Then connect the data cable to the USB-PC interface. Power on blikvm and observe the ACT and PWR LED isn't light. After initialize EMMC through the usbboot/rpiboot, the ACT and PWR LED light is always on. EMMC knowledge If you use Raspberry Pi compute modules such as CM3 eMMC or CM4 eMMC version\uff0cyou can initialize eMMC through the usbboot project. Note that the eMMC board version cannot use the SD card to boot the image. Instead, you need to flash the eMMC storage by using the usbboot project that emulates USB Mass Storage Device (MSD). From this video you can learn how-to flash the image quickly. How to flash the eMMC on a Raspberry Pi Compute Module 4 video Taking Ubuntu system as an example: Linux usbboot If you use an Micro-SD Card, you can skip the following steps and go to the next chapter down below. sudo apt install git libusb-1.0-0-dev pkg-config build-essential git clone --depth = 1 https://github.com/raspberrypi/usbboot cd usbboot make sudo ./rpiboot If the content in the image below appears, that indicates that the eMMC initialization was successful. The next step is to flash the image to your eMMC chip. Flash the Image (Linux, MacOS and Windows) Please do not make any additional settings to the image in RPi Imager, as this will most likely cause the image to fail to boot or repeatedly restart. We are using the \"RPi Imager\" application to flash the image in this example. Download and install the latest version of RPi Imager . Run RPi Imager: Press CHOOSE OS and select Use custom image at bottom of the list: After clicking on this item, select the image file ( .img.xz ), then click CHOOSE STORAGE : Insert the memory card into the card reader. Choose the card reader from this list (or eMMC flash storage, in case you are using a Raspberry Pi Compute module with a eMMC chip). Be careful and choose the right device: After choosing the memory card, press the WRITE button. Confirm the operation when you are asked about it: Wait for the process to finish. Get yourself a coffee or do some stretching :) Tip The process may hang at 99% for a long time, this is okay, just wait for it to complete 8.Remove the memory card after successful completion: Tip If an error occurs during flashing or booting PiKVM, repeat the process.","title":"Flashing OS"},{"location":"flashing_os/#flasing-the-os-image","text":"Micro-SD Card Requirements Minimum 16 Gb Class 10 is strongly recommended Why are there two versions of software, BLIKVM and PiKVM? What is the difference between the two versions? Which one should I choose? Can I use the official image of PiKVM? At the beginning of the BLIKVM project, the hardware was developed, and the software directly used PiKVM. With the continuous progress of the project, BLIKVM has developed its own software version of new architecture, which also lays the foundation for deeper cooperation with its own hardware; The core functions of BLIKVM and PiKVM are the same for users. Some subdivision functions are not the same. For example, BLIKVM supports multiple languages; Select according to your own use experience; You can use the PiKVM official image, but you need to make some adaptations according to the different hardware, mainly involving screens, fans, etc. Since the PiKVM official image is always updated, the specific adaptations need to be seen according to the specific situation you encounter at that time;","title":"Flasing the OS image"},{"location":"flashing_os/#download-the-image","text":"Users who need to run PiKVM on v4 by yourself can refer to this doc .","title":"Download the image"},{"location":"flashing_os/#blikvm-versions-and-software-image-compatibility","text":"The following BliKVM versions use the same BliKVM v1-3 software image: BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 Allwinner, uses a separate Allwinner BliKVM image. BliKVM v4 Web UI The web UI is consistent across all supported versions for easy remote administration.","title":"BliKVM Versions and Software Image Compatibility"},{"location":"flashing_os/#base-on-pikvm-software","text":"Raspberry 4B and CM4 board use different PiKVM software image. After entering the link, you can see the image named with each hardware version (HAT CM4 PCIe) PiKVM image","title":"Base on PiKVM software"},{"location":"flashing_os/#flash-the-image","text":"Tip Ignore request to format your sd card, this step is not nessessary. Choose the most suitable method for you. How to flash the eMMC on a Raspberry Pi Compute Module 4","title":"Flash the image"},{"location":"flashing_os/#board-link","text":"If you use a CM4 with eMMC (like the CM4102016). You can use the v1 or v2 board to flash the eMMC. If your CM4 doesn't have eMMC, your device can just use a SD card to boot from. You don't need to look into this any further. Just flash to the SD card instead. First, use the jumper cap to short the boot pin (allowing you flash the EMMC memory). If you use BLIKVM CM4 version Then connect the data cable to the USB OTG interface. Power on blikvm and observe the act light, the green light is always on. If you use BLIKVM PCIe version Then connect the data cable to the USB-PC interface. Power on blikvm and observe the ACT and PWR LED isn't light. After initialize EMMC through the usbboot/rpiboot, the ACT and PWR LED light is always on. EMMC knowledge If you use Raspberry Pi compute modules such as CM3 eMMC or CM4 eMMC version\uff0cyou can initialize eMMC through the usbboot project. Note that the eMMC board version cannot use the SD card to boot the image. Instead, you need to flash the eMMC storage by using the usbboot project that emulates USB Mass Storage Device (MSD). From this video you can learn how-to flash the image quickly. How to flash the eMMC on a Raspberry Pi Compute Module 4 video Taking Ubuntu system as an example:","title":"Board Link"},{"location":"flashing_os/#linux-usbboot","text":"If you use an Micro-SD Card, you can skip the following steps and go to the next chapter down below. sudo apt install git libusb-1.0-0-dev pkg-config build-essential git clone --depth = 1 https://github.com/raspberrypi/usbboot cd usbboot make sudo ./rpiboot If the content in the image below appears, that indicates that the eMMC initialization was successful. The next step is to flash the image to your eMMC chip.","title":"Linux usbboot"},{"location":"flashing_os/#flash-the-image-linux-macos-and-windows","text":"Please do not make any additional settings to the image in RPi Imager, as this will most likely cause the image to fail to boot or repeatedly restart. We are using the \"RPi Imager\" application to flash the image in this example. Download and install the latest version of RPi Imager . Run RPi Imager: Press CHOOSE OS and select Use custom image at bottom of the list: After clicking on this item, select the image file ( .img.xz ), then click CHOOSE STORAGE : Insert the memory card into the card reader. Choose the card reader from this list (or eMMC flash storage, in case you are using a Raspberry Pi Compute module with a eMMC chip). Be careful and choose the right device: After choosing the memory card, press the WRITE button. Confirm the operation when you are asked about it: Wait for the process to finish. Get yourself a coffee or do some stretching :) Tip The process may hang at 99% for a long time, this is okay, just wait for it to complete 8.Remove the memory card after successful completion: Tip If an error occurs during flashing or booting PiKVM, repeat the process.","title":"Flash the Image (Linux, MacOS and Windows)"},{"location":"hdmi-csi-i2s/","text":"HDMI to CSI&I2S bridge guide Convert HDMI signal acquisition into CSI signal and I2S audio signal. Currently, all platforms are supported (Zero, Pi3B, Pi4B, CM4, Pi5B), and the maximum capture resolution not only depends on the HDMI to CSI converter board you are using but also on the Raspberry Pi hardware version you have. Raspberry Pi hardware versions are primarily divided into two series, one supporting a maximum of 1080P60Hz and the other supporting a maximum of 1080P50Hz. The Raspberry Pi versions that support a maximum of 1080P60Hz are CM3, CM4, and Pi5B. The Raspberry Pi versions that support a maximum of 1080P50Hz are Zero, Zero 2, Pi3B, Pi4B, and so on. Introduction This module takes the incoming HDMI signal and converts it into a separate CSI signal and I2S audio signal. HDMI input supports up to 1080P60Hz. It works well on Raspberry Pi, there are three versions of this module in history (C779, C780, C790). C790 is the latest version. C790 has mitigated HDMI backpowering, and also has two csi channels and four csi channels at the same time. Features C790 Hardware Parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 4 CSI-2 channels & clock The CSI-2 interface, with 15 pin FPC seat, spacing 1.0 mm, is located on the front of the C790 module. The CSI-2 interface, with 22 pin FPC seat, spacing 0.5 mm, is located on the back of the C790 module. Size: 30 x 45 mm Install: 4 x M2.5 Power supply: 3.3V Weight: 10g Pi 4B only support 1080P50Hz, limited by the number of CSI-2 channels. CM4 support 1080P60HZ, So if you must use 1080P60Hz input, please use CM4 and C790 together. Interface C790 has two CSI output interfaces. In front of C790, the CSI-2 interface is 15 pin FPC seat, spacing 1.0 mm. In back of C790, the CSI-2 interface is 22 pin FPC seat, spacing 0.5 mm. Size Install C790 on Raspberry Pi for reference C780 C780A Hardware Parameters HDMI input: supports up to 1080P50Hz on Raspberry Pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install: 6 x M2.5 Power supply: 3.3V Weight: 10g C780B Hardware Parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 4 CSI-2 channels & clock CSI-2 interface: 22 pin FPC seat, spacing 0.5 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install: 6 x M2.5 Power supply: 3.3V Weight: 10g Interface The wiring of audio part is shown in Figure. Size The size of C780 is shown in the image below. There are 6 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. As shown in the image below, the user can directly fix the module on the Raspberry Pi Zero. C780 is designed to be broken, and the hole spacing before breaking can be perfectly installed with most series of Raspberry Pi. C779 Hardware Parameters HDMI input: supports up to 1080P50Hz on Raspberry Pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 35 x 50 mm Install: 4 x M2.5 Power supply: 3.3V Weight: 10g Size The size of C779 is shown in Figure. There are 4 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. CSI Interface Definitions The CSI (Camera Serial Interface) interfaces C779 and C780A have 15 pins each, while the C780B interface has 22 pins. The C790 interface is unique as it supports both 15 and 22 PIN configurations. Software Demo The use guide of C790/C780/C779 depends on the official Raspberry Pi OS version you are using. Different versions have different usage methods. If you have some questions, Join our BLIKVM Discord Community for Support, FAQ & News! To use the kernel drivers, please update your system. There are a few things that have changed with the 5.4 kernel, so these instructions are for 5.4 or later. If uname -a reports anything less, then fix this before proceeding. pi@raspberrypi:~ $ uname -a Linux raspberrypi 5 .10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. Update & upgrade the Raspberry Pi system (It will take a long time depend on the different country) sudo apt-get update sudo apt-get upgrade 2. Enable camera module (the camera is enabled by default in Raspberry pi Bullseys OS) sudo raspi-config sudo reboot Navigate to \u2018Interfacing Options\u2019 and hit Enter. Now select the \u2018Camera\u2019 option, and hit the Enter key to enable it. Select \u201cFinish\u201d and select to reboot your Raspberry Pi. reboot is important!! Due to the absence of hardware encoding on the Pi5B, the software usage instructions for Pi platforms are currently divided into two sections: Pi5B configuration and configuration for other Pi platforms. In platforms such as Zero, Zero 2, Pi3B, Pi4B, etc., there is a reference for testing HDMI to CSI module demo. Edit /boot/config.txt (that will need sudo) sudo nano /boot/config.txt Add the line: dtoverlay=tc358743 Add the line if your shield support audio like C780 or C790. dtoverlay=tc358743-audio If (and only if) you have a device such as the C780 or C790 that supports the 22pin connector with all 4 lanes wired out, and are using a Compute Module with the CAM1 connector that also has all 4 lanes wired up, you can use: dtoverlay=tc358743,4lane=1 Check the amount of memory assigned to the CMA heap with \u201cdmesg | grep cma\u201d. The first line should be along the lines of: pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 If it reports less than 96MB assigned to CMA, then edit /boot/cmdline.txt and add to the start of the line. Do NOT add any carriage returns. cma=96M Reboot. If all is well you should get a /dev/video0 device, and \u201cv4l2-ctl \u2013list-devices\u201d will tell you that it is provided by Unicam. After connecting all the cables, power on the Raspberry Pi, the C790 indicator light is normally green, and after opening the Raspberry Pi terminal, enter the following command: pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 This driver puts all the control in the hands of the user, or the user\u2019s application. By default there is no EDID loaded into the chip to allow it to tell the HDMI source what resolutions are supported. There are EDID editors around. If you create a file edid.txt, then you can push this to the device using the comment of edid.txt file: 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt #copy the above commend in edid.txt, save&exit; pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan The driver does NOT automatically switch to the resolution detected. Use the command: pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: You MUST set the timings via \u201cv4l2-ctl \u2013set-dv-bt-timings\u201d. You can pass in an index to the detected mode, or use: v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. The chip supports two formats \u2013 BGR3 (the default) and UYVY. BGR3 is 24bpp, and UYVY is YUV4:2:2 16bpp. Over the normal 2 CSI-2 lanes the data rate is such that BGR3 can run at a maximum of 1080p30, whilst UYVY will go up to 1080p50. Use the following command to select UYVY, however your application may override that. v4l2-ctl -v pixelformat=UYVY Check that the audio drivers / card is available to ALSA. pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1 means that the card number for the TC358743XBG is \u201c1\u201d and it might be different. Install GStreamer tool. sudo apt install gstreamer1.0-tools Check gstreamer tool version: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note: Different versions have different command line parameters, which is very annoying. Use gstreamer to record video and audio #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. foo.mkv is the output file. If your gstreamer is version 1.8 or above, you can try the following test command. In addition, alsasrc device=hw:1 represents the sound card of TC358743, you can use \u201carecord -l\u201d to query. #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: We recommend that you modify the above framerate parameter to the actual frame rate of your HDMI signal, the actual frame rate value is from the result of \u2018v4l2-ctl \u2013query-dv-timings\u2019 command. For the above HDMI device, because the frame rate is 60, so we modify the framerate parameter to 60 like the followint command. Record the video only: gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Record the video and audio: (if your shield supports audio also) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9) Pi5B platforms HDMI to CSI module test demo reference. In the following test, the CAM1 channel is used, and the input resolution is 1080P24Hz. During the Raspberry Pi 5B test, it was found that the EDID settings were invalid, so an HDMI emulator needs to be added to force the target to output HDMI. Otherwise, the Raspberry Pi 5B may not receive any input. Due to the lack of corresponding hardware encoding on the Raspberry Pi 5B, the image capture performance of the Raspberry Pi 5B + C790 is generally inferior to that of the Raspberry Pi 4B. Edit /boot/config.txt (sudo permission required). sudo nano /boot/config.txt Add the following content: dtoverlay=tc358743 If your modules (C780 and C790) support audio, add the following content to enable audio support. dtoverlay=tc358743-audio Reboot the Raspberry Pi and execute the following command to find the media node corresponding to the CSI as media0, under the rp1-cfe (platform: 1f00128000.csi) field: blikvm@blikvm:~ $ v4l2-ctl --list-devices pispbe (platform:1000880000.pisp_be): /dev/video20 /dev/video21 /dev/video22 /dev/video23 /dev/video24 /dev/video25 /dev/video26 /dev/video27 /dev/video28 /dev/video29 /dev/video30 /dev/video31 /dev/video32 /dev/video33 /dev/video34 /dev/video35 /dev/video36 /dev/video37 /dev/media1 /dev/media2 rp1-cfe (platform:1f00128000.csi): /dev/video0 /dev/video1 /dev/video2 /dev/video3 /dev/video4 /dev/video5 /dev/video6 /dev/video7 /dev/media0 rpivid (platform:rpivid): /dev/video19 /dev/media3 Locate the node corresponding to tc358743 as v4l-subdev2, and the pad0 of rp1-cfe-csi2_ch0 as video0: blikvm@blikvm:~ $ media-ctl -d /dev/media0 -p Media controller API version 6.1.63 Media device information ------------------------ driver rp1-cfe model rp1-cfe serial bus info platform:1f00128000.csi hw revision 0x114666 driver version 6.1.63 Device topology - entity 1: csi2 (8 pads, 8 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"tc358743 4-000f\":0 [ENABLED,IMMUTABLE] pad1: Sink [fmt:unknown/8192x1 field:none] pad2: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad3: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad4: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch0\":0 [] -> \"pisp-fe\":0 [] pad5: Source [fmt:unknown/8192x1 field:none] -> \"rp1-cfe-embedded\":0 [] pad6: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch2\":0 [] -> \"pisp-fe\":0 [] pad7: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch3\":0 [] -> \"pisp-fe\":0 [] - entity 10: pisp-fe (5 pads, 7 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: Sink [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"csi2\":4 [] <- \"csi2\":6 [] <- \"csi2\":7 [] pad1: Sink [fmt:FIXED/8192x1 field:none] <- \"rp1-cfe-fe_config\":0 [] pad2: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image0\":0 [] pad3: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image1\":0 [] pad4: Source [fmt:FIXED/8192x1 field:none] -> \"rp1-cfe-fe_stats\":0 [] - entity 16: tc358743 4-000f (1 pad, 1 link) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev2 pad0: Source [fmt:RGB888_1X24/640x480 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:640x350@13000000 max:1920x1200@165000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom] [dv.detect:BT.656/1120 1920x1080p24 (2750x1125) stds: flags:] [dv.current:BT.656/1120 640x480p59 (800x525) stds:CEA-861,DMT flags:has-cea861-vic] -> \"csi2\":0 [ENABLED,IMMUTABLE] - entity 18: rp1-cfe-csi2_ch0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 pad0: Sink <- \"csi2\":4 [] - entity 22: rp1-cfe-embedded (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- \"csi2\":5 [] - entity 26: rp1-cfe-csi2_ch2 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: Sink <- \"csi2\":6 [] - entity 30: rp1-cfe-csi2_ch3 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video3 pad0: Sink <- \"csi2\":7 [] - entity 34: rp1-cfe-fe_image0 (1 pad, 1 link) type Node subtype V4L flags 1 device node name /dev/video4 pad0: Sink <- \"pisp-fe\":2 [] - entity 38: rp1-cfe-fe_image1 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video5 pad0: Sink <- \"pisp-fe\":3 [] - entity 42: rp1-cfe-fe_stats (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video6 pad0: Sink <- \"pisp-fe\":4 [] - entity 46: rp1-cfe-fe_config (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video7 pad0: Source -> \"pisp-fe\":1 [] To query the current input source information, if the resolution displays as 0, it indicates that no input source signal has been detected. In this case, you should check the hardware connections and follow the steps mentioned above to troubleshoot. blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --query-dv-timings Active width: 1920 Active height: 1080 Total width: 2750 Total height: 1125 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (24.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 830 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 45 Vertical backporch: 0 Standards: Flags: Confirm the current input source information. blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --set-dv-bt-timings query BT timings set Initialize media0. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -r Connect CSI2's pad4 to rp1-cfe-csi2_ch0's pad0. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -l ''\\''csi2'\\'':4 -> '\\''rp1-cfe-csi2_ch0'\\'':0 [1]' Configure the media node. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':0 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':4 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' Set the output format. v4l2-ctl -v width=1920,height=1080,pixelformat=RGB3 Capture two frames for testing to verify if tc358743 is functioning properly. Other methods, such as using GStreamer, are not currently available. v4l2-ctl --verbose -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat='RGB3' --stream-mmap=4 --stream-skip=3 --stream-count=2 --stream-to=hdmiin.yuv --stream-poll If you have installed a desktop version of Raspberry Pi, you can use ffplay to directly play YUV files. ffplay -f rawvideo -video_size 1920x1080 -pixel_format bgr24 hdmiin.yuv On a Windows computer, you can use software like 7yuv to view .yuv files. For the tutorial with an input format of 1920 1080, you should select BGR888 in the top right corner of 7yuv and set the resolution to 1920 1080 to view the two frames you just captured. Chip Docs TC358743 Documentation Packing List C790 Test Video C780A Test C780B Test Purchase Link Purchase C780 & C790 Purchase C779","title":"HDMI to CSI & Audio"},{"location":"hdmi-csi-i2s/#hdmi-to-csii2s-bridge-guide","text":"Convert HDMI signal acquisition into CSI signal and I2S audio signal. Currently, all platforms are supported (Zero, Pi3B, Pi4B, CM4, Pi5B), and the maximum capture resolution not only depends on the HDMI to CSI converter board you are using but also on the Raspberry Pi hardware version you have. Raspberry Pi hardware versions are primarily divided into two series, one supporting a maximum of 1080P60Hz and the other supporting a maximum of 1080P50Hz. The Raspberry Pi versions that support a maximum of 1080P60Hz are CM3, CM4, and Pi5B. The Raspberry Pi versions that support a maximum of 1080P50Hz are Zero, Zero 2, Pi3B, Pi4B, and so on.","title":"HDMI to CSI&I2S bridge guide"},{"location":"hdmi-csi-i2s/#introduction","text":"This module takes the incoming HDMI signal and converts it into a separate CSI signal and I2S audio signal. HDMI input supports up to 1080P60Hz. It works well on Raspberry Pi, there are three versions of this module in history (C779, C780, C790). C790 is the latest version. C790 has mitigated HDMI backpowering, and also has two csi channels and four csi channels at the same time.","title":"Introduction"},{"location":"hdmi-csi-i2s/#features","text":"","title":"Features"},{"location":"hdmi-csi-i2s/#c790","text":"Hardware Parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 4 CSI-2 channels & clock The CSI-2 interface, with 15 pin FPC seat, spacing 1.0 mm, is located on the front of the C790 module. The CSI-2 interface, with 22 pin FPC seat, spacing 0.5 mm, is located on the back of the C790 module. Size: 30 x 45 mm Install: 4 x M2.5 Power supply: 3.3V Weight: 10g Pi 4B only support 1080P50Hz, limited by the number of CSI-2 channels. CM4 support 1080P60HZ, So if you must use 1080P60Hz input, please use CM4 and C790 together. Interface C790 has two CSI output interfaces. In front of C790, the CSI-2 interface is 15 pin FPC seat, spacing 1.0 mm. In back of C790, the CSI-2 interface is 22 pin FPC seat, spacing 0.5 mm. Size Install C790 on Raspberry Pi for reference","title":"C790"},{"location":"hdmi-csi-i2s/#c780","text":"C780A Hardware Parameters HDMI input: supports up to 1080P50Hz on Raspberry Pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install: 6 x M2.5 Power supply: 3.3V Weight: 10g C780B Hardware Parameters HDMI input: supports up to 1080P60Hz on Raspberry Pi HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 4 CSI-2 channels & clock CSI-2 interface: 22 pin FPC seat, spacing 0.5 mm Size: 30 x 65 mm (unbroken PCB size); 30 x 45 mm (PCB size after breaking) Install: 6 x M2.5 Power supply: 3.3V Weight: 10g Interface The wiring of audio part is shown in Figure. Size The size of C780 is shown in the image below. There are 6 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws. As shown in the image below, the user can directly fix the module on the Raspberry Pi Zero. C780 is designed to be broken, and the hole spacing before breaking can be perfectly installed with most series of Raspberry Pi.","title":"C780"},{"location":"hdmi-csi-i2s/#c779","text":"Hardware Parameters HDMI input: supports up to 1080P50Hz on Raspberry Pi(Limited by the number of CSI-2 channels) HDMI to CSI-2 bridge chip: Toshiba TC358743XBG 2 CSI-2 channels & clock CSI-2 interface: 15 pin FPC seat, spacing 1.0 mm Size: 35 x 50 mm Install: 4 x M2.5 Power supply: 3.3V Weight: 10g Size The size of C779 is shown in Figure. There are 4 mounting holes with a diameter of 2.75mm, which are suitable for M2.5 screws.","title":"C779"},{"location":"hdmi-csi-i2s/#csi-interface-definitions","text":"The CSI (Camera Serial Interface) interfaces C779 and C780A have 15 pins each, while the C780B interface has 22 pins. The C790 interface is unique as it supports both 15 and 22 PIN configurations.","title":"CSI Interface Definitions"},{"location":"hdmi-csi-i2s/#software-demo","text":"The use guide of C790/C780/C779 depends on the official Raspberry Pi OS version you are using. Different versions have different usage methods. If you have some questions, Join our BLIKVM Discord Community for Support, FAQ & News! To use the kernel drivers, please update your system. There are a few things that have changed with the 5.4 kernel, so these instructions are for 5.4 or later. If uname -a reports anything less, then fix this before proceeding. pi@raspberrypi:~ $ uname -a Linux raspberrypi 5 .10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. Update & upgrade the Raspberry Pi system (It will take a long time depend on the different country) sudo apt-get update sudo apt-get upgrade 2. Enable camera module (the camera is enabled by default in Raspberry pi Bullseys OS) sudo raspi-config sudo reboot Navigate to \u2018Interfacing Options\u2019 and hit Enter. Now select the \u2018Camera\u2019 option, and hit the Enter key to enable it. Select \u201cFinish\u201d and select to reboot your Raspberry Pi. reboot is important!! Due to the absence of hardware encoding on the Pi5B, the software usage instructions for Pi platforms are currently divided into two sections: Pi5B configuration and configuration for other Pi platforms. In platforms such as Zero, Zero 2, Pi3B, Pi4B, etc., there is a reference for testing HDMI to CSI module demo. Edit /boot/config.txt (that will need sudo) sudo nano /boot/config.txt Add the line: dtoverlay=tc358743 Add the line if your shield support audio like C780 or C790. dtoverlay=tc358743-audio If (and only if) you have a device such as the C780 or C790 that supports the 22pin connector with all 4 lanes wired out, and are using a Compute Module with the CAM1 connector that also has all 4 lanes wired up, you can use: dtoverlay=tc358743,4lane=1 Check the amount of memory assigned to the CMA heap with \u201cdmesg | grep cma\u201d. The first line should be along the lines of: pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 If it reports less than 96MB assigned to CMA, then edit /boot/cmdline.txt and add to the start of the line. Do NOT add any carriage returns. cma=96M Reboot. If all is well you should get a /dev/video0 device, and \u201cv4l2-ctl \u2013list-devices\u201d will tell you that it is provided by Unicam. After connecting all the cables, power on the Raspberry Pi, the C790 indicator light is normally green, and after opening the Raspberry Pi terminal, enter the following command: pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 This driver puts all the control in the hands of the user, or the user\u2019s application. By default there is no EDID loaded into the chip to allow it to tell the HDMI source what resolutions are supported. There are EDID editors around. If you create a file edid.txt, then you can push this to the device using the comment of edid.txt file: 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt #copy the above commend in edid.txt, save&exit; pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan The driver does NOT automatically switch to the resolution detected. Use the command: pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: You MUST set the timings via \u201cv4l2-ctl \u2013set-dv-bt-timings\u201d. You can pass in an index to the detected mode, or use: v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. The chip supports two formats \u2013 BGR3 (the default) and UYVY. BGR3 is 24bpp, and UYVY is YUV4:2:2 16bpp. Over the normal 2 CSI-2 lanes the data rate is such that BGR3 can run at a maximum of 1080p30, whilst UYVY will go up to 1080p50. Use the following command to select UYVY, however your application may override that. v4l2-ctl -v pixelformat=UYVY Check that the audio drivers / card is available to ALSA. pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1 means that the card number for the TC358743XBG is \u201c1\u201d and it might be different. Install GStreamer tool. sudo apt install gstreamer1.0-tools Check gstreamer tool version: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note: Different versions have different command line parameters, which is very annoying. Use gstreamer to record video and audio #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. foo.mkv is the output file. If your gstreamer is version 1.8 or above, you can try the following test command. In addition, alsasrc device=hw:1 represents the sound card of TC358743, you can use \u201carecord -l\u201d to query. #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: We recommend that you modify the above framerate parameter to the actual frame rate of your HDMI signal, the actual frame rate value is from the result of \u2018v4l2-ctl \u2013query-dv-timings\u2019 command. For the above HDMI device, because the frame rate is 60, so we modify the framerate parameter to 60 like the followint command. Record the video only: gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Record the video and audio: (if your shield supports audio also) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9) Pi5B platforms HDMI to CSI module test demo reference. In the following test, the CAM1 channel is used, and the input resolution is 1080P24Hz. During the Raspberry Pi 5B test, it was found that the EDID settings were invalid, so an HDMI emulator needs to be added to force the target to output HDMI. Otherwise, the Raspberry Pi 5B may not receive any input. Due to the lack of corresponding hardware encoding on the Raspberry Pi 5B, the image capture performance of the Raspberry Pi 5B + C790 is generally inferior to that of the Raspberry Pi 4B. Edit /boot/config.txt (sudo permission required). sudo nano /boot/config.txt Add the following content: dtoverlay=tc358743 If your modules (C780 and C790) support audio, add the following content to enable audio support. dtoverlay=tc358743-audio Reboot the Raspberry Pi and execute the following command to find the media node corresponding to the CSI as media0, under the rp1-cfe (platform: 1f00128000.csi) field: blikvm@blikvm:~ $ v4l2-ctl --list-devices pispbe (platform:1000880000.pisp_be): /dev/video20 /dev/video21 /dev/video22 /dev/video23 /dev/video24 /dev/video25 /dev/video26 /dev/video27 /dev/video28 /dev/video29 /dev/video30 /dev/video31 /dev/video32 /dev/video33 /dev/video34 /dev/video35 /dev/video36 /dev/video37 /dev/media1 /dev/media2 rp1-cfe (platform:1f00128000.csi): /dev/video0 /dev/video1 /dev/video2 /dev/video3 /dev/video4 /dev/video5 /dev/video6 /dev/video7 /dev/media0 rpivid (platform:rpivid): /dev/video19 /dev/media3 Locate the node corresponding to tc358743 as v4l-subdev2, and the pad0 of rp1-cfe-csi2_ch0 as video0: blikvm@blikvm:~ $ media-ctl -d /dev/media0 -p Media controller API version 6.1.63 Media device information ------------------------ driver rp1-cfe model rp1-cfe serial bus info platform:1f00128000.csi hw revision 0x114666 driver version 6.1.63 Device topology - entity 1: csi2 (8 pads, 8 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"tc358743 4-000f\":0 [ENABLED,IMMUTABLE] pad1: Sink [fmt:unknown/8192x1 field:none] pad2: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad3: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad4: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch0\":0 [] -> \"pisp-fe\":0 [] pad5: Source [fmt:unknown/8192x1 field:none] -> \"rp1-cfe-embedded\":0 [] pad6: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch2\":0 [] -> \"pisp-fe\":0 [] pad7: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch3\":0 [] -> \"pisp-fe\":0 [] - entity 10: pisp-fe (5 pads, 7 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: Sink [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"csi2\":4 [] <- \"csi2\":6 [] <- \"csi2\":7 [] pad1: Sink [fmt:FIXED/8192x1 field:none] <- \"rp1-cfe-fe_config\":0 [] pad2: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image0\":0 [] pad3: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image1\":0 [] pad4: Source [fmt:FIXED/8192x1 field:none] -> \"rp1-cfe-fe_stats\":0 [] - entity 16: tc358743 4-000f (1 pad, 1 link) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev2 pad0: Source [fmt:RGB888_1X24/640x480 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:640x350@13000000 max:1920x1200@165000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom] [dv.detect:BT.656/1120 1920x1080p24 (2750x1125) stds: flags:] [dv.current:BT.656/1120 640x480p59 (800x525) stds:CEA-861,DMT flags:has-cea861-vic] -> \"csi2\":0 [ENABLED,IMMUTABLE] - entity 18: rp1-cfe-csi2_ch0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 pad0: Sink <- \"csi2\":4 [] - entity 22: rp1-cfe-embedded (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- \"csi2\":5 [] - entity 26: rp1-cfe-csi2_ch2 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: Sink <- \"csi2\":6 [] - entity 30: rp1-cfe-csi2_ch3 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video3 pad0: Sink <- \"csi2\":7 [] - entity 34: rp1-cfe-fe_image0 (1 pad, 1 link) type Node subtype V4L flags 1 device node name /dev/video4 pad0: Sink <- \"pisp-fe\":2 [] - entity 38: rp1-cfe-fe_image1 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video5 pad0: Sink <- \"pisp-fe\":3 [] - entity 42: rp1-cfe-fe_stats (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video6 pad0: Sink <- \"pisp-fe\":4 [] - entity 46: rp1-cfe-fe_config (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video7 pad0: Source -> \"pisp-fe\":1 [] To query the current input source information, if the resolution displays as 0, it indicates that no input source signal has been detected. In this case, you should check the hardware connections and follow the steps mentioned above to troubleshoot. blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --query-dv-timings Active width: 1920 Active height: 1080 Total width: 2750 Total height: 1125 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (24.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 830 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 45 Vertical backporch: 0 Standards: Flags: Confirm the current input source information. blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --set-dv-bt-timings query BT timings set Initialize media0. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -r Connect CSI2's pad4 to rp1-cfe-csi2_ch0's pad0. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -l ''\\''csi2'\\'':4 -> '\\''rp1-cfe-csi2_ch0'\\'':0 [1]' Configure the media node. blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':0 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':4 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' Set the output format. v4l2-ctl -v width=1920,height=1080,pixelformat=RGB3 Capture two frames for testing to verify if tc358743 is functioning properly. Other methods, such as using GStreamer, are not currently available. v4l2-ctl --verbose -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat='RGB3' --stream-mmap=4 --stream-skip=3 --stream-count=2 --stream-to=hdmiin.yuv --stream-poll If you have installed a desktop version of Raspberry Pi, you can use ffplay to directly play YUV files. ffplay -f rawvideo -video_size 1920x1080 -pixel_format bgr24 hdmiin.yuv On a Windows computer, you can use software like 7yuv to view .yuv files. For the tutorial with an input format of 1920 1080, you should select BGR888 in the top right corner of 7yuv and set the resolution to 1920 1080 to view the two frames you just captured.","title":"Software Demo"},{"location":"hdmi-csi-i2s/#chip-docs","text":"TC358743 Documentation","title":"Chip Docs"},{"location":"hdmi-csi-i2s/#packing-list","text":"C790","title":"Packing List"},{"location":"hdmi-csi-i2s/#test-video","text":"C780A Test C780B Test","title":"Test Video"},{"location":"hdmi-csi-i2s/#purchase-link","text":"Purchase C780 & C790 Purchase C779","title":"Purchase Link"},{"location":"hid/","text":"Video Mouse Keyboard Shortcuts After v1.4.5, custom shortcut keys are supported. Find the shortcuts configuration item, where key is the button name on the web UI and value is the specific button. sudo -s vim /mnt/exec/release/config/app.json ## default config\uff1a \"shortcuts\": { \"Ctrl+Alt+Del\": [\"ControlLeft\",\"AltLeft\",\"Delete\"], \"Alt+Tab\": [\"AltLeft\",\"Tab\"], \"Alt+F4\": [\"AltLeft\",\"F4\"], \"Alt+Enter\": [\"AltLeft\",\"Enter\"], \"Ctrl+W\": [\"ControlLeft\",\"KeyW\"] } The key names have uniqueness, and the specific key names are provided below \"{backspace}\": \"Backspace\", \"{tab}\": \"Tab\", \"{enter}\": \"Enter\", \"{shiftleft}\": \"ShiftLeft\", \"{shiftright}\": \"ShiftRight\", \"{altleft}\": \"AltLeft\", \"{altright}\": \"AltRight\", \"{prtscr}\": \"PrtScr\", \"{pause}\": \"Pause\", \"{scrolllock}\": \"ScrollLock\", \"{controlleft}\": \"ControlLeft\", \"{controlright}\": \"ControlRight\", \"{metaleft}\": \"MetaLeft\", \"{metaright}\": \"MetaRight\", \"{capslock}\": \"CapsLock\", \"{escape}\": \"Escape\", \"{space}\": \"Space\", \"{pageup}\": \"PageUp\", \"{pagedown}\": \"PageDown\", \"{end}\": \"End\", \"{home}\": \"Home\", \"{arrowleft}\": \"ArrowLeft\", \"{arrowup}\": \"ArrowUp\", \"{arrowright}\": \"ArrowRight\", \"{arrowdown}\": \"ArrowDown\", \"{insert}\": \"Insert\", \"{delete}\": \"Delete\", // Digits keys 1: \"Digit1\", 2: \"Digit2\", 3: \"Digit3\", 4: \"Digit4\", 5: \"Digit5\", 6: \"Digit6\", 7: \"Digit7\", 8: \"Digit8\", 9: \"Digit9\", 0: \"Digit0\", // \"!\": \"Digit1\", // ! maps to the '1' key \"@\": \"Digit2\", // @ maps to the '2' key \"#\": \"Digit3\", // # maps to the '3' key $: \"Digit4\", // $ maps to the '4' key \"%\": \"Digit5\", // % maps to the '5' key \"^\": \"Digit6\", // ^ maps to the '6' key \"&\": \"Digit7\", // & maps to the '7' key \"*\": \"Digit8\", // * maps to the '8' key \"(\": \"Digit9\", // ( maps to the '9' key \")\": \"Digit0\", // ) maps to the '0' key a: \"KeyA\", b: \"KeyB\", c: \"KeyC\", d: \"KeyD\", e: \"KeyE\", f: \"KeyF\", g: \"KeyG\", h: \"KeyH\", i: \"KeyI\", j: \"KeyJ\", k: \"KeyK\", l: \"KeyL\", m: \"KeyM\", n: \"KeyN\", o: \"KeyO\", p: \"KeyP\", q: \"KeyQ\", r: \"KeyR\", s: \"KeyS\", t: \"KeyT\", u: \"KeyU\", v: \"KeyV\", w: \"KeyW\", x: \"KeyX\", y: \"KeyY\", z: \"KeyZ\", // A: \"KeyA\", B: \"KeyB\", C: \"KeyC\", D: \"KeyD\", E: \"KeyE\", F: \"KeyF\", G: \"KeyG\", H: \"KeyH\", I: \"KeyI\", J: \"KeyJ\", K: \"KeyK\", L: \"KeyL\", M: \"KeyM\", N: \"KeyN\", O: \"KeyO\", P: \"KeyP\", Q: \"KeyQ\", R: \"KeyR\", S: \"KeyS\", T: \"KeyT\", U: \"KeyU\", V: \"KeyV\", W: \"KeyW\", X: \"KeyX\", Y: \"KeyY\", Z: \"KeyZ\", \"-\": \"Minus\", _: \"Minus\", \"=\": \"Equal\", \"+\": \"Equal\", \"[\": \"BracketLeft\", \"{\": \"BracketLeft\", \"]\": \"BracketRight\", \"}\": \"BracketRight\", \"|\": \"Backslash\", \"\\\\\": \"Backslash\", \"`\": \"Backquote\", \"~\": \"Backquote\", \";\": \"Semicolon\", \":\": \"Semicolon\", \"'\": \"Quote\", '\"': \"Quote\", \",\": \"Comma\", \"<\": \"Comma\", \".\": \"Period\", \">\": \"Period\", \"/\": \"Slash\", \"?\": \"Slash\", // Numpad keys \"{numpad0}\": \"Numpad0\", \"{numpad1}\": \"Numpad1\", \"{numpad2}\": \"Numpad2\", \"{numpad3}\": \"Numpad3\", \"{numpad4}\": \"Numpad4\", \"{numpad5}\": \"Numpad5\", \"{numpad6}\": \"Numpad6\", \"{numpad7}\": \"Numpad7\", \"{numpad8}\": \"Numpad8\", \"{numpad9}\": \"Numpad9\", \"{numlock}\": \"numlock\", \"{numpadmultiply}\": \"NumpadMultiply\", \"{numpadadd}\": \"NumpadAdd\", \"{numpadsubtract}\": \"NumpadSubtract\", \"{numpaddecimal}\": \"NumpadDecimal\", \"{numpaddivide}\": \"NumpadDivide\", \"{numpadenter}\": \"NumpadEnter\", // Function keys \"{f1}\": \"F1\", \"{f2}\": \"F2\", \"{f3}\": \"F3\", \"{f4}\": \"F4\", \"{f5}\": \"F5\", \"{f6}\": \"F6\", \"{f7}\": \"F7\", \"{f8}\": \"F8\", \"{f9}\": \"F9\", \"{f10}\": \"F10\", \"{f11}\": \"F11\", \"{f12}\": \"F12\"","title":"Keyboard"},{"location":"hid/#video-mouse-keyboard","text":"","title":"Video Mouse Keyboard"},{"location":"hid/#shortcuts","text":"After v1.4.5, custom shortcut keys are supported. Find the shortcuts configuration item, where key is the button name on the web UI and value is the specific button. sudo -s vim /mnt/exec/release/config/app.json ## default config\uff1a \"shortcuts\": { \"Ctrl+Alt+Del\": [\"ControlLeft\",\"AltLeft\",\"Delete\"], \"Alt+Tab\": [\"AltLeft\",\"Tab\"], \"Alt+F4\": [\"AltLeft\",\"F4\"], \"Alt+Enter\": [\"AltLeft\",\"Enter\"], \"Ctrl+W\": [\"ControlLeft\",\"KeyW\"] } The key names have uniqueness, and the specific key names are provided below \"{backspace}\": \"Backspace\", \"{tab}\": \"Tab\", \"{enter}\": \"Enter\", \"{shiftleft}\": \"ShiftLeft\", \"{shiftright}\": \"ShiftRight\", \"{altleft}\": \"AltLeft\", \"{altright}\": \"AltRight\", \"{prtscr}\": \"PrtScr\", \"{pause}\": \"Pause\", \"{scrolllock}\": \"ScrollLock\", \"{controlleft}\": \"ControlLeft\", \"{controlright}\": \"ControlRight\", \"{metaleft}\": \"MetaLeft\", \"{metaright}\": \"MetaRight\", \"{capslock}\": \"CapsLock\", \"{escape}\": \"Escape\", \"{space}\": \"Space\", \"{pageup}\": \"PageUp\", \"{pagedown}\": \"PageDown\", \"{end}\": \"End\", \"{home}\": \"Home\", \"{arrowleft}\": \"ArrowLeft\", \"{arrowup}\": \"ArrowUp\", \"{arrowright}\": \"ArrowRight\", \"{arrowdown}\": \"ArrowDown\", \"{insert}\": \"Insert\", \"{delete}\": \"Delete\", // Digits keys 1: \"Digit1\", 2: \"Digit2\", 3: \"Digit3\", 4: \"Digit4\", 5: \"Digit5\", 6: \"Digit6\", 7: \"Digit7\", 8: \"Digit8\", 9: \"Digit9\", 0: \"Digit0\", // \"!\": \"Digit1\", // ! maps to the '1' key \"@\": \"Digit2\", // @ maps to the '2' key \"#\": \"Digit3\", // # maps to the '3' key $: \"Digit4\", // $ maps to the '4' key \"%\": \"Digit5\", // % maps to the '5' key \"^\": \"Digit6\", // ^ maps to the '6' key \"&\": \"Digit7\", // & maps to the '7' key \"*\": \"Digit8\", // * maps to the '8' key \"(\": \"Digit9\", // ( maps to the '9' key \")\": \"Digit0\", // ) maps to the '0' key a: \"KeyA\", b: \"KeyB\", c: \"KeyC\", d: \"KeyD\", e: \"KeyE\", f: \"KeyF\", g: \"KeyG\", h: \"KeyH\", i: \"KeyI\", j: \"KeyJ\", k: \"KeyK\", l: \"KeyL\", m: \"KeyM\", n: \"KeyN\", o: \"KeyO\", p: \"KeyP\", q: \"KeyQ\", r: \"KeyR\", s: \"KeyS\", t: \"KeyT\", u: \"KeyU\", v: \"KeyV\", w: \"KeyW\", x: \"KeyX\", y: \"KeyY\", z: \"KeyZ\", // A: \"KeyA\", B: \"KeyB\", C: \"KeyC\", D: \"KeyD\", E: \"KeyE\", F: \"KeyF\", G: \"KeyG\", H: \"KeyH\", I: \"KeyI\", J: \"KeyJ\", K: \"KeyK\", L: \"KeyL\", M: \"KeyM\", N: \"KeyN\", O: \"KeyO\", P: \"KeyP\", Q: \"KeyQ\", R: \"KeyR\", S: \"KeyS\", T: \"KeyT\", U: \"KeyU\", V: \"KeyV\", W: \"KeyW\", X: \"KeyX\", Y: \"KeyY\", Z: \"KeyZ\", \"-\": \"Minus\", _: \"Minus\", \"=\": \"Equal\", \"+\": \"Equal\", \"[\": \"BracketLeft\", \"{\": \"BracketLeft\", \"]\": \"BracketRight\", \"}\": \"BracketRight\", \"|\": \"Backslash\", \"\\\\\": \"Backslash\", \"`\": \"Backquote\", \"~\": \"Backquote\", \";\": \"Semicolon\", \":\": \"Semicolon\", \"'\": \"Quote\", '\"': \"Quote\", \",\": \"Comma\", \"<\": \"Comma\", \".\": \"Period\", \">\": \"Period\", \"/\": \"Slash\", \"?\": \"Slash\", // Numpad keys \"{numpad0}\": \"Numpad0\", \"{numpad1}\": \"Numpad1\", \"{numpad2}\": \"Numpad2\", \"{numpad3}\": \"Numpad3\", \"{numpad4}\": \"Numpad4\", \"{numpad5}\": \"Numpad5\", \"{numpad6}\": \"Numpad6\", \"{numpad7}\": \"Numpad7\", \"{numpad8}\": \"Numpad8\", \"{numpad9}\": \"Numpad9\", \"{numlock}\": \"numlock\", \"{numpadmultiply}\": \"NumpadMultiply\", \"{numpadadd}\": \"NumpadAdd\", \"{numpadsubtract}\": \"NumpadSubtract\", \"{numpaddecimal}\": \"NumpadDecimal\", \"{numpaddivide}\": \"NumpadDivide\", \"{numpadenter}\": \"NumpadEnter\", // Function keys \"{f1}\": \"F1\", \"{f2}\": \"F2\", \"{f3}\": \"F3\", \"{f4}\": \"F4\", \"{f5}\": \"F5\", \"{f6}\": \"F6\", \"{f7}\": \"F7\", \"{f8}\": \"F8\", \"{f9}\": \"F9\", \"{f10}\": \"F10\", \"{f11}\": \"F11\", \"{f12}\": \"F12\"","title":"Shortcuts"},{"location":"https/","text":"Encryption Certificate From version v1.4.9, blikvm defaults to HTTPS. Even if you access via HTTP, it will automatically redirect to HTTPS: sudo -s vim /mnt/exec/release/config/app.json Find the following configuration content. The key and cert are located in the path /mnt/exec/release/lib/https/. Users can replace them as needed. \"server\": { \"ssl\": { \"key\": \"./lib/https/key.pem\", \"cert\": \"./lib/https/cert.pem\" } Let's Encrypt Info You need a publicly valid domain name to use Let's Encrypt. This example uses the domain blikvm.space. Start applying for the certificate Run the following command to start applying for the certificate: certbot certonly --manual --preferred-challenges dns -d example.com Add a DNS record in the domain console. Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator manual, Installer None Requesting a certificate for blikvm.space Performing the following challenges: dns-01 challenge for blikvm.space - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Please deploy a DNS TXT record under the name _acme-challenge.blikvm.space with the following value: UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc Before continuing, verify the record is deployed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Press Enter to Continue After executing the above command, you will see similar output. Follow the prompts to log in to the domain backend (such as Amazon Cloud, Alibaba Cloud, Tencent Cloud, etc.), add a TXT record named _acme-challenge.example.com, and use UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc as the record value. When the DNS record takes effect, press Enter to continue. Warn DNS records do not take effect immediately, so press Enter later. Use the command nslookup -type=TXT _acme-challenge.blikvm.space to verify if the DNS is effective, as shown below: root@blikvm(rw):/mnt/tmp# nslookup -type=TXT _acme-challenge.blikvm.space Server: 192.168.8.1 Address: 192.168.8.1#53 Non-authoritative answer: _acme-challenge.blikvm.space text = \"UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc\" Authoritative answers can be found from: You will receive a certificate application success prompt (similar to the following content): Waiting for verification... Cleaning up challenges Subscribe to the EFF mailing list (email: info@blicube.com). IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/blikvm.space/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/blikvm.space/privkey.pem Your certificate will expire on 2025-03-04. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run \"certbot renew\" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le 4. Use the certificate According to step 3, you can see that the certificate path is in /etc/letsencrypt/live/blikvm.space/. Modify the configuration file: vim /mnt/exec/release/config/app.json Replace the following key and cert with \"server\": { \"ssl\": { \"key\": \"/etc/letsencrypt/live/blikvm.space/privkey.pem\", \"cert\": \"/etc/letsencrypt/live/blikvm.space/fullchain.pem\" } 5. Set the local domain name for blikvm. Open /etc/hosts on the PC, and add the following line. The IP and domain name here depend on your actual situation. 192.168.8.16 blikvm.space Then you can directly access blikvm using the domain name.","title":"Encrypt certificates"},{"location":"https/#encryption-certificate","text":"From version v1.4.9, blikvm defaults to HTTPS. Even if you access via HTTP, it will automatically redirect to HTTPS: sudo -s vim /mnt/exec/release/config/app.json Find the following configuration content. The key and cert are located in the path /mnt/exec/release/lib/https/. Users can replace them as needed. \"server\": { \"ssl\": { \"key\": \"./lib/https/key.pem\", \"cert\": \"./lib/https/cert.pem\" }","title":"Encryption Certificate"},{"location":"https/#lets-encrypt","text":"Info You need a publicly valid domain name to use Let's Encrypt. This example uses the domain blikvm.space. Start applying for the certificate Run the following command to start applying for the certificate: certbot certonly --manual --preferred-challenges dns -d example.com Add a DNS record in the domain console. Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator manual, Installer None Requesting a certificate for blikvm.space Performing the following challenges: dns-01 challenge for blikvm.space - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Please deploy a DNS TXT record under the name _acme-challenge.blikvm.space with the following value: UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc Before continuing, verify the record is deployed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Press Enter to Continue After executing the above command, you will see similar output. Follow the prompts to log in to the domain backend (such as Amazon Cloud, Alibaba Cloud, Tencent Cloud, etc.), add a TXT record named _acme-challenge.example.com, and use UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc as the record value. When the DNS record takes effect, press Enter to continue. Warn DNS records do not take effect immediately, so press Enter later. Use the command nslookup -type=TXT _acme-challenge.blikvm.space to verify if the DNS is effective, as shown below: root@blikvm(rw):/mnt/tmp# nslookup -type=TXT _acme-challenge.blikvm.space Server: 192.168.8.1 Address: 192.168.8.1#53 Non-authoritative answer: _acme-challenge.blikvm.space text = \"UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc\" Authoritative answers can be found from: You will receive a certificate application success prompt (similar to the following content): Waiting for verification... Cleaning up challenges Subscribe to the EFF mailing list (email: info@blicube.com). IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/blikvm.space/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/blikvm.space/privkey.pem Your certificate will expire on 2025-03-04. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run \"certbot renew\" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le 4. Use the certificate According to step 3, you can see that the certificate path is in /etc/letsencrypt/live/blikvm.space/. Modify the configuration file: vim /mnt/exec/release/config/app.json Replace the following key and cert with \"server\": { \"ssl\": { \"key\": \"/etc/letsencrypt/live/blikvm.space/privkey.pem\", \"cert\": \"/etc/letsencrypt/live/blikvm.space/fullchain.pem\" } 5. Set the local domain name for blikvm. Open /etc/hosts on the PC, and add the following line. The IP and domain name here depend on your actual situation. 192.168.8.16 blikvm.space Then you can directly access blikvm using the domain name.","title":"Let's Encrypt"},{"location":"make-image/","text":"Make your own image When you have made modifications to an image and want to create your own image, you can follow the steps below on Linux to create a minimal image. touch /mnt/tmp/firstboot > ~/.bash_history Firstly, use the gparted software to open the SD card of the image you want to create. Use gparted to partition the unused space and set it as unallocated. This ensures that this portion of empty space without any valid content is not included in the image creation. Next, use the fdisk command to view the size of the available space, as shown in the following image, which is 10151935. Then, use the dd command to write to an empty img file. Set the count value to be greater than the size of the volume end obtained from fdisk by at least 1. touch blikvm-armbian-v4-20230623.img sudo dd if = /dev/sdb of = ./blikvm-armbian-v4-20230623.img bs = 512 count = 10151936 Wait for the dd command to finish executing.","title":"Make Image"},{"location":"make-image/#make-your-own-image","text":"When you have made modifications to an image and want to create your own image, you can follow the steps below on Linux to create a minimal image. touch /mnt/tmp/firstboot > ~/.bash_history Firstly, use the gparted software to open the SD card of the image you want to create. Use gparted to partition the unused space and set it as unallocated. This ensures that this portion of empty space without any valid content is not included in the image creation. Next, use the fdisk command to view the size of the available space, as shown in the following image, which is 10151935. Then, use the dd command to write to an empty img file. Set the count value to be greater than the size of the volume end obtained from fdisk by at least 1. touch blikvm-armbian-v4-20230623.img sudo dd if = /dev/sdb of = ./blikvm-armbian-v4-20230623.img bs = 512 count = 10151936 Wait for the dd command to finish executing.","title":"Make your own image"},{"location":"modify_pikvm_image/","text":"Modifying PiKVM image to work with BliKVM hardware Because the blikvm hardware implementation scheme and PiKVM hardware implementation scheme are not exactly the same, you need to modify some errors through the following configuration for the official image of PiKVM. Of course, you can use the configured image . Fan config Since BliKVM's fan hardware is different to PiKVM's, you need to replace the control fan script first. The following default starting fan temperature is 40 degrees Celsius su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro Edit the /etc/kvmd/override.yaml file and add the following content to remove the web UI error warning about fans. kvmd: info: fan: unix: '' Check EDID file for 1080P60Hz input The function of the EDID file is to set the controlled computer to input according to the expected resolution. Since the image EDID file of PiKVM in different periods does not necessarily meet 1080P60Hz, when you use the CM4 version of hardware, it is found that the default output of the controlled computer is not 1080P60Hz, you can modify /etc/kvmd/tc358743-edid.hex to the following contents 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 make sure /boot/config.txt has the 4lane=1 entry in it for 1080p60hz support # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio If you use webrtc can't get audio, try to edit /etc/kvmd/janus/janus.plugin.ustreamer.jcfg to add audio support. audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" } OLED Follow the method below to enable OLED. If you use PiKVM official image, log in to PiKVM and run these commands: # rw # systemctl enable --now kvmd-oled //Enable OLED # ro If the oled still can't work, you need to check whether there has \"dtparam=i2c_arm=on\" in \"/boot/config.txt\" file, and whether there has \"i2c-dev\" in \"/etc/modules-load.d/i2c.conf\" file. If not, please create and add them. If it still does not work after the above configuration, please burn the image provided by blikvm for testing to check whether the OLED hardware is damaged. Config about v4mini image If you want to PiKVM v4mini image for blikvm v1 and v2, because v4mini image uses different gpio pins for ATX controls, so you will need the following override if you want to run v4mini image on your blikvm v1 or v2 version and be able to use ATX controls; if you don't make this change, ATX controls won't work properly (the led pins are different); Edit the /etc/kvmd/override.yaml file and add the following: kvmd: ### disable fan socket check ### info: fan: unix: '' atx: hdd_led_pin: 22 power_led_pin: 24 power_switch_pin: 23 reset_switch_pin: 27 type: gpio gpio: scheme: __v3_usb_breaker__: pin: 5 mode: output initial: false pulse: delay: 0","title":"Config for PiKVM OS"},{"location":"modify_pikvm_image/#modifying-pikvm-image-to-work-with-blikvm-hardware","text":"Because the blikvm hardware implementation scheme and PiKVM hardware implementation scheme are not exactly the same, you need to modify some errors through the following configuration for the official image of PiKVM. Of course, you can use the configured image .","title":"Modifying PiKVM image to work with BliKVM hardware"},{"location":"modify_pikvm_image/#fan-config","text":"Since BliKVM's fan hardware is different to PiKVM's, you need to replace the control fan script first. The following default starting fan temperature is 40 degrees Celsius su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro Edit the /etc/kvmd/override.yaml file and add the following content to remove the web UI error warning about fans. kvmd: info: fan: unix: ''","title":"Fan config"},{"location":"modify_pikvm_image/#check-edid-file-for-1080p60hz-input","text":"The function of the EDID file is to set the controlled computer to input according to the expected resolution. Since the image EDID file of PiKVM in different periods does not necessarily meet 1080P60Hz, when you use the CM4 version of hardware, it is found that the default output of the controlled computer is not 1080P60Hz, you can modify /etc/kvmd/tc358743-edid.hex to the following contents 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 make sure /boot/config.txt has the 4lane=1 entry in it for 1080p60hz support # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio If you use webrtc can't get audio, try to edit /etc/kvmd/janus/janus.plugin.ustreamer.jcfg to add audio support. audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" }","title":"Check EDID file for 1080P60Hz input"},{"location":"modify_pikvm_image/#oled","text":"Follow the method below to enable OLED. If you use PiKVM official image, log in to PiKVM and run these commands: # rw # systemctl enable --now kvmd-oled //Enable OLED # ro If the oled still can't work, you need to check whether there has \"dtparam=i2c_arm=on\" in \"/boot/config.txt\" file, and whether there has \"i2c-dev\" in \"/etc/modules-load.d/i2c.conf\" file. If not, please create and add them. If it still does not work after the above configuration, please burn the image provided by blikvm for testing to check whether the OLED hardware is damaged.","title":"OLED"},{"location":"modify_pikvm_image/#config-about-v4mini-image","text":"If you want to PiKVM v4mini image for blikvm v1 and v2, because v4mini image uses different gpio pins for ATX controls, so you will need the following override if you want to run v4mini image on your blikvm v1 or v2 version and be able to use ATX controls; if you don't make this change, ATX controls won't work properly (the led pins are different); Edit the /etc/kvmd/override.yaml file and add the following: kvmd: ### disable fan socket check ### info: fan: unix: '' atx: hdd_led_pin: 22 power_led_pin: 24 power_switch_pin: 23 reset_switch_pin: 27 type: gpio gpio: scheme: __v3_usb_breaker__: pin: 5 mode: output initial: false pulse: delay: 0","title":"Config about v4mini image"},{"location":"msd/","text":"Mass Storage Drive Reinstall the system Video BliKVM's USB device simulation feature allows you to remotely mount images on the virtual machine's mass storage drive, making it easy to install or reinstall operating systems and other software. This can be a useful feature for system administrators who need to manage multiple virtual machines remotely. By mounting an image on the mass storage drive, you can quickly and easily set up or configure a new virtual machine without having to physically connect a USB drive or other external storage device. Note: the size of the MSD is limited by the size of your sd card or eMMC module. Web UI The entrance to the MSD virtual USB drive is as follows: Using the web to upload images and create bootable drives are both synchronous processes. If you exit the MSD UI interface after uploading an image, you can resume the upload from where it left off the next time you select the same image. However, once you exit the bootable drive creation process, you cannot resume it; you will need to start over. The default upload path for images is /mnt/upload . If an upload fails, you can manually delete the cache files that were not successfully uploaded. Due to the large size of some image files, image uploads are divided into slices and then merged. The merging process cannot be resumed, so please ensure you wait for the merge to complete (which may take some time) before proceeding to the next step. Creating a bootable drive involves two steps: creating a virtual USB drive and copying the selected ISO image into the created virtual USB drive. Both steps have progress indicators. Please wait until both steps show 100% progress before clicking Next. Upload images manually (without Web UI) Confirm that the following four paths exist. If you are using the official latest image of blikvm, and it is fully configured, there is no need to check. /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy SSH logs in to blikvm, executes the rw command, and changes the system permission to writable. rw In your PC ,use scp cmd send iso file to kvm board. scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ excute msd cmd.wait until excute end. If you don't use option paramter\uff1a The default size of the USB flash disk is 5GB. The default filename is scan /mnt/msd/user dir. The default msd name is ventoy. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make If your iso is large than 5GB.You can specify the optional parameter - s xxx, xxx is the Size. If you need specify iso ,you can use -f xxx.iso. If you want to specify the msd name, you can use -n xxx. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso Tips: cp progresses slowly, please be patient. If you want to excute other cmd, you can use other option. c option contains : make/conn/disconn/clean Connect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn Disconnect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn Clean msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean Through the WebUI restart PC, enter BIOS, modify boot priority, set BliKVM USB first. According to the steps, select operating system, format partition and install.","title":"MSD"},{"location":"msd/#mass-storage-drive","text":"Reinstall the system Video BliKVM's USB device simulation feature allows you to remotely mount images on the virtual machine's mass storage drive, making it easy to install or reinstall operating systems and other software. This can be a useful feature for system administrators who need to manage multiple virtual machines remotely. By mounting an image on the mass storage drive, you can quickly and easily set up or configure a new virtual machine without having to physically connect a USB drive or other external storage device. Note: the size of the MSD is limited by the size of your sd card or eMMC module.","title":"Mass Storage Drive"},{"location":"msd/#web-ui","text":"The entrance to the MSD virtual USB drive is as follows: Using the web to upload images and create bootable drives are both synchronous processes. If you exit the MSD UI interface after uploading an image, you can resume the upload from where it left off the next time you select the same image. However, once you exit the bootable drive creation process, you cannot resume it; you will need to start over. The default upload path for images is /mnt/upload . If an upload fails, you can manually delete the cache files that were not successfully uploaded. Due to the large size of some image files, image uploads are divided into slices and then merged. The merging process cannot be resumed, so please ensure you wait for the merge to complete (which may take some time) before proceeding to the next step. Creating a bootable drive involves two steps: creating a virtual USB drive and copying the selected ISO image into the created virtual USB drive. Both steps have progress indicators. Please wait until both steps show 100% progress before clicking Next.","title":"Web UI"},{"location":"msd/#upload-images-manually-without-web-ui","text":"Confirm that the following four paths exist. If you are using the official latest image of blikvm, and it is fully configured, there is no need to check. /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy SSH logs in to blikvm, executes the rw command, and changes the system permission to writable. rw In your PC ,use scp cmd send iso file to kvm board. scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ excute msd cmd.wait until excute end. If you don't use option paramter\uff1a The default size of the USB flash disk is 5GB. The default filename is scan /mnt/msd/user dir. The default msd name is ventoy. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make If your iso is large than 5GB.You can specify the optional parameter - s xxx, xxx is the Size. If you need specify iso ,you can use -f xxx.iso. If you want to specify the msd name, you can use -n xxx. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso Tips: cp progresses slowly, please be patient. If you want to excute other cmd, you can use other option. c option contains : make/conn/disconn/clean Connect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn Disconnect msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn Clean msd sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean Through the WebUI restart PC, enter BIOS, modify boot priority, set BliKVM USB first. According to the steps, select operating system, format partition and install.","title":"Upload images manually (without Web UI)"},{"location":"port-forwarding/","text":"Port forwarding After v1.4.7 version If your ISP provides an external IP address for the router, you can configure Port forwarding to access BliKVM: If the web interface uses the HTTP protocol and occupies port 80; If the web interface uses the HTTPS protocol and occupies port 443; If you do not have an external IP address, we suggest trying to use Tailscale VPN \u3002","title":"Port Forwarding"},{"location":"port-forwarding/#port-forwarding","text":"After v1.4.7 version If your ISP provides an external IP address for the router, you can configure Port forwarding to access BliKVM: If the web interface uses the HTTP protocol and occupies port 80; If the web interface uses the HTTPS protocol and occupies port 443; If you do not have an external IP address, we suggest trying to use Tailscale VPN \u3002","title":"Port forwarding"},{"location":"rtc/","text":"RTC Clock The purpose of an RTC (Real-Time Clock) is to provide real-time information about the current date and time for a device or system. It is an independent clock chip or module that has its own power source, allowing it to maintain accurate time even when the device is powered off or experiences a power outage. Due to shipping restrictions on international deliveries, the RTC hardware is shipped without a battery, and users need to purchase a CR1220 button cell battery themselves. The specific RTC clock model used in different versions of BliKVM may vary, and the usage methods may differ slightly. BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563 1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc0 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30 BliKVM V4 - pcf8563 1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc1 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"RTC clock"},{"location":"rtc/#rtc-clock","text":"The purpose of an RTC (Real-Time Clock) is to provide real-time information about the current date and time for a device or system. It is an independent clock chip or module that has its own power source, allowing it to maintain accurate time even when the device is powered off or experiences a power outage. Due to shipping restrictions on international deliveries, the RTC hardware is shipped without a battery, and users need to purchase a CR1220 button cell battery themselves. The specific RTC clock model used in different versions of BliKVM may vary, and the usage methods may differ slightly.","title":"RTC Clock"},{"location":"rtc/#blikvm-v2-pcie-and-blikvm-v3-hat-pcf8563","text":"1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc0 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563"},{"location":"rtc/#blikvm-v4-pcf8563","text":"1. Check if the pcf8563 RTC clock hardware is properly recognized on the i2c bus. The pcf8563 RTC clock has an i2c address of 0x51. Execute the following command as root to verify if the rtc clock is correctly detected on the i2c bus: root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. Register a new i2c device with the Linux system's i2c subsystem. The device is a pcf8563 with an i2c address of 0x51. Use the command ls /dev | grep rtc to verify if the rtc1 device appears, indicating a successful registration. echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. Set the current system time to the RTC clock time. hwclock -f /dev/rtc1 -w 4. Read the time from the RTC clock. If the time can be read, it indicates that the RTC module is functioning correctly. root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V4 - pcf8563"},{"location":"serial_over_usb/","text":"Serial-over-USB connection The BliKVM device can be accessed through the serial port terminal. 1. For hardware connection, you should use the USB to TTL module to connect the USB of the computer to the uart of BliKVM. If you are using the Hat version, please connect the serial ports GPIO14 and GPIO15. If you are using the PCIe version, connect the GTR pin marked by the PCB 2. Install terminal login tools on the computer. For example, Putty for Windows 3. Use the Putty instructions. Enter the correct COM port. The default baud rate is 115200 . Select serial as the connection method, and then click Open\uff08Use PiKVM firmware as an example If your computer cannot correctly recognize the USB to TTL module, please follow the steps below to install the driver for your computer Connect the USB-A connector to your admin host (in this example, it's on a Windows host). As a result, Device Manager will show a new USB Serial device in Other Devices. Download and extract/run drivers. In this example, I downloaded and extracted the ZIP file. https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all Update driver for the new USB Serial device, point it to where you extracted the files, and click Next then Close. If done right, the new USB serial device should now show up under Ports as USB-SERIAL CH340 (COMX).","title":"Serial-over-USB"},{"location":"serial_over_usb/#serial-over-usb-connection","text":"The BliKVM device can be accessed through the serial port terminal. 1. For hardware connection, you should use the USB to TTL module to connect the USB of the computer to the uart of BliKVM. If you are using the Hat version, please connect the serial ports GPIO14 and GPIO15. If you are using the PCIe version, connect the GTR pin marked by the PCB 2. Install terminal login tools on the computer. For example, Putty for Windows 3. Use the Putty instructions. Enter the correct COM port. The default baud rate is 115200 . Select serial as the connection method, and then click Open\uff08Use PiKVM firmware as an example If your computer cannot correctly recognize the USB to TTL module, please follow the steps below to install the driver for your computer Connect the USB-A connector to your admin host (in this example, it's on a Windows host). As a result, Device Manager will show a new USB Serial device in Other Devices. Download and extract/run drivers. In this example, I downloaded and extracted the ZIP file. https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all Update driver for the new USB Serial device, point it to where you extracted the files, and click Next then Close. If done right, the new USB serial device should now show up under Ports as USB-SERIAL CH340 (COMX).","title":"Serial-over-USB connection"},{"location":"ssh/","text":"SSH Config Starting from version 1.4.7, the web interface supports direct access to the blikvm SSH terminal. The default username and password to access the terminal are blikvm/blikvm. If you have changed the password for this user, you will need to update the corresponding username and password in the app.json file. sudo -s vim /mnt/exec/release/config/app.json # Locate the following configuration and update it with your new credentials. \"sshUser\": \"blikvm\", \"sshPassword\": \"blikvm\"","title":"SSH Terminal"},{"location":"ssh/#ssh-config","text":"Starting from version 1.4.7, the web interface supports direct access to the blikvm SSH terminal. The default username and password to access the terminal are blikvm/blikvm. If you have changed the password for this user, you will need to update the corresponding username and password in the app.json file. sudo -s vim /mnt/exec/release/config/app.json # Locate the following configuration and update it with your new credentials. \"sshUser\": \"blikvm\", \"sshPassword\": \"blikvm\"","title":"SSH Config"},{"location":"static_ip/","text":"Set static IP To configure a static IP address on a BliKVM image, you can follow these steps: v1 v2 v3 versions - Debian SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/dhcpcd.conf Within the file, locate the section that starts with # Example static IP configuration . Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: interface eth0 static ip_address = 192 .168.1.100/24 static routers = 192 .168.1.1 static domain_name_servers = 192 .168.1.1 Adjust the values according to your network configuration. Save the changes. Restart the BliKVM for the changes to take effect: sudo reboot v4 version - armbian SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/network/interfaces Within the file, locate the section that starts with # Example static IP configuration . Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: source /etc/network/interfaces.d/* auto eth0 allow-hotplug eth0 iface eth0 inet static address 192 .168.0.100 netmask 255 .255.255.0 gateway 192 .168.0.1 dns-nameservers 192 .168.0.1 Adjust the values according to your network configuration. Save the changes. Restart the NetworkManager for the changes to take effect: sudo systemctl restart NetworkManager After the reboot, your BliKVM will use the configured static IP address instead of obtaining one dynamically from a DHCP server. Make sure the static IP address you choose is not already assigned to another device on the network and is within the same subnet.","title":"Set Static IP "},{"location":"static_ip/#set-static-ip","text":"To configure a static IP address on a BliKVM image, you can follow these steps:","title":"Set static IP"},{"location":"static_ip/#v1-v2-v3-versions-debian","text":"SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/dhcpcd.conf Within the file, locate the section that starts with # Example static IP configuration . Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: interface eth0 static ip_address = 192 .168.1.100/24 static routers = 192 .168.1.1 static domain_name_servers = 192 .168.1.1 Adjust the values according to your network configuration. Save the changes. Restart the BliKVM for the changes to take effect: sudo reboot","title":"v1 v2 v3 versions - Debian"},{"location":"static_ip/#v4-version-armbian","text":"SSH into the BliKVM, If it is a read-only system, please use the rw command to make the system writable. Edit the network interfaces configuration file using the following command: sudo vim /etc/network/interfaces Within the file, locate the section that starts with # Example static IP configuration . Uncomment the lines below that section and modify them to set your desired static IP address, gateway, DNS servers, and other network settings. For example: source /etc/network/interfaces.d/* auto eth0 allow-hotplug eth0 iface eth0 inet static address 192 .168.0.100 netmask 255 .255.255.0 gateway 192 .168.0.1 dns-nameservers 192 .168.0.1 Adjust the values according to your network configuration. Save the changes. Restart the NetworkManager for the changes to take effect: sudo systemctl restart NetworkManager After the reboot, your BliKVM will use the configured static IP address instead of obtaining one dynamically from a DHCP server. Make sure the static IP address you choose is not already assigned to another device on the network and is within the same subnet.","title":"v4 version - armbian"},{"location":"tailscale/","text":"Tailscale VPN Tailscale can be used to access your BliKVM from the public internet. It is a convenient and free networking tool for setting up a small VPN network. This document provides an example for accessing your BliKVM over the internet, but you can also use Zerotier or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the Tailscale documentation. BliKVM Installation First, make sure that your system has read-write access. If it's a read-only system, use the rw command to make it writable. Then, proceed with the Tailscale installation by running the following command: curl -fsSL https://tailscale.com/install.sh | sh Note that in some regions, such as China, downloading Tailscale directly might be problematic due to network restrictions. Please configure your network accordingly. Adding BliKVM to your Tailscale Network Register an account on the Tailscale website and generate your own keys in the settings. On the BliKVM terminal, use the following command to add BliKVM to your Tailscale network: sudo tailscale up --authkey = your-auth-key --accept-routes If everything goes well, you can run ip addr show tailscale0 on the BliKVM terminal to view the IP address assigned by Tailscale for the virtual network. Here's an example output: 3 : tailscale0: mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100 .126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever The IP address, such as 100.126.223.28 , can be used to access the BliKVM web interface from your host machine. Host Installation Download and install Tailscale from the Tailscale website on your controlling host machine. Log in with your Tailscale account, and then you can check the Tailscale admin page to verify if both your machines are online. Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://","title":"Tailscale VPN"},{"location":"tailscale/#tailscale-vpn","text":"Tailscale can be used to access your BliKVM from the public internet. It is a convenient and free networking tool for setting up a small VPN network. This document provides an example for accessing your BliKVM over the internet, but you can also use Zerotier or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the Tailscale documentation.","title":"Tailscale VPN"},{"location":"tailscale/#blikvm-installation","text":"First, make sure that your system has read-write access. If it's a read-only system, use the rw command to make it writable. Then, proceed with the Tailscale installation by running the following command: curl -fsSL https://tailscale.com/install.sh | sh Note that in some regions, such as China, downloading Tailscale directly might be problematic due to network restrictions. Please configure your network accordingly.","title":"BliKVM Installation"},{"location":"tailscale/#adding-blikvm-to-your-tailscale-network","text":"Register an account on the Tailscale website and generate your own keys in the settings. On the BliKVM terminal, use the following command to add BliKVM to your Tailscale network: sudo tailscale up --authkey = your-auth-key --accept-routes If everything goes well, you can run ip addr show tailscale0 on the BliKVM terminal to view the IP address assigned by Tailscale for the virtual network. Here's an example output: 3 : tailscale0: mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100 .126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever The IP address, such as 100.126.223.28 , can be used to access the BliKVM web interface from your host machine.","title":"Adding BliKVM to your Tailscale Network"},{"location":"tailscale/#host-installation","text":"Download and install Tailscale from the Tailscale website on your controlling host machine. Log in with your Tailscale account, and then you can check the Tailscale admin page to verify if both your machines are online. Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://","title":"Host Installation"},{"location":"update/","text":"Software update introduction If you are running an older version then we recommend first reflashing and subsequently running the update process, while you are next to your BliKVM device. Introduction The currently available versions of the BLIKVM project are hosted in the release package of the GitHub. The update software function needs to keep the device connected. There are currently two ways to update the software. Method 1: Click the update button through the web interface, and the program will be updated automatically. A restart is required after the update. Method 2: Manually run the script on the KVM terminal to update, and restart after the update. Common causes of upgrade errors The device is not connected to the network; Network access to GitHub is limited; We strongly recommend performing the update while you are in close proximity to the BliKVM hardware you are upgrading. This way if anything goes wrong you can intervene. If you are familiar with command-line operations, we recommend manually updating so that you can monitor the command-line status in real time. If the update is abnormal and the web interface cannot exit the update status, use ssh to get you a terminal and reboot to recover. Manually run the script to update In the terminal\uff0cif the system terminal shows the ro keyword that means your system is currently in read-only, it is necessary to use the rw command to make the system writable. sudo -i curl -L https://raw.githubusercontent.com/ThomasVon2021/blikvm/master/script/update.py -o /tmp/update.py && python3 /tmp/update.py Observe the output of the terminal. When you see the message of a successful upgrade, enter in the terminal the: reboot command and the reboot should take effect. If you are unable to update successfully due to network issues, you can download the latest release.tar.gz package on another PC with a stable network connection and follow the instructions below for installation. Download Address: https://github.com/ThomasVon2021/blikvm/releases v1 v2 v3 hardware use release.tar.gz v4 hardware use release-h616-v4.tar.gz SSH into the device terminal and use tar -zxvf release.tar.gz to extract the release.tar.gz file. sudo -i cd /your release path/ python3 install_release.py --releasepath=./ You can compare the versions before and after in /usr/bin/blikvm/package.json . If you have upgraded to the specified version, the installation is successful, and you can reboot for the changes to take effect.","title":"Upgrade"},{"location":"update/#software-update-introduction","text":"If you are running an older version then we recommend first reflashing and subsequently running the update process, while you are next to your BliKVM device.","title":"Software update introduction"},{"location":"update/#introduction","text":"The currently available versions of the BLIKVM project are hosted in the release package of the GitHub. The update software function needs to keep the device connected. There are currently two ways to update the software. Method 1: Click the update button through the web interface, and the program will be updated automatically. A restart is required after the update. Method 2: Manually run the script on the KVM terminal to update, and restart after the update. Common causes of upgrade errors The device is not connected to the network; Network access to GitHub is limited; We strongly recommend performing the update while you are in close proximity to the BliKVM hardware you are upgrading. This way if anything goes wrong you can intervene. If you are familiar with command-line operations, we recommend manually updating so that you can monitor the command-line status in real time. If the update is abnormal and the web interface cannot exit the update status, use ssh to get you a terminal and reboot to recover.","title":"Introduction"},{"location":"update/#manually-run-the-script-to-update","text":"In the terminal\uff0cif the system terminal shows the ro keyword that means your system is currently in read-only, it is necessary to use the rw command to make the system writable. sudo -i curl -L https://raw.githubusercontent.com/ThomasVon2021/blikvm/master/script/update.py -o /tmp/update.py && python3 /tmp/update.py Observe the output of the terminal. When you see the message of a successful upgrade, enter in the terminal the: reboot command and the reboot should take effect. If you are unable to update successfully due to network issues, you can download the latest release.tar.gz package on another PC with a stable network connection and follow the instructions below for installation. Download Address: https://github.com/ThomasVon2021/blikvm/releases v1 v2 v3 hardware use release.tar.gz v4 hardware use release-h616-v4.tar.gz SSH into the device terminal and use tar -zxvf release.tar.gz to extract the release.tar.gz file. sudo -i cd /your release path/ python3 install_release.py --releasepath=./ You can compare the versions before and after in /usr/bin/blikvm/package.json . If you have upgraded to the specified version, the installation is successful, and you can reboot for the changes to take effect.","title":"Manually run the script to update"},{"location":"usb-splitter-guide/","text":"USB/PWR Splitter guide 1. Introduction The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage. 2.Mechanical Diagram 3.Test video USB splitter Video 4.3D printable case A simple snap fit case for the USB splitter. Download file","title":"USB Splitter"},{"location":"usb-splitter-guide/#usbpwr-splitter-guide","text":"","title":"USB/PWR Splitter guide"},{"location":"usb-splitter-guide/#1-introduction","text":"The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage.","title":"1. Introduction"},{"location":"usb-splitter-guide/#2mechanical-diagram","text":"","title":"2.Mechanical Diagram"},{"location":"usb-splitter-guide/#3test-video","text":"USB splitter Video","title":"3.Test video"},{"location":"usb-splitter-guide/#43d-printable-case","text":"A simple snap fit case for the USB splitter. Download file","title":"4.3D printable case"},{"location":"wake-on-lan/","text":"Wake-on-LAN Introduction Wake-on-LAN, abbreviated as WOL or WoL, is a feature that allows a computer that is in sleep or shutdown state to be powered on remotely by KVM through a local network by sending a specific message. WoL requires support from the controlled computer; otherwise, the feature won't work. Additionally, it needs to be ensured that WoL is enabled and configured correctly. With this feature, you can power on the computer without needing to use the ATX function. If users encounter anomalies when using KVM's WoL, they can try testing it using software that supports WoL. How to Use","title":"Wake-on-LAN"},{"location":"wake-on-lan/#wake-on-lan","text":"","title":"Wake-on-LAN"},{"location":"wake-on-lan/#introduction","text":"Wake-on-LAN, abbreviated as WOL or WoL, is a feature that allows a computer that is in sleep or shutdown state to be powered on remotely by KVM through a local network by sending a specific message. WoL requires support from the controlled computer; otherwise, the feature won't work. Additionally, it needs to be ensured that WoL is enabled and configured correctly. With this feature, you can power on the computer without needing to use the ATX function. If users encounter anomalies when using KVM's WoL, they can try testing it using software that supports WoL.","title":"Introduction"},{"location":"wake-on-lan/#how-to-use","text":"","title":"How to Use"},{"location":"wifi/","text":"Wifi Configure Because BLIKVM has many kinds of hardware and supports different OS, such as BLIKVM OS and PiKVM OS, different OS confifure wifi methods may not be the same. Please confirm the hardware and OS usage before using the method in this document. Please confirm that the hardware you use supports wifi function, for example, the CM400200 version does not have wifi function; If the SOC of KVM hardware is CM4, please confirm whether wifi antenna is connected; PiKVM OS is arch linux; BLIKVM OS raspberry pi series is debian system, and v4 series is armbian system; v1 v2 v3 Use raspi-config for Wi-Fi config on Raspberry Pi Debian systems Log in to SSH. Command: ssh blikvm@ip Mount the system as writable. Command: rw Start raspi-config. Command: sudo raspi-config Select System Options Select Wireless LAN Select the country where Wi-Fi is located, and China will select CN. If it has been set before, this step will skip to 7 Enter the Wi-Fi SSID (name) Enter the Wi-Fi password. If there is no password, press Enter directly At this time, you will return to the interface in Step 4, press the tab key to select Finish , then press Enter Check whether to connect to wifi. Command: ifconfig wlan0. If you see the ip obtained, you are connected Mount the system as read-only. Command: ro v4 Hardware using Armbian System with armbian-config Log in via SSH using the command: ssh blikvm@ip to access the Armbian system. Enter the following command to launch the armbian-config tool: sudo armbian-config In the armbian-config menu, navigate and select options using the arrow keys and press Enter . Scroll down to the \"Network\" option using the arrow keys and press Enter to enter the submenu. In the \"Network\" submenu, select the \"Wireless\" option and press Enter to enter the Wi-Fi configuration menu. In the Wi-Fi configuration menu, select the \"Connect to Wi-Fi\" option and press Enter to enter the Wi-Fi connection setup. armbian-config will list the available wireless interfaces and already configured networks. Select the wireless interface you want to connect to and press Enter . armbian-config will display the list of available Wi-Fi networks. Use the arrow keys to select the Wi-Fi network you want to connect to and press Enter . If the Wi-Fi network is password-protected, armbian-config will prompt you to enter the Wi-Fi password. Enter the password and press Enter . Wait for a moment while the Armbian system attempts to connect to the specified Wi-Fi network. If the connection is successful, you will see a corresponding message on the screen. Exit the armbian-config tool. Please note that the menu options and configurations mentioned above may vary slightly depending on the specific version of the Armbian system. Make sure to follow the appropriate steps based on your system version and configuration.","title":"Wifi Config"},{"location":"wifi/#wifi-configure","text":"Because BLIKVM has many kinds of hardware and supports different OS, such as BLIKVM OS and PiKVM OS, different OS confifure wifi methods may not be the same. Please confirm the hardware and OS usage before using the method in this document. Please confirm that the hardware you use supports wifi function, for example, the CM400200 version does not have wifi function; If the SOC of KVM hardware is CM4, please confirm whether wifi antenna is connected; PiKVM OS is arch linux; BLIKVM OS raspberry pi series is debian system, and v4 series is armbian system;","title":"Wifi Configure"},{"location":"wifi/#v1-v2-v3-use-raspi-config-for-wi-fi-config-on-raspberry-pi-debian-systems","text":"Log in to SSH. Command: ssh blikvm@ip Mount the system as writable. Command: rw Start raspi-config. Command: sudo raspi-config Select System Options Select Wireless LAN Select the country where Wi-Fi is located, and China will select CN. If it has been set before, this step will skip to 7 Enter the Wi-Fi SSID (name) Enter the Wi-Fi password. If there is no password, press Enter directly At this time, you will return to the interface in Step 4, press the tab key to select Finish , then press Enter Check whether to connect to wifi. Command: ifconfig wlan0. If you see the ip obtained, you are connected Mount the system as read-only. Command: ro","title":"v1 v2 v3 Use raspi-config for Wi-Fi config on Raspberry Pi Debian systems"},{"location":"wifi/#v4-hardware-using-armbian-system-with-armbian-config","text":"Log in via SSH using the command: ssh blikvm@ip to access the Armbian system. Enter the following command to launch the armbian-config tool: sudo armbian-config In the armbian-config menu, navigate and select options using the arrow keys and press Enter . Scroll down to the \"Network\" option using the arrow keys and press Enter to enter the submenu. In the \"Network\" submenu, select the \"Wireless\" option and press Enter to enter the Wi-Fi configuration menu. In the Wi-Fi configuration menu, select the \"Connect to Wi-Fi\" option and press Enter to enter the Wi-Fi connection setup. armbian-config will list the available wireless interfaces and already configured networks. Select the wireless interface you want to connect to and press Enter . armbian-config will display the list of available Wi-Fi networks. Use the arrow keys to select the Wi-Fi network you want to connect to and press Enter . If the Wi-Fi network is password-protected, armbian-config will prompt you to enter the Wi-Fi password. Enter the password and press Enter . Wait for a moment while the Armbian system attempts to connect to the specified Wi-Fi network. If the connection is successful, you will see a corresponding message on the screen. Exit the armbian-config tool. Please note that the menu options and configurations mentioned above may vary slightly depending on the specific version of the Armbian system. Make sure to follow the appropriate steps based on your system version and configuration.","title":"v4 Hardware using Armbian System with armbian-config"},{"location":"zerotier/","text":"ZeroTier VPN ZeroTier allows secure access to your BliKVM even throught NAT on both sides. It lets you build modern, secure multi-point virtualized networks of almost any type. This document provides an example for accessing your BliKVM over the internet, but you can also use Tailscale or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the ZeroTier documentation . Installing ZeroTier on BliKVM First of all, prepare account and VPN network at ZeroTier with instructions here: Create a Network , save Network ID for later usage. Next, connect with BliKVM terminal using SSH protocol, and check for read-write access. If it's a read-only system, use the rw command to make it writable. Now install ZeroTier client using the command below: curl -s https://install.zerotier.com | sudo bash Note that in some regions, such as China, downloading ZeroTier directly might be problematic due to network restrictions. Please configure your network accordingly. Adding BliKVM to your ZeroTier Network On the BliKVM terminal, use the following command to add BliKVM to your ZeroTier network (using your ZeoroTier Network ID, for example d5e04297a16fa690): sudo zerotier-cli join d5e04297a16fa690 If everything goes well, you can run ip addr show zerotier network device (name is starting with zt) on the BliKVM terminal to view the IP address assigned by ZeroTier for the virtual network. Here's an example output: 3 : zt6ovrlscs: mtu 2800 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether d6:e4:eb:ae:db:64 brd ff:ff:ff:ff:ff:ff inet 172 .25.96.75/16 brd 172 .25.255.255 scope global zt6ovrlscs valid_lft forever preferred_lft forever inet6 fe80::d4e4:ebff:feae:db64/64 scope link valid_lft forever preferred_lft forever The IP address, such as 172.25.96.75 , can be used to access the BliKVM web interface from your host machine. Installing ZeroTier on client computer Go to Download section at ZeroTier website and install ZeroTier on your controlling host machine. Join your ZeroTier Network ID, and then you can check your network page to verify if both your machines are online. Check if they are authorzied to connect to network there (Auth? column). Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://","title":"ZeroTier VPN"},{"location":"zerotier/#zerotier-vpn","text":"ZeroTier allows secure access to your BliKVM even throught NAT on both sides. It lets you build modern, secure multi-point virtualized networks of almost any type. This document provides an example for accessing your BliKVM over the internet, but you can also use Tailscale or other VPN solutions. The following is a basic example, and for any specific settings or functionalities, please refer to the ZeroTier documentation .","title":"ZeroTier VPN"},{"location":"zerotier/#installing-zerotier-on-blikvm","text":"First of all, prepare account and VPN network at ZeroTier with instructions here: Create a Network , save Network ID for later usage. Next, connect with BliKVM terminal using SSH protocol, and check for read-write access. If it's a read-only system, use the rw command to make it writable. Now install ZeroTier client using the command below: curl -s https://install.zerotier.com | sudo bash Note that in some regions, such as China, downloading ZeroTier directly might be problematic due to network restrictions. Please configure your network accordingly.","title":"Installing ZeroTier on BliKVM"},{"location":"zerotier/#adding-blikvm-to-your-zerotier-network","text":"On the BliKVM terminal, use the following command to add BliKVM to your ZeroTier network (using your ZeoroTier Network ID, for example d5e04297a16fa690): sudo zerotier-cli join d5e04297a16fa690 If everything goes well, you can run ip addr show zerotier network device (name is starting with zt) on the BliKVM terminal to view the IP address assigned by ZeroTier for the virtual network. Here's an example output: 3 : zt6ovrlscs: mtu 2800 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether d6:e4:eb:ae:db:64 brd ff:ff:ff:ff:ff:ff inet 172 .25.96.75/16 brd 172 .25.255.255 scope global zt6ovrlscs valid_lft forever preferred_lft forever inet6 fe80::d4e4:ebff:feae:db64/64 scope link valid_lft forever preferred_lft forever The IP address, such as 172.25.96.75 , can be used to access the BliKVM web interface from your host machine.","title":"Adding BliKVM to your ZeroTier Network"},{"location":"zerotier/#installing-zerotier-on-client-computer","text":"Go to Download section at ZeroTier website and install ZeroTier on your controlling host machine. Join your ZeroTier Network ID, and then you can check your network page to verify if both your machines are online. Check if they are authorzied to connect to network there (Auth? column). Once they are online, you can use the following address to access BliKVM from your controlling host machine: http://","title":"Installing ZeroTier on client computer"}]} \ No newline at end of file diff --git a/generated/en/sitemap.xml b/generated/en/sitemap.xml index 32fc6e89..a25d0a7e 100644 --- a/generated/en/sitemap.xml +++ b/generated/en/sitemap.xml @@ -2,192 +2,192 @@ None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily None - 2024-11-28 + 2024-12-04 daily \ No newline at end of file diff --git a/generated/en/sitemap.xml.gz b/generated/en/sitemap.xml.gz index ea6e5413..5c3499d5 100644 Binary files a/generated/en/sitemap.xml.gz and b/generated/en/sitemap.xml.gz differ diff --git a/generated/en/static_ip/index.html b/generated/en/static_ip/index.html index bdafd9fb..752800a5 100644 --- a/generated/en/static_ip/index.html +++ b/generated/en/static_ip/index.html @@ -534,9 +534,9 @@

v4 version - armbian

Adjust the values according to your network configuration.

  1. Save the changes.
    2. -
  2. Restart the BliKVM for the changes to take effect:
    3. +
  3. Restart the NetworkManager for the changes to take effect:
-
sudo reboot
+
sudo systemctl restart NetworkManager
 

 
After the reboot, your BliKVM will use the configured static IP address instead of obtaining one dynamically from a DHCP server. Make sure the static IP address you choose is not already assigned to another device on the network and is within the same subnet.

 

diff --git a/generated/en/update/index.html b/generated/en/update/index.html
index 29692216..ee71219c 100644
--- a/generated/en/update/index.html
+++ b/generated/en/update/index.html
@@ -537,7 +537,7 @@ 
Manually run the script to up
 
     
       Last update:
-      November 15, 2024
+      November 28, 2024
 

         Created:
         January 21, 2023
diff --git a/generated/zh/OLED-display/index.html b/generated/zh/OLED-display/index.html
index 3f010a7f..3bca709f 100644
--- a/generated/zh/OLED-display/index.html
+++ b/generated/zh/OLED-display/index.html
@@ -549,7 +549,7 @@ 
仅 BliKVM v4 Allwinner

 
     
       Last update:
-      November 18, 2024
+      November 28, 2024
 

         Created:
         June 10, 2022
diff --git a/generated/zh/assets/images/https/letsencrypt.png b/generated/zh/assets/images/https/letsencrypt.png
new file mode 100644
index 00000000..c78a1782
Binary files /dev/null and b/generated/zh/assets/images/https/letsencrypt.png differ
diff --git a/generated/zh/https/index.html b/generated/zh/https/index.html
index 2898873d..f24df4fa 100644
--- a/generated/zh/https/index.html
+++ b/generated/zh/https/index.html
@@ -441,7 +441,7 @@
 
 
 
-
加密证书

+
加密证书

 
blikvm v1.4.9版本后,默认为https启动，即使访问http也会自动被重定向到https:
 
sudo -s
 vim /mnt/exec/release/config/app.json
@@ -453,6 +453,91 @@ 
加密证书

     "cert": "./lib/https/cert.pem"
 }
 

+
Let's Encrypt申请合法证书:

+

+
Info

+
你需要有一个公网合法的域名才能使用Let's Encrypt,本说明以blikvm.space域名为例

+

+
    
+
  1. 开始申请证书
+执行如下命令开始申请证书：
+
    certbot certonly --manual --preferred-challenges dns -d example.com
+
    2. 
+
  2. 
+
    在域名控制台中添加解析记录.
+
    Saving debug log to /var/log/letsencrypt/letsencrypt.log
+Plugins selected: Authenticator manual, Installer None
+Requesting a certificate for blikvm.space
+Performing the following challenges:
+dns-01 challenge for blikvm.space
+
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+Please deploy a DNS TXT record under the name
+_acme-challenge.blikvm.space with the following value:
+
+UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc
+
+Before continuing, verify the record is deployed.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+Press Enter to Continue
+
    
+执行完上面命令后,会有如上类似输出，根据上面提示，登录域名后台（比如亚马逊云，阿里云、腾讯云等等），添加名为 _acme-challenge.example.com 的 TXT 记录，并使用 UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc 作为记录值。 
    
+
    3. 
+
  3. 
+
    当DNS记录生效后，点击回车继续  
    
+
    4. 
+

+

+
Warn

+
    
+
  • 由于 DNS 记录不会马上生效，所以稍后再按回车键。
    • 
+
  • 使用 nslookup -type=TXT _acme-challenge.blikvm.space 命令验证 DNS 是否生效，生效如下:
+
    root@blikvm(rw):/mnt/tmp# nslookup -type=TXT _acme-challenge.blikvm.space
+Server:     192.168.8.1
+Address:    192.168.8.1#53
+
+Non-authoritative answer:
+_acme-challenge.blikvm.space    text = "UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc"
+Authoritative answers can be found from:
+
    • 
+

+

+
将会收到证书申请成功的提示（类似如下内容）：
+
Waiting for verification...
+Cleaning up challenges
+Subscribe to the EFF mailing list (email: info@blicube.com).
+
+IMPORTANT NOTES:
+ - Congratulations! Your certificate and chain have been saved at:
+   /etc/letsencrypt/live/blikvm.space/fullchain.pem
+   Your key file has been saved at:
+   /etc/letsencrypt/live/blikvm.space/privkey.pem
+   Your certificate will expire on 2025-03-04. To obtain a new or
+   tweaked version of this certificate in the future, simply run
+   certbot again. To non-interactively renew *all* of your
+   certificates, run "certbot renew"
+ - If you like Certbot, please consider supporting our work by:
+
+   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
+   Donating to EFF:                    https://eff.org/donate-le
+

+4. 使用证书
+根据步骤3可以看到证书路径在/etc/letsencrypt/live/blikvm.space/，修改配置文件：
+
vim /mnt/exec/release/config/app.json
+将下面key和cert替换为
+"server": {
+    "ssl": {
+    "key": "/etc/letsencrypt/live/blikvm.space/privkey.pem",
+    "cert": "/etc/letsencrypt/live/blikvm.space/fullchain.pem"
+}
+

+5. 设置blikvm的局域网域名，在pc上打开/etc/hosts,如可以增加下面这一行，这里的ip和域名根据你的实际情况而定
+
192.168.8.16 blikvm.space
+

+
    
+
  1. 然后你就可以直接用域名访问blikvm。
+ 
    2. 
+

 

 

 
diff --git a/generated/zh/search/search_index.json b/generated/zh/search/search_index.json
index b01558a6..5e7da4eb 100644
--- a/generated/zh/search/search_index.json
+++ b/generated/zh/search/search_index.json
@@ -1 +1 @@
-{"config":{"indexing":"full","lang":["en","ja","ru"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"BLIKVM Overview BLIKVM\u662f\u4e00\u6b3e\u5f00\u6e90\u8f6f\u4ef6\u7684KVM\u4e13\u4e1a\u8bbe\u5907\uff0c\u76ee\u524d\u67094\u4e2a\u7248\u672c\uff0cv1 CM4, v2 PCIe, v3 HAT, v4 Allwinner\u3002\u8be5\u8bbe\u5907\u5728\u4e8e\u5e2e\u52a9\u7528\u6237\u901a\u8fc7\u5f97\u5230\u63a7\u5236\u8bbe\u5907\u7684HDMI \u753b\u9762\u548c\u9f20\u6807\u952e\u76d8\uff0c\u53bb\u8fdc\u7a0b\u7ba1\u7406\u670d\u52a1\u5668\u3001\u5de5\u4f5c\u7ad9\u6216\u4e2a\u4ebaPC\u7b49\u3002 \u65e0\u8bba\u76ee\u6807\u8bbe\u5907\u7684\u64cd\u4f5c\u7cfb\u7edf\u662f\u5426\u80fd\u6b63\u5e38\u8fd0\u884c\uff0c\u53ef\u4ee5\u901a\u8fc7BLIKVM\u89e3\u51b3\u76ee\u6807\u8bbe\u5907\u7684\u4e00\u5207\u95ee\u9898\u3002\u5982\uff1a\u914d\u7f6eBIOS\u7cfb\u7edf\uff0c\u901a\u8fc7\u4f7f\u7528\u8fdc\u7a0bCD-ROM\u6216\u8005\u95ea\u5b58\u9a71\u52a8\u5668\u7ed9\u76ee\u6807\u8bbe\u5907\u91cd\u65b0\u5b89\u88c5\u64cd\u4f5c\u7cfb\u7edf\u3002\u548c\u57fa\u4e8e\u8f6f\u4ef6\u7684\u8fdc\u7a0b\u7ba1\u7406\u65b9\u5f0f\u4e0d\u540c\uff0c\u4f60\u65e0\u9700\u5728\u88ab\u63a7\u7535\u8111\u5b89\u88c5\u4efb\u4f55\u8f6f\u4ef6\uff0c\u505a\u5230\u65e0\u4fb5\u5165\u5f0f\u63a7\u5236\u3002 \u5728\u8fd9\u91cc\u4f60\u53ef\u4ee5\u627e\u5230\u5173\u4e8eBLIKVM\u6240\u6709\u7684\u4f7f\u7528\u6587\u6863\u3002\u6b22\u8fce\u52a0\u5165BLIKVM\u7684 Discord \u7fa4\u7ec4\u548c\u6765\u81ea\u5168\u4e16\u754c\u7684\u7231\u597d\u8005\u548c\u7528\u6237\u8fdb\u884c\u4ea4\u6d41\uff0c\u83b7\u5f97\u6280\u672f\u652f\u6301\uff0c\u5e38\u89c1\u95ee\u9898\u89e3\u7b54\u548c\u65b0\u95fb\u7b49\u3002 \u529f\u80fd BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 H616/H313 SOC \u6811\u8393\u6d3eCM4 \u6811\u8393\u6d3eCM4 \u6811\u8393\u6d3e4B \u5168\u5fd7H616/H313 \u652f\u6301\u8f93\u5165\u7684\u6700\u9ad8\u5206\u8fa8\u7387 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI\u91c7\u96c6\u82af\u7247 TC358743 TC358743 TC358743 MS2131 HDMI\u73af\u51fa \u65e0 \u65e0 \u65e0 \u6709 PoE\u4f9b\u7535 \u4e0d\u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 DC\u4f9b\u7535 \u4e0d\u652f\u6301 \u4e0d\u652f\u6301 \u4e0d\u652f\u6301 \u652f\u6301 USB-C\u4f9b\u7535 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 USB\u7535\u6e90/\u6570\u636e\u5206\u79bb\u5668 \u6709 \u6709(\u989d\u5916\u6a21\u5757) \u6709 \u6709 \u4e32\u53e3\u7ec8\u7aef \u4e0d\u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 ATX\u5f00\u5173\u673a\u63a7\u5236 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 BIOS\u63a7\u5236 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u7cfb\u7edf\u5f00\u6e90 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u91cd\u88c5\u88ab\u63a7\u7535\u8111\u7cfb\u7edf \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u98ce\u6247 \u6709(\u4e0d\u652f\u6301\u8c03\u901f) \u6709 \u6709 \u53ef\u914d(\u9ed8\u8ba4\u914d\u6563\u70ed\u7247) \u5c4f\u5e55\u79cd\u7c7b OLED 128x64 \u767d\u8272 OLED 128x64 \u767d\u8272 OLED 128x32 \u767d\u8272 LCD 240x240 \u5f69\u8272 RTC\u65f6\u949f \u6709(DS1307) \u6709(PCF8563) \u6709(PCF8563) \u6709(PCF8563) \u5916\u58f3 \u91d1\u5c5e\u9ed1 \u65e0 \u91d1\u5c5e\u9ed1\u84dd\u6a58\u767d(1U\u673a\u67b6\u517c\u5bb9) \u91d1\u5c5e\u9ed1(1U\u673a\u67b6\u517c\u5bb9) \u8702\u9e23\u5668 \u65e0 \u65e0 \u65e0 \u6709 \u81ea\u5b9a\u4e49\u6309\u94ae \u65e0 \u65e0 \u65e0 \u6709 \u8f6f\u4ef6\u5347\u7ea7 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 32GB SD\u5361 \u6709(\u542bOS) \u6709(\u542bOS) \u6709(\u542bOS) \u6709(\u542bOS) \u89e3\u51b3HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898 \u672a\u89e3\u51b3 \u5df2\u89e3\u51b3 \u5df2\u89e3\u51b3 \u5df2\u89e3\u51b3 \u4e13\u4e1a\u6280\u672f\u652f\u6301 \u6709 \u6709 \u6709 \u6709 \u529f\u80fd HDMI\u89c6\u9891\u91c7\u96c6 (\u6700\u9ad8\u652f\u63011080P 60Hz) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 ATX\u5f00\u5173\u673a PWM\u98ce\u6247\u63a7\u5236 \u5168\u5c4f\u6a21\u5f0f \u4ece\u526a\u8d34\u677f\u7c98\u8d34\u6587\u672c VPN\u7ec4\u7f51\u652f\u6301 \u5927\u5bb9\u91cf\u5b58\u50a8\u9a71\u52a8\u5668 (\u6a21\u62dfCD-ROM\u6216\u95ea\u5b58\u9a71\u52a8\u5668) \u8fdc\u7a0b\u63a7\u5236\u591a\u53f0\u4e3b\u673a\uff08\u901a\u8fc7\u642d\u914dKVM\u5207\u6362\u5668\uff09 OLED\u5c4f\u5e55\u663e\u793a\u7cfb\u7edf\u4fe1\u606f\uff08\u6e29\u5ea6\u3001IP\u5730\u5740\uff0c\u8fd0\u884c\u65f6\u95f4\u7b49\uff09 \u8d26\u53f7\u5bc6\u7801\u8ba4\u8bc1 Guide 1.BliKVM v1 CM4 \u7248\u672c 2.BliKVM v2 PCIe \u7248\u672c 3.BliKVM v3 HAT \u7248\u672c 4.BliKVM v4 Allwinner \u7248\u672c","title":"BliKVM\u4ecb\u7ecd"},{"location":"#blikvm-overview","text":"BLIKVM\u662f\u4e00\u6b3e\u5f00\u6e90\u8f6f\u4ef6\u7684KVM\u4e13\u4e1a\u8bbe\u5907\uff0c\u76ee\u524d\u67094\u4e2a\u7248\u672c\uff0cv1 CM4, v2 PCIe, v3 HAT, v4 Allwinner\u3002\u8be5\u8bbe\u5907\u5728\u4e8e\u5e2e\u52a9\u7528\u6237\u901a\u8fc7\u5f97\u5230\u63a7\u5236\u8bbe\u5907\u7684HDMI \u753b\u9762\u548c\u9f20\u6807\u952e\u76d8\uff0c\u53bb\u8fdc\u7a0b\u7ba1\u7406\u670d\u52a1\u5668\u3001\u5de5\u4f5c\u7ad9\u6216\u4e2a\u4ebaPC\u7b49\u3002 \u65e0\u8bba\u76ee\u6807\u8bbe\u5907\u7684\u64cd\u4f5c\u7cfb\u7edf\u662f\u5426\u80fd\u6b63\u5e38\u8fd0\u884c\uff0c\u53ef\u4ee5\u901a\u8fc7BLIKVM\u89e3\u51b3\u76ee\u6807\u8bbe\u5907\u7684\u4e00\u5207\u95ee\u9898\u3002\u5982\uff1a\u914d\u7f6eBIOS\u7cfb\u7edf\uff0c\u901a\u8fc7\u4f7f\u7528\u8fdc\u7a0bCD-ROM\u6216\u8005\u95ea\u5b58\u9a71\u52a8\u5668\u7ed9\u76ee\u6807\u8bbe\u5907\u91cd\u65b0\u5b89\u88c5\u64cd\u4f5c\u7cfb\u7edf\u3002\u548c\u57fa\u4e8e\u8f6f\u4ef6\u7684\u8fdc\u7a0b\u7ba1\u7406\u65b9\u5f0f\u4e0d\u540c\uff0c\u4f60\u65e0\u9700\u5728\u88ab\u63a7\u7535\u8111\u5b89\u88c5\u4efb\u4f55\u8f6f\u4ef6\uff0c\u505a\u5230\u65e0\u4fb5\u5165\u5f0f\u63a7\u5236\u3002 \u5728\u8fd9\u91cc\u4f60\u53ef\u4ee5\u627e\u5230\u5173\u4e8eBLIKVM\u6240\u6709\u7684\u4f7f\u7528\u6587\u6863\u3002\u6b22\u8fce\u52a0\u5165BLIKVM\u7684 Discord \u7fa4\u7ec4\u548c\u6765\u81ea\u5168\u4e16\u754c\u7684\u7231\u597d\u8005\u548c\u7528\u6237\u8fdb\u884c\u4ea4\u6d41\uff0c\u83b7\u5f97\u6280\u672f\u652f\u6301\uff0c\u5e38\u89c1\u95ee\u9898\u89e3\u7b54\u548c\u65b0\u95fb\u7b49\u3002 \u529f\u80fd BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 H616/H313 SOC \u6811\u8393\u6d3eCM4 \u6811\u8393\u6d3eCM4 \u6811\u8393\u6d3e4B \u5168\u5fd7H616/H313 \u652f\u6301\u8f93\u5165\u7684\u6700\u9ad8\u5206\u8fa8\u7387 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI\u91c7\u96c6\u82af\u7247 TC358743 TC358743 TC358743 MS2131 HDMI\u73af\u51fa \u65e0 \u65e0 \u65e0 \u6709 PoE\u4f9b\u7535 \u4e0d\u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 DC\u4f9b\u7535 \u4e0d\u652f\u6301 \u4e0d\u652f\u6301 \u4e0d\u652f\u6301 \u652f\u6301 USB-C\u4f9b\u7535 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 USB\u7535\u6e90/\u6570\u636e\u5206\u79bb\u5668 \u6709 \u6709(\u989d\u5916\u6a21\u5757) \u6709 \u6709 \u4e32\u53e3\u7ec8\u7aef \u4e0d\u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 ATX\u5f00\u5173\u673a\u63a7\u5236 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 BIOS\u63a7\u5236 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u7cfb\u7edf\u5f00\u6e90 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u91cd\u88c5\u88ab\u63a7\u7535\u8111\u7cfb\u7edf \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u98ce\u6247 \u6709(\u4e0d\u652f\u6301\u8c03\u901f) \u6709 \u6709 \u53ef\u914d(\u9ed8\u8ba4\u914d\u6563\u70ed\u7247) \u5c4f\u5e55\u79cd\u7c7b OLED 128x64 \u767d\u8272 OLED 128x64 \u767d\u8272 OLED 128x32 \u767d\u8272 LCD 240x240 \u5f69\u8272 RTC\u65f6\u949f \u6709(DS1307) \u6709(PCF8563) \u6709(PCF8563) \u6709(PCF8563) \u5916\u58f3 \u91d1\u5c5e\u9ed1 \u65e0 \u91d1\u5c5e\u9ed1\u84dd\u6a58\u767d(1U\u673a\u67b6\u517c\u5bb9) \u91d1\u5c5e\u9ed1(1U\u673a\u67b6\u517c\u5bb9) \u8702\u9e23\u5668 \u65e0 \u65e0 \u65e0 \u6709 \u81ea\u5b9a\u4e49\u6309\u94ae \u65e0 \u65e0 \u65e0 \u6709 \u8f6f\u4ef6\u5347\u7ea7 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 32GB SD\u5361 \u6709(\u542bOS) \u6709(\u542bOS) \u6709(\u542bOS) \u6709(\u542bOS) \u89e3\u51b3HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898 \u672a\u89e3\u51b3 \u5df2\u89e3\u51b3 \u5df2\u89e3\u51b3 \u5df2\u89e3\u51b3 \u4e13\u4e1a\u6280\u672f\u652f\u6301 \u6709 \u6709 \u6709 \u6709","title":"BLIKVM Overview"},{"location":"#_1","text":"HDMI\u89c6\u9891\u91c7\u96c6 (\u6700\u9ad8\u652f\u63011080P 60Hz) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 ATX\u5f00\u5173\u673a PWM\u98ce\u6247\u63a7\u5236 \u5168\u5c4f\u6a21\u5f0f \u4ece\u526a\u8d34\u677f\u7c98\u8d34\u6587\u672c VPN\u7ec4\u7f51\u652f\u6301 \u5927\u5bb9\u91cf\u5b58\u50a8\u9a71\u52a8\u5668 (\u6a21\u62dfCD-ROM\u6216\u95ea\u5b58\u9a71\u52a8\u5668) \u8fdc\u7a0b\u63a7\u5236\u591a\u53f0\u4e3b\u673a\uff08\u901a\u8fc7\u642d\u914dKVM\u5207\u6362\u5668\uff09 OLED\u5c4f\u5e55\u663e\u793a\u7cfb\u7edf\u4fe1\u606f\uff08\u6e29\u5ea6\u3001IP\u5730\u5740\uff0c\u8fd0\u884c\u65f6\u95f4\u7b49\uff09 \u8d26\u53f7\u5bc6\u7801\u8ba4\u8bc1","title":"\u529f\u80fd"},{"location":"#guide","text":"1.BliKVM v1 CM4 \u7248\u672c 2.BliKVM v2 PCIe \u7248\u672c 3.BliKVM v3 HAT \u7248\u672c 4.BliKVM v4 Allwinner \u7248\u672c","title":"Guide"},{"location":"BLIHAT-Installation/","text":"BLIHAT \u5b89\u88c5\u8bf4\u660e 1.\u62c6\u5f00\u5305\u88c5\uff0c\u6253\u5f00\u888b\u5b50\uff0c\u62ff\u51fa\u8bbe\u5907 2.\u5b89\u88c5\u4e3b\u4f53\u8bbe\u5907 \u5378\u4e0b\u5916\u58f3\u80cc\u9762\u7684\u5982\u56fe\u4e2d\u6240\u793a\u7684\u87ba\u4e1d \u6253\u5f00\u5916\u58f3 \u5378\u4e0b\u80cc\u9762\u5269\u4e0b\u7684\u87ba\u4e1d \u6253\u5f00\u914d\u4ef6\u5305\uff0c\u62ff\u51fa\u56fe\u7247\u4e2d\u7684\u8bbe\u5907 \u5b89\u88c5SD\u5361 \u5b89\u88c5FFC\u7ebf\u7f06 \u5b89\u88c5Hat\u5230\u6811\u8393\u6d3e4B\u4e0a \u5b89\u88c54\u9897\u94dc\u67f1 \u5b89\u88c5C790\u6a21\u5757\u5230Hat\u4e0a\uff0c\u4f7f\u7528\u4f60\u5378\u4e0b\u6765\u7684\u957f\u87ba\u4e1d \u5b89\u88c5\u97f3\u9891\u7ebf\u7f06 \u6495\u53bb\u7845\u80f6\u7247\u4e0a\u7684\u4fdd\u62a4\u819c\uff0c\u5c06\u5176\u8d34\u5230\u6811\u8393\u6d3e\u5982\u56fe\u6240\u793a\u7684\u4f4d\u7f6e Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"v3 HAT\u5b89\u88c5\u8bf4\u660e"},{"location":"BLIHAT-Installation/#blihat","text":"1.\u62c6\u5f00\u5305\u88c5\uff0c\u6253\u5f00\u888b\u5b50\uff0c\u62ff\u51fa\u8bbe\u5907 2.\u5b89\u88c5\u4e3b\u4f53\u8bbe\u5907 \u5378\u4e0b\u5916\u58f3\u80cc\u9762\u7684\u5982\u56fe\u4e2d\u6240\u793a\u7684\u87ba\u4e1d \u6253\u5f00\u5916\u58f3 \u5378\u4e0b\u80cc\u9762\u5269\u4e0b\u7684\u87ba\u4e1d \u6253\u5f00\u914d\u4ef6\u5305\uff0c\u62ff\u51fa\u56fe\u7247\u4e2d\u7684\u8bbe\u5907 \u5b89\u88c5SD\u5361 \u5b89\u88c5FFC\u7ebf\u7f06 \u5b89\u88c5Hat\u5230\u6811\u8393\u6d3e4B\u4e0a \u5b89\u88c54\u9897\u94dc\u67f1 \u5b89\u88c5C790\u6a21\u5757\u5230Hat\u4e0a\uff0c\u4f7f\u7528\u4f60\u5378\u4e0b\u6765\u7684\u957f\u87ba\u4e1d \u5b89\u88c5\u97f3\u9891\u7ebf\u7f06 \u6495\u53bb\u7845\u80f6\u7247\u4e0a\u7684\u4fdd\u62a4\u819c\uff0c\u5c06\u5176\u8d34\u5230\u6811\u8393\u6d3e\u5982\u56fe\u6240\u793a\u7684\u4f4d\u7f6e Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"BLIHAT \u5b89\u88c5\u8bf4\u660e"},{"location":"BLIKVM-CM4-guide/","text":"BLIKVM v1 CM4\u4f7f\u7528\u8bf4\u660e BLIKVM CM4 v1\u8bc4\u6d4b\u89c6\u9891 BliKVM v1\u662f\u4e00\u6b3e\u751f\u4ea7\u5c31\u7eea\u3001\u5373\u63d2\u5373\u7528\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86\u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406\u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e\u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5\u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1\uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01 BliKVM v1 Datasheet \u529f\u80fd\u7279\u70b9 \u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@60Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 WiFi \uff08\u53ef\u9009\uff09 OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) \u5b89\u88c5\u8981\u6c42 \u5982\u679c\u4f60\u8d2d\u4e70\u7684\u662f\u9700\u81ea\u5df1\u7ec4\u88c5\u7684\u7248\u672c\uff08\u4e0d\u662fplug-n-play\u7248\u672c\uff09\uff0c\u4f60\u9700\u8981\u81ea\u5df1\u51c6\u5907\u4ee5\u4e0b\u8bbe\u5907 \u6811\u8393\u6d3eCM4\uff0c\u6700\u5c0f1Gb RAM. USB-C\u8f6cUSB-A\u7ebf\u7f06. HDMI\u7ebf\u7f06. \u7f51\u7ebf. \u7535\u6e90\u9002\u914d\u5668(5.1V 3A USB-C). \u7535\u6e90\u9002\u914d\u5668 \u5728BLIKVM CM4 V2.2\u7248\u672c\u4e2d\uff0c\u4f60\u5fc5\u987b\u4f7f\u7528USB-C\u8f6cUSB-A\u7ebf\u7f06\u8fdb\u884c\u4f9b\u7535\uff0c\u5982\u679c\u4f7f\u7528USB-C\u8f6cUSB-C\u7ebf\u7f06\u53ef\u80fd\u65e0\u6cd5\u4f9b\u7535\u3002\u8fd9\u662f\u8fd9\u4e2a\u7248\u672c\u786c\u4ef6\u8bbe\u8ba1\u7684bug\uff0c\u5728\u5b83\u540e\u9762\u7684\u7248\u672c \u4e2d\u6b64\u95ee\u9898\u5c06\u4f1a\u88ab\u4fee\u590d\u3002 \u57fa\u7840\u914d\u7f6e 1. \u51fa\u5382\u9ed8\u8ba4\u914d\u7684SD\u5361\u5df2\u70e7\u5f55\u955c\u50cf\uff0c\u65e0\u9700\u70e7\u5f55\u3002\u82e5\u60a8\u9700\u8981\u91cd\u5237\u7cfb\u7edf\u6216\u8005DIY\uff0c\u53ef\u53c2\u8003 \u70e7\u5f55\u955c\u50cf\u5230SD\u5361\u6216\u8005eMMC 2. \u5982\u679c\u60a8\u4e0d\u662fplug\u7248\u672c,\u53c2\u8003\u4e0b\u9762\u7684\u89c6\u9891\u548c\u8bf4\u660e\u8fdb\u884c\u8bbe\u5907\u5b89\u88c5: 1. \u7528\u5305\u88f9\u914d\u7684\u87ba\u4e1d\u5200\u6253\u5f00\u91d1\u5c5e\u5916\u58f3\uff0c\u62c6\u4e0bPCB\u4e3b\u677f\uff1b 2. \u5c06CM4\u5b89\u88c5\u5728PCB\u4e3b\u677f\u4e0a\uff0c\u6ce8\u610f\u5b89\u88c5CM4\u65f6\u4e24\u6392\u5361\u69fd\u8981\u5bf9\u9f50\uff0c\u7136\u540e\u5c06\u7845\u80f6\u5bfc\u70ed\u7247\u8d34\u5728CM4\u4e3b\u82af\u7247\u4e0a\uff0c\u4ece\u800c\u53ef\u4ee5\u4f7fCM4\u5229\u7528\u91d1\u5c5e\u5916\u58f3\u6563\u70ed\uff1b 3. \u98ce\u6247\u9ed8\u8ba4\u4e0d\u63a5\uff0c\u5916\u58f3\u6563\u70ed\u8db3\u591f\uff0c\u6839\u636e\u60a8\u7684CM4\u7248\u672c\u9009\u62e9\u6027\u5b89\u88c5Wi-Fi\u5929\u7ebf; 4. \u91cd\u65b0\u5b89\u88c5\u597dPCB\u4e3b\u677f\u548c\u91d1\u5c5e\u5916\u58f3\uff0c\u5373\u5b89\u88c5\u5b8c\u6210. \u5b8c\u6574\u62c6\u7bb1\u548c\u5b89\u88c5\u89c6\u9891 Ortimo\u4f7f\u7528BLIKVM CM4 eMMC\u7248\u672c\u6307\u5bfc 3. \u6839\u636e\u4e0b\u56fe\u63a5\u53e3\u5b9a\u4e49\u6240\u793a\uff0c\u8fde\u63a5\u88ab\u63a7\u7535\u8111\u5230BLIKVM\u4e0a: HDMI IN\u548cotg\u63a5\u53e3\u5fc5\u987b\u548c\u88ab\u63a7\u7535\u8111\u8fde\u63a5\uff0cATX\u662f\u53ef\u9009\u9879\u3002\u5efa\u8bae\u5728BLIKVM\u548c\u88ab\u63a7\u7535\u8111\u4e4b\u95f4\u6700\u597d\u4e0d\u8981\u6709USB\u6269\u5c55\u575e\uff0c\u56e0\u4e3a\u5728UEFI\u6216BIOS\u9636\u6bb5\uff0c\u53ef\u80fd\u68c0\u6d4b\u4e0d\u5230\u6269\u5c55\u575e\u3002 BLIKVM CM4\u7248\u672c\u6700\u9ad8\u652f\u63011080P60Hz\u7684\u8f93\u5165\u3002 \u901a\u8fc7Ethernet\u5c06BLIKVM\u8fde\u63a5\u5230\u7f51\u7edc\uff0c\u901a\u8fc7PWR IN\u7aef\u53e3\u5de5\u4f9b\u7535\u3002 4. ATX\u7535\u6e90\u63a7\u5236\u8fde\u63a5 \u4e3a\u4e86\u7ba1\u7406\u88ab\u63a7\u8ba1\u7b97\u673a\u7684\u7535\u6e90\uff0c\u4f60\u9700\u8981\u5c06CN-ATX\u7aef\u53e3\u548c\u88ab\u63a7\u7535\u8111\u8fde\u63a5\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528\u63d0\u4f9b\u7684ATX\u7ebf\u7f06(60\u5398\u7c73)\u6216\u8005\u675c\u90a6\u7ebf\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111\u7684\u4e3b\u677f\u4e0a\u3002 \u4e3a\u4e86\u517c\u5bb9\u7f51\u53e3\u5f62\u5f0f\u7684ATX\u63a7\u5236\u677f\uff0cv1\u6709\u4e13\u95e8\u7684ATX\u6269\u5c55\u5305\uff0c\u65b9\u4fbf\u5ba2\u6237\u76f4\u63a5\u901a\u8fc7\u7f51\u7ebf\u548c\u5b89\u88c5\u5230\u673a\u7bb1\u6321\u677f\u7684ATX\u677f\u8fde\u63a5\u3002 5. \u5728\u6240\u6709\u8fde\u63a5\u7ebf\u8fde\u63a5\u597d\u540e,\u5bf9BliKVM\u8fdb\u884c\u4e0a\u7535\uff0c\u76f4\u5230\u663e\u793a\u5c4f\u51fa\u73b0\u753b\u9762\uff0c\u5373\u8bbe\u5907\u6b63\u5e38\u542f\u52a8\u3002 6. \u4ed4\u7ec6\u9605\u8bfb \u201c\u7b2c\u4e00\u6b65\u201d \u6307\u5357-\u5982\u4f55\u5728\u7f51\u7edc\u4e0a\u67e5\u627e\u8bbe\u5907\u3001\u5982\u4f55\u767b\u5f55\u3001\u66f4\u6539\u5bc6\u7801\u7b49\u7b49\u3002\u6309\u7167\u4e0a\u9762\u63cf\u8ff0\u7684\u6b65\u9aa4\u64cd\u4f5c\uff0c\u7136\u540e\u8fd4\u56de\u672c\u9875\u3002 \u7531\u4e8eBliKVM v1\u4e5f\u652f\u6301PiKVM OS\uff0c\u82e5\u4f60\u624b\u4e0a\u7684v1\u51fa\u5382OS\u4e3aPiKVM\uff0c\u5173\u4e8eweb\u4f7f\u7528\u8bf4\u660e\u8bf7 \u53c2\u8003\u6587\u6863 \u3002 7. \u5c1d\u8bd5\u4f7f\u7528 Web \u754c\u9762\u7ba1\u7406\u8ba1\u7b97\u673a\u7684 BliKVM\u3002 \u786e\u4fdd\u60a8\u53ef\u4ee5\u770b\u5230\u56fe\u50cf\u5e76\u4e14\u952e\u76d8\u548c\u9f20\u6807\u90fd\u6b63\u5e38\u5de5\u4f5c\u3002\u5982\u679c\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u8bf7\u67e5\u770b\u6211\u4eec\u7684 \u5e38\u89c1\u95ee\u9898 \uff08\u5b83\u975e\u5e38\u6709\u7528\uff09\u3002\u5982\u679c\u6ca1\u6709\u4efb\u4f55\u5e2e\u52a9\uff0c\u8bf7\u5728\u6211\u4eec\u7684 Discord\u804a\u5929\u5ba4 \u5bfb\u6c42\u652f\u6301\u3002 8. \u60a8\u53ef\u4ee5\u67e5\u770bwiki\u5176\u4ed6\u7684\u9875\u9762\uff0c\u63a2\u7d22BliKVM\u7684\u66f4\u591a\u529f\u80fd\uff0c\u795d\u60a8\u73a9\u7684\u5f00\u5fc3\uff01 Wi-Fi\u5929\u7ebf\u8fde\u63a5 \u5982\u4f60\u7684CM4\u6709Wi-Fi\u529f\u80fd\uff0c\u62c6\u5f00v1\u7684\u91d1\u5c5e\u76d2\u5b50\uff0c\u8bf7\u5c06\u5305\u88f9\u4e2d\u7684Wi-Fi\u5929\u7ebf\uff0c\u5b89\u88c5\u5230CM4\u7684IPX\u63a5\u53e3\uff0c\u5373\u4e0b\u56fe\u4e2d\u7ea2\u6846\u7684\u63a5\u53e3\uff1b\u5176\u4e2d\u5916\u58f3\u5b89\u88c5\u5929\u7ebf\u4f4d\u7f6e\u4e3a\u63a5\u53e3\u5b9a\u4e49\u56fe\u4e2d\u768411\u5904\u3002 \u652f\u6301 1080p60hz HDMI\u8f93\u5165 \u5728V2.2\u7248\u672c\u4e2d\uff0c\u8fd9\u91cc\u6709\u4e00\u4e2aCSI\u901a\u9053\u5207\u6362\u5668\u3002\u786e\u8ba4\u5207\u6362\u5668\u57284\u901a\u9053\u4e00\u4fa7\u3002\u518d\u5176\u5b83\u7248\u672c\u4e2d\uff0c\u79fb\u9664\u4e86\u6b64\u5207\u6362\u5668\uff0c\u9ed8\u8ba44\u901a\u9053\u5168\u90e8\u4f7f\u80fd\u3002 \u53d1\u8d27\u6e05\u5355 BLIKVM v1 \u4e0d\u542b CM4 \u5916\u58f3 1 PCB\u4e3b\u677f 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 OLED\u5c4f\u5e55 1 BLIKVM v1\u542b CM4102000 \u5916\u58f3 1 PCB\u4e3b\u677f 1 CM4102000 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 OLED\u5c4f\u5e55 1 WiFi\u5929\u7ebf 1 BLIKVM v1 \u542b CM4002000 \u5916\u58f3 1 PCB\u4e3b\u677f 1 CM4002000 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 WiFi\u5929\u7ebf 1 \u8d2d\u4e70\u94fe\u63a5 v1\u6dd8\u5b9d\u5730\u5740","title":"BliKVM v1 CM4\u5bfc\u89c8"},{"location":"BLIKVM-CM4-guide/#blikvm-v1-cm4","text":"BLIKVM CM4 v1\u8bc4\u6d4b\u89c6\u9891 BliKVM v1\u662f\u4e00\u6b3e\u751f\u4ea7\u5c31\u7eea\u3001\u5373\u63d2\u5373\u7528\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86\u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406\u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e\u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5\u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1\uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01 BliKVM v1 Datasheet","title":"BLIKVM v1 CM4\u4f7f\u7528\u8bf4\u660e"},{"location":"BLIKVM-CM4-guide/#_1","text":"\u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@60Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 WiFi \uff08\u53ef\u9009\uff09 OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC)","title":"\u529f\u80fd\u7279\u70b9"},{"location":"BLIKVM-CM4-guide/#_2","text":"\u5982\u679c\u4f60\u8d2d\u4e70\u7684\u662f\u9700\u81ea\u5df1\u7ec4\u88c5\u7684\u7248\u672c\uff08\u4e0d\u662fplug-n-play\u7248\u672c\uff09\uff0c\u4f60\u9700\u8981\u81ea\u5df1\u51c6\u5907\u4ee5\u4e0b\u8bbe\u5907 \u6811\u8393\u6d3eCM4\uff0c\u6700\u5c0f1Gb RAM. USB-C\u8f6cUSB-A\u7ebf\u7f06. HDMI\u7ebf\u7f06. \u7f51\u7ebf. \u7535\u6e90\u9002\u914d\u5668(5.1V 3A USB-C). \u7535\u6e90\u9002\u914d\u5668 \u5728BLIKVM CM4 V2.2\u7248\u672c\u4e2d\uff0c\u4f60\u5fc5\u987b\u4f7f\u7528USB-C\u8f6cUSB-A\u7ebf\u7f06\u8fdb\u884c\u4f9b\u7535\uff0c\u5982\u679c\u4f7f\u7528USB-C\u8f6cUSB-C\u7ebf\u7f06\u53ef\u80fd\u65e0\u6cd5\u4f9b\u7535\u3002\u8fd9\u662f\u8fd9\u4e2a\u7248\u672c\u786c\u4ef6\u8bbe\u8ba1\u7684bug\uff0c\u5728\u5b83\u540e\u9762\u7684\u7248\u672c \u4e2d\u6b64\u95ee\u9898\u5c06\u4f1a\u88ab\u4fee\u590d\u3002","title":"\u5b89\u88c5\u8981\u6c42"},{"location":"BLIKVM-CM4-guide/#_3","text":"1. \u51fa\u5382\u9ed8\u8ba4\u914d\u7684SD\u5361\u5df2\u70e7\u5f55\u955c\u50cf\uff0c\u65e0\u9700\u70e7\u5f55\u3002\u82e5\u60a8\u9700\u8981\u91cd\u5237\u7cfb\u7edf\u6216\u8005DIY\uff0c\u53ef\u53c2\u8003 \u70e7\u5f55\u955c\u50cf\u5230SD\u5361\u6216\u8005eMMC 2. \u5982\u679c\u60a8\u4e0d\u662fplug\u7248\u672c,\u53c2\u8003\u4e0b\u9762\u7684\u89c6\u9891\u548c\u8bf4\u660e\u8fdb\u884c\u8bbe\u5907\u5b89\u88c5: 1. \u7528\u5305\u88f9\u914d\u7684\u87ba\u4e1d\u5200\u6253\u5f00\u91d1\u5c5e\u5916\u58f3\uff0c\u62c6\u4e0bPCB\u4e3b\u677f\uff1b 2. \u5c06CM4\u5b89\u88c5\u5728PCB\u4e3b\u677f\u4e0a\uff0c\u6ce8\u610f\u5b89\u88c5CM4\u65f6\u4e24\u6392\u5361\u69fd\u8981\u5bf9\u9f50\uff0c\u7136\u540e\u5c06\u7845\u80f6\u5bfc\u70ed\u7247\u8d34\u5728CM4\u4e3b\u82af\u7247\u4e0a\uff0c\u4ece\u800c\u53ef\u4ee5\u4f7fCM4\u5229\u7528\u91d1\u5c5e\u5916\u58f3\u6563\u70ed\uff1b 3. \u98ce\u6247\u9ed8\u8ba4\u4e0d\u63a5\uff0c\u5916\u58f3\u6563\u70ed\u8db3\u591f\uff0c\u6839\u636e\u60a8\u7684CM4\u7248\u672c\u9009\u62e9\u6027\u5b89\u88c5Wi-Fi\u5929\u7ebf; 4. \u91cd\u65b0\u5b89\u88c5\u597dPCB\u4e3b\u677f\u548c\u91d1\u5c5e\u5916\u58f3\uff0c\u5373\u5b89\u88c5\u5b8c\u6210. \u5b8c\u6574\u62c6\u7bb1\u548c\u5b89\u88c5\u89c6\u9891 Ortimo\u4f7f\u7528BLIKVM CM4 eMMC\u7248\u672c\u6307\u5bfc 3. \u6839\u636e\u4e0b\u56fe\u63a5\u53e3\u5b9a\u4e49\u6240\u793a\uff0c\u8fde\u63a5\u88ab\u63a7\u7535\u8111\u5230BLIKVM\u4e0a: HDMI IN\u548cotg\u63a5\u53e3\u5fc5\u987b\u548c\u88ab\u63a7\u7535\u8111\u8fde\u63a5\uff0cATX\u662f\u53ef\u9009\u9879\u3002\u5efa\u8bae\u5728BLIKVM\u548c\u88ab\u63a7\u7535\u8111\u4e4b\u95f4\u6700\u597d\u4e0d\u8981\u6709USB\u6269\u5c55\u575e\uff0c\u56e0\u4e3a\u5728UEFI\u6216BIOS\u9636\u6bb5\uff0c\u53ef\u80fd\u68c0\u6d4b\u4e0d\u5230\u6269\u5c55\u575e\u3002 BLIKVM CM4\u7248\u672c\u6700\u9ad8\u652f\u63011080P60Hz\u7684\u8f93\u5165\u3002 \u901a\u8fc7Ethernet\u5c06BLIKVM\u8fde\u63a5\u5230\u7f51\u7edc\uff0c\u901a\u8fc7PWR IN\u7aef\u53e3\u5de5\u4f9b\u7535\u3002 4. ATX\u7535\u6e90\u63a7\u5236\u8fde\u63a5 \u4e3a\u4e86\u7ba1\u7406\u88ab\u63a7\u8ba1\u7b97\u673a\u7684\u7535\u6e90\uff0c\u4f60\u9700\u8981\u5c06CN-ATX\u7aef\u53e3\u548c\u88ab\u63a7\u7535\u8111\u8fde\u63a5\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528\u63d0\u4f9b\u7684ATX\u7ebf\u7f06(60\u5398\u7c73)\u6216\u8005\u675c\u90a6\u7ebf\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111\u7684\u4e3b\u677f\u4e0a\u3002 \u4e3a\u4e86\u517c\u5bb9\u7f51\u53e3\u5f62\u5f0f\u7684ATX\u63a7\u5236\u677f\uff0cv1\u6709\u4e13\u95e8\u7684ATX\u6269\u5c55\u5305\uff0c\u65b9\u4fbf\u5ba2\u6237\u76f4\u63a5\u901a\u8fc7\u7f51\u7ebf\u548c\u5b89\u88c5\u5230\u673a\u7bb1\u6321\u677f\u7684ATX\u677f\u8fde\u63a5\u3002 5. \u5728\u6240\u6709\u8fde\u63a5\u7ebf\u8fde\u63a5\u597d\u540e,\u5bf9BliKVM\u8fdb\u884c\u4e0a\u7535\uff0c\u76f4\u5230\u663e\u793a\u5c4f\u51fa\u73b0\u753b\u9762\uff0c\u5373\u8bbe\u5907\u6b63\u5e38\u542f\u52a8\u3002 6. \u4ed4\u7ec6\u9605\u8bfb \u201c\u7b2c\u4e00\u6b65\u201d \u6307\u5357-\u5982\u4f55\u5728\u7f51\u7edc\u4e0a\u67e5\u627e\u8bbe\u5907\u3001\u5982\u4f55\u767b\u5f55\u3001\u66f4\u6539\u5bc6\u7801\u7b49\u7b49\u3002\u6309\u7167\u4e0a\u9762\u63cf\u8ff0\u7684\u6b65\u9aa4\u64cd\u4f5c\uff0c\u7136\u540e\u8fd4\u56de\u672c\u9875\u3002 \u7531\u4e8eBliKVM v1\u4e5f\u652f\u6301PiKVM OS\uff0c\u82e5\u4f60\u624b\u4e0a\u7684v1\u51fa\u5382OS\u4e3aPiKVM\uff0c\u5173\u4e8eweb\u4f7f\u7528\u8bf4\u660e\u8bf7 \u53c2\u8003\u6587\u6863 \u3002 7. \u5c1d\u8bd5\u4f7f\u7528 Web \u754c\u9762\u7ba1\u7406\u8ba1\u7b97\u673a\u7684 BliKVM\u3002 \u786e\u4fdd\u60a8\u53ef\u4ee5\u770b\u5230\u56fe\u50cf\u5e76\u4e14\u952e\u76d8\u548c\u9f20\u6807\u90fd\u6b63\u5e38\u5de5\u4f5c\u3002\u5982\u679c\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u8bf7\u67e5\u770b\u6211\u4eec\u7684 \u5e38\u89c1\u95ee\u9898 \uff08\u5b83\u975e\u5e38\u6709\u7528\uff09\u3002\u5982\u679c\u6ca1\u6709\u4efb\u4f55\u5e2e\u52a9\uff0c\u8bf7\u5728\u6211\u4eec\u7684 Discord\u804a\u5929\u5ba4 \u5bfb\u6c42\u652f\u6301\u3002 8. \u60a8\u53ef\u4ee5\u67e5\u770bwiki\u5176\u4ed6\u7684\u9875\u9762\uff0c\u63a2\u7d22BliKVM\u7684\u66f4\u591a\u529f\u80fd\uff0c\u795d\u60a8\u73a9\u7684\u5f00\u5fc3\uff01","title":"\u57fa\u7840\u914d\u7f6e"},{"location":"BLIKVM-CM4-guide/#wi-fi","text":"\u5982\u4f60\u7684CM4\u6709Wi-Fi\u529f\u80fd\uff0c\u62c6\u5f00v1\u7684\u91d1\u5c5e\u76d2\u5b50\uff0c\u8bf7\u5c06\u5305\u88f9\u4e2d\u7684Wi-Fi\u5929\u7ebf\uff0c\u5b89\u88c5\u5230CM4\u7684IPX\u63a5\u53e3\uff0c\u5373\u4e0b\u56fe\u4e2d\u7ea2\u6846\u7684\u63a5\u53e3\uff1b\u5176\u4e2d\u5916\u58f3\u5b89\u88c5\u5929\u7ebf\u4f4d\u7f6e\u4e3a\u63a5\u53e3\u5b9a\u4e49\u56fe\u4e2d\u768411\u5904\u3002","title":"Wi-Fi\u5929\u7ebf\u8fde\u63a5"},{"location":"BLIKVM-CM4-guide/#1080p60hz-hdmi","text":"\u5728V2.2\u7248\u672c\u4e2d\uff0c\u8fd9\u91cc\u6709\u4e00\u4e2aCSI\u901a\u9053\u5207\u6362\u5668\u3002\u786e\u8ba4\u5207\u6362\u5668\u57284\u901a\u9053\u4e00\u4fa7\u3002\u518d\u5176\u5b83\u7248\u672c\u4e2d\uff0c\u79fb\u9664\u4e86\u6b64\u5207\u6362\u5668\uff0c\u9ed8\u8ba44\u901a\u9053\u5168\u90e8\u4f7f\u80fd\u3002","title":"\u652f\u6301 1080p60hz HDMI\u8f93\u5165"},{"location":"BLIKVM-CM4-guide/#_4","text":"BLIKVM v1 \u4e0d\u542b CM4 \u5916\u58f3 1 PCB\u4e3b\u677f 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 OLED\u5c4f\u5e55 1 BLIKVM v1\u542b CM4102000 \u5916\u58f3 1 PCB\u4e3b\u677f 1 CM4102000 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 OLED\u5c4f\u5e55 1 WiFi\u5929\u7ebf 1 BLIKVM v1 \u542b CM4002000 \u5916\u58f3 1 PCB\u4e3b\u677f 1 CM4002000 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 WiFi\u5929\u7ebf 1","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"BLIKVM-CM4-guide/#_5","text":"v1\u6dd8\u5b9d\u5730\u5740","title":"\u8d2d\u4e70\u94fe\u63a5"},{"location":"BLIKVM-HAT-guide/","text":"BliKVM Hat \u4f7f\u7528\u8bf4\u660e \u4ecb\u7ecd BliKVM Hat 360\u5ea6 \u89c6\u9891 BliKVM Hat\u7248\u672c\u662f\u57fa\u4e8e\u6811\u8393\u6d3e4B\u5236\u4f5c\u7684\u4e00\u6b3e\u786c\u4ef6\uff0c\u7528\u4e8eKVM Over IP\u3002Hat\u5173\u952e\u529f\u80fd\u5305\u62ecHDMI\u89c6\u9891\u6355\u83b7\u3001ATX\u63a7\u5236\u3001PoE\u4f9b\u7535\u3001OLED\u5c4f\u5e55\u663e\u793a\u3001RTC\u65f6\u949f\u3002 Hat\u914d\u6709\u91d1\u5c5e\u5916\u58f3\uff0c\u7528\u4e8e\u4fdd\u62a4\u548c\u6563\u70ed\u3002Hat\u53ef\u4ee5\u88ab\u5b89\u88c5\u52301U\u7684\u673a\u67b6\u3002\u540c\u65f6\u652f\u6301blikvm\u955c\u50cf\u548cpikvm\u955c\u50cf\u3002 \u5b89\u88c5\u8981\u6c42 \u5982\u679c\u4f60\u8d2d\u4e70\u7684\u53ea\u662f\u4e00\u4e2aHat\uff0c\u4f60\u8fd8\u9700\u8981\u4e0b\u9762\u8bbe\u5907 \u6811\u8393\u6d3e4B\uff0c1GB RAM\u6216\u8005\u66f4\u591a MicroSD card (\u63a8\u8350\u6700\u5c1116Gb, class 10). HDMI \u7ebf\u7f06. \u7f51\u7ebf (\u7528\u4e8eHat\u548cATX\u7684\u8fde\u63a5). \u7535\u6e90\u9002\u914d\u5668\u548c\u7ebf\u7f06(5.1V 3A USB-C). \u529f\u80fd \u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@50Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE \u4f9b\u7535 \u652f\u6301\u4e32\u53e3\u7ec8\u7aef OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) PWM\u98ce\u6247 \u57fa\u7840\u8bbe\u7f6e 1. \u70e7\u5f55\u955c\u50cf 2.\u7ec4\u88c5Hat \u53c2\u8003\u4e0b\u9762\u7684\u89c6\u9891\u8bf4\u660e\u6216\u8005\u53c2\u8003 \u56fe\u6587\u8bf4\u660e : Hat \u89c6\u9891\u5b89\u88c5\u5bfc\u89c8: \u624b\u628a\u624b\u6559\u4f60\u5982\u4f55\u7ec4\u88c5Hat\u5230\u6811\u8393\u6d3e\u4e0a 3. \u5b89\u88c5 ATX \u6a21\u5757 ATX\u6a21\u5757\u914d\u6709\u4e00\u4e2a\u5168\u9ad8\u6216\u8005\u534a\u9ad8\u7684PCIe\u6321\u677f\uff0c\u4f60\u53ef\u4ee5\u6839\u636e\u9700\u6c42\u9009\u62e9\u5b89\u88c5 \u4f7f\u7528\u675c\u90a6\u7ebf\u8fde\u63a5ATX\u6a21\u5757\u548c\u673a\u7bb1\u91cc\u7684\u4e3b\u677f\uff0cATX\u6a21\u5757\u4e0a\u90fd\u6709\u6e05\u6670\u7684\u5f15\u811a\u5b9a\u4e49\u65b9\u4fbf\u4f60\u8fde\u63a5 \u5c06ATX\u6a21\u5757\u5b89\u88c5\u5230\u673a\u7bb1\u5916\u58f3\u4e0a \u4f7f\u7528RJ45\u7684\u7f51\u7ebf\u8fde\u63a5ATX\u548cHat 4. \u8fde\u63a5HDMI\u7ebf\u7f06 \u4f7f\u7528HDMI\u7ebf\u7f06\uff0c\u5c06\u88ab\u63a7\u7535\u8111\u7684HDMI\u548cHat\u7684HDMI IN\u7aef\u53e3\u8fde\u63a5\u3002HDMI\u6a21\u62df\u5668\u4e0d\u662f\u5fc5\u987b\u4f7f\u7528\u7684\uff0c\u5f53\u4f60\u7684\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8f93\u51fa\u753b\u9762\u65f6\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528HDMI\u6a21\u62df\u5668\u6765\u6821\u6b63\u7535\u8111\u7684HDMI\u8f93\u51fa 5. \u5b89\u88c5USB\u7ebf\u7f06 \u8bf7\u6ce8\u610f\u8fd9\u91cc\u4f7f\u7528USB\u5206\u7535\u677f\u4e0d\u662f\u5fc5\u987b\u7684\uff0c\u5982\u679c\u4f60\u4f7f\u7528PoE\u4f9b\u7535\u4e0d\u9700\u8981\u4f7f\u7528\u6b64\u6a21\u5757\uff0c\u5982\u679c\u4f60\u9700\u8981\u4f7f\u7528USB\u4f9b\u7535\u5219\u9700\u8981\u3002\u901a\u8fc7USB-C\u7ebf\u8fde\u63a5\u6811\u8393\u6d3e4B\u7684TYPE-C\u53e3\u5230\u5206\u7535\u677f\u7684RPI4\u7aef\u53e3 \u8fde\u63a5\u5206\u7535\u677f\u4e0a\u7684USB\u7aef\u53e3\u5230\u88ab\u63a7\u7535\u8111 \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u8bf7\u6ce8\u610f\u4e0d\u9700\u8981\u5728\u4f7f\u7528USB\u4f9b\u7535\u8bbe\u5907\u3002\u5f53\u4e0d\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u63a8\u8350\u4f7f\u75285V/3A\u7684\u7535\u6e90\u9002\u914d\u5668\u5230\u5206\u7535\u677f\u7684PWR\u7aef\u53e3 6. \u6d4b\u8bd5 \u56fe\u4e2d\u901a\u8fc7PoE\u4f9b\u7535\uff0cHat\u901a\u8fc7\u7f51\u7ebf\u8fde\u63a5\u5230\u7f51\u7edc\u4e2d OLED\u5c4f\u5e55\u5c06\u4f1a\u6b63\u5e38\u663e\u793a\u8bbe\u5907\u7684\u5de5\u4f5c\u72b6\u6001\uff0c\u5305\u62ec\u8bbe\u5907\u7684IP\u5730\u5740 \u6253\u5f00\u6d4f\u89c8\u5668\uff0c\u8f93\u5165\u8bbe\u5907\u7684IP\u5730\u5740\uff0c\u5373\u53ef\u6253\u5f00\u63a7\u5236\u7684WEB\u754c\u9762\uff0c\u73b0\u5728\u53bb\u4f7f\u7528\u5b83\u5427\uff01 \u6027\u80fd\u53c2\u6570 HDMI \u8f93\u5165 \u4f7f\u7528Toshiba TC358743\u4e3aHDMI\u8f6c\u6362\u7684\u4e3b\u82af\u7247\uff0c\u540c\u65f6\u652f\u6301\u89c6\u9891\u548c\u58f0\u97f3\u7684\u91c7\u96c6\uff0c\u652f\u6301\u89c6\u9891\u6700\u9ad8\u8f93\u5165\u4e3a1080P50Hz.\u89e3\u51b3\u4e86HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898\u3002 CN-ATX CN-ATX\u63a5\u53e3\u901a\u8fc7\u7f51\u7ebf\u8fde\u63a5ATX\u6a21\u5757\uff0c\u7528\u6765\u63a7\u5236\u88ab\u63a7\u7535\u8111\u7684\u5f00\u673a\u3001\u5173\u673a\u3001\u548c\u91cd\u542f\u64cd\u4f5c\u3002 \u663e\u793a\u5c4f \u914d\u6709\u767d\u8272\u7684\u663e\u793a\u5c4f\uff0c\u5206\u8fa8\u7387\u4e3a128x32\uff0c\u4f7f\u7528\u82af\u7247\u4e3aSSD1306\u3002\u663e\u793a\u5c4f\u4f1a\u663e\u793a\u5982\u6e29\u5ea6\u3001IP\u5730\u5740\u7b49\u6811\u8393\u6d3e\u7684\u4fe1\u606f\u3002 PoE \u6807\u51c6: IEEE 802.3af PoE \u8f93\u5165\u7535\u538b: 37-57 V DC \u8f93\u51fa\u7535\u538b: 5 V DC/2.4 A \u4f7f\u7528PoE\u6a21\u5757\u4f9b\u7535\uff0c\u9700\u8981\u5c06Hat\u4e0a\u7684PoE\u7684\u5f15\u811a\u4f7f\u7528\u8df3\u7ebf\u5e3d\u77ed\u63a5\u3002 \u98ce\u6247 \u98ce\u6247\u9ed8\u8ba4\u4f7f\u7528\u6811\u8393\u6d3e\u4e0a\u7684GPIO12\u63a7\u5236\u3002 RTC\u65f6\u949f RTC\u65f6\u949f\u4e3b\u82af\u7247\u4e3aPCF8563\uff0c\u901a\u8fc7I2C\u548c\u6811\u8393\u6d3e\u8fde\u63a5\u3002\u542f\u7528RTC\u65f6\u949f\u5de5\u4f5c\u7684\u7ebd\u6263\u7535\u6c60\u5b89\u88c5\u4f4d\u7f6e\u5728HDMI-IN\u6a21\u5757\u7684\u4e0b\u9762\u3002 \u914d\u4ef6 ATX\u6a21\u5757 ATX\u6a21\u5757\u901a\u8fc7\u675c\u90a6\u7ebf\u548c\u7535\u8111\u7684\u4e3b\u677f\u8fde\u63a5\u3002ATX\u6a21\u5757\u914d\u6709\u5168\u9ad8\u548c\u534a\u9ad8\u7684PCIe\u6321\u677f\u3002 USB/PWR \u5206\u7535\u677f RPI4\u7aef\u53e3\u7528\u4e8e\u8fde\u63a5\u5230\u6811\u8393\u6d3e4B. USB\u7aef\u53e3\u7528\u4e8e\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111. \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u4e0d\u9700\u8981\u4f7f\u7528\u5206\u7535\u677f. HDMI\u6a21\u62df\u5668 \u5982\u679c\u88ab\u63a7\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8f93\u51fa\u753b\u9762\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528\u6b64\u6a21\u5757\u6765\u89e3\u51b3\u3002\u5c06\u6b64\u6a21\u5757\u8fde\u63a5\u5230Hat\u4e0a\u540e\uff0c\u518d\u901a\u8fc7HDMI\u7ebf\u7f06\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111\u3002 \u91d1\u5c5e\u5916\u58f3 \u91d1\u5c5e\u5916\u58f3\u53ef\u4ee5\u4fdd\u62a4Hat\u548c\u7528\u4e8e\u6563\u70ed.\u5916\u58f3\u4e0a\u6bcf\u4e2a\u7aef\u53e3\u6709\u6e05\u6670\u7684\u4e1d\u5370\u6765\u8868\u793a\u6b64\u7aef\u53e3\u7528\u9014\u3002\u6b64\u5916\u58f3\u53ef\u4ee5\u65b9\u4fbf\u7684\u5b89\u88c5\u57281U\u7684\u673a\u67b6\u4e0a\u3002 List Product List BliKVM Hat \u6a21\u5757 1 ATX \u6a21\u5757 1 USB/PWR \u5206\u7535\u677f 1 HDMI\u6a21\u62df\u5668 1 \u91d1\u5c5e\u5916\u58f3 1 32G TF \u5361 1 USB Type-C \u8f6c USB Type-C \u7ebf\u7f06 30cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 \u5341\u5b57\u6273\u624b\u5957\u7b52 1 \u7528\u6237\u9700\u8981\u51c6\u5907\u8bbe\u5907\u7684\u6e05\u5355 \u6811\u8393\u6d3e4B 1 RJ45 \u7f51\u7ebf 2 USB Type-A \u8f6c USB Type-C \u7ebf\u7f06 2 HDMI \u7ebf\u7f06 1 PoE\u4f9b\u7535\u8bbe\u5907 or 5V/3A USB \u7535\u6e90\u9002\u914d\u5668 1 CR1220\u7ebd\u6263\u7535\u6c60 1 \u8d2d\u4e70\u94fe\u63a5 v3\u6dd8\u5b9d\u5730\u5740","title":"BliKVM v3 HAT\u5bfc\u89c8"},{"location":"BLIKVM-HAT-guide/#blikvm-hat","text":"","title":"BliKVM Hat \u4f7f\u7528\u8bf4\u660e"},{"location":"BLIKVM-HAT-guide/#_1","text":"BliKVM Hat 360\u5ea6 \u89c6\u9891 BliKVM Hat\u7248\u672c\u662f\u57fa\u4e8e\u6811\u8393\u6d3e4B\u5236\u4f5c\u7684\u4e00\u6b3e\u786c\u4ef6\uff0c\u7528\u4e8eKVM Over IP\u3002Hat\u5173\u952e\u529f\u80fd\u5305\u62ecHDMI\u89c6\u9891\u6355\u83b7\u3001ATX\u63a7\u5236\u3001PoE\u4f9b\u7535\u3001OLED\u5c4f\u5e55\u663e\u793a\u3001RTC\u65f6\u949f\u3002 Hat\u914d\u6709\u91d1\u5c5e\u5916\u58f3\uff0c\u7528\u4e8e\u4fdd\u62a4\u548c\u6563\u70ed\u3002Hat\u53ef\u4ee5\u88ab\u5b89\u88c5\u52301U\u7684\u673a\u67b6\u3002\u540c\u65f6\u652f\u6301blikvm\u955c\u50cf\u548cpikvm\u955c\u50cf\u3002","title":"\u4ecb\u7ecd"},{"location":"BLIKVM-HAT-guide/#_2","text":"\u5982\u679c\u4f60\u8d2d\u4e70\u7684\u53ea\u662f\u4e00\u4e2aHat\uff0c\u4f60\u8fd8\u9700\u8981\u4e0b\u9762\u8bbe\u5907 \u6811\u8393\u6d3e4B\uff0c1GB RAM\u6216\u8005\u66f4\u591a MicroSD card (\u63a8\u8350\u6700\u5c1116Gb, class 10). HDMI \u7ebf\u7f06. \u7f51\u7ebf (\u7528\u4e8eHat\u548cATX\u7684\u8fde\u63a5). \u7535\u6e90\u9002\u914d\u5668\u548c\u7ebf\u7f06(5.1V 3A USB-C).","title":"\u5b89\u88c5\u8981\u6c42"},{"location":"BLIKVM-HAT-guide/#_3","text":"\u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@50Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE \u4f9b\u7535 \u652f\u6301\u4e32\u53e3\u7ec8\u7aef OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) PWM\u98ce\u6247","title":"\u529f\u80fd"},{"location":"BLIKVM-HAT-guide/#_4","text":"1. \u70e7\u5f55\u955c\u50cf 2.\u7ec4\u88c5Hat \u53c2\u8003\u4e0b\u9762\u7684\u89c6\u9891\u8bf4\u660e\u6216\u8005\u53c2\u8003 \u56fe\u6587\u8bf4\u660e : Hat \u89c6\u9891\u5b89\u88c5\u5bfc\u89c8: \u624b\u628a\u624b\u6559\u4f60\u5982\u4f55\u7ec4\u88c5Hat\u5230\u6811\u8393\u6d3e\u4e0a 3. \u5b89\u88c5 ATX \u6a21\u5757 ATX\u6a21\u5757\u914d\u6709\u4e00\u4e2a\u5168\u9ad8\u6216\u8005\u534a\u9ad8\u7684PCIe\u6321\u677f\uff0c\u4f60\u53ef\u4ee5\u6839\u636e\u9700\u6c42\u9009\u62e9\u5b89\u88c5 \u4f7f\u7528\u675c\u90a6\u7ebf\u8fde\u63a5ATX\u6a21\u5757\u548c\u673a\u7bb1\u91cc\u7684\u4e3b\u677f\uff0cATX\u6a21\u5757\u4e0a\u90fd\u6709\u6e05\u6670\u7684\u5f15\u811a\u5b9a\u4e49\u65b9\u4fbf\u4f60\u8fde\u63a5 \u5c06ATX\u6a21\u5757\u5b89\u88c5\u5230\u673a\u7bb1\u5916\u58f3\u4e0a \u4f7f\u7528RJ45\u7684\u7f51\u7ebf\u8fde\u63a5ATX\u548cHat 4. \u8fde\u63a5HDMI\u7ebf\u7f06 \u4f7f\u7528HDMI\u7ebf\u7f06\uff0c\u5c06\u88ab\u63a7\u7535\u8111\u7684HDMI\u548cHat\u7684HDMI IN\u7aef\u53e3\u8fde\u63a5\u3002HDMI\u6a21\u62df\u5668\u4e0d\u662f\u5fc5\u987b\u4f7f\u7528\u7684\uff0c\u5f53\u4f60\u7684\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8f93\u51fa\u753b\u9762\u65f6\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528HDMI\u6a21\u62df\u5668\u6765\u6821\u6b63\u7535\u8111\u7684HDMI\u8f93\u51fa 5. \u5b89\u88c5USB\u7ebf\u7f06 \u8bf7\u6ce8\u610f\u8fd9\u91cc\u4f7f\u7528USB\u5206\u7535\u677f\u4e0d\u662f\u5fc5\u987b\u7684\uff0c\u5982\u679c\u4f60\u4f7f\u7528PoE\u4f9b\u7535\u4e0d\u9700\u8981\u4f7f\u7528\u6b64\u6a21\u5757\uff0c\u5982\u679c\u4f60\u9700\u8981\u4f7f\u7528USB\u4f9b\u7535\u5219\u9700\u8981\u3002\u901a\u8fc7USB-C\u7ebf\u8fde\u63a5\u6811\u8393\u6d3e4B\u7684TYPE-C\u53e3\u5230\u5206\u7535\u677f\u7684RPI4\u7aef\u53e3 \u8fde\u63a5\u5206\u7535\u677f\u4e0a\u7684USB\u7aef\u53e3\u5230\u88ab\u63a7\u7535\u8111 \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u8bf7\u6ce8\u610f\u4e0d\u9700\u8981\u5728\u4f7f\u7528USB\u4f9b\u7535\u8bbe\u5907\u3002\u5f53\u4e0d\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u63a8\u8350\u4f7f\u75285V/3A\u7684\u7535\u6e90\u9002\u914d\u5668\u5230\u5206\u7535\u677f\u7684PWR\u7aef\u53e3 6. \u6d4b\u8bd5 \u56fe\u4e2d\u901a\u8fc7PoE\u4f9b\u7535\uff0cHat\u901a\u8fc7\u7f51\u7ebf\u8fde\u63a5\u5230\u7f51\u7edc\u4e2d OLED\u5c4f\u5e55\u5c06\u4f1a\u6b63\u5e38\u663e\u793a\u8bbe\u5907\u7684\u5de5\u4f5c\u72b6\u6001\uff0c\u5305\u62ec\u8bbe\u5907\u7684IP\u5730\u5740 \u6253\u5f00\u6d4f\u89c8\u5668\uff0c\u8f93\u5165\u8bbe\u5907\u7684IP\u5730\u5740\uff0c\u5373\u53ef\u6253\u5f00\u63a7\u5236\u7684WEB\u754c\u9762\uff0c\u73b0\u5728\u53bb\u4f7f\u7528\u5b83\u5427\uff01","title":"\u57fa\u7840\u8bbe\u7f6e"},{"location":"BLIKVM-HAT-guide/#_5","text":"HDMI \u8f93\u5165 \u4f7f\u7528Toshiba TC358743\u4e3aHDMI\u8f6c\u6362\u7684\u4e3b\u82af\u7247\uff0c\u540c\u65f6\u652f\u6301\u89c6\u9891\u548c\u58f0\u97f3\u7684\u91c7\u96c6\uff0c\u652f\u6301\u89c6\u9891\u6700\u9ad8\u8f93\u5165\u4e3a1080P50Hz.\u89e3\u51b3\u4e86HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898\u3002 CN-ATX CN-ATX\u63a5\u53e3\u901a\u8fc7\u7f51\u7ebf\u8fde\u63a5ATX\u6a21\u5757\uff0c\u7528\u6765\u63a7\u5236\u88ab\u63a7\u7535\u8111\u7684\u5f00\u673a\u3001\u5173\u673a\u3001\u548c\u91cd\u542f\u64cd\u4f5c\u3002 \u663e\u793a\u5c4f \u914d\u6709\u767d\u8272\u7684\u663e\u793a\u5c4f\uff0c\u5206\u8fa8\u7387\u4e3a128x32\uff0c\u4f7f\u7528\u82af\u7247\u4e3aSSD1306\u3002\u663e\u793a\u5c4f\u4f1a\u663e\u793a\u5982\u6e29\u5ea6\u3001IP\u5730\u5740\u7b49\u6811\u8393\u6d3e\u7684\u4fe1\u606f\u3002 PoE \u6807\u51c6: IEEE 802.3af PoE \u8f93\u5165\u7535\u538b: 37-57 V DC \u8f93\u51fa\u7535\u538b: 5 V DC/2.4 A \u4f7f\u7528PoE\u6a21\u5757\u4f9b\u7535\uff0c\u9700\u8981\u5c06Hat\u4e0a\u7684PoE\u7684\u5f15\u811a\u4f7f\u7528\u8df3\u7ebf\u5e3d\u77ed\u63a5\u3002 \u98ce\u6247 \u98ce\u6247\u9ed8\u8ba4\u4f7f\u7528\u6811\u8393\u6d3e\u4e0a\u7684GPIO12\u63a7\u5236\u3002 RTC\u65f6\u949f RTC\u65f6\u949f\u4e3b\u82af\u7247\u4e3aPCF8563\uff0c\u901a\u8fc7I2C\u548c\u6811\u8393\u6d3e\u8fde\u63a5\u3002\u542f\u7528RTC\u65f6\u949f\u5de5\u4f5c\u7684\u7ebd\u6263\u7535\u6c60\u5b89\u88c5\u4f4d\u7f6e\u5728HDMI-IN\u6a21\u5757\u7684\u4e0b\u9762\u3002","title":"\u6027\u80fd\u53c2\u6570"},{"location":"BLIKVM-HAT-guide/#_6","text":"","title":"\u914d\u4ef6"},{"location":"BLIKVM-HAT-guide/#atx","text":"ATX\u6a21\u5757\u901a\u8fc7\u675c\u90a6\u7ebf\u548c\u7535\u8111\u7684\u4e3b\u677f\u8fde\u63a5\u3002ATX\u6a21\u5757\u914d\u6709\u5168\u9ad8\u548c\u534a\u9ad8\u7684PCIe\u6321\u677f\u3002","title":"ATX\u6a21\u5757"},{"location":"BLIKVM-HAT-guide/#usbpwr","text":"RPI4\u7aef\u53e3\u7528\u4e8e\u8fde\u63a5\u5230\u6811\u8393\u6d3e4B. USB\u7aef\u53e3\u7528\u4e8e\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111. \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u4e0d\u9700\u8981\u4f7f\u7528\u5206\u7535\u677f.","title":"USB/PWR \u5206\u7535\u677f"},{"location":"BLIKVM-HAT-guide/#hdmi","text":"\u5982\u679c\u88ab\u63a7\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8f93\u51fa\u753b\u9762\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528\u6b64\u6a21\u5757\u6765\u89e3\u51b3\u3002\u5c06\u6b64\u6a21\u5757\u8fde\u63a5\u5230Hat\u4e0a\u540e\uff0c\u518d\u901a\u8fc7HDMI\u7ebf\u7f06\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111\u3002","title":"HDMI\u6a21\u62df\u5668"},{"location":"BLIKVM-HAT-guide/#_7","text":"\u91d1\u5c5e\u5916\u58f3\u53ef\u4ee5\u4fdd\u62a4Hat\u548c\u7528\u4e8e\u6563\u70ed.\u5916\u58f3\u4e0a\u6bcf\u4e2a\u7aef\u53e3\u6709\u6e05\u6670\u7684\u4e1d\u5370\u6765\u8868\u793a\u6b64\u7aef\u53e3\u7528\u9014\u3002\u6b64\u5916\u58f3\u53ef\u4ee5\u65b9\u4fbf\u7684\u5b89\u88c5\u57281U\u7684\u673a\u67b6\u4e0a\u3002","title":"\u91d1\u5c5e\u5916\u58f3"},{"location":"BLIKVM-HAT-guide/#list","text":"","title":"List"},{"location":"BLIKVM-HAT-guide/#product-list","text":"BliKVM Hat \u6a21\u5757 1 ATX \u6a21\u5757 1 USB/PWR \u5206\u7535\u677f 1 HDMI\u6a21\u62df\u5668 1 \u91d1\u5c5e\u5916\u58f3 1 32G TF \u5361 1 USB Type-C \u8f6c USB Type-C \u7ebf\u7f06 30cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 \u5341\u5b57\u6273\u624b\u5957\u7b52 1","title":"Product List"},{"location":"BLIKVM-HAT-guide/#_8","text":"\u6811\u8393\u6d3e4B 1 RJ45 \u7f51\u7ebf 2 USB Type-A \u8f6c USB Type-C \u7ebf\u7f06 2 HDMI \u7ebf\u7f06 1 PoE\u4f9b\u7535\u8bbe\u5907 or 5V/3A USB \u7535\u6e90\u9002\u914d\u5668 1 CR1220\u7ebd\u6263\u7535\u6c60 1","title":"\u7528\u6237\u9700\u8981\u51c6\u5907\u8bbe\u5907\u7684\u6e05\u5355"},{"location":"BLIKVM-HAT-guide/#_9","text":"v3\u6dd8\u5b9d\u5730\u5740","title":"\u8d2d\u4e70\u94fe\u63a5"},{"location":"BLIKVM-PCIE-guide-zh/","text":"BLIKVM PCIe \u4ecb\u7ecd BLIKVM PCIe\u662f\u4e00\u6b3e\u57fa\u4e8e\u6811\u8393\u6d3eCM4\u7684IPKVM\u6269\u5c55\u5361\uff0c\u53ef\u4ee5\u5b89\u88c5\u5230PC\u6216\u8005\u670d\u52a1\u5668\u7684PCIe\u63d2\u69fd\uff0c\u5b8c\u7f8e\u8fd0\u884cPiKVM\u9879\u76ee\u3002\u4e3b\u8981\u529f\u80fd\u6709\uff1aHDMI\u89c6\u9891\u91c7\u96c6\uff0c\u952e\u76d8\u9f20\u6807\u63a7\u5236\uff0cATX\u5f00\u5173\u673a\u63a7\u5236\uff0cPoE\u4f9b\u7535\uff0cOLED\u5c4f\u5e55\u663e\u793a\uff0c \u4e32\u53e3\u7ec8\u7aef\u8c03\u8bd5\u548cRTC\u65f6\u949f\u529f\u80fd\u3002\u6b64PCIe\u5361\u914d\u6709\u5168\u9ad8\u548c\u534a\u9ad8\u7684\u6321\u677f\u3002 BLIKVM PCIe\u7248\u672c\u652f\u6301blikvm\u548cpikvm\u7684\u7cfb\u7edf\u955c\u50cf\u3002 \u5b89\u88c5\u8981\u6c42 \u4f60\u9700\u8981\u4e0b\u9762\u7684\u8bbe\u5907 \u6811\u8393\u6d3eCM4(\u5982\u679c\u4f60\u53ea\u8ba2\u8d2d\u4e86PCIe\u5361). PoE\u4f9b\u7535\u8bbe\u5907\u62165V/3A USB\u4f9b\u7535\u8bbe\u5907. CR1220 \u7ebd\u6263\u7535\u6c60. \u529f\u80fd \u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@60Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE \u4f9b\u7535 \u652f\u6301\u4e32\u53e3\u7ec8\u7aef \u652f\u6301 WiFi \uff08\u53ef\u9009\uff09 OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) PWM\u98ce\u6247 \u5feb\u901f\u5b89\u88c5\u8bf4\u660e 1. \u5982\u679c\u4f60\u8d2d\u4e70\u7684\u662f\u9700\u8981\u81ea\u5df1\u7ec4\u88c5\u7684\u7248\u672c\uff0c\u70e7\u5f55\u7cfb\u7edf\u955c\u50cf\u53c2\u8003\u8bf7\u70b9\u51fb\u6b64\u5904 2.\u7ec4\u88c5 BLIKVM \u53c2\u8003\u7684 \u8bf4\u660e\u6587\u6863 Geerling\u7684\u6d4b\u8bd5\u89c6\u9891 Craft Computing: Never Pay For IPMI Again - BliKVM Review \u4ea7\u54c1\u7279\u6027 \u786c\u4ef6\u63a5\u53e3\u6e05\u5355 1 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 2 USB-PC \u7aef\u53e3 1 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 2 USB-PC \u7aef\u53e3 3 \u4f9b\u7535\u53e3 5V 3A 4 RJ45 100M \u7f51\u53e3 & PoE 5 ATX\u63a7\u5236\u7aef\u53e3 6 OLED \u663e\u793a\u5c4f\u63a5\u53e3 7 PWM \u98ce\u6247 8 BOOT 9 RTC\u65f6\u949f 10 \u4e32\u884c\u7ec8\u7aef\u7aef\u53e3 11 USB-PC\u7aef\u53e3 HDMI IN \u4f7f\u7528\u4e1c\u829d\u7684TC358743\u4f5c\u4e3aHDMI\u7684\u6865\u63a5\u82af\u7247\uff0c\u540c\u65f6\u652f\u6301\u89c6\u9891\u548c\u97f3\u9891\u91c7\u96c6\uff0c\u652f\u6301\u89c6\u9891\u8f93\u5165\u6700\u9ad8\u5206\u8fa8\u7387\u4e3a1080P60Hz\u3002 USB-PC BLIKVM PCIe\u5361\u63d0\u4f9b\u4e24\u4e2ausb\u63a5\u53e3\uff0c\u4e00\u4e2a\u662fPC-IN\uff08type c\u63a5\u53e3\uff09\uff0c\u53e6\u4e00\u4e2a\u662fUSB-PC2\uff08\u6392\u9488\u63a5\u53e3\uff09\u3002\u8fd9\u4e24\u4e2a\u63a5\u53e3\u7684\u4f5c\u7528\u90fd\u662f\u4e3a\u4e86\u8fde\u63a5\u88ab\u63a7\u7535\u8111\u7684usb\uff0c\u7528\u4e8e\u63a7\u5236\u9f20\u6807\u548c\u952e\u76d8\u3002\u540c\u65f6\u4e24\u4e2a\u63a5\u53e3\u53ea\u80fd\u4f7f\u7528\u4e00\u4e2a\uff0c\u8bbe\u8ba1\u4e24\u4e2a\u63a5\u53e3\u7684\u76ee\u7684\u662f\uff0c\u5f53\u7528\u6237pc\u4e3b\u673a\u5185\u6709\u6392\u9488\u7684usb\u63a5\u53e3\u65f6\uff0c\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528usb-pc2\uff0c\u8fd9\u6837\u63a5\u7ebf\u4f1a\u66f4\u52a0\u7b80\u6d01\u3002 POWER-IN \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u6539\u63a5\u53e3\u4e0d\u9700\u8981\u88ab\u4f7f\u7528\u3002\u5f53\u4e0d\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u8fde\u63a5\u8be5\u63a5\u53e3\u7684\u7535\u6e90\u9002\u914d\u5668\uff0c\u63a8\u8350\u4e3a5V/3A\u3002 \u4ee5\u592a\u7f51\u53e3-PoE Gigabit Ethernet port \u6807\u51c6: IEEE 802.3af PoE \u8f93\u5165\u7535\u538b: 37-57 V DC \u8f93\u51fa\u7535\u538b: 5 V DC/2.4 A ATX\u63a5\u53e3 \u6539\u63a5\u53e3\u901a\u8fc7\u675c\u90a6\u7ebf\u94fe\u63a5\u88ab\u63a7\u8ba1\u7b97\u673a\u4e3b\u677f\u7684\u7535\u6e90\u63a7\u5236\u63a5\u53e3\u3002ATX\u529f\u80fd\u53ef\u4ee5\u5f00\u542f\u6216\u8005\u91cd\u542f\u88ab\u63a7\u8ba1\u7b97\u673a\u3002 PCIe\u677f\u5b50\u4e0a\u7684BTN\u4e1d\u5370\u4e3abutton\u7684\u7f29\u5199\u3002 \u6839\u636e\u7535\u8111\u4e3b\u677f\u8bf4\u660e\uff0c\u9996\u5148\u627e\u5230\u4e3b\u677f\u4e0aATX\u529f\u80fd\u76f8\u5173\u5f15\u811a\u4f4d\u7f6e\uff0c\u62d4\u4e0b\u4e3b\u677f\u5df2\u7ecf\u63a5\u597d\u7684ATX\u7ebf\uff0c\u62d4\u4e0b\u540e\u7535\u8111\u7684\u7535\u6e90\u6309\u94ae\u5c06\u5931\u53bb\u4f5c\u7528\u3002PCIe\u4e3b\u677f\u5171\u6709\u4e24\u63928PIN\u5f15\u811a\uff0c\u4e24\u6392\u5f15\u811a\u529f\u80fd\u5b8c\u5168\u76f8\u540c\u4f7f\u7528\u65f6\u65e0\u9700\u533a\u5206\u3002\u5176\u4e2d\u4e00\u6392\u5f15\u811a\u7528\u4e8eKVM\u63a7\u5236ATX\u76f8\u5173\u529f\u80fd\uff0c\u53e6\u4e00\u6392\u5f15\u811a\u63a5\u4e3b\u677f\u4e0a\u62d4\u4e0b\u6765\u7684ATX\u675c\u90a6\u5934\uff0c\u4fdd\u6301\u539f\u6709\u673a\u7bb1\u7535\u6e90\u6309\u94ae\u529f\u80fd\u3002\u6839\u636e\u4e3b\u677f\u548cPCIe\u4e0a\u7684\u5177\u4f53\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u6bcf\u6839\u7ebf\u7684\u8fde\u63a5\uff0c\u8fde\u63a5\u5173\u7cfb\u53ef\u4ee5\u53c2\u8003\u4e0b\u56fe\uff1a OLED\u663e\u793a\u5c4f \u663e\u793a\u5c4f\u5206\u8fa8\u7387\u4e3a128x64\uff0c\u4e3b\u82af\u7247\u4e3aSSD1306\u3002\u901a\u8fc7\u6539\u5c4f\u5e55\u53ef\u4ee5\u5c55\u793aBLIKVM\u7684CPU\u7684\u6e29\u5ea6\u3001IP\u5730\u5740\u3001\u542f\u52a8\u65f6\u95f4\u7b49\u4fe1\u606f\u3002 \u98ce\u6247 \u98ce\u6247\u9ed8\u8ba4\u8bbe\u7f6e\u5de5\u4f5c\u6e29\u5ea6\u4e3a60\u6444\u6c0f\u5ea6\uff0c\u4e0e\u6811\u8393\u6d3eCM4\u7684\u901a\u8fc7GPIO12\u94fe\u63a5\u3002 BOOT Fit jumper to disable eMMC Boot \u901a\u8fc7\u8be5\u77ed\u63a5\u53e3\u53ef\u4ee5\u4f7f\u7528PCIe\u5361\u5bf9eMMC\u7248\u672c\u7684CM4\u8fdb\u884c\u955c\u50cf\u70e7\u5f55\u3002 \u5b9e\u65f6\u65f6\u949f (RTC) \u65f6\u949f\u82af\u7247\u4e3aPCF8563\uff0c\u4e0e\u6811\u8393\u6d3eCM4\u7684\u901a\u4fe1\u65b9\u5f0f\u4e3aI2C\u3002RTC\u5de5\u4f5c\u9700\u8981\u518d\u5b89\u88c5CR1220\u7535\u6c60\u540e\u3002 \u4e32\u53e3 \u53ef\u4ee5\u901a\u8fc7\u6539\u4e32\u53e3\u767b\u9646\u8bbe\u5907\u8fdb\u884c\u8c03\u8bd5\uff0c\u4e00\u822c\u5728\u5728\u7f51\u7edc\u94fe\u63a5\u6545\u969c\u7b49\u60c5\u51b5\u4e0b\u4f7f\u7528\u3002 \u6811\u8393\u6d3eCM4\u7684\u4e32\u53e3. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. \u5c06USB\u8f6cTTL\u6a21\u5757\u7684\u675c\u90a6\u5934\u8fde\u63a5\u5230PCIe\u7684 GTR \u53e3\uff0cUSB\u8f6cttl\u6a21\u5757\u4e0e GTR \u63a5\u7ebf\u5173\u7cfb\u4e3a\uff08\u9ed1\u8272\u7ebf-G, \u767d\u8272\u7ebf-T, \u7eff\u8272\u7ebf-R\uff09;\u5177\u4f53\u65b9\u6cd5\u53ef\u53c2\u8003 \u6b64\u6587\u6863 \u914d\u4ef6 HDMI EDID\u6a21\u62df\u5668 \u5982\u679c\u88ab\u63a7\u8ba1\u7b97\u673a\u4e0d\u80fd\u6b63\u786e\u7684\u8f93\u51faHDMI\u56fe\u50cf\uff0c\u53ef\u4ee5\u4f7f\u7528\u6b64\u8bbe\u5907\u8fdb\u884c\u6d4b\u8bd5\u3002\u5b89\u88c5\u5728\u88ab\u63a7\u8bbe\u5907\u7684HDMI\u8f93\u51fa\u63a5\u53e3\u4e0a\uff0c\u7136\u540e\u518d\u901a\u8fc7HDMI\u7ebf\u8fde\u63a5\u5230BLIKVM\u3002 VGA\u8f6cHDMI\u6a21\u5757 \u5f53\u88ab\u63a7\u8ba1\u7b97\u673a\u4e0d\u662fHDMI\u8f93\u51fa\u63a5\u53e3\uff0c\u800c\u662fVGA\u8f93\u51fa\u63a5\u53e3\uff0c\u8bf7\u4f7f\u7528\u8be5\u6a21\u5757\u5b8c\u6210VGA\u8f6cHDMI\u4fe1\u53f7\u8f6c\u6362\u3002 USB\u8f6cTTL\u6a21\u5757 \u901a\u8fc7\u6539\u6a21\u5757\uff0c\u53ef\u4ee5\u8fde\u63a5BLIKVM PCIe\u5361\u7684\u4e32\u53e3\uff0c\u7136\u540e\u4f7f\u7528\u4e32\u53e3\u8fdb\u5165\u8bbe\u5907\u8fdb\u884c\u8c03\u8bd5\u3002 \u98ce\u6247 Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card. \u4f7f\u7528\u98ce\u6247\u5bf9\u6811\u8393\u6d3eCM4\u8fdb\u884c\u964d\u6e29\uff0c\u4f46\u5b89\u88c5\u98ce\u6247\u540e\u4f1a\u4f7fBLIKVM PCIe\u5361\u7684\u539a\u5ea6\u539a\u4e8e\u6807\u51c6\u7684PCIe\u5361\u539a\u5ea6\u3002 \u5c3a\u5bf8 \u6d4b\u8bd5\u89c6\u9891 BLIKVM PCIe\u7248\u672c\u5b9e\u6d4b\u89c6\u9891\uff0c\u8f6f\u4ef6\u4f7f\u7528PiKVM \u53d1\u8d27\u6e05\u5355 BLIKVM only PCIe\u5361\u7248\u672c 1 BLIKVM PCIe\u5361 1 \u98ce\u6247 1 OLED\u663e\u793a\u5c4f 1 USB\u8f6cTTL\u6a21\u5757 1 HDMI EDID\u6a21\u62df\u5668 1 VGA\u8f6cHDMI\u6a21\u5757 1 32G Micro SD card 1 HDMI\u7ebf 0.5m 1 HDMI \u76f4\u901a\u5934 1 \u5343\u5146\u7f51\u7ebf 1m 1 USB-A\u8f6cUSB-C\u7ebf 1m 2 USB\u675c\u90a6\u7ebf 0.4m 1 WiFi\u5929\u7ebf 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u91d1\u5c5e\u6563\u70ed\u7247 1 \u5341\u5b57\u5957\u7b52 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 BLIKVM PCIe \u5230\u624b\u5373\u7528\u7248\u672c 1 BLIKVM PCIe\u5361 1 CM4 102000 1 \u98ce\u6247 1 OLED\u663e\u793a\u5c4f 1 USB\u8f6cTTL\u6a21\u5757 1 HDMI EDID\u6a21\u62df\u5668 1 VGA\u8f6cHDMI\u6a21\u5757 1 32G Micro SD card 1 HDMI\u7ebf 0.5m 1 HDMI \u76f4\u901a\u5934 1 \u5343\u5146\u7f51\u7ebf 1m 1 USB-A\u8f6cUSB-C\u7ebf 1m 2 USB\u675c\u90a6\u7ebf 0.4m 1 WiFi\u5929\u7ebf 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u91d1\u5c5e\u6563\u70ed\u7247 1 \u5341\u5b57\u5957\u7b52 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 \u5907\u6ce8\uff1a\u7531\u4e8e\u6811\u8393\u6d3eCM4\u4e00\u76f4\u7d27\u7f3a\uff0c\u5230\u624b\u5373\u7528\u7248\u672c\u4e2dCM4\u7248\u672c\u53ef\u80fd\u4f1a\u66f4\u6362\u4e3aeMMC\u7248\u672c\uff0c\u6b64\u4e2d\u60c5\u51b5\u4e0b\u5c06\u4e0d\u5e26SD\u5361\u3002 \u8d2d\u4e70\u94fe\u63a5 v2\u6dd8\u5b9d\u5730\u5740 3D\u5916\u58f3 \u4e00\u4e2a\u7b80\u5355\u7684PCIe\u5916\u58f3 Download file","title":"BliKVM v2 PCIe\u5bfc\u89c8"},{"location":"BLIKVM-PCIE-guide-zh/#blikvm-pcie","text":"","title":"BLIKVM PCIe"},{"location":"BLIKVM-PCIE-guide-zh/#_1","text":"BLIKVM PCIe\u662f\u4e00\u6b3e\u57fa\u4e8e\u6811\u8393\u6d3eCM4\u7684IPKVM\u6269\u5c55\u5361\uff0c\u53ef\u4ee5\u5b89\u88c5\u5230PC\u6216\u8005\u670d\u52a1\u5668\u7684PCIe\u63d2\u69fd\uff0c\u5b8c\u7f8e\u8fd0\u884cPiKVM\u9879\u76ee\u3002\u4e3b\u8981\u529f\u80fd\u6709\uff1aHDMI\u89c6\u9891\u91c7\u96c6\uff0c\u952e\u76d8\u9f20\u6807\u63a7\u5236\uff0cATX\u5f00\u5173\u673a\u63a7\u5236\uff0cPoE\u4f9b\u7535\uff0cOLED\u5c4f\u5e55\u663e\u793a\uff0c \u4e32\u53e3\u7ec8\u7aef\u8c03\u8bd5\u548cRTC\u65f6\u949f\u529f\u80fd\u3002\u6b64PCIe\u5361\u914d\u6709\u5168\u9ad8\u548c\u534a\u9ad8\u7684\u6321\u677f\u3002 BLIKVM PCIe\u7248\u672c\u652f\u6301blikvm\u548cpikvm\u7684\u7cfb\u7edf\u955c\u50cf\u3002","title":"\u4ecb\u7ecd"},{"location":"BLIKVM-PCIE-guide-zh/#_2","text":"\u4f60\u9700\u8981\u4e0b\u9762\u7684\u8bbe\u5907 \u6811\u8393\u6d3eCM4(\u5982\u679c\u4f60\u53ea\u8ba2\u8d2d\u4e86PCIe\u5361). PoE\u4f9b\u7535\u8bbe\u5907\u62165V/3A USB\u4f9b\u7535\u8bbe\u5907. CR1220 \u7ebd\u6263\u7535\u6c60.","title":"\u5b89\u88c5\u8981\u6c42"},{"location":"BLIKVM-PCIE-guide-zh/#_3","text":"\u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@60Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE \u4f9b\u7535 \u652f\u6301\u4e32\u53e3\u7ec8\u7aef \u652f\u6301 WiFi \uff08\u53ef\u9009\uff09 OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) PWM\u98ce\u6247","title":"\u529f\u80fd"},{"location":"BLIKVM-PCIE-guide-zh/#_4","text":"1. \u5982\u679c\u4f60\u8d2d\u4e70\u7684\u662f\u9700\u8981\u81ea\u5df1\u7ec4\u88c5\u7684\u7248\u672c\uff0c\u70e7\u5f55\u7cfb\u7edf\u955c\u50cf\u53c2\u8003\u8bf7\u70b9\u51fb\u6b64\u5904 2.\u7ec4\u88c5 BLIKVM \u53c2\u8003\u7684 \u8bf4\u660e\u6587\u6863 Geerling\u7684\u6d4b\u8bd5\u89c6\u9891 Craft Computing: Never Pay For IPMI Again - BliKVM Review","title":"\u5feb\u901f\u5b89\u88c5\u8bf4\u660e"},{"location":"BLIKVM-PCIE-guide-zh/#_5","text":"\u786c\u4ef6\u63a5\u53e3\u6e05\u5355 1 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 2 USB-PC \u7aef\u53e3 1 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 2 USB-PC \u7aef\u53e3 3 \u4f9b\u7535\u53e3 5V 3A 4 RJ45 100M \u7f51\u53e3 & PoE 5 ATX\u63a7\u5236\u7aef\u53e3 6 OLED \u663e\u793a\u5c4f\u63a5\u53e3 7 PWM \u98ce\u6247 8 BOOT 9 RTC\u65f6\u949f 10 \u4e32\u884c\u7ec8\u7aef\u7aef\u53e3 11 USB-PC\u7aef\u53e3 HDMI IN \u4f7f\u7528\u4e1c\u829d\u7684TC358743\u4f5c\u4e3aHDMI\u7684\u6865\u63a5\u82af\u7247\uff0c\u540c\u65f6\u652f\u6301\u89c6\u9891\u548c\u97f3\u9891\u91c7\u96c6\uff0c\u652f\u6301\u89c6\u9891\u8f93\u5165\u6700\u9ad8\u5206\u8fa8\u7387\u4e3a1080P60Hz\u3002 USB-PC BLIKVM PCIe\u5361\u63d0\u4f9b\u4e24\u4e2ausb\u63a5\u53e3\uff0c\u4e00\u4e2a\u662fPC-IN\uff08type c\u63a5\u53e3\uff09\uff0c\u53e6\u4e00\u4e2a\u662fUSB-PC2\uff08\u6392\u9488\u63a5\u53e3\uff09\u3002\u8fd9\u4e24\u4e2a\u63a5\u53e3\u7684\u4f5c\u7528\u90fd\u662f\u4e3a\u4e86\u8fde\u63a5\u88ab\u63a7\u7535\u8111\u7684usb\uff0c\u7528\u4e8e\u63a7\u5236\u9f20\u6807\u548c\u952e\u76d8\u3002\u540c\u65f6\u4e24\u4e2a\u63a5\u53e3\u53ea\u80fd\u4f7f\u7528\u4e00\u4e2a\uff0c\u8bbe\u8ba1\u4e24\u4e2a\u63a5\u53e3\u7684\u76ee\u7684\u662f\uff0c\u5f53\u7528\u6237pc\u4e3b\u673a\u5185\u6709\u6392\u9488\u7684usb\u63a5\u53e3\u65f6\uff0c\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528usb-pc2\uff0c\u8fd9\u6837\u63a5\u7ebf\u4f1a\u66f4\u52a0\u7b80\u6d01\u3002 POWER-IN \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u6539\u63a5\u53e3\u4e0d\u9700\u8981\u88ab\u4f7f\u7528\u3002\u5f53\u4e0d\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u8fde\u63a5\u8be5\u63a5\u53e3\u7684\u7535\u6e90\u9002\u914d\u5668\uff0c\u63a8\u8350\u4e3a5V/3A\u3002 \u4ee5\u592a\u7f51\u53e3-PoE Gigabit Ethernet port \u6807\u51c6: IEEE 802.3af PoE \u8f93\u5165\u7535\u538b: 37-57 V DC \u8f93\u51fa\u7535\u538b: 5 V DC/2.4 A ATX\u63a5\u53e3 \u6539\u63a5\u53e3\u901a\u8fc7\u675c\u90a6\u7ebf\u94fe\u63a5\u88ab\u63a7\u8ba1\u7b97\u673a\u4e3b\u677f\u7684\u7535\u6e90\u63a7\u5236\u63a5\u53e3\u3002ATX\u529f\u80fd\u53ef\u4ee5\u5f00\u542f\u6216\u8005\u91cd\u542f\u88ab\u63a7\u8ba1\u7b97\u673a\u3002 PCIe\u677f\u5b50\u4e0a\u7684BTN\u4e1d\u5370\u4e3abutton\u7684\u7f29\u5199\u3002 \u6839\u636e\u7535\u8111\u4e3b\u677f\u8bf4\u660e\uff0c\u9996\u5148\u627e\u5230\u4e3b\u677f\u4e0aATX\u529f\u80fd\u76f8\u5173\u5f15\u811a\u4f4d\u7f6e\uff0c\u62d4\u4e0b\u4e3b\u677f\u5df2\u7ecf\u63a5\u597d\u7684ATX\u7ebf\uff0c\u62d4\u4e0b\u540e\u7535\u8111\u7684\u7535\u6e90\u6309\u94ae\u5c06\u5931\u53bb\u4f5c\u7528\u3002PCIe\u4e3b\u677f\u5171\u6709\u4e24\u63928PIN\u5f15\u811a\uff0c\u4e24\u6392\u5f15\u811a\u529f\u80fd\u5b8c\u5168\u76f8\u540c\u4f7f\u7528\u65f6\u65e0\u9700\u533a\u5206\u3002\u5176\u4e2d\u4e00\u6392\u5f15\u811a\u7528\u4e8eKVM\u63a7\u5236ATX\u76f8\u5173\u529f\u80fd\uff0c\u53e6\u4e00\u6392\u5f15\u811a\u63a5\u4e3b\u677f\u4e0a\u62d4\u4e0b\u6765\u7684ATX\u675c\u90a6\u5934\uff0c\u4fdd\u6301\u539f\u6709\u673a\u7bb1\u7535\u6e90\u6309\u94ae\u529f\u80fd\u3002\u6839\u636e\u4e3b\u677f\u548cPCIe\u4e0a\u7684\u5177\u4f53\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u6bcf\u6839\u7ebf\u7684\u8fde\u63a5\uff0c\u8fde\u63a5\u5173\u7cfb\u53ef\u4ee5\u53c2\u8003\u4e0b\u56fe\uff1a OLED\u663e\u793a\u5c4f \u663e\u793a\u5c4f\u5206\u8fa8\u7387\u4e3a128x64\uff0c\u4e3b\u82af\u7247\u4e3aSSD1306\u3002\u901a\u8fc7\u6539\u5c4f\u5e55\u53ef\u4ee5\u5c55\u793aBLIKVM\u7684CPU\u7684\u6e29\u5ea6\u3001IP\u5730\u5740\u3001\u542f\u52a8\u65f6\u95f4\u7b49\u4fe1\u606f\u3002 \u98ce\u6247 \u98ce\u6247\u9ed8\u8ba4\u8bbe\u7f6e\u5de5\u4f5c\u6e29\u5ea6\u4e3a60\u6444\u6c0f\u5ea6\uff0c\u4e0e\u6811\u8393\u6d3eCM4\u7684\u901a\u8fc7GPIO12\u94fe\u63a5\u3002 BOOT Fit jumper to disable eMMC Boot \u901a\u8fc7\u8be5\u77ed\u63a5\u53e3\u53ef\u4ee5\u4f7f\u7528PCIe\u5361\u5bf9eMMC\u7248\u672c\u7684CM4\u8fdb\u884c\u955c\u50cf\u70e7\u5f55\u3002 \u5b9e\u65f6\u65f6\u949f (RTC) \u65f6\u949f\u82af\u7247\u4e3aPCF8563\uff0c\u4e0e\u6811\u8393\u6d3eCM4\u7684\u901a\u4fe1\u65b9\u5f0f\u4e3aI2C\u3002RTC\u5de5\u4f5c\u9700\u8981\u518d\u5b89\u88c5CR1220\u7535\u6c60\u540e\u3002 \u4e32\u53e3 \u53ef\u4ee5\u901a\u8fc7\u6539\u4e32\u53e3\u767b\u9646\u8bbe\u5907\u8fdb\u884c\u8c03\u8bd5\uff0c\u4e00\u822c\u5728\u5728\u7f51\u7edc\u94fe\u63a5\u6545\u969c\u7b49\u60c5\u51b5\u4e0b\u4f7f\u7528\u3002 \u6811\u8393\u6d3eCM4\u7684\u4e32\u53e3. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. \u5c06USB\u8f6cTTL\u6a21\u5757\u7684\u675c\u90a6\u5934\u8fde\u63a5\u5230PCIe\u7684 GTR \u53e3\uff0cUSB\u8f6cttl\u6a21\u5757\u4e0e GTR \u63a5\u7ebf\u5173\u7cfb\u4e3a\uff08\u9ed1\u8272\u7ebf-G, \u767d\u8272\u7ebf-T, \u7eff\u8272\u7ebf-R\uff09;\u5177\u4f53\u65b9\u6cd5\u53ef\u53c2\u8003 \u6b64\u6587\u6863","title":"\u4ea7\u54c1\u7279\u6027"},{"location":"BLIKVM-PCIE-guide-zh/#_6","text":"HDMI EDID\u6a21\u62df\u5668 \u5982\u679c\u88ab\u63a7\u8ba1\u7b97\u673a\u4e0d\u80fd\u6b63\u786e\u7684\u8f93\u51faHDMI\u56fe\u50cf\uff0c\u53ef\u4ee5\u4f7f\u7528\u6b64\u8bbe\u5907\u8fdb\u884c\u6d4b\u8bd5\u3002\u5b89\u88c5\u5728\u88ab\u63a7\u8bbe\u5907\u7684HDMI\u8f93\u51fa\u63a5\u53e3\u4e0a\uff0c\u7136\u540e\u518d\u901a\u8fc7HDMI\u7ebf\u8fde\u63a5\u5230BLIKVM\u3002 VGA\u8f6cHDMI\u6a21\u5757 \u5f53\u88ab\u63a7\u8ba1\u7b97\u673a\u4e0d\u662fHDMI\u8f93\u51fa\u63a5\u53e3\uff0c\u800c\u662fVGA\u8f93\u51fa\u63a5\u53e3\uff0c\u8bf7\u4f7f\u7528\u8be5\u6a21\u5757\u5b8c\u6210VGA\u8f6cHDMI\u4fe1\u53f7\u8f6c\u6362\u3002 USB\u8f6cTTL\u6a21\u5757 \u901a\u8fc7\u6539\u6a21\u5757\uff0c\u53ef\u4ee5\u8fde\u63a5BLIKVM PCIe\u5361\u7684\u4e32\u53e3\uff0c\u7136\u540e\u4f7f\u7528\u4e32\u53e3\u8fdb\u5165\u8bbe\u5907\u8fdb\u884c\u8c03\u8bd5\u3002 \u98ce\u6247 Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card. \u4f7f\u7528\u98ce\u6247\u5bf9\u6811\u8393\u6d3eCM4\u8fdb\u884c\u964d\u6e29\uff0c\u4f46\u5b89\u88c5\u98ce\u6247\u540e\u4f1a\u4f7fBLIKVM PCIe\u5361\u7684\u539a\u5ea6\u539a\u4e8e\u6807\u51c6\u7684PCIe\u5361\u539a\u5ea6\u3002","title":"\u914d\u4ef6"},{"location":"BLIKVM-PCIE-guide-zh/#_7","text":"","title":"\u5c3a\u5bf8"},{"location":"BLIKVM-PCIE-guide-zh/#_8","text":"BLIKVM PCIe\u7248\u672c\u5b9e\u6d4b\u89c6\u9891\uff0c\u8f6f\u4ef6\u4f7f\u7528PiKVM","title":"\u6d4b\u8bd5\u89c6\u9891"},{"location":"BLIKVM-PCIE-guide-zh/#_9","text":"BLIKVM only PCIe\u5361\u7248\u672c 1 BLIKVM PCIe\u5361 1 \u98ce\u6247 1 OLED\u663e\u793a\u5c4f 1 USB\u8f6cTTL\u6a21\u5757 1 HDMI EDID\u6a21\u62df\u5668 1 VGA\u8f6cHDMI\u6a21\u5757 1 32G Micro SD card 1 HDMI\u7ebf 0.5m 1 HDMI \u76f4\u901a\u5934 1 \u5343\u5146\u7f51\u7ebf 1m 1 USB-A\u8f6cUSB-C\u7ebf 1m 2 USB\u675c\u90a6\u7ebf 0.4m 1 WiFi\u5929\u7ebf 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u91d1\u5c5e\u6563\u70ed\u7247 1 \u5341\u5b57\u5957\u7b52 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 BLIKVM PCIe \u5230\u624b\u5373\u7528\u7248\u672c 1 BLIKVM PCIe\u5361 1 CM4 102000 1 \u98ce\u6247 1 OLED\u663e\u793a\u5c4f 1 USB\u8f6cTTL\u6a21\u5757 1 HDMI EDID\u6a21\u62df\u5668 1 VGA\u8f6cHDMI\u6a21\u5757 1 32G Micro SD card 1 HDMI\u7ebf 0.5m 1 HDMI \u76f4\u901a\u5934 1 \u5343\u5146\u7f51\u7ebf 1m 1 USB-A\u8f6cUSB-C\u7ebf 1m 2 USB\u675c\u90a6\u7ebf 0.4m 1 WiFi\u5929\u7ebf 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u91d1\u5c5e\u6563\u70ed\u7247 1 \u5341\u5b57\u5957\u7b52 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 \u5907\u6ce8\uff1a\u7531\u4e8e\u6811\u8393\u6d3eCM4\u4e00\u76f4\u7d27\u7f3a\uff0c\u5230\u624b\u5373\u7528\u7248\u672c\u4e2dCM4\u7248\u672c\u53ef\u80fd\u4f1a\u66f4\u6362\u4e3aeMMC\u7248\u672c\uff0c\u6b64\u4e2d\u60c5\u51b5\u4e0b\u5c06\u4e0d\u5e26SD\u5361\u3002","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"BLIKVM-PCIE-guide-zh/#_10","text":"v2\u6dd8\u5b9d\u5730\u5740","title":"\u8d2d\u4e70\u94fe\u63a5"},{"location":"BLIKVM-PCIE-guide-zh/#3d","text":"\u4e00\u4e2a\u7b80\u5355\u7684PCIe\u5916\u58f3 Download file","title":"3D\u5916\u58f3"},{"location":"BLIKVM-PCIe-installation-zh/","text":"BLIKVM PCIe \u5b89\u88c5\u8bf4\u660e 1.\u62c6\u5f00\u5305\u88c5\uff0c\u62ff\u51fa\u8bbe\u5907 \u4ea7\u54c1\u6e05\u5355 2.\u5b89\u88c5\u4e3b\u4f53\u8bbe\u5907 \u5b89\u88c5CM4\u548c4\u4e2a\u516d\u89d2\u87ba\u67f1(\u6b64\u6587\u7ae0\u4f7f\u7528\u7684\u662fCM4 lite\u4f5c\u4e3a\u5217\u5b50\uff0c\u955c\u50cf\u5728\u51fa\u5382\u7684SD\u5361\u91cc\u5df2\u7ecf\u88ab\u9884\u88c5\u8f7d\uff0c\u7528\u6237\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528\u3002\u82e5\u4f60\u7684CM4\u662fEMMc\u7248\u672c\uff0c\u5219\u4f60\u9700\u8981\u81ea\u5df1\u70e7\u5f55\u955c\u50cf \uff0c\u65e0\u6cd5\u76f4\u63a5\u4f7f\u7528SD\u5361\u542f\u52a8)\u3002\u7136\u540e\u5c06\u5bfc\u70ed\u7247\u6495\u4e0b\u4fdd\u62a4\u819c\uff0c\u7c98\u8d34\u5728CM4\u9876\u90e8\u3002 \u5b89\u88c5\u91d1\u5c5e\u6563\u70ed\u7247\u3002 \u4e3b\u4f53\u8bbe\u5907\u5df2\u5b89\u88c5\u5b8c\u6210 3.\u8fde\u63a5USB\u63a5\u53e3\u548cATX\u63a5\u53e3 \u6b64\u6587\u4e2d\u7684\u4e3b\u677f\u4f7f\u7528\u7684\u662fAsus H520M-E\uff0c\u4e0d\u540c\u7684\u4e3b\u677f\u63a5\u53e3\u5b9a\u4e49\u4e0d\u4e00\u5b9a\u76f8\u540c\uff0c\u8bf7\u53c2\u8003\u60a8\u7684\u4e3b\u677f\u76f8\u5173\u624b\u518c\u3002 4.\u94fe\u63a5OLED\u663e\u793a\u5c4f \u60a8\u6536\u5230\u7684OLED\u662f\u672a\u5b89\u88c5\u652f\u67b6\u7684\uff0c\u8bf7\u53c2\u8003\u56fe\u7247\u8fdb\u884c\u5b89\u88c5\u3002\u53e6\u5916OLED\u652f\u67b6\u4e3a\u4e9a\u514b\u529b\u6750\u6599\uff0c\u9700\u8981\u6495\u53bb\u8868\u9762\u7684\u4fdd\u62a4\u819c\u540e\u4f7f\u7528\u3002 \u4e0a\u9762\u7684\u5c31\u662f\u5b89\u88c5\u6b65\u9aa4\uff0c\u672a\u6495\u819c\u7684\u6548\u679c\uff0c\u5b9e\u9645\u4f7f\u7528\u8bf7\u6495\u53bb\u4fdd\u62a4\u819c\uff0c\u6548\u679c\u5982\u4e0b\uff1a 5.\u8fde\u63a5HDMI\u7ebf \u5c06\u60a8\u7535\u8111\u7684HDMI\u8f93\u51fa\u53e3\u901a\u8fc7HDMI\u7ebf\u76f4\u63a5\u8fde\u63a5\u5230BLIKVM PCIe\u5361\u7684HDMI IN\u63a5\u53e3\u3002HDMI EDID\u6a21\u62df\u5668\u4e0d\u662f\u5fc5\u987b\u8981\u662f\u7528\u7684\uff0c\u5f53\u60a8\u7684\u8ba1\u7b97\u673a\u4e0d\u80fd\u6b63\u786e\u8f93\u51faHDMI\u753b\u9762\u65f6\uff0c\u53ef\u4ee5\u901a\u8fc7\u5c1d\u8bd5\u4f7f\u7528\u6b64\u6a21\u5757\u63a5\u5728\u4f60\u7684\u8ba1\u7b97\u673a\u7684HDMI\u63a5\u53e3\u4e0a\uff0c\u4ece\u800c\u8ba9\u60a8\u7684\u8ba1\u7b97\u673a\u53ef\u4ee5\u8f93\u51fa\u4e00\u4e2a\u6b63\u786e\u627dHDMI\u753b\u9762 6.\u8fde\u63a5\u7f51\u7ebf \u6807\u51c6: IEEE 802.3af PoE\u8f93\u5165\u7535\u538b:37v-57v. \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u4e0d\u9700\u8981\u4f7f\u7528PWR-IN\u7aef\u53e3\u518d\u4f9b\u7535 7.\u8fde\u63a5USB\u4f9b\u7535\u63a5\u53e3 \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6, \u901a\u8fc7\u4f7f\u7528PWR-IN\u7aef\u53e3\u8fdb\u884c\u4f9b\u7535\u7684USB\u7535\u6e90\u9002\u914d\u5668\u9700\u89815V/3A\u3002 8.\u6d4b\u8bd5 OLED\u663e\u793a\u5c4f\u73b0\u5b9e\u8bbe\u5907IP\u5730\u5740\u548c\u5176\u5b83\u4fe1\u606f \u4f7f\u7528\u8be5IP\u5730\u5740\u5728\u6d4f\u89c8\u5668\u4e0a\u76f4\u63a5\u8f93\u5165\uff0c\u5373\u53ef\u6253\u5f00web\u63a7\u5236\u754c\u9762\u3002\u5982\u679c\u89c6\u9891\u9f20\u6807\u952e\u76d8\u4ee5\u53ca\u5176\u5b83\u4f60\u5173\u5fc3\u7684\u529f\u80fd\u6d4b\u8bd5\u4e00\u5207\u6b63\u5728\uff0c\u5c31\u53ef\u4ee5\u5c06BLIKVM PCIe\u5361\u5b89\u88c5\u5230\u4f60\u7684\u673a\u7bb1\u4e2d\u3002 9.\u5b89\u88c5BLIKVM PCIe\u5361\u5230\u673a\u7bb1\u4e2d \u65ad\u5f00\u7535\u6e90\u548c\u8fde\u63a5\u7ebf\uff0c\u5148\u5c06PCIe\u5361\u5b89\u88c5\u5230\u4e3b\u677f\u4e0a\uff0c\u7136\u540e\u91cd\u65b0\u5c06\u7ebf\u7f06\u8fde\u63a5\u597d\u3002\u4e0d\u540c\u6279\u6b21\u6536\u5230\u7684ATX\u7ebf\u989c\u8272\u53ef\u80fd\u4e0d\u4e00\u6837\uff0c\u8bf7\u76f4\u63a5\u53c2\u8003\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u8fde\u63a5\u3002 \u5230\u8fd9\u91cc\u4f60\u5c31\u53ef\u4ee5\u4eab\u53d7BLIKVM PCIe\u5361\u6765\u7ba1\u7406\u4f60\u7684\u8ba1\u7b97\u673a\u5566! \u9644\u5f55 1.\u5b89\u88c5\u534a\u9ad8\u7684PCIe\u6321\u677f Note \u9644\u5f55 2.\u5b89\u88c5\u6563\u70ed\u98ce\u6247 \u901a\u5e38\u4f7f\u7528\u91d1\u5c5e\u6563\u70ed\u7247\u5df2\u7ecf\u8db3\u591f\uff0c\u5b89\u88c5\u6563\u70ed\u98ce\u6247\u4e0d\u662f\u5fc5\u987b\u7684 \u98ce\u6247\u88ab\u6811\u8393\u6d3e\u7684GPIO12\u53e3\u63a7\u5236 \u9644\u5f55 3.\u5b89\u88c5wifi\u5929\u7ebf Note","title":"v2 PCIe\u5b89\u88c5\u8bf4\u660e"},{"location":"BLIKVM-PCIe-installation-zh/#blikvm-pcie","text":"","title":"BLIKVM PCIe \u5b89\u88c5\u8bf4\u660e"},{"location":"BLIKVM-PCIe-installation-zh/#1","text":"\u4ea7\u54c1\u6e05\u5355","title":"1.\u62c6\u5f00\u5305\u88c5\uff0c\u62ff\u51fa\u8bbe\u5907"},{"location":"BLIKVM-PCIe-installation-zh/#2","text":"\u5b89\u88c5CM4\u548c4\u4e2a\u516d\u89d2\u87ba\u67f1(\u6b64\u6587\u7ae0\u4f7f\u7528\u7684\u662fCM4 lite\u4f5c\u4e3a\u5217\u5b50\uff0c\u955c\u50cf\u5728\u51fa\u5382\u7684SD\u5361\u91cc\u5df2\u7ecf\u88ab\u9884\u88c5\u8f7d\uff0c\u7528\u6237\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528\u3002\u82e5\u4f60\u7684CM4\u662fEMMc\u7248\u672c\uff0c\u5219\u4f60\u9700\u8981\u81ea\u5df1\u70e7\u5f55\u955c\u50cf \uff0c\u65e0\u6cd5\u76f4\u63a5\u4f7f\u7528SD\u5361\u542f\u52a8)\u3002\u7136\u540e\u5c06\u5bfc\u70ed\u7247\u6495\u4e0b\u4fdd\u62a4\u819c\uff0c\u7c98\u8d34\u5728CM4\u9876\u90e8\u3002 \u5b89\u88c5\u91d1\u5c5e\u6563\u70ed\u7247\u3002 \u4e3b\u4f53\u8bbe\u5907\u5df2\u5b89\u88c5\u5b8c\u6210","title":"2.\u5b89\u88c5\u4e3b\u4f53\u8bbe\u5907"},{"location":"BLIKVM-PCIe-installation-zh/#3usbatx","text":"\u6b64\u6587\u4e2d\u7684\u4e3b\u677f\u4f7f\u7528\u7684\u662fAsus H520M-E\uff0c\u4e0d\u540c\u7684\u4e3b\u677f\u63a5\u53e3\u5b9a\u4e49\u4e0d\u4e00\u5b9a\u76f8\u540c\uff0c\u8bf7\u53c2\u8003\u60a8\u7684\u4e3b\u677f\u76f8\u5173\u624b\u518c\u3002","title":"3.\u8fde\u63a5USB\u63a5\u53e3\u548cATX\u63a5\u53e3"},{"location":"BLIKVM-PCIe-installation-zh/#4oled","text":"\u60a8\u6536\u5230\u7684OLED\u662f\u672a\u5b89\u88c5\u652f\u67b6\u7684\uff0c\u8bf7\u53c2\u8003\u56fe\u7247\u8fdb\u884c\u5b89\u88c5\u3002\u53e6\u5916OLED\u652f\u67b6\u4e3a\u4e9a\u514b\u529b\u6750\u6599\uff0c\u9700\u8981\u6495\u53bb\u8868\u9762\u7684\u4fdd\u62a4\u819c\u540e\u4f7f\u7528\u3002 \u4e0a\u9762\u7684\u5c31\u662f\u5b89\u88c5\u6b65\u9aa4\uff0c\u672a\u6495\u819c\u7684\u6548\u679c\uff0c\u5b9e\u9645\u4f7f\u7528\u8bf7\u6495\u53bb\u4fdd\u62a4\u819c\uff0c\u6548\u679c\u5982\u4e0b\uff1a","title":"4.\u94fe\u63a5OLED\u663e\u793a\u5c4f"},{"location":"BLIKVM-PCIe-installation-zh/#5hdmi","text":"\u5c06\u60a8\u7535\u8111\u7684HDMI\u8f93\u51fa\u53e3\u901a\u8fc7HDMI\u7ebf\u76f4\u63a5\u8fde\u63a5\u5230BLIKVM PCIe\u5361\u7684HDMI IN\u63a5\u53e3\u3002HDMI EDID\u6a21\u62df\u5668\u4e0d\u662f\u5fc5\u987b\u8981\u662f\u7528\u7684\uff0c\u5f53\u60a8\u7684\u8ba1\u7b97\u673a\u4e0d\u80fd\u6b63\u786e\u8f93\u51faHDMI\u753b\u9762\u65f6\uff0c\u53ef\u4ee5\u901a\u8fc7\u5c1d\u8bd5\u4f7f\u7528\u6b64\u6a21\u5757\u63a5\u5728\u4f60\u7684\u8ba1\u7b97\u673a\u7684HDMI\u63a5\u53e3\u4e0a\uff0c\u4ece\u800c\u8ba9\u60a8\u7684\u8ba1\u7b97\u673a\u53ef\u4ee5\u8f93\u51fa\u4e00\u4e2a\u6b63\u786e\u627dHDMI\u753b\u9762","title":"5.\u8fde\u63a5HDMI\u7ebf"},{"location":"BLIKVM-PCIe-installation-zh/#6","text":"\u6807\u51c6: IEEE 802.3af PoE\u8f93\u5165\u7535\u538b:37v-57v. \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u4e0d\u9700\u8981\u4f7f\u7528PWR-IN\u7aef\u53e3\u518d\u4f9b\u7535","title":"6.\u8fde\u63a5\u7f51\u7ebf"},{"location":"BLIKVM-PCIe-installation-zh/#7usb","text":"\u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6, \u901a\u8fc7\u4f7f\u7528PWR-IN\u7aef\u53e3\u8fdb\u884c\u4f9b\u7535\u7684USB\u7535\u6e90\u9002\u914d\u5668\u9700\u89815V/3A\u3002","title":"7.\u8fde\u63a5USB\u4f9b\u7535\u63a5\u53e3"},{"location":"BLIKVM-PCIe-installation-zh/#8","text":"OLED\u663e\u793a\u5c4f\u73b0\u5b9e\u8bbe\u5907IP\u5730\u5740\u548c\u5176\u5b83\u4fe1\u606f \u4f7f\u7528\u8be5IP\u5730\u5740\u5728\u6d4f\u89c8\u5668\u4e0a\u76f4\u63a5\u8f93\u5165\uff0c\u5373\u53ef\u6253\u5f00web\u63a7\u5236\u754c\u9762\u3002\u5982\u679c\u89c6\u9891\u9f20\u6807\u952e\u76d8\u4ee5\u53ca\u5176\u5b83\u4f60\u5173\u5fc3\u7684\u529f\u80fd\u6d4b\u8bd5\u4e00\u5207\u6b63\u5728\uff0c\u5c31\u53ef\u4ee5\u5c06BLIKVM PCIe\u5361\u5b89\u88c5\u5230\u4f60\u7684\u673a\u7bb1\u4e2d\u3002","title":"8.\u6d4b\u8bd5"},{"location":"BLIKVM-PCIe-installation-zh/#9blikvm-pcie","text":"\u65ad\u5f00\u7535\u6e90\u548c\u8fde\u63a5\u7ebf\uff0c\u5148\u5c06PCIe\u5361\u5b89\u88c5\u5230\u4e3b\u677f\u4e0a\uff0c\u7136\u540e\u91cd\u65b0\u5c06\u7ebf\u7f06\u8fde\u63a5\u597d\u3002\u4e0d\u540c\u6279\u6b21\u6536\u5230\u7684ATX\u7ebf\u989c\u8272\u53ef\u80fd\u4e0d\u4e00\u6837\uff0c\u8bf7\u76f4\u63a5\u53c2\u8003\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u8fde\u63a5\u3002 \u5230\u8fd9\u91cc\u4f60\u5c31\u53ef\u4ee5\u4eab\u53d7BLIKVM PCIe\u5361\u6765\u7ba1\u7406\u4f60\u7684\u8ba1\u7b97\u673a\u5566!","title":"9.\u5b89\u88c5BLIKVM PCIe\u5361\u5230\u673a\u7bb1\u4e2d"},{"location":"BLIKVM-PCIe-installation-zh/#1pcie","text":"Note","title":"\u9644\u5f55 1.\u5b89\u88c5\u534a\u9ad8\u7684PCIe\u6321\u677f"},{"location":"BLIKVM-PCIe-installation-zh/#2_1","text":"\u901a\u5e38\u4f7f\u7528\u91d1\u5c5e\u6563\u70ed\u7247\u5df2\u7ecf\u8db3\u591f\uff0c\u5b89\u88c5\u6563\u70ed\u98ce\u6247\u4e0d\u662f\u5fc5\u987b\u7684 \u98ce\u6247\u88ab\u6811\u8393\u6d3e\u7684GPIO12\u53e3\u63a7\u5236","title":"\u9644\u5f55 2.\u5b89\u88c5\u6563\u70ed\u98ce\u6247"},{"location":"BLIKVM-PCIe-installation-zh/#3wifi","text":"Note","title":"\u9644\u5f55 3.\u5b89\u88c5wifi\u5929\u7ebf"},{"location":"BliKVM-v4-guide/","text":"BliKVM v4 Allwinner BliKVM v4\u662f\u4e00\u6b3e\u751f\u4ea7\u5c31\u7eea\u3001\u5373\u63d2\u5373\u7528\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86 \u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406 \u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e \u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5 \u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1 \uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01 BliKVM V4 Datasheet Craft Computing: Goodbye IPMI - Blicube BliKVM V4 \u6d4b\u8bc4 Lawrence Systems: Blicube BliKVM V4: Is This the Best Linux IP KVM Yet? RainCat: BliKVM V4 Allwinnner\u5b89\u88c5PiKVM\u6559\u7a0b \u529f\u80fd\u7279\u70b9 \u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63014K@30Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) HDMI\u89c6\u9891\u73af\u51fa ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE & DC \u652f\u6301 WiFi \u4e32\u53e3 \u63a7\u5236\u53f0\u7aef\u53e3 1.33\u82f1\u5bf8 \u5f69\u8272 \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) HDMI\u652f\u6301\u7684\u5206\u8fa8\u7387\u7c7b\u578b \u5b89\u88c5\u8981\u6c42 \u9664v4\u5957\u4ef6\u5916\uff0c\u60a8\u8fd8\u9700\u81ea\u5907\u4ee5\u4e0b\u8bbe\u5907 \u7535\u6e90\u9002\u914d\u5668\uff085V 3A, USB-C\u7aef\u53e3\u621612V 2ADC\u7aef\u53e3\uff09,\u82e5\u4f60\u8ba1\u5212\u4f7f\u7528PoE\u4f9b\u7535\uff0c\u6216\u8005\u6240\u7684\u88ab\u63a7\u8ba1\u7b97\u673aUSB\u53e3\u6709\u5145\u8db3\u7684\u4f9b\u7535\u80fd\u529b\uff0c\u5219\u4e5f\u4e0d\u9700\u8981\u5355\u72ec\u7684\u7535\u6e90\u9002\u914d\u5668\uff1b HDMI \u7ebf\u7f06(\u81f3\u5c11\u4e00\u6839)\uff0c\u82e5\u60a8\u540c\u65f6\u9700\u8981\u4f7f\u7528HDMI\u73af\u51fa\u63a5\u53e3\uff0c\u5219\u9700\u89812\u6839\uff1b \u7f51\u7ebf\uff08\u7ed3\u5408\u60a8\u9700\u6c42\u81ea\u5907\uff09,\u4f7f\u7528ATX\u5f00\u5173\u673a\u529f\u80fd\u9700\u4e00\u6839\uff0c\u4f7f\u7528\u7f51\u7ebf\u4e0a\u7f51\u529f\u80fd\u9700\u4e00\u6839\uff1b USB-C\u8f6cUSB-A\u7ebf\u7f06\u4e00\u6839\uff08\u7528\u4e8e\u9f20\u6807\u548c\u952e\u76d8\u6570\u636e\u4f20\u8f93\uff09. \u7ec8\u7aef\u5347\u7ea7\u6ce8\u610f\uff01 \u5728\u5347\u7ea7\u524d\uff0c\u9700\u6267\u884c\u4e0b\u9762\u547d\u4ee4\uff0c\u5426\u5219apt-get update \u548c apt-get upgrade\u540e\u955c\u50cf\u4f1a\u65e0\u6cd5\u542f\u52a8 apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64 BliKVM v4 \u62c6\u7bb1\uff0c\u8fde\u63a5\uff0c\u4f7f\u7528\u53c2\u8003\u89c6\u9891 \u5b89\u88c5\u6b65\u9aa4 1. \u6253\u5f00v4\u5957\u4ef6\u5305\u88c5\uff0c\u6839\u636e\u4e0b\u9762\u6240\u793a\u7684\u8fde\u63a5\u793a\u610f\u56fe\uff0c\u5c06BliKVM\u548c\u88ab\u63a7\u8ba1\u7b97\u673a\u8fde\u63a5\u8d77\u6765\uff1b ATX\u8fde\u63a5 \u8bf7\u53c2\u8003 ATX\u8fde\u63a5\u6307\u5357 \u3002 2. \u5728\u6240\u6709\u8fde\u63a5\u7ebf\u8fde\u63a5\u597d\u540e,\u5bf9BliKVM\u8fdb\u884c\u4e0a\u7535\uff0c\u76f4\u5230\u663e\u793a\u5c4f\u51fa\u73b0\u753b\u9762\uff0c\u5373\u8bbe\u5907\u6b63\u5e38\u542f\u52a8\u3002 3. \u4ed4\u7ec6\u9605\u8bfb \u201c\u7b2c\u4e00\u6b65\u201d \u6307\u5357-\u5982\u4f55\u5728\u7f51\u7edc\u4e0a\u67e5\u627e\u8bbe\u5907\u3001\u5982\u4f55\u767b\u5f55\u3001\u66f4\u6539\u5bc6\u7801\u7b49\u7b49\u3002\u6309\u7167\u4e0a\u9762\u63cf\u8ff0\u7684\u6b65\u9aa4\u64cd\u4f5c\uff0c\u7136\u540e\u8fd4\u56de\u672c\u9875\u3002 4. \u5c1d\u8bd5\u4f7f\u7528 Web \u754c\u9762\u7ba1\u7406\u8ba1\u7b97\u673a\u7684 BliKVM\u3002 \u786e\u4fdd\u60a8\u53ef\u4ee5\u770b\u5230\u56fe\u50cf\u5e76\u4e14\u952e\u76d8\u548c\u9f20\u6807\u90fd\u6b63\u5e38\u5de5\u4f5c\u3002\u5982\u679c\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u8bf7\u67e5\u770b\u6211\u4eec\u7684 \u5e38\u89c1\u95ee\u9898 \uff08\u5b83\u975e\u5e38\u6709\u7528\uff09\u3002\u5982\u679c\u6ca1\u6709\u4efb\u4f55\u5e2e\u52a9\uff0c\u8bf7\u5728\u6211\u4eec\u7684 Discord\u804a\u5929\u5ba4 \u5bfb\u6c42\u652f\u6301\u3002 5. \u60a8\u53ef\u4ee5\u67e5\u770bwiki\u5176\u4ed6\u7684\u9875\u9762\uff0c\u63a2\u7d22BliKVM\u7684\u66f4\u591a\u529f\u80fd\uff0c\u795d\u60a8\u73a9\u7684\u5f00\u5fc3\uff01 \u89c6\u9891\u6a21\u5f0f v4\u6700\u9ad8\u652f\u63014K30Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u4f20\u8f93\u5206\u8fa8\u7387\u9ed8\u8ba4\u4e3a1920x1080\u3002 \u53d1\u8d27\u6e05\u5355 BLIKVM v4 Allwinner\u7248\u672c 1 BLIKVM v4 1 WiFi\u5929\u7ebf 1 ATX\u9002\u914d\u677f 1 ATX\u675c\u90a6\u7ebf\u7f06 8pin \u6bcd\u5bf9\u6bcd 60cm 1 ATX\u675c\u90a6\u7ebf\u7f06 8pin \u6bcd\u5bf9\u516c 60cm 1 1U\u5b89\u88c5\u6302\u8033 2 M2.5x5\u87ba\u4e1d 8 \u7845\u80f6\u9632\u649e\u7c92 1 \u901a\u8fc75V\u7aef\u53e3\u8bbf\u95ee\u4e32\u884c\u63a7\u5236\u53f0 5V\u7aef\u53e3\u53ef\u4ee5\u540c\u65f6\u7528\u4e8e\u4f9b\u7535\u548c\u4e32\u884c\u63a7\u5236\u53f0\u8bbf\u95ee\uff0c\u9ed8\u8ba4\u6ce2\u7279\u7387\u4e3a115200\u3002BliKVM v4\u5185\u90e8\u6709\u4e00\u4e2a\u57fa\u4e8eCH341\u7684USB\u5230UART\u8f6c\u6362\u5668\uff0c\u5b83\u8fde\u63a5\u5230 mCore-H616 SoC \u7684UART0\uff0c\u6240\u4ee5\u4f60\u53ef\u4ee5\u5c06PC\u7684USB\u7aef\u53e3\u8fde\u63a5\u52305V\u7aef\u53e3\uff0c\u65e0\u9700\u5916\u90e8UART\u548cUSB-C\u5230\u675c\u90a6\u9002\u914d\u5668\u3002 PC USB\u7aef\u53e3\u7535\u6d41\u8f93\u51fa \u5c1d\u8bd5\u4f7f\u75285V\u7aef\u53e3\u65f6\u8981\u5c0f\u5fc3\uff0c\u56e0\u4e3a\u5355\u72ec\u7684PC USB\u7aef\u53e3\u53ef\u80fd\u65e0\u6cd5\u63d0\u4f9b3A\uff085V\uff09\uff0c\u8fd9\u662f\u677f\u5361\u5de5\u4f5c\u7684\u8981\u6c42\u3002\u53ef\u4ee5\u540c\u65f6\u4f7f\u752812V 2A DC\u7aef\u53e3\u4f9b\u7535\u548c5V\u7aef\u53e3\u8fdb\u884c\u4e32\u884c\u901a\u4fe1\uff0c\u65e0\u9700 USB\u5206\u7ebf\u5668\u677f \u3002\u6216\u8005\u4f7f\u7528\u5206\u7ebf\u5668\u677f\u5206\u79bb\u51faVCC\u5f15\u811a\uff0c\u5e76\u4f7f\u7528\u5355\u72ec\u76845V 3A\u7535\u6e90\u4e3a5V\u7aef\u53e3\u7684VCC\u5f15\u811a\u4f9b\u7535\u3002\u540c\u6837\uff0c\u5f53BliKVM\u901a\u7535\u65f6\u4ece12V 2A DC\u7aef\u53e3\u65ad\u5f00\u7535\u7f06\u65f6\uff0c\u8981\u786e\u4fdd\u5148\u4ece5V\u7aef\u53e3\u65ad\u5f00\u7535\u7f06\uff08\u56e0\u4e3a\u572812V 2A\u7535\u6e90\u65ad\u5f00\u540e\uff0c\u9664\u975e\u4f7f\u7528\u4e86\u5206\u7ebf\u5668\uff0c\u5426\u52195V\u7aef\u53e3\u5c06\u6210\u4e3aBliKVM v4\u7684\u7535\u6e90\uff09\u3002 \u5f53\u4f60\u5c06USB\u7535\u7f06\u8fde\u63a5\u5230BliKVM v4\u76845V\u7aef\u53e3\u65f6\uff0c\u4f60\u5e94\u8be5\u5728\u4e3b\u673a\u5185\u6838\u65e5\u5fd7\u4e2d\u770b\u5230\u7c7b\u4f3c\u8fd9\u6837\u7684\u5185\u5bb9\uff08\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662f\u57fa\u4e8eLinux\u7684\u64cd\u4f5c\u7cfb\u7edf\uff09: usb 1-1.2: new full-speed USB device number 12 using xhci_hcd usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34 usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.2: Product: USB Serial ch341 1-1.2:1.0: ch341-uart converter detected usb 1-1.2: ch341-uart converter now attached to ttyUSB0 \u7136\u540e\uff0c\u53ef\u4ee5\u4f7f\u7528 GNU screen \u6216 TIO \u8bbf\u95ee\u6b64\u7aef\u53e3: tio /dev/ttyUSB0 mangopimcore login: blikvm # ... \u5982\u679c\u4f60\u9700\u8981\u68c0\u67e5\u901a\u8fc7UART0\u63a5\u6536\u4e86\u591a\u5c11\u6570\u636e\uff0c\u53ef\u4ee5\u901a\u8fc7\u67e5\u770b\u901a\u8fc7proc\u516c\u5f00\u7684\u8ba1\u6570\u5668\u6765\u5b9e\u73b0\uff08\u5f53\u4ece\u5916\u90e8\u4e3b\u673a\u53d1\u9001\u6570\u636e\u65f6\uff0c\u5982\u679c\u5185\u7f6e\u7684USB\u5230UART\u8f6c\u6362\u5668\u5de5\u4f5c\u6b63\u5e38\uff0crx\u8ba1\u6570\u5668\u5e94\u8be5\u4f1a\u589e\u52a0\uff09\uff1a root@mangopimcore:~# grep '0: uart' /proc/tty/driver/serial 0: uart:16550A mmio:0x05000000 irq:284 tx:20306 rx:40 pe:1 RTS|DTR \u8d2d\u4e70\u94fe\u63a5 v4\u6dd8\u5b9d\u5730\u5740","title":"BliKVM v4 Allwinner\u5bfc\u89c8"},{"location":"BliKVM-v4-guide/#blikvm-v4-allwinner","text":"BliKVM v4\u662f\u4e00\u6b3e\u751f\u4ea7\u5c31\u7eea\u3001\u5373\u63d2\u5373\u7528\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86 \u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406 \u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e \u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5 \u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1 \uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01 BliKVM V4 Datasheet Craft Computing: Goodbye IPMI - Blicube BliKVM V4 \u6d4b\u8bc4 Lawrence Systems: Blicube BliKVM V4: Is This the Best Linux IP KVM Yet? RainCat: BliKVM V4 Allwinnner\u5b89\u88c5PiKVM\u6559\u7a0b","title":"BliKVM v4 Allwinner"},{"location":"BliKVM-v4-guide/#_1","text":"\u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63014K@30Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) HDMI\u89c6\u9891\u73af\u51fa ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE & DC \u652f\u6301 WiFi \u4e32\u53e3 \u63a7\u5236\u53f0\u7aef\u53e3 1.33\u82f1\u5bf8 \u5f69\u8272 \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) HDMI\u652f\u6301\u7684\u5206\u8fa8\u7387\u7c7b\u578b","title":"\u529f\u80fd\u7279\u70b9"},{"location":"BliKVM-v4-guide/#_2","text":"\u9664v4\u5957\u4ef6\u5916\uff0c\u60a8\u8fd8\u9700\u81ea\u5907\u4ee5\u4e0b\u8bbe\u5907 \u7535\u6e90\u9002\u914d\u5668\uff085V 3A, USB-C\u7aef\u53e3\u621612V 2ADC\u7aef\u53e3\uff09,\u82e5\u4f60\u8ba1\u5212\u4f7f\u7528PoE\u4f9b\u7535\uff0c\u6216\u8005\u6240\u7684\u88ab\u63a7\u8ba1\u7b97\u673aUSB\u53e3\u6709\u5145\u8db3\u7684\u4f9b\u7535\u80fd\u529b\uff0c\u5219\u4e5f\u4e0d\u9700\u8981\u5355\u72ec\u7684\u7535\u6e90\u9002\u914d\u5668\uff1b HDMI \u7ebf\u7f06(\u81f3\u5c11\u4e00\u6839)\uff0c\u82e5\u60a8\u540c\u65f6\u9700\u8981\u4f7f\u7528HDMI\u73af\u51fa\u63a5\u53e3\uff0c\u5219\u9700\u89812\u6839\uff1b \u7f51\u7ebf\uff08\u7ed3\u5408\u60a8\u9700\u6c42\u81ea\u5907\uff09,\u4f7f\u7528ATX\u5f00\u5173\u673a\u529f\u80fd\u9700\u4e00\u6839\uff0c\u4f7f\u7528\u7f51\u7ebf\u4e0a\u7f51\u529f\u80fd\u9700\u4e00\u6839\uff1b USB-C\u8f6cUSB-A\u7ebf\u7f06\u4e00\u6839\uff08\u7528\u4e8e\u9f20\u6807\u548c\u952e\u76d8\u6570\u636e\u4f20\u8f93\uff09. \u7ec8\u7aef\u5347\u7ea7\u6ce8\u610f\uff01 \u5728\u5347\u7ea7\u524d\uff0c\u9700\u6267\u884c\u4e0b\u9762\u547d\u4ee4\uff0c\u5426\u5219apt-get update \u548c apt-get upgrade\u540e\u955c\u50cf\u4f1a\u65e0\u6cd5\u542f\u52a8 apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64 BliKVM v4 \u62c6\u7bb1\uff0c\u8fde\u63a5\uff0c\u4f7f\u7528\u53c2\u8003\u89c6\u9891","title":"\u5b89\u88c5\u8981\u6c42"},{"location":"BliKVM-v4-guide/#_3","text":"1. \u6253\u5f00v4\u5957\u4ef6\u5305\u88c5\uff0c\u6839\u636e\u4e0b\u9762\u6240\u793a\u7684\u8fde\u63a5\u793a\u610f\u56fe\uff0c\u5c06BliKVM\u548c\u88ab\u63a7\u8ba1\u7b97\u673a\u8fde\u63a5\u8d77\u6765\uff1b ATX\u8fde\u63a5 \u8bf7\u53c2\u8003 ATX\u8fde\u63a5\u6307\u5357 \u3002 2. \u5728\u6240\u6709\u8fde\u63a5\u7ebf\u8fde\u63a5\u597d\u540e,\u5bf9BliKVM\u8fdb\u884c\u4e0a\u7535\uff0c\u76f4\u5230\u663e\u793a\u5c4f\u51fa\u73b0\u753b\u9762\uff0c\u5373\u8bbe\u5907\u6b63\u5e38\u542f\u52a8\u3002 3. \u4ed4\u7ec6\u9605\u8bfb \u201c\u7b2c\u4e00\u6b65\u201d \u6307\u5357-\u5982\u4f55\u5728\u7f51\u7edc\u4e0a\u67e5\u627e\u8bbe\u5907\u3001\u5982\u4f55\u767b\u5f55\u3001\u66f4\u6539\u5bc6\u7801\u7b49\u7b49\u3002\u6309\u7167\u4e0a\u9762\u63cf\u8ff0\u7684\u6b65\u9aa4\u64cd\u4f5c\uff0c\u7136\u540e\u8fd4\u56de\u672c\u9875\u3002 4. \u5c1d\u8bd5\u4f7f\u7528 Web \u754c\u9762\u7ba1\u7406\u8ba1\u7b97\u673a\u7684 BliKVM\u3002 \u786e\u4fdd\u60a8\u53ef\u4ee5\u770b\u5230\u56fe\u50cf\u5e76\u4e14\u952e\u76d8\u548c\u9f20\u6807\u90fd\u6b63\u5e38\u5de5\u4f5c\u3002\u5982\u679c\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u8bf7\u67e5\u770b\u6211\u4eec\u7684 \u5e38\u89c1\u95ee\u9898 \uff08\u5b83\u975e\u5e38\u6709\u7528\uff09\u3002\u5982\u679c\u6ca1\u6709\u4efb\u4f55\u5e2e\u52a9\uff0c\u8bf7\u5728\u6211\u4eec\u7684 Discord\u804a\u5929\u5ba4 \u5bfb\u6c42\u652f\u6301\u3002 5. \u60a8\u53ef\u4ee5\u67e5\u770bwiki\u5176\u4ed6\u7684\u9875\u9762\uff0c\u63a2\u7d22BliKVM\u7684\u66f4\u591a\u529f\u80fd\uff0c\u795d\u60a8\u73a9\u7684\u5f00\u5fc3\uff01","title":"\u5b89\u88c5\u6b65\u9aa4"},{"location":"BliKVM-v4-guide/#_4","text":"v4\u6700\u9ad8\u652f\u63014K30Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u4f20\u8f93\u5206\u8fa8\u7387\u9ed8\u8ba4\u4e3a1920x1080\u3002","title":"\u89c6\u9891\u6a21\u5f0f"},{"location":"BliKVM-v4-guide/#_5","text":"BLIKVM v4 Allwinner\u7248\u672c 1 BLIKVM v4 1 WiFi\u5929\u7ebf 1 ATX\u9002\u914d\u677f 1 ATX\u675c\u90a6\u7ebf\u7f06 8pin \u6bcd\u5bf9\u6bcd 60cm 1 ATX\u675c\u90a6\u7ebf\u7f06 8pin \u6bcd\u5bf9\u516c 60cm 1 1U\u5b89\u88c5\u6302\u8033 2 M2.5x5\u87ba\u4e1d 8 \u7845\u80f6\u9632\u649e\u7c92 1","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"BliKVM-v4-guide/#5v","text":"5V\u7aef\u53e3\u53ef\u4ee5\u540c\u65f6\u7528\u4e8e\u4f9b\u7535\u548c\u4e32\u884c\u63a7\u5236\u53f0\u8bbf\u95ee\uff0c\u9ed8\u8ba4\u6ce2\u7279\u7387\u4e3a115200\u3002BliKVM v4\u5185\u90e8\u6709\u4e00\u4e2a\u57fa\u4e8eCH341\u7684USB\u5230UART\u8f6c\u6362\u5668\uff0c\u5b83\u8fde\u63a5\u5230 mCore-H616 SoC \u7684UART0\uff0c\u6240\u4ee5\u4f60\u53ef\u4ee5\u5c06PC\u7684USB\u7aef\u53e3\u8fde\u63a5\u52305V\u7aef\u53e3\uff0c\u65e0\u9700\u5916\u90e8UART\u548cUSB-C\u5230\u675c\u90a6\u9002\u914d\u5668\u3002 PC USB\u7aef\u53e3\u7535\u6d41\u8f93\u51fa \u5c1d\u8bd5\u4f7f\u75285V\u7aef\u53e3\u65f6\u8981\u5c0f\u5fc3\uff0c\u56e0\u4e3a\u5355\u72ec\u7684PC USB\u7aef\u53e3\u53ef\u80fd\u65e0\u6cd5\u63d0\u4f9b3A\uff085V\uff09\uff0c\u8fd9\u662f\u677f\u5361\u5de5\u4f5c\u7684\u8981\u6c42\u3002\u53ef\u4ee5\u540c\u65f6\u4f7f\u752812V 2A DC\u7aef\u53e3\u4f9b\u7535\u548c5V\u7aef\u53e3\u8fdb\u884c\u4e32\u884c\u901a\u4fe1\uff0c\u65e0\u9700 USB\u5206\u7ebf\u5668\u677f \u3002\u6216\u8005\u4f7f\u7528\u5206\u7ebf\u5668\u677f\u5206\u79bb\u51faVCC\u5f15\u811a\uff0c\u5e76\u4f7f\u7528\u5355\u72ec\u76845V 3A\u7535\u6e90\u4e3a5V\u7aef\u53e3\u7684VCC\u5f15\u811a\u4f9b\u7535\u3002\u540c\u6837\uff0c\u5f53BliKVM\u901a\u7535\u65f6\u4ece12V 2A DC\u7aef\u53e3\u65ad\u5f00\u7535\u7f06\u65f6\uff0c\u8981\u786e\u4fdd\u5148\u4ece5V\u7aef\u53e3\u65ad\u5f00\u7535\u7f06\uff08\u56e0\u4e3a\u572812V 2A\u7535\u6e90\u65ad\u5f00\u540e\uff0c\u9664\u975e\u4f7f\u7528\u4e86\u5206\u7ebf\u5668\uff0c\u5426\u52195V\u7aef\u53e3\u5c06\u6210\u4e3aBliKVM v4\u7684\u7535\u6e90\uff09\u3002 \u5f53\u4f60\u5c06USB\u7535\u7f06\u8fde\u63a5\u5230BliKVM v4\u76845V\u7aef\u53e3\u65f6\uff0c\u4f60\u5e94\u8be5\u5728\u4e3b\u673a\u5185\u6838\u65e5\u5fd7\u4e2d\u770b\u5230\u7c7b\u4f3c\u8fd9\u6837\u7684\u5185\u5bb9\uff08\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662f\u57fa\u4e8eLinux\u7684\u64cd\u4f5c\u7cfb\u7edf\uff09: usb 1-1.2: new full-speed USB device number 12 using xhci_hcd usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34 usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.2: Product: USB Serial ch341 1-1.2:1.0: ch341-uart converter detected usb 1-1.2: ch341-uart converter now attached to ttyUSB0 \u7136\u540e\uff0c\u53ef\u4ee5\u4f7f\u7528 GNU screen \u6216 TIO \u8bbf\u95ee\u6b64\u7aef\u53e3: tio /dev/ttyUSB0 mangopimcore login: blikvm # ... \u5982\u679c\u4f60\u9700\u8981\u68c0\u67e5\u901a\u8fc7UART0\u63a5\u6536\u4e86\u591a\u5c11\u6570\u636e\uff0c\u53ef\u4ee5\u901a\u8fc7\u67e5\u770b\u901a\u8fc7proc\u516c\u5f00\u7684\u8ba1\u6570\u5668\u6765\u5b9e\u73b0\uff08\u5f53\u4ece\u5916\u90e8\u4e3b\u673a\u53d1\u9001\u6570\u636e\u65f6\uff0c\u5982\u679c\u5185\u7f6e\u7684USB\u5230UART\u8f6c\u6362\u5668\u5de5\u4f5c\u6b63\u5e38\uff0crx\u8ba1\u6570\u5668\u5e94\u8be5\u4f1a\u589e\u52a0\uff09\uff1a root@mangopimcore:~# grep '0: uart' /proc/tty/driver/serial 0: uart:16550A mmio:0x05000000 irq:284 tx:20306 rx:40 pe:1 RTS|DTR","title":"\u901a\u8fc75V\u7aef\u53e3\u8bbf\u95ee\u4e32\u884c\u63a7\u5236\u53f0"},{"location":"BliKVM-v4-guide/#_6","text":"v4\u6dd8\u5b9d\u5730\u5740","title":"\u8d2d\u4e70\u94fe\u63a5"},{"location":"Datasheet-BliKVM-v4/","text":"BliKVM v4 \u786c\u4ef6\u624b\u518c \u63a5\u53e3\u5b9a\u4e49 1 USB 2.0 10 \u5929\u7ebf\u63a5\u53e3 2 \u4f9b\u7535\u53e3 5V 3A & UART 11 \u7f51\u53e3 100M & PoE 3 ATX \u63a7\u5236\u7aef\u53e3 12 1.33\u5bf8LCD\u5c4f\u5e55 4 HDMI \u89c6\u9891\u73af\u51fa\u7aef\u53e3 13 \u4f9b\u7535\u6307\u793a\u706f (\u7ea2\u8272) 5 USB-PC 14 \u7528\u6237\u81ea\u5b9a\u4e49\u6309\u94ae 6 \u4f9b\u7535\u53e3 12V 2A 5.5*2.1mm 15 \u72b6\u6001\u6307\u793a\u706f (\u7eff\u8272) 7 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 16 \u5c4f\u5e55\u663e\u793a\u6309\u94ae 8 HDMI \u8f93\u5165\u6307\u793a\u706f (\u7eff\u8272) 17 Micro SD \u5361\u69fd 9 HDMI \u8f93\u51fa\u6307\u793a\u706f (\u9ec4\u8272) \u53c2\u6570 \u53c2\u6570\u540d\u79f0 \u63cf\u8ff0 \u4f9b\u7535 5V 3A 5V \u7aef\u53e3, USB-PC \u7aef\u53e3 12V 2A 12V DC\u7aef\u53e3 PoE \u4ee5\u592a\u7f51\u4f9b\u7535 (IEEE802.3af\u534f\u8bae) 48V DC \u7aef\u53e3 HDMI-IN HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 HDMI-OUT HDMI \u89c6\u9891\u73af\u51fa\u7aef\u53e3 USB-PC \u6a21\u62df\u952e\u76d8\uff0c\u9f20\u6807\uff0c\u5927\u5bb9\u91cf\u5b58\u50a8\u5668\u6216\u5176\u4ed6USB\u8bbe\u5907 ATX \u5f00\u5173\u673a\u88ab\u63a7\u7535\u8111\uff0c\u8bfb\u53d6\u88ab\u63a7\u7535\u8111\u72b6\u6001\u6307\u793a\u706f WiFi&BT IEEE802.11 b/g/n + BLE4.2 Micro SD \u5361\u69fd \u5b89\u88c5\u955c\u50cf\u5185\u5b58\u5361 5V port 5V 3A \u7535\u6e90\u6216\u4e32\u884c\u63a7\u5236\u53f0\u7ba1\u7406\u7aef\u53e3 \u663e\u793a\u548c\u6307\u793a\u706f LED\u6307\u793a\u706f \u7535\u6e90\u6307\u793a\u706f\uff0c\u72b6\u6001\u6307\u793a\u706f\uff0cHDM\u8f93\u5165\u8f93\u51fa\u6307\u793a\u706f \u663e\u793a\u5c4f 1.33\u5bf8 TFT \u5f69\u8272\u5c4f\u5e55 \u7528\u6237\u81ea\u5b9a\u4e49\u6309\u94ae SW1 \u8702\u9e23\u5668 Find me \u89c6\u9891 \u5206\u8fa8\u7387 \u6700\u9ad8\u652f\u63014k@30Hz \u7f16\u7801\u683c\u5f0f MJPEG \u6838\u5fc3 \u82af\u7247 \u5168\u5fd7 H616/H313 RAM 1GB \u529f\u8017 \u6700\u9ad815W \u73af\u5883\u53c2\u6570 \u5de5\u4f5c\u6e29\u5ea6 0\u00b0C to 70\u00b0C \u5b58\u50a8\u6e29\u5ea6 -20\u00b0C to 60\u00b0C \u5c3a\u5bf8\u548c\u91cd\u91cf \u5c3a\u5bf8 100 (L) x 134 (W) x 44.4 (H) mm \u91cd\u91cf 0.45 kg BLIKVM CM4\u7248\u672c OLED\u663e\u793a\u5c4f \u8be5\u4ea7\u54c1\u6807\u914d\u4e00\u5757\u5206\u8fa8\u7387\u4e3a128x64\u7684\u5355\u8272OLED\u663e\u793a\u5c4f\uff0c\u82af\u7247\u578b\u53f7\u4e3aSSD1306\u3002 \u7528\u6237\u901a\u8fc7\u663e\u793a\u5c4f\u7684\u5e03\u7ebf\u5c06\u5176\u8fde\u63a5\u5230\u4ea7\u54c1\u3002 \u8be5\u6a21\u5757\u901a\u8fc7I^2^C\u63a5\u53e3\u8fde\u63a5\u5230CM4\u3002\u5e03\u7ebf\u5b9a\u4e49\u5982\u4e0b\u8868\u6240\u793a\u3002 \u8fd9\u662f\u4e00\u4e2a\u57fa\u4e8e SSD1306\u9a71\u52a8 \u7684\u5355\u8272OLED\u5e93\u3002 Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C) \u5916\u5f62\u5c3a\u5bf8","title":"BliKVM v4 \u786c\u4ef6\u624b\u518c"},{"location":"Datasheet-BliKVM-v4/#blikvm-v4","text":"","title":"BliKVM v4 \u786c\u4ef6\u624b\u518c"},{"location":"Datasheet-BliKVM-v4/#_1","text":"1 USB 2.0 10 \u5929\u7ebf\u63a5\u53e3 2 \u4f9b\u7535\u53e3 5V 3A & UART 11 \u7f51\u53e3 100M & PoE 3 ATX \u63a7\u5236\u7aef\u53e3 12 1.33\u5bf8LCD\u5c4f\u5e55 4 HDMI \u89c6\u9891\u73af\u51fa\u7aef\u53e3 13 \u4f9b\u7535\u6307\u793a\u706f (\u7ea2\u8272) 5 USB-PC 14 \u7528\u6237\u81ea\u5b9a\u4e49\u6309\u94ae 6 \u4f9b\u7535\u53e3 12V 2A 5.5*2.1mm 15 \u72b6\u6001\u6307\u793a\u706f (\u7eff\u8272) 7 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 16 \u5c4f\u5e55\u663e\u793a\u6309\u94ae 8 HDMI \u8f93\u5165\u6307\u793a\u706f (\u7eff\u8272) 17 Micro SD \u5361\u69fd 9 HDMI \u8f93\u51fa\u6307\u793a\u706f (\u9ec4\u8272)","title":"\u63a5\u53e3\u5b9a\u4e49"},{"location":"Datasheet-BliKVM-v4/#_2","text":"\u53c2\u6570\u540d\u79f0 \u63cf\u8ff0 \u4f9b\u7535 5V 3A 5V \u7aef\u53e3, USB-PC \u7aef\u53e3 12V 2A 12V DC\u7aef\u53e3 PoE \u4ee5\u592a\u7f51\u4f9b\u7535 (IEEE802.3af\u534f\u8bae) 48V DC \u7aef\u53e3 HDMI-IN HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 HDMI-OUT HDMI \u89c6\u9891\u73af\u51fa\u7aef\u53e3 USB-PC \u6a21\u62df\u952e\u76d8\uff0c\u9f20\u6807\uff0c\u5927\u5bb9\u91cf\u5b58\u50a8\u5668\u6216\u5176\u4ed6USB\u8bbe\u5907 ATX \u5f00\u5173\u673a\u88ab\u63a7\u7535\u8111\uff0c\u8bfb\u53d6\u88ab\u63a7\u7535\u8111\u72b6\u6001\u6307\u793a\u706f WiFi&BT IEEE802.11 b/g/n + BLE4.2 Micro SD \u5361\u69fd \u5b89\u88c5\u955c\u50cf\u5185\u5b58\u5361 5V port 5V 3A \u7535\u6e90\u6216\u4e32\u884c\u63a7\u5236\u53f0\u7ba1\u7406\u7aef\u53e3 \u663e\u793a\u548c\u6307\u793a\u706f LED\u6307\u793a\u706f \u7535\u6e90\u6307\u793a\u706f\uff0c\u72b6\u6001\u6307\u793a\u706f\uff0cHDM\u8f93\u5165\u8f93\u51fa\u6307\u793a\u706f \u663e\u793a\u5c4f 1.33\u5bf8 TFT \u5f69\u8272\u5c4f\u5e55 \u7528\u6237\u81ea\u5b9a\u4e49\u6309\u94ae SW1 \u8702\u9e23\u5668 Find me \u89c6\u9891 \u5206\u8fa8\u7387 \u6700\u9ad8\u652f\u63014k@30Hz \u7f16\u7801\u683c\u5f0f MJPEG \u6838\u5fc3 \u82af\u7247 \u5168\u5fd7 H616/H313 RAM 1GB \u529f\u8017 \u6700\u9ad815W \u73af\u5883\u53c2\u6570 \u5de5\u4f5c\u6e29\u5ea6 0\u00b0C to 70\u00b0C \u5b58\u50a8\u6e29\u5ea6 -20\u00b0C to 60\u00b0C \u5c3a\u5bf8\u548c\u91cd\u91cf \u5c3a\u5bf8 100 (L) x 134 (W) x 44.4 (H) mm \u91cd\u91cf 0.45 kg BLIKVM CM4\u7248\u672c OLED\u663e\u793a\u5c4f \u8be5\u4ea7\u54c1\u6807\u914d\u4e00\u5757\u5206\u8fa8\u7387\u4e3a128x64\u7684\u5355\u8272OLED\u663e\u793a\u5c4f\uff0c\u82af\u7247\u578b\u53f7\u4e3aSSD1306\u3002 \u7528\u6237\u901a\u8fc7\u663e\u793a\u5c4f\u7684\u5e03\u7ebf\u5c06\u5176\u8fde\u63a5\u5230\u4ea7\u54c1\u3002 \u8be5\u6a21\u5757\u901a\u8fc7I^2^C\u63a5\u53e3\u8fde\u63a5\u5230CM4\u3002\u5e03\u7ebf\u5b9a\u4e49\u5982\u4e0b\u8868\u6240\u793a\u3002 \u8fd9\u662f\u4e00\u4e2a\u57fa\u4e8e SSD1306\u9a71\u52a8 \u7684\u5355\u8272OLED\u5e93\u3002 Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C)","title":"\u53c2\u6570"},{"location":"Datasheet-BliKVM-v4/#_3","text":"","title":"\u5916\u5f62\u5c3a\u5bf8"},{"location":"Expand_Filesystem/","text":"\u6811\u8393\u6d3e\u6269\u5bb9 \u7b80\u4ecb \u7531\u4e8e\u5728\u5236\u4f5c\u955c\u50cf\u8fc7\u7a0b\u4e2d\uff0c\u5bf9\u955c\u50cf\u8fdb\u884c\u4e86\u538b\u7f29\uff0c\u5982\u679c\u4f60\u53d1\u73b0\u6811\u8393\u6d3eSD\u5361\u6216\u8005eMMC\u7684\u53ef\u7528\u7a7a\u95f4\u5c0f\u4e8e\u5b9e\u9645SD\u5361\u6216\u8005eMMc\u7684\u5bb9\u91cf\uff0c\u4f60\u53ef\u80fd\u9700\u8981\u8fdb\u884c\u4ee5\u4e0b\u64cd\u4f5c\uff0c\u5bf9\u6811\u8393\u6d3e\u8fdb\u884c\u6269\u5bb9\u3002 \u5982\u679c\u4f60\u53d1\u73b0\u7cfb\u7edf\u5e76\u65e0raspi-config\u5de5\u5177\uff0c\u5219\u53ef\u4f7f\u7528\u65b9\u6cd5\u4e8c\uff08\u4f7f\u7528GParted\u5206\u533a\u5de5\u5177\uff09\u3002 \u65b9\u6cd5\u4e00 \u4f7f\u7528raspi-config\u5de5\u5177 \u5982\u679c\u4f60\u4f7f\u7528\u76842023\u5e746\u6708\u4efd\u540e\u7684\u955c\u50cf\uff0c\u56e0\u589e\u52a0\u4e86\u7b2c\u4e09\u4e2a\u53ef\u8bfb\u5199\u7684\u5206\u533a\uff0c\u6b64\u65b9\u6cd5\u5df2\u7ecf\u4e0d\u9002\u7528\uff0c\u8bf7\u53c2\u8003\u65b9\u6848\u4e8c\u548c\u65b9\u6848\u4e09\u3002 1. \u6253\u5f00raspi-config\u7cfb\u7edf\u914d\u7f6e\u5de5\u5177 sudo raspi-config 2. \u9009\u62e9Advancd Options\uff1a 3. \u9009\u62e9Expand Filesystem\uff1a 4. Ok: 5. \u7ec8\u7aef\u6267\u884c resize2fs /dev/mmcblk0p2 \u6b64\u547d\u4ee4\u5373\u53ef\u770b\u5230SD\u5361\u5df2\u7ecf\u6269\u5bb9\u6210\u529f\u3002 \u65b9\u6cd5\u4e8c \u4f7f\u7528GParted\u5206\u533a\u5de5\u5177 1. \u5c06\u70e7\u5f55\u597d\u955c\u50cf\u7684SD\u5361\u6216\u8005EMMc\u901a\u8fc7usb\u63a5\u5230\u7535\u8111\u4e0a\uff0c\u4ee5linux\u4e0bGParted\u5206\u533a\u5de5\u5177\u4e3a\u4f8b\uff0c\u5176\u5b83\u5e73\u53f0\u4e5f\u6709\u7c7b\u4f3c\u7684\u5206\u533a\u5de5\u5177\u3002\u6253\u5f00GParted\u8f6f\u4ef6\uff0c\u9009\u62e9SD\u5361\uff1a 2. \u89c2\u5bdf\u4e0a\u56feSD\u5361\u7684\u5206\u533a\u60c5\u51b5\uff0c\u53ef\u4ee5\u53d1\u73b0\u5728sdb3\u5206\u533a\u7684\u524d\u540e\u5404\u67092.01GB\u548c21.87GB\u7684\u7a7a\u95f4\u672a\u4f7f\u7528\uff0c\u8fd9\u90e8\u5206\u7a7a\u95f4\u5c31\u662f\u6211\u4eec\u8981\u6269\u5bb9\u7684\u7a7a\u95f4\u3002\u9009\u4e2dsdb3\u5206\u533a\uff0c\u70b9\u51fb\u8c03\u6574\u5927\u5c0f\u3002 3. \u53ef\u4ee5\u62d6\u52a8sdb3\u7684\u767d\u8272\u5206\u533a\u6269\u5927\u5230\u6700\u5de6\u548c\u6700\u53f3\uff0c\u6216\u8005\u586b\u5199\u201c\u4e4b\u524d\u7684\u53ef\u7528\u7a7a\u95f4\u201d\u4e3a\u201c0\u201d\uff0c\u201c\u65b0\u5927\u5c0f\u201d\u4e3a\u201c\u6700\u5927\u5927\u5c0f\u201d\u768425958\uff0c\u7136\u540e\u70b9\u51fb\u53f3\u4e0b\u89d2\u7684\u8c03\u6574\u5927\u5c0f\uff0c\u7136\u540e\u5f39\u51fa\u6765\u7684\u63d0\u9192\u70b9\u51fb\u786e\u8ba4\uff0c\u5373\u53ef\u770b\u5230sd\u7684\u6240\u6709\u672a\u4f7f\u7528\u7a7a\u95f4\u5168\u90e8\u7528\u4e0a\u4e86\u3002 4. \u5c06SD\u5361\u63d2\u5165\u8bbe\u5907\uff0c\u542f\u52a8\u5373\u53ef\u3002 \u65b9\u6cd5\u4e09: \u4f7f\u7528\u811a\u672c \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM\u955c\u50cf\uff0c\u53ef\u4ee5\u5728KVM\u4e0a\u8fd0\u884c\u4e0b\u9762\u7684\u811a\u672c\uff0c\u6765\u81ea\u52a8\u6269\u5927\u7a7a\u95f4\u3002 1. \u7ec8\u7aef\u767b\u5f55\u5230KVM\u4e0a\uff0c\u786e\u8ba4\u7cfb\u7edf\u6709\u53ef\u8bfb\u5199\u6743\u9650\uff0c\u5728\u4efb\u610f\u8def\u5f84\u8fd0\u884c vim expand.sh ,\u5c06\u4e0b\u9762\u5185\u5bb9\u5199\u5165\u5230expand.sh\u4e2d. \u5982\u679c\u4f60\u662fv1,v2,v3\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u4e0b\u9762\u5185\u5bb9\uff1a #!/bin/bash set -x resize_mmcblk0p3() { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100% resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" \u5982\u679c\u4f60\u662fv4\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u4e0b\u9762\u5185\u5bb9\uff1a #!/bin/bash set -x resize_mmcblk0p1() { echo \"Resizing mmcblk0p1 partition...\" parted /dev/mmcblk0 resizepart 1 100% resize2fs /dev/mmcblk0p1 echo \"mmcblk0p1 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p1 echo \"Partition resizing completed.\" 2. \u7ec8\u7aef\u6267\u884c bash expand.sh ,\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002 \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM\u7684\u955c\u50cf\uff0c\u53ef\u4ee5\u5728KVM\u4e0a\u8fd0\u884c\u4e0b\u9762\u7684\u811a\u672c\uff0c\u6765\u81ea\u52a8\u6269\u5927\u7a7a\u95f4\u3002 1. \u7ec8\u7aef\u767b\u5f55\u5230KVM\u4e0a\uff0c\u786e\u8ba4\u7cfb\u7edf\u6709\u53ef\u8bfb\u5199\u6743\u9650\uff0c\u5728\u4efb\u610f\u8def\u5f84\u8fd0\u884c vim expand.sh ,\u5c06\u4e0b\u9762\u5185\u5bb9\u5199\u5165\u5230expand.sh\u4e2d. #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab; then part=$(grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}') # shellcheck disable=SC2206 splitted=(${part//=/ }) if [ \"${splitted[0]}\" == LABEL ]; then label=${splitted[1]} part=$(blkid -c /dev/null -L \"$label\") else label=PIMSD fi unset splitted disk=/dev/$(lsblk -no pkname \"$part\") npart=$(cat \"/sys/class/block/${part//\\/dev\\//}/partition\") umount \"$part\" parted \"$disk\" -a optimal -s resizepart \"$npart\" 100% yes | mkfs.ext4 -L \"$label\" -F -m 0 \"$part\" mount \"$part\" unset disk part npart label fi 2. \u7ec8\u7aef\u6267\u884c bash expand.sh ,\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002","title":"\u5b58\u50a8\u5361\u6269\u5bb9"},{"location":"Expand_Filesystem/#_1","text":"","title":"\u6811\u8393\u6d3e\u6269\u5bb9"},{"location":"Expand_Filesystem/#_2","text":"\u7531\u4e8e\u5728\u5236\u4f5c\u955c\u50cf\u8fc7\u7a0b\u4e2d\uff0c\u5bf9\u955c\u50cf\u8fdb\u884c\u4e86\u538b\u7f29\uff0c\u5982\u679c\u4f60\u53d1\u73b0\u6811\u8393\u6d3eSD\u5361\u6216\u8005eMMC\u7684\u53ef\u7528\u7a7a\u95f4\u5c0f\u4e8e\u5b9e\u9645SD\u5361\u6216\u8005eMMc\u7684\u5bb9\u91cf\uff0c\u4f60\u53ef\u80fd\u9700\u8981\u8fdb\u884c\u4ee5\u4e0b\u64cd\u4f5c\uff0c\u5bf9\u6811\u8393\u6d3e\u8fdb\u884c\u6269\u5bb9\u3002 \u5982\u679c\u4f60\u53d1\u73b0\u7cfb\u7edf\u5e76\u65e0raspi-config\u5de5\u5177\uff0c\u5219\u53ef\u4f7f\u7528\u65b9\u6cd5\u4e8c\uff08\u4f7f\u7528GParted\u5206\u533a\u5de5\u5177\uff09\u3002","title":"\u7b80\u4ecb"},{"location":"Expand_Filesystem/#raspi-config","text":"\u5982\u679c\u4f60\u4f7f\u7528\u76842023\u5e746\u6708\u4efd\u540e\u7684\u955c\u50cf\uff0c\u56e0\u589e\u52a0\u4e86\u7b2c\u4e09\u4e2a\u53ef\u8bfb\u5199\u7684\u5206\u533a\uff0c\u6b64\u65b9\u6cd5\u5df2\u7ecf\u4e0d\u9002\u7528\uff0c\u8bf7\u53c2\u8003\u65b9\u6848\u4e8c\u548c\u65b9\u6848\u4e09\u3002 1. \u6253\u5f00raspi-config\u7cfb\u7edf\u914d\u7f6e\u5de5\u5177 sudo raspi-config 2. \u9009\u62e9Advancd Options\uff1a 3. \u9009\u62e9Expand Filesystem\uff1a 4. Ok: 5. \u7ec8\u7aef\u6267\u884c resize2fs /dev/mmcblk0p2 \u6b64\u547d\u4ee4\u5373\u53ef\u770b\u5230SD\u5361\u5df2\u7ecf\u6269\u5bb9\u6210\u529f\u3002","title":"\u65b9\u6cd5\u4e00 \u4f7f\u7528raspi-config\u5de5\u5177"},{"location":"Expand_Filesystem/#gparted","text":"1. \u5c06\u70e7\u5f55\u597d\u955c\u50cf\u7684SD\u5361\u6216\u8005EMMc\u901a\u8fc7usb\u63a5\u5230\u7535\u8111\u4e0a\uff0c\u4ee5linux\u4e0bGParted\u5206\u533a\u5de5\u5177\u4e3a\u4f8b\uff0c\u5176\u5b83\u5e73\u53f0\u4e5f\u6709\u7c7b\u4f3c\u7684\u5206\u533a\u5de5\u5177\u3002\u6253\u5f00GParted\u8f6f\u4ef6\uff0c\u9009\u62e9SD\u5361\uff1a 2. \u89c2\u5bdf\u4e0a\u56feSD\u5361\u7684\u5206\u533a\u60c5\u51b5\uff0c\u53ef\u4ee5\u53d1\u73b0\u5728sdb3\u5206\u533a\u7684\u524d\u540e\u5404\u67092.01GB\u548c21.87GB\u7684\u7a7a\u95f4\u672a\u4f7f\u7528\uff0c\u8fd9\u90e8\u5206\u7a7a\u95f4\u5c31\u662f\u6211\u4eec\u8981\u6269\u5bb9\u7684\u7a7a\u95f4\u3002\u9009\u4e2dsdb3\u5206\u533a\uff0c\u70b9\u51fb\u8c03\u6574\u5927\u5c0f\u3002 3. \u53ef\u4ee5\u62d6\u52a8sdb3\u7684\u767d\u8272\u5206\u533a\u6269\u5927\u5230\u6700\u5de6\u548c\u6700\u53f3\uff0c\u6216\u8005\u586b\u5199\u201c\u4e4b\u524d\u7684\u53ef\u7528\u7a7a\u95f4\u201d\u4e3a\u201c0\u201d\uff0c\u201c\u65b0\u5927\u5c0f\u201d\u4e3a\u201c\u6700\u5927\u5927\u5c0f\u201d\u768425958\uff0c\u7136\u540e\u70b9\u51fb\u53f3\u4e0b\u89d2\u7684\u8c03\u6574\u5927\u5c0f\uff0c\u7136\u540e\u5f39\u51fa\u6765\u7684\u63d0\u9192\u70b9\u51fb\u786e\u8ba4\uff0c\u5373\u53ef\u770b\u5230sd\u7684\u6240\u6709\u672a\u4f7f\u7528\u7a7a\u95f4\u5168\u90e8\u7528\u4e0a\u4e86\u3002 4. \u5c06SD\u5361\u63d2\u5165\u8bbe\u5907\uff0c\u542f\u52a8\u5373\u53ef\u3002","title":"\u65b9\u6cd5\u4e8c \u4f7f\u7528GParted\u5206\u533a\u5de5\u5177"},{"location":"Expand_Filesystem/#_3","text":"\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM\u955c\u50cf\uff0c\u53ef\u4ee5\u5728KVM\u4e0a\u8fd0\u884c\u4e0b\u9762\u7684\u811a\u672c\uff0c\u6765\u81ea\u52a8\u6269\u5927\u7a7a\u95f4\u3002 1. \u7ec8\u7aef\u767b\u5f55\u5230KVM\u4e0a\uff0c\u786e\u8ba4\u7cfb\u7edf\u6709\u53ef\u8bfb\u5199\u6743\u9650\uff0c\u5728\u4efb\u610f\u8def\u5f84\u8fd0\u884c vim expand.sh ,\u5c06\u4e0b\u9762\u5185\u5bb9\u5199\u5165\u5230expand.sh\u4e2d. \u5982\u679c\u4f60\u662fv1,v2,v3\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u4e0b\u9762\u5185\u5bb9\uff1a #!/bin/bash set -x resize_mmcblk0p3() { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100% resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" \u5982\u679c\u4f60\u662fv4\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u4e0b\u9762\u5185\u5bb9\uff1a #!/bin/bash set -x resize_mmcblk0p1() { echo \"Resizing mmcblk0p1 partition...\" parted /dev/mmcblk0 resizepart 1 100% resize2fs /dev/mmcblk0p1 echo \"mmcblk0p1 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p1 echo \"Partition resizing completed.\" 2. \u7ec8\u7aef\u6267\u884c bash expand.sh ,\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002 \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM\u7684\u955c\u50cf\uff0c\u53ef\u4ee5\u5728KVM\u4e0a\u8fd0\u884c\u4e0b\u9762\u7684\u811a\u672c\uff0c\u6765\u81ea\u52a8\u6269\u5927\u7a7a\u95f4\u3002 1. \u7ec8\u7aef\u767b\u5f55\u5230KVM\u4e0a\uff0c\u786e\u8ba4\u7cfb\u7edf\u6709\u53ef\u8bfb\u5199\u6743\u9650\uff0c\u5728\u4efb\u610f\u8def\u5f84\u8fd0\u884c vim expand.sh ,\u5c06\u4e0b\u9762\u5185\u5bb9\u5199\u5165\u5230expand.sh\u4e2d. #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab; then part=$(grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}') # shellcheck disable=SC2206 splitted=(${part//=/ }) if [ \"${splitted[0]}\" == LABEL ]; then label=${splitted[1]} part=$(blkid -c /dev/null -L \"$label\") else label=PIMSD fi unset splitted disk=/dev/$(lsblk -no pkname \"$part\") npart=$(cat \"/sys/class/block/${part//\\/dev\\//}/partition\") umount \"$part\" parted \"$disk\" -a optimal -s resizepart \"$npart\" 100% yes | mkfs.ext4 -L \"$label\" -F -m 0 \"$part\" mount \"$part\" unset disk part npart label fi 2. \u7ec8\u7aef\u6267\u884c bash expand.sh ,\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002","title":"\u65b9\u6cd5\u4e09: \u4f7f\u7528\u811a\u672c"},{"location":"OLED-display/","text":"\u7b56\u7565 \u5728\u7248\u672c v1.5.0 \u4e4b\u540e, \u4e3a\u4e86\u907f\u514d OLED/LCD \u663e\u793a\u5c4f\u70e7\u5c4f\uff0c\u663e\u793a\u5c4f\u7684\u5f00\u542f\u65f6\u95f4\u4ec5\u6839\u636e\u5176\u914d\u7f6e\u8fdb\u884c\u63a7\u5236\u3002 \u914d\u7f6e // \u6240\u6709\u65f6\u95f4\u53c2\u6570\u5747\u4ee5\u79d2\u4e3a\u5355\u4f4d\uff0c\u4e14\u5fc5\u987b\u4e3a 5 \u7684\u6574\u6570\u500d\u3002 // \u914d\u7f6e\u6587\u4ef6\u8def\u5f84\u5728/mnt/exec/release/config/app.json \"display\":{ \"isActive\": true, \"mode\": 1, \"onBootTime\": 3600, \"cycleInterval\": 300, \"displayTime\": 30, } \u5f53 isActive : true \u6fc0\u6d3b\u663e\u793a\u5c4f \u3002\u5f53 \"isActive\": \"false\" \u65f6\uff0c\u663e\u793a\u5c4f\u5c06\u4e0d\u4f1a\u5de5\u4f5c\u3002 \u6240\u6709 BliKVM \u7248\u672c \u6a21\u5f0f \u63cf\u8ff0 0 \u59cb\u7ec8\u5f00\u542f\uff0c\u4e0d\u8003\u8651\u4efb\u4f55\u53c2\u6570 1 \u663e\u793a\u5c4f\u4fdd\u6301\u5f00\u542f onBootTime \u79d2\uff0c\u7136\u540e\u5173\u95ed\u3002\u53d6\u51b3\u4e8e \"onBootTime\" 2 \u6bcf\u4e2a cycleInterval \u5468\u671f\u5185\uff0c\u663e\u793a\u5c4f\u5f00\u542f displayTime \u79d2\uff0c\u7136\u540e\u5173\u95ed\u3002:rotating_light: \u53d6\u51b3\u4e8e \"cycleInterval\" \u548c \"displayTime\" \u4ec5 BliKVM v4 Allwinner \u7531\u4e8e v4 \u5177\u6709 sw1 \u6309\u94ae\uff0c\u5982\u679c\u8bbe\u7f6e\u6a21\u5f0f\u4e3a 1\u3002 \u884c\u4e3a\uff1a \u542f\u52a8\u65f6\uff1a\u663e\u793a\u5c4f\u5f00\u542f onBootTime \u79d2\uff0c\u7136\u540e\u81ea\u52a8\u5173\u95ed\u3002 \u6309\u4e0b\u6309\u94ae (sw1)\uff1a\u6309\u4e0b sw1 \u663e\u793a\u5c4f\u5f00\u542f displayTime \u79d2\u3002\u5982\u679c\u663e\u793a\u5c4f\u5df2\u7ecf\u5f00\u542f\uff0c\u6309\u4e0b sw1 \u5c06\u6ca1\u6709\u4efb\u4f55\u5f71\u54cd\u3002","title":"OLED\u663e\u793a\u5668"},{"location":"OLED-display/#_1","text":"\u5728\u7248\u672c v1.5.0 \u4e4b\u540e, \u4e3a\u4e86\u907f\u514d OLED/LCD \u663e\u793a\u5c4f\u70e7\u5c4f\uff0c\u663e\u793a\u5c4f\u7684\u5f00\u542f\u65f6\u95f4\u4ec5\u6839\u636e\u5176\u914d\u7f6e\u8fdb\u884c\u63a7\u5236\u3002","title":"\u7b56\u7565"},{"location":"OLED-display/#_2","text":"// \u6240\u6709\u65f6\u95f4\u53c2\u6570\u5747\u4ee5\u79d2\u4e3a\u5355\u4f4d\uff0c\u4e14\u5fc5\u987b\u4e3a 5 \u7684\u6574\u6570\u500d\u3002 // \u914d\u7f6e\u6587\u4ef6\u8def\u5f84\u5728/mnt/exec/release/config/app.json \"display\":{ \"isActive\": true, \"mode\": 1, \"onBootTime\": 3600, \"cycleInterval\": 300, \"displayTime\": 30, } \u5f53 isActive : true \u6fc0\u6d3b\u663e\u793a\u5c4f \u3002\u5f53 \"isActive\": \"false\" \u65f6\uff0c\u663e\u793a\u5c4f\u5c06\u4e0d\u4f1a\u5de5\u4f5c\u3002","title":"\u914d\u7f6e"},{"location":"OLED-display/#blikvm","text":"\u6a21\u5f0f \u63cf\u8ff0 0 \u59cb\u7ec8\u5f00\u542f\uff0c\u4e0d\u8003\u8651\u4efb\u4f55\u53c2\u6570 1 \u663e\u793a\u5c4f\u4fdd\u6301\u5f00\u542f onBootTime \u79d2\uff0c\u7136\u540e\u5173\u95ed\u3002\u53d6\u51b3\u4e8e \"onBootTime\" 2 \u6bcf\u4e2a cycleInterval \u5468\u671f\u5185\uff0c\u663e\u793a\u5c4f\u5f00\u542f displayTime \u79d2\uff0c\u7136\u540e\u5173\u95ed\u3002:rotating_light: \u53d6\u51b3\u4e8e \"cycleInterval\" \u548c \"displayTime\"","title":"\u6240\u6709 BliKVM \u7248\u672c"},{"location":"OLED-display/#blikvm-v4-allwinner","text":"\u7531\u4e8e v4 \u5177\u6709 sw1 \u6309\u94ae\uff0c\u5982\u679c\u8bbe\u7f6e\u6a21\u5f0f\u4e3a 1\u3002 \u884c\u4e3a\uff1a \u542f\u52a8\u65f6\uff1a\u663e\u793a\u5c4f\u5f00\u542f onBootTime \u79d2\uff0c\u7136\u540e\u81ea\u52a8\u5173\u95ed\u3002 \u6309\u4e0b\u6309\u94ae (sw1)\uff1a\u6309\u4e0b sw1 \u663e\u793a\u5c4f\u5f00\u542f displayTime \u79d2\u3002\u5982\u679c\u663e\u793a\u5c4f\u5df2\u7ecf\u5f00\u542f\uff0c\u6309\u4e0b sw1 \u5c06\u6ca1\u6709\u4efb\u4f55\u5f71\u54cd\u3002","title":"\u4ec5 BliKVM v4 Allwinner"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4-ZH/","text":"BliKVM v1 (RPI CM4) BliKVM v1\u662f\u4e00\u6b3e\u57fa\u4e8e\u6811\u8393\u6d3eCM4\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86 \u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406 \u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e \u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5 \u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1 \uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01 \u63a5\u53e3\u5b9a\u4e49 1 OTG \u7aef\u53e3 7 Micro SD \u5361\u69fd 1 OTG \u7aef\u53e3 7 Micro SD \u5361\u69fd 2 USB3.0 x2 8 \u72b6\u6001\u6307\u793a\u706f (\u7eff\u8272) 3 ATX \u63a7\u5236\u7aef\u53e3 9 \u7f51\u53e3 1000M 4 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 10 OLED \u663e\u793a\u5c4f 128x64 5 Type-C\u4f9b\u7535\u7aef\u53e3 5V3A 11 \u5929\u7ebf\u5b89\u88c5\u5b54 6 \u7535\u6e90\u6307\u793a\u706f (\u7ea2\u8272) \u53c2\u6570 \u53c2\u6570\u540d\u79f0 \u63cf\u8ff0 \u4f9b\u7535 5V 3A PWR IN \u7aef\u53e3 \u7aef\u53e3 HDMI IN HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 OTG \u6a21\u62df\u952e\u76d8\uff0c\u9f20\u6807\uff0c\u5927\u5bb9\u91cf\u5b58\u50a8\u5668\u6216\u5176\u4ed6USB\u8bbe\u5907 CN-ATX \u5f00\u5173\u673a\u88ab\u63a7\u7535\u8111\uff0c\u8bfb\u53d6\u88ab\u63a7\u7535\u8111\u72b6\u6001\u6307\u793a\u706f Micro SD \u5361\u69fd \u5b89\u88c5\u955c\u50cf\u5185\u5b58\u5361 PWR IN \u7aef\u53e3 5V3A \u7535\u6e90 \u663e\u793a\u548c\u6307\u793a\u706f LED \u6307\u793a\u706f \u7535\u6e90\u6307\u793a\u706f\uff08\u7ea2\u8272\uff09\uff0c\u72b6\u6001\u6307\u793a\u706f\uff08\u7eff\u8272\uff09 OLED \u663e\u793a\u5c4f OLED 128x64 0.96\u5bf8 \u89c6\u9891 \u5206\u8fa8\u7387 \u6700\u9ad8\u652f\u6301 1920x1200@60Hz \u7f16\u7801\u683c\u5f0f H.264, MJPEG \u6838\u5fc3 \u6a21\u5757 \u6811\u8393\u6d3eCM4\uff08\u81ea\u5907\uff09 \u529f\u8017 Up to 15W \u73af\u5883\u53c2\u6570 \u5de5\u4f5c\u6e29\u5ea6 0\u00b0C to 70\u00b0C \u5b58\u50a8\u6e29\u5ea6 -20\u00b0C to 60\u00b0C \u5c3a\u5bf8\u548c\u91cd\u91cf \u5c3a\u5bf8 120(L) x 70W) x 37(H) mm \u91cd\u91cf 0.45 kg \u5916\u5f62\u5c3a\u5bf8","title":"BliKVM v1 (RPI CM4)"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4-ZH/#blikvm-v1-rpi-cm4","text":"BliKVM v1\u662f\u4e00\u6b3e\u57fa\u4e8e\u6811\u8393\u6d3eCM4\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86 \u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406 \u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e \u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5 \u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1 \uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01","title":"BliKVM v1 (RPI CM4)"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4-ZH/#_1","text":"1 OTG \u7aef\u53e3 7 Micro SD \u5361\u69fd 1 OTG \u7aef\u53e3 7 Micro SD \u5361\u69fd 2 USB3.0 x2 8 \u72b6\u6001\u6307\u793a\u706f (\u7eff\u8272) 3 ATX \u63a7\u5236\u7aef\u53e3 9 \u7f51\u53e3 1000M 4 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 10 OLED \u663e\u793a\u5c4f 128x64 5 Type-C\u4f9b\u7535\u7aef\u53e3 5V3A 11 \u5929\u7ebf\u5b89\u88c5\u5b54 6 \u7535\u6e90\u6307\u793a\u706f (\u7ea2\u8272)","title":"\u63a5\u53e3\u5b9a\u4e49"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4-ZH/#_2","text":"\u53c2\u6570\u540d\u79f0 \u63cf\u8ff0 \u4f9b\u7535 5V 3A PWR IN \u7aef\u53e3 \u7aef\u53e3 HDMI IN HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 OTG \u6a21\u62df\u952e\u76d8\uff0c\u9f20\u6807\uff0c\u5927\u5bb9\u91cf\u5b58\u50a8\u5668\u6216\u5176\u4ed6USB\u8bbe\u5907 CN-ATX \u5f00\u5173\u673a\u88ab\u63a7\u7535\u8111\uff0c\u8bfb\u53d6\u88ab\u63a7\u7535\u8111\u72b6\u6001\u6307\u793a\u706f Micro SD \u5361\u69fd \u5b89\u88c5\u955c\u50cf\u5185\u5b58\u5361 PWR IN \u7aef\u53e3 5V3A \u7535\u6e90 \u663e\u793a\u548c\u6307\u793a\u706f LED \u6307\u793a\u706f \u7535\u6e90\u6307\u793a\u706f\uff08\u7ea2\u8272\uff09\uff0c\u72b6\u6001\u6307\u793a\u706f\uff08\u7eff\u8272\uff09 OLED \u663e\u793a\u5c4f OLED 128x64 0.96\u5bf8 \u89c6\u9891 \u5206\u8fa8\u7387 \u6700\u9ad8\u652f\u6301 1920x1200@60Hz \u7f16\u7801\u683c\u5f0f H.264, MJPEG \u6838\u5fc3 \u6a21\u5757 \u6811\u8393\u6d3eCM4\uff08\u81ea\u5907\uff09 \u529f\u8017 Up to 15W \u73af\u5883\u53c2\u6570 \u5de5\u4f5c\u6e29\u5ea6 0\u00b0C to 70\u00b0C \u5b58\u50a8\u6e29\u5ea6 -20\u00b0C to 60\u00b0C \u5c3a\u5bf8\u548c\u91cd\u91cf \u5c3a\u5bf8 120(L) x 70W) x 37(H) mm \u91cd\u91cf 0.45 kg","title":"\u53c2\u6570"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4-ZH/#_3","text":"","title":"\u5916\u5f62\u5c3a\u5bf8"},{"location":"atx-guide/","text":"ATXA guide 1. Introduction ATXA is an ATX adapter borad to manage the power of your computer. The product includes two modules A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable.Join to the Discord Community Chat for news, questions and support! ATXA_A ATXA_B 2. A-board A-board is connected to the Raspberry Pi. The following table is a typical connection method in BLIKVM and PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed 3. B-board The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B\u4e0e\u7535\u8111\u4e3b\u677f\u8fde\u63a5\u8bf4\u660e \u6839\u636e\u7535\u8111\u4e3b\u677f\u8bf4\u660e\uff0c\u9996\u5148\u627e\u5230\u4e3b\u677f\u4e0aATX\u529f\u80fd\u76f8\u5173\u5f15\u811a\u4f4d\u7f6e\uff0c\u62d4\u4e0b\u4e3b\u677f\u5df2\u7ecf\u63a5\u597d\u7684ATX\u7ebf\uff0c\u62d4\u4e0b\u540e\u7535\u8111\u7684\u7535\u6e90\u6309\u94ae\u5c06\u5931\u53bb\u4f5c\u7528\u3002ATXA-B\u4e3b\u677f\u5171\u6709\u4e24\u63928PIN\u5f15\u811a\uff0c\u4e24\u6392\u5f15\u811a\u529f\u80fd\u5b8c\u5168\u76f8\u540c\u4f7f\u7528\u65f6\u65e0\u9700\u533a\u5206\u3002\u5176\u4e2d\u4e00\u6392\u5f15\u811a\u7528\u4e8eKVM\u63a7\u5236ATX\u76f8\u5173\u529f\u80fd\uff0c\u53e6\u4e00\u6392\u5f15\u811a\u63a5\u4e3b\u677f\u4e0a\u62d4\u4e0b\u6765\u7684ATX\u675c\u90a6\u5934\uff0c\u4fdd\u6301\u539f\u6709\u673a\u7bb1\u7535\u6e90\u6309\u94ae\u529f\u80fd\u3002\u6839\u636e\u4e3b\u677f\u548cATX-B\u4e0a\u7684\u5177\u4f53\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u6bcf\u6839\u7ebf\u7684\u8fde\u63a5\uff0c\u8fde\u63a5\u5173\u7cfb\u53ef\u4ee5\u53c2\u8003\u4e0b\u56fe\uff1a 4.Mechanical Diagram 5.Test video youtube\uff1a ATX 6.More link Purchase\uff1a ATX","title":"ATX\u7528\u6237\u624b\u518c"},{"location":"atx-guide/#atxa-guide","text":"","title":"ATXA guide"},{"location":"atx-guide/#1-introduction","text":"ATXA is an ATX adapter borad to manage the power of your computer. The product includes two modules A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable.Join to the Discord Community Chat for news, questions and support! ATXA_A ATXA_B","title":"1. Introduction"},{"location":"atx-guide/#2-a-board","text":"A-board is connected to the Raspberry Pi. The following table is a typical connection method in BLIKVM and PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed","title":"2. A-board"},{"location":"atx-guide/#3-b-board","text":"The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B\u4e0e\u7535\u8111\u4e3b\u677f\u8fde\u63a5\u8bf4\u660e \u6839\u636e\u7535\u8111\u4e3b\u677f\u8bf4\u660e\uff0c\u9996\u5148\u627e\u5230\u4e3b\u677f\u4e0aATX\u529f\u80fd\u76f8\u5173\u5f15\u811a\u4f4d\u7f6e\uff0c\u62d4\u4e0b\u4e3b\u677f\u5df2\u7ecf\u63a5\u597d\u7684ATX\u7ebf\uff0c\u62d4\u4e0b\u540e\u7535\u8111\u7684\u7535\u6e90\u6309\u94ae\u5c06\u5931\u53bb\u4f5c\u7528\u3002ATXA-B\u4e3b\u677f\u5171\u6709\u4e24\u63928PIN\u5f15\u811a\uff0c\u4e24\u6392\u5f15\u811a\u529f\u80fd\u5b8c\u5168\u76f8\u540c\u4f7f\u7528\u65f6\u65e0\u9700\u533a\u5206\u3002\u5176\u4e2d\u4e00\u6392\u5f15\u811a\u7528\u4e8eKVM\u63a7\u5236ATX\u76f8\u5173\u529f\u80fd\uff0c\u53e6\u4e00\u6392\u5f15\u811a\u63a5\u4e3b\u677f\u4e0a\u62d4\u4e0b\u6765\u7684ATX\u675c\u90a6\u5934\uff0c\u4fdd\u6301\u539f\u6709\u673a\u7bb1\u7535\u6e90\u6309\u94ae\u529f\u80fd\u3002\u6839\u636e\u4e3b\u677f\u548cATX-B\u4e0a\u7684\u5177\u4f53\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u6bcf\u6839\u7ebf\u7684\u8fde\u63a5\uff0c\u8fde\u63a5\u5173\u7cfb\u53ef\u4ee5\u53c2\u8003\u4e0b\u56fe\uff1a","title":"3. B-board"},{"location":"atx-guide/#4mechanical-diagram","text":"","title":"4.Mechanical Diagram"},{"location":"atx-guide/#5test-video","text":"youtube\uff1a ATX","title":"5.Test video"},{"location":"atx-guide/#6more-link","text":"Purchase\uff1a ATX","title":"6.More link"},{"location":"atx/","text":"ATX\u63a7\u5236\u677f \u4e3a\u4e86\u7ba1\u7406\u60a8\u7684\u8ba1\u7b97\u673a\u7684\u7535\u6e90\uff0c\u60a8\u9700\u8981\u5728\u673a\u7bb1\u5185\u5b89\u88c5\u4e00\u4e2aATX\u9002\u914d\u677f\uff0c\u5e76\u5c06\u5176\u8fde\u63a5\u5230\u4e3b\u677f\u4e0a\uff08\u4e3a\u4e86KVM\u76f4\u63a5\u901a\u8fc7ATX\u63a7\u5236\u5f00\u5173\u673a\uff09\u3002\u6709\u4e00\u6839\u4ece\u4e3b\u677f\u5230ATX\u9002\u914d\u677f\u7684\u6bcd\u5bf9\u6bcd\u7ebf\u7f06\uff0c\u4ee5\u53ca\u4e00\u4e2a\u4eceATX\u9002\u914d\u677f\u5230\u524d\u9762\u677f\u7684\u516c\u5bf9\u6bcd\u7ebf\u7f06\uff08\u4e3a\u4e86\u4f7f\u673a\u7bb1\u7684\u5f00\u5173\u673a\u6309\u94ae\u4ecd\u7136\u6709\u6548\uff09\u3002ATX\u9002\u914d\u677f\u4e0a\u6709\u4e2a\u63a5\u53e3(TO CASE, TO MB)\uff0c\u4e24\u4e2a\u63a5\u53e3\u529f\u80fd\u4e00\u6a21\u4e00\u6837\uff0c\u4f7f\u7528\u65f6\u53ef\u4ee5\u4e0d\u7528\u533a\u5206\u3002 \u7b14\u8bb0\u672c\u7535\u8111\u4e0d\u517c\u5bb9ATX\uff0c\u56e0\u4e3a\u5b83\u4eec\u7f3a\u5c11\u6240\u9700\u7684ATX\u5f15\u811a\uff0c\u6b64\u65b9\u6cd5\u4ec5\u9002\u7528\u4e8ePC\u670d\u52a1\u5668\u548c\u53f0\u5f0f\u673a\u3002 \u8be6\u7ec6\u8bf4\u660e 1. \u5c06\u4e24\u6839\u7ebf\u7f06\u8fde\u63a5\u5230ATX\u9002\u914d\u677f, \u4e3a\u4e86\u56fa\u5b9aATX\u9002\u914d\u677f\u5728\u673a\u7bb1\u4e2d\uff0c\u60a8\u53ef\u4ee5\u9009\u62e9\u4f7f\u7528\u6321\u677f\u5c06ATX\u9002\u914d\u677f\u5b89\u88c5\u5728PCIe\u63d2\u69fd\u4e0a\u3002 Example 2. \u627e\u5230\u8d1f\u8d23\u8fde\u63a5\u673a\u7bb1\u524d\u9762\u677f\u6309\u94ae\u548cLED\u7684\u4e3b\u677f\u5f15\u811a\uff0c\u5e76\u5c06\u5176\u62d4\u51fa\u3002\u901a\u5e38\u4e3b\u677f\u4e0a\u7684\u7ebf\u7f06\u548c\u8fde\u63a5\u5668\u90fd\u6709\u6807\u8bc6\u3002\u5982\u679c\u60a8\u4e0d\u786e\u5b9a\uff0c\u53ef\u4ee5\u67e5\u9605\u60a8\u4e3b\u677f\u7684\u6587\u6863\u3002 Example 3. \u8fde\u63a5\u524d\u9762\u677f\u7684\u675c\u90a6\u6bcd\u5934\u548cATX\u7ebf\u7f06\u7684\u675c\u90a6\u516c\u5934\uff0c\u6309\u7167\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u8fde\u63a5\uff0c\u6ce8\u610f\u6807\u7b7e\u548c\u6781\u6027\uff08+\u6216-\uff09\u3002 Example 4. \u4f7f\u7528\u76f8\u540c\u7684\u65b9\u5f0f\uff0c\u5c06ATX\u677f\u7684\u6bcd\u5f15\u811a\u8fde\u63a5\u5230\u4e3b\u677f\u7684\u8fde\u63a5\u5668\u4e0a\u3002\u67e5\u9605\u60a8\u4e3b\u677f\u7684\u6587\u6863\u4ee5\u4e86\u89e3\u4e3b\u677f\u4e0a\u7684\u54ea\u4e2a\u5f15\u811a\u8fde\u63a5\u5230ATX\u9002\u914d\u677f\u7684\u54ea\u4e2a\u5f15\u811a\u3002\u6709\u65f6\u8fd9\u4e9b\u4fe1\u606f\u4f1a\u5370\u5728\u4e3b\u677f\u4e0a\u3002 Example 5. \u5c06ATX\u677f\u5b89\u88c5\u5230\u673a\u7bb1\u7684PCI\u63d2\u69fd\u4e2d\uff0c\u5e76\u7528\u87ba\u9489\u56fa\u5b9a\uff0c\u6216\u6839\u636e\u60a8\u7684\u559c\u597d\u4f7f\u7528\u5176\u4ed6\u5b89\u88c5\u65b9\u6cd5\u3002 Example 6. \u5c06\u7ebf\u7f06\u6574\u7406\u6210\u65b9\u4fbf\u7684\u65b9\u5f0f\uff0c\u5e76\u5728\u9700\u8981\u65f6\u56fa\u5b9a\u5b83\u4eec\u3002\u786e\u4fdd\u7ebf\u7f06\u4e0d\u4e0e\u673a\u7bb1\u5185\u7684\u4efb\u4f55\u98ce\u6247\u63a5\u89e6\u3002\u4f7f\u7528\u4ee5\u592a\u7f51\u7ebf\u5c06ATX\u677f\u4e0eBliKVM\u7684ATX\u63a5\u53e3\u8fde\u63a5\u8d77\u6765\u3002\u81f3\u6b64ATX\u9002\u914d\u677f\u786c\u4ef6\u90e8\u5206\u8fde\u63a5\u5df2\u5b8c\u6210\u3002","title":"ATX\u63a7\u5236\u677f"},{"location":"atx/#atx","text":"\u4e3a\u4e86\u7ba1\u7406\u60a8\u7684\u8ba1\u7b97\u673a\u7684\u7535\u6e90\uff0c\u60a8\u9700\u8981\u5728\u673a\u7bb1\u5185\u5b89\u88c5\u4e00\u4e2aATX\u9002\u914d\u677f\uff0c\u5e76\u5c06\u5176\u8fde\u63a5\u5230\u4e3b\u677f\u4e0a\uff08\u4e3a\u4e86KVM\u76f4\u63a5\u901a\u8fc7ATX\u63a7\u5236\u5f00\u5173\u673a\uff09\u3002\u6709\u4e00\u6839\u4ece\u4e3b\u677f\u5230ATX\u9002\u914d\u677f\u7684\u6bcd\u5bf9\u6bcd\u7ebf\u7f06\uff0c\u4ee5\u53ca\u4e00\u4e2a\u4eceATX\u9002\u914d\u677f\u5230\u524d\u9762\u677f\u7684\u516c\u5bf9\u6bcd\u7ebf\u7f06\uff08\u4e3a\u4e86\u4f7f\u673a\u7bb1\u7684\u5f00\u5173\u673a\u6309\u94ae\u4ecd\u7136\u6709\u6548\uff09\u3002ATX\u9002\u914d\u677f\u4e0a\u6709\u4e2a\u63a5\u53e3(TO CASE, TO MB)\uff0c\u4e24\u4e2a\u63a5\u53e3\u529f\u80fd\u4e00\u6a21\u4e00\u6837\uff0c\u4f7f\u7528\u65f6\u53ef\u4ee5\u4e0d\u7528\u533a\u5206\u3002 \u7b14\u8bb0\u672c\u7535\u8111\u4e0d\u517c\u5bb9ATX\uff0c\u56e0\u4e3a\u5b83\u4eec\u7f3a\u5c11\u6240\u9700\u7684ATX\u5f15\u811a\uff0c\u6b64\u65b9\u6cd5\u4ec5\u9002\u7528\u4e8ePC\u670d\u52a1\u5668\u548c\u53f0\u5f0f\u673a\u3002","title":"ATX\u63a7\u5236\u677f"},{"location":"atx/#_1","text":"1. \u5c06\u4e24\u6839\u7ebf\u7f06\u8fde\u63a5\u5230ATX\u9002\u914d\u677f, \u4e3a\u4e86\u56fa\u5b9aATX\u9002\u914d\u677f\u5728\u673a\u7bb1\u4e2d\uff0c\u60a8\u53ef\u4ee5\u9009\u62e9\u4f7f\u7528\u6321\u677f\u5c06ATX\u9002\u914d\u677f\u5b89\u88c5\u5728PCIe\u63d2\u69fd\u4e0a\u3002 Example 2. \u627e\u5230\u8d1f\u8d23\u8fde\u63a5\u673a\u7bb1\u524d\u9762\u677f\u6309\u94ae\u548cLED\u7684\u4e3b\u677f\u5f15\u811a\uff0c\u5e76\u5c06\u5176\u62d4\u51fa\u3002\u901a\u5e38\u4e3b\u677f\u4e0a\u7684\u7ebf\u7f06\u548c\u8fde\u63a5\u5668\u90fd\u6709\u6807\u8bc6\u3002\u5982\u679c\u60a8\u4e0d\u786e\u5b9a\uff0c\u53ef\u4ee5\u67e5\u9605\u60a8\u4e3b\u677f\u7684\u6587\u6863\u3002 Example 3. \u8fde\u63a5\u524d\u9762\u677f\u7684\u675c\u90a6\u6bcd\u5934\u548cATX\u7ebf\u7f06\u7684\u675c\u90a6\u516c\u5934\uff0c\u6309\u7167\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u8fde\u63a5\uff0c\u6ce8\u610f\u6807\u7b7e\u548c\u6781\u6027\uff08+\u6216-\uff09\u3002 Example 4. \u4f7f\u7528\u76f8\u540c\u7684\u65b9\u5f0f\uff0c\u5c06ATX\u677f\u7684\u6bcd\u5f15\u811a\u8fde\u63a5\u5230\u4e3b\u677f\u7684\u8fde\u63a5\u5668\u4e0a\u3002\u67e5\u9605\u60a8\u4e3b\u677f\u7684\u6587\u6863\u4ee5\u4e86\u89e3\u4e3b\u677f\u4e0a\u7684\u54ea\u4e2a\u5f15\u811a\u8fde\u63a5\u5230ATX\u9002\u914d\u677f\u7684\u54ea\u4e2a\u5f15\u811a\u3002\u6709\u65f6\u8fd9\u4e9b\u4fe1\u606f\u4f1a\u5370\u5728\u4e3b\u677f\u4e0a\u3002 Example 5. \u5c06ATX\u677f\u5b89\u88c5\u5230\u673a\u7bb1\u7684PCI\u63d2\u69fd\u4e2d\uff0c\u5e76\u7528\u87ba\u9489\u56fa\u5b9a\uff0c\u6216\u6839\u636e\u60a8\u7684\u559c\u597d\u4f7f\u7528\u5176\u4ed6\u5b89\u88c5\u65b9\u6cd5\u3002 Example 6. \u5c06\u7ebf\u7f06\u6574\u7406\u6210\u65b9\u4fbf\u7684\u65b9\u5f0f\uff0c\u5e76\u5728\u9700\u8981\u65f6\u56fa\u5b9a\u5b83\u4eec\u3002\u786e\u4fdd\u7ebf\u7f06\u4e0d\u4e0e\u673a\u7bb1\u5185\u7684\u4efb\u4f55\u98ce\u6247\u63a5\u89e6\u3002\u4f7f\u7528\u4ee5\u592a\u7f51\u7ebf\u5c06ATX\u677f\u4e0eBliKVM\u7684ATX\u63a5\u53e3\u8fde\u63a5\u8d77\u6765\u3002\u81f3\u6b64ATX\u9002\u914d\u677f\u786c\u4ef6\u90e8\u5206\u8fde\u63a5\u5df2\u5b8c\u6210\u3002","title":"\u8be6\u7ec6\u8bf4\u660e"},{"location":"bliswitch-v1-guide/","text":"BliKVM switch v1 KVM\u5207\u6362\u5668\u624b\u518c BliKVM-Switch-V1.0\u5b9e\u9645\u4f7f\u7528\u548c\u6d4b\u8bd5\u89c6\u9891\uff0c\u652f\u6301BliKVM\u548cPiKVM \u7b80\u4ecb BliKVM-Switch-V1.0\u4e3a\u56db\u901a\u9053HDMI+USB\u5207\u6362\u5668\uff0c\u652f\u6301\u673a\u5668\u6309\u952e\u5207\u6362\uff0c\u684c\u9762\u63a7\u5236\u5668\u5207\u6362\uff0cKVM\u8fdc\u7a0b\u5207\u6362\uff0c3\u79cd\u5207\u6362\u6a21\u5f0f\u3002\u5207\u6362\u5668\u672c\u8eab\u6700\u9ad8\u652f\u63014K@60HZ\u7684\u8f93\u5165\uff0c\u5373\u63d2\u5373\u7528\uff0c\u514d\u9a71\u52a8\u3002 BliKVM-Switch-V1.0\u4f7f\u7528\u548cXH-HK4401\u76f8\u540c\u7684\u786c\u4ef6\u65b9\u6848,AG7210 HDMI\u5207\u6362\u82af\u7247\u6700\u9ad8\u652f\u6301\u52304K@60Hz\uff0cCH444G USB\u5207\u6362\u82af\u7247\u652f\u6301USB2.0\u3002\u4e0d\u540c\u7684\u662fBliKVM-Switch-V1.0\u914d\u5907\u6709KVM USB cable,\u53ef\u4ee5\u901a\u8fc7KVM USB cable\u8fde\u63a5BliKVM-Switch-V1.0,\u5b9e\u73b0\u5bf9KVM\u7aef\u53e3\u7684\u9009\u62e9\u3002BliKVM-Switch-V1.0\u9002\u914dBliKVM\u548cPiKVM\u3002 \u6ce8\u610f\u4e8b\u9879 switch\u53ef\u4ee5\u76f4\u63a5\u4ece\u8f93\u5165\u7535\u8111\u7684USB\u53d6\u7535\uff0c\u5373\u4e00\u822c\u4e0d\u9700\u8981\u7ed9switch\u4f9b\u7535\uff0c\u5373\u53ef\u6b63\u5e38\u5de5\u4f5c\uff1b \u82e5\u88ab\u63a7\u7535\u8111\u7684USB\u4f9b\u7535\u65e0\u6cd5\u4f7fswitch\u5de5\u4f5c\uff0c\u53ef\u4ee5\u5bf9switch\u8fdb\u884c\u5355\u72ec\u4f9b\u7535\u4f7f\u7528\uff1b switch\u5957\u88c5\u53ea\u63d0\u4f9b\u4e86USB\u7535\u6e90\u7ebf\uff0c\u5e76\u6ca1\u6709\u63d0\u4f9b\u7535\u6e90\u9002\u914d\u5668\uff0c\u9700\u8981\u5ba2\u6237\u81ea\u884c\u914d\u7f6e\u7535\u6e90\u9002\u914d\u5668\uff085V\uff09\uff1b \u684c\u9762\u63a7\u5236\u5668 \u53ef\u4ee5\u901a\u8fc7USB\u7535\u7f06\u63a7\u5236\u5207\u6362\uff0c\u5bf9\u4e8e\u4e0d\u4f7f\u7528KVM\u7684\u5ba2\u6237\uff0c\u5f53\u60a8\u5728\u8bbe\u5907\u65c1\u8fb9\u65f6\uff0c\u8fd9\u662f\u9664\u4f7f\u7528switch\u8bbe\u5907\u4e0a\u6309\u94ae\u5207\u6362\u4e4b\u5916\u7684\u53e6\u4e00\u79cd\u5207\u6362\u65b9\u5f0f\uff1b HDMI\u8f93\u5165\u6700\u9ad8\u652f\u6301 4096x2160/60Hz \uff1b 4K 60Hz\u7684HDMI\u8f93\u5165, \u529f\u7387\u5927\u6982\u662f200mW; \u63a5\u53e3\u793a\u610f\u56fe \u8fd9\u91cc\u9700\u8981\u4e24\u6839USB\u7ebf\uff0c\u8fde\u63a5switch\u548ckvm\u786c\u4ef6\uff0c\u4e00\u6839\u7528\u4e8e\u4f20\u8f93\u63a7\u5236\u5207\u6362\u901a\u9053\u4fe1\u606f\uff0c\u4e00\u6839\u7528\u4e8e\u4f20\u8f93\u9f20\u6807\u952e\u76d8\u6570\u636e\uff0c\u5177\u4f53\u8fde\u63a5\u53ef\u4ee5\u53c2\u8003\u9762\u8bf4\u660e\u3002 \u6b63\u9762\u548c\u53cd\u9762\u63a5\u53e3\u793a\u610f\u56fe\uff0c\u53f3\u4fa7\u56fe\u4e2d\u7684control\u63a5\u53e3\u5373\u4e3a\u8fdc\u7a0b\u63a7\u5236\u63a5\u53e3, \u4e00\u5934\u4e3aUSB-A\uff0c\u53e6\u4e00\u5934\u4e3amicro usb\u5e76\u4e14\u6807\u7b7e\u5e26\u6709kvm\u5b57\u6837\u7684\u7ebf\uff0c\u4e3a\u63a7\u5236\u7ebf\uff0c\u5176\u4e2dmicro usb\u53e3\u4e0eswitch\u7684control\u63a5\u53e3\u8fde\u63a5\uff0cUSB-A\u63a5\u53e3\u4e0eKVM\u7684USB\u53e3\u8fde\u63a5\u3002 \u4fa7\u9762\u63a5\u53e3\u793a\u610f\u56fe \u8bbe\u5907\u8fde\u63a5\u793a\u610f\u56fe \u8f6f\u4ef6\u914d\u7f6e !!! info \"\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM\u8f6f\u4ef6\uff0c\u5728BliKVM\u542f\u52a8\u524d\u5148\u628aswitch\u901a\u7535\u5e76\u63a5\u597d\u7ebf\uff0c\u901a\u8fc7\u7ec8\u7aef\u786e\u8ba4switch\u63d2\u5165BliKVM\u540e\uff0c\u8bc6\u522b\u5230\u7684\u8bbe\u5907\u63cf\u8ff0\u7b26\u540d\u79f0\uff0c\u5982 /dev/ttyUSB0 ,\u7136\u540e\u7f16\u8f91 /usr/bin/blikvm/package.json \u4e2d\u7684 switch_handle \u5b57\u6bb5\uff0c\u5c06switch_enable\u8d4b\u503c\u4e3a1, switch_path\u8d4b\u503c\u4e3a /dev/ttyUSB0 \uff0c\u7136\u540e\u91cd\u542fBliKVM\u5373\u53ef\u3002 \u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u5148\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u7cfb\u7edf\u53d8\u4e3a\u53ef\u8bfb\u5199\u7cfb\u7edf\u3002\u7f16\u8f91\u914d\u7f6e\u6587\u4ef6\u53ef\u4ee5\u53c2\u8003\u4e0b\u547d\u4ee4: sudo vim /usr/bin/blikvm/package.json \u70b9\u51fb\u5de6\u4e0b\u89d2\u7684MORE\uff0c\u627e\u5230BliKVM switch\u8fd9\u4e00\u680f\uff0c\u8fdb\u884c\u5207\u6362\u9009\u62e9\u5373\u53ef\u3002\u6ce8\u610f\u5bf9\u5e94\u901a\u9053\u84dd\u8272\u5c0f\u70b9\u95ea\u52a8\u8868\u793a\u8bc6\u522b\u5230\u4e86switch\u63d2\u5165\uff0c\u5e76\u4e14\u6b63\u5904\u4e8e\u5f53\u524d\u901a\u9053\uff0c\u82e5\u65e0\u84dd\u8272\u5c0f\u70b9\u5219\u8868\u793a\u672a\u8bc6\u522b\u5230switch\u63d2\u5165\u3002\" \u82e5\u60a8\u4f7f\u7528\u7684PiKVM\u8f6f\u4ef6\uff0c\u8bf7\u6309\u7167\u4e0b\u9762\u7684\u8bf4\u660e\u8fdb\u884c\u914d\u7f6e \u901a\u8fc7SSH\u767b\u9646PiKVM\uff0c\u7528\u6237\u540d\u548c\u5bc6\u7801\u5747\u4e3aroot; \u7ec8\u7aef\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u7cfb\u7edf\u6539\u4e3a\u53ef\u8bfb\u5199\u7cfb\u7edf; \u7f16\u8f91 /etc/kvmd/override.yaml \u6b64\u6587\u4ef6\uff0c\u4f7f\u6539\u6587\u4ef6\u5305\u542b\u4e0b\u9762\u7684\u5185\u5bb9\uff0c\u5373\u5728\u539f\u6709\u5185\u5bb9\u540e\u8ffd\u52a0. kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] !!! warning \"\u4e0a\u8ff0\u914d\u7f6e\u57fa\u4e8e2022 pikvm\u56fe\u50cf\u3002\u5982\u679c\u60a8\u4f7f\u7528\u7684\u662f\u6700\u65b0\u7684pikvm\u6620\u50cf\u6216\u6700\u65b0\u7684\u8f6f\u4ef6\u7248\u672c\uff0c\u8bf7\u7f16\u8f91\u6587\u4ef6/etc/kvmd/override.yaml\u5e76\u6dfb\u52a0\u884c\uff1aprotocol:2\uff0c\u4f8b\u5b50\u5982\u4e0b:\" kvmd: gpio: drivers: hk: type: xh_hk4401 protocol: 2 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk ... \u7ec8\u7aef\u4f7f\u7528 ro \u547d\u4ee4\u5c06\u7cfb\u7edf\u91cd\u65b0\u8bbe\u7f6e\u4e3a\u53ea\u8bfb\u7cfb\u7edf\uff1b \u7ec8\u7aef\u4f7f\u7528 systemctl restart kvmd \u91cd\u542f\u670d\u52a1\u3002 \u8fdb\u5165PiKVM web\u754c\u9762\uff0c\u5e76\u5355\u51fb\u201cGPIO\u201d\u83dc\u5355\u3002\u60a8\u5e94\u8be5\u770b\u52304\u4e2a\u8f93\u5165\uff0c\u5176\u4e2d\u4e00\u4e2a\u8f93\u5165\u6709\u4e00\u4e2a\u7eff\u8272\u5706\u5708\uff0c\u8868\u793a\u5f53\u524d\u5df2\u9009\u4e2d\u3002\u5355\u51fb\u5176\u4ed6\u8f93\u5165\u4ee5\u66f4\u6539\u9009\u5b9a\u7684\u4e3b\u673a\u3002 \u63a7\u5236\u534f\u8bae \u82e5\u60a8\u5e0c\u671b\u5c06blicube\u7684switch\u7528\u5728\u5176\u5b83\u5e73\u53f0\u4e0a\uff0c\u8bf7\u53c2\u8003\u4e0b\u9762\u7684\u534f\u8bae \u901a\u4fe1\u6ce2\u7279\u7387\u4e3a19200 \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW1\\r\\nG01gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW2\\r\\nG02gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW3\\r\\nG03gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW4\\r\\nG04gA switch\u8fd4\u56de\u5f53\u524d\u6240\u5728\u901a\u9053\u6d88\u606f\u4e3a: G01gA , G02gA , G03gA , G04gA \u53d1\u8d27\u6e05\u5355 \u4ea7\u54c1 \u6570\u91cf \u5907\u6ce8\uff5c KVM Switch\u5207\u6362\u5668\uff084\u901a\u9053) 1 110mm * 60mm * 33mm USB\u684c\u9762\u63a7\u5236\u5668 1 USB\u6570\u636e\u7ebf 4 \u957f\u5ea6: 1.2m HDMI\uff08\u6807\u51c6\u63a5\u5934\uff09\u7ebf 4 \u957f\u5ea6: 1.5m USB\u7535\u6e90\u7ebf 1 \u957f\u5ea6: 0.8m KVM USB\u7ebf 1 \u957f\u5ea6: 1.5m USB\u684c\u9762\u63a7\u5236\u7ebf 1 \u957f\u5ea6: 1m","title":"switchV1\u5207\u6362\u5668\u624b\u518c"},{"location":"bliswitch-v1-guide/#blikvm-switch-v1-kvm","text":"BliKVM-Switch-V1.0\u5b9e\u9645\u4f7f\u7528\u548c\u6d4b\u8bd5\u89c6\u9891\uff0c\u652f\u6301BliKVM\u548cPiKVM","title":"BliKVM switch v1 KVM\u5207\u6362\u5668\u624b\u518c"},{"location":"bliswitch-v1-guide/#_1","text":"BliKVM-Switch-V1.0\u4e3a\u56db\u901a\u9053HDMI+USB\u5207\u6362\u5668\uff0c\u652f\u6301\u673a\u5668\u6309\u952e\u5207\u6362\uff0c\u684c\u9762\u63a7\u5236\u5668\u5207\u6362\uff0cKVM\u8fdc\u7a0b\u5207\u6362\uff0c3\u79cd\u5207\u6362\u6a21\u5f0f\u3002\u5207\u6362\u5668\u672c\u8eab\u6700\u9ad8\u652f\u63014K@60HZ\u7684\u8f93\u5165\uff0c\u5373\u63d2\u5373\u7528\uff0c\u514d\u9a71\u52a8\u3002 BliKVM-Switch-V1.0\u4f7f\u7528\u548cXH-HK4401\u76f8\u540c\u7684\u786c\u4ef6\u65b9\u6848,AG7210 HDMI\u5207\u6362\u82af\u7247\u6700\u9ad8\u652f\u6301\u52304K@60Hz\uff0cCH444G USB\u5207\u6362\u82af\u7247\u652f\u6301USB2.0\u3002\u4e0d\u540c\u7684\u662fBliKVM-Switch-V1.0\u914d\u5907\u6709KVM USB cable,\u53ef\u4ee5\u901a\u8fc7KVM USB cable\u8fde\u63a5BliKVM-Switch-V1.0,\u5b9e\u73b0\u5bf9KVM\u7aef\u53e3\u7684\u9009\u62e9\u3002BliKVM-Switch-V1.0\u9002\u914dBliKVM\u548cPiKVM\u3002 \u6ce8\u610f\u4e8b\u9879 switch\u53ef\u4ee5\u76f4\u63a5\u4ece\u8f93\u5165\u7535\u8111\u7684USB\u53d6\u7535\uff0c\u5373\u4e00\u822c\u4e0d\u9700\u8981\u7ed9switch\u4f9b\u7535\uff0c\u5373\u53ef\u6b63\u5e38\u5de5\u4f5c\uff1b \u82e5\u88ab\u63a7\u7535\u8111\u7684USB\u4f9b\u7535\u65e0\u6cd5\u4f7fswitch\u5de5\u4f5c\uff0c\u53ef\u4ee5\u5bf9switch\u8fdb\u884c\u5355\u72ec\u4f9b\u7535\u4f7f\u7528\uff1b switch\u5957\u88c5\u53ea\u63d0\u4f9b\u4e86USB\u7535\u6e90\u7ebf\uff0c\u5e76\u6ca1\u6709\u63d0\u4f9b\u7535\u6e90\u9002\u914d\u5668\uff0c\u9700\u8981\u5ba2\u6237\u81ea\u884c\u914d\u7f6e\u7535\u6e90\u9002\u914d\u5668\uff085V\uff09\uff1b \u684c\u9762\u63a7\u5236\u5668 \u53ef\u4ee5\u901a\u8fc7USB\u7535\u7f06\u63a7\u5236\u5207\u6362\uff0c\u5bf9\u4e8e\u4e0d\u4f7f\u7528KVM\u7684\u5ba2\u6237\uff0c\u5f53\u60a8\u5728\u8bbe\u5907\u65c1\u8fb9\u65f6\uff0c\u8fd9\u662f\u9664\u4f7f\u7528switch\u8bbe\u5907\u4e0a\u6309\u94ae\u5207\u6362\u4e4b\u5916\u7684\u53e6\u4e00\u79cd\u5207\u6362\u65b9\u5f0f\uff1b HDMI\u8f93\u5165\u6700\u9ad8\u652f\u6301 4096x2160/60Hz \uff1b 4K 60Hz\u7684HDMI\u8f93\u5165, \u529f\u7387\u5927\u6982\u662f200mW;","title":"\u7b80\u4ecb"},{"location":"bliswitch-v1-guide/#_2","text":"\u8fd9\u91cc\u9700\u8981\u4e24\u6839USB\u7ebf\uff0c\u8fde\u63a5switch\u548ckvm\u786c\u4ef6\uff0c\u4e00\u6839\u7528\u4e8e\u4f20\u8f93\u63a7\u5236\u5207\u6362\u901a\u9053\u4fe1\u606f\uff0c\u4e00\u6839\u7528\u4e8e\u4f20\u8f93\u9f20\u6807\u952e\u76d8\u6570\u636e\uff0c\u5177\u4f53\u8fde\u63a5\u53ef\u4ee5\u53c2\u8003\u9762\u8bf4\u660e\u3002 \u6b63\u9762\u548c\u53cd\u9762\u63a5\u53e3\u793a\u610f\u56fe\uff0c\u53f3\u4fa7\u56fe\u4e2d\u7684control\u63a5\u53e3\u5373\u4e3a\u8fdc\u7a0b\u63a7\u5236\u63a5\u53e3, \u4e00\u5934\u4e3aUSB-A\uff0c\u53e6\u4e00\u5934\u4e3amicro usb\u5e76\u4e14\u6807\u7b7e\u5e26\u6709kvm\u5b57\u6837\u7684\u7ebf\uff0c\u4e3a\u63a7\u5236\u7ebf\uff0c\u5176\u4e2dmicro usb\u53e3\u4e0eswitch\u7684control\u63a5\u53e3\u8fde\u63a5\uff0cUSB-A\u63a5\u53e3\u4e0eKVM\u7684USB\u53e3\u8fde\u63a5\u3002 \u4fa7\u9762\u63a5\u53e3\u793a\u610f\u56fe \u8bbe\u5907\u8fde\u63a5\u793a\u610f\u56fe","title":"\u63a5\u53e3\u793a\u610f\u56fe"},{"location":"bliswitch-v1-guide/#_3","text":"!!! info \"\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM\u8f6f\u4ef6\uff0c\u5728BliKVM\u542f\u52a8\u524d\u5148\u628aswitch\u901a\u7535\u5e76\u63a5\u597d\u7ebf\uff0c\u901a\u8fc7\u7ec8\u7aef\u786e\u8ba4switch\u63d2\u5165BliKVM\u540e\uff0c\u8bc6\u522b\u5230\u7684\u8bbe\u5907\u63cf\u8ff0\u7b26\u540d\u79f0\uff0c\u5982 /dev/ttyUSB0 ,\u7136\u540e\u7f16\u8f91 /usr/bin/blikvm/package.json \u4e2d\u7684 switch_handle \u5b57\u6bb5\uff0c\u5c06switch_enable\u8d4b\u503c\u4e3a1, switch_path\u8d4b\u503c\u4e3a /dev/ttyUSB0 \uff0c\u7136\u540e\u91cd\u542fBliKVM\u5373\u53ef\u3002 \u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u5148\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u7cfb\u7edf\u53d8\u4e3a\u53ef\u8bfb\u5199\u7cfb\u7edf\u3002\u7f16\u8f91\u914d\u7f6e\u6587\u4ef6\u53ef\u4ee5\u53c2\u8003\u4e0b\u547d\u4ee4: sudo vim /usr/bin/blikvm/package.json \u70b9\u51fb\u5de6\u4e0b\u89d2\u7684MORE\uff0c\u627e\u5230BliKVM switch\u8fd9\u4e00\u680f\uff0c\u8fdb\u884c\u5207\u6362\u9009\u62e9\u5373\u53ef\u3002\u6ce8\u610f\u5bf9\u5e94\u901a\u9053\u84dd\u8272\u5c0f\u70b9\u95ea\u52a8\u8868\u793a\u8bc6\u522b\u5230\u4e86switch\u63d2\u5165\uff0c\u5e76\u4e14\u6b63\u5904\u4e8e\u5f53\u524d\u901a\u9053\uff0c\u82e5\u65e0\u84dd\u8272\u5c0f\u70b9\u5219\u8868\u793a\u672a\u8bc6\u522b\u5230switch\u63d2\u5165\u3002\" \u82e5\u60a8\u4f7f\u7528\u7684PiKVM\u8f6f\u4ef6\uff0c\u8bf7\u6309\u7167\u4e0b\u9762\u7684\u8bf4\u660e\u8fdb\u884c\u914d\u7f6e \u901a\u8fc7SSH\u767b\u9646PiKVM\uff0c\u7528\u6237\u540d\u548c\u5bc6\u7801\u5747\u4e3aroot; \u7ec8\u7aef\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u7cfb\u7edf\u6539\u4e3a\u53ef\u8bfb\u5199\u7cfb\u7edf; \u7f16\u8f91 /etc/kvmd/override.yaml \u6b64\u6587\u4ef6\uff0c\u4f7f\u6539\u6587\u4ef6\u5305\u542b\u4e0b\u9762\u7684\u5185\u5bb9\uff0c\u5373\u5728\u539f\u6709\u5185\u5bb9\u540e\u8ffd\u52a0. kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] !!! warning \"\u4e0a\u8ff0\u914d\u7f6e\u57fa\u4e8e2022 pikvm\u56fe\u50cf\u3002\u5982\u679c\u60a8\u4f7f\u7528\u7684\u662f\u6700\u65b0\u7684pikvm\u6620\u50cf\u6216\u6700\u65b0\u7684\u8f6f\u4ef6\u7248\u672c\uff0c\u8bf7\u7f16\u8f91\u6587\u4ef6/etc/kvmd/override.yaml\u5e76\u6dfb\u52a0\u884c\uff1aprotocol:2\uff0c\u4f8b\u5b50\u5982\u4e0b:\" kvmd: gpio: drivers: hk: type: xh_hk4401 protocol: 2 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk ... \u7ec8\u7aef\u4f7f\u7528 ro \u547d\u4ee4\u5c06\u7cfb\u7edf\u91cd\u65b0\u8bbe\u7f6e\u4e3a\u53ea\u8bfb\u7cfb\u7edf\uff1b \u7ec8\u7aef\u4f7f\u7528 systemctl restart kvmd \u91cd\u542f\u670d\u52a1\u3002 \u8fdb\u5165PiKVM web\u754c\u9762\uff0c\u5e76\u5355\u51fb\u201cGPIO\u201d\u83dc\u5355\u3002\u60a8\u5e94\u8be5\u770b\u52304\u4e2a\u8f93\u5165\uff0c\u5176\u4e2d\u4e00\u4e2a\u8f93\u5165\u6709\u4e00\u4e2a\u7eff\u8272\u5706\u5708\uff0c\u8868\u793a\u5f53\u524d\u5df2\u9009\u4e2d\u3002\u5355\u51fb\u5176\u4ed6\u8f93\u5165\u4ee5\u66f4\u6539\u9009\u5b9a\u7684\u4e3b\u673a\u3002","title":"\u8f6f\u4ef6\u914d\u7f6e"},{"location":"bliswitch-v1-guide/#_4","text":"\u82e5\u60a8\u5e0c\u671b\u5c06blicube\u7684switch\u7528\u5728\u5176\u5b83\u5e73\u53f0\u4e0a\uff0c\u8bf7\u53c2\u8003\u4e0b\u9762\u7684\u534f\u8bae \u901a\u4fe1\u6ce2\u7279\u7387\u4e3a19200 \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW1\\r\\nG01gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW2\\r\\nG02gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW3\\r\\nG03gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW4\\r\\nG04gA switch\u8fd4\u56de\u5f53\u524d\u6240\u5728\u901a\u9053\u6d88\u606f\u4e3a: G01gA , G02gA , G03gA , G04gA","title":"\u63a7\u5236\u534f\u8bae"},{"location":"bliswitch-v1-guide/#_5","text":"\u4ea7\u54c1 \u6570\u91cf \u5907\u6ce8\uff5c KVM Switch\u5207\u6362\u5668\uff084\u901a\u9053) 1 110mm * 60mm * 33mm USB\u684c\u9762\u63a7\u5236\u5668 1 USB\u6570\u636e\u7ebf 4 \u957f\u5ea6: 1.2m HDMI\uff08\u6807\u51c6\u63a5\u5934\uff09\u7ebf 4 \u957f\u5ea6: 1.5m USB\u7535\u6e90\u7ebf 1 \u957f\u5ea6: 0.8m KVM USB\u7ebf 1 \u957f\u5ea6: 1.5m USB\u684c\u9762\u63a7\u5236\u7ebf 1 \u957f\u5ea6: 1m","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"bliswitch-v2-guide/","text":"8\u53e3KVM+ATX\u5207\u6362\u5668 BliSwitch v2 BliSwitch v2\u662f\u4e00\u6b3e8\u901a\u9053KVM+ATX\u5207\u6362\u5668\uff0c\u4f7f8\u53f0\u4e3b\u673a\u5171\u4eab\u4e00\u5957\u952e\u76d8\u3001\u9f20\u6807\u548cHDMI\u5c4f\u5e55\uff0c\u4e14\u5b9e\u73b0\u5bf98\u53f0\u4e3b\u673a\u7684\u5f00\u5173\u673a\u63a7\u5236\u3002 \u7aef\u53e3\u5b9a\u4e49 \u4ea7\u54c1\u53c2\u6570 \u54c1\u724c BLI \u54c1\u540d 8\u53e3KVM+ATX\u5207\u6362\u5668 \u578b\u53f7 BliSwitch v2 \u529f\u80fd \u516b\u53f0\u4e3b\u673a\u5171\u4eab\u4e00\u5957\u952e\u9f20\u548c\u663e\u793a\u5668\uff0c8\u53f0\u4e3b\u673a\u5f00\u5173\u673a\u63a7\u5236 \u6750\u8d28 \u5168\u91d1\u5c5e \u5206\u8fa8\u7387 1080P60Hz \u5207\u6362\u65b9\u5f0f \u6309\u952e\u5207\u6362 \u6216 USB\u63a7\u5236\u6a21\u5757\u5207\u6362 \u4f9b\u7535 5V1A \u63a7\u5236\u534f\u8bae \u82e5\u60a8\u5e0c\u671b\u5c06blicube\u7684switch\u7528\u5728\u5176\u5b83\u5e73\u53f0\u4e0a\uff0c\u8bf7\u53c2\u8003\u4e0b\u9762\u7684\u534f\u8bae \u901a\u4fe1\u6ce2\u7279\u7387\u4e3a19200 \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW1\\r\\nG01gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW2\\r\\nG02gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW3\\r\\nG03gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW4\\r\\nG04gA \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW5\\r\\nG05gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW6\\r\\nG06gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW7\\r\\nG07gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW8\\r\\nG07gA switch\u8fd4\u56de\u5f53\u524d\u6240\u5728\u901a\u9053\u6d88\u606f\u4e3a:G01gA,G02gA,G03gA,G04gA,G05gA,G06gA,G07gA,G08gA \u8fde\u63a5\u53c2\u8003 \u5c3a\u5bf8 \u53d1\u8d27\u6e05\u5355 \u4ea7\u54c1 \u6570\u91cf \u5907\u6ce8\uff5c BliSwitch v4\u5207\u6362\u5668 1 \u6302\u8033 2 ATX\u7ebf \u516c\u5934 8 ATX\u7ebf \u6bcd\u5934 8 \u5168\u9ad8PCIe\u6321\u677f 8 \u534a\u9ad8PCIe\u6321\u677f 8 ATX\u677f 8 \u63a7\u5236\u7ebf 1 USB\u7ebf 1 \u80f6\u57ab 4 M2.5x5 \u6c89\u5934\u87ba\u9489 10","title":"switchV2\u5207\u6362\u5668\u624b\u518c"},{"location":"bliswitch-v2-guide/#8kvmatx-bliswitch-v2","text":"BliSwitch v2\u662f\u4e00\u6b3e8\u901a\u9053KVM+ATX\u5207\u6362\u5668\uff0c\u4f7f8\u53f0\u4e3b\u673a\u5171\u4eab\u4e00\u5957\u952e\u76d8\u3001\u9f20\u6807\u548cHDMI\u5c4f\u5e55\uff0c\u4e14\u5b9e\u73b0\u5bf98\u53f0\u4e3b\u673a\u7684\u5f00\u5173\u673a\u63a7\u5236\u3002","title":"8\u53e3KVM+ATX\u5207\u6362\u5668 BliSwitch v2"},{"location":"bliswitch-v2-guide/#_1","text":"","title":"\u7aef\u53e3\u5b9a\u4e49"},{"location":"bliswitch-v2-guide/#_2","text":"\u54c1\u724c BLI \u54c1\u540d 8\u53e3KVM+ATX\u5207\u6362\u5668 \u578b\u53f7 BliSwitch v2 \u529f\u80fd \u516b\u53f0\u4e3b\u673a\u5171\u4eab\u4e00\u5957\u952e\u9f20\u548c\u663e\u793a\u5668\uff0c8\u53f0\u4e3b\u673a\u5f00\u5173\u673a\u63a7\u5236 \u6750\u8d28 \u5168\u91d1\u5c5e \u5206\u8fa8\u7387 1080P60Hz \u5207\u6362\u65b9\u5f0f \u6309\u952e\u5207\u6362 \u6216 USB\u63a7\u5236\u6a21\u5757\u5207\u6362 \u4f9b\u7535 5V1A","title":"\u4ea7\u54c1\u53c2\u6570"},{"location":"bliswitch-v2-guide/#_3","text":"\u82e5\u60a8\u5e0c\u671b\u5c06blicube\u7684switch\u7528\u5728\u5176\u5b83\u5e73\u53f0\u4e0a\uff0c\u8bf7\u53c2\u8003\u4e0b\u9762\u7684\u534f\u8bae \u901a\u4fe1\u6ce2\u7279\u7387\u4e3a19200 \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW1\\r\\nG01gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW2\\r\\nG02gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW3\\r\\nG03gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW4\\r\\nG04gA \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW5\\r\\nG05gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW6\\r\\nG06gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW7\\r\\nG07gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW8\\r\\nG07gA switch\u8fd4\u56de\u5f53\u524d\u6240\u5728\u901a\u9053\u6d88\u606f\u4e3a:G01gA,G02gA,G03gA,G04gA,G05gA,G06gA,G07gA,G08gA","title":"\u63a7\u5236\u534f\u8bae"},{"location":"bliswitch-v2-guide/#_4","text":"","title":"\u8fde\u63a5\u53c2\u8003"},{"location":"bliswitch-v2-guide/#_5","text":"","title":"\u5c3a\u5bf8"},{"location":"bliswitch-v2-guide/#_6","text":"\u4ea7\u54c1 \u6570\u91cf \u5907\u6ce8\uff5c BliSwitch v4\u5207\u6362\u5668 1 \u6302\u8033 2 ATX\u7ebf \u516c\u5934 8 ATX\u7ebf \u6bcd\u5934 8 \u5168\u9ad8PCIe\u6321\u677f 8 \u534a\u9ad8PCIe\u6321\u677f 8 ATX\u677f 8 \u63a7\u5236\u7ebf 1 USB\u7ebf 1 \u80f6\u57ab 4 M2.5x5 \u6c89\u5934\u87ba\u9489 10","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"dev-v4/","text":"\u9700\u6267\u884c\u4e0b\u9762\u547d\u4ee4\uff0c\u5426\u5219apt-get update \u548c apt-get upgrade\u540e\u955c\u50cf\u4f1a\u65e0\u6cd5\u542f\u52a8 apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64","title":"Dev v4"},{"location":"dev-v4/#apt-get-update-apt-get-upgrade","text":"apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64","title":"\u9700\u6267\u884c\u4e0b\u9762\u547d\u4ee4\uff0c\u5426\u5219apt-get update \u548c apt-get upgrade\u540e\u955c\u50cf\u4f1a\u65e0\u6cd5\u542f\u52a8"},{"location":"dev_api/","text":"API \u7533\u660e: \u6b64API\u4e3a\u5b9e\u9a8c\u6027\u7684\uff0c\u4efb\u4f55\u65f6\u5019\u90fd\u6709\u53ef\u80fd\u88ab\u6539\u53d8!\u6b64\u6587\u6863\u53ea\u5728v1.4.0\u548c\u4e4b\u524d\u7248\u672c\u6709\u6548\uff0c\u5373\u5c06\u66f4\u65b0. \u6b64\u6587\u6863\u4e3aBLIKVM OS\u7684http API\u5f00\u53d1\u624b\u518c\uff0c\u82e5\u60a8\u6709\u65b0\u7684API\u9700\u6c42\u4e0d\u5728\u6b64\u6587\u6863\u4e2d\uff0c\u53ef\u4ee5\u5728github\u4e2d\u63d0pr\u83b7\u5f97\u652f\u6301\u3002\u8bf7\u6c42URL\u4e2d\u7684kvmip\u9700\u6839\u636e\u4f60kvm\u7684ip\u5b9e\u9645\u66ff\u6362\u3002 \u767b\u5f55\u8ba4\u8bc1 \u6b64API\u7528\u4e8e\u7528\u6237\u767b\u5f55\uff0c\u5e76\u8fd4\u56de\u8bbf\u95ee\u4ee4\u724c\u3002\u540e\u7eed\u6709\u7684api\u5747\u9700\u8981token\u4ee4\u724c\u3002 \u8bf7\u6c42URL: http://kvmip/login_api \u8bf7\u6c42\u65b9\u6cd5: GET \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f,\u5982: { \"username\": \"admin\", \"password\": \"admin\" } \u54cd\u5e94\u7ed3\u679c\u5982\u4e0b\uff0c\u82e5status\u4e0d\u4e3a1\uff0c\u5219\u8ba4\u8bc1\u5931\u8d25\u3002 { \"status\": 1, \"info\": \"login success\", \"data\": { \"token\": \"2sscdada6a97a774fcd4714c\" } } ATX\u5f00\u5173\u673a \u6b64API\u7528\u4e8e\u63a7\u5236\u76ee\u6807\u8bbe\u5907\u5f00\u5173\u673a\uff0c\u548c\u91cd\u542f\u3002 - \u8bf7\u6c42URL: http://kvmip/atx - \u8bf7\u6c42\u65b9\u6cd5: POST - \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f: 1. \u5176\u4e2dcmd\u4e3a128\u4e3a\u5f00\u5173\u673a(\u5373\u5f00\u673a\u7684\u60c5\u51b5\u4e0b\u6a21\u62df\u7684\u4e3a\u77ed\u6309\u5173\u673a\uff0c\u5173\u673a\u7684\u60c5\u51b5\u4e0b\u4e3a\u77ed\u6309\u5f00\u673a); 2. 192\u4e3a\u5f3a\u5236\u5173\u673a(\u6a21\u62df\u957f\u6309\u5f3a\u5236\u5173\u673a); 3. cmd\u4e3a8\u8868\u793a\u91cd\u542f\u3002\u5982: { \"cmd\": 128 } \u54cd\u5e94\u7ed3\u679c\u5982\u4e0b\uff0c\u82e5status\u4e0d\u4e3a1\uff0c\u5219\u5931\u8d25\u3002 { \"status\": 1, \"info\": \"success\", } mjepg\u56fe\u50cf \u6b64API\u7528\u4e8e\u5728\u56fe\u50cf\u6a21\u5f0f\u4e3amjepg\u7684\u6a21\u5f0f\u4e0b\uff0c\u62ff\u5230mjpeg\u7684\u89c6\u5c4f\u6d41\u3002 - \u8bf7\u6c42URL: http://kvmip:8008/stream \uff0c\u6b64API\u7528\u4e8e\u5728\u56fe\u50cf\u6a21\u5f0f\u4e3amjepg\u7684\u6a21\u5f0f\u4e0b\uff0c\u62ff\u5230mjpeg\u7684\u4e00\u5e27\u56fe\u7247\u3002 - \u8bf7\u6c42URL: http://kvmip:8008/snapshot - \u8bf7\u6c42\u65b9\u6cd5: GET \u952e\u76d8 \u952e\u76d8\u5177\u4f53\u7f16\u7801\u53ef\u53c2\u8003 \"KeyA\"=> 4, \"KeyB\"=> 5, \"KeyC\"=> 6, \"KeyD\"=> 7, \"KeyE\"=> 8, \"KeyF\"=> 9, \"KeyG\"=> 10, \"KeyH\"=> 11, \"KeyI\"=> 12, \"KeyJ\"=> 13, \"KeyK\"=> 14, \"KeyL\"=> 15, \"KeyM\"=> 16, \"KeyN\"=> 17, \"KeyO\"=> 18, \"KeyP\"=> 19, \"KeyQ\"=> 20, \"KeyR\"=> 21, \"KeyS\"=> 22, \"KeyT\"=> 23, \"KeyU\"=> 24, \"KeyV\"=> 25, \"KeyW\"=> 26, \"KeyX\"=> 27, \"KeyY\"=> 28, \"KeyZ\"=> 29, \"Digit1\"=> 30, \"Digit2\"=> 31, \"Digit3\"=> 32, \"Digit4\"=> 33, \"Digit5\"=> 34, \"Digit6\"=> 35, \"Digit7\"=> 36, \"Digit8\"=> 37, \"Digit9\"=> 38, \"Digit0\"=> 39, \"Enter\"=> 40, \"Escape\"=> 41, \"Backspace\"=> 42, \"Tab\"=> 43, \"Space\"=> 44, \"Minus\"=> 45, \"Equal\"=> 46, \"BracketLeft\"=> 47, \"BracketRight\"=> 48, \"Backslash\"=> 49, \"Semicolon\"=> 51, \"Quote\"=> 52, \"Backquote\"=> 53, \"Comma\"=> 54, \"Period\"=> 55, \"Slash\"=> 56, \"CapsLock\"=> 57, \"F1\"=> 58, \"F2\"=> 59, \"F3\"=> 60, \"F4\"=> 61, \"F5\"=> 62, \"F6\"=> 63, \"F7\"=> 64, \"F8\"=> 65, \"F9\"=> 66, \"F10\"=> 67, \"F11\"=> 68, \"F12\"=> 69, \"PrtSc\"=> 70, \"ScrollLock\"=> 71, \"Pause\"=> 72, \"Insert\"=> 73, \"Home\"=> 74, \"PageUp\"=> 75, \"Delete\"=> 76, \"End\"=> 77, \"PageDown\"=> 78, \"ArrowRight\"=> 79, \"ArrowLeft\"=> 80, \"ArrowDown\"=> 81, \"ArrowUp\"=> 82, \"NumLock\"=> 83, \"NumpadDivide\"=> 84, \"NumpadMultiply\"=> 85, \"NumpadSubtract\"=> 86, \"NumpadAdd\"=> 87, \"NumpadEnter\"=> 88, \"Numpad1\"=> 89, \"Numpad2\"=> 90, \"Numpad3\"=> 91, \"Numpad4\"=> 92, \"Numpad5\"=> 93, \"Numpad6\"=> 94, \"Numpad7\"=> 95, \"Numpad8\"=> 96, \"Numpad9\"=> 97, \"Numpad0\"=> 98, \"NumpadDecimal\"=> 99 \u8bf7\u6c42URL: http://kvmip/keyboard \u8bf7\u6c42\u65b9\u6cd5: GET \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f,keycodes\u4e3a\u5b57\u7b26\u4e32\u6570\u7ec4\uff0c\u652f\u6301\u4e00\u6b21\u8f93\u5165\u591a\u4e2a,\u5982: { \"keycodes\": [\"Digit1\"] } \u54cd\u5e94\u7ed3\u679c\u5982: { \"status\": 1, \"info\": \"key input success\", \"data\": [] }","title":"http API"},{"location":"dev_api/#api","text":"\u7533\u660e: \u6b64API\u4e3a\u5b9e\u9a8c\u6027\u7684\uff0c\u4efb\u4f55\u65f6\u5019\u90fd\u6709\u53ef\u80fd\u88ab\u6539\u53d8!\u6b64\u6587\u6863\u53ea\u5728v1.4.0\u548c\u4e4b\u524d\u7248\u672c\u6709\u6548\uff0c\u5373\u5c06\u66f4\u65b0. \u6b64\u6587\u6863\u4e3aBLIKVM OS\u7684http API\u5f00\u53d1\u624b\u518c\uff0c\u82e5\u60a8\u6709\u65b0\u7684API\u9700\u6c42\u4e0d\u5728\u6b64\u6587\u6863\u4e2d\uff0c\u53ef\u4ee5\u5728github\u4e2d\u63d0pr\u83b7\u5f97\u652f\u6301\u3002\u8bf7\u6c42URL\u4e2d\u7684kvmip\u9700\u6839\u636e\u4f60kvm\u7684ip\u5b9e\u9645\u66ff\u6362\u3002","title":"API"},{"location":"dev_api/#_1","text":"\u6b64API\u7528\u4e8e\u7528\u6237\u767b\u5f55\uff0c\u5e76\u8fd4\u56de\u8bbf\u95ee\u4ee4\u724c\u3002\u540e\u7eed\u6709\u7684api\u5747\u9700\u8981token\u4ee4\u724c\u3002 \u8bf7\u6c42URL: http://kvmip/login_api \u8bf7\u6c42\u65b9\u6cd5: GET \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f,\u5982: { \"username\": \"admin\", \"password\": \"admin\" } \u54cd\u5e94\u7ed3\u679c\u5982\u4e0b\uff0c\u82e5status\u4e0d\u4e3a1\uff0c\u5219\u8ba4\u8bc1\u5931\u8d25\u3002 { \"status\": 1, \"info\": \"login success\", \"data\": { \"token\": \"2sscdada6a97a774fcd4714c\" } }","title":"\u767b\u5f55\u8ba4\u8bc1"},{"location":"dev_api/#atx","text":"\u6b64API\u7528\u4e8e\u63a7\u5236\u76ee\u6807\u8bbe\u5907\u5f00\u5173\u673a\uff0c\u548c\u91cd\u542f\u3002 - \u8bf7\u6c42URL: http://kvmip/atx - \u8bf7\u6c42\u65b9\u6cd5: POST - \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f: 1. \u5176\u4e2dcmd\u4e3a128\u4e3a\u5f00\u5173\u673a(\u5373\u5f00\u673a\u7684\u60c5\u51b5\u4e0b\u6a21\u62df\u7684\u4e3a\u77ed\u6309\u5173\u673a\uff0c\u5173\u673a\u7684\u60c5\u51b5\u4e0b\u4e3a\u77ed\u6309\u5f00\u673a); 2. 192\u4e3a\u5f3a\u5236\u5173\u673a(\u6a21\u62df\u957f\u6309\u5f3a\u5236\u5173\u673a); 3. cmd\u4e3a8\u8868\u793a\u91cd\u542f\u3002\u5982: { \"cmd\": 128 } \u54cd\u5e94\u7ed3\u679c\u5982\u4e0b\uff0c\u82e5status\u4e0d\u4e3a1\uff0c\u5219\u5931\u8d25\u3002 { \"status\": 1, \"info\": \"success\", }","title":"ATX\u5f00\u5173\u673a"},{"location":"dev_api/#mjepg","text":"\u6b64API\u7528\u4e8e\u5728\u56fe\u50cf\u6a21\u5f0f\u4e3amjepg\u7684\u6a21\u5f0f\u4e0b\uff0c\u62ff\u5230mjpeg\u7684\u89c6\u5c4f\u6d41\u3002 - \u8bf7\u6c42URL: http://kvmip:8008/stream \uff0c\u6b64API\u7528\u4e8e\u5728\u56fe\u50cf\u6a21\u5f0f\u4e3amjepg\u7684\u6a21\u5f0f\u4e0b\uff0c\u62ff\u5230mjpeg\u7684\u4e00\u5e27\u56fe\u7247\u3002 - \u8bf7\u6c42URL: http://kvmip:8008/snapshot - \u8bf7\u6c42\u65b9\u6cd5: GET","title":"mjepg\u56fe\u50cf"},{"location":"dev_api/#_2","text":"\u952e\u76d8\u5177\u4f53\u7f16\u7801\u53ef\u53c2\u8003 \"KeyA\"=> 4, \"KeyB\"=> 5, \"KeyC\"=> 6, \"KeyD\"=> 7, \"KeyE\"=> 8, \"KeyF\"=> 9, \"KeyG\"=> 10, \"KeyH\"=> 11, \"KeyI\"=> 12, \"KeyJ\"=> 13, \"KeyK\"=> 14, \"KeyL\"=> 15, \"KeyM\"=> 16, \"KeyN\"=> 17, \"KeyO\"=> 18, \"KeyP\"=> 19, \"KeyQ\"=> 20, \"KeyR\"=> 21, \"KeyS\"=> 22, \"KeyT\"=> 23, \"KeyU\"=> 24, \"KeyV\"=> 25, \"KeyW\"=> 26, \"KeyX\"=> 27, \"KeyY\"=> 28, \"KeyZ\"=> 29, \"Digit1\"=> 30, \"Digit2\"=> 31, \"Digit3\"=> 32, \"Digit4\"=> 33, \"Digit5\"=> 34, \"Digit6\"=> 35, \"Digit7\"=> 36, \"Digit8\"=> 37, \"Digit9\"=> 38, \"Digit0\"=> 39, \"Enter\"=> 40, \"Escape\"=> 41, \"Backspace\"=> 42, \"Tab\"=> 43, \"Space\"=> 44, \"Minus\"=> 45, \"Equal\"=> 46, \"BracketLeft\"=> 47, \"BracketRight\"=> 48, \"Backslash\"=> 49, \"Semicolon\"=> 51, \"Quote\"=> 52, \"Backquote\"=> 53, \"Comma\"=> 54, \"Period\"=> 55, \"Slash\"=> 56, \"CapsLock\"=> 57, \"F1\"=> 58, \"F2\"=> 59, \"F3\"=> 60, \"F4\"=> 61, \"F5\"=> 62, \"F6\"=> 63, \"F7\"=> 64, \"F8\"=> 65, \"F9\"=> 66, \"F10\"=> 67, \"F11\"=> 68, \"F12\"=> 69, \"PrtSc\"=> 70, \"ScrollLock\"=> 71, \"Pause\"=> 72, \"Insert\"=> 73, \"Home\"=> 74, \"PageUp\"=> 75, \"Delete\"=> 76, \"End\"=> 77, \"PageDown\"=> 78, \"ArrowRight\"=> 79, \"ArrowLeft\"=> 80, \"ArrowDown\"=> 81, \"ArrowUp\"=> 82, \"NumLock\"=> 83, \"NumpadDivide\"=> 84, \"NumpadMultiply\"=> 85, \"NumpadSubtract\"=> 86, \"NumpadAdd\"=> 87, \"NumpadEnter\"=> 88, \"Numpad1\"=> 89, \"Numpad2\"=> 90, \"Numpad3\"=> 91, \"Numpad4\"=> 92, \"Numpad5\"=> 93, \"Numpad6\"=> 94, \"Numpad7\"=> 95, \"Numpad8\"=> 96, \"Numpad9\"=> 97, \"Numpad0\"=> 98, \"NumpadDecimal\"=> 99 \u8bf7\u6c42URL: http://kvmip/keyboard \u8bf7\u6c42\u65b9\u6cd5: GET \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f,keycodes\u4e3a\u5b57\u7b26\u4e32\u6570\u7ec4\uff0c\u652f\u6301\u4e00\u6b21\u8f93\u5165\u591a\u4e2a,\u5982: { \"keycodes\": [\"Digit1\"] } \u54cd\u5e94\u7ed3\u679c\u5982: { \"status\": 1, \"info\": \"key input success\", \"data\": [] }","title":"\u952e\u76d8"},{"location":"edid/","text":"EDID EDID\u6587\u4ef6\u5728BliKVM\u4e2d\u7684\u4f5c\u7528\u662f\u544a\u8bc9\u88ab\u63a7\u8ba1\u7b97\u673a\u671f\u671b\u8f93\u51fa\u7684HDMI\u5206\u8fa8\u7387\uff0c\u5373\u5982\u4f55\u4f7f\u7528\u7684\u662f1080P60Hz\u7684EDID\uff0c\u82e5\u88ab\u63a7\u8ba1\u7b97\u673a\u652f\u6301\u8f93\u51fa\u6b64\u5206\u8fa8\u7387\uff0c\u88ab\u63a7\u8ba1\u7b97\u673a\u5c31\u4f1a\u63091080P60Hz\u8f93\u51fa\u3002\u53e6\u5916\u901a\u8fc7EDID\u8fd8\u53ef\u4ee5\u5c4f\u853d\u58f0\u97f3\uff0c\u4fee\u6539\u663e\u793a\u5668\u578b\u53f7\uff0c\u540d\u5b57\uff0c\u5382\u5546\u7b49\u4fe1\u606f\u3002\u901a\u5e38\u60c5\u51b5\u4e0b\uff0c\u60a8\u4e0d\u9700\u8981\u66f4\u6539\u5b83\uff0c\u4f46\u6709\u65f6\uff0c\u4f8b\u5982\u5bf9\u4e8e\u5947\u602a\u7684 UEFI/BIOS\uff0c\u53ef\u80fd\u9700\u8981\u66f4\u6539\u5b83\u3002 Note BliKVM v1 v2 v3\u4f7f\u7528\u7684\u4e3aCSI\u89c6\u9891\u91c7\u96c6\u65b9\u6848\uff0c\u652f\u6301EDID\u8bbe\u7f6e\uff0cv4\u4f7f\u7528\u7684\u662fUSB\u89c6\u9891\u91c7\u96c6\u65b9\u6848\uff0c\u4e0d\u652f\u6301EDID\u8bbe\u7f6e\uff1b \u5176\u4e2dv3 HAT\u53d7\u6811\u8393\u6d3e4B\u53ea\u67092\u901a\u9053CSI\u9650\u5236\uff0c\u6700\u9ad8\u53ea\u80fd\u91c7\u96c61080P50Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u56e0\u6b64\u82e5\u5bf9v3\u8bbe\u7f6e1080P60Hz\u7684EDID\uff0cv3\u4f1a\u65e0\u6cd5\u6355\u83b7\u5230\u56fe\u50cf\uff1b \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM OS\uff0c\u53ef\u4ee5\u53c2\u7167 \u6b64\u94fe\u63a5 \u8fdb\u884c\u4fee\u6539; \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM OS\uff0cEDID\u6587\u4ef6\u5728 /usr/bin/blikvm/edid.txt ,\u6253\u5f00\u6b64\u6587\u4ef6\uff0c\u66ff\u6362\u4e0b\u9762\u4f60\u60f3\u8981\u5206\u8fa8\u7387\u7684EDID\u6587\u4ef6\u5373\u53ef\uff1b EDID \u4f8b\u5b50 1080P60Hz \u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u548cv2\u786c\u4ef6\u3002 1920x1080 60Hz, \u5e26\u97f3\u9891 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C EDID \u4f8b\u5b50 1080P50Hz \u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u3001v2\u3001v3\u786c\u4ef6\uff0c\u5c24\u5176\u5f53\u5e0c\u671bv3 HAT\u6355\u83b71080P\u5206\u8fa8\u7387\u65f6\u53ef\u4ee5\u4f7f\u7528\u5b83\u3002 1920x1080 50Hz, \u5e26\u97f3\u9891 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028 EDID \u4f8b\u5b50 720P60Hz \u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u3001v2\u3001v3\u786c\u4ef6\u3002 1280x720 60Hz, \u5e26\u97f3\u9891 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 \u81ea\u5b9a\u4e49EDID \u6700\u597d\u4f7f\u7528\u7b2c\u4e09\u65b9\u5de5\u5177\u6765\u7f16\u8f91EDID\uff0c\u6bd4\u5982\u63a8\u8350\u7684\u9ad8\u7ea7 AW EDID Editor \uff08Windows\u73af\u5883\u4e0b\u8fd0\u884c\u826f\u597d\uff0c\u4e5f\u53ef\u5728wine\u4e2d\u4f7f\u7528\uff09\u6216\u8005 wxEDID \u3002\u8fd9\u4e24\u4e2a\u7f16\u8f91\u5668\u90fd\u53ef\u4ee5\u5904\u7406\u4e8c\u8fdb\u5236\u7684EDID\u683c\u5f0f\u3002 \u4f7f\u7528\u8fd9\u4e9b\u5de5\u5177\uff0c\u60a8\u53ef\u4ee5\u50cf\u7f16\u8f91\u6587\u4ef6\u4e00\u6837\u4fee\u6539EDID\u4fe1\u606f\uff0c\u7c7b\u4f3c\u4e8e\u66f4\u6539\u8eab\u4efd\u8bc1\u4fe1\u606f\u3002\u901a\u8fc7\u7f16\u8f91EDID\uff0c\u60a8\u53ef\u4ee5\u8c03\u6574\u663e\u793a\u5668\u7684\u53c2\u6570\u548c\u7279\u6027\uff0c\u4ee5\u9002\u5e94\u4e0d\u540c\u7684\u4f7f\u7528\u9700\u6c42\uff0c\u4ece\u800c\u83b7\u5f97\u66f4\u597d\u7684\u663e\u793a\u6548\u679c\u3002","title":"HDMI EDID\u8bbe\u7f6e"},{"location":"edid/#edid","text":"EDID\u6587\u4ef6\u5728BliKVM\u4e2d\u7684\u4f5c\u7528\u662f\u544a\u8bc9\u88ab\u63a7\u8ba1\u7b97\u673a\u671f\u671b\u8f93\u51fa\u7684HDMI\u5206\u8fa8\u7387\uff0c\u5373\u5982\u4f55\u4f7f\u7528\u7684\u662f1080P60Hz\u7684EDID\uff0c\u82e5\u88ab\u63a7\u8ba1\u7b97\u673a\u652f\u6301\u8f93\u51fa\u6b64\u5206\u8fa8\u7387\uff0c\u88ab\u63a7\u8ba1\u7b97\u673a\u5c31\u4f1a\u63091080P60Hz\u8f93\u51fa\u3002\u53e6\u5916\u901a\u8fc7EDID\u8fd8\u53ef\u4ee5\u5c4f\u853d\u58f0\u97f3\uff0c\u4fee\u6539\u663e\u793a\u5668\u578b\u53f7\uff0c\u540d\u5b57\uff0c\u5382\u5546\u7b49\u4fe1\u606f\u3002\u901a\u5e38\u60c5\u51b5\u4e0b\uff0c\u60a8\u4e0d\u9700\u8981\u66f4\u6539\u5b83\uff0c\u4f46\u6709\u65f6\uff0c\u4f8b\u5982\u5bf9\u4e8e\u5947\u602a\u7684 UEFI/BIOS\uff0c\u53ef\u80fd\u9700\u8981\u66f4\u6539\u5b83\u3002 Note BliKVM v1 v2 v3\u4f7f\u7528\u7684\u4e3aCSI\u89c6\u9891\u91c7\u96c6\u65b9\u6848\uff0c\u652f\u6301EDID\u8bbe\u7f6e\uff0cv4\u4f7f\u7528\u7684\u662fUSB\u89c6\u9891\u91c7\u96c6\u65b9\u6848\uff0c\u4e0d\u652f\u6301EDID\u8bbe\u7f6e\uff1b \u5176\u4e2dv3 HAT\u53d7\u6811\u8393\u6d3e4B\u53ea\u67092\u901a\u9053CSI\u9650\u5236\uff0c\u6700\u9ad8\u53ea\u80fd\u91c7\u96c61080P50Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u56e0\u6b64\u82e5\u5bf9v3\u8bbe\u7f6e1080P60Hz\u7684EDID\uff0cv3\u4f1a\u65e0\u6cd5\u6355\u83b7\u5230\u56fe\u50cf\uff1b \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM OS\uff0c\u53ef\u4ee5\u53c2\u7167 \u6b64\u94fe\u63a5 \u8fdb\u884c\u4fee\u6539; \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM OS\uff0cEDID\u6587\u4ef6\u5728 /usr/bin/blikvm/edid.txt ,\u6253\u5f00\u6b64\u6587\u4ef6\uff0c\u66ff\u6362\u4e0b\u9762\u4f60\u60f3\u8981\u5206\u8fa8\u7387\u7684EDID\u6587\u4ef6\u5373\u53ef\uff1b","title":"EDID"},{"location":"edid/#edid-1080p60hz","text":"\u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u548cv2\u786c\u4ef6\u3002 1920x1080 60Hz, \u5e26\u97f3\u9891 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C","title":"EDID \u4f8b\u5b50 1080P60Hz"},{"location":"edid/#edid-1080p50hz","text":"\u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u3001v2\u3001v3\u786c\u4ef6\uff0c\u5c24\u5176\u5f53\u5e0c\u671bv3 HAT\u6355\u83b71080P\u5206\u8fa8\u7387\u65f6\u53ef\u4ee5\u4f7f\u7528\u5b83\u3002 1920x1080 50Hz, \u5e26\u97f3\u9891 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028","title":"EDID \u4f8b\u5b50 1080P50Hz"},{"location":"edid/#edid-720p60hz","text":"\u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u3001v2\u3001v3\u786c\u4ef6\u3002 1280x720 60Hz, \u5e26\u97f3\u9891 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000","title":"EDID \u4f8b\u5b50 720P60Hz"},{"location":"edid/#edid_1","text":"\u6700\u597d\u4f7f\u7528\u7b2c\u4e09\u65b9\u5de5\u5177\u6765\u7f16\u8f91EDID\uff0c\u6bd4\u5982\u63a8\u8350\u7684\u9ad8\u7ea7 AW EDID Editor \uff08Windows\u73af\u5883\u4e0b\u8fd0\u884c\u826f\u597d\uff0c\u4e5f\u53ef\u5728wine\u4e2d\u4f7f\u7528\uff09\u6216\u8005 wxEDID \u3002\u8fd9\u4e24\u4e2a\u7f16\u8f91\u5668\u90fd\u53ef\u4ee5\u5904\u7406\u4e8c\u8fdb\u5236\u7684EDID\u683c\u5f0f\u3002 \u4f7f\u7528\u8fd9\u4e9b\u5de5\u5177\uff0c\u60a8\u53ef\u4ee5\u50cf\u7f16\u8f91\u6587\u4ef6\u4e00\u6837\u4fee\u6539EDID\u4fe1\u606f\uff0c\u7c7b\u4f3c\u4e8e\u66f4\u6539\u8eab\u4efd\u8bc1\u4fe1\u606f\u3002\u901a\u8fc7\u7f16\u8f91EDID\uff0c\u60a8\u53ef\u4ee5\u8c03\u6574\u663e\u793a\u5668\u7684\u53c2\u6570\u548c\u7279\u6027\uff0c\u4ee5\u9002\u5e94\u4e0d\u540c\u7684\u4f7f\u7528\u9700\u6c42\uff0c\u4ece\u800c\u83b7\u5f97\u66f4\u597d\u7684\u663e\u793a\u6548\u679c\u3002","title":"\u81ea\u5b9a\u4e49EDID"},{"location":"faq/","text":"FAQ & \u6545\u969c\u6392\u9664 \u4f5c\u4e3a\u7b2c\u4e00\u6b65\uff0c\u6211\u4eec\u5efa\u8bae\u4ed4\u7ec6\u9605\u8bfb\u6211\u4eec\u7684\u6587\u6863\u3002\u5927\u90e8\u5206\u8bbe\u7f6eBLIKVM\u6240\u9700\u7684\u6b65\u9aa4\u5df2\u7ecf\u5728\u6587\u6863\u4e2d\u63cf\u8ff0\u4e86\u3002\u5982\u679c\u60a8\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u60a8\u53ef\u4ee5\u67e5\u770b\u672c\u9875\uff0c\u5176\u4e2d\u5217\u51fa\u4e86\u5e38\u89c1\u9519\u8bef\u3002\u5982\u679c\u4ecd\u7136\u65e0\u6cd5\u89e3\u51b3\u95ee\u9898\uff0c\u6b22\u8fce\u63d0\u4ea4 \u95ee\u9898\u53cd\u9988 \u6216 \u52a0\u5165\u6211\u4eec\u7684Discord \u5bfb\u6c42\u8fdb\u4e00\u6b65\u5e2e\u52a9\u3002 \u5e38\u89c1\u95ee\u9898 \u6211\u53ef\u4ee5\u5c06\u591a\u53f0\u670d\u52a1\u5668\u8fde\u63a5\u5230\u5355\u4e2aBLIKVM\u5417\uff1f \u53ef\u4ee5\uff0c\u4f46\u9700\u8981\u8fdb\u884c\u989d\u5916\u7684\u8bbe\u7f6e\u5de5\u4f5c\u3002\u8bf7\u53c2\u8003 \u6b64\u9875\u9762 \u3002 \u5982\u4f55\u5728\u672c\u5730\u7f51\u7edc\u4e0a\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95eeBliKVM\uff1f \u5982\u679c\u60a8\u7684\u8def\u7531\u5668\u5177\u6709\u5916\u90e8IP\u5730\u5740\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u7aef\u53e3\u8f6c\u53d1\u6765\u8f6c\u53d180\u7aef\u53e3(Web),8008\u7aef\u53e3(mjpeg)\uff0c8188\u7aef\u53e3\uff08webrtc\uff09\u3002\u5728\u5176\u4ed6\u60c5\u51b5\u4e0b\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u51fa\u8272\u7684\u514d\u8d39VPN\u670d\u52a1Tailscale\u3002 BLiKVM\u6709\u591a\u6b3e\u786c\u4ef6\uff0c\u5982BliKVM V1 CM4\u3001BliKVM V2 PCIe\u3001BliKVM V3 Hat\uff0c\u6211\u5e94\u8be5\u9009\u54ea\u6b3e\uff1f \u9996\u5148\u5404\u4e2a\u7248\u672c\u7684\u4e3b\u8981\u53c2\u6570\u5bf9\u6bd4\u8bf7\u53c2\u8003 \u6b64\u9875\u9762 \u3002 V1\u548cV3\u5c5e\u4e8e\u5916\u7f6e\u65b9\u6848\uff0cV2\u5c5e\u4e8e\u5185\u7f6e\u673a\u7bb1\u65b9\u6848\u3002\u5982\u679c\u60a8\u662f\u673a\u7bb1\u5f62\u5f0f\uff0c\u5e76\u4e14\u673a\u7bb1\u5185\u90e8\u6709\u7a7a\u95f4\uff0c\u90a3\u4e48\u6beb\u65e0\u7591\u95ee\u9009\u62e9V2 PCIe\u7248\u672c\u662f\u8f83\u597d\u7684\u9009\u62e9\u3002 \u90a3\u4e48V1\u548cV3\u4e24\u4e2a\u5916\u7f6e\u65b9\u6848\u5982\u4f55\u9009\u62e9\u5462\uff0cV1\u57fa\u4e8eCM4\u7684\u65b9\u6848\uff0c\u96c6\u6210\u5ea6\u66f4\u9ad8\uff0c\u6709\u5230\u624b\u53ef\u7528\u7248\u672c\u3002V3\u57fa\u4e8e\u6811\u8393\u6d3e4B\u65b9\u6848\uff0c\u6240\u6709IO\u53e3\u5747\u5f15\u51fa\uff0c\u53ef\u6269\u5c55\u6027\u66f4\u5f3a\u3002\u4e24\u8005\u7684\u53e6\u4e00\u4e2a\u6838\u5fc3\u533a\u522b\u5c31\u662fV1\u6700\u9ad8\u652f\u63011080P60Hz\u8f93\u5165\uff0cV3\u6700\u9ad8\u652f\u63011080P50Hz\u8f93\u5165\u3002\u5f53\u7136\u540c\u65f6\u9700\u8981\u8003\u8651\u60a8\u662f\u5df2\u5426\u6709CM4\u6216\u80054B\uff0c\u5982\u679c\u6709\u7684\u8bdd\u53ea\u4e70\u5bf9\u5e94\u7684\u5e95\u677f\uff0c\u6027\u4ef7\u6bd4\u66f4\u9ad8\u3002 \u6211\u53ef\u4ee5\u7528BLIKVM\u8fdb\u884c\u6e38\u620f\u5417\uff1f \u4e0d\u53ef\u4ee5\uff0c\u539f\u56e0\u5982\u4e0b\uff1a \u5bf9\u4e8eHDMI-CSI\u6865\u63a5\u5668\uff0c\u603b\u7ebf\u5e26\u5bbd\u4e0d\u8db3\u4ee5\u4f20\u8f93\u8d85\u8fc71080p60\u7684\u89c6\u9891\u3002 \u5bf9\u4e8eHDMI-USB\u8f6c\u6362\u5668\uff0c\u5ef6\u8fdf\u8f83\u9ad8\u4e14\u89c6\u9891\u8d28\u91cf\u8f83\u4f4e\u3002 \u4e00\u822c\u7684\u786c\u4ef6\u89c6\u9891\u6355\u83b7\u4e0e\u8f6f\u4ef6\u6d41\u5a92\u4f53\u6709\u6240\u4e0d\u540c\uff0c\u4f1a\u5f15\u5165\u989d\u5916\u7684\u5ef6\u8fdf\u3002 BLIKVM\u652f\u63014K\u89c6\u9891\u5417\uff1f \u5bf9\u4e8eHDMI-CSI\u6865\u63a5\u5668\uff0c\u4e0d\u652f\u6301\u3002CSI\u603b\u7ebf\u7684\u5e26\u5bbd\u4e0d\u8db3\u4ee5\u5904\u7406\u5982\u6b64\u5927\u91cf\u7684\u6570\u636e\u30021080p60\u662f\u5e26\u5bbd\u7684\u4e0a\u9650\u3002 \u5bf9\u4e8eUSB\u6355\u83b7\u8bbe\u5907\uff1a\u4ece\u6280\u672f\u4e0a\u8bb2\uff0c\u662f\u53ef\u4ee5\u7684\uff0c\u4f46\u5b83\u4eec\u4f1a\u964d\u4f4e\u5206\u8fa8\u7387\u4ee5\u9002\u5e94USB 2.0\u7684\u5e26\u5bbd\u9650\u5236\uff0c\u56e0\u6b64\u6d41\u5a92\u4f53\u7684\u5206\u8fa8\u7387\u4e0d\u4f1a\u662f4K\u3002 \u65e0\u8bba\u5982\u4f55\uff0c4K\u5b9e\u65f6\u89c6\u9891\u4e5f\u65e0\u6cd5\u901a\u8fc7\u7f51\u7edc\u4f20\u8f93\u3002 \u5149\u6807/\u89c6\u9891\u5ef6\u8fdf\u662f\u7531\u4ec0\u4e48\u5f15\u8d77\u7684\uff1f \u56fe\u50cf\u4f20\u8f93\u5230\u6d4f\u89c8\u5668\u6216VNC\u5ba2\u6237\u7aef\u7684\u8fc7\u7a0b\u5982\u4e0b\uff1a \u6355\u83b7\u8bbe\u5907 -> \u538b\u7f29 -> \u7f51\u7edc -> \u89e3\u538b\u7f29 -> \u6e32\u67d3 \u5728\u6b64\u8fc7\u7a0b\u4e2d\uff0c100-200ms\u7684\u5ef6\u8fdf\u5df2\u7ecf\u975e\u5e38\u5feb\u901f\u4e86\u3002\u4f46\u6211\u4eec\u6b63\u5728\u52aa\u529b\u8fdb\u4e00\u6b65\u63d0\u9ad8\u901f\u5ea6\u3002 BLIKVM\u652f\u6301\u97f3\u9891\u5417\uff1f BliKVM v1 CM4, v2 PCIe, v3 HAT\u7248\u672c\u652f\u6301\uff0c v4 Allwinner\u7248\u672c\u4e0d\u652f\u6301\u3002 \u6211\u53ef\u4ee5\u901a\u8fc7PoE\u7ed9Pi\u4f9b\u7535\u5417\uff1f \u53ef\u4ee5\uff01Hat\u7248\u672c\u548cPCIe\u7248\u672c\u90fd\u652f\u6301PoE\u3002 \u7b2c\u4e00\u6b65 \u9ed8\u8ba4\u5bc6\u7801\u662f\u4ec0\u4e48\uff1f\u5982\u4f55\u66f4\u6539\u5bc6\u7801\uff1f \u5982\u679c\u60a8\u4f7f\u7528PiKVM\uff0c\u6709\u4e24\u79cd\u7c7b\u578b\u7684\u5e10\u6237\uff1a\u64cd\u4f5c\u7cfb\u7edf\u5e10\u6237\u548cPiKVM\uff08Web\u754c\u9762\uff09\u5e10\u6237\u3002\u7cfb\u7edf\u5e10\u6237 root \u53ef\u7528\u4e8eSSH/UART\u8bbf\u95ee\uff0c\u5bc6\u7801\u4e3a root \u3002Web\u754c\u9762\u5e10\u6237\u79f0\u4e3a admin \uff0c\u5bc6\u7801\u4e3a admin \u3002PiKVM\u5e10\u6237\u4e0d\u80fd\u7528\u4e8eSSH\u8bbf\u95ee\uff0c\u53cd\u4e4b\u4ea6\u7136\u3002 \u8981\u66f4\u6539\u5bc6\u7801\uff0c\u8bf7\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\uff08\u5728root\u7528\u6237\u4e0b\uff09\uff1a su - # \u5982\u679c\u60a8\u5728Webterm\u4e2d rw # \u5207\u6362\u6587\u4ef6\u7cfb\u7edf\u4e3a\u8bfb\u5199\u6a21\u5f0f passwd root # \u66f4\u6539\u64cd\u4f5c\u7cfb\u7edfroot\u5bc6\u7801 kvmd-htpasswd set admin # \u66f4\u6539Web\u754c\u9762\u7ba1\u7406\u5458\u5bc6\u7801 ro # \u5207\u6362\u56de\u53ea\u8bfb\u6a21\u5f0f \u5982\u679c\u60a8\u4f7f\u7528\u7684\u662fBliKVM\uff0cWeb\u754c\u9762\u5e10\u6237\u79f0\u4e3a admin \uff0c\u5bc6\u7801\u4e3a admin ,\u7ec8\u7aef\u7528\u6237\u540d\u79f0\u4e3a blikvm \uff0c\u5bc6\u7801\u4e3a blikvm \u3002 \u5982\u4f55\u6dfb\u52a0\u53e6\u4e00\u4e2a\u7528\u6237\uff1f \u5982\u679c\u60a8\u4f7f\u7528PiKVM\u8f6f\u4ef6\uff0c\u5982\u4e0a\u6240\u8ff0\uff0c\u60a8\u9700\u8981\u521b\u5efa2\u4e2a\u5e10\u6237\uff0c\u4e00\u4e2a\u7528\u4e8eShell\uff0c\u53e6\u4e00\u4e2a\u7528\u4e8ePiKVM Web\u754c\u9762\u3002 \u5982\u679c\u60a8\u9700\u8981\u4e3aPiKVM Web\u754c\u9762\u6dfb\u52a0\u5176\u4ed6\u7528\u6237\uff0c\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\uff1a # rw # su - # kvmd-htpasswd set  # \u6dfb\u52a0\u65b0\u7528\u6237 # kvmd-htpasswd set  # \u8bbe\u7f6e\u5bc6\u7801\uff08\u53ea\u8981\u7528\u6237\u5b58\u5728\uff09 # kvmd-htpasswd del  # \u5220\u9664\u7528\u6237 \u8981\u6dfb\u52a0Shell/\u7ec8\u7aef\u5e10\u6237\uff1a # rw # su - # adduser  # passwd  \u8bf7\u6ce8\u610f\uff0c\u6dfb\u52a0\u7684\u7528\u6237\u8d8a\u591a\uff0c\u8bbf\u95ee\u6d41\u5a92\u4f53\u65f6\u5e27\u7387\u4f1a\u964d\u4f4e\u3002 \u89c6\u9891\u95ee\u9898 BLIKVM\u6839\u672c\u6ca1\u6709\u663e\u793a\u6765\u81ea\u8ba1\u7b97\u673a\u7684\u89c6\u9891 \u8bf7\u4ed4\u7ec6\u68c0\u67e5\u89c6\u9891\u6355\u83b7\u8bbe\u5907\u7684\u8fde\u63a5\u60c5\u51b5\u3002\u5bf9\u4e8eCSI\u6865\u63a5\u5668\uff0c\u5e94\u8fde\u63a5\u5230\u76f8\u673a\u7aef\u53e3\u3002 \u6709\u4e9b\u7b14\u8bb0\u672c\u7535\u8111\u5728\u60a8\u5207\u6362\u8f93\u51fa\u4e4b\u524d\uff08\u901a\u5e38\u901a\u8fc7\u952e\u76d8\u4e0a\u7684FN +\u548cF5\u952e\uff09\u4e0d\u4f1a\u8f93\u51fa\u4efb\u4f55\u4fe1\u53f7\u3002 \u60a8\u7684\u8ba1\u7b97\u673a\u53ef\u80fd\u5df2\u7ecf\u5c06\u663e\u793a\u5668\u8bbe\u7f6e\u4e3a\u7761\u7720\u6a21\u5f0f\u3002\u79fb\u52a8\u9f20\u6807\u4ee5\u5173\u95ed\u7761\u7720\u6a21\u5f0f\u3002 \u5bf9\u4e8eWindows\u7cfb\u7edf\uff0c\u60a8\u53ef\u80fd\u9700\u8981\u68c0\u67e5\u6d3b\u52a8\u4fe1\u53f7\u5206\u8fa8\u7387\u3002\u8981\u66f4\u6539\u6d3b\u52a8\u4fe1\u53f7\u5206\u8fa8\u7387\uff0c\u8bf7\u8f6c\u5230\u201c\u8bbe\u7f6e\u201d>\u201c\u7cfb\u7edf\u201d>\u201c\u663e\u793a\u201d>\u201c\u9ad8\u7ea7\u663e\u793a\u8bbe\u7f6e\u201d>\u201c\u663e\u793a\u9002\u914d\u5668\u5c5e\u6027\u201d\uff0c\u7136\u540e\u70b9\u51fb\u201c\u5217\u51fa\u6240\u6709\u6a21\u5f0f\u201d\uff0c\u9009\u62e9\u6240\u9700\u7684\u6a21\u5f0f\u3002\u5c1d\u8bd5\u4e0d\u540c\u7684\u5237\u65b0\u7387\u8bbe\u7f6e\u3002 \u5728\u5df2\u542f\u52a8\u7684\u64cd\u4f5c\u7cfb\u7edf\u4e2d\u53ef\u4ee5\u770b\u5230\u89c6\u9891\uff0c\u4f46\u5728BIOS/UEFI\u4e2d\u770b\u4e0d\u5230 \u5f53\u4f7f\u7528CSI\u6865\u63a5\u5668\u65f6\uff0cIntel NUC\u3001GA-H77-DS3H\u548c\u4e00\u4e9b\u5176\u4ed6\u8bbe\u5907\u4e0a\u4f1a\u51fa\u73b0\u6b64\u95ee\u9898\u3002\u60a8\u53ea\u9700\u8981\u66f4\u6539EDID\u6570\u636e\uff0c\u8fd9\u662fCSI\u6865\u63a5\u5668\u5411\u8ba1\u7b97\u673a\u62a5\u544a\u7684\u652f\u6301\u7684\u5206\u8fa8\u7387\u4fe1\u606f\u3002 BIOS/UEFI\u5206\u8fa8\u7387\u51fa\u73b0\u6545\u969c\u6216\u9519\u8bef \u5728\u67d0\u4e9b\u4e3b\u677f\u4e0a\uff0cBIOS\u53ef\u80fd\u4ee5\u8f83\u4f4e\u7684\u5206\u8fa8\u7387\u663e\u793a\uff0c\u6216\u51fa\u73b0\u4e00\u4e9b\u6e32\u67d3\u95ee\u9898/\u6545\u969c\uff0c\u7279\u522b\u662f\u5728\u8f83\u65b0\u7684ASUS\u4e3b\u677f\u4e0a\u3002\u5982\u4e0b\u56fe\u6240\u793a\uff1a \u60a8\u53ef\u4ee5\u901a\u8fc7\u5728BIOS\u4e2d\u542f\u7528 \u517c\u5bb9\u6027\u652f\u6301\u6a21\u5757\uff08CSM\uff09 \u6765\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u901a\u5e38\u4f4d\u4e8e \u5f15\u5bfc \u9009\u9879\u4e0b\u3002 \u5982\u679c\u60a8\u65e0\u6cd5\u6216\u4e0d\u60f3\u542f\u7528CSM\uff0c\u60a8\u53ef\u4ee5\u5c1d\u8bd5\u8fde\u63a5\u4e00\u4e2aDisplayPort\uff08DP\uff09\u663e\u793a\u5668\u6216 \u865a\u62df\u63d2\u5934 \u3002\u5982\u679c\u62d4\u6389DP\u7535\u7f06/\u8f6c\u63a5\u5668\uff0c\u95ee\u9898\u5c06\u91cd\u65b0\u51fa\u73b0\u3002 \u5982\u679c\u4e0a\u8ff0\u65b9\u6cd5\u90fd\u4e0d\u8d77\u4f5c\u7528\uff0c\u8bf7\u5c1d\u8bd5\u5148\u8fde\u63a5DP\u7535\u7f06\uff0c\u7136\u540e\u542f\u52a8\u5230BIOS\uff0c\u7981\u7528CSM\u5e76\u5173\u673a\uff08\u4e0d\u8981\u91cd\u65b0\u542f\u52a8\uff09\u60a8\u7684\u8ba1\u7b97\u673a\u3002\u7136\u540e\uff0c\u5728\u518d\u6b21\u542f\u52a8\u5230BIOS\u5e76\u542f\u7528CSM\u4e4b\u524d\uff0c\u8fde\u63a5HDMI\u5e76\u518d\u6b21\u6253\u5f00\u8ba1\u7b97\u673a\u3002 GRUB2\u4e2d\u6ca1\u6709\u89c6\u9891\uff0c\u4f46\u4e4b\u524d\u548c\u4e4b\u540e\u90fd\u6709 \u6709\u65f6\u8fd9\u53ef\u80fd\u662f\u7531\u4e8eBIOS/UEFI\u7684\u7279\u5b9a\u95ee\u9898\u4ee5\u53caGRUB2\u4e0e\u89c6\u9891\u7684\u5de5\u4f5c\u65b9\u5f0f\u6240\u5bfc\u81f4\u7684\u3002 \u60a8\u53ef\u4ee5\u901a\u8fc7\u5728BIOS\u4e2d\u542f\u7528 \u517c\u5bb9\u6027\u652f\u6301\u6a21\u5757\uff08CSM\uff09 \u6765\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u901a\u5e38\u4f4d\u4e8e \u5f15\u5bfc \u9009\u9879\u4e0b\u3002\u89c6\u9891\u6a21\u5f0f\u4e5f\u4f4d\u4e8e\u540c\u4e00\u90e8\u5206\u3002\u5c06 \u89c6\u9891 \u6a21\u5f0f\u4ece UEFI \u5207\u6362\u4e3a Legacy \u3002 Linux + Awesome WM\u6ca1\u6709\u8ba1\u7b97\u673a\u56fe\u50cf \u6709\u65f6\uff0c\u5728Linux\u4e0a\u4f7f\u7528Awesome WM\u53ef\u80fd\u65e0\u6cd5\u8bc6\u522b\u7535\u7f06\u7684\u89c6\u9891\u8f93\u51fa\u66f4\u6539\u3002\u4e5f\u5c31\u662f\u8bf4\uff0c\u5982\u679c\u7535\u7f06\u5148\u63d2\u5165\u663e\u793a\u5668\uff0c\u7136\u540e\u518d\u8fde\u63a5\u5230BLIKVM\uff0c\u53ef\u80fd\u4f1a\u5bfc\u81f4\u60a8\u770b\u4e0d\u5230\u56fe\u50cf\u3002\u8fd9\u4f3c\u4e4e\u662fAwesome WM\u7684\u95ee\u9898\uff0c\u56e0\u4e3a\u4f8b\u5982\u5728KDE\u4e2d\uff0c\u8fd9\u79cd\u60c5\u51b5\u65e0\u6cd5\u590d\u73b0\u3002\u5982\u679c\u60a8\u5728\u8fde\u63a5BLIKVM\u540e\u542f\u52a8\u5de5\u4f5c\u7ad9\uff0c\u4e00\u5207\u90fd\u5c06\u6b63\u5e38\u5de5\u4f5c\u3002 USB\u95ee\u9898\uff08\u952e\u76d8\u3001\u9f20\u6807\u3001U\u76d8\u7b49\uff09 USB OTG\u7aef\u53e3\u7684\u901f\u5ea6\u662f\u591a\u5c11\uff1f \u6839\u636e\u5b98\u65b9\u7684RPI\u6587\u6863\uff0c\u8fd9\u662fSoC\u7684\u9650\u5236\u3002OTG\u7aef\u53e3\u53ea\u652f\u6301USB 2.0\uff0c\u56e0\u6b64\u901f\u5ea6\u9650\u5236\u4e3a455 Mbit/s\u3002 \u4e3a\u4ec0\u4e48\u65e0\u6cd5\u6355\u83b7\u67d0\u4e9b\u5b9e\u4f53\u952e\u76d8\u7684\u952e\u76d8\u5feb\u6377\u952e\uff0c\u4f46\u53ef\u4ee5\u6355\u83b7\u865a\u62df\u952e\u76d8\u7684\u952e\u76d8\u5feb\u6377\u952e\uff1f\u4f8b\u5982\uff0c\u65e0\u6cd5\u6355\u83b7Mac\u7535\u8111\u7684F11\u6309\u952e \u8fd9\u662f\u56e0\u4e3a\u4e00\u4e9b\u5feb\u6377\u952e\u5df2\u7ecf\u88ab\u64cd\u4f5c\u7cfb\u7edf\u4f7f\u7528\u4e86\uff0c\u4f8b\u5982\u5728 macOS \u4e2d\uff0cF11 \u88ab\u9ed8\u8ba4\u5206\u914d\u7ed9\u4e86\u201c\u663e\u793a\u684c\u9762\u201d\u7684\u529f\u80fd\u3002\u5f53\u60a8\u5728Web\u754c\u9762\u6309\u4e0bF11\u65f6\uff0c\u952e\u76d8\u4e8b\u4ef6\u9996\u5148\u88ab\u64cd\u4f5c\u7cfb\u7edf\u6355\u83b7\uff0c\u5982\u679c\u64cd\u4f5c\u7cfb\u7edf\u6ce8\u518c\u4e86\u56de\u8c03\u51fd\u6570\uff0c\u952e\u76d8\u4e8b\u4ef6\u5c06\u4e0d\u4f1a\u4f20\u9012\u7ed9\u5e94\u7528\u7a0b\u5e8f\u3002\u8981\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u60a8\u53ef\u4ee5\u5173\u95ed\u64cd\u4f5c\u7cfb\u7edf\u8bbe\u7f6e\u4e2d\u7684\u5feb\u6377\u952e\uff0c\u6216\u8005\u4f7f\u7528\u865a\u62df\u952e\u76d8\u3002 \u786c\u4ef6\u95ee\u9898\uff08Wi-Fi\u3001ATX\u7b49\uff09 \u5982\u679c\u4f7f\u7528PiKVM\u8f6f\u4ef6\uff0cWeb\u754c\u9762\u663e\u793a FAN \u9519\u8bef\uff01 \u7531\u4e8eBLIKVM\u786c\u4ef6\u4f7f\u7528\u7684\u98ce\u6247\u578b\u53f7\u4e0ePIKVM\u786c\u4ef6\u4e0d\u540c\uff0c\u56e0\u6b64\u5728pikvm\u7684\u6700\u65b0\u7cfb\u7edf\u4e2d\uff0c\u901a\u8fc7Web\u754c\u9762\u67e5\u770b\u98ce\u6247\u72b6\u6001\u53ef\u80fd\u4f1a\u5931\u8d25\u3002\u4f46\u8fd9\u4e0d\u4f1a\u5f71\u54cdBLIKVM\u98ce\u6247\u7684\u6b63\u5e38\u8fd0\u884c\u3002\u56e0\u6b64\uff0c\u5728\u4f7f\u7528PIKVM\u955c\u50cf\u65f6\uff0c\u53ea\u8981\u786e\u4fdd \u5b89\u88c5\u811a\u672c \u663e\u793aOK\uff0c\u5c31\u8868\u793akvmd\u98ce\u6247\u7a0b\u5e8f\u7684\u66f4\u65b0\u6210\u529f\u3002\u9ed8\u8ba4\u7a0b\u5e8f\u8bbe\u7f6e\u7684\u6e29\u5ea6\u9608\u503c\u4e3a\u6444\u6c0f60\u5ea6\u3002\u5f53\u68c0\u6d4b\u5230CPU\u6e29\u5ea6\u8d85\u8fc760\u6444\u6c0f\u5ea6\u65f6\uff0c\u98ce\u6247\u5c06\u4ee585%\u7684\u901f\u5ea6\u5f00\u59cb\u65cb\u8f6c\u3002\u5982\u679c\u8981\u4fee\u6539\u6e29\u5ea6\u9608\u503c\u548c\u901f\u5ea6\uff0c\u53ef\u4ee5\u4fee\u6539kvmd-fan.py\u811a\u672c\uff0c\u7136\u540e\u91cd\u65b0\u6267\u884cinstall.sh\u3002 \u6211\u6839\u672c\u65e0\u6cd5\u8fde\u63a5\u5230Wi-Fi\uff01 \u5982\u679c\u60a8\u7684\u8bbe\u5907\u65e0\u6cd5\u8fde\u63a5\u5230\u60a8\u8bbe\u7f6e\u7684Wi-Fi\u7f51\u7edc\uff0c\u8bf7\u68c0\u67e5\u60a8\u7684Wi-Fi\u63a5\u5165\u70b9\u4f7f\u7528\u76842.4GHz Wi-Fi\u4fe1\u9053\u3002\u5982\u679c\u4f7f\u7528\u4e8612\u523014\u4fe1\u9053\uff08\u67d0\u4e9b\u56fd\u5bb6\u7981\u6b62\u4f7f\u7528\u8fd9\u4e9b\u4fe1\u9053\uff09\uff0c\u8bf7\u5c1d\u8bd5\u4f7f\u75281\u523011\u4e4b\u95f4\u7684\u4fe1\u9053\u3002 BLIKVM\u663e\u793a\u4f4e\u7535\u538b\u8b66\u544a \u60a8\u662f\u5426\u4f7f\u7528\u4e86\u201c\u6b63\u786e\u201d\u7684\u7535\u6e90\u9002\u914d\u5668\uff1f\u800c\u4e0d\u662f\u81ea\u5df1\u62fc\u51d1\u7684\u9002\u914d\u5668\uff1f \u4e00\u4e9bUSB\u7535\u6e90\u9002\u914d\u5668\u5ba3\u4f20\u4e3a5V 2.1A\u6216\u66f4\u9ad8\uff0c\u4f46\u65e0\u6cd5\u63d0\u4f9b\u7a33\u5b9a\u76845V\u7535\u538b\u3002\u6700\u597d\u4f7f\u7528\u6811\u8393\u6d3e\u57fa\u91d1\u4f1a\u63a8\u8350\u7684\u7535\u6e90\u9002\u914d\u5668\u3002\u5176\u8f93\u51fa\u5e94\u4e3a5.1V\u548c3A\u76f4\u6d41\u7535\u538b\u3002 \u5f53\u6211\u4f7f\u7528PoE\u65f6\uff0c\u662f\u5426\u4ecd\u7136\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u6765\u9632\u6b62\u673a\u5668USB\u7684\u53cd\u5411\u4f9b\u7535\uff1f \u53ea\u6709HAT\u7248\u672c\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u6765\u9632\u6b62\u53cd\u5411\u4f9b\u7535\u3002\u901a\u5e38\uff0c\u5927\u591a\u6570\u4e3b\u673a\u8ba1\u7b97\u673a\u90fd\u6709\u53cd\u5411\u4f9b\u7535\u4fdd\u62a4\uff0c\u56e0\u6b64\u5728\u8fd9\u79cd\u60c5\u51b5\u4e0b\u4e0d\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u3002 BLIKVM-CM4-V2.2\u548cBLIKVM-PCIe\u7248\u672c\u4e0d\u9700\u8981\u3002 \u5728\u4e00\u4e9b\u50cfBLIKVM-PCIe\u6216BLIKVM-CM4-V2.2\u8fd9\u6837\u7684\u677f\u5b50\u4e0a\u6709\u5f15\u5bfc\u5f15\u811a\uff0c\u5982\u4f55\u8fde\u63a5\uff1f \u5982\u679c\u5c06\u5b83\u4eec\u8fde\u63a5\u77ed\u8def\uff0cCM4\u5c06\u65e0\u6cd5\u6b63\u5e38\u542f\u52a8\uff0c\u800c\u5c06\u8fdb\u5165\u70e7\u5f55\u6620\u50cf\u6a21\u5f0f\u3002\u5982\u679c\u60a8\u7684\u786c\u4ef6\u7248\u672c\u7684\u5f15\u5bfc\u5f15\u811a\u53ea\u6709\u4e24\u4e2a\u5f15\u811a\uff0c\u4f7f\u7528\u8df3\u7ebf\u5e3d\u5c06\u8fd9\u4e24\u4e2a\u5f15\u811a\u8fde\u63a5\u8d77\u6765\uff0c\u5f62\u6210\u77ed\u8def\u3002\u5982\u679c\u60a8\u4e0d\u4f7f\u7528\u8df3\u7ebf\u5e3d\u6216\u53ea\u5c06\u5176\u63d2\u5165\u4e00\u4e2a\u5f15\u811a\uff0cCM4\u5c06\u6b63\u5e38\u542f\u52a8\u3002\u5982\u679c\u60a8\u4f7f\u7528\u7684\u662f\u4e09\u4e2a\u5f15\u5bfc\u5f15\u811a\u7684\u786c\u4ef6\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u8df3\u7ebf\u5e3d\u5c06GND\u548c\u53e6\u4e00\u4e2a\u975eGND\u5f15\u811a\u8fde\u63a5\u8d77\u6765\u4ee5\u793a\u77ed\u8def\uff0c\u5e76\u5c06\u8df3\u7ebf\u5e3d\u63d2\u5728\u4e24\u4e2aGND\u5f15\u811a\u4e0a\u6216\u4e0d\u4f7f\u7528\u8df3\u7ebf\u5e3d\uff0cCM4\u5c06\u6b63\u5e38\u542f\u52a8\u3002 Web\u95ee\u9898 BliKVM OS\u5360\u7528\u7684\u7aef\u53e3\u6709\u54ea\u4e9b\uff0c\u5728\u7528\u516c\u7f51\u670d\u52a1\u5668\u8f6c\u53d1\u65f6\uff0c\u5e94\u8be5\u600e\u4e48\u505a\uff1f Web\u754c\u9762\u4e3ahttp\u534f\u8bae\uff0c\u5360\u7528\u7684\u662f80\u7aef\u53e3\uff1b \u5982\u679c\u60a8\u7684\u786c\u4ef6\u662fV1 V2 V3\uff0c\u4f7f\u7528\u7684\u662f\u662fweb-rtc\u4f20\u8f93\uff0c\u7aef\u53e3\u662f8188\uff1b \u5982\u679c\u60a8\u7684\u786c\u4ef6\u662fV4\uff0c\u4f7f\u7528\u7684\u662fmjepg\u4f20\u8f93\uff0c\u7aef\u53e3\u662f8008\uff1b \u6ce8\u610f\u7aef\u53e3\u4e0d\u652f\u6301\u88ab\u4fee\u6539\uff0c\u53ea\u80fd\u914d\u7f6e\u8f6c\u53d1\uff1b \u6811\u8393\u6d3e\u76f8\u5173\u95ee\u9898 \u6211\u662f\u5426\u53ef\u4ee5\u540c\u65f6\u4f7f\u7528\u5e26eMMC\u7248\u672c\u7684CM4\u548cSD\u5361? \u4e0d\u53ef\u4ee5\uff0c\u56e0\u4e3a\u5728CM4\u786c\u4ef6\u8bbe\u8ba1\u4e0a\uff0c\u51e0\u4e2aSD\u5361\u7684\u5f15\u811a\u53ea\u5728lite\u7248\u672c\u4e2d\u662f\u53ef\u7528\u7684\uff0c\u4f60\u53ef\u4ee5\u5728\u6811\u8393\u6d3e\u5b98\u7f51\u627e\u5230\u8bf4\u660e\u3002","title":"\u5e38\u89c1\u95ee\u9898\u89e3\u7b54"},{"location":"faq/#faq","text":"\u4f5c\u4e3a\u7b2c\u4e00\u6b65\uff0c\u6211\u4eec\u5efa\u8bae\u4ed4\u7ec6\u9605\u8bfb\u6211\u4eec\u7684\u6587\u6863\u3002\u5927\u90e8\u5206\u8bbe\u7f6eBLIKVM\u6240\u9700\u7684\u6b65\u9aa4\u5df2\u7ecf\u5728\u6587\u6863\u4e2d\u63cf\u8ff0\u4e86\u3002\u5982\u679c\u60a8\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u60a8\u53ef\u4ee5\u67e5\u770b\u672c\u9875\uff0c\u5176\u4e2d\u5217\u51fa\u4e86\u5e38\u89c1\u9519\u8bef\u3002\u5982\u679c\u4ecd\u7136\u65e0\u6cd5\u89e3\u51b3\u95ee\u9898\uff0c\u6b22\u8fce\u63d0\u4ea4 \u95ee\u9898\u53cd\u9988 \u6216 \u52a0\u5165\u6211\u4eec\u7684Discord \u5bfb\u6c42\u8fdb\u4e00\u6b65\u5e2e\u52a9\u3002","title":"FAQ & \u6545\u969c\u6392\u9664"},{"location":"faq/#_1","text":"\u6211\u53ef\u4ee5\u5c06\u591a\u53f0\u670d\u52a1\u5668\u8fde\u63a5\u5230\u5355\u4e2aBLIKVM\u5417\uff1f \u53ef\u4ee5\uff0c\u4f46\u9700\u8981\u8fdb\u884c\u989d\u5916\u7684\u8bbe\u7f6e\u5de5\u4f5c\u3002\u8bf7\u53c2\u8003 \u6b64\u9875\u9762 \u3002 \u5982\u4f55\u5728\u672c\u5730\u7f51\u7edc\u4e0a\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95eeBliKVM\uff1f \u5982\u679c\u60a8\u7684\u8def\u7531\u5668\u5177\u6709\u5916\u90e8IP\u5730\u5740\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u7aef\u53e3\u8f6c\u53d1\u6765\u8f6c\u53d180\u7aef\u53e3(Web),8008\u7aef\u53e3(mjpeg)\uff0c8188\u7aef\u53e3\uff08webrtc\uff09\u3002\u5728\u5176\u4ed6\u60c5\u51b5\u4e0b\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u51fa\u8272\u7684\u514d\u8d39VPN\u670d\u52a1Tailscale\u3002 BLiKVM\u6709\u591a\u6b3e\u786c\u4ef6\uff0c\u5982BliKVM V1 CM4\u3001BliKVM V2 PCIe\u3001BliKVM V3 Hat\uff0c\u6211\u5e94\u8be5\u9009\u54ea\u6b3e\uff1f \u9996\u5148\u5404\u4e2a\u7248\u672c\u7684\u4e3b\u8981\u53c2\u6570\u5bf9\u6bd4\u8bf7\u53c2\u8003 \u6b64\u9875\u9762 \u3002 V1\u548cV3\u5c5e\u4e8e\u5916\u7f6e\u65b9\u6848\uff0cV2\u5c5e\u4e8e\u5185\u7f6e\u673a\u7bb1\u65b9\u6848\u3002\u5982\u679c\u60a8\u662f\u673a\u7bb1\u5f62\u5f0f\uff0c\u5e76\u4e14\u673a\u7bb1\u5185\u90e8\u6709\u7a7a\u95f4\uff0c\u90a3\u4e48\u6beb\u65e0\u7591\u95ee\u9009\u62e9V2 PCIe\u7248\u672c\u662f\u8f83\u597d\u7684\u9009\u62e9\u3002 \u90a3\u4e48V1\u548cV3\u4e24\u4e2a\u5916\u7f6e\u65b9\u6848\u5982\u4f55\u9009\u62e9\u5462\uff0cV1\u57fa\u4e8eCM4\u7684\u65b9\u6848\uff0c\u96c6\u6210\u5ea6\u66f4\u9ad8\uff0c\u6709\u5230\u624b\u53ef\u7528\u7248\u672c\u3002V3\u57fa\u4e8e\u6811\u8393\u6d3e4B\u65b9\u6848\uff0c\u6240\u6709IO\u53e3\u5747\u5f15\u51fa\uff0c\u53ef\u6269\u5c55\u6027\u66f4\u5f3a\u3002\u4e24\u8005\u7684\u53e6\u4e00\u4e2a\u6838\u5fc3\u533a\u522b\u5c31\u662fV1\u6700\u9ad8\u652f\u63011080P60Hz\u8f93\u5165\uff0cV3\u6700\u9ad8\u652f\u63011080P50Hz\u8f93\u5165\u3002\u5f53\u7136\u540c\u65f6\u9700\u8981\u8003\u8651\u60a8\u662f\u5df2\u5426\u6709CM4\u6216\u80054B\uff0c\u5982\u679c\u6709\u7684\u8bdd\u53ea\u4e70\u5bf9\u5e94\u7684\u5e95\u677f\uff0c\u6027\u4ef7\u6bd4\u66f4\u9ad8\u3002 \u6211\u53ef\u4ee5\u7528BLIKVM\u8fdb\u884c\u6e38\u620f\u5417\uff1f \u4e0d\u53ef\u4ee5\uff0c\u539f\u56e0\u5982\u4e0b\uff1a \u5bf9\u4e8eHDMI-CSI\u6865\u63a5\u5668\uff0c\u603b\u7ebf\u5e26\u5bbd\u4e0d\u8db3\u4ee5\u4f20\u8f93\u8d85\u8fc71080p60\u7684\u89c6\u9891\u3002 \u5bf9\u4e8eHDMI-USB\u8f6c\u6362\u5668\uff0c\u5ef6\u8fdf\u8f83\u9ad8\u4e14\u89c6\u9891\u8d28\u91cf\u8f83\u4f4e\u3002 \u4e00\u822c\u7684\u786c\u4ef6\u89c6\u9891\u6355\u83b7\u4e0e\u8f6f\u4ef6\u6d41\u5a92\u4f53\u6709\u6240\u4e0d\u540c\uff0c\u4f1a\u5f15\u5165\u989d\u5916\u7684\u5ef6\u8fdf\u3002 BLIKVM\u652f\u63014K\u89c6\u9891\u5417\uff1f \u5bf9\u4e8eHDMI-CSI\u6865\u63a5\u5668\uff0c\u4e0d\u652f\u6301\u3002CSI\u603b\u7ebf\u7684\u5e26\u5bbd\u4e0d\u8db3\u4ee5\u5904\u7406\u5982\u6b64\u5927\u91cf\u7684\u6570\u636e\u30021080p60\u662f\u5e26\u5bbd\u7684\u4e0a\u9650\u3002 \u5bf9\u4e8eUSB\u6355\u83b7\u8bbe\u5907\uff1a\u4ece\u6280\u672f\u4e0a\u8bb2\uff0c\u662f\u53ef\u4ee5\u7684\uff0c\u4f46\u5b83\u4eec\u4f1a\u964d\u4f4e\u5206\u8fa8\u7387\u4ee5\u9002\u5e94USB 2.0\u7684\u5e26\u5bbd\u9650\u5236\uff0c\u56e0\u6b64\u6d41\u5a92\u4f53\u7684\u5206\u8fa8\u7387\u4e0d\u4f1a\u662f4K\u3002 \u65e0\u8bba\u5982\u4f55\uff0c4K\u5b9e\u65f6\u89c6\u9891\u4e5f\u65e0\u6cd5\u901a\u8fc7\u7f51\u7edc\u4f20\u8f93\u3002 \u5149\u6807/\u89c6\u9891\u5ef6\u8fdf\u662f\u7531\u4ec0\u4e48\u5f15\u8d77\u7684\uff1f \u56fe\u50cf\u4f20\u8f93\u5230\u6d4f\u89c8\u5668\u6216VNC\u5ba2\u6237\u7aef\u7684\u8fc7\u7a0b\u5982\u4e0b\uff1a \u6355\u83b7\u8bbe\u5907 -> \u538b\u7f29 -> \u7f51\u7edc -> \u89e3\u538b\u7f29 -> \u6e32\u67d3 \u5728\u6b64\u8fc7\u7a0b\u4e2d\uff0c100-200ms\u7684\u5ef6\u8fdf\u5df2\u7ecf\u975e\u5e38\u5feb\u901f\u4e86\u3002\u4f46\u6211\u4eec\u6b63\u5728\u52aa\u529b\u8fdb\u4e00\u6b65\u63d0\u9ad8\u901f\u5ea6\u3002 BLIKVM\u652f\u6301\u97f3\u9891\u5417\uff1f BliKVM v1 CM4, v2 PCIe, v3 HAT\u7248\u672c\u652f\u6301\uff0c v4 Allwinner\u7248\u672c\u4e0d\u652f\u6301\u3002 \u6211\u53ef\u4ee5\u901a\u8fc7PoE\u7ed9Pi\u4f9b\u7535\u5417\uff1f \u53ef\u4ee5\uff01Hat\u7248\u672c\u548cPCIe\u7248\u672c\u90fd\u652f\u6301PoE\u3002","title":"\u5e38\u89c1\u95ee\u9898"},{"location":"faq/#_2","text":"\u9ed8\u8ba4\u5bc6\u7801\u662f\u4ec0\u4e48\uff1f\u5982\u4f55\u66f4\u6539\u5bc6\u7801\uff1f \u5982\u679c\u60a8\u4f7f\u7528PiKVM\uff0c\u6709\u4e24\u79cd\u7c7b\u578b\u7684\u5e10\u6237\uff1a\u64cd\u4f5c\u7cfb\u7edf\u5e10\u6237\u548cPiKVM\uff08Web\u754c\u9762\uff09\u5e10\u6237\u3002\u7cfb\u7edf\u5e10\u6237 root \u53ef\u7528\u4e8eSSH/UART\u8bbf\u95ee\uff0c\u5bc6\u7801\u4e3a root \u3002Web\u754c\u9762\u5e10\u6237\u79f0\u4e3a admin \uff0c\u5bc6\u7801\u4e3a admin \u3002PiKVM\u5e10\u6237\u4e0d\u80fd\u7528\u4e8eSSH\u8bbf\u95ee\uff0c\u53cd\u4e4b\u4ea6\u7136\u3002 \u8981\u66f4\u6539\u5bc6\u7801\uff0c\u8bf7\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\uff08\u5728root\u7528\u6237\u4e0b\uff09\uff1a su - # \u5982\u679c\u60a8\u5728Webterm\u4e2d rw # \u5207\u6362\u6587\u4ef6\u7cfb\u7edf\u4e3a\u8bfb\u5199\u6a21\u5f0f passwd root # \u66f4\u6539\u64cd\u4f5c\u7cfb\u7edfroot\u5bc6\u7801 kvmd-htpasswd set admin # \u66f4\u6539Web\u754c\u9762\u7ba1\u7406\u5458\u5bc6\u7801 ro # \u5207\u6362\u56de\u53ea\u8bfb\u6a21\u5f0f \u5982\u679c\u60a8\u4f7f\u7528\u7684\u662fBliKVM\uff0cWeb\u754c\u9762\u5e10\u6237\u79f0\u4e3a admin \uff0c\u5bc6\u7801\u4e3a admin ,\u7ec8\u7aef\u7528\u6237\u540d\u79f0\u4e3a blikvm \uff0c\u5bc6\u7801\u4e3a blikvm \u3002 \u5982\u4f55\u6dfb\u52a0\u53e6\u4e00\u4e2a\u7528\u6237\uff1f \u5982\u679c\u60a8\u4f7f\u7528PiKVM\u8f6f\u4ef6\uff0c\u5982\u4e0a\u6240\u8ff0\uff0c\u60a8\u9700\u8981\u521b\u5efa2\u4e2a\u5e10\u6237\uff0c\u4e00\u4e2a\u7528\u4e8eShell\uff0c\u53e6\u4e00\u4e2a\u7528\u4e8ePiKVM Web\u754c\u9762\u3002 \u5982\u679c\u60a8\u9700\u8981\u4e3aPiKVM Web\u754c\u9762\u6dfb\u52a0\u5176\u4ed6\u7528\u6237\uff0c\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\uff1a # rw # su - # kvmd-htpasswd set  # \u6dfb\u52a0\u65b0\u7528\u6237 # kvmd-htpasswd set  # \u8bbe\u7f6e\u5bc6\u7801\uff08\u53ea\u8981\u7528\u6237\u5b58\u5728\uff09 # kvmd-htpasswd del  # \u5220\u9664\u7528\u6237 \u8981\u6dfb\u52a0Shell/\u7ec8\u7aef\u5e10\u6237\uff1a # rw # su - # adduser  # passwd  \u8bf7\u6ce8\u610f\uff0c\u6dfb\u52a0\u7684\u7528\u6237\u8d8a\u591a\uff0c\u8bbf\u95ee\u6d41\u5a92\u4f53\u65f6\u5e27\u7387\u4f1a\u964d\u4f4e\u3002","title":"\u7b2c\u4e00\u6b65"},{"location":"faq/#_3","text":"BLIKVM\u6839\u672c\u6ca1\u6709\u663e\u793a\u6765\u81ea\u8ba1\u7b97\u673a\u7684\u89c6\u9891 \u8bf7\u4ed4\u7ec6\u68c0\u67e5\u89c6\u9891\u6355\u83b7\u8bbe\u5907\u7684\u8fde\u63a5\u60c5\u51b5\u3002\u5bf9\u4e8eCSI\u6865\u63a5\u5668\uff0c\u5e94\u8fde\u63a5\u5230\u76f8\u673a\u7aef\u53e3\u3002 \u6709\u4e9b\u7b14\u8bb0\u672c\u7535\u8111\u5728\u60a8\u5207\u6362\u8f93\u51fa\u4e4b\u524d\uff08\u901a\u5e38\u901a\u8fc7\u952e\u76d8\u4e0a\u7684FN +\u548cF5\u952e\uff09\u4e0d\u4f1a\u8f93\u51fa\u4efb\u4f55\u4fe1\u53f7\u3002 \u60a8\u7684\u8ba1\u7b97\u673a\u53ef\u80fd\u5df2\u7ecf\u5c06\u663e\u793a\u5668\u8bbe\u7f6e\u4e3a\u7761\u7720\u6a21\u5f0f\u3002\u79fb\u52a8\u9f20\u6807\u4ee5\u5173\u95ed\u7761\u7720\u6a21\u5f0f\u3002 \u5bf9\u4e8eWindows\u7cfb\u7edf\uff0c\u60a8\u53ef\u80fd\u9700\u8981\u68c0\u67e5\u6d3b\u52a8\u4fe1\u53f7\u5206\u8fa8\u7387\u3002\u8981\u66f4\u6539\u6d3b\u52a8\u4fe1\u53f7\u5206\u8fa8\u7387\uff0c\u8bf7\u8f6c\u5230\u201c\u8bbe\u7f6e\u201d>\u201c\u7cfb\u7edf\u201d>\u201c\u663e\u793a\u201d>\u201c\u9ad8\u7ea7\u663e\u793a\u8bbe\u7f6e\u201d>\u201c\u663e\u793a\u9002\u914d\u5668\u5c5e\u6027\u201d\uff0c\u7136\u540e\u70b9\u51fb\u201c\u5217\u51fa\u6240\u6709\u6a21\u5f0f\u201d\uff0c\u9009\u62e9\u6240\u9700\u7684\u6a21\u5f0f\u3002\u5c1d\u8bd5\u4e0d\u540c\u7684\u5237\u65b0\u7387\u8bbe\u7f6e\u3002 \u5728\u5df2\u542f\u52a8\u7684\u64cd\u4f5c\u7cfb\u7edf\u4e2d\u53ef\u4ee5\u770b\u5230\u89c6\u9891\uff0c\u4f46\u5728BIOS/UEFI\u4e2d\u770b\u4e0d\u5230 \u5f53\u4f7f\u7528CSI\u6865\u63a5\u5668\u65f6\uff0cIntel NUC\u3001GA-H77-DS3H\u548c\u4e00\u4e9b\u5176\u4ed6\u8bbe\u5907\u4e0a\u4f1a\u51fa\u73b0\u6b64\u95ee\u9898\u3002\u60a8\u53ea\u9700\u8981\u66f4\u6539EDID\u6570\u636e\uff0c\u8fd9\u662fCSI\u6865\u63a5\u5668\u5411\u8ba1\u7b97\u673a\u62a5\u544a\u7684\u652f\u6301\u7684\u5206\u8fa8\u7387\u4fe1\u606f\u3002 BIOS/UEFI\u5206\u8fa8\u7387\u51fa\u73b0\u6545\u969c\u6216\u9519\u8bef \u5728\u67d0\u4e9b\u4e3b\u677f\u4e0a\uff0cBIOS\u53ef\u80fd\u4ee5\u8f83\u4f4e\u7684\u5206\u8fa8\u7387\u663e\u793a\uff0c\u6216\u51fa\u73b0\u4e00\u4e9b\u6e32\u67d3\u95ee\u9898/\u6545\u969c\uff0c\u7279\u522b\u662f\u5728\u8f83\u65b0\u7684ASUS\u4e3b\u677f\u4e0a\u3002\u5982\u4e0b\u56fe\u6240\u793a\uff1a \u60a8\u53ef\u4ee5\u901a\u8fc7\u5728BIOS\u4e2d\u542f\u7528 \u517c\u5bb9\u6027\u652f\u6301\u6a21\u5757\uff08CSM\uff09 \u6765\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u901a\u5e38\u4f4d\u4e8e \u5f15\u5bfc \u9009\u9879\u4e0b\u3002 \u5982\u679c\u60a8\u65e0\u6cd5\u6216\u4e0d\u60f3\u542f\u7528CSM\uff0c\u60a8\u53ef\u4ee5\u5c1d\u8bd5\u8fde\u63a5\u4e00\u4e2aDisplayPort\uff08DP\uff09\u663e\u793a\u5668\u6216 \u865a\u62df\u63d2\u5934 \u3002\u5982\u679c\u62d4\u6389DP\u7535\u7f06/\u8f6c\u63a5\u5668\uff0c\u95ee\u9898\u5c06\u91cd\u65b0\u51fa\u73b0\u3002 \u5982\u679c\u4e0a\u8ff0\u65b9\u6cd5\u90fd\u4e0d\u8d77\u4f5c\u7528\uff0c\u8bf7\u5c1d\u8bd5\u5148\u8fde\u63a5DP\u7535\u7f06\uff0c\u7136\u540e\u542f\u52a8\u5230BIOS\uff0c\u7981\u7528CSM\u5e76\u5173\u673a\uff08\u4e0d\u8981\u91cd\u65b0\u542f\u52a8\uff09\u60a8\u7684\u8ba1\u7b97\u673a\u3002\u7136\u540e\uff0c\u5728\u518d\u6b21\u542f\u52a8\u5230BIOS\u5e76\u542f\u7528CSM\u4e4b\u524d\uff0c\u8fde\u63a5HDMI\u5e76\u518d\u6b21\u6253\u5f00\u8ba1\u7b97\u673a\u3002 GRUB2\u4e2d\u6ca1\u6709\u89c6\u9891\uff0c\u4f46\u4e4b\u524d\u548c\u4e4b\u540e\u90fd\u6709 \u6709\u65f6\u8fd9\u53ef\u80fd\u662f\u7531\u4e8eBIOS/UEFI\u7684\u7279\u5b9a\u95ee\u9898\u4ee5\u53caGRUB2\u4e0e\u89c6\u9891\u7684\u5de5\u4f5c\u65b9\u5f0f\u6240\u5bfc\u81f4\u7684\u3002 \u60a8\u53ef\u4ee5\u901a\u8fc7\u5728BIOS\u4e2d\u542f\u7528 \u517c\u5bb9\u6027\u652f\u6301\u6a21\u5757\uff08CSM\uff09 \u6765\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u901a\u5e38\u4f4d\u4e8e \u5f15\u5bfc \u9009\u9879\u4e0b\u3002\u89c6\u9891\u6a21\u5f0f\u4e5f\u4f4d\u4e8e\u540c\u4e00\u90e8\u5206\u3002\u5c06 \u89c6\u9891 \u6a21\u5f0f\u4ece UEFI \u5207\u6362\u4e3a Legacy \u3002 Linux + Awesome WM\u6ca1\u6709\u8ba1\u7b97\u673a\u56fe\u50cf \u6709\u65f6\uff0c\u5728Linux\u4e0a\u4f7f\u7528Awesome WM\u53ef\u80fd\u65e0\u6cd5\u8bc6\u522b\u7535\u7f06\u7684\u89c6\u9891\u8f93\u51fa\u66f4\u6539\u3002\u4e5f\u5c31\u662f\u8bf4\uff0c\u5982\u679c\u7535\u7f06\u5148\u63d2\u5165\u663e\u793a\u5668\uff0c\u7136\u540e\u518d\u8fde\u63a5\u5230BLIKVM\uff0c\u53ef\u80fd\u4f1a\u5bfc\u81f4\u60a8\u770b\u4e0d\u5230\u56fe\u50cf\u3002\u8fd9\u4f3c\u4e4e\u662fAwesome WM\u7684\u95ee\u9898\uff0c\u56e0\u4e3a\u4f8b\u5982\u5728KDE\u4e2d\uff0c\u8fd9\u79cd\u60c5\u51b5\u65e0\u6cd5\u590d\u73b0\u3002\u5982\u679c\u60a8\u5728\u8fde\u63a5BLIKVM\u540e\u542f\u52a8\u5de5\u4f5c\u7ad9\uff0c\u4e00\u5207\u90fd\u5c06\u6b63\u5e38\u5de5\u4f5c\u3002","title":"\u89c6\u9891\u95ee\u9898"},{"location":"faq/#usbu","text":"USB OTG\u7aef\u53e3\u7684\u901f\u5ea6\u662f\u591a\u5c11\uff1f \u6839\u636e\u5b98\u65b9\u7684RPI\u6587\u6863\uff0c\u8fd9\u662fSoC\u7684\u9650\u5236\u3002OTG\u7aef\u53e3\u53ea\u652f\u6301USB 2.0\uff0c\u56e0\u6b64\u901f\u5ea6\u9650\u5236\u4e3a455 Mbit/s\u3002 \u4e3a\u4ec0\u4e48\u65e0\u6cd5\u6355\u83b7\u67d0\u4e9b\u5b9e\u4f53\u952e\u76d8\u7684\u952e\u76d8\u5feb\u6377\u952e\uff0c\u4f46\u53ef\u4ee5\u6355\u83b7\u865a\u62df\u952e\u76d8\u7684\u952e\u76d8\u5feb\u6377\u952e\uff1f\u4f8b\u5982\uff0c\u65e0\u6cd5\u6355\u83b7Mac\u7535\u8111\u7684F11\u6309\u952e \u8fd9\u662f\u56e0\u4e3a\u4e00\u4e9b\u5feb\u6377\u952e\u5df2\u7ecf\u88ab\u64cd\u4f5c\u7cfb\u7edf\u4f7f\u7528\u4e86\uff0c\u4f8b\u5982\u5728 macOS \u4e2d\uff0cF11 \u88ab\u9ed8\u8ba4\u5206\u914d\u7ed9\u4e86\u201c\u663e\u793a\u684c\u9762\u201d\u7684\u529f\u80fd\u3002\u5f53\u60a8\u5728Web\u754c\u9762\u6309\u4e0bF11\u65f6\uff0c\u952e\u76d8\u4e8b\u4ef6\u9996\u5148\u88ab\u64cd\u4f5c\u7cfb\u7edf\u6355\u83b7\uff0c\u5982\u679c\u64cd\u4f5c\u7cfb\u7edf\u6ce8\u518c\u4e86\u56de\u8c03\u51fd\u6570\uff0c\u952e\u76d8\u4e8b\u4ef6\u5c06\u4e0d\u4f1a\u4f20\u9012\u7ed9\u5e94\u7528\u7a0b\u5e8f\u3002\u8981\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u60a8\u53ef\u4ee5\u5173\u95ed\u64cd\u4f5c\u7cfb\u7edf\u8bbe\u7f6e\u4e2d\u7684\u5feb\u6377\u952e\uff0c\u6216\u8005\u4f7f\u7528\u865a\u62df\u952e\u76d8\u3002","title":"USB\u95ee\u9898\uff08\u952e\u76d8\u3001\u9f20\u6807\u3001U\u76d8\u7b49\uff09"},{"location":"faq/#wi-fiatx","text":"\u5982\u679c\u4f7f\u7528PiKVM\u8f6f\u4ef6\uff0cWeb\u754c\u9762\u663e\u793a FAN \u9519\u8bef\uff01 \u7531\u4e8eBLIKVM\u786c\u4ef6\u4f7f\u7528\u7684\u98ce\u6247\u578b\u53f7\u4e0ePIKVM\u786c\u4ef6\u4e0d\u540c\uff0c\u56e0\u6b64\u5728pikvm\u7684\u6700\u65b0\u7cfb\u7edf\u4e2d\uff0c\u901a\u8fc7Web\u754c\u9762\u67e5\u770b\u98ce\u6247\u72b6\u6001\u53ef\u80fd\u4f1a\u5931\u8d25\u3002\u4f46\u8fd9\u4e0d\u4f1a\u5f71\u54cdBLIKVM\u98ce\u6247\u7684\u6b63\u5e38\u8fd0\u884c\u3002\u56e0\u6b64\uff0c\u5728\u4f7f\u7528PIKVM\u955c\u50cf\u65f6\uff0c\u53ea\u8981\u786e\u4fdd \u5b89\u88c5\u811a\u672c \u663e\u793aOK\uff0c\u5c31\u8868\u793akvmd\u98ce\u6247\u7a0b\u5e8f\u7684\u66f4\u65b0\u6210\u529f\u3002\u9ed8\u8ba4\u7a0b\u5e8f\u8bbe\u7f6e\u7684\u6e29\u5ea6\u9608\u503c\u4e3a\u6444\u6c0f60\u5ea6\u3002\u5f53\u68c0\u6d4b\u5230CPU\u6e29\u5ea6\u8d85\u8fc760\u6444\u6c0f\u5ea6\u65f6\uff0c\u98ce\u6247\u5c06\u4ee585%\u7684\u901f\u5ea6\u5f00\u59cb\u65cb\u8f6c\u3002\u5982\u679c\u8981\u4fee\u6539\u6e29\u5ea6\u9608\u503c\u548c\u901f\u5ea6\uff0c\u53ef\u4ee5\u4fee\u6539kvmd-fan.py\u811a\u672c\uff0c\u7136\u540e\u91cd\u65b0\u6267\u884cinstall.sh\u3002 \u6211\u6839\u672c\u65e0\u6cd5\u8fde\u63a5\u5230Wi-Fi\uff01 \u5982\u679c\u60a8\u7684\u8bbe\u5907\u65e0\u6cd5\u8fde\u63a5\u5230\u60a8\u8bbe\u7f6e\u7684Wi-Fi\u7f51\u7edc\uff0c\u8bf7\u68c0\u67e5\u60a8\u7684Wi-Fi\u63a5\u5165\u70b9\u4f7f\u7528\u76842.4GHz Wi-Fi\u4fe1\u9053\u3002\u5982\u679c\u4f7f\u7528\u4e8612\u523014\u4fe1\u9053\uff08\u67d0\u4e9b\u56fd\u5bb6\u7981\u6b62\u4f7f\u7528\u8fd9\u4e9b\u4fe1\u9053\uff09\uff0c\u8bf7\u5c1d\u8bd5\u4f7f\u75281\u523011\u4e4b\u95f4\u7684\u4fe1\u9053\u3002 BLIKVM\u663e\u793a\u4f4e\u7535\u538b\u8b66\u544a \u60a8\u662f\u5426\u4f7f\u7528\u4e86\u201c\u6b63\u786e\u201d\u7684\u7535\u6e90\u9002\u914d\u5668\uff1f\u800c\u4e0d\u662f\u81ea\u5df1\u62fc\u51d1\u7684\u9002\u914d\u5668\uff1f \u4e00\u4e9bUSB\u7535\u6e90\u9002\u914d\u5668\u5ba3\u4f20\u4e3a5V 2.1A\u6216\u66f4\u9ad8\uff0c\u4f46\u65e0\u6cd5\u63d0\u4f9b\u7a33\u5b9a\u76845V\u7535\u538b\u3002\u6700\u597d\u4f7f\u7528\u6811\u8393\u6d3e\u57fa\u91d1\u4f1a\u63a8\u8350\u7684\u7535\u6e90\u9002\u914d\u5668\u3002\u5176\u8f93\u51fa\u5e94\u4e3a5.1V\u548c3A\u76f4\u6d41\u7535\u538b\u3002 \u5f53\u6211\u4f7f\u7528PoE\u65f6\uff0c\u662f\u5426\u4ecd\u7136\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u6765\u9632\u6b62\u673a\u5668USB\u7684\u53cd\u5411\u4f9b\u7535\uff1f \u53ea\u6709HAT\u7248\u672c\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u6765\u9632\u6b62\u53cd\u5411\u4f9b\u7535\u3002\u901a\u5e38\uff0c\u5927\u591a\u6570\u4e3b\u673a\u8ba1\u7b97\u673a\u90fd\u6709\u53cd\u5411\u4f9b\u7535\u4fdd\u62a4\uff0c\u56e0\u6b64\u5728\u8fd9\u79cd\u60c5\u51b5\u4e0b\u4e0d\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u3002 BLIKVM-CM4-V2.2\u548cBLIKVM-PCIe\u7248\u672c\u4e0d\u9700\u8981\u3002 \u5728\u4e00\u4e9b\u50cfBLIKVM-PCIe\u6216BLIKVM-CM4-V2.2\u8fd9\u6837\u7684\u677f\u5b50\u4e0a\u6709\u5f15\u5bfc\u5f15\u811a\uff0c\u5982\u4f55\u8fde\u63a5\uff1f \u5982\u679c\u5c06\u5b83\u4eec\u8fde\u63a5\u77ed\u8def\uff0cCM4\u5c06\u65e0\u6cd5\u6b63\u5e38\u542f\u52a8\uff0c\u800c\u5c06\u8fdb\u5165\u70e7\u5f55\u6620\u50cf\u6a21\u5f0f\u3002\u5982\u679c\u60a8\u7684\u786c\u4ef6\u7248\u672c\u7684\u5f15\u5bfc\u5f15\u811a\u53ea\u6709\u4e24\u4e2a\u5f15\u811a\uff0c\u4f7f\u7528\u8df3\u7ebf\u5e3d\u5c06\u8fd9\u4e24\u4e2a\u5f15\u811a\u8fde\u63a5\u8d77\u6765\uff0c\u5f62\u6210\u77ed\u8def\u3002\u5982\u679c\u60a8\u4e0d\u4f7f\u7528\u8df3\u7ebf\u5e3d\u6216\u53ea\u5c06\u5176\u63d2\u5165\u4e00\u4e2a\u5f15\u811a\uff0cCM4\u5c06\u6b63\u5e38\u542f\u52a8\u3002\u5982\u679c\u60a8\u4f7f\u7528\u7684\u662f\u4e09\u4e2a\u5f15\u5bfc\u5f15\u811a\u7684\u786c\u4ef6\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u8df3\u7ebf\u5e3d\u5c06GND\u548c\u53e6\u4e00\u4e2a\u975eGND\u5f15\u811a\u8fde\u63a5\u8d77\u6765\u4ee5\u793a\u77ed\u8def\uff0c\u5e76\u5c06\u8df3\u7ebf\u5e3d\u63d2\u5728\u4e24\u4e2aGND\u5f15\u811a\u4e0a\u6216\u4e0d\u4f7f\u7528\u8df3\u7ebf\u5e3d\uff0cCM4\u5c06\u6b63\u5e38\u542f\u52a8\u3002","title":"\u786c\u4ef6\u95ee\u9898\uff08Wi-Fi\u3001ATX\u7b49\uff09"},{"location":"faq/#web","text":"BliKVM OS\u5360\u7528\u7684\u7aef\u53e3\u6709\u54ea\u4e9b\uff0c\u5728\u7528\u516c\u7f51\u670d\u52a1\u5668\u8f6c\u53d1\u65f6\uff0c\u5e94\u8be5\u600e\u4e48\u505a\uff1f Web\u754c\u9762\u4e3ahttp\u534f\u8bae\uff0c\u5360\u7528\u7684\u662f80\u7aef\u53e3\uff1b \u5982\u679c\u60a8\u7684\u786c\u4ef6\u662fV1 V2 V3\uff0c\u4f7f\u7528\u7684\u662f\u662fweb-rtc\u4f20\u8f93\uff0c\u7aef\u53e3\u662f8188\uff1b \u5982\u679c\u60a8\u7684\u786c\u4ef6\u662fV4\uff0c\u4f7f\u7528\u7684\u662fmjepg\u4f20\u8f93\uff0c\u7aef\u53e3\u662f8008\uff1b \u6ce8\u610f\u7aef\u53e3\u4e0d\u652f\u6301\u88ab\u4fee\u6539\uff0c\u53ea\u80fd\u914d\u7f6e\u8f6c\u53d1\uff1b","title":"Web\u95ee\u9898"},{"location":"faq/#_4","text":"\u6211\u662f\u5426\u53ef\u4ee5\u540c\u65f6\u4f7f\u7528\u5e26eMMC\u7248\u672c\u7684CM4\u548cSD\u5361? \u4e0d\u53ef\u4ee5\uff0c\u56e0\u4e3a\u5728CM4\u786c\u4ef6\u8bbe\u8ba1\u4e0a\uff0c\u51e0\u4e2aSD\u5361\u7684\u5f15\u811a\u53ea\u5728lite\u7248\u672c\u4e2d\u662f\u53ef\u7528\u7684\uff0c\u4f60\u53ef\u4ee5\u5728\u6811\u8393\u6d3e\u5b98\u7f51\u627e\u5230\u8bf4\u660e\u3002","title":"\u6811\u8393\u6d3e\u76f8\u5173\u95ee\u9898"},{"location":"first_steps/","text":"\u521d\u6b65\u64cd\u4f5c \u9996\u6b21\u4e0a\u7535 \u53ef\u9009\uff1a\u8bbe\u7f6eWi-Fi\u8fde\u63a5 \u8bf7\u9605\u8bfb\u4ee5\u4e0b\u6ce8\u610f\u4e8b\u9879 \u6709\u7ebf\u4ee5\u592a\u7f51\u8fde\u63a5\u662f\u6700\u53ef\u9760\u7684\u65b9\u5f0f\uff0c\u56e0\u6b64\u6700\u597d\u4f7f\u7528 \u6709\u7ebf\u7535\u7f06 \u3002\u4f46\u6211\u4eec\u4e0d\u80fd\u963b\u6b62\u60a8\u4f7f\u7528\u65e0\u7ebf\u8fde\u63a5... :) \u786e\u8ba4\u60a8\u4f7f\u7528\u7684\u7248\u672c\u542b\u6709Wi-Fi\u529f\u80fd\uff0c\u5e76\u4e14Wi-Fi\u5929\u7ebf\u5df2\u5b89\u88c5. \u8bf7\u53c2\u8003 Wi-Fi\u8fde\u63a5\u6307\u5357 \uff0c\u5bf9\u60a8\u7684\u8bbe\u5907\u8fdb\u884cWi-Fi\u8bbe\u7f6e\uff1b \u7ed9\u8bbe\u5907\u4f9b\u7535\u3002 \u5728\u8bbe\u5907\u5b8c\u5168\u542f\u52a8\u524d\uff0c\u8bf7\u52ff\u5173\u95ed\u7535\u6e90 \u8bbf\u95eeBliKVM \u9ed8\u8ba4\u60c5\u51b5\u4e0b\uff0cBliKVM\u901a\u8fc7DHCP\u63a5\u6536\u52a8\u6001IP\u5730\u5740\u3002\u4f1a\u5728BliKVM\u663e\u793a\u5668\u4e0a\u663e\u793aIP\u5730\u5740\u3002\u5982\u679c\u60a8\u662fDIY\u786c\u4ef6\u6ca1\u6709\u663e\u793a\u5668\uff0c\u8bf7\u4f7f\u7528\u4ee5\u4e0b\u63d0\u793a\uff1a \u5728\u7f51\u7edc\u4e2d\u67e5\u627eBliKVM \u60a8\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u65b9\u6cd5\u786e\u5b9aBliKVM\u7684IP\u5730\u5740\uff1a \u5e38\u7528\u65b9\u6cd5\uff1a \u6253\u5f00\u8def\u7531\u5668\u7684Web\u754c\u9762\uff0c\u5e76\u67e5\u627e\u5df2\u5206\u914d\u7684IP\u5730\u5740\u5217\u8868\u3002\u5177\u4f53\u65b9\u6cd5\u53d6\u51b3\u4e8e\u8def\u7531\u5668\u578b\u53f7\u3002 \u4ec5\u9650Linux\uff1a \u4f7f\u7528\u547d\u4ee4 arp-scan --localnet \u3002 Linux\u3001MacOS\u3001Windows\uff1a \u4e0b\u8f7d\u5e76\u8fd0\u884c Angry IP Scanner \u3002 Windows PowerShell\uff1a \u4f7f\u7528\u547d\u4ee4 arp -a \u3002 \u5728\u4e0b\u9762\u7684\u793a\u4f8b\u4e2d\uff0c\u8ba9\u6211\u4eec\u5047\u8bbe\u60a8\u7684BliKVM\u5df2\u83b7\u5f97\u5730\u5740 192.168.0.100 \uff0c\u60a8\u5df2\u7ecf\u6210\u529f\u4f7f\u7528\u4e0a\u8ff0\u6307\u793a\u627e\u5230\u4e86\u8be5\u5730\u5740\u3002 \u8bbf\u95eeBliKVM Web\u754c\u9762 \u5728 \u5927\u591a\u6570 \u7f51\u7edc\u4e2d\uff0c\u60a8\u53ef\u4ee5\u5728\u4efb\u4f55\u6d4f\u89c8\u5668\u4e2d\u4f7f\u7528\u4ee5\u4e0bURL\u8bbf\u95eeBliKVM\uff1a http://192.168.0.100/ \u3002Google Chrome\uff08Chromium\uff09\u3001Firefox\u548cSafari\u4e0e\u542f\u75280\u4e2a\u6269\u5c55\u7684\u60c5\u51b5\u4e0b\u6548\u679c\u6700\u4f73\uff0c\u5982\u679c\u5176\u4e2d\u4e00\u4e2a\u53ef\u4ee5\u6b63\u5e38\u5de5\u4f5c\u800c\u53e6\u4e00\u4e2a\u65e0\u6cd5\u6b63\u5e38\u5de5\u4f5c\uff0c\u5219\u53ef\u80fd\u662f\u6d4f\u89c8\u5668/\u6269\u5c55\u7684\u95ee\u9898\u3002\u5efa\u8bae\u60a8\u4f7f\u7528\u79c1\u5bc6\u6d4f\u89c8\u7a97\u53e3\u6216\u65e0\u75d5\u6a21\u5f0f\u3002\u4e0d\u652f\u6301Internet Explorer\u548c\u65e9\u671f\u7248\u672c\u7684Microsoft Edge\uff08\u975eChromium\u7248\u672c\uff09\u3002 \u9ed8\u8ba4\u7528\u6237\u540d\u4e3a admin \uff0c\u5bc6\u7801\u4e5f\u4e3a admin \u3002 \u767b\u5f55\u540e\uff0c\u60a8\u5c06\u83b7\u5f97\u8bbf\u95ee\u4e3b\u8981\u529f\u80fd\u83dc\u5355\u7684\u6743\u9650\u3002\u4f7f\u7528Web\u7684\u4fee\u6539\u8d26\u53f7\u5bc6\u7801\u529f\u80fd\uff0c\u60a8\u53ef\u4ee5\u66f4\u6539\u7cfb\u7edf\u8bbe\u7f6e\u548c\u5bc6\u7801\u3002 \u6ce8\u610f\u5f53\u524d\u8bbf\u95eeBliKVM web\u662fhttp\uff0c\u800c\u975ehttps \u901a\u8fc7SSH\u8bbf\u95eeBliKVM SSH\u662fLinux\u4e16\u754c\u4e2d\u6700\u5e38\u7528\u7684\u8fdc\u7a0b\u8bbf\u95ee\u65b9\u6cd5\u3002\u60a8\u53ef\u4ee5\u901a\u8fc7SSH\u8bbf\u95eeBliKVM\u3002\u6b64\u65b9\u6cd5\u7528\u4e8e\u7ba1\u7406\u8bbe\u5907\uff1a Linux\u3001MacOS\uff1a \u6253\u5f00\u4efb\u4f55\u7ec8\u7aef\u5e94\u7528\u7a0b\u5e8f\uff0c\u7136\u540e\u8fd0\u884c\uff1a ssh blikvm@192.168.0.100 \u3002 Windows\uff1a \u4f7f\u7528 PuTTY \u8fdb\u884c\u64cd\u4f5c\u3002 \u9ed8\u8ba4\u7684 blikvm \u7528\u6237\u5bc6\u7801\u4e3a blikvm \u3002 \u60a8\u53ef\u4ee5\u4f7f\u7528 sudo -i \u83b7\u5f97root\u6743\u9650\u3002 \u53ef\u9009\uff1a\u66f4\u65b0BliKVM\u8f6f\u4ef6 \u8fd9\u90e8\u5206\u4e0d\u662f\u5fc5\u9700\u7684\uff0c\u4ec5\u5728\u60a8\u5728BliKVM\u65c1\u8fb9\u4ee5\u4fbf\u6062\u590d\u5b83\u65f6\u624d\u5e94\u6267\u884c\uff0c\u53ef\u4ee5\u53c2\u8003 \u66f4\u65b0\u8f6f\u4ef6\u6307\u5357 \u5b8c\u6210\uff1b BliKVM OS\u7ec8\u7aef\u4f7f\u7528\u6ce8\u610f\u4e8b\u9879 \u4e00\u4e9b\u914d\u7f6e\u66f4\u6539\u90fd\u5fc5\u987b\u5728 root \u7528\u6237\uff08\u5373\u7ba1\u7406\u5458\uff09\u4e0b\u8fdb\u884c\u3002 \u83b7\u53d6root\u6743\u9650 \u5982\u679c\u60a8\u901a\u8fc7SSH\u767b\u5f55\uff0c\u9700\u4f7f\u7528 sudo -i \u83b7\u5f97root\u6743\u9650\uff1b v1\u3001v2\u3001v3\u7248\u672c\u7684BliKVM\u5b58\u50a8\u5361\u4ee5\u53ea\u8bfb\u6a21\u5f0f\u6302\u8f7d\u3002\u8fd9\u6837\u53ef\u4ee5\u5728\u7a81\u7136\u505c\u7535\u65f6\u4fdd\u62a4\u6587\u4ef6\u7cfb\u7edf\u514d\u53d7\u635f\u574f\u3002\u8981\u7f16\u8f91\u4efb\u4f55\u6587\u4ef6\u5e76\u8fdb\u884c\u66f4\u6539\uff0c\u9700\u8981\u5c06\u6587\u4ef6\u7cfb\u7edf\u91cd\u65b0\u6302\u8f7d\u4e3a\u8bfb\u5199\u6a21\u5f0f\u3002\u60a8\u53ef\u4ee5\u901a\u8fc7\u7ec8\u7aef\u662f\u6709\u6709ro\u6216rw\u5b57\u6837\u6765\u5224\u65ad\u5f53\u524d\u7cfb\u7edf\u6a21\u5f0f\u3002 \u542f\u7528\u5199\u5165\u6a21\u5f0f \u8981\u542f\u7528\u5199\u5165\u6a21\u5f0f\uff0c\u8bf7\u8fd0\u884c rw \u547d\u4ee4\u3002 \u8981\u7981\u7528\u5199\u5165\u6a21\u5f0f\uff0c\u8bf7\u8fd0\u884c ro \u547d\u4ee4\u3002 \u5982\u679c\u6536\u5230 \"Device is busy\"\uff08\u8bbe\u5907\u5fd9\uff09\u7684\u6d88\u606f\uff0c\u8bf7\u6267\u884c reboot \u547d\u4ee4\u3002 \u4e0b\u4e00\u6b65\u662f\u4ec0\u4e48\uff1f \u4f7f\u7528 \u7aef\u53e3\u8f6c\u53d1 \u6216 Tailscale VPN \u8bbe\u7f6e\u4e92\u8054\u7f51\u8bbf\u95ee\u3002 \u4f7f\u7528\u5de6\u4fa7\u7684\u76ee\u5f55\u5bfc\u822a\u63a2\u7d22BliKVM\u7684\u529f\u80fd\u3002 \u52a0\u5165\u6211\u4eec\u7684 Discord \u4e0e\u793e\u533a\u548c\u5f00\u53d1\u4eba\u5458\u4ea4\u6d41\u3002 \u67e5\u770b GitHub - BliKVM \u662f\u4e00\u4e2a\u5f00\u6e90\u7684\u9879\u76ee\uff01 \u5e38\u89c1\u95ee\u9898\u548c\u6545\u969c\u6392\u9664 \u5982\u679c\u60a8\u6709\u4efb\u4f55\u95ee\u9898\u6216\u9047\u5230\u95ee\u9898\uff0c\u8bf7\u67e5\u770b \u5e38\u89c1\u95ee\u9898 \u3002 \u771f\u7684\uff0c\u5b83\u975e\u5e38\u6709\u7528\uff01\u6211\u4eec\u53ef\u80fd\u5df2\u7ecf\u4e3a\u60a8\u627e\u5230\u89e3\u51b3\u65b9\u6848\u4e86 :) \u5982\u679c\u9700\u8981\u4efb\u4f55\u5176\u4ed6\u5e2e\u52a9\u548c\u652f\u6301\uff0c\u60a8\u53ef\u4ee5\u901a\u8fc7 Discord\u804a\u5929 \u4e0e\u6211\u4eec\u8054\u7cfb\u3002","title":"\u7b2c\u4e00\u6b65"},{"location":"first_steps/#_1","text":"","title":"\u521d\u6b65\u64cd\u4f5c"},{"location":"first_steps/#_2","text":"\u53ef\u9009\uff1a\u8bbe\u7f6eWi-Fi\u8fde\u63a5 \u8bf7\u9605\u8bfb\u4ee5\u4e0b\u6ce8\u610f\u4e8b\u9879 \u6709\u7ebf\u4ee5\u592a\u7f51\u8fde\u63a5\u662f\u6700\u53ef\u9760\u7684\u65b9\u5f0f\uff0c\u56e0\u6b64\u6700\u597d\u4f7f\u7528 \u6709\u7ebf\u7535\u7f06 \u3002\u4f46\u6211\u4eec\u4e0d\u80fd\u963b\u6b62\u60a8\u4f7f\u7528\u65e0\u7ebf\u8fde\u63a5... :) \u786e\u8ba4\u60a8\u4f7f\u7528\u7684\u7248\u672c\u542b\u6709Wi-Fi\u529f\u80fd\uff0c\u5e76\u4e14Wi-Fi\u5929\u7ebf\u5df2\u5b89\u88c5. \u8bf7\u53c2\u8003 Wi-Fi\u8fde\u63a5\u6307\u5357 \uff0c\u5bf9\u60a8\u7684\u8bbe\u5907\u8fdb\u884cWi-Fi\u8bbe\u7f6e\uff1b \u7ed9\u8bbe\u5907\u4f9b\u7535\u3002 \u5728\u8bbe\u5907\u5b8c\u5168\u542f\u52a8\u524d\uff0c\u8bf7\u52ff\u5173\u95ed\u7535\u6e90","title":"\u9996\u6b21\u4e0a\u7535"},{"location":"first_steps/#blikvm","text":"\u9ed8\u8ba4\u60c5\u51b5\u4e0b\uff0cBliKVM\u901a\u8fc7DHCP\u63a5\u6536\u52a8\u6001IP\u5730\u5740\u3002\u4f1a\u5728BliKVM\u663e\u793a\u5668\u4e0a\u663e\u793aIP\u5730\u5740\u3002\u5982\u679c\u60a8\u662fDIY\u786c\u4ef6\u6ca1\u6709\u663e\u793a\u5668\uff0c\u8bf7\u4f7f\u7528\u4ee5\u4e0b\u63d0\u793a\uff1a \u5728\u7f51\u7edc\u4e2d\u67e5\u627eBliKVM \u60a8\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u65b9\u6cd5\u786e\u5b9aBliKVM\u7684IP\u5730\u5740\uff1a \u5e38\u7528\u65b9\u6cd5\uff1a \u6253\u5f00\u8def\u7531\u5668\u7684Web\u754c\u9762\uff0c\u5e76\u67e5\u627e\u5df2\u5206\u914d\u7684IP\u5730\u5740\u5217\u8868\u3002\u5177\u4f53\u65b9\u6cd5\u53d6\u51b3\u4e8e\u8def\u7531\u5668\u578b\u53f7\u3002 \u4ec5\u9650Linux\uff1a \u4f7f\u7528\u547d\u4ee4 arp-scan --localnet \u3002 Linux\u3001MacOS\u3001Windows\uff1a \u4e0b\u8f7d\u5e76\u8fd0\u884c Angry IP Scanner \u3002 Windows PowerShell\uff1a \u4f7f\u7528\u547d\u4ee4 arp -a \u3002 \u5728\u4e0b\u9762\u7684\u793a\u4f8b\u4e2d\uff0c\u8ba9\u6211\u4eec\u5047\u8bbe\u60a8\u7684BliKVM\u5df2\u83b7\u5f97\u5730\u5740 192.168.0.100 \uff0c\u60a8\u5df2\u7ecf\u6210\u529f\u4f7f\u7528\u4e0a\u8ff0\u6307\u793a\u627e\u5230\u4e86\u8be5\u5730\u5740\u3002 \u8bbf\u95eeBliKVM Web\u754c\u9762 \u5728 \u5927\u591a\u6570 \u7f51\u7edc\u4e2d\uff0c\u60a8\u53ef\u4ee5\u5728\u4efb\u4f55\u6d4f\u89c8\u5668\u4e2d\u4f7f\u7528\u4ee5\u4e0bURL\u8bbf\u95eeBliKVM\uff1a http://192.168.0.100/ \u3002Google Chrome\uff08Chromium\uff09\u3001Firefox\u548cSafari\u4e0e\u542f\u75280\u4e2a\u6269\u5c55\u7684\u60c5\u51b5\u4e0b\u6548\u679c\u6700\u4f73\uff0c\u5982\u679c\u5176\u4e2d\u4e00\u4e2a\u53ef\u4ee5\u6b63\u5e38\u5de5\u4f5c\u800c\u53e6\u4e00\u4e2a\u65e0\u6cd5\u6b63\u5e38\u5de5\u4f5c\uff0c\u5219\u53ef\u80fd\u662f\u6d4f\u89c8\u5668/\u6269\u5c55\u7684\u95ee\u9898\u3002\u5efa\u8bae\u60a8\u4f7f\u7528\u79c1\u5bc6\u6d4f\u89c8\u7a97\u53e3\u6216\u65e0\u75d5\u6a21\u5f0f\u3002\u4e0d\u652f\u6301Internet Explorer\u548c\u65e9\u671f\u7248\u672c\u7684Microsoft Edge\uff08\u975eChromium\u7248\u672c\uff09\u3002 \u9ed8\u8ba4\u7528\u6237\u540d\u4e3a admin \uff0c\u5bc6\u7801\u4e5f\u4e3a admin \u3002 \u767b\u5f55\u540e\uff0c\u60a8\u5c06\u83b7\u5f97\u8bbf\u95ee\u4e3b\u8981\u529f\u80fd\u83dc\u5355\u7684\u6743\u9650\u3002\u4f7f\u7528Web\u7684\u4fee\u6539\u8d26\u53f7\u5bc6\u7801\u529f\u80fd\uff0c\u60a8\u53ef\u4ee5\u66f4\u6539\u7cfb\u7edf\u8bbe\u7f6e\u548c\u5bc6\u7801\u3002 \u6ce8\u610f\u5f53\u524d\u8bbf\u95eeBliKVM web\u662fhttp\uff0c\u800c\u975ehttps \u901a\u8fc7SSH\u8bbf\u95eeBliKVM SSH\u662fLinux\u4e16\u754c\u4e2d\u6700\u5e38\u7528\u7684\u8fdc\u7a0b\u8bbf\u95ee\u65b9\u6cd5\u3002\u60a8\u53ef\u4ee5\u901a\u8fc7SSH\u8bbf\u95eeBliKVM\u3002\u6b64\u65b9\u6cd5\u7528\u4e8e\u7ba1\u7406\u8bbe\u5907\uff1a Linux\u3001MacOS\uff1a \u6253\u5f00\u4efb\u4f55\u7ec8\u7aef\u5e94\u7528\u7a0b\u5e8f\uff0c\u7136\u540e\u8fd0\u884c\uff1a ssh blikvm@192.168.0.100 \u3002 Windows\uff1a \u4f7f\u7528 PuTTY \u8fdb\u884c\u64cd\u4f5c\u3002 \u9ed8\u8ba4\u7684 blikvm \u7528\u6237\u5bc6\u7801\u4e3a blikvm \u3002 \u60a8\u53ef\u4ee5\u4f7f\u7528 sudo -i \u83b7\u5f97root\u6743\u9650\u3002 \u53ef\u9009\uff1a\u66f4\u65b0BliKVM\u8f6f\u4ef6 \u8fd9\u90e8\u5206\u4e0d\u662f\u5fc5\u9700\u7684\uff0c\u4ec5\u5728\u60a8\u5728BliKVM\u65c1\u8fb9\u4ee5\u4fbf\u6062\u590d\u5b83\u65f6\u624d\u5e94\u6267\u884c\uff0c\u53ef\u4ee5\u53c2\u8003 \u66f4\u65b0\u8f6f\u4ef6\u6307\u5357 \u5b8c\u6210\uff1b","title":"\u8bbf\u95eeBliKVM"},{"location":"first_steps/#blikvm-os","text":"\u4e00\u4e9b\u914d\u7f6e\u66f4\u6539\u90fd\u5fc5\u987b\u5728 root \u7528\u6237\uff08\u5373\u7ba1\u7406\u5458\uff09\u4e0b\u8fdb\u884c\u3002 \u83b7\u53d6root\u6743\u9650 \u5982\u679c\u60a8\u901a\u8fc7SSH\u767b\u5f55\uff0c\u9700\u4f7f\u7528 sudo -i \u83b7\u5f97root\u6743\u9650\uff1b v1\u3001v2\u3001v3\u7248\u672c\u7684BliKVM\u5b58\u50a8\u5361\u4ee5\u53ea\u8bfb\u6a21\u5f0f\u6302\u8f7d\u3002\u8fd9\u6837\u53ef\u4ee5\u5728\u7a81\u7136\u505c\u7535\u65f6\u4fdd\u62a4\u6587\u4ef6\u7cfb\u7edf\u514d\u53d7\u635f\u574f\u3002\u8981\u7f16\u8f91\u4efb\u4f55\u6587\u4ef6\u5e76\u8fdb\u884c\u66f4\u6539\uff0c\u9700\u8981\u5c06\u6587\u4ef6\u7cfb\u7edf\u91cd\u65b0\u6302\u8f7d\u4e3a\u8bfb\u5199\u6a21\u5f0f\u3002\u60a8\u53ef\u4ee5\u901a\u8fc7\u7ec8\u7aef\u662f\u6709\u6709ro\u6216rw\u5b57\u6837\u6765\u5224\u65ad\u5f53\u524d\u7cfb\u7edf\u6a21\u5f0f\u3002 \u542f\u7528\u5199\u5165\u6a21\u5f0f \u8981\u542f\u7528\u5199\u5165\u6a21\u5f0f\uff0c\u8bf7\u8fd0\u884c rw \u547d\u4ee4\u3002 \u8981\u7981\u7528\u5199\u5165\u6a21\u5f0f\uff0c\u8bf7\u8fd0\u884c ro \u547d\u4ee4\u3002 \u5982\u679c\u6536\u5230 \"Device is busy\"\uff08\u8bbe\u5907\u5fd9\uff09\u7684\u6d88\u606f\uff0c\u8bf7\u6267\u884c reboot \u547d\u4ee4\u3002","title":"BliKVM OS\u7ec8\u7aef\u4f7f\u7528\u6ce8\u610f\u4e8b\u9879"},{"location":"first_steps/#_3","text":"\u4f7f\u7528 \u7aef\u53e3\u8f6c\u53d1 \u6216 Tailscale VPN \u8bbe\u7f6e\u4e92\u8054\u7f51\u8bbf\u95ee\u3002 \u4f7f\u7528\u5de6\u4fa7\u7684\u76ee\u5f55\u5bfc\u822a\u63a2\u7d22BliKVM\u7684\u529f\u80fd\u3002 \u52a0\u5165\u6211\u4eec\u7684 Discord \u4e0e\u793e\u533a\u548c\u5f00\u53d1\u4eba\u5458\u4ea4\u6d41\u3002 \u67e5\u770b GitHub - BliKVM \u662f\u4e00\u4e2a\u5f00\u6e90\u7684\u9879\u76ee\uff01","title":"\u4e0b\u4e00\u6b65\u662f\u4ec0\u4e48\uff1f"},{"location":"first_steps/#_4","text":"\u5982\u679c\u60a8\u6709\u4efb\u4f55\u95ee\u9898\u6216\u9047\u5230\u95ee\u9898\uff0c\u8bf7\u67e5\u770b \u5e38\u89c1\u95ee\u9898 \u3002 \u771f\u7684\uff0c\u5b83\u975e\u5e38\u6709\u7528\uff01\u6211\u4eec\u53ef\u80fd\u5df2\u7ecf\u4e3a\u60a8\u627e\u5230\u89e3\u51b3\u65b9\u6848\u4e86 :) \u5982\u679c\u9700\u8981\u4efb\u4f55\u5176\u4ed6\u5e2e\u52a9\u548c\u652f\u6301\uff0c\u60a8\u53ef\u4ee5\u901a\u8fc7 Discord\u804a\u5929 \u4e0e\u6211\u4eec\u8054\u7cfb\u3002","title":"\u5e38\u89c1\u95ee\u9898\u548c\u6545\u969c\u6392\u9664"},{"location":"flashing_os/","text":"\u70e7\u5f55\u955c\u50cf Micro-SD\u5361\u914d\u7f6e \u6700\u5c0f\u5efa\u8bae 16 Gb \u4ee5\u4e0a \u63a8\u8350\u4f7f\u7528 Class 10 \u4e3a\u4ec0\u4e48\u8f6f\u4ef6\u6709BLIKVM\u548cPiKVM\u4e24\u4e2a\u7248\u672c\uff1f\u4e24\u4e2a\u7248\u672c\u6709\u4ec0\u4e48\u533a\u522b\uff1f\u6211\u5e94\u8be5\u9009\u62e9\u54ea\u4e2a\uff1f\u6211\u53ef\u4ee5\u7528PiKVM\u5b98\u65b9\u955c\u50cf\u5417\uff1f BLIKVM\u9879\u76ee\u8bde\u751f\u4e4b\u521d\u5148\u7814\u53d1\u4e86\u786c\u4ef6\uff0c\u8f6f\u4ef6\u76f4\u63a5\u4f7f\u7528\u4e86PiKVM\u3002\u968f\u7740\u9879\u76ee\u7684\u4e0d\u65ad\u8fdb\u884c\uff0cBLIKVM\u81ea\u7814\u4e86\u81ea\u5df1\u7684\u5168\u65b0\u67b6\u6784\u7684\u8f6f\u4ef6\u7248\u672c\uff0c\u4e5f\u540c\u65f6\u4e3a\u66f4\u6df1\u5ea6\u7684\u548c\u81ea\u5df1\u7684\u786c\u4ef6\u914d\u5408\u505a\u597d\u57fa\u7840\uff1b BLIKVM\u548cPiKVM\u6700\u6838\u5fc3\u7684\u529f\u80fd\u5bf9\u7528\u6237\u6765\u8bf4\u662f\u4e00\u81f4\u7684\uff0c\u4e00\u4e9b\u7ec6\u5206\u529f\u80fd\u4e0d\u592a\u4e00\u6837\uff0c\u5982BLIKVM\u652f\u6301\u591a\u8bed\u8a00\uff1b \u9700\u6839\u636e\u60a8\u81ea\u5df1\u4f7f\u7528\u611f\u53d7\u53bb\u9009\u62e9\uff1b \u53ef\u4ee5\u4f7f\u7528PiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u4f46\u9700\u8981\u60a8\u6839\u636e\u786c\u4ef6\u7684\u4e0d\u540c\u505a\u4e00\u4e9b\u9002\u914d\uff0c\u4e3b\u8981\u6d89\u53ca\u5230\u7684\u6709\u5c4f\u5e55\u3001\u98ce\u6247\u7b49\uff0c\u56e0PiKVM\u5b98\u7f51\u955c\u50cf\u4e00\u76f4\u518d\u66f4\u65b0\uff0c\u6240\u4ee5\u5177\u4f53\u9002\u914d\u60c5\u51b5\u9700\u6839\u636e\u5f53\u65f6\u60a8\u4f7f\u7528\u5177\u4f53\u9047\u5230\u7684\u60c5\u51b5\u518d\u770b\uff1b \u4e0b\u8f7d\u955c\u50cf \u9700\u8981\u5728v4\u4e0a\u8fd0\u884c\u81ea\u884c\u5b89\u88c5PiKVM\u7684\u7528\u6237\u53ef\u4ee5\u53c2\u8003\u6b64 \u8bf4\u660e \u3002 BliKVM \u7248\u672c\u548c\u8f6f\u4ef6\u955c\u50cf\u517c\u5bb9\u6027 \u4ee5\u4e0b BliKVM \u7248\u672c\u4f7f\u7528\u76f8\u540c\u7684 BliKVM v1-3 \u8f6f\u4ef6\u955c\u50cf\uff1a BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 Allwinner \u4f7f\u7528\u5355\u72ec\u7684 Allwinner BliKVM \u955c\u50cf\u3002 BliKVM v4 Web UI \u6240\u6709\u652f\u6301\u7684\u7248\u672c\u7684 Web UI \u90fd\u4fdd\u6301\u4e00\u81f4\uff0c\u4fbf\u4e8e\u8fdc\u7a0b\u7ba1\u7406\u3002 \u57fa\u4e8e PiKVM \u7684\u8f6f\u4ef6 \u57fa\u4e8ePiKVM\u7684\u955c\u50cf\uff0c\u6811\u8393\u6d3e4B\u548cCM4\u4e0d\u516c\u7528\u4e00\u4e2a\u955c\u50cf\uff0c\u8fdb\u5165\u94fe\u63a5\u540e\u53ef\u770b\u5230\u4ee5\u5404\u786c\u4ef6\u7248\u672c(HAT CM4 PCIe)\u547d\u540d\u7684\u955c\u50cf\u3002 PiKVM \u955c\u50cf \u70e7\u5f55\u955c\u50cf Tip \u5ffd\u7565\u683c\u5f0f\u5316SD\u5361\u7684\u8bf7\u6c42\uff0c\u8fd9\u4e00\u6b65\u4e0d\u662f\u5fc5\u987b\u7684\u3002\u9009\u62e9\u6700\u9002\u5408\u4f60\u7684\u65b9\u6cd5\u3002 \u5982\u4f55\u5728\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u57574\u4e0a\u70e7\u5f55eMMC \u677f\u5b50\u94fe\u63a5 \u5982\u679c\u4f60\u4f7f\u7528\u7684CM4\u662f\u542beMMC\u7684\u7248\u672c\uff0c\u5982CM4102016\u578b\u53f7\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528v1\u548cv2\u786c\u4ef6\u76f4\u63a5\u5bf9CM4\u7684eMMC\u8fdb\u884c\u70e7\u5f55\u3002\u5982\u679c\u4f60\u7684CM4\u4e0d\u5e26eMMC\uff0c\u800c\u662f\u4f7f\u7528SD\u5361\uff0c\u4f60\u5219\u4e0d\u9700\u8981\u770b\u6b64\u7ae0\u8282\u3002\u9996\u5148\u5728blikvm\u786c\u4ef6\u4e0a\u5bf9CM4\u7684eMMC\u8fdb\u884c\u70e7\u5f55\uff0c\u4f60\u9700\u8981\u5148\u77ed\u63a5boot\u5f15\u811a\u3002 \u5982\u679c\u4f60\u4f7f\u7528 BLIKVM CM4 \u7248\u672c \u7136\u540e\u5c06\u6570\u636e\u7ebf\u8fde\u63a5\u5230USB OTG\u63a5\u53e3\u3002\u6253\u5f00blikvm\u7535\u6e90\u5e76\u89c2\u5bdfact\u706f\uff0c\u7eff\u706f\u5e38\u4eae\u3002 \u5982\u679c\u4f60\u4f7f\u7528 BLIKVM PCIe \u7248\u672c \u7136\u540e\u5c06\u6570\u636e\u7ebf\u8fde\u63a5\u5230USB-PC\u63a5\u53e3\u3002\u6253\u5f00blikvm\u7535\u6e90\u5e76\u89c2\u5bdfACT\u548cPWR LED\u706f\u4e0d\u4eae\u3002 \u901a\u8fc7usbboot/rpiboot\u521d\u59cb\u5316EMMC\u540e\uff0cACT\u548cPWR LED\u706f\u5e38\u4eae\u3002 EMMC \u77e5\u8bc6 \u5982\u679c\u4f60\u4f7f\u7528\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u5757\u5982CM3\u6216CM4 EMMC\uff0c\u4f60\u53ef\u4ee5\u901a\u8fc7usbboot\u521d\u59cb\u5316EMMC\u3002\u6ce8\u610fEMMC\u7248\u672c\u4e0d\u80fd\u76f4\u63a5\u4f7f\u7528SD\u5361\u542f\u52a8\u955c\u50cf\u3002 \u4ece\u8fd9\u4e2a\u89c6\u9891\u4e2d\u4f60\u53ef\u4ee5\u5feb\u901f\u5b66\u4e60\u5982\u4f55\u70e7\u5f55\u955c\u50cf\u3002 \u5982\u4f55\u5728\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u57574\u4e0a\u70e7\u5f55eMMC\u89c6\u9891 \u4ee5Ubuntu\u7cfb\u7edf\u4e3a\u53c2\u8003\u4f8b\u5b50 Linux usbboot \u5982\u679c\u4f60\u4f7f\u7528Micro-SD\u5361\uff0c\u4f60\u4e0d\u9700\u8981\u5173\u5fc3\u8fd9\u4e2a\u3002 # sudo apt-get install libusb-1.0-0-dev # git clone --depth=1 https://github.com/raspberrypi/usbboot # cd usbboot # make # sudo ./rpiboot \u5982\u679c\u51fa\u73b0\u4e0b\u56fe\u6240\u793a\u7684\u5185\u5bb9\uff0c\u5219\u8868\u793aEMMC\u521d\u59cb\u5316\u6210\u529f\u3002 \u4f7f\u7528 RPi Imager (Linux, MacOS \u548c Windows) \u8bf7\u6ce8\u610f\u4e0d\u8981\u5728RPi Imager\u5bf9\u955c\u50cf\u8fdb\u884c\u4efb\u4f55\u989d\u5916\u8bbe\u7f6e\uff0c\u5426\u5219\u5927\u6982\u7387\u4f1a\u5bfc\u81f4\u955c\u50cf\u542f\u52a8\u4e0d\u4e86\u6216\u8005\u53cd\u590d\u91cd\u542f\u95ee\u9898\u3002 \u4e0b\u8f7d\u5e76\u5b89\u88c5 \u6700\u65b0\u7248\u672c \u7684 RPi Imager \u3002 \u8fd0\u884c RPi Imager: \u6309 CHOOSE OS \u5e76\u5728\u5217\u8868\u5e95\u90e8\u9009\u62e9 Use custom \u955c\u50cf: \u70b9\u51fb\u6b64\u9879\u540e\uff0c\u9009\u62e9\u955c\u50cf\u6587\u4ef6 ( .img.xz )\uff0c\u7136\u540e\u70b9\u51fb CHOOSE STORAGE : \u5c06\u5185\u5b58\u5361\u63d2\u5165\u8bfb\u5361\u5668\u3002\u4ece\u6b64\u5217\u8868\u4e2d\u9009\u62e9\u8bfb\u5361\u5668\u3002 \u5c0f\u5fc3 \u5e76\u9009\u62e9\u6b63\u786e\u7684\u8bbe\u5907: \u9009\u62e9\u5185\u5b58\u5361\u540e\uff0c\u6309 WRITE \u6309\u94ae\u3002\u5f53\u88ab\u8be2\u95ee\u65f6\u786e\u8ba4\u64cd\u4f5c: \u7b49\u5f85\u8fc7\u7a0b\u5b8c\u6210\u3002\u559d\u676f\u5496\u5561\u6216\u505a\u4e9b\u4f38\u5c55\u8fd0\u52a8 :) Tip \u8fc7\u7a0b\u53ef\u80fd\u4f1a\u572899%\u65f6\u6302\u8d77\u5f88\u957f\u65f6\u95f4\uff0c\u8fd9\u6ca1\u5173\u7cfb\uff0c\u53ea\u9700\u7b49\u5f85\u5b8c\u6210 \u6210\u529f\u5b8c\u6210\u540e\u53d6\u51fa\u5185\u5b58\u5361: Tip \u5982\u679c\u5728\u70e7\u5f55\u6216\u542f\u52a8PiKVM\u65f6\u53d1\u751f\u9519\u8bef\uff0c\u8bf7\u91cd\u590d\u6b64\u8fc7\u7a0b\u3002","title":"\u70e7\u5f55\u955c\u50cf"},{"location":"flashing_os/#_1","text":"Micro-SD\u5361\u914d\u7f6e \u6700\u5c0f\u5efa\u8bae 16 Gb \u4ee5\u4e0a \u63a8\u8350\u4f7f\u7528 Class 10 \u4e3a\u4ec0\u4e48\u8f6f\u4ef6\u6709BLIKVM\u548cPiKVM\u4e24\u4e2a\u7248\u672c\uff1f\u4e24\u4e2a\u7248\u672c\u6709\u4ec0\u4e48\u533a\u522b\uff1f\u6211\u5e94\u8be5\u9009\u62e9\u54ea\u4e2a\uff1f\u6211\u53ef\u4ee5\u7528PiKVM\u5b98\u65b9\u955c\u50cf\u5417\uff1f BLIKVM\u9879\u76ee\u8bde\u751f\u4e4b\u521d\u5148\u7814\u53d1\u4e86\u786c\u4ef6\uff0c\u8f6f\u4ef6\u76f4\u63a5\u4f7f\u7528\u4e86PiKVM\u3002\u968f\u7740\u9879\u76ee\u7684\u4e0d\u65ad\u8fdb\u884c\uff0cBLIKVM\u81ea\u7814\u4e86\u81ea\u5df1\u7684\u5168\u65b0\u67b6\u6784\u7684\u8f6f\u4ef6\u7248\u672c\uff0c\u4e5f\u540c\u65f6\u4e3a\u66f4\u6df1\u5ea6\u7684\u548c\u81ea\u5df1\u7684\u786c\u4ef6\u914d\u5408\u505a\u597d\u57fa\u7840\uff1b BLIKVM\u548cPiKVM\u6700\u6838\u5fc3\u7684\u529f\u80fd\u5bf9\u7528\u6237\u6765\u8bf4\u662f\u4e00\u81f4\u7684\uff0c\u4e00\u4e9b\u7ec6\u5206\u529f\u80fd\u4e0d\u592a\u4e00\u6837\uff0c\u5982BLIKVM\u652f\u6301\u591a\u8bed\u8a00\uff1b \u9700\u6839\u636e\u60a8\u81ea\u5df1\u4f7f\u7528\u611f\u53d7\u53bb\u9009\u62e9\uff1b \u53ef\u4ee5\u4f7f\u7528PiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u4f46\u9700\u8981\u60a8\u6839\u636e\u786c\u4ef6\u7684\u4e0d\u540c\u505a\u4e00\u4e9b\u9002\u914d\uff0c\u4e3b\u8981\u6d89\u53ca\u5230\u7684\u6709\u5c4f\u5e55\u3001\u98ce\u6247\u7b49\uff0c\u56e0PiKVM\u5b98\u7f51\u955c\u50cf\u4e00\u76f4\u518d\u66f4\u65b0\uff0c\u6240\u4ee5\u5177\u4f53\u9002\u914d\u60c5\u51b5\u9700\u6839\u636e\u5f53\u65f6\u60a8\u4f7f\u7528\u5177\u4f53\u9047\u5230\u7684\u60c5\u51b5\u518d\u770b\uff1b","title":"\u70e7\u5f55\u955c\u50cf"},{"location":"flashing_os/#_2","text":"\u9700\u8981\u5728v4\u4e0a\u8fd0\u884c\u81ea\u884c\u5b89\u88c5PiKVM\u7684\u7528\u6237\u53ef\u4ee5\u53c2\u8003\u6b64 \u8bf4\u660e \u3002","title":"\u4e0b\u8f7d\u955c\u50cf"},{"location":"flashing_os/#blikvm","text":"\u4ee5\u4e0b BliKVM \u7248\u672c\u4f7f\u7528\u76f8\u540c\u7684 BliKVM v1-3 \u8f6f\u4ef6\u955c\u50cf\uff1a BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 Allwinner \u4f7f\u7528\u5355\u72ec\u7684 Allwinner BliKVM \u955c\u50cf\u3002 BliKVM v4 Web UI \u6240\u6709\u652f\u6301\u7684\u7248\u672c\u7684 Web UI \u90fd\u4fdd\u6301\u4e00\u81f4\uff0c\u4fbf\u4e8e\u8fdc\u7a0b\u7ba1\u7406\u3002","title":"BliKVM \u7248\u672c\u548c\u8f6f\u4ef6\u955c\u50cf\u517c\u5bb9\u6027"},{"location":"flashing_os/#pikvm","text":"\u57fa\u4e8ePiKVM\u7684\u955c\u50cf\uff0c\u6811\u8393\u6d3e4B\u548cCM4\u4e0d\u516c\u7528\u4e00\u4e2a\u955c\u50cf\uff0c\u8fdb\u5165\u94fe\u63a5\u540e\u53ef\u770b\u5230\u4ee5\u5404\u786c\u4ef6\u7248\u672c(HAT CM4 PCIe)\u547d\u540d\u7684\u955c\u50cf\u3002 PiKVM \u955c\u50cf","title":"\u57fa\u4e8e PiKVM \u7684\u8f6f\u4ef6"},{"location":"flashing_os/#_3","text":"Tip \u5ffd\u7565\u683c\u5f0f\u5316SD\u5361\u7684\u8bf7\u6c42\uff0c\u8fd9\u4e00\u6b65\u4e0d\u662f\u5fc5\u987b\u7684\u3002\u9009\u62e9\u6700\u9002\u5408\u4f60\u7684\u65b9\u6cd5\u3002 \u5982\u4f55\u5728\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u57574\u4e0a\u70e7\u5f55eMMC","title":"\u70e7\u5f55\u955c\u50cf"},{"location":"flashing_os/#_4","text":"\u5982\u679c\u4f60\u4f7f\u7528\u7684CM4\u662f\u542beMMC\u7684\u7248\u672c\uff0c\u5982CM4102016\u578b\u53f7\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528v1\u548cv2\u786c\u4ef6\u76f4\u63a5\u5bf9CM4\u7684eMMC\u8fdb\u884c\u70e7\u5f55\u3002\u5982\u679c\u4f60\u7684CM4\u4e0d\u5e26eMMC\uff0c\u800c\u662f\u4f7f\u7528SD\u5361\uff0c\u4f60\u5219\u4e0d\u9700\u8981\u770b\u6b64\u7ae0\u8282\u3002\u9996\u5148\u5728blikvm\u786c\u4ef6\u4e0a\u5bf9CM4\u7684eMMC\u8fdb\u884c\u70e7\u5f55\uff0c\u4f60\u9700\u8981\u5148\u77ed\u63a5boot\u5f15\u811a\u3002 \u5982\u679c\u4f60\u4f7f\u7528 BLIKVM CM4 \u7248\u672c \u7136\u540e\u5c06\u6570\u636e\u7ebf\u8fde\u63a5\u5230USB OTG\u63a5\u53e3\u3002\u6253\u5f00blikvm\u7535\u6e90\u5e76\u89c2\u5bdfact\u706f\uff0c\u7eff\u706f\u5e38\u4eae\u3002 \u5982\u679c\u4f60\u4f7f\u7528 BLIKVM PCIe \u7248\u672c \u7136\u540e\u5c06\u6570\u636e\u7ebf\u8fde\u63a5\u5230USB-PC\u63a5\u53e3\u3002\u6253\u5f00blikvm\u7535\u6e90\u5e76\u89c2\u5bdfACT\u548cPWR LED\u706f\u4e0d\u4eae\u3002 \u901a\u8fc7usbboot/rpiboot\u521d\u59cb\u5316EMMC\u540e\uff0cACT\u548cPWR LED\u706f\u5e38\u4eae\u3002 EMMC \u77e5\u8bc6 \u5982\u679c\u4f60\u4f7f\u7528\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u5757\u5982CM3\u6216CM4 EMMC\uff0c\u4f60\u53ef\u4ee5\u901a\u8fc7usbboot\u521d\u59cb\u5316EMMC\u3002\u6ce8\u610fEMMC\u7248\u672c\u4e0d\u80fd\u76f4\u63a5\u4f7f\u7528SD\u5361\u542f\u52a8\u955c\u50cf\u3002 \u4ece\u8fd9\u4e2a\u89c6\u9891\u4e2d\u4f60\u53ef\u4ee5\u5feb\u901f\u5b66\u4e60\u5982\u4f55\u70e7\u5f55\u955c\u50cf\u3002 \u5982\u4f55\u5728\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u57574\u4e0a\u70e7\u5f55eMMC\u89c6\u9891 \u4ee5Ubuntu\u7cfb\u7edf\u4e3a\u53c2\u8003\u4f8b\u5b50","title":"\u677f\u5b50\u94fe\u63a5"},{"location":"flashing_os/#linux-usbboot","text":"\u5982\u679c\u4f60\u4f7f\u7528Micro-SD\u5361\uff0c\u4f60\u4e0d\u9700\u8981\u5173\u5fc3\u8fd9\u4e2a\u3002 # sudo apt-get install libusb-1.0-0-dev # git clone --depth=1 https://github.com/raspberrypi/usbboot # cd usbboot # make # sudo ./rpiboot \u5982\u679c\u51fa\u73b0\u4e0b\u56fe\u6240\u793a\u7684\u5185\u5bb9\uff0c\u5219\u8868\u793aEMMC\u521d\u59cb\u5316\u6210\u529f\u3002","title":"Linux usbboot"},{"location":"flashing_os/#rpi-imager-linux-macos-windows","text":"\u8bf7\u6ce8\u610f\u4e0d\u8981\u5728RPi Imager\u5bf9\u955c\u50cf\u8fdb\u884c\u4efb\u4f55\u989d\u5916\u8bbe\u7f6e\uff0c\u5426\u5219\u5927\u6982\u7387\u4f1a\u5bfc\u81f4\u955c\u50cf\u542f\u52a8\u4e0d\u4e86\u6216\u8005\u53cd\u590d\u91cd\u542f\u95ee\u9898\u3002 \u4e0b\u8f7d\u5e76\u5b89\u88c5 \u6700\u65b0\u7248\u672c \u7684 RPi Imager \u3002 \u8fd0\u884c RPi Imager: \u6309 CHOOSE OS \u5e76\u5728\u5217\u8868\u5e95\u90e8\u9009\u62e9 Use custom \u955c\u50cf: \u70b9\u51fb\u6b64\u9879\u540e\uff0c\u9009\u62e9\u955c\u50cf\u6587\u4ef6 ( .img.xz )\uff0c\u7136\u540e\u70b9\u51fb CHOOSE STORAGE : \u5c06\u5185\u5b58\u5361\u63d2\u5165\u8bfb\u5361\u5668\u3002\u4ece\u6b64\u5217\u8868\u4e2d\u9009\u62e9\u8bfb\u5361\u5668\u3002 \u5c0f\u5fc3 \u5e76\u9009\u62e9\u6b63\u786e\u7684\u8bbe\u5907: \u9009\u62e9\u5185\u5b58\u5361\u540e\uff0c\u6309 WRITE \u6309\u94ae\u3002\u5f53\u88ab\u8be2\u95ee\u65f6\u786e\u8ba4\u64cd\u4f5c: \u7b49\u5f85\u8fc7\u7a0b\u5b8c\u6210\u3002\u559d\u676f\u5496\u5561\u6216\u505a\u4e9b\u4f38\u5c55\u8fd0\u52a8 :) Tip \u8fc7\u7a0b\u53ef\u80fd\u4f1a\u572899%\u65f6\u6302\u8d77\u5f88\u957f\u65f6\u95f4\uff0c\u8fd9\u6ca1\u5173\u7cfb\uff0c\u53ea\u9700\u7b49\u5f85\u5b8c\u6210 \u6210\u529f\u5b8c\u6210\u540e\u53d6\u51fa\u5185\u5b58\u5361: Tip \u5982\u679c\u5728\u70e7\u5f55\u6216\u542f\u52a8PiKVM\u65f6\u53d1\u751f\u9519\u8bef\uff0c\u8bf7\u91cd\u590d\u6b64\u8fc7\u7a0b\u3002","title":"\u4f7f\u7528 RPi Imager (Linux, MacOS \u548c Windows)"},{"location":"hdmi-csi-i2s/","text":"HDMI\u8f6cCSI&I2S\u6a21\u5757\u624b\u518c \u5c06HDMI\u4fe1\u53f7\u8f6c\u6362\u6210CSI\u89c6\u9891\u4fe1\u53f7\u548cI2S\u97f3\u9891\u4fe1\u53f7, \u76ee\u524d\u5168\u5e73\u53f0\u652f\u6301(zero, Pi3B, Pi4B, CM4, Pi5B),\u5176\u4e2d\u6700\u9ad8\u91c7\u96c6\u5206\u8fa8\u7387\u4e0d\u4ec5\u4ec5\u53d6\u51b3\u4e8eHDMI\u8f6cCSI\u8f6c\u6362\u677f\uff0c\u540c\u65f6\u4e5f\u53d6\u51b3\u4e8e\u4f60\u4f7f\u7528\u7684\u6811\u8393\u6d3e\u786c\u4ef6\u7248\u672c\uff0c\u6811\u8393\u6d3e\u786c\u4ef6\u7248\u76ee\u524d\u4e3b\u8981\u5206\u4e24\u4e2a\u7cfb\u5217\uff0c\u6700\u9ad8\u652f\u63011080P60Hz\uff0c\u548c\u6700\u9ad8\u652f\u63011080P50Hz\u3002 \u6700\u9ad8\u652f\u63011080P60Hz\u7684Pi\u7248\u672c(CM3\uff0cCM4\uff0cPi5B) \u6700\u9ad8\u652f\u63011080P50Hz\u7684Pi\u7248\u672c(zero, zero2, Pi3B, Pi4B\u7b49) \u7b80\u4ecb \u6b64\u6a21\u5757\u5c06HDMI\u4fe1\u53f7\u8f6c\u6362\u6210CSI\u89c6\u9891\u4fe1\u53f7\u548cI2S\u97f3\u9891\u4fe1\u53f7\uff0c\u6700\u9ad8\u652f\u63011080P60Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u5728\u6811\u8393\u6d3e\u4e0a\u5de5\u4f5c\u7684\u5f88\u597d\uff0c\u76ee\u524d\u5171\u67093\u4e2a\u7248\u672c(C779\u3001C780\u3001C790). C790\u662f\u76ee\u524d\u6700\u65b0\u7684\u7248\u672c\uff0c\u89e3\u51b3\u4e86\u6240\u6709\u5df2\u77e5\u7684\u95ee\u9898\uff0c\u540c\u662f\u6709CSI 2\u901a\u9053\u548c4\u901a\u9053\u63a5\u53e3\uff0cI2S\u97f3\u9891\u63a5\u53e3\uff0c\u4fee\u590d\u4e86HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898\u3002 \u6027\u80fd\u53c2\u6570 C790 \u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u5728\u6811\u8393\u6d3e\u4e0a\u6b64\u6a21\u5757\u6700\u9ad8\u652f\u63011080P60Hz\u8f93\u5165\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG 4\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f CSI-2\u63a5\u53e31: 15 pin FPC, \u95f4\u8ddd1.0 mm, \u5728C790\u6a21\u5757\u7684\u6b63\u9762. CSI-2\u63a5\u53e32, 22 pin FPC, \u95f4\u8ddd0.5 mm, \u5728C790\u6a21\u5757\u7684\u80cc\u9762. \u5c3a\u5bf8: 30 x 45 mm \u5b89\u88c5\u5b54\u4f4d:4 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u6811\u8393\u6d3e4B\u53ea\u652f\u63011080P50Hz(\u56e0\u4e3a4B\u53ea\u6709\u4e24\u4e2aCSI-2\u901a\u9053) ,\u6811\u8393\u6d3eCM4\u53ea\u652f\u63011080P60Hz,\u6240\u4ee5\u5982\u679c\u4f60\u7684\u8f93\u5165\u8bbe\u5907\u4e00\u5b9a\u8981\u662f1080P60Hz\uff0c\u8bf7\u540c\u65f6\u4f7f\u7528CM4\u548cC790. \u63a5\u53e3 C790\u6709\u4e24\u4e2aCSI\u8f93\u51fa\u63a5\u53e3: \u63a5\u53e31\uff0c\u5728C790\u6b63\u9762\uff0c15 pin FPC, \u95f4\u8ddd1.0 mm; \u63a5\u53e31\uff0c\u5728C790\u80cc\u9762,22 pin FPC, \u95f4\u8ddd0.5 mm\u3002 \u5c3a\u5bf8 \u5b89\u88c5\u53c2\u8003 C780 C780A\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P50Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 2\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 15 pin FPC, \u95f4\u8ddd 1.0 mm\uff1b \u5c3a\u5bf8: 30 x 65 mm (\u6298\u65ad\u524d); 30 x 45 mm (\u6298\u65ad\u540e) \u5b89\u88c5\u5b54\u4f4d:6 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g C780B\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P60Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 4\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 22 pin FPC, \u95f4\u8ddd 0.5 mm\uff1b \u5c3a\u5bf8: 30 x 65 mm (\u6298\u65ad\u524d); 30 x 45 mm (\u6298\u65ad\u540e) \u5b89\u88c5\u5b54\u4f4d:6 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u63a5\u53e3 \u97f3\u9891\u5f15\u811a\u5b9a\u4e49\u5982\u4e0b\u56fe\u6240\u793a: \u5c3a\u5bf8 \u5c3a\u5bf8\u5982\u4e0b\u56fe\u6240\u793a. \u67096\u4e2a\u76f4\u5f84\u4e3a2\u300275mm\u7684\u5b54\u4f4d\u7528\u4e8e\u5b89\u88c5\uff0c\u5b89\u88c5\u87ba\u9489\u53ef\u4ee5\u9009\u62e9M2.5\u3002 \u5982\u4e0b\u56fe\u6240\u793a\uff0cC780\u88ab\u8bbe\u8ba1\u6210\u53ef\u6298\u65ad\u5f0f\u7684\uff0cC780\u6a21\u5757\u5728\u672a\u88ab\u6298\u65ad\u524d\u53ef\u4ee5\u5b8c\u7f8e\u7684\u5b89\u88c5\u5728zero\u4e0a\u3002 C779 \u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P50Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 2\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 15 pin FPC, \u95f4\u8ddd 1.0 mm\uff1b \u5c3a\u5bf8: 35 x 50 mm \u5b89\u88c5\u5b54\u4f4d:4 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u5c3a\u5bf8 \u5c3a\u5bf8\u5982\u4e0b\u56fe\u6240\u793a. \u67094\u4e2a\u76f4\u5f84\u4e3a2.75mm\u7684\u5b54\u4f4d\u7528\u4e8e\u5b89\u88c5\uff0c\u5b89\u88c5\u87ba\u9489\u53ef\u4ee5\u9009\u62e9M2.5\u3002 CSI\u63a5\u53e3\u5b9a\u4e49 \u5176\u4e2dC779\uff0cC780A\u53ea\u670915PIN\u5f15\u811a\uff0cC780B\u53ea\u670922PIN\u5f15\u811a\uff0cC790\u540c\u65f6\u670915\u548c22PIN\u5f15\u811a\u3002 \u8f6f\u4ef6\u4f7f\u7528demo \u4e0b\u6587\u4e2d\u7684\u8f6f\u4ef6\u4f7f\u7528\u65b9\u6cd5\u8ddf\u4f60\u4f7f\u7528\u7684\u6811\u8393\u6d3e\u955c\u50cf\u7248\u672c\u6709\u5173\uff0c\u53ef\u80fd\u5b58\u5728\u4e0d\u540c\u3002\u5982\u679c\u4f60\u6709\u4efb\u4f55\u7591\u95ee\uff0c\u8bf7\u52a0\u5165 BLIKVM Discord \u793e\u533a \u83b7\u5f97\u652f\u6301\u3001\u89e3\u7b54\u548c\u65b0\u95fb\u3002 \u4ee5\u4e0b\u8bf4\u660e\u9002\u7528\u4e8e\u5185\u6838\u4e3a5.4\u6216\u8005\u66f4\u9ad8\u7248\u672c\u3002\u5982\u679c\u4f60\u7684\u6811\u8393\u6d3e\u955c\u50cf\u4f4e\u4e8e\u6b64\u7248\u672c\uff0c\u8bf7\u5347\u7ea7\u3002\u7ec8\u7aef\u4f7f\u7528\u4f7f\u7528\u201cuname-a\u201d\u53ef\u4ee5\u67e5\u770b\u4f60\u7cfb\u7edf\u7684\u5185\u6838\u7248\u672c\u3002 pi@raspberrypi:~ $ uname -a Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. \u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u8fdb\u884c\u5347\u7ea7 (\u4e0d\u662f\u5fc5\u987b\u7684\uff0c\u5728\u67d0\u4e9b\u56fd\u5bb6\u8fd9\u4e2a\u82b1\u8d39\u7684\u65f6\u95f4\u53ef\u80fd\u5f88\u957f) sudo apt-get update sudo apt-get upgrade 2. \u4f7f\u80fd\u76f8\u673a\u6a21\u5757(\u5728\u6811\u8393\u6d3eBullseys OS\u7cfb\u7edf\u4e2d\uff0c\u76f8\u673a\u5df2\u9ed8\u8ba4\u88ab\u4f7f\u80fd) sudo raspi-config sudo reboot \u79fb\u52a8\u5149\u6807\u5230\u2018Interfacing Options\u2019\uff0c\u7136\u540e\u6309Enter\u952e\u8fdb\u5165\u3002\u7136\u540e\u9009\u62e9\u2018Camera\u2019\u9009\u9879\uff0c\u6309Enter\u952e\u8fdb\u5165\u540e\uff0c\u4f7f\u80fd\u76f8\u673a\u3002\u7136\u540e\u9009\u62e9\u201cFinish\u201d\u540e\uff0c \u9009\u62e9\u201creboot\u201d\u3002 \u91cd\u542f\u975e\u5e38\u91cd\u8981!! \u7531\u4e8ePi5B\u53d6\u6d88\u4e86\u786c\u7f16\u7801\u5668\uff0c\u4e0b\u9762\u8f6f\u4ef6\u4f7f\u7528\u65b9\u6cd5\u5728Pi\u5e73\u53f0\u76ee\u524d\u5206\u4e3a\u4e24\u4e2a\u90e8\u5206\uff0cPi5B\u914d\u7f6e\uff0c\u548c\u5176\u5b83Pi\u5e73\u53f0\u914d\u7f6e\u3002 \u5728zero, zero2,Pi3B,Pi4B\u7b49\u5e73\u53f0HDMI\u8f6cCSI\u6a21\u5757\u6d4b\u8bd5demo\u53c2\u8003 \u7f16\u8f91 /boot/config.txt (\u9700\u8981sudo\u6743\u9650) sudo nano /boot/config.txt \u6dfb\u52a0\u4e0b\u9762\u7684\u5185\u5bb9 dtoverlay=tc358743 \u5982\u679c\u4f60\u7684\u6a21\u5757(C780\u548cC790)\u652f\u6301\u58f0\u97f3\uff0c\u6dfb\u52a0\u4e0b\u9762\u5185\u5bb9\u652f\u6301\u58f0\u97f3 dtoverlay=tc358743-audio \u5982\u679c\u4f60\u662f\u7528\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u7ec4(CM3\u3001CM4)\uff0c\u53ef\u4ee5\u901a\u8fc7\u4e0b\u5217\u914d\u7f6e\uff0c\u4f7f\u80fdCSI\u76844\u4e2a\u901a\u9053\u3002 dtoverlay=tc358743,4lane=1 \u4f7f\u7528\u201cdmesg | grep cma\u201d\u68c0\u67e5\u5206\u914d\u7ed9CMA\u5806\u7684\u5185\u5b58\u91cf\uff0c\u7ec8\u7aef\u51fa\u73b0\u7684\u7b2c\u4e00\u884c\u5185\u5bb9\u5e94\u8be5\u5982\u4e0b\u6240\u793a: pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 \u5982\u679c\u663e\u793a\u5c11\u4e8e96MB\uff0c\u7f16\u8f91/boot/cmdline.txt\uff0c\u6dfb\u52a0\u4e0b\u9762\u4e00\u884c\u3002 cma=96M \u91cd\u542f\u6811\u8393\u6d3e\uff0c\u5982\u679c\u914d\u7f6e\u6210\u529f\uff0c\u4f60\u5c06\u4f1a\u770b\u5230/dev/video0\u8bbe\u5907\u63cf\u8ff0\u7b26\u51fa\u73b0\u3002\u53ef\u4ee5\u4f7f\u7528\u201cv4l2-ctl \u2013list-devices\u201d \u547d\u4ee4\u5217\u51fa\u6240\u6709\u7684video\u63cf\u8ff0\u7b26\u3002\u518d\u5c06\u6811\u8393\u6d3e\u4e0e\u6a21\u5757\u6b63\u786e\u8fde\u63a5\u540e\uff0c\u6811\u8393\u6d3e\u4e0a\u7535\uff0c\u4f60\u53ef\u4ee5\u770b\u5230C790\u6a21\u5757\u4e0a\u6709\u4e00\u4e2a\u7eff\u8272\u706f\u5e38\u4eae\uff0c\u7136\u540e\u53ef\u4ee5\u6309\u7167\u4e0b\u9762\u7684\u547d\u4ee4\uff0c\u68c0\u67e5\u662f\u5426\u5df2\u7ecf\u6b63\u5e38\u51fa\u73b0\u4e86video0\u3002 pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 \u9ed8\u8ba4\u6ca1\u6709\u52a0\u8f7dEDID,\u5982\u679c\u4f60\u6709EDID\u7f16\u8f91\u5668\uff0c\u4f60\u53ef\u4ee5\u81ea\u5df1\u7f16\u8f91\u4f60\u6240\u9700\u8981\u7684\u5206\u8fa8\u7387\uff0c\u6216\u8005\u4f7f\u7528\u4e0b\u9762\u63d0\u4f9b\u7684EDID\u5206\u8fa8\u7387\uff08720p60hz\uff09\u3002 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt # \u62f7\u8d1d\u4e0a\u95e8\u7684\u5185\u5bb9\u5230edid.txt\u6587\u4ef6\u4e2d\uff0c\u7136\u540e\u4fdd\u5b58\u9000\u51fa\u3002\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u8bbe\u7f6e\u52a0\u8f7dedid\uff0c\u5982\u679c\u6b63\u786e\u8bbe\u7f6e\uff0c\u53ef\u4ee5\u770b\u5230\u5982\u4e0b\u7684\u8f93\u51fa\u3002 pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan \u9a71\u52a8\u7a0b\u5e8f\u4e0d\u4f1a\u81ea\u52a8\u5207\u6362\u5230\u68c0\u6d4b\u5230\u7684\u5206\u8fa8\u7387\u3002\u662f\u7528\u4e0b\u5217\u547d\u4ee4\u68c0\u67e5\u76ee\u524dHDMI\u7684\u8f93\u5165 pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: \u4f60\u5fc5\u987b\u4f7f\u7528\u201cv4l2-ctl \u2013set-dv-bt-timings\u201d\u547d\u4ee4\u8bbe\u7f6e\u9a71\u52a8\u7a0b\u5e8f\u4f7f\u7528\u76ee\u524d\u7684\u8f93\u5165\u5206\u8fa8\u7387 v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. \u82af\u7247\u652f\u6301\u4e24\u79cd\u683c\u5f0f(BGR3\u548cUYVY)\uff0cBGR3\u50cf\u7d20\u6df1\u5ea6\u4e3a24bpp\uff0cUYVY\u4e3aYUV4:2:2 16bpp\u3002\u5982\u679c\u4f7f\u7528CSI 2\u901a\u9053\uff0cBGR3\u683c\u5f0f\u6700\u5927\u652f\u63011080P30Hz\u7684\u8f93\u5165\uff0c\u4f7f\u7528UYVY\u5219\u6700\u5927\u652f\u63011080P60Hz\u7684\u8f93\u5165\u3002\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u8bbe\u7f6e\u4e3aUYVY\u683c\u5f0f\u3002 v4l2-ctl -v pixelformat=UYVY \u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\uff0c\u68c0\u67e5\u97f3\u9891\u786c\u4ef6\u548c\u9a71\u52a8\u662f\u5426\u6b63\u5e38\u3002 pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1: tc358743\u610f\u5473\u7740\u97f3\u9891\u76f8\u5173\u786c\u4ef6\u5df2\u88ab\u6b63\u786e\u52a0\u8f7d\uff0c\u6ce8\u610f\u8fd9\u91cc\u76841\u53ef\u80fd\u4e0d\u540c\u3002 \u5b89\u88c5GStreamer\u5de5\u5177. sudo apt install gstreamer1.0-tools sudo apt-get install gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-plugins-bad sudo apt-get install gstreamer1.0-plugins-base \u68c0\u67e5gstreamer\u5de5\u5177\u7248\u672c: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note:\u4e0d\u540c\u7684\u7248\u672c\u8fd9\u91cc\u8f93\u51fa\u53ef\u80fd\u4e0d\u540c. \u4f7f\u7528gstreamer\u53bb\u5f55\u5236\u89c6\u9891\u6216\u8005\u58f0\u97f3 #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. \u4f60\u4f1a\u5f97\u5230\u4e00\u4e2afoo.mkv\u6587\u4ef6. \u5982\u679c\u4f60\u7684gstreamer\u662f1.8\u6216\u8005\u66f4\u9ad8\u7248\u672c\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u3002\u5176\u4e2ddevice=hw:1\u8868\u793a\u7684\u662fTC358743\u58f0\u5361\u3002 #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: \u8fd9\u91cc\u6211\u4eec\u5efa\u8bae\u4f60\u4f7f\u7528\u5b9e\u9645\u7684\u8f93\u5165\u5e27\u7387\u53bb\u91c7\u96c6HDMI\u4fe1\u53f7\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528 \u2018v4l2-ctl \u2013query-dv-timings\u2019\u53bb\u68c0\u67e5\u5b9e\u9645\u8f93\u5165\u5e27\u7387\u3002 \u5982\u4e0a\u56fe\u4e2d\u7684HDMI\u8f93\u5165\u8bbe\u5907\uff0c\u5e27\u7387\u662f60Hz\uff0c\u6240\u4ee5\u6211\u4eec\u53ef\u4ee5\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u53bb\u5f55\u5236\u89c6\u9891\uff1a gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv \u5f55\u5236\u89c6\u9891\u548c\u97f3\u9891: (\u5982\u679c\u4f60\u7684\u8bbe\u5907\u652f\u6301\u97f3\u9891\u7684\u8bdd) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9) Pi5B\u7b49\u5e73\u53f0HDMI\u8f6cCSI\u6a21\u5757\u6d4b\u8bd5demo\u53c2\u8003 \u4e0b\u9762\u6d4b\u8bd5\u4e2d\uff0c\u4f7f\u7528cam1\u901a\u9053\u8fdb\u884c\u6d4b\u8bd5\uff0c\u6d4b\u8bd5\u8f93\u5165\u5206\u8fa8\u7387\u4e3a1080P24Hz\u3002\u6811\u8393\u6d3e5b\u6d4b\u8bd5\u8fc7\u7a0b\u4e2d\u53d1\u73b0edid\u8bbe\u7f6e\u65e0\u6548\uff0c\u56e0\u6b64\u9700\u8981\u901a\u8fc7\u6dfb\u52a0HDMI\u8bf1\u9a97\u5668\u6765\u5f3a\u5236\u76ee\u6807\u8bbe\u7f6e\u8f93\u51faHDMI\uff0c\u5426\u5219\u6811\u8393\u6d3e5b\u5f88\u6709\u53ef\u80fd\u83b7\u53d6\u4e0d\u5230\u4efb\u4f55\u8f93\u5165\u3002\u7531\u4e8e\u6811\u8393\u6d3e5b\u6ca1\u6709\u5bf9\u5e94\u7684\u786c\u7f16\u7801\u786c\u4ef6\uff0c\u6240\u4ee5\u6811\u8393\u6d3e5b+C790\u56fe\u50cf\u91c7\u96c6\u80fd\u529b\u6027\u80fd\u4e00\u822c\uff0c\u4e0d\u5982\u7528\u6811\u8393\u6d3e4b \u7f16\u8f91 /boot/config.txt (\u9700\u8981sudo\u6743\u9650) sudo nano /boot/config.txt \u6dfb\u52a0\u4e0b\u9762\u7684\u5185\u5bb9 dtoverlay=tc358743 \u5982\u679c\u4f60\u7684\u6a21\u5757(C780\u548cC790)\u652f\u6301\u58f0\u97f3\uff0c\u6dfb\u52a0\u4e0b\u9762\u5185\u5bb9\u652f\u6301\u58f0\u97f3 dtoverlay=tc358743-audio \u91cd\u542f\u6811\u8393\u6d3e,\u6267\u884c\u4e0b\u9762\u6307\u4ee4\uff0c\u627e\u5230csi\u5bf9\u5e94\u7684media\u8282\u70b9\u4e3amedia0,\u5373rp1-cfe (platform:1f00128000.csi)\u5b57\u6bb5\u4e0b\u7684media\u8bbe\u5907: blikvm@blikvm:~ $ v4l2-ctl --list-devices pispbe (platform:1000880000.pisp_be): /dev/video20 /dev/video21 /dev/video22 /dev/video23 /dev/video24 /dev/video25 /dev/video26 /dev/video27 /dev/video28 /dev/video29 /dev/video30 /dev/video31 /dev/video32 /dev/video33 /dev/video34 /dev/video35 /dev/video36 /dev/video37 /dev/media1 /dev/media2 rp1-cfe (platform:1f00128000.csi): /dev/video0 /dev/video1 /dev/video2 /dev/video3 /dev/video4 /dev/video5 /dev/video6 /dev/video7 /dev/media0 rpivid (platform:rpivid): /dev/video19 /dev/media3 \u627e\u5230tc358743\u5bf9\u5e94\u8282\u70b9\u4e3av4l-subdev2\uff0crp1-cfe-csi2_ch0\u7684pad0\u4e3avideo0: blikvm@blikvm:~ $ media-ctl -d /dev/media0 -p Media controller API version 6.1.63 Media device information ------------------------ driver rp1-cfe model rp1-cfe serial bus info platform:1f00128000.csi hw revision 0x114666 driver version 6.1.63 Device topology - entity 1: csi2 (8 pads, 8 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"tc358743 4-000f\":0 [ENABLED,IMMUTABLE] pad1: Sink [fmt:unknown/8192x1 field:none] pad2: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad3: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad4: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch0\":0 [] -> \"pisp-fe\":0 [] pad5: Source [fmt:unknown/8192x1 field:none] -> \"rp1-cfe-embedded\":0 [] pad6: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch2\":0 [] -> \"pisp-fe\":0 [] pad7: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch3\":0 [] -> \"pisp-fe\":0 [] - entity 10: pisp-fe (5 pads, 7 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: Sink [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"csi2\":4 [] <- \"csi2\":6 [] <- \"csi2\":7 [] pad1: Sink [fmt:FIXED/8192x1 field:none] <- \"rp1-cfe-fe_config\":0 [] pad2: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image0\":0 [] pad3: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image1\":0 [] pad4: Source [fmt:FIXED/8192x1 field:none] -> \"rp1-cfe-fe_stats\":0 [] - entity 16: tc358743 4-000f (1 pad, 1 link) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev2 pad0: Source [fmt:RGB888_1X24/640x480 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:640x350@13000000 max:1920x1200@165000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom] [dv.detect:BT.656/1120 1920x1080p24 (2750x1125) stds: flags:] [dv.current:BT.656/1120 640x480p59 (800x525) stds:CEA-861,DMT flags:has-cea861-vic] -> \"csi2\":0 [ENABLED,IMMUTABLE] - entity 18: rp1-cfe-csi2_ch0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 pad0: Sink <- \"csi2\":4 [] - entity 22: rp1-cfe-embedded (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- \"csi2\":5 [] - entity 26: rp1-cfe-csi2_ch2 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: Sink <- \"csi2\":6 [] - entity 30: rp1-cfe-csi2_ch3 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video3 pad0: Sink <- \"csi2\":7 [] - entity 34: rp1-cfe-fe_image0 (1 pad, 1 link) type Node subtype V4L flags 1 device node name /dev/video4 pad0: Sink <- \"pisp-fe\":2 [] - entity 38: rp1-cfe-fe_image1 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video5 pad0: Sink <- \"pisp-fe\":3 [] - entity 42: rp1-cfe-fe_stats (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video6 pad0: Sink <- \"pisp-fe\":4 [] - entity 46: rp1-cfe-fe_config (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video7 pad0: Source -> \"pisp-fe\":1 [] \u67e5\u8be2\u5f53\u524d\u8f93\u5165\u6e90\u4fe1\u606f,\u82e5\u5206\u8fa8\u7387\u663e\u793a0\u5219\u8868\u793a\u4e3a\u68c0\u67e5\u5230\u8f93\u5165\u6e90\u4fe1\u53f7\uff0c\u9700\u8981\u68c0\u67e5\u786c\u4ef6\u8fde\u63a5\u548c\u4e0a\u8ff0\u6b65\u9aa4\u6392\u67e5\u3002 blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --query-dv-timings Active width: 1920 Active height: 1080 Total width: 2750 Total height: 1125 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (24.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 830 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 45 Vertical backporch: 0 Standards: Flags: \u786e\u8ba4\u5f53\u524d\u8f93\u5165\u6e90\u4fe1\u606f blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --set-dv-bt-timings query BT timings set \u521d\u59cb\u5316media0 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -r \u628acsi2\u7684pad4\u8fde\u63a5\u5230rp1-cfe-csi2_ch0\u7684pad0 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -l ''\\''csi2'\\'':4 -> '\\''rp1-cfe-csi2_ch0'\\'':0 [1]' \u914d\u7f6emedia\u8282\u70b9 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':0 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':4 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' \u8bbe\u7f6e\u8f93\u51fa\u683c\u5f0f v4l2-ctl -v width=1920,height=1080,pixelformat=RGB3 \u91c7\u96c6\u4e24\u5e27\u753b\u9762\u7528\u4e8e\u6d4b\u8bd5tc358743\u662f\u5426\u53ef\u4ee5\u5de5\u4f5c\uff0c\u5176\u5b83\u5982\u4f7f\u7528gstreamer\u7684\u65b9\u6cd5\u6682\u65f6\u672a v4l2-ctl --verbose -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat='RGB3' --stream-mmap=4 --stream-skip=3 --stream-count=2 --stream-to=hdmiin.yuv --stream-poll Pi\u5982\u679c\u5b89\u88c5\u7684\u662f\u5e26\u684c\u9762\u7684\u7cfb\u7edf\uff0c\u53ef\u4ee5\u4f7f\u7528ffplay\u76f4\u63a5\u64ad\u653eyuv\u6587\u4ef6\u3002 ffplay -f rawvideo -video_size 1920x1080 -pixel_format bgr24 hdmiin.yuv windows\u7535\u8111\u53ef\u4ee5\u4f7f\u75287yuv\u7b49\u8f6f\u4ef6\u67e5\u770b.yuv\u6587\u4ef6\uff0c\u6559\u7a0b\u8f93\u5165\u683c\u5f0f\u4e3a1920 1080\uff0c\u6240\u4ee5\u57287yuv\u53f3\u4e0a\u89d2\u683c\u5f0f\u9009\u62e9BGR888\uff0c\u5206\u8fa8\u7387\u8bbe\u7f6e1920 1080\uff0c\u5373\u53ef\u770b\u5230\u4e24\u5e27\u521a\u91c7\u96c6\u5230\u7684\u753b\u9762 \u82af\u7247\u8d44\u6599 tc358743\u82af\u7247\u8d44\u6599 \u53d1\u8d27\u6e05\u5355 C790 \u6d4b\u8bd5\u89c6\u9891 C780A \u6d4b\u8bd5:https://www.youtube.com/watch?v=ecqyINoiHNQ C780B \u6d4b\u8bd5:https://www.youtube.com/watch?v=nc-hwPT2Uak&t=15s \u91c7\u8d2d\u8fde\u63a5 \u4e2d\u56fd\u5ba2\u6237\u91c7\u8d2d\u94fe\u63a5\uff1a C790 & C780 \u5176\u5b83\u56fd\u5bb6\u5ba2\u6237\u91c7\u8d2d\u8fde\u63a5\uff1a C779","title":"HDMI\u8f6cCSI & Audio\u6a21\u5757\u7528\u6237\u624b\u518c"},{"location":"hdmi-csi-i2s/#hdmicsii2s","text":"\u5c06HDMI\u4fe1\u53f7\u8f6c\u6362\u6210CSI\u89c6\u9891\u4fe1\u53f7\u548cI2S\u97f3\u9891\u4fe1\u53f7, \u76ee\u524d\u5168\u5e73\u53f0\u652f\u6301(zero, Pi3B, Pi4B, CM4, Pi5B),\u5176\u4e2d\u6700\u9ad8\u91c7\u96c6\u5206\u8fa8\u7387\u4e0d\u4ec5\u4ec5\u53d6\u51b3\u4e8eHDMI\u8f6cCSI\u8f6c\u6362\u677f\uff0c\u540c\u65f6\u4e5f\u53d6\u51b3\u4e8e\u4f60\u4f7f\u7528\u7684\u6811\u8393\u6d3e\u786c\u4ef6\u7248\u672c\uff0c\u6811\u8393\u6d3e\u786c\u4ef6\u7248\u76ee\u524d\u4e3b\u8981\u5206\u4e24\u4e2a\u7cfb\u5217\uff0c\u6700\u9ad8\u652f\u63011080P60Hz\uff0c\u548c\u6700\u9ad8\u652f\u63011080P50Hz\u3002 \u6700\u9ad8\u652f\u63011080P60Hz\u7684Pi\u7248\u672c(CM3\uff0cCM4\uff0cPi5B) \u6700\u9ad8\u652f\u63011080P50Hz\u7684Pi\u7248\u672c(zero, zero2, Pi3B, Pi4B\u7b49)","title":"HDMI\u8f6cCSI&I2S\u6a21\u5757\u624b\u518c"},{"location":"hdmi-csi-i2s/#_1","text":"\u6b64\u6a21\u5757\u5c06HDMI\u4fe1\u53f7\u8f6c\u6362\u6210CSI\u89c6\u9891\u4fe1\u53f7\u548cI2S\u97f3\u9891\u4fe1\u53f7\uff0c\u6700\u9ad8\u652f\u63011080P60Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u5728\u6811\u8393\u6d3e\u4e0a\u5de5\u4f5c\u7684\u5f88\u597d\uff0c\u76ee\u524d\u5171\u67093\u4e2a\u7248\u672c(C779\u3001C780\u3001C790). C790\u662f\u76ee\u524d\u6700\u65b0\u7684\u7248\u672c\uff0c\u89e3\u51b3\u4e86\u6240\u6709\u5df2\u77e5\u7684\u95ee\u9898\uff0c\u540c\u662f\u6709CSI 2\u901a\u9053\u548c4\u901a\u9053\u63a5\u53e3\uff0cI2S\u97f3\u9891\u63a5\u53e3\uff0c\u4fee\u590d\u4e86HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898\u3002","title":"\u7b80\u4ecb"},{"location":"hdmi-csi-i2s/#_2","text":"","title":"\u6027\u80fd\u53c2\u6570"},{"location":"hdmi-csi-i2s/#c790","text":"\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u5728\u6811\u8393\u6d3e\u4e0a\u6b64\u6a21\u5757\u6700\u9ad8\u652f\u63011080P60Hz\u8f93\u5165\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG 4\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f CSI-2\u63a5\u53e31: 15 pin FPC, \u95f4\u8ddd1.0 mm, \u5728C790\u6a21\u5757\u7684\u6b63\u9762. CSI-2\u63a5\u53e32, 22 pin FPC, \u95f4\u8ddd0.5 mm, \u5728C790\u6a21\u5757\u7684\u80cc\u9762. \u5c3a\u5bf8: 30 x 45 mm \u5b89\u88c5\u5b54\u4f4d:4 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u6811\u8393\u6d3e4B\u53ea\u652f\u63011080P50Hz(\u56e0\u4e3a4B\u53ea\u6709\u4e24\u4e2aCSI-2\u901a\u9053) ,\u6811\u8393\u6d3eCM4\u53ea\u652f\u63011080P60Hz,\u6240\u4ee5\u5982\u679c\u4f60\u7684\u8f93\u5165\u8bbe\u5907\u4e00\u5b9a\u8981\u662f1080P60Hz\uff0c\u8bf7\u540c\u65f6\u4f7f\u7528CM4\u548cC790. \u63a5\u53e3 C790\u6709\u4e24\u4e2aCSI\u8f93\u51fa\u63a5\u53e3: \u63a5\u53e31\uff0c\u5728C790\u6b63\u9762\uff0c15 pin FPC, \u95f4\u8ddd1.0 mm; \u63a5\u53e31\uff0c\u5728C790\u80cc\u9762,22 pin FPC, \u95f4\u8ddd0.5 mm\u3002 \u5c3a\u5bf8 \u5b89\u88c5\u53c2\u8003","title":"C790"},{"location":"hdmi-csi-i2s/#c780","text":"C780A\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P50Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 2\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 15 pin FPC, \u95f4\u8ddd 1.0 mm\uff1b \u5c3a\u5bf8: 30 x 65 mm (\u6298\u65ad\u524d); 30 x 45 mm (\u6298\u65ad\u540e) \u5b89\u88c5\u5b54\u4f4d:6 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g C780B\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P60Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 4\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 22 pin FPC, \u95f4\u8ddd 0.5 mm\uff1b \u5c3a\u5bf8: 30 x 65 mm (\u6298\u65ad\u524d); 30 x 45 mm (\u6298\u65ad\u540e) \u5b89\u88c5\u5b54\u4f4d:6 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u63a5\u53e3 \u97f3\u9891\u5f15\u811a\u5b9a\u4e49\u5982\u4e0b\u56fe\u6240\u793a: \u5c3a\u5bf8 \u5c3a\u5bf8\u5982\u4e0b\u56fe\u6240\u793a. \u67096\u4e2a\u76f4\u5f84\u4e3a2\u300275mm\u7684\u5b54\u4f4d\u7528\u4e8e\u5b89\u88c5\uff0c\u5b89\u88c5\u87ba\u9489\u53ef\u4ee5\u9009\u62e9M2.5\u3002 \u5982\u4e0b\u56fe\u6240\u793a\uff0cC780\u88ab\u8bbe\u8ba1\u6210\u53ef\u6298\u65ad\u5f0f\u7684\uff0cC780\u6a21\u5757\u5728\u672a\u88ab\u6298\u65ad\u524d\u53ef\u4ee5\u5b8c\u7f8e\u7684\u5b89\u88c5\u5728zero\u4e0a\u3002","title":"C780"},{"location":"hdmi-csi-i2s/#c779","text":"\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P50Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 2\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 15 pin FPC, \u95f4\u8ddd 1.0 mm\uff1b \u5c3a\u5bf8: 35 x 50 mm \u5b89\u88c5\u5b54\u4f4d:4 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u5c3a\u5bf8 \u5c3a\u5bf8\u5982\u4e0b\u56fe\u6240\u793a. \u67094\u4e2a\u76f4\u5f84\u4e3a2.75mm\u7684\u5b54\u4f4d\u7528\u4e8e\u5b89\u88c5\uff0c\u5b89\u88c5\u87ba\u9489\u53ef\u4ee5\u9009\u62e9M2.5\u3002","title":"C779"},{"location":"hdmi-csi-i2s/#csi","text":"\u5176\u4e2dC779\uff0cC780A\u53ea\u670915PIN\u5f15\u811a\uff0cC780B\u53ea\u670922PIN\u5f15\u811a\uff0cC790\u540c\u65f6\u670915\u548c22PIN\u5f15\u811a\u3002","title":"CSI\u63a5\u53e3\u5b9a\u4e49"},{"location":"hdmi-csi-i2s/#demo","text":"\u4e0b\u6587\u4e2d\u7684\u8f6f\u4ef6\u4f7f\u7528\u65b9\u6cd5\u8ddf\u4f60\u4f7f\u7528\u7684\u6811\u8393\u6d3e\u955c\u50cf\u7248\u672c\u6709\u5173\uff0c\u53ef\u80fd\u5b58\u5728\u4e0d\u540c\u3002\u5982\u679c\u4f60\u6709\u4efb\u4f55\u7591\u95ee\uff0c\u8bf7\u52a0\u5165 BLIKVM Discord \u793e\u533a \u83b7\u5f97\u652f\u6301\u3001\u89e3\u7b54\u548c\u65b0\u95fb\u3002 \u4ee5\u4e0b\u8bf4\u660e\u9002\u7528\u4e8e\u5185\u6838\u4e3a5.4\u6216\u8005\u66f4\u9ad8\u7248\u672c\u3002\u5982\u679c\u4f60\u7684\u6811\u8393\u6d3e\u955c\u50cf\u4f4e\u4e8e\u6b64\u7248\u672c\uff0c\u8bf7\u5347\u7ea7\u3002\u7ec8\u7aef\u4f7f\u7528\u4f7f\u7528\u201cuname-a\u201d\u53ef\u4ee5\u67e5\u770b\u4f60\u7cfb\u7edf\u7684\u5185\u6838\u7248\u672c\u3002 pi@raspberrypi:~ $ uname -a Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. \u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u8fdb\u884c\u5347\u7ea7 (\u4e0d\u662f\u5fc5\u987b\u7684\uff0c\u5728\u67d0\u4e9b\u56fd\u5bb6\u8fd9\u4e2a\u82b1\u8d39\u7684\u65f6\u95f4\u53ef\u80fd\u5f88\u957f) sudo apt-get update sudo apt-get upgrade 2. \u4f7f\u80fd\u76f8\u673a\u6a21\u5757(\u5728\u6811\u8393\u6d3eBullseys OS\u7cfb\u7edf\u4e2d\uff0c\u76f8\u673a\u5df2\u9ed8\u8ba4\u88ab\u4f7f\u80fd) sudo raspi-config sudo reboot \u79fb\u52a8\u5149\u6807\u5230\u2018Interfacing Options\u2019\uff0c\u7136\u540e\u6309Enter\u952e\u8fdb\u5165\u3002\u7136\u540e\u9009\u62e9\u2018Camera\u2019\u9009\u9879\uff0c\u6309Enter\u952e\u8fdb\u5165\u540e\uff0c\u4f7f\u80fd\u76f8\u673a\u3002\u7136\u540e\u9009\u62e9\u201cFinish\u201d\u540e\uff0c \u9009\u62e9\u201creboot\u201d\u3002 \u91cd\u542f\u975e\u5e38\u91cd\u8981!! \u7531\u4e8ePi5B\u53d6\u6d88\u4e86\u786c\u7f16\u7801\u5668\uff0c\u4e0b\u9762\u8f6f\u4ef6\u4f7f\u7528\u65b9\u6cd5\u5728Pi\u5e73\u53f0\u76ee\u524d\u5206\u4e3a\u4e24\u4e2a\u90e8\u5206\uff0cPi5B\u914d\u7f6e\uff0c\u548c\u5176\u5b83Pi\u5e73\u53f0\u914d\u7f6e\u3002 \u5728zero, zero2,Pi3B,Pi4B\u7b49\u5e73\u53f0HDMI\u8f6cCSI\u6a21\u5757\u6d4b\u8bd5demo\u53c2\u8003 \u7f16\u8f91 /boot/config.txt (\u9700\u8981sudo\u6743\u9650) sudo nano /boot/config.txt \u6dfb\u52a0\u4e0b\u9762\u7684\u5185\u5bb9 dtoverlay=tc358743 \u5982\u679c\u4f60\u7684\u6a21\u5757(C780\u548cC790)\u652f\u6301\u58f0\u97f3\uff0c\u6dfb\u52a0\u4e0b\u9762\u5185\u5bb9\u652f\u6301\u58f0\u97f3 dtoverlay=tc358743-audio \u5982\u679c\u4f60\u662f\u7528\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u7ec4(CM3\u3001CM4)\uff0c\u53ef\u4ee5\u901a\u8fc7\u4e0b\u5217\u914d\u7f6e\uff0c\u4f7f\u80fdCSI\u76844\u4e2a\u901a\u9053\u3002 dtoverlay=tc358743,4lane=1 \u4f7f\u7528\u201cdmesg | grep cma\u201d\u68c0\u67e5\u5206\u914d\u7ed9CMA\u5806\u7684\u5185\u5b58\u91cf\uff0c\u7ec8\u7aef\u51fa\u73b0\u7684\u7b2c\u4e00\u884c\u5185\u5bb9\u5e94\u8be5\u5982\u4e0b\u6240\u793a: pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 \u5982\u679c\u663e\u793a\u5c11\u4e8e96MB\uff0c\u7f16\u8f91/boot/cmdline.txt\uff0c\u6dfb\u52a0\u4e0b\u9762\u4e00\u884c\u3002 cma=96M \u91cd\u542f\u6811\u8393\u6d3e\uff0c\u5982\u679c\u914d\u7f6e\u6210\u529f\uff0c\u4f60\u5c06\u4f1a\u770b\u5230/dev/video0\u8bbe\u5907\u63cf\u8ff0\u7b26\u51fa\u73b0\u3002\u53ef\u4ee5\u4f7f\u7528\u201cv4l2-ctl \u2013list-devices\u201d \u547d\u4ee4\u5217\u51fa\u6240\u6709\u7684video\u63cf\u8ff0\u7b26\u3002\u518d\u5c06\u6811\u8393\u6d3e\u4e0e\u6a21\u5757\u6b63\u786e\u8fde\u63a5\u540e\uff0c\u6811\u8393\u6d3e\u4e0a\u7535\uff0c\u4f60\u53ef\u4ee5\u770b\u5230C790\u6a21\u5757\u4e0a\u6709\u4e00\u4e2a\u7eff\u8272\u706f\u5e38\u4eae\uff0c\u7136\u540e\u53ef\u4ee5\u6309\u7167\u4e0b\u9762\u7684\u547d\u4ee4\uff0c\u68c0\u67e5\u662f\u5426\u5df2\u7ecf\u6b63\u5e38\u51fa\u73b0\u4e86video0\u3002 pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 \u9ed8\u8ba4\u6ca1\u6709\u52a0\u8f7dEDID,\u5982\u679c\u4f60\u6709EDID\u7f16\u8f91\u5668\uff0c\u4f60\u53ef\u4ee5\u81ea\u5df1\u7f16\u8f91\u4f60\u6240\u9700\u8981\u7684\u5206\u8fa8\u7387\uff0c\u6216\u8005\u4f7f\u7528\u4e0b\u9762\u63d0\u4f9b\u7684EDID\u5206\u8fa8\u7387\uff08720p60hz\uff09\u3002 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt # \u62f7\u8d1d\u4e0a\u95e8\u7684\u5185\u5bb9\u5230edid.txt\u6587\u4ef6\u4e2d\uff0c\u7136\u540e\u4fdd\u5b58\u9000\u51fa\u3002\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u8bbe\u7f6e\u52a0\u8f7dedid\uff0c\u5982\u679c\u6b63\u786e\u8bbe\u7f6e\uff0c\u53ef\u4ee5\u770b\u5230\u5982\u4e0b\u7684\u8f93\u51fa\u3002 pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan \u9a71\u52a8\u7a0b\u5e8f\u4e0d\u4f1a\u81ea\u52a8\u5207\u6362\u5230\u68c0\u6d4b\u5230\u7684\u5206\u8fa8\u7387\u3002\u662f\u7528\u4e0b\u5217\u547d\u4ee4\u68c0\u67e5\u76ee\u524dHDMI\u7684\u8f93\u5165 pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: \u4f60\u5fc5\u987b\u4f7f\u7528\u201cv4l2-ctl \u2013set-dv-bt-timings\u201d\u547d\u4ee4\u8bbe\u7f6e\u9a71\u52a8\u7a0b\u5e8f\u4f7f\u7528\u76ee\u524d\u7684\u8f93\u5165\u5206\u8fa8\u7387 v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. \u82af\u7247\u652f\u6301\u4e24\u79cd\u683c\u5f0f(BGR3\u548cUYVY)\uff0cBGR3\u50cf\u7d20\u6df1\u5ea6\u4e3a24bpp\uff0cUYVY\u4e3aYUV4:2:2 16bpp\u3002\u5982\u679c\u4f7f\u7528CSI 2\u901a\u9053\uff0cBGR3\u683c\u5f0f\u6700\u5927\u652f\u63011080P30Hz\u7684\u8f93\u5165\uff0c\u4f7f\u7528UYVY\u5219\u6700\u5927\u652f\u63011080P60Hz\u7684\u8f93\u5165\u3002\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u8bbe\u7f6e\u4e3aUYVY\u683c\u5f0f\u3002 v4l2-ctl -v pixelformat=UYVY \u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\uff0c\u68c0\u67e5\u97f3\u9891\u786c\u4ef6\u548c\u9a71\u52a8\u662f\u5426\u6b63\u5e38\u3002 pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1: tc358743\u610f\u5473\u7740\u97f3\u9891\u76f8\u5173\u786c\u4ef6\u5df2\u88ab\u6b63\u786e\u52a0\u8f7d\uff0c\u6ce8\u610f\u8fd9\u91cc\u76841\u53ef\u80fd\u4e0d\u540c\u3002 \u5b89\u88c5GStreamer\u5de5\u5177. sudo apt install gstreamer1.0-tools sudo apt-get install gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-plugins-bad sudo apt-get install gstreamer1.0-plugins-base \u68c0\u67e5gstreamer\u5de5\u5177\u7248\u672c: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note:\u4e0d\u540c\u7684\u7248\u672c\u8fd9\u91cc\u8f93\u51fa\u53ef\u80fd\u4e0d\u540c. \u4f7f\u7528gstreamer\u53bb\u5f55\u5236\u89c6\u9891\u6216\u8005\u58f0\u97f3 #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. \u4f60\u4f1a\u5f97\u5230\u4e00\u4e2afoo.mkv\u6587\u4ef6. \u5982\u679c\u4f60\u7684gstreamer\u662f1.8\u6216\u8005\u66f4\u9ad8\u7248\u672c\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u3002\u5176\u4e2ddevice=hw:1\u8868\u793a\u7684\u662fTC358743\u58f0\u5361\u3002 #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: \u8fd9\u91cc\u6211\u4eec\u5efa\u8bae\u4f60\u4f7f\u7528\u5b9e\u9645\u7684\u8f93\u5165\u5e27\u7387\u53bb\u91c7\u96c6HDMI\u4fe1\u53f7\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528 \u2018v4l2-ctl \u2013query-dv-timings\u2019\u53bb\u68c0\u67e5\u5b9e\u9645\u8f93\u5165\u5e27\u7387\u3002 \u5982\u4e0a\u56fe\u4e2d\u7684HDMI\u8f93\u5165\u8bbe\u5907\uff0c\u5e27\u7387\u662f60Hz\uff0c\u6240\u4ee5\u6211\u4eec\u53ef\u4ee5\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u53bb\u5f55\u5236\u89c6\u9891\uff1a gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv \u5f55\u5236\u89c6\u9891\u548c\u97f3\u9891: (\u5982\u679c\u4f60\u7684\u8bbe\u5907\u652f\u6301\u97f3\u9891\u7684\u8bdd) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9) Pi5B\u7b49\u5e73\u53f0HDMI\u8f6cCSI\u6a21\u5757\u6d4b\u8bd5demo\u53c2\u8003 \u4e0b\u9762\u6d4b\u8bd5\u4e2d\uff0c\u4f7f\u7528cam1\u901a\u9053\u8fdb\u884c\u6d4b\u8bd5\uff0c\u6d4b\u8bd5\u8f93\u5165\u5206\u8fa8\u7387\u4e3a1080P24Hz\u3002\u6811\u8393\u6d3e5b\u6d4b\u8bd5\u8fc7\u7a0b\u4e2d\u53d1\u73b0edid\u8bbe\u7f6e\u65e0\u6548\uff0c\u56e0\u6b64\u9700\u8981\u901a\u8fc7\u6dfb\u52a0HDMI\u8bf1\u9a97\u5668\u6765\u5f3a\u5236\u76ee\u6807\u8bbe\u7f6e\u8f93\u51faHDMI\uff0c\u5426\u5219\u6811\u8393\u6d3e5b\u5f88\u6709\u53ef\u80fd\u83b7\u53d6\u4e0d\u5230\u4efb\u4f55\u8f93\u5165\u3002\u7531\u4e8e\u6811\u8393\u6d3e5b\u6ca1\u6709\u5bf9\u5e94\u7684\u786c\u7f16\u7801\u786c\u4ef6\uff0c\u6240\u4ee5\u6811\u8393\u6d3e5b+C790\u56fe\u50cf\u91c7\u96c6\u80fd\u529b\u6027\u80fd\u4e00\u822c\uff0c\u4e0d\u5982\u7528\u6811\u8393\u6d3e4b \u7f16\u8f91 /boot/config.txt (\u9700\u8981sudo\u6743\u9650) sudo nano /boot/config.txt \u6dfb\u52a0\u4e0b\u9762\u7684\u5185\u5bb9 dtoverlay=tc358743 \u5982\u679c\u4f60\u7684\u6a21\u5757(C780\u548cC790)\u652f\u6301\u58f0\u97f3\uff0c\u6dfb\u52a0\u4e0b\u9762\u5185\u5bb9\u652f\u6301\u58f0\u97f3 dtoverlay=tc358743-audio \u91cd\u542f\u6811\u8393\u6d3e,\u6267\u884c\u4e0b\u9762\u6307\u4ee4\uff0c\u627e\u5230csi\u5bf9\u5e94\u7684media\u8282\u70b9\u4e3amedia0,\u5373rp1-cfe (platform:1f00128000.csi)\u5b57\u6bb5\u4e0b\u7684media\u8bbe\u5907: blikvm@blikvm:~ $ v4l2-ctl --list-devices pispbe (platform:1000880000.pisp_be): /dev/video20 /dev/video21 /dev/video22 /dev/video23 /dev/video24 /dev/video25 /dev/video26 /dev/video27 /dev/video28 /dev/video29 /dev/video30 /dev/video31 /dev/video32 /dev/video33 /dev/video34 /dev/video35 /dev/video36 /dev/video37 /dev/media1 /dev/media2 rp1-cfe (platform:1f00128000.csi): /dev/video0 /dev/video1 /dev/video2 /dev/video3 /dev/video4 /dev/video5 /dev/video6 /dev/video7 /dev/media0 rpivid (platform:rpivid): /dev/video19 /dev/media3 \u627e\u5230tc358743\u5bf9\u5e94\u8282\u70b9\u4e3av4l-subdev2\uff0crp1-cfe-csi2_ch0\u7684pad0\u4e3avideo0: blikvm@blikvm:~ $ media-ctl -d /dev/media0 -p Media controller API version 6.1.63 Media device information ------------------------ driver rp1-cfe model rp1-cfe serial bus info platform:1f00128000.csi hw revision 0x114666 driver version 6.1.63 Device topology - entity 1: csi2 (8 pads, 8 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"tc358743 4-000f\":0 [ENABLED,IMMUTABLE] pad1: Sink [fmt:unknown/8192x1 field:none] pad2: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad3: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad4: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch0\":0 [] -> \"pisp-fe\":0 [] pad5: Source [fmt:unknown/8192x1 field:none] -> \"rp1-cfe-embedded\":0 [] pad6: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch2\":0 [] -> \"pisp-fe\":0 [] pad7: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch3\":0 [] -> \"pisp-fe\":0 [] - entity 10: pisp-fe (5 pads, 7 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: Sink [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"csi2\":4 [] <- \"csi2\":6 [] <- \"csi2\":7 [] pad1: Sink [fmt:FIXED/8192x1 field:none] <- \"rp1-cfe-fe_config\":0 [] pad2: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image0\":0 [] pad3: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image1\":0 [] pad4: Source [fmt:FIXED/8192x1 field:none] -> \"rp1-cfe-fe_stats\":0 [] - entity 16: tc358743 4-000f (1 pad, 1 link) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev2 pad0: Source [fmt:RGB888_1X24/640x480 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:640x350@13000000 max:1920x1200@165000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom] [dv.detect:BT.656/1120 1920x1080p24 (2750x1125) stds: flags:] [dv.current:BT.656/1120 640x480p59 (800x525) stds:CEA-861,DMT flags:has-cea861-vic] -> \"csi2\":0 [ENABLED,IMMUTABLE] - entity 18: rp1-cfe-csi2_ch0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 pad0: Sink <- \"csi2\":4 [] - entity 22: rp1-cfe-embedded (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- \"csi2\":5 [] - entity 26: rp1-cfe-csi2_ch2 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: Sink <- \"csi2\":6 [] - entity 30: rp1-cfe-csi2_ch3 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video3 pad0: Sink <- \"csi2\":7 [] - entity 34: rp1-cfe-fe_image0 (1 pad, 1 link) type Node subtype V4L flags 1 device node name /dev/video4 pad0: Sink <- \"pisp-fe\":2 [] - entity 38: rp1-cfe-fe_image1 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video5 pad0: Sink <- \"pisp-fe\":3 [] - entity 42: rp1-cfe-fe_stats (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video6 pad0: Sink <- \"pisp-fe\":4 [] - entity 46: rp1-cfe-fe_config (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video7 pad0: Source -> \"pisp-fe\":1 [] \u67e5\u8be2\u5f53\u524d\u8f93\u5165\u6e90\u4fe1\u606f,\u82e5\u5206\u8fa8\u7387\u663e\u793a0\u5219\u8868\u793a\u4e3a\u68c0\u67e5\u5230\u8f93\u5165\u6e90\u4fe1\u53f7\uff0c\u9700\u8981\u68c0\u67e5\u786c\u4ef6\u8fde\u63a5\u548c\u4e0a\u8ff0\u6b65\u9aa4\u6392\u67e5\u3002 blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --query-dv-timings Active width: 1920 Active height: 1080 Total width: 2750 Total height: 1125 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (24.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 830 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 45 Vertical backporch: 0 Standards: Flags: \u786e\u8ba4\u5f53\u524d\u8f93\u5165\u6e90\u4fe1\u606f blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --set-dv-bt-timings query BT timings set \u521d\u59cb\u5316media0 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -r \u628acsi2\u7684pad4\u8fde\u63a5\u5230rp1-cfe-csi2_ch0\u7684pad0 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -l ''\\''csi2'\\'':4 -> '\\''rp1-cfe-csi2_ch0'\\'':0 [1]' \u914d\u7f6emedia\u8282\u70b9 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':0 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':4 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' \u8bbe\u7f6e\u8f93\u51fa\u683c\u5f0f v4l2-ctl -v width=1920,height=1080,pixelformat=RGB3 \u91c7\u96c6\u4e24\u5e27\u753b\u9762\u7528\u4e8e\u6d4b\u8bd5tc358743\u662f\u5426\u53ef\u4ee5\u5de5\u4f5c\uff0c\u5176\u5b83\u5982\u4f7f\u7528gstreamer\u7684\u65b9\u6cd5\u6682\u65f6\u672a v4l2-ctl --verbose -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat='RGB3' --stream-mmap=4 --stream-skip=3 --stream-count=2 --stream-to=hdmiin.yuv --stream-poll Pi\u5982\u679c\u5b89\u88c5\u7684\u662f\u5e26\u684c\u9762\u7684\u7cfb\u7edf\uff0c\u53ef\u4ee5\u4f7f\u7528ffplay\u76f4\u63a5\u64ad\u653eyuv\u6587\u4ef6\u3002 ffplay -f rawvideo -video_size 1920x1080 -pixel_format bgr24 hdmiin.yuv windows\u7535\u8111\u53ef\u4ee5\u4f7f\u75287yuv\u7b49\u8f6f\u4ef6\u67e5\u770b.yuv\u6587\u4ef6\uff0c\u6559\u7a0b\u8f93\u5165\u683c\u5f0f\u4e3a1920 1080\uff0c\u6240\u4ee5\u57287yuv\u53f3\u4e0a\u89d2\u683c\u5f0f\u9009\u62e9BGR888\uff0c\u5206\u8fa8\u7387\u8bbe\u7f6e1920 1080\uff0c\u5373\u53ef\u770b\u5230\u4e24\u5e27\u521a\u91c7\u96c6\u5230\u7684\u753b\u9762","title":"\u8f6f\u4ef6\u4f7f\u7528demo"},{"location":"hdmi-csi-i2s/#_3","text":"tc358743\u82af\u7247\u8d44\u6599","title":"\u82af\u7247\u8d44\u6599"},{"location":"hdmi-csi-i2s/#_4","text":"C790","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"hdmi-csi-i2s/#_5","text":"C780A \u6d4b\u8bd5:https://www.youtube.com/watch?v=ecqyINoiHNQ C780B \u6d4b\u8bd5:https://www.youtube.com/watch?v=nc-hwPT2Uak&t=15s","title":"\u6d4b\u8bd5\u89c6\u9891"},{"location":"hdmi-csi-i2s/#_6","text":"\u4e2d\u56fd\u5ba2\u6237\u91c7\u8d2d\u94fe\u63a5\uff1a C790 & C780 \u5176\u5b83\u56fd\u5bb6\u5ba2\u6237\u91c7\u8d2d\u8fde\u63a5\uff1a C779","title":"\u91c7\u8d2d\u8fde\u63a5"},{"location":"hid/","text":"\u89c6\u9891 \u952e\u76d8 \u9f20\u6807 \u5feb\u6377\u952e \u5728v1.4.5\u7248\u672c\u540e\uff0c\u652f\u6301\u81ea\u5b9a\u4e49\u5feb\u6377\u952e,\u627e\u5230shortcuts\u914d\u7f6e\u9879\u76ee, \u5176\u4e2dkey\u4e3aweb ui\u4e0a\u7684\u6309\u94ae\u540d\u79f0\uff0cvalue\u4e3a\u5177\u4f53\u7684\u6309\u952e\u3002 sudo -s vim /mnt/exec/release/config/app.json ## \u9ed8\u8ba4\u914d\u7f6e\u5982\u4e0b\uff1a \"shortcuts\": { \"Ctrl+Alt+Del\": [\"ControlLeft\",\"AltLeft\",\"Delete\"], \"Alt+Tab\": [\"AltLeft\",\"Tab\"], \"Alt+F4\": [\"AltLeft\",\"F4\"], \"Alt+Enter\": [\"AltLeft\",\"Enter\"], \"Ctrl+W\": [\"ControlLeft\",\"KeyW\"] } \u5176\u4e2d\u6309\u952e\u540d\u79f0\u5177\u6709\u552f\u4e00\u6027\uff0c\u4e0b\u9762\u63d0\u4f9b\u5177\u4f53\u7684\u6309\u952e\u540d\u79f0 \"{backspace}\": \"Backspace\", \"{tab}\": \"Tab\", \"{enter}\": \"Enter\", \"{shiftleft}\": \"ShiftLeft\", \"{shiftright}\": \"ShiftRight\", \"{altleft}\": \"AltLeft\", \"{altright}\": \"AltRight\", \"{prtscr}\": \"PrtScr\", \"{pause}\": \"Pause\", \"{scrolllock}\": \"ScrollLock\", \"{controlleft}\": \"ControlLeft\", \"{controlright}\": \"ControlRight\", \"{metaleft}\": \"MetaLeft\", \"{metaright}\": \"MetaRight\", \"{capslock}\": \"CapsLock\", \"{escape}\": \"Escape\", \"{space}\": \"Space\", \"{pageup}\": \"PageUp\", \"{pagedown}\": \"PageDown\", \"{end}\": \"End\", \"{home}\": \"Home\", \"{arrowleft}\": \"ArrowLeft\", \"{arrowup}\": \"ArrowUp\", \"{arrowright}\": \"ArrowRight\", \"{arrowdown}\": \"ArrowDown\", \"{insert}\": \"Insert\", \"{delete}\": \"Delete\", // Digits keys 1: \"Digit1\", 2: \"Digit2\", 3: \"Digit3\", 4: \"Digit4\", 5: \"Digit5\", 6: \"Digit6\", 7: \"Digit7\", 8: \"Digit8\", 9: \"Digit9\", 0: \"Digit0\", // \"!\": \"Digit1\", // ! maps to the '1' key \"@\": \"Digit2\", // @ maps to the '2' key \"#\": \"Digit3\", // # maps to the '3' key $: \"Digit4\", // $ maps to the '4' key \"%\": \"Digit5\", // % maps to the '5' key \"^\": \"Digit6\", // ^ maps to the '6' key \"&\": \"Digit7\", // & maps to the '7' key \"*\": \"Digit8\", // * maps to the '8' key \"(\": \"Digit9\", // ( maps to the '9' key \")\": \"Digit0\", // ) maps to the '0' key a: \"KeyA\", b: \"KeyB\", c: \"KeyC\", d: \"KeyD\", e: \"KeyE\", f: \"KeyF\", g: \"KeyG\", h: \"KeyH\", i: \"KeyI\", j: \"KeyJ\", k: \"KeyK\", l: \"KeyL\", m: \"KeyM\", n: \"KeyN\", o: \"KeyO\", p: \"KeyP\", q: \"KeyQ\", r: \"KeyR\", s: \"KeyS\", t: \"KeyT\", u: \"KeyU\", v: \"KeyV\", w: \"KeyW\", x: \"KeyX\", y: \"KeyY\", z: \"KeyZ\", // A: \"KeyA\", B: \"KeyB\", C: \"KeyC\", D: \"KeyD\", E: \"KeyE\", F: \"KeyF\", G: \"KeyG\", H: \"KeyH\", I: \"KeyI\", J: \"KeyJ\", K: \"KeyK\", L: \"KeyL\", M: \"KeyM\", N: \"KeyN\", O: \"KeyO\", P: \"KeyP\", Q: \"KeyQ\", R: \"KeyR\", S: \"KeyS\", T: \"KeyT\", U: \"KeyU\", V: \"KeyV\", W: \"KeyW\", X: \"KeyX\", Y: \"KeyY\", Z: \"KeyZ\", \"-\": \"Minus\", _: \"Minus\", \"=\": \"Equal\", \"+\": \"Equal\", \"[\": \"BracketLeft\", \"{\": \"BracketLeft\", \"]\": \"BracketRight\", \"}\": \"BracketRight\", \"|\": \"Backslash\", \"\\\\\": \"Backslash\", \"`\": \"Backquote\", \"~\": \"Backquote\", \";\": \"Semicolon\", \":\": \"Semicolon\", \"'\": \"Quote\", '\"': \"Quote\", \",\": \"Comma\", \"<\": \"Comma\", \".\": \"Period\", \">\": \"Period\", \"/\": \"Slash\", \"?\": \"Slash\", // Numpad keys \"{numpad0}\": \"Numpad0\", \"{numpad1}\": \"Numpad1\", \"{numpad2}\": \"Numpad2\", \"{numpad3}\": \"Numpad3\", \"{numpad4}\": \"Numpad4\", \"{numpad5}\": \"Numpad5\", \"{numpad6}\": \"Numpad6\", \"{numpad7}\": \"Numpad7\", \"{numpad8}\": \"Numpad8\", \"{numpad9}\": \"Numpad9\", \"{numlock}\": \"numlock\", \"{numpadmultiply}\": \"NumpadMultiply\", \"{numpadadd}\": \"NumpadAdd\", \"{numpadsubtract}\": \"NumpadSubtract\", \"{numpaddecimal}\": \"NumpadDecimal\", \"{numpaddivide}\": \"NumpadDivide\", \"{numpadenter}\": \"NumpadEnter\", // Function keys \"{f1}\": \"F1\", \"{f2}\": \"F2\", \"{f3}\": \"F3\", \"{f4}\": \"F4\", \"{f5}\": \"F5\", \"{f6}\": \"F6\", \"{f7}\": \"F7\", \"{f8}\": \"F8\", \"{f9}\": \"F9\", \"{f10}\": \"F10\", \"{f11}\": \"F11\", \"{f12}\": \"F12\"","title":"\u89c6\u9891&\u952e\u9f20"},{"location":"hid/#_1","text":"","title":"\u89c6\u9891 \u952e\u76d8 \u9f20\u6807"},{"location":"hid/#_2","text":"\u5728v1.4.5\u7248\u672c\u540e\uff0c\u652f\u6301\u81ea\u5b9a\u4e49\u5feb\u6377\u952e,\u627e\u5230shortcuts\u914d\u7f6e\u9879\u76ee, \u5176\u4e2dkey\u4e3aweb ui\u4e0a\u7684\u6309\u94ae\u540d\u79f0\uff0cvalue\u4e3a\u5177\u4f53\u7684\u6309\u952e\u3002 sudo -s vim /mnt/exec/release/config/app.json ## \u9ed8\u8ba4\u914d\u7f6e\u5982\u4e0b\uff1a \"shortcuts\": { \"Ctrl+Alt+Del\": [\"ControlLeft\",\"AltLeft\",\"Delete\"], \"Alt+Tab\": [\"AltLeft\",\"Tab\"], \"Alt+F4\": [\"AltLeft\",\"F4\"], \"Alt+Enter\": [\"AltLeft\",\"Enter\"], \"Ctrl+W\": [\"ControlLeft\",\"KeyW\"] } \u5176\u4e2d\u6309\u952e\u540d\u79f0\u5177\u6709\u552f\u4e00\u6027\uff0c\u4e0b\u9762\u63d0\u4f9b\u5177\u4f53\u7684\u6309\u952e\u540d\u79f0 \"{backspace}\": \"Backspace\", \"{tab}\": \"Tab\", \"{enter}\": \"Enter\", \"{shiftleft}\": \"ShiftLeft\", \"{shiftright}\": \"ShiftRight\", \"{altleft}\": \"AltLeft\", \"{altright}\": \"AltRight\", \"{prtscr}\": \"PrtScr\", \"{pause}\": \"Pause\", \"{scrolllock}\": \"ScrollLock\", \"{controlleft}\": \"ControlLeft\", \"{controlright}\": \"ControlRight\", \"{metaleft}\": \"MetaLeft\", \"{metaright}\": \"MetaRight\", \"{capslock}\": \"CapsLock\", \"{escape}\": \"Escape\", \"{space}\": \"Space\", \"{pageup}\": \"PageUp\", \"{pagedown}\": \"PageDown\", \"{end}\": \"End\", \"{home}\": \"Home\", \"{arrowleft}\": \"ArrowLeft\", \"{arrowup}\": \"ArrowUp\", \"{arrowright}\": \"ArrowRight\", \"{arrowdown}\": \"ArrowDown\", \"{insert}\": \"Insert\", \"{delete}\": \"Delete\", // Digits keys 1: \"Digit1\", 2: \"Digit2\", 3: \"Digit3\", 4: \"Digit4\", 5: \"Digit5\", 6: \"Digit6\", 7: \"Digit7\", 8: \"Digit8\", 9: \"Digit9\", 0: \"Digit0\", // \"!\": \"Digit1\", // ! maps to the '1' key \"@\": \"Digit2\", // @ maps to the '2' key \"#\": \"Digit3\", // # maps to the '3' key $: \"Digit4\", // $ maps to the '4' key \"%\": \"Digit5\", // % maps to the '5' key \"^\": \"Digit6\", // ^ maps to the '6' key \"&\": \"Digit7\", // & maps to the '7' key \"*\": \"Digit8\", // * maps to the '8' key \"(\": \"Digit9\", // ( maps to the '9' key \")\": \"Digit0\", // ) maps to the '0' key a: \"KeyA\", b: \"KeyB\", c: \"KeyC\", d: \"KeyD\", e: \"KeyE\", f: \"KeyF\", g: \"KeyG\", h: \"KeyH\", i: \"KeyI\", j: \"KeyJ\", k: \"KeyK\", l: \"KeyL\", m: \"KeyM\", n: \"KeyN\", o: \"KeyO\", p: \"KeyP\", q: \"KeyQ\", r: \"KeyR\", s: \"KeyS\", t: \"KeyT\", u: \"KeyU\", v: \"KeyV\", w: \"KeyW\", x: \"KeyX\", y: \"KeyY\", z: \"KeyZ\", // A: \"KeyA\", B: \"KeyB\", C: \"KeyC\", D: \"KeyD\", E: \"KeyE\", F: \"KeyF\", G: \"KeyG\", H: \"KeyH\", I: \"KeyI\", J: \"KeyJ\", K: \"KeyK\", L: \"KeyL\", M: \"KeyM\", N: \"KeyN\", O: \"KeyO\", P: \"KeyP\", Q: \"KeyQ\", R: \"KeyR\", S: \"KeyS\", T: \"KeyT\", U: \"KeyU\", V: \"KeyV\", W: \"KeyW\", X: \"KeyX\", Y: \"KeyY\", Z: \"KeyZ\", \"-\": \"Minus\", _: \"Minus\", \"=\": \"Equal\", \"+\": \"Equal\", \"[\": \"BracketLeft\", \"{\": \"BracketLeft\", \"]\": \"BracketRight\", \"}\": \"BracketRight\", \"|\": \"Backslash\", \"\\\\\": \"Backslash\", \"`\": \"Backquote\", \"~\": \"Backquote\", \";\": \"Semicolon\", \":\": \"Semicolon\", \"'\": \"Quote\", '\"': \"Quote\", \",\": \"Comma\", \"<\": \"Comma\", \".\": \"Period\", \">\": \"Period\", \"/\": \"Slash\", \"?\": \"Slash\", // Numpad keys \"{numpad0}\": \"Numpad0\", \"{numpad1}\": \"Numpad1\", \"{numpad2}\": \"Numpad2\", \"{numpad3}\": \"Numpad3\", \"{numpad4}\": \"Numpad4\", \"{numpad5}\": \"Numpad5\", \"{numpad6}\": \"Numpad6\", \"{numpad7}\": \"Numpad7\", \"{numpad8}\": \"Numpad8\", \"{numpad9}\": \"Numpad9\", \"{numlock}\": \"numlock\", \"{numpadmultiply}\": \"NumpadMultiply\", \"{numpadadd}\": \"NumpadAdd\", \"{numpadsubtract}\": \"NumpadSubtract\", \"{numpaddecimal}\": \"NumpadDecimal\", \"{numpaddivide}\": \"NumpadDivide\", \"{numpadenter}\": \"NumpadEnter\", // Function keys \"{f1}\": \"F1\", \"{f2}\": \"F2\", \"{f3}\": \"F3\", \"{f4}\": \"F4\", \"{f5}\": \"F5\", \"{f6}\": \"F6\", \"{f7}\": \"F7\", \"{f8}\": \"F8\", \"{f9}\": \"F9\", \"{f10}\": \"F10\", \"{f11}\": \"F11\", \"{f12}\": \"F12\"","title":"\u5feb\u6377\u952e"},{"location":"https/","text":"\u52a0\u5bc6\u8bc1\u4e66 blikvm v1.4.9\u7248\u672c\u540e,\u9ed8\u8ba4\u4e3ahttps\u542f\u52a8\uff0c\u5373\u4f7f\u8bbf\u95eehttp\u4e5f\u4f1a\u81ea\u52a8\u88ab\u91cd\u5b9a\u5411\u5230https: sudo -s vim /mnt/exec/release/config/app.json \u627e\u5230\u4e0b\u9762\u914d\u7f6e\u5185\u5bb9\uff0c\u5176\u4e2dkey\u548ccert\u5728 /mnt/exec/release/lib/https/ \u6b64\u8def\u5f84\uff0c\u7528\u6237\u53ef\u4ee5\u81ea\u5df1\u8fdb\u884c\u66ff\u6362\u3002 \"server\": { \"ssl\": { \"key\": \"./lib/https/key.pem\", \"cert\": \"./lib/https/cert.pem\" }","title":"\u52a0\u5bc6\u8bc1\u4e66"},{"location":"https/#_1","text":"blikvm v1.4.9\u7248\u672c\u540e,\u9ed8\u8ba4\u4e3ahttps\u542f\u52a8\uff0c\u5373\u4f7f\u8bbf\u95eehttp\u4e5f\u4f1a\u81ea\u52a8\u88ab\u91cd\u5b9a\u5411\u5230https: sudo -s vim /mnt/exec/release/config/app.json \u627e\u5230\u4e0b\u9762\u914d\u7f6e\u5185\u5bb9\uff0c\u5176\u4e2dkey\u548ccert\u5728 /mnt/exec/release/lib/https/ \u6b64\u8def\u5f84\uff0c\u7528\u6237\u53ef\u4ee5\u81ea\u5df1\u8fdb\u884c\u66ff\u6362\u3002 \"server\": { \"ssl\": { \"key\": \"./lib/https/key.pem\", \"cert\": \"./lib/https/cert.pem\" }","title":"\u52a0\u5bc6\u8bc1\u4e66"},{"location":"jetson_nano_tc358743/","text":"\u5728jstson nano\u4e0a\u4f7f\u7528C790 C779 C780 C790\u5168\u90e8\u9002\u7528\u6b64\u6587\u6863\uff0c\u672c\u6587\u6d4b\u8bd5\u5e95\u677f\u4e3ajetson nano b01\uff0c\u82e5\u4f60\u5176\u5b83\u5e95\u677f\u6709\u4e00\u4e9b\u8bbe\u8ba1\u5230\u8ddf\u677f\u5b50\u578b\u53f7\u76f8\u5173\u7684\u6b65\u9aa4\uff0c\u9700\u8981\u5bf9\u5e94\u6539\u53d8\uff0c\u8bf7\u6ce8\u610f\u3002 \u73b0\u5728\u5185\u6838\u6e90\u7801 wget https://developer.nvidia.com/embedded/l4t/r32_release_v7.2/sources/t210/public_sources.tbz2 tar -xf public_sources.tbz2 Linux_for_Tegra/source/public/kernel_src.tbz2 --strip-components=3 tar xf kernel_src.tbz2 \u6839\u636e\u4ed3\u5e93\u91cc\u7684\u76ee\u5f55\u7ed3\u6784\u8fdb\u884c\u6587\u4ef6\u66ff\u6362\uff0c\u8981\u5168\u90e8\u66ff\u6362 git clone https://github.com/ThomasVon2021/jetson_tc358743 cp ~/jetson_tc358743/* ./ -r . \u2514\u2500\u2500 jetson_tc358743-main \u251c\u2500\u2500 hardware \u2502 \u2514\u2500\u2500 nvidia \u2502 \u2514\u2500\u2500 platform \u2502 \u2514\u2500\u2500 t210 \u2502 \u251c\u2500\u2500 batuu \u2502 \u2502 \u2514\u2500\u2500 kernel-dts \u2502 \u2502 \u2514\u2500\u2500 tegra210-p3448-0003-p3542-0000.dts \u2502 \u2514\u2500\u2500 porg \u2502 \u2514\u2500\u2500 kernel-dts \u2502 \u251c\u2500\u2500 Makefile \u2502 \u251c\u2500\u2500 porg-platforms \u2502 \u2502 \u251c\u2500\u2500 tegra210-dual-tc358743.dtsi \u2502 \u2502 \u251c\u2500\u2500 tegra210-porg-dual-tc358743.dtsi \u2502 \u2502 \u251c\u2500\u2500 tegra210-porg-tc358743.dtsi \u2502 \u2502 \u2514\u2500\u2500 tegra210-tc358743.dtsi \u2502 \u251c\u2500\u2500 tegra210-p3448-0000-p3449-0000-b00.dts \u2502 \u251c\u2500\u2500 tegra210-p3448-all-p3449-0000-camera-tc358743-dual.dts \u2502 \u2514\u2500\u2500 tegra210-p3448-common-tc358743.dts \u251c\u2500\u2500 kernel \u2502 \u2514\u2500\u2500 kernel-4.9 \u2502 \u251c\u2500\u2500 drivers \u2502 \u2502 \u2514\u2500\u2500 media \u2502 \u2502 \u2514\u2500\u2500 i2c \u2502 \u2502 \u251c\u2500\u2500 tc358743.c \u2502 \u2502 \u2514\u2500\u2500 tc358743_regs.h \u2502 \u2514\u2500\u2500 include \u2502 \u2514\u2500\u2500 media \u2502 \u2514\u2500\u2500 i2c \u2502 \u2514\u2500\u2500 tc358743.h \u2514\u2500\u2500 README.md \u4ea4\u53c9\u7f16\u8bd1\u94fe\u4e0b\u8f7d,\u540e\u9762make\u65f6\uff0c\u4f60\u9700\u8981\u6307\u5b9a\u7f16\u8bd1\u94fe wget http://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/aarch64-linux-gnu/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz tar xf gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz \u8fdb\u5165\u5230kernel/kernel-4.9/\uff0c\u5148\u914d\u7f6e\u518d\u7f16\u8bd1\uff0c make ARCH=arm64 tegra_defconfig menuconfig Device Drivers > Multimedia Support > I2C Encoders, decoders, sensors and other helper chips Toshiba TC358743 decoder should be * (press y or space on the option) grep -i tc358743 .config #checking if its really enabled make ARCH=arm64 CROSS_COMPILE=/root/work/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu- -j4 \u5c06\u7f16\u8bd1\u51fa\u6765\u7684Image\u548cdtb\u6587\u4ef6\u5206\u522b\u62f7\u8d1d\u5230nano\u7684\u7cfb\u7edf\u7684\u4e0b\u9762\u8def\u5f84\u4e0b,\u82e5\u4f60\u7684\u8f7d\u677f\u4e0d\u662fB01\uff0c\u9700\u8981\u66f4\u6362\u5bf9\u5e94\u7684dtb\u6587\u4ef6\uff0cdtb\u6587\u4ef6\u4e0e\u4f60\u7684\u677f\u5b50\u578b\u53f7\u5bf9\u5e94\u5173\u7cfb\uff0c\u53ef\u4ee5\u67e5\u627e wiki kernel/kernel-4.9/arch/arm64/boot/Image ==> /boot/Image kernel/kernel-4.9/arch/arm64/boot/dts/tegra210-p3448-0000-p3449-0000-b00.dtb ==> /boot/veyecam/ #\u5176\u4e2d\u4f60\u7684nano\u8def\u5f84\u5982\u679c\u4e0d\u5b58\u5728veyecam\u6587\u4ef6\u5939\uff0c\u5148\u521b\u5efa sudo mkdir /boot/veyecam/ sudo cp / /boot/veyecam/ -f \u5148\u5907\u4efd extlinux.conf \u6587\u4ef6\uff0c\u7136\u540e\u7f16\u8f91/boot/extlinux/extlinux.conf\u6587\u4ef6\uff0c\u5728\u8be5\u6587\u4ef6\u4e0b\u589e\u52a0\uff1a FDT /boot/veyecam/ \u6ce8\u610f \u4e3a\u4f60\u7248\u672c\u7f16\u8bd1\u51fa\u6765\u7684dtb\u5b9e\u9645\u6587\u4ef6\u540d\uff0c \u91cd\u542f\u540e\u751f\u6548","title":"\u5728jstson nano\u4e0a\u4f7f\u7528C790"},{"location":"jetson_nano_tc358743/#jstson-nanoc790","text":"C779 C780 C790\u5168\u90e8\u9002\u7528\u6b64\u6587\u6863\uff0c\u672c\u6587\u6d4b\u8bd5\u5e95\u677f\u4e3ajetson nano b01\uff0c\u82e5\u4f60\u5176\u5b83\u5e95\u677f\u6709\u4e00\u4e9b\u8bbe\u8ba1\u5230\u8ddf\u677f\u5b50\u578b\u53f7\u76f8\u5173\u7684\u6b65\u9aa4\uff0c\u9700\u8981\u5bf9\u5e94\u6539\u53d8\uff0c\u8bf7\u6ce8\u610f\u3002 \u73b0\u5728\u5185\u6838\u6e90\u7801 wget https://developer.nvidia.com/embedded/l4t/r32_release_v7.2/sources/t210/public_sources.tbz2 tar -xf public_sources.tbz2 Linux_for_Tegra/source/public/kernel_src.tbz2 --strip-components=3 tar xf kernel_src.tbz2 \u6839\u636e\u4ed3\u5e93\u91cc\u7684\u76ee\u5f55\u7ed3\u6784\u8fdb\u884c\u6587\u4ef6\u66ff\u6362\uff0c\u8981\u5168\u90e8\u66ff\u6362 git clone https://github.com/ThomasVon2021/jetson_tc358743 cp ~/jetson_tc358743/* ./ -r . \u2514\u2500\u2500 jetson_tc358743-main \u251c\u2500\u2500 hardware \u2502 \u2514\u2500\u2500 nvidia \u2502 \u2514\u2500\u2500 platform \u2502 \u2514\u2500\u2500 t210 \u2502 \u251c\u2500\u2500 batuu \u2502 \u2502 \u2514\u2500\u2500 kernel-dts \u2502 \u2502 \u2514\u2500\u2500 tegra210-p3448-0003-p3542-0000.dts \u2502 \u2514\u2500\u2500 porg \u2502 \u2514\u2500\u2500 kernel-dts \u2502 \u251c\u2500\u2500 Makefile \u2502 \u251c\u2500\u2500 porg-platforms \u2502 \u2502 \u251c\u2500\u2500 tegra210-dual-tc358743.dtsi \u2502 \u2502 \u251c\u2500\u2500 tegra210-porg-dual-tc358743.dtsi \u2502 \u2502 \u251c\u2500\u2500 tegra210-porg-tc358743.dtsi \u2502 \u2502 \u2514\u2500\u2500 tegra210-tc358743.dtsi \u2502 \u251c\u2500\u2500 tegra210-p3448-0000-p3449-0000-b00.dts \u2502 \u251c\u2500\u2500 tegra210-p3448-all-p3449-0000-camera-tc358743-dual.dts \u2502 \u2514\u2500\u2500 tegra210-p3448-common-tc358743.dts \u251c\u2500\u2500 kernel \u2502 \u2514\u2500\u2500 kernel-4.9 \u2502 \u251c\u2500\u2500 drivers \u2502 \u2502 \u2514\u2500\u2500 media \u2502 \u2502 \u2514\u2500\u2500 i2c \u2502 \u2502 \u251c\u2500\u2500 tc358743.c \u2502 \u2502 \u2514\u2500\u2500 tc358743_regs.h \u2502 \u2514\u2500\u2500 include \u2502 \u2514\u2500\u2500 media \u2502 \u2514\u2500\u2500 i2c \u2502 \u2514\u2500\u2500 tc358743.h \u2514\u2500\u2500 README.md \u4ea4\u53c9\u7f16\u8bd1\u94fe\u4e0b\u8f7d,\u540e\u9762make\u65f6\uff0c\u4f60\u9700\u8981\u6307\u5b9a\u7f16\u8bd1\u94fe wget http://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/aarch64-linux-gnu/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz tar xf gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz \u8fdb\u5165\u5230kernel/kernel-4.9/\uff0c\u5148\u914d\u7f6e\u518d\u7f16\u8bd1\uff0c make ARCH=arm64 tegra_defconfig menuconfig Device Drivers > Multimedia Support > I2C Encoders, decoders, sensors and other helper chips Toshiba TC358743 decoder should be * (press y or space on the option) grep -i tc358743 .config #checking if its really enabled make ARCH=arm64 CROSS_COMPILE=/root/work/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu- -j4 \u5c06\u7f16\u8bd1\u51fa\u6765\u7684Image\u548cdtb\u6587\u4ef6\u5206\u522b\u62f7\u8d1d\u5230nano\u7684\u7cfb\u7edf\u7684\u4e0b\u9762\u8def\u5f84\u4e0b,\u82e5\u4f60\u7684\u8f7d\u677f\u4e0d\u662fB01\uff0c\u9700\u8981\u66f4\u6362\u5bf9\u5e94\u7684dtb\u6587\u4ef6\uff0cdtb\u6587\u4ef6\u4e0e\u4f60\u7684\u677f\u5b50\u578b\u53f7\u5bf9\u5e94\u5173\u7cfb\uff0c\u53ef\u4ee5\u67e5\u627e wiki kernel/kernel-4.9/arch/arm64/boot/Image ==> /boot/Image kernel/kernel-4.9/arch/arm64/boot/dts/tegra210-p3448-0000-p3449-0000-b00.dtb ==> /boot/veyecam/ #\u5176\u4e2d\u4f60\u7684nano\u8def\u5f84\u5982\u679c\u4e0d\u5b58\u5728veyecam\u6587\u4ef6\u5939\uff0c\u5148\u521b\u5efa sudo mkdir /boot/veyecam/ sudo cp / /boot/veyecam/ -f \u5148\u5907\u4efd extlinux.conf \u6587\u4ef6\uff0c\u7136\u540e\u7f16\u8f91/boot/extlinux/extlinux.conf\u6587\u4ef6\uff0c\u5728\u8be5\u6587\u4ef6\u4e0b\u589e\u52a0\uff1a FDT /boot/veyecam/ \u6ce8\u610f \u4e3a\u4f60\u7248\u672c\u7f16\u8bd1\u51fa\u6765\u7684dtb\u5b9e\u9645\u6587\u4ef6\u540d\uff0c \u91cd\u542f\u540e\u751f\u6548","title":"\u5728jstson nano\u4e0a\u4f7f\u7528C790"},{"location":"make-image/","text":"Make your owner image \u5f53\u4f60\u5bf9\u955c\u50cf\u8fdb\u884c\u4e86\u4fee\u6539\uff0c\u60f3\u5236\u4f5c\u81ea\u5df1\u7684\u955c\u50cf\u65f6\uff0c\u53ef\u4ee5\u53c2\u8003\u4e0b\u9762\u5728linux\u4e0b\u7684\u65b9\u6cd5\uff0c\u5236\u4f5c\u4e00\u4e2a\u6700\u5c0f\u955c\u50cf\u3002 \u9996\u5148\u4f7f\u7528gparted\u8f6f\u4ef6\uff0c\u6253\u5f00\u6240\u8981\u5236\u4f5c\u7684\u955c\u50cf\u7684sd\u5361\u3002\u5c06\u672a\u4f7f\u7528\u7684\u7a7a\u95f4\u901a\u8fc7gparted\u8f6f\u4ef6\u5c06\u5176\u5206\u5272\u51fa\u6765\uff0c\u5e76\u5c06\u5176\u8bbe\u7f6e\u4e3a\u672a\u5206\u914d\u3002\u8fd9\u6837\u5236\u4f5c\u955c\u50cf\u65f6\uff0c\u8fd9\u90e8\u5206\u65e0\u4efb\u4f55\u6709\u6548\u5185\u5bb9\u7684\u7a7a\u95f4\u5c31\u4e0d\u4f1a\u88ab\u5236\u4f5c\u4e86\u3002 \u7136\u540e\u4f7f\u7528\u9996\u5148\u4f7f\u7528fdisk\u547d\u4ee4\u67e5\u770b\u6709\u6548\u7a7a\u95f4\u7684\u5927\u5c0f\uff0c\u5982\u4e0b\u56fe,\u537310151935\u3002 \u7136\u540e\u4f7f\u7528dd\u547d\u4ee4\u5f80\u4e00\u4e2a\u7a7a\u7684img\u6587\u4ef6\u91cc\u5199\u5165\u5373\u53ef,\u5176\u4e2dcount\u7684\u5927\u5c0f\u6bd4fdisk\u770b\u5230\u7684\u5377\u5c3e\u5927\u5c0f\u5927\u4e8e1\u5373\u53ef\u3002 touch blikvm-armbian-v4-20230623.img sudo dd if=/dev/sdb of=./blikvm-armbian-v4-20230623.img bs=512 count=10151936 \u7b49\u5f85dd\u547d\u4ee4\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002","title":"\u5236\u4f5c\u955c\u50cf"},{"location":"make-image/#make-your-owner-image","text":"\u5f53\u4f60\u5bf9\u955c\u50cf\u8fdb\u884c\u4e86\u4fee\u6539\uff0c\u60f3\u5236\u4f5c\u81ea\u5df1\u7684\u955c\u50cf\u65f6\uff0c\u53ef\u4ee5\u53c2\u8003\u4e0b\u9762\u5728linux\u4e0b\u7684\u65b9\u6cd5\uff0c\u5236\u4f5c\u4e00\u4e2a\u6700\u5c0f\u955c\u50cf\u3002 \u9996\u5148\u4f7f\u7528gparted\u8f6f\u4ef6\uff0c\u6253\u5f00\u6240\u8981\u5236\u4f5c\u7684\u955c\u50cf\u7684sd\u5361\u3002\u5c06\u672a\u4f7f\u7528\u7684\u7a7a\u95f4\u901a\u8fc7gparted\u8f6f\u4ef6\u5c06\u5176\u5206\u5272\u51fa\u6765\uff0c\u5e76\u5c06\u5176\u8bbe\u7f6e\u4e3a\u672a\u5206\u914d\u3002\u8fd9\u6837\u5236\u4f5c\u955c\u50cf\u65f6\uff0c\u8fd9\u90e8\u5206\u65e0\u4efb\u4f55\u6709\u6548\u5185\u5bb9\u7684\u7a7a\u95f4\u5c31\u4e0d\u4f1a\u88ab\u5236\u4f5c\u4e86\u3002 \u7136\u540e\u4f7f\u7528\u9996\u5148\u4f7f\u7528fdisk\u547d\u4ee4\u67e5\u770b\u6709\u6548\u7a7a\u95f4\u7684\u5927\u5c0f\uff0c\u5982\u4e0b\u56fe,\u537310151935\u3002 \u7136\u540e\u4f7f\u7528dd\u547d\u4ee4\u5f80\u4e00\u4e2a\u7a7a\u7684img\u6587\u4ef6\u91cc\u5199\u5165\u5373\u53ef,\u5176\u4e2dcount\u7684\u5927\u5c0f\u6bd4fdisk\u770b\u5230\u7684\u5377\u5c3e\u5927\u5c0f\u5927\u4e8e1\u5373\u53ef\u3002 touch blikvm-armbian-v4-20230623.img sudo dd if=/dev/sdb of=./blikvm-armbian-v4-20230623.img bs=512 count=10151936 \u7b49\u5f85dd\u547d\u4ee4\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002","title":"Make your owner image"},{"location":"modify_pikvm_image/","text":"\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u9700\u8981\u505a\u4ee5\u4e0b\u4fee\u6539\u6765\u9002\u914dBLIKVM\u786c\u4ef6 \u56e0\u4e3ablikvm\u786c\u4ef6\u5b9e\u73b0\u65b9\u6848\u548cPiKVM\u786c\u4ef6\u5b9e\u73b0\u65b9\u6848\u5e76\u4e0d\u5b8c\u5168\u76f8\u540c\uff0c\u56e0\u6b64\u9488\u5bf9PiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u60a8\u9700\u8981\u901a\u8fc7\u4e0b\u5217\u914d\u7f6e\u4fee\u6539\u4e00\u4e9b\u9519\u8bef\u3002\u5f53\u7136\u60a8\u53ef\u4ee5\u4f7f\u7528\u6211\u4eec\u5df2\u7ecf\u505a\u597d\u914d\u7f6e\u7684 \u955c\u50cf \u98ce\u6247 \u56e0BLIKVM\u786c\u4ef6\u4e0ePiKVM\u4f7f\u7528\u98ce\u6247\u4e0d\u540c\uff0c\u9996\u5148\u9700\u66ff\u6362\u63a7\u5236\u98ce\u6247\u811a\u672c\uff0c\u4e0b\u5217\u9ed8\u8ba4\u5f00\u59cb\u98ce\u6247\u6e29\u5ea6\u4e3a40\u6444\u6c0f\u5ea6 su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro \u7f16\u8f91/etc/kvmd/override.yaml\u6587\u4ef6\uff0c\u6dfb\u52a0\u4e0b\u5217\u5185\u5bb9\u5df2\u53bb\u9664Web UI\u5173\u4e8e\u98ce\u6247\u7684\u9519\u8bef\u8b66\u544a\u3002 kvmd: info: fan: unix: '' 2. EDID\u6587\u4ef6\u66f4\u6362 EDID\u6587\u4ef6\u4f5c\u7528\u4e3a\uff0c\u8bbe\u7f6e\u88ab\u63a7\u8ba1\u7b97\u673a\u6309\u7167\u671f\u671b\u7684\u5206\u8fa8\u7387\u8fdb\u884c\u8f93\u5165\uff0c\u7531\u4e8ePiKVM\u4e0d\u540c\u65f6\u671f\u7684\u955c\u50cfEDID\u6587\u4ef6\u4e0d\u4e00\u5b9a\u662f\u6ee1\u8db31080P60Hz, \u5f53\u4f60\u4f7f\u7528\u7684\u786c\u4ef6\u4e3aCM4\u7248\u672c\uff0c\u53d1\u73b0\u88ab\u63a7\u7535\u8111\u9ed8\u8ba4\u8f93\u51fa\u4e0d\u662f1080P60Hz\uff0c\u53ef\u4ee5\u901a\u8fc7\u4fee\u6539/etc/kvmd/tc358743-edid.hex\u4e3a\u4e0b\u5217\u5185\u5bb9\uff1a 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 \u786e\u8ba4 /boot/config.txt \u6dfb\u52a0\u4e86\u4e0b\u5217\u914d\u7f6e\uff0c\u4ece\u800c\u652f\u63011080p60hz\u89c6\u9891\u8f93\u5165\u548c\u58f0\u97f3\u8f93\u5165\uff0c\u76f8\u5173\u914d\u7f6e\u53c2\u8003\u5982\u4e0b\uff1a # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio \u5982\u679c\u4f60\u4f7f\u7528webrtc\u6ca1\u6709\u58f0\u97f3\uff0c\u5c1d\u8bd5\u5728/etc/kvmd/janus/janus.plugin.ustreamer.jcfg\u6b64\u6587\u4ef6\u4e2d\u6dfb\u52a0\u4e0b\u5217\u5185\u5bb9 audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" } 3. OLED\u542f\u7528 PiKVM\u955c\u50cf\uff0c\u6309\u7167\u4e0b\u9762\u7684\u65b9\u6cd5\u542f\u7528OLED\u3002 \u5982\u679c\u60a8\u4f7f\u7528PiKVM\u955c\u50cf\uff0c\u8bf7\u767b\u5f55\u5230PiKVM\u5e76\u8fd0\u884c\u4ee5\u4e0b\u547d\u4ee4\uff1a # rw # systemctl enable --now kvmd-oled //\u542f\u7528OLED # ro \u5982\u679cOLED\u4ecd\u7136\u65e0\u6cd5\u5de5\u4f5c\uff0c\u60a8\u9700\u8981\u68c0\u67e5\"/boot/config.txt\"\u6587\u4ef6\u4e2d\u662f\u5426\u6709\"dtparam=i2c_arm=on\"\uff0c\u4ee5\u53ca\"/etc/modules-load.d/i2c.conf\"\u6587\u4ef6\u4e2d\u662f\u5426\u6709\"i2c-dev\"\u3002\u5982\u679c\u6ca1\u6709\uff0c\u8bf7\u521b\u5efa\u5e76\u6dfb\u52a0\u5b83\u4eec\u3002 \u5982\u679c\u5728\u4e0a\u8ff0\u914d\u7f6e\u4e4b\u540e\u4ecd\u7136\u65e0\u6cd5\u5de5\u4f5c\uff0c\u8bf7\u523b\u5f55 blikvm\u63d0\u4f9b\u7684\u6d4b\u8bd5\u955c\u50cf \u6765\u68c0\u67e5OLED\u786c\u4ef6\u662f\u5426\u635f\u574f\u3002 4. \u5173\u4e8e v4mini \u955c\u50cf\u7684\u914d\u7f6e \u5982\u679c\u4f60\u60f3\u5728 blikvm v1 \u548c v2 \u4e0a\u4f7f\u7528 PiKVM v4mini \u955c\u50cf\uff0c\u7531\u4e8e v4mini \u955c\u50cf\u4f7f\u7528\u4e86\u4e0d\u540c\u7684 GPIO \u5f15\u811a\u6765\u63a7\u5236 ATX\uff0c\u56e0\u6b64\u4f60\u9700\u8981\u8fdb\u884c\u4ee5\u4e0b\u8986\u76d6\u914d\u7f6e\u3002\u5982\u679c\u4f60\u5e0c\u671b\u5728 blikvm v1 \u6216 v2 \u7248\u672c\u4e0a\u8fd0\u884c v4mini \u955c\u50cf\u5e76\u80fd\u591f\u4f7f\u7528 ATX \u63a7\u5236\uff0c\u4f60\u5fc5\u987b\u8fdb\u884c\u8fd9\u4e9b\u4fee\u6539\uff1b\u5982\u679c\u4e0d\u8fdb\u884c\u66f4\u6539\uff0cATX \u63a7\u5236\u5c06\u65e0\u6cd5\u6b63\u5e38\u5de5\u4f5c\uff08LED \u5f15\u811a\u4e0d\u540c\uff09\u3002 \u7f16\u8f91 /etc/kvmd/override.yaml \u6587\u4ef6\uff0c\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff1a kvmd: ### \u7981\u7528\u98ce\u6247\u63d2\u5ea7\u68c0\u67e5 ### info: fan: unix: '' atx: hdd_led_pin: 22 power_led_pin: 24 power_switch_pin: 23 reset_switch_pin: 27 type: gpio gpio: scheme: __v3_usb_breaker__: pin: 5 mode: output initial: false pulse: delay: 0","title":"\u914d\u7f6ePiKVM OS"},{"location":"modify_pikvm_image/#pikvmblikvm","text":"\u56e0\u4e3ablikvm\u786c\u4ef6\u5b9e\u73b0\u65b9\u6848\u548cPiKVM\u786c\u4ef6\u5b9e\u73b0\u65b9\u6848\u5e76\u4e0d\u5b8c\u5168\u76f8\u540c\uff0c\u56e0\u6b64\u9488\u5bf9PiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u60a8\u9700\u8981\u901a\u8fc7\u4e0b\u5217\u914d\u7f6e\u4fee\u6539\u4e00\u4e9b\u9519\u8bef\u3002\u5f53\u7136\u60a8\u53ef\u4ee5\u4f7f\u7528\u6211\u4eec\u5df2\u7ecf\u505a\u597d\u914d\u7f6e\u7684 \u955c\u50cf","title":"\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u9700\u8981\u505a\u4ee5\u4e0b\u4fee\u6539\u6765\u9002\u914dBLIKVM\u786c\u4ef6"},{"location":"modify_pikvm_image/#_1","text":"\u56e0BLIKVM\u786c\u4ef6\u4e0ePiKVM\u4f7f\u7528\u98ce\u6247\u4e0d\u540c\uff0c\u9996\u5148\u9700\u66ff\u6362\u63a7\u5236\u98ce\u6247\u811a\u672c\uff0c\u4e0b\u5217\u9ed8\u8ba4\u5f00\u59cb\u98ce\u6247\u6e29\u5ea6\u4e3a40\u6444\u6c0f\u5ea6 su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro \u7f16\u8f91/etc/kvmd/override.yaml\u6587\u4ef6\uff0c\u6dfb\u52a0\u4e0b\u5217\u5185\u5bb9\u5df2\u53bb\u9664Web UI\u5173\u4e8e\u98ce\u6247\u7684\u9519\u8bef\u8b66\u544a\u3002 kvmd: info: fan: unix: ''","title":"\u98ce\u6247"},{"location":"modify_pikvm_image/#2-edid","text":"EDID\u6587\u4ef6\u4f5c\u7528\u4e3a\uff0c\u8bbe\u7f6e\u88ab\u63a7\u8ba1\u7b97\u673a\u6309\u7167\u671f\u671b\u7684\u5206\u8fa8\u7387\u8fdb\u884c\u8f93\u5165\uff0c\u7531\u4e8ePiKVM\u4e0d\u540c\u65f6\u671f\u7684\u955c\u50cfEDID\u6587\u4ef6\u4e0d\u4e00\u5b9a\u662f\u6ee1\u8db31080P60Hz, \u5f53\u4f60\u4f7f\u7528\u7684\u786c\u4ef6\u4e3aCM4\u7248\u672c\uff0c\u53d1\u73b0\u88ab\u63a7\u7535\u8111\u9ed8\u8ba4\u8f93\u51fa\u4e0d\u662f1080P60Hz\uff0c\u53ef\u4ee5\u901a\u8fc7\u4fee\u6539/etc/kvmd/tc358743-edid.hex\u4e3a\u4e0b\u5217\u5185\u5bb9\uff1a 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 \u786e\u8ba4 /boot/config.txt \u6dfb\u52a0\u4e86\u4e0b\u5217\u914d\u7f6e\uff0c\u4ece\u800c\u652f\u63011080p60hz\u89c6\u9891\u8f93\u5165\u548c\u58f0\u97f3\u8f93\u5165\uff0c\u76f8\u5173\u914d\u7f6e\u53c2\u8003\u5982\u4e0b\uff1a # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio \u5982\u679c\u4f60\u4f7f\u7528webrtc\u6ca1\u6709\u58f0\u97f3\uff0c\u5c1d\u8bd5\u5728/etc/kvmd/janus/janus.plugin.ustreamer.jcfg\u6b64\u6587\u4ef6\u4e2d\u6dfb\u52a0\u4e0b\u5217\u5185\u5bb9 audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" }","title":"2. EDID\u6587\u4ef6\u66f4\u6362"},{"location":"modify_pikvm_image/#3-oled","text":"PiKVM\u955c\u50cf\uff0c\u6309\u7167\u4e0b\u9762\u7684\u65b9\u6cd5\u542f\u7528OLED\u3002 \u5982\u679c\u60a8\u4f7f\u7528PiKVM\u955c\u50cf\uff0c\u8bf7\u767b\u5f55\u5230PiKVM\u5e76\u8fd0\u884c\u4ee5\u4e0b\u547d\u4ee4\uff1a # rw # systemctl enable --now kvmd-oled //\u542f\u7528OLED # ro \u5982\u679cOLED\u4ecd\u7136\u65e0\u6cd5\u5de5\u4f5c\uff0c\u60a8\u9700\u8981\u68c0\u67e5\"/boot/config.txt\"\u6587\u4ef6\u4e2d\u662f\u5426\u6709\"dtparam=i2c_arm=on\"\uff0c\u4ee5\u53ca\"/etc/modules-load.d/i2c.conf\"\u6587\u4ef6\u4e2d\u662f\u5426\u6709\"i2c-dev\"\u3002\u5982\u679c\u6ca1\u6709\uff0c\u8bf7\u521b\u5efa\u5e76\u6dfb\u52a0\u5b83\u4eec\u3002 \u5982\u679c\u5728\u4e0a\u8ff0\u914d\u7f6e\u4e4b\u540e\u4ecd\u7136\u65e0\u6cd5\u5de5\u4f5c\uff0c\u8bf7\u523b\u5f55 blikvm\u63d0\u4f9b\u7684\u6d4b\u8bd5\u955c\u50cf \u6765\u68c0\u67e5OLED\u786c\u4ef6\u662f\u5426\u635f\u574f\u3002","title":"3. OLED\u542f\u7528"},{"location":"modify_pikvm_image/#4-v4mini","text":"\u5982\u679c\u4f60\u60f3\u5728 blikvm v1 \u548c v2 \u4e0a\u4f7f\u7528 PiKVM v4mini \u955c\u50cf\uff0c\u7531\u4e8e v4mini \u955c\u50cf\u4f7f\u7528\u4e86\u4e0d\u540c\u7684 GPIO \u5f15\u811a\u6765\u63a7\u5236 ATX\uff0c\u56e0\u6b64\u4f60\u9700\u8981\u8fdb\u884c\u4ee5\u4e0b\u8986\u76d6\u914d\u7f6e\u3002\u5982\u679c\u4f60\u5e0c\u671b\u5728 blikvm v1 \u6216 v2 \u7248\u672c\u4e0a\u8fd0\u884c v4mini \u955c\u50cf\u5e76\u80fd\u591f\u4f7f\u7528 ATX \u63a7\u5236\uff0c\u4f60\u5fc5\u987b\u8fdb\u884c\u8fd9\u4e9b\u4fee\u6539\uff1b\u5982\u679c\u4e0d\u8fdb\u884c\u66f4\u6539\uff0cATX \u63a7\u5236\u5c06\u65e0\u6cd5\u6b63\u5e38\u5de5\u4f5c\uff08LED \u5f15\u811a\u4e0d\u540c\uff09\u3002 \u7f16\u8f91 /etc/kvmd/override.yaml \u6587\u4ef6\uff0c\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff1a kvmd: ### \u7981\u7528\u98ce\u6247\u63d2\u5ea7\u68c0\u67e5 ### info: fan: unix: '' atx: hdd_led_pin: 22 power_led_pin: 24 power_switch_pin: 23 reset_switch_pin: 27 type: gpio gpio: scheme: __v3_usb_breaker__: pin: 5 mode: output initial: false pulse: delay: 0","title":"4.\u5173\u4e8e v4mini \u955c\u50cf\u7684\u914d\u7f6e"},{"location":"msd/","text":"U\u76d8\u8bbe\u5907\u6a21\u62df \u91cd\u88c5\u7cfb\u7edf\u89c6\u9891 BliKVM\u652f\u6301U\u76d8\u8bbe\u5907\u6a21\u62df\uff0c\u901a\u8fc7\u6b64\u529f\u80fd\u53ef\u4ee5\u8fdb\u884c\u8fdc\u7a0b\u6302\u8f7d\u955c\u50cf\uff0c\u8fdb\u884c\u91cd\u88c5\u7cfb\u7edf\u3002 Web UI msd\u865a\u62dfU\u76d8\u5165\u53e3\u4e3a: \u4f7f\u7528web\u4e0a\u4f20\u955c\u50cf\u548c\u5236\u4f5c\u542f\u52a8\u76d8\uff0c\u5747\u662f\u540c\u6b65\u7ebf\u7a0b\uff0c\u4e0a\u4f20\u955c\u50cf\u9000\u51faMSD\u7684UI\u754c\u9762\u540e\uff0c\u4e0b\u6b21\u518d\u9009\u62e9\u76f8\u540c\u955c\u50cf\u53ef\u65ad\u70b9\u7eed\u4f20\u3002\u5236\u4f5c\u542f\u52a8\u76d8\u63a8\u51fa\u540e\u4e0d\u53ef\u65ad\u70b9\u91cd\u505a\uff0c\u9700\u91cd\u65b0\u5f00\u59cb\u3002 \u4e0a\u4f20\u955c\u50cf\u9ed8\u8ba4\u8def\u5f84\u4e3a/mnt/upload,\u82e5\u51fa\u73b0\u4e0a\u4f20\u5931\u8d25\uff0c\u5220\u9664\u4e3a\u6210\u529f\u7684\u7f13\u5b58\u6587\u4ef6\uff0c\u53ef\u624b\u52a8\u5220\u9664\u6b64\u6587\u4ef6\u5939\uff1b \u56e0\u90e8\u5206\u955c\u50cf\u6587\u4ef6\u5927\u5c0f\u8f83\u5927\uff0c\u91c7\u53d6\u4e0a\u4f20\u955c\u50cf\u65b9\u6848\u4e3a\u5207\u7247\u4e0a\u4f20\u548c\u5408\u5e76\uff0c\u5408\u5e76\u8fc7\u7a0b\u4e0d\u80fd\u65ad\u70b9\u91cd\u6765\uff0c\u5207\u8bb0\u7b49\u5f85\u5408\u5e76\u5b8c\u6210\u540e(\u65f6\u95f4\u8f83\u957f)\uff0c\u518d\u8fdb\u5165\u4e0b\u4e00\u6b65\uff1b \u5236\u4f5c\u542f\u52a8\u76d8\u4e5f\u5f88\u4e3a\u4e24\u4e2a\u6b65\u9aa4\uff0c\u5236\u4f5c\u865a\u62dfU\u76d8\uff0c\u5c06\u9009\u62e9\u7684iso\u955c\u50cf\u62f7\u8d1d\u5230\u5236\u4f5c\u597d\u7684\u865a\u62dfU\u76d8\u91cc\uff0c\u4e24\u4e2a\u6b65\u9aa4\u5747\u6709\u8fdb\u5ea6\uff0c\u8bf7\u7b49\u4e24\u8005\u8fdb\u5ea6\u5747100%\u540e\u518d\u70b9\u51fb\u4e0b\u4e00\u6b65\u6309\u94ae\u3002 \u624b\u52a8 (\u4e0d\u4f7f\u7528Web UI) 1. \u786e\u8ba4\u7cfb\u7edf\u5b58\u5728\u4e0b\u97624\u4e2a\u8def\u5f84\u3002\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662f\u6700\u65b0\u7684BliKVM\u955c\u50cf\uff0c\u65e0\u9700\u8fdb\u884c\u68c0\u67e5\u3002\u5176\u4e2d/opt/bin/msd/user\u8def\u5f84\u7528\u4e8e\u5b58\u653e\u7cfb\u7edf\u955c\u50cf\u3002 /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy 2. \u901a\u8fc7SSH\u767b\u9646\u5230BliKVM\u7ec8\u7aef\uff0c\u7528\u6237\u540d\u548c\u5bc6\u7801\u5747\u4e3ablikvm\uff0c\u901a\u8fc7rw\u547d\u4ee4\uff0c\u4f7f\u53ea\u8bfb\u7cfb\u7edf\u53d8\u4e3a\u53ef\u5199\u7cfb\u7edf\u3002 sudo rw 3. \u5728\u4f60\u63a7\u5236\u7aef\u7684\u7535\u8111\uff0c\u53ef\u4ee5\u5728\u7ec8\u7aef\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06iso\u955c\u50cf\u6587\u4ef6\u62f7\u8d1d\u5230BliKVM\u955c\u50cf\u7684\u6307\u5b9a\u8def\u5f84\u4e0b\u3002 scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ \u5f53\u7136\uff0c\u4f60\u4e5f\u53ef\u4ee5\u901a\u8fc7\u5176\u4ed6\u4efb\u4f55\u4f60\u719f\u6089\u7684\u65b9\u5f0f\u5c06iso\u955c\u50cf\u6587\u4ef6\u62f7\u8d1d\u5230\u6307\u5b9a\u8def\u5f84\u4e0b\u3002 4. \u901a\u8fc7\u4f7f\u7528\u4e0b\u5217\u4e24\u79cd\u547d\u4ee4\u4e2d\u7684\u4e00\u4e2a\uff0c\u5c06\u955c\u50cf\u62f7\u8d1d\u5230\u6a21\u62df\u7684U\u76d8\u4e2d\u3002U\u76d8\u9ed8\u8ba4\u5927\u5c0f\u8bbe\u7f6e\u7684\u4e3a5GB\uff0c\u5982\u679c\u4f60\u9700\u8981\u66f4\u5927\u7684\u7a7a\u95f4\uff0c\u4f60\u9700\u8981\u4fee\u6539kvmd-msd.sh\u811a\u672c\u3002 \u5982\u679c /mnt/msd/user \u8def\u5f84\u4e0b\u53ea\u6709\u4e00\u4e2a\u955c\u50cf\u6587\u4ef6, \u4f60\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528\u6b64\u547d\u4ee4. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make \u5982\u679c /mnt/msd/user \u8def\u5f84\u4e0b\u6709\u4e0d\u6b62\u4e00\u4e2a\u955c\u50cf\u6587\u4ef6, \u4f60\u53ef\u4ee5\u4f7f\u7528\u4e0b\u5217\u6587\u4ef6\u6307\u5b9a. xxx.iso \u8868\u793a\u955c\u50cf\u7684\u540d\u79f0.\u5176\u4e2d-s\u540e\u8ddf\u7684\u6570\u5b57\u5373\u662f\u5236\u4f5c\u7684U\u76d8\u7684\u5927\u5c0f\uff0c\u5355\u4f4d\u662fG\uff0c\u7528\u6237\u53ef\u4ee5\u6839\u636e\u81ea\u5df1\u9700\u6c42\u4fee\u6539\u3002-n\u540e\u8ddf\u7684\u5b57\u7b26\u4e32\u662fu\u76d8\u540d\u79f0\u3002 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso cp\u8fc7\u7a0b\u975e\u5e38\u6162\uff0c\u8bf7\u8010\u5fc3\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u3002 5. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06\u6a21\u62df\u7684U\u76d8\u8fde\u63a5\u5230\u5230\u4f60\u7684\u88ab\u63a7\u8bbe\u5907\u4e0a sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn 6. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06\u6a21\u62df\u7684U\u76d8\u4ece\u4f60\u7684\u88ab\u63a7\u8bbe\u5907\u4e0a\u5f39\u51fa sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn 7. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u6e05\u9664\u6389\u6a21\u62df\u7684U\u76d8\uff0c\u5c06\u4f1a\u91ca\u653e\u6389\u5bf9\u5e94\u7684\u7a7a\u95f4 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean 8. \u4e00\u5207\u6b63\u786e\u7684\u8bdd\uff0c\u6b64\u65f6\u4f60\u53ef\u4ee5\u5728\u4e00\u4e2aPC\u7cfb\u7edf\u91cc\u770b\u5230\u4f60\u6a21\u62df\u51fa\u7684U\u76d8\u3002\u901a\u8fc7WEB\u91cd\u542f\u7684\u4f60\u7684PC\uff0c\u7136\u540e\u4f7f\u7528\u5feb\u6377\u952e\uff08\u5f88\u591a\u7535\u8111\u662f\u6309F2\uff09\u8fdb\u5165BIOS\uff0c\u4fee\u6539boot\u542f\u52a8\u4f18\u5148\u7ea7\uff0c\u5c06\u6a21\u62df\u51fa\u7684U\u76d8\u8bbe\u5907\u4f18\u5148\u7ea7\u8bbe\u7f6e\u5728\u6700\u524d\u9762\u3002 9. \u6839\u636ebios\u7cfb\u7edf\u63d0\u793a\uff0c\u4fdd\u5b58\u91cd\u542f\uff0c\u5373\u53ef\u8fdb\u884cventoy\u7684\u5f15\u5bfc\u754c\u9762\u8fdb\u884c\u91cd\u88c5\u7cfb\u7edf\u3002 \u901a\u7528U\u76d8 \u4f20\u9012\u901a\u7528\u6587\u4ef6\uff0c\u6ce8\u610f\u6587\u4ef6\u540d\u9700\u547d\u540d\u4e3a\u82f1\u6587\uff0c\u4e2d\u6587\u4f1a\u4e71\u7801\u3002 conn\uff0c disconn, clean\u547d\u4ee4\u9488\u5bf9\u901a\u7528U\u76d8\u4f9d\u65e7\u6709\u6548\u3002 \u5236\u4f5c\u901a\u7528U\u76d8 -s\u540e\u8ddf\u7684\u662f\u5236\u4f5c\u901a\u7528U\u76d8\u7684\u5927\u5c0f\uff0c\u5355\u4f4d\u4e3aGb\uff0c\u5bb9\u91cf\u8d8a\u5927\uff0c\u5236\u4f5c\u65f6\u95f4\u8d8a\u957f\uff0c\u8bf7\u7ed3\u5408\u5b9e\u9645\u60c5\u51b5\u8bbe\u7f6e\u3002 -t \u5fc5\u987b\u4e3aother sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 4 -t other \u6587\u4ef6\u4ece\u7528\u6237\u7535\u8111==\u300bKVM==\u300b\u88ab\u63a7\u7535\u8111 \u9996\u5148\u4f60\u9700\u8981\u5c06\u6587\u4ef6\u4ece\u7528\u6237\u63a7\u5236\u7535\u8111\u53d1\u9001\u5230kvm scp xxx blikvm@xxxx:/mnt/msd/user/ \u5c06\u6587\u4ef6\u540c\u6b65\u5230\u88ab\u63a7\u7535\u8111\uff0c\u5e76\u8fde\u63a5\u4e0a\u7535\u8111 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c forward \u540e\u9762\u6709\u9700\u8981\u65b0\u7684\u5185\u5bb9\u4ece\u7528\u6237\u7535\u8111\uff0c\u4f20\u9012\u5230\u88ab\u63a7\u7535\u8111\uff0c\u91cd\u590d\u7b2c1\u548c\u7b2c2\u6b65\u5373\u53ef \u6587\u4ef6\u4ece\u88ab\u63a7\u7535\u8111==\u300bKVM==\u7528\u6237\u7535\u8111 \u9996\u5148\u5728\u88ab\u63a7\u7535\u8111\u4e0a\u5c06\u6587\u4ef6\u62f7\u8d1d\u5230\u6a21\u62df\u7684\u865a\u62dfU\u76d8\u91cc\uff0c\u7136\u540e\u6267\u884c\u4e0b\u9762\u7684\u6307\u4ee4\uff0c\u5c06\u6587\u4ef6\u62f7\u8d1d\u5230kvm\u7684/mnt/msd/user/\u76ee\u5f55\u4e0b sudo bash /usr/bin/blikvm/kvmd-msd.sh -c rever \u5c06\u6587\u4ef6\u4ecekvm\u62f7\u8d1d\u5230\u7528\u6237\u7535\u8111 scp blikvm@xxxx:/mnt/msd/user/* .","title":"U\u76d8\u9a71\u52a8"},{"location":"msd/#u","text":"\u91cd\u88c5\u7cfb\u7edf\u89c6\u9891 BliKVM\u652f\u6301U\u76d8\u8bbe\u5907\u6a21\u62df\uff0c\u901a\u8fc7\u6b64\u529f\u80fd\u53ef\u4ee5\u8fdb\u884c\u8fdc\u7a0b\u6302\u8f7d\u955c\u50cf\uff0c\u8fdb\u884c\u91cd\u88c5\u7cfb\u7edf\u3002","title":"U\u76d8\u8bbe\u5907\u6a21\u62df"},{"location":"msd/#web-ui","text":"msd\u865a\u62dfU\u76d8\u5165\u53e3\u4e3a: \u4f7f\u7528web\u4e0a\u4f20\u955c\u50cf\u548c\u5236\u4f5c\u542f\u52a8\u76d8\uff0c\u5747\u662f\u540c\u6b65\u7ebf\u7a0b\uff0c\u4e0a\u4f20\u955c\u50cf\u9000\u51faMSD\u7684UI\u754c\u9762\u540e\uff0c\u4e0b\u6b21\u518d\u9009\u62e9\u76f8\u540c\u955c\u50cf\u53ef\u65ad\u70b9\u7eed\u4f20\u3002\u5236\u4f5c\u542f\u52a8\u76d8\u63a8\u51fa\u540e\u4e0d\u53ef\u65ad\u70b9\u91cd\u505a\uff0c\u9700\u91cd\u65b0\u5f00\u59cb\u3002 \u4e0a\u4f20\u955c\u50cf\u9ed8\u8ba4\u8def\u5f84\u4e3a/mnt/upload,\u82e5\u51fa\u73b0\u4e0a\u4f20\u5931\u8d25\uff0c\u5220\u9664\u4e3a\u6210\u529f\u7684\u7f13\u5b58\u6587\u4ef6\uff0c\u53ef\u624b\u52a8\u5220\u9664\u6b64\u6587\u4ef6\u5939\uff1b \u56e0\u90e8\u5206\u955c\u50cf\u6587\u4ef6\u5927\u5c0f\u8f83\u5927\uff0c\u91c7\u53d6\u4e0a\u4f20\u955c\u50cf\u65b9\u6848\u4e3a\u5207\u7247\u4e0a\u4f20\u548c\u5408\u5e76\uff0c\u5408\u5e76\u8fc7\u7a0b\u4e0d\u80fd\u65ad\u70b9\u91cd\u6765\uff0c\u5207\u8bb0\u7b49\u5f85\u5408\u5e76\u5b8c\u6210\u540e(\u65f6\u95f4\u8f83\u957f)\uff0c\u518d\u8fdb\u5165\u4e0b\u4e00\u6b65\uff1b \u5236\u4f5c\u542f\u52a8\u76d8\u4e5f\u5f88\u4e3a\u4e24\u4e2a\u6b65\u9aa4\uff0c\u5236\u4f5c\u865a\u62dfU\u76d8\uff0c\u5c06\u9009\u62e9\u7684iso\u955c\u50cf\u62f7\u8d1d\u5230\u5236\u4f5c\u597d\u7684\u865a\u62dfU\u76d8\u91cc\uff0c\u4e24\u4e2a\u6b65\u9aa4\u5747\u6709\u8fdb\u5ea6\uff0c\u8bf7\u7b49\u4e24\u8005\u8fdb\u5ea6\u5747100%\u540e\u518d\u70b9\u51fb\u4e0b\u4e00\u6b65\u6309\u94ae\u3002","title":"Web UI"},{"location":"msd/#web-ui_1","text":"1. \u786e\u8ba4\u7cfb\u7edf\u5b58\u5728\u4e0b\u97624\u4e2a\u8def\u5f84\u3002\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662f\u6700\u65b0\u7684BliKVM\u955c\u50cf\uff0c\u65e0\u9700\u8fdb\u884c\u68c0\u67e5\u3002\u5176\u4e2d/opt/bin/msd/user\u8def\u5f84\u7528\u4e8e\u5b58\u653e\u7cfb\u7edf\u955c\u50cf\u3002 /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy 2. \u901a\u8fc7SSH\u767b\u9646\u5230BliKVM\u7ec8\u7aef\uff0c\u7528\u6237\u540d\u548c\u5bc6\u7801\u5747\u4e3ablikvm\uff0c\u901a\u8fc7rw\u547d\u4ee4\uff0c\u4f7f\u53ea\u8bfb\u7cfb\u7edf\u53d8\u4e3a\u53ef\u5199\u7cfb\u7edf\u3002 sudo rw 3. \u5728\u4f60\u63a7\u5236\u7aef\u7684\u7535\u8111\uff0c\u53ef\u4ee5\u5728\u7ec8\u7aef\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06iso\u955c\u50cf\u6587\u4ef6\u62f7\u8d1d\u5230BliKVM\u955c\u50cf\u7684\u6307\u5b9a\u8def\u5f84\u4e0b\u3002 scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ \u5f53\u7136\uff0c\u4f60\u4e5f\u53ef\u4ee5\u901a\u8fc7\u5176\u4ed6\u4efb\u4f55\u4f60\u719f\u6089\u7684\u65b9\u5f0f\u5c06iso\u955c\u50cf\u6587\u4ef6\u62f7\u8d1d\u5230\u6307\u5b9a\u8def\u5f84\u4e0b\u3002 4. \u901a\u8fc7\u4f7f\u7528\u4e0b\u5217\u4e24\u79cd\u547d\u4ee4\u4e2d\u7684\u4e00\u4e2a\uff0c\u5c06\u955c\u50cf\u62f7\u8d1d\u5230\u6a21\u62df\u7684U\u76d8\u4e2d\u3002U\u76d8\u9ed8\u8ba4\u5927\u5c0f\u8bbe\u7f6e\u7684\u4e3a5GB\uff0c\u5982\u679c\u4f60\u9700\u8981\u66f4\u5927\u7684\u7a7a\u95f4\uff0c\u4f60\u9700\u8981\u4fee\u6539kvmd-msd.sh\u811a\u672c\u3002 \u5982\u679c /mnt/msd/user \u8def\u5f84\u4e0b\u53ea\u6709\u4e00\u4e2a\u955c\u50cf\u6587\u4ef6, \u4f60\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528\u6b64\u547d\u4ee4. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make \u5982\u679c /mnt/msd/user \u8def\u5f84\u4e0b\u6709\u4e0d\u6b62\u4e00\u4e2a\u955c\u50cf\u6587\u4ef6, \u4f60\u53ef\u4ee5\u4f7f\u7528\u4e0b\u5217\u6587\u4ef6\u6307\u5b9a. xxx.iso \u8868\u793a\u955c\u50cf\u7684\u540d\u79f0.\u5176\u4e2d-s\u540e\u8ddf\u7684\u6570\u5b57\u5373\u662f\u5236\u4f5c\u7684U\u76d8\u7684\u5927\u5c0f\uff0c\u5355\u4f4d\u662fG\uff0c\u7528\u6237\u53ef\u4ee5\u6839\u636e\u81ea\u5df1\u9700\u6c42\u4fee\u6539\u3002-n\u540e\u8ddf\u7684\u5b57\u7b26\u4e32\u662fu\u76d8\u540d\u79f0\u3002 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso cp\u8fc7\u7a0b\u975e\u5e38\u6162\uff0c\u8bf7\u8010\u5fc3\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u3002 5. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06\u6a21\u62df\u7684U\u76d8\u8fde\u63a5\u5230\u5230\u4f60\u7684\u88ab\u63a7\u8bbe\u5907\u4e0a sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn 6. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06\u6a21\u62df\u7684U\u76d8\u4ece\u4f60\u7684\u88ab\u63a7\u8bbe\u5907\u4e0a\u5f39\u51fa sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn 7. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u6e05\u9664\u6389\u6a21\u62df\u7684U\u76d8\uff0c\u5c06\u4f1a\u91ca\u653e\u6389\u5bf9\u5e94\u7684\u7a7a\u95f4 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean 8. \u4e00\u5207\u6b63\u786e\u7684\u8bdd\uff0c\u6b64\u65f6\u4f60\u53ef\u4ee5\u5728\u4e00\u4e2aPC\u7cfb\u7edf\u91cc\u770b\u5230\u4f60\u6a21\u62df\u51fa\u7684U\u76d8\u3002\u901a\u8fc7WEB\u91cd\u542f\u7684\u4f60\u7684PC\uff0c\u7136\u540e\u4f7f\u7528\u5feb\u6377\u952e\uff08\u5f88\u591a\u7535\u8111\u662f\u6309F2\uff09\u8fdb\u5165BIOS\uff0c\u4fee\u6539boot\u542f\u52a8\u4f18\u5148\u7ea7\uff0c\u5c06\u6a21\u62df\u51fa\u7684U\u76d8\u8bbe\u5907\u4f18\u5148\u7ea7\u8bbe\u7f6e\u5728\u6700\u524d\u9762\u3002 9. \u6839\u636ebios\u7cfb\u7edf\u63d0\u793a\uff0c\u4fdd\u5b58\u91cd\u542f\uff0c\u5373\u53ef\u8fdb\u884cventoy\u7684\u5f15\u5bfc\u754c\u9762\u8fdb\u884c\u91cd\u88c5\u7cfb\u7edf\u3002","title":"\u624b\u52a8 (\u4e0d\u4f7f\u7528Web UI)"},{"location":"msd/#u_1","text":"\u4f20\u9012\u901a\u7528\u6587\u4ef6\uff0c\u6ce8\u610f\u6587\u4ef6\u540d\u9700\u547d\u540d\u4e3a\u82f1\u6587\uff0c\u4e2d\u6587\u4f1a\u4e71\u7801\u3002 conn\uff0c disconn, clean\u547d\u4ee4\u9488\u5bf9\u901a\u7528U\u76d8\u4f9d\u65e7\u6709\u6548\u3002","title":"\u901a\u7528U\u76d8"},{"location":"msd/#u_2","text":"-s\u540e\u8ddf\u7684\u662f\u5236\u4f5c\u901a\u7528U\u76d8\u7684\u5927\u5c0f\uff0c\u5355\u4f4d\u4e3aGb\uff0c\u5bb9\u91cf\u8d8a\u5927\uff0c\u5236\u4f5c\u65f6\u95f4\u8d8a\u957f\uff0c\u8bf7\u7ed3\u5408\u5b9e\u9645\u60c5\u51b5\u8bbe\u7f6e\u3002 -t \u5fc5\u987b\u4e3aother sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 4 -t other","title":"\u5236\u4f5c\u901a\u7528U\u76d8"},{"location":"msd/#kvm","text":"\u9996\u5148\u4f60\u9700\u8981\u5c06\u6587\u4ef6\u4ece\u7528\u6237\u63a7\u5236\u7535\u8111\u53d1\u9001\u5230kvm scp xxx blikvm@xxxx:/mnt/msd/user/ \u5c06\u6587\u4ef6\u540c\u6b65\u5230\u88ab\u63a7\u7535\u8111\uff0c\u5e76\u8fde\u63a5\u4e0a\u7535\u8111 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c forward \u540e\u9762\u6709\u9700\u8981\u65b0\u7684\u5185\u5bb9\u4ece\u7528\u6237\u7535\u8111\uff0c\u4f20\u9012\u5230\u88ab\u63a7\u7535\u8111\uff0c\u91cd\u590d\u7b2c1\u548c\u7b2c2\u6b65\u5373\u53ef","title":"\u6587\u4ef6\u4ece\u7528\u6237\u7535\u8111==\u300bKVM==\u300b\u88ab\u63a7\u7535\u8111"},{"location":"msd/#kvm_1","text":"\u9996\u5148\u5728\u88ab\u63a7\u7535\u8111\u4e0a\u5c06\u6587\u4ef6\u62f7\u8d1d\u5230\u6a21\u62df\u7684\u865a\u62dfU\u76d8\u91cc\uff0c\u7136\u540e\u6267\u884c\u4e0b\u9762\u7684\u6307\u4ee4\uff0c\u5c06\u6587\u4ef6\u62f7\u8d1d\u5230kvm\u7684/mnt/msd/user/\u76ee\u5f55\u4e0b sudo bash /usr/bin/blikvm/kvmd-msd.sh -c rever \u5c06\u6587\u4ef6\u4ecekvm\u62f7\u8d1d\u5230\u7528\u6237\u7535\u8111 scp blikvm@xxxx:/mnt/msd/user/* .","title":"\u6587\u4ef6\u4ece\u88ab\u63a7\u7535\u8111==\u300bKVM==\u7528\u6237\u7535\u8111"},{"location":"port-forwarding/","text":"\u7aef\u53e3\u8f6c\u53d1 \u5728v1.4.7\u7248\u672c\u540e,\u5982\u679c\u60a8\u7684ISP\u4e3a\u8def\u7531\u5668\u63d0\u4f9b\u4e86\u5916\u90e8IP\u5730\u5740\uff0c\u60a8\u53ef\u4ee5\u914d\u7f6e\u7aef\u53e3\u8f6c\u53d1\u4ee5\u8bbf\u95eeBliKVM\u3002 Web\u5982\u679c\u9009\u62e9\u4e3ahttp\u534f\u8bae\uff0c\u5360\u7528\u7684\u662f80\u7aef\u53e3\uff0c\u5982\u679c\u9009\u62e9\u7684\u4e3ahttps\u534f\u8bae\u5360\u7528\u7684\u662f443\uff1b \u5982\u679c\u60a8\u6ca1\u6709\u5916\u90e8IP\u5730\u5740\uff0c\u6211\u4eec\u5efa\u8bae\u5c1d\u8bd5\u4f7f\u7528 Tailscale VPN \u3002","title":"\u7aef\u53e3\u8f6c\u53d1"},{"location":"port-forwarding/#_1","text":"\u5728v1.4.7\u7248\u672c\u540e,\u5982\u679c\u60a8\u7684ISP\u4e3a\u8def\u7531\u5668\u63d0\u4f9b\u4e86\u5916\u90e8IP\u5730\u5740\uff0c\u60a8\u53ef\u4ee5\u914d\u7f6e\u7aef\u53e3\u8f6c\u53d1\u4ee5\u8bbf\u95eeBliKVM\u3002 Web\u5982\u679c\u9009\u62e9\u4e3ahttp\u534f\u8bae\uff0c\u5360\u7528\u7684\u662f80\u7aef\u53e3\uff0c\u5982\u679c\u9009\u62e9\u7684\u4e3ahttps\u534f\u8bae\u5360\u7528\u7684\u662f443\uff1b \u5982\u679c\u60a8\u6ca1\u6709\u5916\u90e8IP\u5730\u5740\uff0c\u6211\u4eec\u5efa\u8bae\u5c1d\u8bd5\u4f7f\u7528 Tailscale VPN \u3002","title":"\u7aef\u53e3\u8f6c\u53d1"},{"location":"rtc/","text":"RTC\u65f6\u949f RTC\uff08Real-Time Clock\uff0c\u5b9e\u65f6\u65f6\u949f\uff09\u7684\u4f5c\u7528\u662f\u63d0\u4f9b\u8bbe\u5907\u6216\u7cfb\u7edf\u7684\u5b9e\u65f6\u65f6\u95f4\u548c\u65e5\u671f\u4fe1\u606f\u3002\u5b83\u662f\u4e00\u4e2a\u72ec\u7acb\u7684\u65f6\u949f\u82af\u7247\u6216\u6a21\u5757\uff0c\u5177\u6709\u81ea\u5df1\u7684\u7535\u6e90\uff0c\u53ef\u4ee5\u5728\u8bbe\u5907\u5173\u95ed\u6216\u65ad\u7535\u65f6\u4ecd\u7136\u4fdd\u6301\u65f6\u95f4\u7684\u51c6\u786e\u6027\u3002\u56e0\u56fd\u9645\u5feb\u9012\u7535\u6c60\u4e0d\u65b9\u4fbf\u90ae\u5bc4\u95ee\u9898\uff0c\u51fa\u5382\u786c\u4ef6\u65e0\u7535\u6c60\uff0c\u9700\u7528\u6237\u81ea\u5df1\u8d2d\u4e70(\u7ebd\u6263\u7535\u6c60\u578b\u53f7CR1220)\u3002BliKVM\u4e0d\u540c\u786c\u4ef6\u7248\u672c\u4e0a\u4f7f\u7528\u7684RTC\u65f6\u949f\u578b\u53f7\u4e0d\u5b8c\u5168\u4e00\u6837\uff0c\u4f7f\u7528\u65b9\u6cd5\u4e5f\u7565\u6709\u4e0d\u540c\u3002 BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563 1. \u68c0\u67e5i2c\u603b\u7ebf\u4e0a\u662f\u5426\u6b63\u5e38\u8bc6\u522b\u5230\u4e86pcf8563 RTC\u65f6\u949f\u786c\u4ef6\uff0cpcf8563\u7684i2c\u5730\u5740\u662fx51\uff0c\u672c\u8282\u6240\u6709\u547d\u4ee4\u5747\u9700\u5728root\u6743\u9650\u4e0b\uff0c\u6267\u884c\u4e0b\u9762\u7684\u547d\u4ee4\u80fd\u6b63\u786e\u67e5\u770b\u5230x51\u5373\u8bc1\u660ertc\u65f6\u949f\u5df2\u88abi2c\u603b\u7ebf\u6b63\u786e\u8bc6\u522b\u5230\u3002 root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. \u5411Linux \u7cfb\u7edf\u7684i2c\u5b50\u7cfb\u7edf\u6ce8\u518c\u4e00\u4e2a\u65b0\u7684i2c\u8bbe\u5907\uff0c\u8be5\u8bbe\u5907\u7684\u578b\u53f7\u662f pcf8563\uff0c\u8bbe\u5907\u7684i2c\u5730\u5740\u4e3a 0x51\u3002\u518d\u4f7f\u7528 ls /dev | grep rtc \u547d\u4ee4\u67e5\u770b\u662f\u5426\u6b63\u786e\u51fa\u73b0rtc1\u8bbe\u5907\uff0c\u51fa\u73b0\u5373\u6ce8\u518c\u6210\u529f\u3002 echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. \u5c06\u5f53\u524d\u7cfb\u7edf\u65f6\u95f4\u8bbe\u7f6e\u4e3artc\u65f6\u949f\u65f6\u95f4\u3002 hwclock -f /dev/rtc0 -w 4. \u4ecertc\u65f6\u949f\u8bfb\u53d6\u65f6\u95f4\uff0c\u5982\u679c\u80fd\u8bfb\u53d6\u5230\u65f6\u95f4\u5373\u8868\u660ertc\u6a21\u5757\u6b63\u5e38\u3002 root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30 BliKVM V4 - pcf8563 1. \u68c0\u67e5i2c\u603b\u7ebf\u4e0a\u662f\u5426\u6b63\u5e38\u8bc6\u522b\u5230\u4e86pcf8563 RTC\u65f6\u949f\u786c\u4ef6\uff0cpcf8563\u7684i2c\u5730\u5740\u662fx51\uff0c\u672c\u8282\u6240\u6709\u547d\u4ee4\u5747\u9700\u5728root\u6743\u9650\u4e0b\uff0c\u6267\u884c\u4e0b\u9762\u7684\u547d\u4ee4\u80fd\u6b63\u786e\u67e5\u770b\u5230x51\u5373\u8bc1\u660ertc\u65f6\u949f\u5df2\u88abi2c\u603b\u7ebf\u6b63\u786e\u8bc6\u522b\u5230\u3002 root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. \u5411Linux \u7cfb\u7edf\u7684i2c\u5b50\u7cfb\u7edf\u6ce8\u518c\u4e00\u4e2a\u65b0\u7684i2c\u8bbe\u5907\uff0c\u8be5\u8bbe\u5907\u7684\u578b\u53f7\u662f pcf8563\uff0c\u8bbe\u5907\u7684i2c\u5730\u5740\u4e3a 0x51\u3002\u518d\u4f7f\u7528 ls /dev | grep rtc \u547d\u4ee4\u67e5\u770b\u662f\u5426\u6b63\u786e\u51fa\u73b0rtc1\u8bbe\u5907\uff0c\u51fa\u73b0\u5373\u6ce8\u518c\u6210\u529f\u3002 echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. \u5c06\u5f53\u524d\u7cfb\u7edf\u65f6\u95f4\u8bbe\u7f6e\u4e3artc\u65f6\u949f\u65f6\u95f4\u3002 hwclock -f /dev/rtc1 -w 4. \u4ecertc\u65f6\u949f\u8bfb\u53d6\u65f6\u95f4\uff0c\u5982\u679c\u80fd\u8bfb\u53d6\u5230\u65f6\u95f4\u5373\u8868\u660ertc\u6a21\u5757\u6b63\u5e38\u3002 root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"RTC\u65f6\u949f"},{"location":"rtc/#rtc","text":"RTC\uff08Real-Time Clock\uff0c\u5b9e\u65f6\u65f6\u949f\uff09\u7684\u4f5c\u7528\u662f\u63d0\u4f9b\u8bbe\u5907\u6216\u7cfb\u7edf\u7684\u5b9e\u65f6\u65f6\u95f4\u548c\u65e5\u671f\u4fe1\u606f\u3002\u5b83\u662f\u4e00\u4e2a\u72ec\u7acb\u7684\u65f6\u949f\u82af\u7247\u6216\u6a21\u5757\uff0c\u5177\u6709\u81ea\u5df1\u7684\u7535\u6e90\uff0c\u53ef\u4ee5\u5728\u8bbe\u5907\u5173\u95ed\u6216\u65ad\u7535\u65f6\u4ecd\u7136\u4fdd\u6301\u65f6\u95f4\u7684\u51c6\u786e\u6027\u3002\u56e0\u56fd\u9645\u5feb\u9012\u7535\u6c60\u4e0d\u65b9\u4fbf\u90ae\u5bc4\u95ee\u9898\uff0c\u51fa\u5382\u786c\u4ef6\u65e0\u7535\u6c60\uff0c\u9700\u7528\u6237\u81ea\u5df1\u8d2d\u4e70(\u7ebd\u6263\u7535\u6c60\u578b\u53f7CR1220)\u3002BliKVM\u4e0d\u540c\u786c\u4ef6\u7248\u672c\u4e0a\u4f7f\u7528\u7684RTC\u65f6\u949f\u578b\u53f7\u4e0d\u5b8c\u5168\u4e00\u6837\uff0c\u4f7f\u7528\u65b9\u6cd5\u4e5f\u7565\u6709\u4e0d\u540c\u3002","title":"RTC\u65f6\u949f"},{"location":"rtc/#blikvm-v2-pcie-and-blikvm-v3-hat-pcf8563","text":"1. \u68c0\u67e5i2c\u603b\u7ebf\u4e0a\u662f\u5426\u6b63\u5e38\u8bc6\u522b\u5230\u4e86pcf8563 RTC\u65f6\u949f\u786c\u4ef6\uff0cpcf8563\u7684i2c\u5730\u5740\u662fx51\uff0c\u672c\u8282\u6240\u6709\u547d\u4ee4\u5747\u9700\u5728root\u6743\u9650\u4e0b\uff0c\u6267\u884c\u4e0b\u9762\u7684\u547d\u4ee4\u80fd\u6b63\u786e\u67e5\u770b\u5230x51\u5373\u8bc1\u660ertc\u65f6\u949f\u5df2\u88abi2c\u603b\u7ebf\u6b63\u786e\u8bc6\u522b\u5230\u3002 root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. \u5411Linux \u7cfb\u7edf\u7684i2c\u5b50\u7cfb\u7edf\u6ce8\u518c\u4e00\u4e2a\u65b0\u7684i2c\u8bbe\u5907\uff0c\u8be5\u8bbe\u5907\u7684\u578b\u53f7\u662f pcf8563\uff0c\u8bbe\u5907\u7684i2c\u5730\u5740\u4e3a 0x51\u3002\u518d\u4f7f\u7528 ls /dev | grep rtc \u547d\u4ee4\u67e5\u770b\u662f\u5426\u6b63\u786e\u51fa\u73b0rtc1\u8bbe\u5907\uff0c\u51fa\u73b0\u5373\u6ce8\u518c\u6210\u529f\u3002 echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. \u5c06\u5f53\u524d\u7cfb\u7edf\u65f6\u95f4\u8bbe\u7f6e\u4e3artc\u65f6\u949f\u65f6\u95f4\u3002 hwclock -f /dev/rtc0 -w 4. \u4ecertc\u65f6\u949f\u8bfb\u53d6\u65f6\u95f4\uff0c\u5982\u679c\u80fd\u8bfb\u53d6\u5230\u65f6\u95f4\u5373\u8868\u660ertc\u6a21\u5757\u6b63\u5e38\u3002 root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563"},{"location":"rtc/#blikvm-v4-pcf8563","text":"1. \u68c0\u67e5i2c\u603b\u7ebf\u4e0a\u662f\u5426\u6b63\u5e38\u8bc6\u522b\u5230\u4e86pcf8563 RTC\u65f6\u949f\u786c\u4ef6\uff0cpcf8563\u7684i2c\u5730\u5740\u662fx51\uff0c\u672c\u8282\u6240\u6709\u547d\u4ee4\u5747\u9700\u5728root\u6743\u9650\u4e0b\uff0c\u6267\u884c\u4e0b\u9762\u7684\u547d\u4ee4\u80fd\u6b63\u786e\u67e5\u770b\u5230x51\u5373\u8bc1\u660ertc\u65f6\u949f\u5df2\u88abi2c\u603b\u7ebf\u6b63\u786e\u8bc6\u522b\u5230\u3002 root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. \u5411Linux \u7cfb\u7edf\u7684i2c\u5b50\u7cfb\u7edf\u6ce8\u518c\u4e00\u4e2a\u65b0\u7684i2c\u8bbe\u5907\uff0c\u8be5\u8bbe\u5907\u7684\u578b\u53f7\u662f pcf8563\uff0c\u8bbe\u5907\u7684i2c\u5730\u5740\u4e3a 0x51\u3002\u518d\u4f7f\u7528 ls /dev | grep rtc \u547d\u4ee4\u67e5\u770b\u662f\u5426\u6b63\u786e\u51fa\u73b0rtc1\u8bbe\u5907\uff0c\u51fa\u73b0\u5373\u6ce8\u518c\u6210\u529f\u3002 echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. \u5c06\u5f53\u524d\u7cfb\u7edf\u65f6\u95f4\u8bbe\u7f6e\u4e3artc\u65f6\u949f\u65f6\u95f4\u3002 hwclock -f /dev/rtc1 -w 4. \u4ecertc\u65f6\u949f\u8bfb\u53d6\u65f6\u95f4\uff0c\u5982\u679c\u80fd\u8bfb\u53d6\u5230\u65f6\u95f4\u5373\u8868\u660ertc\u6a21\u5757\u6b63\u5e38\u3002 root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V4 - pcf8563"},{"location":"serial_over_usb/","text":"\u4e32\u53e3\u7ec8\u7aef\u8fde\u63a5 \u53ef\u4ee5\u901a\u8fc7\u4e32\u53e3\u7ec8\u7aef\u5bf9BliKVM\u8bbe\u5907\u8fdb\u884c\u8bbf\u95ee\u3002 1.\u786c\u4ef6\u8fde\u63a5\uff0c\u60a8\u5e94\u8be5\u4f7f\u7528USB\u8f6cttl\u6a21\u5757\u5c06\u8ba1\u7b97\u673a\u7684USB\u8fde\u63a5\u5230BliKVM\u7684uart\u3002\u5176\u4e2d\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fHat\u7248\u672c\uff0c\u8bf7\u6ce8\u610f\u8fde\u63a5GPIO14\u548cGPIO15\u8fd9\u4e2a\u4e32\u53e3\uff0c\u82e5\u662fPCIe\u7248\u672c\uff0c\u8fde\u63a5\u4e1d\u5370\u6807\u6ce8\u7684 GRT \u5f15\u811a\u5373\u53ef 2.\u7535\u8111\u4e0a\u5b89\u88c5\u53ef\u7ec8\u7aef\u767b\u9646\u7684\u5de5\u5177\uff0c\u5982\u5728windows\u4e0a\u53ef\u4ee5\u5b89\u88c5putty\u5de5\u5177 3. putty\u4f7f\u7528\u8bf4\u660e,\u8f93\u5165\u6b63\u786e\u7684COM\u53e3\uff0c\u9ed8\u8ba4\u6ce2\u7279\u7387115200\uff0c\u9009\u62e9\u8fde\u63a5\u65b9\u5f0f\u4e3aserial,\u7136\u540e\u70b9\u51fbopen\u5373\u53ef\uff08\u4ee5\u4f7f\u7528PiKVM\u56fa\u4ef6\u4e3a\u4f8b\uff09 \u5982\u679c\u4f60\u7684\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8bc6\u522busb\u8f6cttl\u6a21\u5757\uff0c\u8bf7\u6309\u7167\u4e0b\u5217\u6b65\u9aa4\u5bf9\u7535\u8111\u5b89\u88c5\u9a71\u52a8 \u5c06usb-a\u5934\u8fde\u63a5\u5230\u60a8\u7684\u4e3b\u673a\uff08\u5728\u672c\u4f8b\u4e2d\uff0c\u5b83\u4f4d\u4e8ewindows\u4e3b\u673a\u4e0a\uff09\u3002\u56e0\u6b64\uff0c\u8bbe\u5907\u7ba1\u7406\u5668\u5c06\u5728\u5176\u4ed6\u8bbe\u5907\u4e2d\u663e\u793a\u4e00\u4e2a\u65b0\u7684USB\u4e32\u884c\u8bbe\u5907\u3002 \u4e0b\u8f7d\u5e76\u63d0\u53d6/\u8fd0\u884c\u9a71\u52a8\u7a0b\u5e8f\u3002\u5728\u8fd9\u4e2a\u4f8b\u5b50\u4e2d\uff0c\u6211\u4e0b\u8f7d\u5e76\u63d0\u53d6\u4e86ZIP\u6587\u4ef6\u3002 https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all \u66f4\u65b0\u65b0USB\u4e32\u884c\u8bbe\u5907\u7684\u9a71\u52a8\u7a0b\u5e8f\uff0c\u5c06\u5176\u6307\u5411\u63d0\u53d6\u6587\u4ef6\u7684\u4f4d\u7f6e\uff0c\u7136\u540e\u5355\u51fb\u4e0b\u4e00\u6b65\uff0c\u7136\u540e\u5355\u51fb\u5173\u95ed\u3002 \u5982\u679c\u4e00\u5207\u6b63\u786e\uff0c\u65b0\u7684USB\u4e32\u884c\u8bbe\u5907\u73b0\u5728\u5e94\u8be5\u663e\u793a\u5728\u7aef\u53e3\u4e0b\u7684USB-serial CH340\uff08COMX\uff09\u3002","title":"\u4e32\u53e3\u7ec8\u7aef"},{"location":"serial_over_usb/#_1","text":"\u53ef\u4ee5\u901a\u8fc7\u4e32\u53e3\u7ec8\u7aef\u5bf9BliKVM\u8bbe\u5907\u8fdb\u884c\u8bbf\u95ee\u3002 1.\u786c\u4ef6\u8fde\u63a5\uff0c\u60a8\u5e94\u8be5\u4f7f\u7528USB\u8f6cttl\u6a21\u5757\u5c06\u8ba1\u7b97\u673a\u7684USB\u8fde\u63a5\u5230BliKVM\u7684uart\u3002\u5176\u4e2d\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fHat\u7248\u672c\uff0c\u8bf7\u6ce8\u610f\u8fde\u63a5GPIO14\u548cGPIO15\u8fd9\u4e2a\u4e32\u53e3\uff0c\u82e5\u662fPCIe\u7248\u672c\uff0c\u8fde\u63a5\u4e1d\u5370\u6807\u6ce8\u7684 GRT \u5f15\u811a\u5373\u53ef 2.\u7535\u8111\u4e0a\u5b89\u88c5\u53ef\u7ec8\u7aef\u767b\u9646\u7684\u5de5\u5177\uff0c\u5982\u5728windows\u4e0a\u53ef\u4ee5\u5b89\u88c5putty\u5de5\u5177 3. putty\u4f7f\u7528\u8bf4\u660e,\u8f93\u5165\u6b63\u786e\u7684COM\u53e3\uff0c\u9ed8\u8ba4\u6ce2\u7279\u7387115200\uff0c\u9009\u62e9\u8fde\u63a5\u65b9\u5f0f\u4e3aserial,\u7136\u540e\u70b9\u51fbopen\u5373\u53ef\uff08\u4ee5\u4f7f\u7528PiKVM\u56fa\u4ef6\u4e3a\u4f8b\uff09 \u5982\u679c\u4f60\u7684\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8bc6\u522busb\u8f6cttl\u6a21\u5757\uff0c\u8bf7\u6309\u7167\u4e0b\u5217\u6b65\u9aa4\u5bf9\u7535\u8111\u5b89\u88c5\u9a71\u52a8 \u5c06usb-a\u5934\u8fde\u63a5\u5230\u60a8\u7684\u4e3b\u673a\uff08\u5728\u672c\u4f8b\u4e2d\uff0c\u5b83\u4f4d\u4e8ewindows\u4e3b\u673a\u4e0a\uff09\u3002\u56e0\u6b64\uff0c\u8bbe\u5907\u7ba1\u7406\u5668\u5c06\u5728\u5176\u4ed6\u8bbe\u5907\u4e2d\u663e\u793a\u4e00\u4e2a\u65b0\u7684USB\u4e32\u884c\u8bbe\u5907\u3002 \u4e0b\u8f7d\u5e76\u63d0\u53d6/\u8fd0\u884c\u9a71\u52a8\u7a0b\u5e8f\u3002\u5728\u8fd9\u4e2a\u4f8b\u5b50\u4e2d\uff0c\u6211\u4e0b\u8f7d\u5e76\u63d0\u53d6\u4e86ZIP\u6587\u4ef6\u3002 https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all \u66f4\u65b0\u65b0USB\u4e32\u884c\u8bbe\u5907\u7684\u9a71\u52a8\u7a0b\u5e8f\uff0c\u5c06\u5176\u6307\u5411\u63d0\u53d6\u6587\u4ef6\u7684\u4f4d\u7f6e\uff0c\u7136\u540e\u5355\u51fb\u4e0b\u4e00\u6b65\uff0c\u7136\u540e\u5355\u51fb\u5173\u95ed\u3002 \u5982\u679c\u4e00\u5207\u6b63\u786e\uff0c\u65b0\u7684USB\u4e32\u884c\u8bbe\u5907\u73b0\u5728\u5e94\u8be5\u663e\u793a\u5728\u7aef\u53e3\u4e0b\u7684USB-serial CH340\uff08COMX\uff09\u3002","title":"\u4e32\u53e3\u7ec8\u7aef\u8fde\u63a5"},{"location":"ssh/","text":"SSH\u914d\u7f6e \u57281.4.7\u7248\u672c\u53ca\u4ee5\u540e\uff0cweb\u652f\u6301\u76f4\u63a5\u8fdb\u5165blikvm\u7684ssh\u7ec8\u7aef\uff0c\u9ed8\u8ba4\u8fdb\u5165\u7ec8\u7aef\u7684\u8d26\u53f7\u5bc6\u7801\u4e3a blikvm/blikvm\uff0c \u5982\u679c\u4fee\u6539\u4e86\u6b64\u7528\u6237\u7684\u5bc6\u7801\u4fe1\u606f\uff0c\u9700\u8981\u5728app.json\u6587\u4ef6\u4e2d\u4fee\u6539\u5bf9\u5e94\u7684\u8d26\u53f7\u5bc6\u7801 sudo -s vim /mnt/exec/release/config/app.json // \u627e\u5230\u4e0b\u9762\u914d\u7f6e\uff0c\u4fee\u6539\u6210\u4f60\u4fee\u6539\u540e\u7684\u3002 \"sshUser\": \"blikvm\", \"sshPassword\": \"blikvm\"","title":"SSH\u7ec8\u7aef"},{"location":"ssh/#ssh","text":"\u57281.4.7\u7248\u672c\u53ca\u4ee5\u540e\uff0cweb\u652f\u6301\u76f4\u63a5\u8fdb\u5165blikvm\u7684ssh\u7ec8\u7aef\uff0c\u9ed8\u8ba4\u8fdb\u5165\u7ec8\u7aef\u7684\u8d26\u53f7\u5bc6\u7801\u4e3a blikvm/blikvm\uff0c \u5982\u679c\u4fee\u6539\u4e86\u6b64\u7528\u6237\u7684\u5bc6\u7801\u4fe1\u606f\uff0c\u9700\u8981\u5728app.json\u6587\u4ef6\u4e2d\u4fee\u6539\u5bf9\u5e94\u7684\u8d26\u53f7\u5bc6\u7801 sudo -s vim /mnt/exec/release/config/app.json // \u627e\u5230\u4e0b\u9762\u914d\u7f6e\uff0c\u4fee\u6539\u6210\u4f60\u4fee\u6539\u540e\u7684\u3002 \"sshUser\": \"blikvm\", \"sshPassword\": \"blikvm\"","title":"SSH\u914d\u7f6e"},{"location":"static_ip/","text":"BliKVM OS\u8bbe\u7f6e\u9759\u6001IP v1 v2 v3\u53c2\u8003 \u4f7f\u7528SSH\u8fde\u63a5\u5230BliKVM\u7684\u7ec8\u7aef,\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\u3002 \u6253\u5f00\u7f51\u7edc\u914d\u7f6e\u6587\u4ef6 /etc/dhcpcd.conf \u4ee5\u8fdb\u884c\u7f16\u8f91\uff1a sudo vim /etc/dhcpcd.conf \u5728\u6587\u4ef6\u672b\u5c3e\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff0c\u66ff\u6362\u4e3a\u60a8\u60f3\u8981\u8bbe\u7f6e\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\uff1a interface eth0 static ip_address=192.168.0.100/24 static routers=192.168.0.1 static domain_name_servers=192.168.0.1 \u6ce8\u610f\uff1a\u6839\u636e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\uff0c\u53ef\u80fd\u9700\u8981\u4fee\u6539\u4e0a\u8ff0\u793a\u4f8b\u4e2d\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u503c\u3002 \u4fdd\u5b58\u6587\u4ef6\u5e76\u9000\u51fa\u7f16\u8f91\u5668\u3002 \u91cd\u65b0\u542f\u52a8BliKVM\u4ee5\u4f7f\u9759\u6001IP\u8bbe\u7f6e\u751f\u6548\uff1a sudo reboot v4\u53c2\u8003 \u4f7f\u7528SSH\u8fde\u63a5\u5230BliKVM\u7684\u7ec8\u7aef,\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\u3002 \u6253\u5f00\u7f51\u7edc\u914d\u7f6e\u6587\u4ef6 /etc/network/interfaces \u4ee5\u8fdb\u884c\u7f16\u8f91\uff1a sudo vim /etc/network/interfaces \u5728\u6587\u4ef6\u672b\u5c3e\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff0c\u66ff\u6362\u4e3a\u60a8\u60f3\u8981\u8bbe\u7f6e\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\uff1a source /etc/network/interfaces.d/* auto eth0 allow-hotplug eth0 iface eth0 inet static address 192.168.0.100 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 192.168.0.1 \u6ce8\u610f\uff1a\u6839\u636e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\uff0c\u53ef\u80fd\u9700\u8981\u4fee\u6539\u4e0a\u8ff0\u793a\u4f8b\u4e2d\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u503c\u3002 \u4fdd\u5b58\u6587\u4ef6\u5e76\u9000\u51fa\u7f16\u8f91\u5668\u3002 \u91cd\u65b0\u542f\u52a8BliKVM\u4ee5\u4f7f\u9759\u6001IP\u8bbe\u7f6e\u751f\u6548\uff1a sudo reboot \u6839\u636e\u60a8\u7684\u7f51\u7edc\u73af\u5883\u548c\u9700\u6c42\uff0c\u60a8\u53ef\u4ee5\u6839\u636e\u4e0a\u8ff0\u6b65\u9aa4\u81ea\u5b9a\u4e49\u914d\u7f6e\u9759\u6001IP\u5730\u5740\u3002\u8bf7\u786e\u4fddIP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u8bbe\u7f6e\u4e0e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\u76f8\u5339\u914d\u3002","title":"\u8bbe\u7f6e\u9759\u6001IP"},{"location":"static_ip/#blikvm-osip","text":"","title":"BliKVM OS\u8bbe\u7f6e\u9759\u6001IP"},{"location":"static_ip/#v1-v2-v3","text":"\u4f7f\u7528SSH\u8fde\u63a5\u5230BliKVM\u7684\u7ec8\u7aef,\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\u3002 \u6253\u5f00\u7f51\u7edc\u914d\u7f6e\u6587\u4ef6 /etc/dhcpcd.conf \u4ee5\u8fdb\u884c\u7f16\u8f91\uff1a sudo vim /etc/dhcpcd.conf \u5728\u6587\u4ef6\u672b\u5c3e\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff0c\u66ff\u6362\u4e3a\u60a8\u60f3\u8981\u8bbe\u7f6e\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\uff1a interface eth0 static ip_address=192.168.0.100/24 static routers=192.168.0.1 static domain_name_servers=192.168.0.1 \u6ce8\u610f\uff1a\u6839\u636e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\uff0c\u53ef\u80fd\u9700\u8981\u4fee\u6539\u4e0a\u8ff0\u793a\u4f8b\u4e2d\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u503c\u3002 \u4fdd\u5b58\u6587\u4ef6\u5e76\u9000\u51fa\u7f16\u8f91\u5668\u3002 \u91cd\u65b0\u542f\u52a8BliKVM\u4ee5\u4f7f\u9759\u6001IP\u8bbe\u7f6e\u751f\u6548\uff1a sudo reboot","title":"v1 v2 v3\u53c2\u8003"},{"location":"static_ip/#v4","text":"\u4f7f\u7528SSH\u8fde\u63a5\u5230BliKVM\u7684\u7ec8\u7aef,\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\u3002 \u6253\u5f00\u7f51\u7edc\u914d\u7f6e\u6587\u4ef6 /etc/network/interfaces \u4ee5\u8fdb\u884c\u7f16\u8f91\uff1a sudo vim /etc/network/interfaces \u5728\u6587\u4ef6\u672b\u5c3e\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff0c\u66ff\u6362\u4e3a\u60a8\u60f3\u8981\u8bbe\u7f6e\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\uff1a source /etc/network/interfaces.d/* auto eth0 allow-hotplug eth0 iface eth0 inet static address 192.168.0.100 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 192.168.0.1 \u6ce8\u610f\uff1a\u6839\u636e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\uff0c\u53ef\u80fd\u9700\u8981\u4fee\u6539\u4e0a\u8ff0\u793a\u4f8b\u4e2d\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u503c\u3002 \u4fdd\u5b58\u6587\u4ef6\u5e76\u9000\u51fa\u7f16\u8f91\u5668\u3002 \u91cd\u65b0\u542f\u52a8BliKVM\u4ee5\u4f7f\u9759\u6001IP\u8bbe\u7f6e\u751f\u6548\uff1a sudo reboot \u6839\u636e\u60a8\u7684\u7f51\u7edc\u73af\u5883\u548c\u9700\u6c42\uff0c\u60a8\u53ef\u4ee5\u6839\u636e\u4e0a\u8ff0\u6b65\u9aa4\u81ea\u5b9a\u4e49\u914d\u7f6e\u9759\u6001IP\u5730\u5740\u3002\u8bf7\u786e\u4fddIP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u8bbe\u7f6e\u4e0e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\u76f8\u5339\u914d\u3002","title":"v4\u53c2\u8003"},{"location":"tailscale/","text":"Tailscale VPN Tailscale \u53ef\u4ee5\u7528\u4e8e\u5c06\u60a8\u7684\u4e3b\u673a\u548cBliKVM\u5728\u516c\u7f51\u4e0b\u8fdb\u884c\u8bbf\u95ee\u3002\u8fd9\u662f\u4e00\u4e2a\u65b9\u4fbf\u4e14\u514d\u8d39\u7684\u7ec4\u7f51\u5de5\u5177\uff0c\u7528\u4e8e\u7ec4\u7ec7\u5c0f\u578bVPN\u7f51\u7edc\u3002\u672c\u6587\u6863\u63d0\u4f9b\u4e86\u4e00\u4e2a\u793a\u4f8b\uff0c\u7528\u4e8e\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95ee\u60a8\u7684BliKVM\uff0c\u4f46\u60a8\u4e5f\u53ef\u4ee5\u4f7f\u7528Zerotier\u6216\u8005\u5176\u5b83VPN\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u57fa\u672c\u652f\u6301\u7684\u793a\u4f8b\uff0c\u9047\u5230\u4efb\u4f55\u95ee\u9898\u53ef\u4ee5\u53bbTailscale\u5b98\u7f51\u67e5\u627e\u3002 BliKVM\u5b89\u88c5Tailscale \u9996\u5148\u786e\u8ba4\u5f53\u524d\u7cfb\u7edf\u662f\u8bfb\u5199\u6743\u9650\uff0c\u82e5\u662f\u53ea\u8bfb\u7cfb\u7edf\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\uff0c\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u8fdb\u884c \u5b89\u88c5 : curl -fsSL https://tailscale.com/install.sh | sh \u6709\u4e00\u4e9b\u5730\u533a\u5982\u4e2d\u56fd\uff0c\u6709\u53ef\u80fd\u4f1a\u56e0\u4e3a\u7f51\u7edc\u539f\u56e0\u65e0\u6cd5\u987a\u5229\u4e0b\u8f7d\uff0c\u8bf7\u6b63\u786e\u914d\u7f6e\u7f51\u7edc \u4f7fBliKVM\u52a0\u5165\u5230\u4f60\u7684Tailscale\u5c40\u57df\u7f51\u4e2d \u5728\u5b98\u7f51\u6ce8\u518c\u4f60\u7684tailscale\u8d26\u6237\uff0c\u5e76\u5728\u8bbe\u7f6e\u4e2d\u751f\u6210\u4f60\u81ea\u5df1\u7684keys\uff0c\u5728BliKVM\u7ec8\u7aef\u4e0a\uff0c\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\uff0c\u5373\u53ef\u5c06BliKVM\u52a0\u5165\u5230tailscale\u751f\u6210\u7684\u5c40\u57df\u7f51\u4e2d\u3002 sudo tailscale up --authkey=your-auth-key --accept-routes \u82e5\u4e00\u5207\u987a\u5229\uff0c\u4f60\u5728BliKMV\u7ec8\u7aef\u8fd0\u884c ip addr show tailscale0 \uff0c\u5373\u53ef\u67e5\u770b\u5230tailscale0\u751f\u6210\u7684\u865a\u62df\u5c40\u57df\u7f51\u7684ip\u5730\u5740\uff0c\u4e00\u4e2a\u4f8b\u5b50\u5982\u4e0b\uff1a 3: tailscale0:  mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100.126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever \u5176\u4e2d100.126.223.28\u5c31\u662f\u53ef\u4ee5\u7528\u6765\u5728\u4e3b\u673a\u4e0a\u8bbf\u95eeBliKVM web\u754c\u9762\u7684UI\u5730\u5740\u3002 \u4e3b\u673a\u5b89\u88c5Tailscale \u5c06Tailscale \u4e0b\u8f7d \u5e76\u5b89\u88c5\u5230\u60a8\u7684\u63a7\u5236\u4e3b\u673a\u4e0a\uff0c\u767b\u5f55\u5bf9\u5e94\u7684\u8d26\u6237\uff0c\u7136\u540e\u60a8\u53ef\u4ee5\u5728Tailscale\u7684 \u63a7\u5236\u754c\u9762 \uff0c\u67e5\u770b\u60a8\u7684\u4e24\u53f0\u673a\u5668\u662f\u5426\u90fd\u5728\u7ebf\uff0c\u5982\u679c\u90fd\u5728\u7ebf\uff0c\u5373\u53ef\u4f7f\u7528\u4e0b\u9762\u5730\u5740\uff0c\u5728\u60a8\u7684\u63a7\u5236\u4e3b\u673a\u4e0a\u8bbf\u95eeBliKVM http://","title":"Tailscale VPN"},{"location":"tailscale/#tailscale-vpn","text":"Tailscale \u53ef\u4ee5\u7528\u4e8e\u5c06\u60a8\u7684\u4e3b\u673a\u548cBliKVM\u5728\u516c\u7f51\u4e0b\u8fdb\u884c\u8bbf\u95ee\u3002\u8fd9\u662f\u4e00\u4e2a\u65b9\u4fbf\u4e14\u514d\u8d39\u7684\u7ec4\u7f51\u5de5\u5177\uff0c\u7528\u4e8e\u7ec4\u7ec7\u5c0f\u578bVPN\u7f51\u7edc\u3002\u672c\u6587\u6863\u63d0\u4f9b\u4e86\u4e00\u4e2a\u793a\u4f8b\uff0c\u7528\u4e8e\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95ee\u60a8\u7684BliKVM\uff0c\u4f46\u60a8\u4e5f\u53ef\u4ee5\u4f7f\u7528Zerotier\u6216\u8005\u5176\u5b83VPN\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u57fa\u672c\u652f\u6301\u7684\u793a\u4f8b\uff0c\u9047\u5230\u4efb\u4f55\u95ee\u9898\u53ef\u4ee5\u53bbTailscale\u5b98\u7f51\u67e5\u627e\u3002","title":"Tailscale VPN"},{"location":"tailscale/#blikvmtailscale","text":"\u9996\u5148\u786e\u8ba4\u5f53\u524d\u7cfb\u7edf\u662f\u8bfb\u5199\u6743\u9650\uff0c\u82e5\u662f\u53ea\u8bfb\u7cfb\u7edf\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\uff0c\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u8fdb\u884c \u5b89\u88c5 : curl -fsSL https://tailscale.com/install.sh | sh \u6709\u4e00\u4e9b\u5730\u533a\u5982\u4e2d\u56fd\uff0c\u6709\u53ef\u80fd\u4f1a\u56e0\u4e3a\u7f51\u7edc\u539f\u56e0\u65e0\u6cd5\u987a\u5229\u4e0b\u8f7d\uff0c\u8bf7\u6b63\u786e\u914d\u7f6e\u7f51\u7edc","title":"BliKVM\u5b89\u88c5Tailscale"},{"location":"tailscale/#blikvmtailscale_1","text":"\u5728\u5b98\u7f51\u6ce8\u518c\u4f60\u7684tailscale\u8d26\u6237\uff0c\u5e76\u5728\u8bbe\u7f6e\u4e2d\u751f\u6210\u4f60\u81ea\u5df1\u7684keys\uff0c\u5728BliKVM\u7ec8\u7aef\u4e0a\uff0c\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\uff0c\u5373\u53ef\u5c06BliKVM\u52a0\u5165\u5230tailscale\u751f\u6210\u7684\u5c40\u57df\u7f51\u4e2d\u3002 sudo tailscale up --authkey=your-auth-key --accept-routes \u82e5\u4e00\u5207\u987a\u5229\uff0c\u4f60\u5728BliKMV\u7ec8\u7aef\u8fd0\u884c ip addr show tailscale0 \uff0c\u5373\u53ef\u67e5\u770b\u5230tailscale0\u751f\u6210\u7684\u865a\u62df\u5c40\u57df\u7f51\u7684ip\u5730\u5740\uff0c\u4e00\u4e2a\u4f8b\u5b50\u5982\u4e0b\uff1a 3: tailscale0:  mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100.126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever \u5176\u4e2d100.126.223.28\u5c31\u662f\u53ef\u4ee5\u7528\u6765\u5728\u4e3b\u673a\u4e0a\u8bbf\u95eeBliKVM web\u754c\u9762\u7684UI\u5730\u5740\u3002","title":"\u4f7fBliKVM\u52a0\u5165\u5230\u4f60\u7684Tailscale\u5c40\u57df\u7f51\u4e2d"},{"location":"tailscale/#tailscale","text":"\u5c06Tailscale \u4e0b\u8f7d \u5e76\u5b89\u88c5\u5230\u60a8\u7684\u63a7\u5236\u4e3b\u673a\u4e0a\uff0c\u767b\u5f55\u5bf9\u5e94\u7684\u8d26\u6237\uff0c\u7136\u540e\u60a8\u53ef\u4ee5\u5728Tailscale\u7684 \u63a7\u5236\u754c\u9762 \uff0c\u67e5\u770b\u60a8\u7684\u4e24\u53f0\u673a\u5668\u662f\u5426\u90fd\u5728\u7ebf\uff0c\u5982\u679c\u90fd\u5728\u7ebf\uff0c\u5373\u53ef\u4f7f\u7528\u4e0b\u9762\u5730\u5740\uff0c\u5728\u60a8\u7684\u63a7\u5236\u4e3b\u673a\u4e0a\u8bbf\u95eeBliKVM http://","title":"\u4e3b\u673a\u5b89\u88c5Tailscale"},{"location":"update/","text":"\u8f6f\u4ef6\u66f4\u65b0\u4ecb\u7ecd \u5982\u679c\u60a8\u8fd0\u884c\u7684\u662f\u975e\u5e38\u65e7\u7684\u7248\u672c\uff0c\u6211\u4eec\u5efa\u8bae\u60a8\u5148\u91cd\u65b0\u5237\u673a\uff0c\u7136\u540e\u5728\u9760\u8fd1\u60a8\u7684BliKVM\u8bbe\u5907\u65f6\u8fd0\u884c\u66f4\u65b0\u8fc7\u7a0b\u3002 \u4ecb\u7ecd BLIKVM\u9879\u76ee\u76ee\u524d\u53ef\u7528\u7248\u672c\u6258\u7ba1\u5728github\u4ed3\u5e93\u7684release\u5305\u91cc\uff0c\u66f4\u65b0\u8f6f\u4ef6\u529f\u80fd\u9700\u4fdd\u6301\u8bbe\u5907\u8054\u7f51\uff0c\u66f4\u65b0\u8f6f\u4ef6\u76ee\u524d\u63d0\u4f9b\u4e24\u79cd\u65b9\u5f0f \u65b9\u5f0f1\uff0c\u901a\u8fc7web\u754c\u9762\u70b9\u51fb\u66f4\u65b0\u6309\u94ae\uff0c\u7a0b\u5e8f\u81ea\u52a8\u8fdb\u884c\u66f4\u65b0,\u66f4\u65b0\u5b8c\u9700\u8981\u91cd\u542f\u3002 \u65b9\u5f0f2\uff0c\u624b\u52a8\u5728KVM\u7ec8\u7aef\u4e0a\u8fd0\u884c\u811a\u672c\u8fdb\u884c\u66f4\u65b0\uff0c\u66f4\u65b0\u5b8c\u540e\u9700\u8981\u91cd\u542f\u3002 \u5347\u7ea7\u9519\u8bef\u5e38\u89c1\u539f\u56e0 \u8bbe\u5907\u672a\u8054\u7f51; \u7f51\u7edc\u8bbf\u95eegithub\u53d7\u9650; \u6211\u4eec\u5f3a\u70c8\u5efa\u8bae\u60a8\u5728\u9760\u8fd1\u8981\u5347\u7ea7\u7684BliKVM\u786c\u4ef6\u65f6\u6267\u884c\u66f4\u65b0\u3002\u539f\u56e0\u662f\uff0c\u5982\u679c\u51fa\u73b0\u4efb\u4f55\u95ee\u9898\uff0c\u4f60\u53ef\u4ee5\u8fdb\u884c\u5e72\u9884\u3002 \u5982\u679c\u60a8\u719f\u6089\u547d\u4ee4\u884c\u64cd\u4f5c\uff0c\u5efa\u8bae\u60a8\u624b\u52a8\u66f4\u65b0\u53ef\u4ee5\u5b9e\u65f6\u67e5\u770b\u547d\u4ee4\u884c\u72b6\u6001\u3002 \u82e5\u66f4\u65b0\u5f02\u5e38\uff0cweb\u754c\u9762\u65e0\u6cd5\u9000\u51fa\u66f4\u65b0\u72b6\u6001\uff0c\u53ef\u4ee5\u7ec8\u7aefssh\u8fdb\u5165kvm\u540e\u91cd\u542f\u6062\u590d\u3002 \u624b\u52a8\u8fd0\u884c\u811a\u672c\u66f4\u65b0 ssh\u8fdb\u5165\u8bbe\u5907\u7ec8\u7aef\u3002\u82e5\u5f53\u524d\u7cfb\u7edf\u7ec8\u7aef\u53ef\u4ee5\u770b\u5230ro\u5173\u952e\u5b57\uff0c\u4e3a\u53ea\u8bfb\u7cfb\u7edf\uff0c\u9700\u4f7f\u7528 rw \u8ba9\u7cfb\u7edf\u4e3a\u53ef\u5199\u6743\u9650\u3002 sudo -i curl -L https://raw.githubusercontent.com/ThomasVon2021/blikvm/master/script/update.py -o /tmp/update.py && python3 /tmp/update.py \u89c2\u5bdf\u7ec8\u7aef\u8f93\u51fa\uff0c\u5f53\u770b\u5230\u5347\u7ea7\u5347\u7ea7\u6210\u529f\u6d88\u606f\u63d0\u9192\u65f6\uff0c\u7ec8\u7aef\u8f93\u5165reboot\uff0c\u91cd\u542f\u751f\u6548\u3002 \u82e5\u60a8\u56e0\u7f51\u7edc\u539f\u56e0\uff0c\u4e00\u76f4\u65e0\u6cd5\u66f4\u65b0\u6210\u529f\uff0c\u53ef\u4ee5\u91c7\u7528\u5728\u5176\u5b83\u7f51\u7edcok\u7684PC\u4e0a\u4e0b\u8f7d\u6700\u65b0\u7684release\u5305\uff0c\u7136\u540e\u6309\u7167\u4ee5\u4e0b\u547d\u4ee4\u8fdb\u884c\u5b89\u88c5\u3002 \u4e0b\u8f7d\u5730\u5740: https://github.com/ThomasVon2021/blikvm/releases \u5176\u4e2dv1 v2 v3\u786c\u4ef6\u4f7f\u7528 release.tar.gz v4\u786c\u4ef6\u4f7f\u7528 release-h616-v4.tar.gz ssh\u8fdb\u5165\u8bbe\u5907\u7ec8\u7aef\uff0c\u5e76\u4f7f\u7528 tar -zxvf release.tar.gz \u89e3\u538brelease.tar.gz\u3002 sudo -i cd /your release path/ python3 install_release.py --releasepath=./ \u53ef\u4ee5\u89c2\u5bdf/usr/bin/blikvm/package.json\u524d\u540e\u7684\u7248\u672c\u5bf9\u6bd4\uff0c\u82e5\u5347\u7ea7\u5230\u4e86\u6307\u5b9a\u7248\u672c\uff0c\u5219\u6210\u529f\uff0c\u91cd\u542f\u751f\u6548\u3002","title":"\u66f4\u65b0\u8f6f\u4ef6"},{"location":"update/#_1","text":"\u5982\u679c\u60a8\u8fd0\u884c\u7684\u662f\u975e\u5e38\u65e7\u7684\u7248\u672c\uff0c\u6211\u4eec\u5efa\u8bae\u60a8\u5148\u91cd\u65b0\u5237\u673a\uff0c\u7136\u540e\u5728\u9760\u8fd1\u60a8\u7684BliKVM\u8bbe\u5907\u65f6\u8fd0\u884c\u66f4\u65b0\u8fc7\u7a0b\u3002","title":"\u8f6f\u4ef6\u66f4\u65b0\u4ecb\u7ecd"},{"location":"update/#_2","text":"BLIKVM\u9879\u76ee\u76ee\u524d\u53ef\u7528\u7248\u672c\u6258\u7ba1\u5728github\u4ed3\u5e93\u7684release\u5305\u91cc\uff0c\u66f4\u65b0\u8f6f\u4ef6\u529f\u80fd\u9700\u4fdd\u6301\u8bbe\u5907\u8054\u7f51\uff0c\u66f4\u65b0\u8f6f\u4ef6\u76ee\u524d\u63d0\u4f9b\u4e24\u79cd\u65b9\u5f0f \u65b9\u5f0f1\uff0c\u901a\u8fc7web\u754c\u9762\u70b9\u51fb\u66f4\u65b0\u6309\u94ae\uff0c\u7a0b\u5e8f\u81ea\u52a8\u8fdb\u884c\u66f4\u65b0,\u66f4\u65b0\u5b8c\u9700\u8981\u91cd\u542f\u3002 \u65b9\u5f0f2\uff0c\u624b\u52a8\u5728KVM\u7ec8\u7aef\u4e0a\u8fd0\u884c\u811a\u672c\u8fdb\u884c\u66f4\u65b0\uff0c\u66f4\u65b0\u5b8c\u540e\u9700\u8981\u91cd\u542f\u3002 \u5347\u7ea7\u9519\u8bef\u5e38\u89c1\u539f\u56e0 \u8bbe\u5907\u672a\u8054\u7f51; \u7f51\u7edc\u8bbf\u95eegithub\u53d7\u9650; \u6211\u4eec\u5f3a\u70c8\u5efa\u8bae\u60a8\u5728\u9760\u8fd1\u8981\u5347\u7ea7\u7684BliKVM\u786c\u4ef6\u65f6\u6267\u884c\u66f4\u65b0\u3002\u539f\u56e0\u662f\uff0c\u5982\u679c\u51fa\u73b0\u4efb\u4f55\u95ee\u9898\uff0c\u4f60\u53ef\u4ee5\u8fdb\u884c\u5e72\u9884\u3002 \u5982\u679c\u60a8\u719f\u6089\u547d\u4ee4\u884c\u64cd\u4f5c\uff0c\u5efa\u8bae\u60a8\u624b\u52a8\u66f4\u65b0\u53ef\u4ee5\u5b9e\u65f6\u67e5\u770b\u547d\u4ee4\u884c\u72b6\u6001\u3002 \u82e5\u66f4\u65b0\u5f02\u5e38\uff0cweb\u754c\u9762\u65e0\u6cd5\u9000\u51fa\u66f4\u65b0\u72b6\u6001\uff0c\u53ef\u4ee5\u7ec8\u7aefssh\u8fdb\u5165kvm\u540e\u91cd\u542f\u6062\u590d\u3002","title":"\u4ecb\u7ecd"},{"location":"update/#_3","text":"ssh\u8fdb\u5165\u8bbe\u5907\u7ec8\u7aef\u3002\u82e5\u5f53\u524d\u7cfb\u7edf\u7ec8\u7aef\u53ef\u4ee5\u770b\u5230ro\u5173\u952e\u5b57\uff0c\u4e3a\u53ea\u8bfb\u7cfb\u7edf\uff0c\u9700\u4f7f\u7528 rw \u8ba9\u7cfb\u7edf\u4e3a\u53ef\u5199\u6743\u9650\u3002 sudo -i curl -L https://raw.githubusercontent.com/ThomasVon2021/blikvm/master/script/update.py -o /tmp/update.py && python3 /tmp/update.py \u89c2\u5bdf\u7ec8\u7aef\u8f93\u51fa\uff0c\u5f53\u770b\u5230\u5347\u7ea7\u5347\u7ea7\u6210\u529f\u6d88\u606f\u63d0\u9192\u65f6\uff0c\u7ec8\u7aef\u8f93\u5165reboot\uff0c\u91cd\u542f\u751f\u6548\u3002 \u82e5\u60a8\u56e0\u7f51\u7edc\u539f\u56e0\uff0c\u4e00\u76f4\u65e0\u6cd5\u66f4\u65b0\u6210\u529f\uff0c\u53ef\u4ee5\u91c7\u7528\u5728\u5176\u5b83\u7f51\u7edcok\u7684PC\u4e0a\u4e0b\u8f7d\u6700\u65b0\u7684release\u5305\uff0c\u7136\u540e\u6309\u7167\u4ee5\u4e0b\u547d\u4ee4\u8fdb\u884c\u5b89\u88c5\u3002 \u4e0b\u8f7d\u5730\u5740: https://github.com/ThomasVon2021/blikvm/releases \u5176\u4e2dv1 v2 v3\u786c\u4ef6\u4f7f\u7528 release.tar.gz v4\u786c\u4ef6\u4f7f\u7528 release-h616-v4.tar.gz ssh\u8fdb\u5165\u8bbe\u5907\u7ec8\u7aef\uff0c\u5e76\u4f7f\u7528 tar -zxvf release.tar.gz \u89e3\u538brelease.tar.gz\u3002 sudo -i cd /your release path/ python3 install_release.py --releasepath=./ \u53ef\u4ee5\u89c2\u5bdf/usr/bin/blikvm/package.json\u524d\u540e\u7684\u7248\u672c\u5bf9\u6bd4\uff0c\u82e5\u5347\u7ea7\u5230\u4e86\u6307\u5b9a\u7248\u672c\uff0c\u5219\u6210\u529f\uff0c\u91cd\u542f\u751f\u6548\u3002","title":"\u624b\u52a8\u8fd0\u884c\u811a\u672c\u66f4\u65b0"},{"location":"usb-splitter-guide/","text":"USB\u548c\u7535\u6e90\u5206\u7ebf\u677f 1. \u7b80\u4ecb The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage. 2.\u5c3a\u5bf8\u56fe 3.\u6d4b\u8bd5\u89c6\u9891 USB splitter Video 4.3D \u6253\u5370\u5916\u58f3 A simple snap fit case for the USB splitter. \u4e0b\u8f7d\u6587\u4ef6","title":"USB\u4e00\u5206\u4e8c\u7528\u6237\u624b\u518c"},{"location":"usb-splitter-guide/#usb","text":"","title":"USB\u548c\u7535\u6e90\u5206\u7ebf\u677f"},{"location":"usb-splitter-guide/#1","text":"The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage.","title":"1. \u7b80\u4ecb"},{"location":"usb-splitter-guide/#2","text":"","title":"2.\u5c3a\u5bf8\u56fe"},{"location":"usb-splitter-guide/#3","text":"USB splitter Video","title":"3.\u6d4b\u8bd5\u89c6\u9891"},{"location":"usb-splitter-guide/#43d","text":"A simple snap fit case for the USB splitter. \u4e0b\u8f7d\u6587\u4ef6","title":"4.3D \u6253\u5370\u5916\u58f3"},{"location":"wake-on-lan/","text":"Wake-on-LAN \u4ecb\u7ecd Wake-on-LAN\u7b80\u79f0WOL\u6216WoL\uff0c\u529f\u80fd\u4e3a\u8ba9\u5df2\u7ecf\u8fdb\u5165\u4f11\u7720\u72b6\u6001\u6216\u5173\u673a\u72b6\u6001\u7684\u8ba1\u7b97\u673a\uff0cKVM\u901a\u8fc7\u5c40\u57df\u7f51\u53d1\u9001\u7279\u5b9a\u6d88\u606f\uff0c\u4f7f\u88ab\u63a7\u7535\u8111\u4ece\u4f11\u7720\u72b6\u6001\u6216\u5173\u673a\u72b6\u6001\u6539\u4e3a\u5f00\u673a\u72b6\u6001\u3002WoL\u9700\u88ab\u63a7\u7535\u8111\u652f\u6301\uff0c\u5426\u5219\u8be5\u529f\u80fd\u65e0\u6548\uff0c\u53e6\u5916\u9700\u786e\u8ba4WoL\u5df2\u88ab\u5f00\u542f\u548c\u6b63\u786e\u914d\u7f6e\u3002\u4f7f\u7528\u6b64\u529f\u80fd\uff0c\u4e0d\u9700\u8981\u4f7f\u7528atx\u529f\u80fd\u4e5f\u53ef\u4ee5\u5b9e\u73b0\u5f00\u673a\u3002\u82e5\u7528\u6237\u5728\u4f7f\u7528kvm\u7684WoL\u7684\u9047\u5230\u5f02\u5e38\uff0c\u53ef\u5c1d\u8bd5\u4f7f\u7528\u652f\u6301WoL\u7684\u8f6f\u4ef6\u8fdb\u884c\u6d4b\u8bd5\u3002 \u4f7f\u7528\u65b9\u6cd5","title":"Wake-on-LAN"},{"location":"wake-on-lan/#wake-on-lan","text":"","title":"Wake-on-LAN"},{"location":"wake-on-lan/#_1","text":"Wake-on-LAN\u7b80\u79f0WOL\u6216WoL\uff0c\u529f\u80fd\u4e3a\u8ba9\u5df2\u7ecf\u8fdb\u5165\u4f11\u7720\u72b6\u6001\u6216\u5173\u673a\u72b6\u6001\u7684\u8ba1\u7b97\u673a\uff0cKVM\u901a\u8fc7\u5c40\u57df\u7f51\u53d1\u9001\u7279\u5b9a\u6d88\u606f\uff0c\u4f7f\u88ab\u63a7\u7535\u8111\u4ece\u4f11\u7720\u72b6\u6001\u6216\u5173\u673a\u72b6\u6001\u6539\u4e3a\u5f00\u673a\u72b6\u6001\u3002WoL\u9700\u88ab\u63a7\u7535\u8111\u652f\u6301\uff0c\u5426\u5219\u8be5\u529f\u80fd\u65e0\u6548\uff0c\u53e6\u5916\u9700\u786e\u8ba4WoL\u5df2\u88ab\u5f00\u542f\u548c\u6b63\u786e\u914d\u7f6e\u3002\u4f7f\u7528\u6b64\u529f\u80fd\uff0c\u4e0d\u9700\u8981\u4f7f\u7528atx\u529f\u80fd\u4e5f\u53ef\u4ee5\u5b9e\u73b0\u5f00\u673a\u3002\u82e5\u7528\u6237\u5728\u4f7f\u7528kvm\u7684WoL\u7684\u9047\u5230\u5f02\u5e38\uff0c\u53ef\u5c1d\u8bd5\u4f7f\u7528\u652f\u6301WoL\u7684\u8f6f\u4ef6\u8fdb\u884c\u6d4b\u8bd5\u3002","title":"\u4ecb\u7ecd"},{"location":"wake-on-lan/#_2","text":"","title":"\u4f7f\u7528\u65b9\u6cd5"},{"location":"wifi/","text":"Wifi\u529f\u80fd \u7531\u4e8eBLIKVM\u6709\u591a\u6b3e\u786c\u4ef6\uff0c\u652f\u6301\u4e0d\u540c\u7684OS\uff0c\u5982BLIKVM OS\u548cPiKVM OS\uff0c\u4e0d\u540cOS\u94fe\u63a5wifi\u65b9\u5f0f\u4e0d\u4e00\u5b9a\u76f8\u540c\uff0c\u8bf7\u5728\u4f7f\u7528\u672c\u6587\u6863\u65b9\u6cd5\u524d\uff0c\u8bf7\u786e\u8ba4\u81ea\u5df1\u786c\u4ef6\u548c\u4f7f\u7528OS\u7684\u60c5\u51b5\u3002 \u8bf7\u786e\u8ba4\u4f60\u4f7f\u7528\u7684\u786c\u4ef6\u652f\u6301wifi\u529f\u80fd\uff0c\u5982CM400200\u7248\u672c\u4e0d\u5e26wifi\u529f\u80fd\uff1b \u82e5KVM\u786c\u4ef6\u7684SOC\u4e3aCM4\uff0c\u8bf7\u786e\u8ba4\u662f\u5426\u8fde\u63a5\u4e86wifi\u5929\u7ebf\uff1b PiKVM OS\u4e3aarch linux\uff1b BLIKVM OS\u6811\u8393\u6d3e\u7cfb\u5217\u4e3adebian\u7cfb\u7edf\uff0cv4\u7cfb\u5217\u4e3aarmbian\u7cfb\u7edf\uff1b v1\uff0cv2\uff0cv3\u786c\u4ef6\u4f7f\u7528\u7684\u4e3a\u6811\u8393\u6d3edebian\u7cfb\u7edf\uff0c\u4f7f\u7528raspi-config\u8fdb\u884cwifi\u94fe\u63a5 \u767b\u5f55ssh,\u547d\u4ee4: ssh blikvm@ip \u7cfb\u7edf\u91cd\u52a0\u8f7d\u4e3a\u53ef\u5199, \u547d\u4ee4: rw \u542f\u52a8raspi-config, \u547d\u4ee4: sudo raspi-config \u9009\u62e9 System Options \u9009\u62e9 Wireless LAN \u9009\u62e9wifi\u6240\u5728\u56fd\u5bb6,\u4e2d\u56fd\u9009CN, \u5982\u679c\u4ee5\u524d\u8bbe\u7f6e\u8fc7,\u8fd9\u4e00\u6b65\u4f1a\u8df3\u8fc7\u76f4\u63a5\u52307 \u8f93\u5165Wi-Fi\u7684ssid(\u540d\u79f0) \u8f93\u5165Wi-Fi\u7684\u5bc6\u7801,\u5982\u679c\u6ca1\u6709\u5bc6\u7801\u76f4\u63a5\u56de\u8f66 \u8fd9\u65f6\u4f1a\u56de\u5230\u6b65\u9aa44\u7684\u754c\u9762,\u6309tab\u952e\u9009\u62e9 ,\u56de\u8f66 \u67e5\u770b\u662f\u5426\u8fde\u4e0awifi, \u547d\u4ee4: ifconfig wlan0 ,\u5982\u679c\u770b\u5230\u83b7\u53d6\u5230ip\u5c31\u662f\u5df2\u7ecf\u8fde\u4e0a\u4e86 \u5c06\u7cfb\u7edf\u6302\u8f7d\u4e3a\u53ea\u8bfb, \u547d\u4ee4: ro v4\u786c\u4ef6\u4f7f\u7528\u7684\u4e3aarmbian\u7cfb\u7edf\uff0c\u4f7f\u7528armbian-config \u767b\u5f55ssh,\u547d\u4ee4: ssh blikvm@ip\uff0c\u767b\u5f55\u5230 Armbian \u7cfb\u7edf\u3002 \u8f93\u5165\u4ee5\u4e0b\u547d\u4ee4\u4ee5\u542f\u52a8 armbian-config \u5de5\u5177\uff1a sudo armbian-config \u5728 armbian-config \u83dc\u5355\u4e2d\uff0c\u4f7f\u7528\u65b9\u5411\u952e\u548c\u56de\u8f66\u952e\u5bfc\u822a\u548c\u9009\u62e9\u9009\u9879\u3002 \u4f7f\u7528\u65b9\u5411\u952e\u5411\u4e0b\u6eda\u52a8\u5230 \"Network\" \u9009\u9879\uff0c\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165\u5b50\u83dc\u5355\u3002 \u5728 \"Network\" \u5b50\u83dc\u5355\u4e2d\uff0c\u9009\u62e9 \"Wireless\" \u9009\u9879\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165 Wi-Fi \u914d\u7f6e\u83dc\u5355\u3002 \u5728 Wi-Fi \u914d\u7f6e\u83dc\u5355\u4e2d\uff0c\u9009\u62e9 \"Connect to Wi-Fi\" \u9009\u9879\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165 Wi-Fi \u8fde\u63a5\u8bbe\u7f6e\u3002 armbian-config \u5c06\u5217\u51fa\u53ef\u7528\u7684\u65e0\u7ebf\u7f51\u7edc\u63a5\u53e3\u548c\u5df2\u914d\u7f6e\u7684\u7f51\u7edc\u3002\u9009\u62e9\u8981\u8fde\u63a5\u7684\u65e0\u7ebf\u7f51\u7edc\u63a5\u53e3\u5e76\u6309\u56de\u8f66\u952e\u3002 armbian-config \u5c06\u663e\u793a\u53ef\u7528\u7684 Wi-Fi \u7f51\u7edc\u5217\u8868\u3002\u4f7f\u7528\u65b9\u5411\u952e\u9009\u62e9\u8981\u8fde\u63a5\u7684 Wi-Fi \u7f51\u7edc\u5e76\u6309\u56de\u8f66\u952e\u3002 \u5982\u679c Wi-Fi \u7f51\u7edc\u53d7\u5230\u5bc6\u7801\u4fdd\u62a4\uff0c armbian-config \u5c06\u63d0\u793a\u60a8\u8f93\u5165 Wi-Fi \u5bc6\u7801\u3002\u8f93\u5165\u5bc6\u7801\u5e76\u6309\u56de\u8f66\u952e\u3002 \u7b49\u5f85\u7247\u523b\uff0cArmbian \u7cfb\u7edf\u5c06\u5c1d\u8bd5\u8fde\u63a5\u5230\u6307\u5b9a\u7684 Wi-Fi \u7f51\u7edc\u3002\u5982\u679c\u8fde\u63a5\u6210\u529f\uff0c\u60a8\u5c06\u5728\u5c4f\u5e55\u4e0a\u770b\u5230\u76f8\u5e94\u7684\u6d88\u606f\u3002 \u9000\u51fa armbian-config \u5de5\u5177\u3002 \u8bf7\u6ce8\u610f\uff0c\u4e0a\u8ff0\u6b65\u9aa4\u4e2d\u7684\u83dc\u5355\u9009\u9879\u548c\u914d\u7f6e\u53ef\u80fd\u4f1a\u6839\u636e\u4e0d\u540c\u7248\u672c\u7684 Armbian \u7cfb\u7edf\u7565\u6709\u4e0d\u540c\u3002\u786e\u4fdd\u6839\u636e\u60a8\u7684\u7cfb\u7edf\u7248\u672c\u548c\u914d\u7f6e\u8fdb\u884c\u76f8\u5e94\u7684\u64cd\u4f5c\u3002","title":"Wifi\u914d\u7f6e"},{"location":"wifi/#wifi","text":"\u7531\u4e8eBLIKVM\u6709\u591a\u6b3e\u786c\u4ef6\uff0c\u652f\u6301\u4e0d\u540c\u7684OS\uff0c\u5982BLIKVM OS\u548cPiKVM OS\uff0c\u4e0d\u540cOS\u94fe\u63a5wifi\u65b9\u5f0f\u4e0d\u4e00\u5b9a\u76f8\u540c\uff0c\u8bf7\u5728\u4f7f\u7528\u672c\u6587\u6863\u65b9\u6cd5\u524d\uff0c\u8bf7\u786e\u8ba4\u81ea\u5df1\u786c\u4ef6\u548c\u4f7f\u7528OS\u7684\u60c5\u51b5\u3002 \u8bf7\u786e\u8ba4\u4f60\u4f7f\u7528\u7684\u786c\u4ef6\u652f\u6301wifi\u529f\u80fd\uff0c\u5982CM400200\u7248\u672c\u4e0d\u5e26wifi\u529f\u80fd\uff1b \u82e5KVM\u786c\u4ef6\u7684SOC\u4e3aCM4\uff0c\u8bf7\u786e\u8ba4\u662f\u5426\u8fde\u63a5\u4e86wifi\u5929\u7ebf\uff1b PiKVM OS\u4e3aarch linux\uff1b BLIKVM OS\u6811\u8393\u6d3e\u7cfb\u5217\u4e3adebian\u7cfb\u7edf\uff0cv4\u7cfb\u5217\u4e3aarmbian\u7cfb\u7edf\uff1b","title":"Wifi\u529f\u80fd"},{"location":"wifi/#v1v2v3debianraspi-configwifi","text":"\u767b\u5f55ssh,\u547d\u4ee4: ssh blikvm@ip \u7cfb\u7edf\u91cd\u52a0\u8f7d\u4e3a\u53ef\u5199, \u547d\u4ee4: rw \u542f\u52a8raspi-config, \u547d\u4ee4: sudo raspi-config \u9009\u62e9 System Options \u9009\u62e9 Wireless LAN \u9009\u62e9wifi\u6240\u5728\u56fd\u5bb6,\u4e2d\u56fd\u9009CN, \u5982\u679c\u4ee5\u524d\u8bbe\u7f6e\u8fc7,\u8fd9\u4e00\u6b65\u4f1a\u8df3\u8fc7\u76f4\u63a5\u52307 \u8f93\u5165Wi-Fi\u7684ssid(\u540d\u79f0) \u8f93\u5165Wi-Fi\u7684\u5bc6\u7801,\u5982\u679c\u6ca1\u6709\u5bc6\u7801\u76f4\u63a5\u56de\u8f66 \u8fd9\u65f6\u4f1a\u56de\u5230\u6b65\u9aa44\u7684\u754c\u9762,\u6309tab\u952e\u9009\u62e9 ,\u56de\u8f66 \u67e5\u770b\u662f\u5426\u8fde\u4e0awifi, \u547d\u4ee4: ifconfig wlan0 ,\u5982\u679c\u770b\u5230\u83b7\u53d6\u5230ip\u5c31\u662f\u5df2\u7ecf\u8fde\u4e0a\u4e86 \u5c06\u7cfb\u7edf\u6302\u8f7d\u4e3a\u53ea\u8bfb, \u547d\u4ee4: ro","title":"v1\uff0cv2\uff0cv3\u786c\u4ef6\u4f7f\u7528\u7684\u4e3a\u6811\u8393\u6d3edebian\u7cfb\u7edf\uff0c\u4f7f\u7528raspi-config\u8fdb\u884cwifi\u94fe\u63a5"},{"location":"wifi/#v4armbianarmbian-config","text":"\u767b\u5f55ssh,\u547d\u4ee4: ssh blikvm@ip\uff0c\u767b\u5f55\u5230 Armbian \u7cfb\u7edf\u3002 \u8f93\u5165\u4ee5\u4e0b\u547d\u4ee4\u4ee5\u542f\u52a8 armbian-config \u5de5\u5177\uff1a sudo armbian-config \u5728 armbian-config \u83dc\u5355\u4e2d\uff0c\u4f7f\u7528\u65b9\u5411\u952e\u548c\u56de\u8f66\u952e\u5bfc\u822a\u548c\u9009\u62e9\u9009\u9879\u3002 \u4f7f\u7528\u65b9\u5411\u952e\u5411\u4e0b\u6eda\u52a8\u5230 \"Network\" \u9009\u9879\uff0c\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165\u5b50\u83dc\u5355\u3002 \u5728 \"Network\" \u5b50\u83dc\u5355\u4e2d\uff0c\u9009\u62e9 \"Wireless\" \u9009\u9879\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165 Wi-Fi \u914d\u7f6e\u83dc\u5355\u3002 \u5728 Wi-Fi \u914d\u7f6e\u83dc\u5355\u4e2d\uff0c\u9009\u62e9 \"Connect to Wi-Fi\" \u9009\u9879\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165 Wi-Fi \u8fde\u63a5\u8bbe\u7f6e\u3002 armbian-config \u5c06\u5217\u51fa\u53ef\u7528\u7684\u65e0\u7ebf\u7f51\u7edc\u63a5\u53e3\u548c\u5df2\u914d\u7f6e\u7684\u7f51\u7edc\u3002\u9009\u62e9\u8981\u8fde\u63a5\u7684\u65e0\u7ebf\u7f51\u7edc\u63a5\u53e3\u5e76\u6309\u56de\u8f66\u952e\u3002 armbian-config \u5c06\u663e\u793a\u53ef\u7528\u7684 Wi-Fi \u7f51\u7edc\u5217\u8868\u3002\u4f7f\u7528\u65b9\u5411\u952e\u9009\u62e9\u8981\u8fde\u63a5\u7684 Wi-Fi \u7f51\u7edc\u5e76\u6309\u56de\u8f66\u952e\u3002 \u5982\u679c Wi-Fi \u7f51\u7edc\u53d7\u5230\u5bc6\u7801\u4fdd\u62a4\uff0c armbian-config \u5c06\u63d0\u793a\u60a8\u8f93\u5165 Wi-Fi \u5bc6\u7801\u3002\u8f93\u5165\u5bc6\u7801\u5e76\u6309\u56de\u8f66\u952e\u3002 \u7b49\u5f85\u7247\u523b\uff0cArmbian \u7cfb\u7edf\u5c06\u5c1d\u8bd5\u8fde\u63a5\u5230\u6307\u5b9a\u7684 Wi-Fi \u7f51\u7edc\u3002\u5982\u679c\u8fde\u63a5\u6210\u529f\uff0c\u60a8\u5c06\u5728\u5c4f\u5e55\u4e0a\u770b\u5230\u76f8\u5e94\u7684\u6d88\u606f\u3002 \u9000\u51fa armbian-config \u5de5\u5177\u3002 \u8bf7\u6ce8\u610f\uff0c\u4e0a\u8ff0\u6b65\u9aa4\u4e2d\u7684\u83dc\u5355\u9009\u9879\u548c\u914d\u7f6e\u53ef\u80fd\u4f1a\u6839\u636e\u4e0d\u540c\u7248\u672c\u7684 Armbian \u7cfb\u7edf\u7565\u6709\u4e0d\u540c\u3002\u786e\u4fdd\u6839\u636e\u60a8\u7684\u7cfb\u7edf\u7248\u672c\u548c\u914d\u7f6e\u8fdb\u884c\u76f8\u5e94\u7684\u64cd\u4f5c\u3002","title":"v4\u786c\u4ef6\u4f7f\u7528\u7684\u4e3aarmbian\u7cfb\u7edf\uff0c\u4f7f\u7528armbian-config"},{"location":"zerotier/","text":"ZeroTier VPN ZeroTier \u5141\u8bb8\u901a\u8fc7 NAT \u5728\u53cc\u65b9\u4e4b\u95f4\u5b89\u5168\u8bbf\u95ee\u60a8\u7684 BliKVM\u3002\u5b83\u5141\u8bb8\u60a8\u6784\u5efa\u51e0\u4e4e\u4efb\u4f55\u7c7b\u578b\u7684\u73b0\u4ee3\u3001\u5b89\u5168\u7684\u591a\u70b9\u865a\u62df\u5316\u7f51\u7edc\u3002\u672c\u6587\u63d0\u4f9b\u4e86\u4e00\u4e2a\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95ee\u60a8\u7684 BliKVM \u7684\u793a\u4f8b\uff0c\u4f46\u60a8\u4e5f\u53ef\u4ee5\u4f7f\u7528 Tailscale \u6216\u5176\u4ed6 VPN \u89e3\u51b3\u65b9\u6848\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u57fa\u672c\u793a\u4f8b\uff0c\u5982\u9700\u4efb\u4f55\u7279\u5b9a\u8bbe\u7f6e\u6216\u529f\u80fd\uff0c\u8bf7\u53c2\u9605 ZeroTier\u6587\u6863 \u3002 \u5728 BliKVM \u4e0a\u5b89\u88c5 ZeroTier \u9996\u5148\uff0c\u5728 ZeroTier \u4e0a\u51c6\u5907\u8d26\u6237\u548c VPN \u7f51\u7edc\uff0c\u5177\u4f53\u64cd\u4f5c\u8bf7\u53c2\u89c1\u8fd9\u91cc\uff1a \u521b\u5efa\u7f51\u7edc \uff0c\u4fdd\u5b58\u7f51\u7edc ID \u4ee5\u4f9b\u4ee5\u540e\u4f7f\u7528\u3002\u63a5\u4e0b\u6765\uff0c\u4f7f\u7528 SSH \u534f\u8bae\u8fde\u63a5\u5230 BliKVM \u7ec8\u7aef\uff0c\u5e76\u68c0\u67e5\u8bfb\u5199\u6743\u9650\u3002\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u5176\u8bbe\u7f6e\u4e3a\u53ef\u5199\u3002 \u73b0\u5728\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\u5b89\u88c5 ZeroTier \u5ba2\u6237\u7aef\uff1a curl -s https://install.zerotier.com | sudo bash \u8bf7\u6ce8\u610f\uff0c\u5728\u67d0\u4e9b\u5730\u533a\uff0c\u5982\u4e2d\u56fd\uff0c\u76f4\u63a5\u4e0b\u8f7d ZeroTier \u53ef\u80fd\u4f1a\u53d7\u5230\u7f51\u7edc\u9650\u5236\u7684\u5f71\u54cd\u3002\u8bf7\u76f8\u5e94\u914d\u7f6e\u60a8\u7684\u7f51\u7edc\u3002 \u5c06 BliKVM \u6dfb\u52a0\u5230\u60a8\u7684 ZeroTier \u7f51\u7edc \u5728 BliKVM \u7ec8\u7aef\u4e0a\uff0c\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\u5c06 BliKVM \u6dfb\u52a0\u5230\u60a8\u7684 ZeroTier \u7f51\u7edc\uff08\u4f7f\u7528 ZeroTier \u7f51\u7edc ID\uff0c\u4f8b\u5982 d5e04297a16fa690\uff09\uff1a sudo zerotier-cli join d5e04297a16fa690 \u5982\u679c\u4e00\u5207\u987a\u5229\uff0c\u60a8\u53ef\u4ee5\u5728 BliKVM \u7ec8\u7aef\u4e0a\u8fd0\u884c ip addr show zerotier \u7f51\u7edc\u8bbe\u5907\uff08\u540d\u79f0\u4ee5 zt \u5f00\u5934\uff09\u4ee5\u67e5\u770b ZeroTier \u4e3a\u865a\u62df\u7f51\u7edc\u5206\u914d\u7684 IP \u5730\u5740\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u793a\u4f8b\u8f93\u51fa\uff1a 3: zt6ovrlscs:  mtu 2800 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether d6:e4:eb:ae:db:64 brd ff:ff:ff:ff:ff:ff inet 172.25.96.75/16 brd 172.25.255.255 scope global zt6ovrlscs valid_lft forever preferred_lft forever inet6 fe80::d4e4:ebff:feae:db64/64 scope link valid_lft forever preferred_lft forever IP \u5730\u5740\uff0c\u4f8b\u5982 172.25.96.75\uff0c\u53ef\u7528\u4e8e\u4ece\u4e3b\u673a\u673a\u5668\u8bbf\u95ee BliKVM Web \u754c\u9762\u3002 \u5728\u5ba2\u6237\u8ba1\u7b97\u673a\u4e0a\u5b89\u88c5 ZeroTier \u8f6c\u5230\u4e0b\u8f7d\u9875\u9762\uff0c\u5728 ZeroTier \u7f51\u7ad9\u4e0a\u5b89\u88c5 ZeroTier \u5230\u63a7\u5236\u4e3b\u673a\u3002\u52a0\u5165\u60a8\u7684 ZeroTier \u7f51\u7edc ID\uff0c\u7136\u540e\u60a8\u53ef\u4ee5\u68c0\u67e5\u60a8\u7684\u7f51\u7edc\u9875\u9762\uff0c\u9a8c\u8bc1\u4e24\u53f0\u673a\u5668\u662f\u5426\u5728\u7ebf\u3002\u68c0\u67e5\u5b83\u4eec\u662f\u5426\u88ab\u6388\u6743\u8fde\u63a5\u5230\u7f51\u7edc\uff08Auth? \u5217\uff09\u3002\u4e00\u65e6\u5b83\u4eec\u5728\u7ebf\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u5730\u5740\u4ece\u63a7\u5236\u4e3b\u673a\u673a\u5668\u8bbf\u95ee BliKVM\uff1a http://","title":"Zerotier VPN"},{"location":"zerotier/#zerotier-vpn","text":"ZeroTier \u5141\u8bb8\u901a\u8fc7 NAT \u5728\u53cc\u65b9\u4e4b\u95f4\u5b89\u5168\u8bbf\u95ee\u60a8\u7684 BliKVM\u3002\u5b83\u5141\u8bb8\u60a8\u6784\u5efa\u51e0\u4e4e\u4efb\u4f55\u7c7b\u578b\u7684\u73b0\u4ee3\u3001\u5b89\u5168\u7684\u591a\u70b9\u865a\u62df\u5316\u7f51\u7edc\u3002\u672c\u6587\u63d0\u4f9b\u4e86\u4e00\u4e2a\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95ee\u60a8\u7684 BliKVM \u7684\u793a\u4f8b\uff0c\u4f46\u60a8\u4e5f\u53ef\u4ee5\u4f7f\u7528 Tailscale \u6216\u5176\u4ed6 VPN \u89e3\u51b3\u65b9\u6848\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u57fa\u672c\u793a\u4f8b\uff0c\u5982\u9700\u4efb\u4f55\u7279\u5b9a\u8bbe\u7f6e\u6216\u529f\u80fd\uff0c\u8bf7\u53c2\u9605 ZeroTier\u6587\u6863 \u3002","title":"ZeroTier VPN"},{"location":"zerotier/#blikvm-zerotier","text":"\u9996\u5148\uff0c\u5728 ZeroTier \u4e0a\u51c6\u5907\u8d26\u6237\u548c VPN \u7f51\u7edc\uff0c\u5177\u4f53\u64cd\u4f5c\u8bf7\u53c2\u89c1\u8fd9\u91cc\uff1a \u521b\u5efa\u7f51\u7edc \uff0c\u4fdd\u5b58\u7f51\u7edc ID \u4ee5\u4f9b\u4ee5\u540e\u4f7f\u7528\u3002\u63a5\u4e0b\u6765\uff0c\u4f7f\u7528 SSH \u534f\u8bae\u8fde\u63a5\u5230 BliKVM \u7ec8\u7aef\uff0c\u5e76\u68c0\u67e5\u8bfb\u5199\u6743\u9650\u3002\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u5176\u8bbe\u7f6e\u4e3a\u53ef\u5199\u3002 \u73b0\u5728\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\u5b89\u88c5 ZeroTier \u5ba2\u6237\u7aef\uff1a curl -s https://install.zerotier.com | sudo bash \u8bf7\u6ce8\u610f\uff0c\u5728\u67d0\u4e9b\u5730\u533a\uff0c\u5982\u4e2d\u56fd\uff0c\u76f4\u63a5\u4e0b\u8f7d ZeroTier \u53ef\u80fd\u4f1a\u53d7\u5230\u7f51\u7edc\u9650\u5236\u7684\u5f71\u54cd\u3002\u8bf7\u76f8\u5e94\u914d\u7f6e\u60a8\u7684\u7f51\u7edc\u3002","title":"\u5728 BliKVM \u4e0a\u5b89\u88c5 ZeroTier"},{"location":"zerotier/#blikvm-zerotier_1","text":"\u5728 BliKVM \u7ec8\u7aef\u4e0a\uff0c\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\u5c06 BliKVM \u6dfb\u52a0\u5230\u60a8\u7684 ZeroTier \u7f51\u7edc\uff08\u4f7f\u7528 ZeroTier \u7f51\u7edc ID\uff0c\u4f8b\u5982 d5e04297a16fa690\uff09\uff1a sudo zerotier-cli join d5e04297a16fa690 \u5982\u679c\u4e00\u5207\u987a\u5229\uff0c\u60a8\u53ef\u4ee5\u5728 BliKVM \u7ec8\u7aef\u4e0a\u8fd0\u884c ip addr show zerotier \u7f51\u7edc\u8bbe\u5907\uff08\u540d\u79f0\u4ee5 zt \u5f00\u5934\uff09\u4ee5\u67e5\u770b ZeroTier \u4e3a\u865a\u62df\u7f51\u7edc\u5206\u914d\u7684 IP \u5730\u5740\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u793a\u4f8b\u8f93\u51fa\uff1a 3: zt6ovrlscs:  mtu 2800 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether d6:e4:eb:ae:db:64 brd ff:ff:ff:ff:ff:ff inet 172.25.96.75/16 brd 172.25.255.255 scope global zt6ovrlscs valid_lft forever preferred_lft forever inet6 fe80::d4e4:ebff:feae:db64/64 scope link valid_lft forever preferred_lft forever IP \u5730\u5740\uff0c\u4f8b\u5982 172.25.96.75\uff0c\u53ef\u7528\u4e8e\u4ece\u4e3b\u673a\u673a\u5668\u8bbf\u95ee BliKVM Web \u754c\u9762\u3002","title":"\u5c06 BliKVM \u6dfb\u52a0\u5230\u60a8\u7684 ZeroTier \u7f51\u7edc"},{"location":"zerotier/#zerotier","text":"\u8f6c\u5230\u4e0b\u8f7d\u9875\u9762\uff0c\u5728 ZeroTier \u7f51\u7ad9\u4e0a\u5b89\u88c5 ZeroTier \u5230\u63a7\u5236\u4e3b\u673a\u3002\u52a0\u5165\u60a8\u7684 ZeroTier \u7f51\u7edc ID\uff0c\u7136\u540e\u60a8\u53ef\u4ee5\u68c0\u67e5\u60a8\u7684\u7f51\u7edc\u9875\u9762\uff0c\u9a8c\u8bc1\u4e24\u53f0\u673a\u5668\u662f\u5426\u5728\u7ebf\u3002\u68c0\u67e5\u5b83\u4eec\u662f\u5426\u88ab\u6388\u6743\u8fde\u63a5\u5230\u7f51\u7edc\uff08Auth? \u5217\uff09\u3002\u4e00\u65e6\u5b83\u4eec\u5728\u7ebf\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u5730\u5740\u4ece\u63a7\u5236\u4e3b\u673a\u673a\u5668\u8bbf\u95ee BliKVM\uff1a http://","title":"\u5728\u5ba2\u6237\u8ba1\u7b97\u673a\u4e0a\u5b89\u88c5 ZeroTier"}]}
\ No newline at end of file
+{"config":{"indexing":"full","lang":["en","ja","ru"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"BLIKVM Overview BLIKVM\u662f\u4e00\u6b3e\u5f00\u6e90\u8f6f\u4ef6\u7684KVM\u4e13\u4e1a\u8bbe\u5907\uff0c\u76ee\u524d\u67094\u4e2a\u7248\u672c\uff0cv1 CM4, v2 PCIe, v3 HAT, v4 Allwinner\u3002\u8be5\u8bbe\u5907\u5728\u4e8e\u5e2e\u52a9\u7528\u6237\u901a\u8fc7\u5f97\u5230\u63a7\u5236\u8bbe\u5907\u7684HDMI \u753b\u9762\u548c\u9f20\u6807\u952e\u76d8\uff0c\u53bb\u8fdc\u7a0b\u7ba1\u7406\u670d\u52a1\u5668\u3001\u5de5\u4f5c\u7ad9\u6216\u4e2a\u4ebaPC\u7b49\u3002 \u65e0\u8bba\u76ee\u6807\u8bbe\u5907\u7684\u64cd\u4f5c\u7cfb\u7edf\u662f\u5426\u80fd\u6b63\u5e38\u8fd0\u884c\uff0c\u53ef\u4ee5\u901a\u8fc7BLIKVM\u89e3\u51b3\u76ee\u6807\u8bbe\u5907\u7684\u4e00\u5207\u95ee\u9898\u3002\u5982\uff1a\u914d\u7f6eBIOS\u7cfb\u7edf\uff0c\u901a\u8fc7\u4f7f\u7528\u8fdc\u7a0bCD-ROM\u6216\u8005\u95ea\u5b58\u9a71\u52a8\u5668\u7ed9\u76ee\u6807\u8bbe\u5907\u91cd\u65b0\u5b89\u88c5\u64cd\u4f5c\u7cfb\u7edf\u3002\u548c\u57fa\u4e8e\u8f6f\u4ef6\u7684\u8fdc\u7a0b\u7ba1\u7406\u65b9\u5f0f\u4e0d\u540c\uff0c\u4f60\u65e0\u9700\u5728\u88ab\u63a7\u7535\u8111\u5b89\u88c5\u4efb\u4f55\u8f6f\u4ef6\uff0c\u505a\u5230\u65e0\u4fb5\u5165\u5f0f\u63a7\u5236\u3002 \u5728\u8fd9\u91cc\u4f60\u53ef\u4ee5\u627e\u5230\u5173\u4e8eBLIKVM\u6240\u6709\u7684\u4f7f\u7528\u6587\u6863\u3002\u6b22\u8fce\u52a0\u5165BLIKVM\u7684 Discord \u7fa4\u7ec4\u548c\u6765\u81ea\u5168\u4e16\u754c\u7684\u7231\u597d\u8005\u548c\u7528\u6237\u8fdb\u884c\u4ea4\u6d41\uff0c\u83b7\u5f97\u6280\u672f\u652f\u6301\uff0c\u5e38\u89c1\u95ee\u9898\u89e3\u7b54\u548c\u65b0\u95fb\u7b49\u3002 \u529f\u80fd BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 H616/H313 SOC \u6811\u8393\u6d3eCM4 \u6811\u8393\u6d3eCM4 \u6811\u8393\u6d3e4B \u5168\u5fd7H616/H313 \u652f\u6301\u8f93\u5165\u7684\u6700\u9ad8\u5206\u8fa8\u7387 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI\u91c7\u96c6\u82af\u7247 TC358743 TC358743 TC358743 MS2131 HDMI\u73af\u51fa \u65e0 \u65e0 \u65e0 \u6709 PoE\u4f9b\u7535 \u4e0d\u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 DC\u4f9b\u7535 \u4e0d\u652f\u6301 \u4e0d\u652f\u6301 \u4e0d\u652f\u6301 \u652f\u6301 USB-C\u4f9b\u7535 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 USB\u7535\u6e90/\u6570\u636e\u5206\u79bb\u5668 \u6709 \u6709(\u989d\u5916\u6a21\u5757) \u6709 \u6709 \u4e32\u53e3\u7ec8\u7aef \u4e0d\u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 ATX\u5f00\u5173\u673a\u63a7\u5236 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 BIOS\u63a7\u5236 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u7cfb\u7edf\u5f00\u6e90 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u91cd\u88c5\u88ab\u63a7\u7535\u8111\u7cfb\u7edf \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u98ce\u6247 \u6709(\u4e0d\u652f\u6301\u8c03\u901f) \u6709 \u6709 \u53ef\u914d(\u9ed8\u8ba4\u914d\u6563\u70ed\u7247) \u5c4f\u5e55\u79cd\u7c7b OLED 128x64 \u767d\u8272 OLED 128x64 \u767d\u8272 OLED 128x32 \u767d\u8272 LCD 240x240 \u5f69\u8272 RTC\u65f6\u949f \u6709(DS1307) \u6709(PCF8563) \u6709(PCF8563) \u6709(PCF8563) \u5916\u58f3 \u91d1\u5c5e\u9ed1 \u65e0 \u91d1\u5c5e\u9ed1\u84dd\u6a58\u767d(1U\u673a\u67b6\u517c\u5bb9) \u91d1\u5c5e\u9ed1(1U\u673a\u67b6\u517c\u5bb9) \u8702\u9e23\u5668 \u65e0 \u65e0 \u65e0 \u6709 \u81ea\u5b9a\u4e49\u6309\u94ae \u65e0 \u65e0 \u65e0 \u6709 \u8f6f\u4ef6\u5347\u7ea7 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 32GB SD\u5361 \u6709(\u542bOS) \u6709(\u542bOS) \u6709(\u542bOS) \u6709(\u542bOS) \u89e3\u51b3HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898 \u672a\u89e3\u51b3 \u5df2\u89e3\u51b3 \u5df2\u89e3\u51b3 \u5df2\u89e3\u51b3 \u4e13\u4e1a\u6280\u672f\u652f\u6301 \u6709 \u6709 \u6709 \u6709 \u529f\u80fd HDMI\u89c6\u9891\u91c7\u96c6 (\u6700\u9ad8\u652f\u63011080P 60Hz) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 ATX\u5f00\u5173\u673a PWM\u98ce\u6247\u63a7\u5236 \u5168\u5c4f\u6a21\u5f0f \u4ece\u526a\u8d34\u677f\u7c98\u8d34\u6587\u672c VPN\u7ec4\u7f51\u652f\u6301 \u5927\u5bb9\u91cf\u5b58\u50a8\u9a71\u52a8\u5668 (\u6a21\u62dfCD-ROM\u6216\u95ea\u5b58\u9a71\u52a8\u5668) \u8fdc\u7a0b\u63a7\u5236\u591a\u53f0\u4e3b\u673a\uff08\u901a\u8fc7\u642d\u914dKVM\u5207\u6362\u5668\uff09 OLED\u5c4f\u5e55\u663e\u793a\u7cfb\u7edf\u4fe1\u606f\uff08\u6e29\u5ea6\u3001IP\u5730\u5740\uff0c\u8fd0\u884c\u65f6\u95f4\u7b49\uff09 \u8d26\u53f7\u5bc6\u7801\u8ba4\u8bc1 Guide 1.BliKVM v1 CM4 \u7248\u672c 2.BliKVM v2 PCIe \u7248\u672c 3.BliKVM v3 HAT \u7248\u672c 4.BliKVM v4 Allwinner \u7248\u672c","title":"BliKVM\u4ecb\u7ecd"},{"location":"#blikvm-overview","text":"BLIKVM\u662f\u4e00\u6b3e\u5f00\u6e90\u8f6f\u4ef6\u7684KVM\u4e13\u4e1a\u8bbe\u5907\uff0c\u76ee\u524d\u67094\u4e2a\u7248\u672c\uff0cv1 CM4, v2 PCIe, v3 HAT, v4 Allwinner\u3002\u8be5\u8bbe\u5907\u5728\u4e8e\u5e2e\u52a9\u7528\u6237\u901a\u8fc7\u5f97\u5230\u63a7\u5236\u8bbe\u5907\u7684HDMI \u753b\u9762\u548c\u9f20\u6807\u952e\u76d8\uff0c\u53bb\u8fdc\u7a0b\u7ba1\u7406\u670d\u52a1\u5668\u3001\u5de5\u4f5c\u7ad9\u6216\u4e2a\u4ebaPC\u7b49\u3002 \u65e0\u8bba\u76ee\u6807\u8bbe\u5907\u7684\u64cd\u4f5c\u7cfb\u7edf\u662f\u5426\u80fd\u6b63\u5e38\u8fd0\u884c\uff0c\u53ef\u4ee5\u901a\u8fc7BLIKVM\u89e3\u51b3\u76ee\u6807\u8bbe\u5907\u7684\u4e00\u5207\u95ee\u9898\u3002\u5982\uff1a\u914d\u7f6eBIOS\u7cfb\u7edf\uff0c\u901a\u8fc7\u4f7f\u7528\u8fdc\u7a0bCD-ROM\u6216\u8005\u95ea\u5b58\u9a71\u52a8\u5668\u7ed9\u76ee\u6807\u8bbe\u5907\u91cd\u65b0\u5b89\u88c5\u64cd\u4f5c\u7cfb\u7edf\u3002\u548c\u57fa\u4e8e\u8f6f\u4ef6\u7684\u8fdc\u7a0b\u7ba1\u7406\u65b9\u5f0f\u4e0d\u540c\uff0c\u4f60\u65e0\u9700\u5728\u88ab\u63a7\u7535\u8111\u5b89\u88c5\u4efb\u4f55\u8f6f\u4ef6\uff0c\u505a\u5230\u65e0\u4fb5\u5165\u5f0f\u63a7\u5236\u3002 \u5728\u8fd9\u91cc\u4f60\u53ef\u4ee5\u627e\u5230\u5173\u4e8eBLIKVM\u6240\u6709\u7684\u4f7f\u7528\u6587\u6863\u3002\u6b22\u8fce\u52a0\u5165BLIKVM\u7684 Discord \u7fa4\u7ec4\u548c\u6765\u81ea\u5168\u4e16\u754c\u7684\u7231\u597d\u8005\u548c\u7528\u6237\u8fdb\u884c\u4ea4\u6d41\uff0c\u83b7\u5f97\u6280\u672f\u652f\u6301\uff0c\u5e38\u89c1\u95ee\u9898\u89e3\u7b54\u548c\u65b0\u95fb\u7b49\u3002 \u529f\u80fd BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 H616/H313 SOC \u6811\u8393\u6d3eCM4 \u6811\u8393\u6d3eCM4 \u6811\u8393\u6d3e4B \u5168\u5fd7H616/H313 \u652f\u6301\u8f93\u5165\u7684\u6700\u9ad8\u5206\u8fa8\u7387 1920x1080@60Hz 1920x1080@60Hz 1920x1080@50Hz 3840x2160@30Hz HDMI\u91c7\u96c6\u82af\u7247 TC358743 TC358743 TC358743 MS2131 HDMI\u73af\u51fa \u65e0 \u65e0 \u65e0 \u6709 PoE\u4f9b\u7535 \u4e0d\u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 DC\u4f9b\u7535 \u4e0d\u652f\u6301 \u4e0d\u652f\u6301 \u4e0d\u652f\u6301 \u652f\u6301 USB-C\u4f9b\u7535 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 USB\u7535\u6e90/\u6570\u636e\u5206\u79bb\u5668 \u6709 \u6709(\u989d\u5916\u6a21\u5757) \u6709 \u6709 \u4e32\u53e3\u7ec8\u7aef \u4e0d\u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 ATX\u5f00\u5173\u673a\u63a7\u5236 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 BIOS\u63a7\u5236 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u7cfb\u7edf\u5f00\u6e90 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u91cd\u88c5\u88ab\u63a7\u7535\u8111\u7cfb\u7edf \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u98ce\u6247 \u6709(\u4e0d\u652f\u6301\u8c03\u901f) \u6709 \u6709 \u53ef\u914d(\u9ed8\u8ba4\u914d\u6563\u70ed\u7247) \u5c4f\u5e55\u79cd\u7c7b OLED 128x64 \u767d\u8272 OLED 128x64 \u767d\u8272 OLED 128x32 \u767d\u8272 LCD 240x240 \u5f69\u8272 RTC\u65f6\u949f \u6709(DS1307) \u6709(PCF8563) \u6709(PCF8563) \u6709(PCF8563) \u5916\u58f3 \u91d1\u5c5e\u9ed1 \u65e0 \u91d1\u5c5e\u9ed1\u84dd\u6a58\u767d(1U\u673a\u67b6\u517c\u5bb9) \u91d1\u5c5e\u9ed1(1U\u673a\u67b6\u517c\u5bb9) \u8702\u9e23\u5668 \u65e0 \u65e0 \u65e0 \u6709 \u81ea\u5b9a\u4e49\u6309\u94ae \u65e0 \u65e0 \u65e0 \u6709 \u8f6f\u4ef6\u5347\u7ea7 \u652f\u6301 \u652f\u6301 \u652f\u6301 \u652f\u6301 32GB SD\u5361 \u6709(\u542bOS) \u6709(\u542bOS) \u6709(\u542bOS) \u6709(\u542bOS) \u89e3\u51b3HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898 \u672a\u89e3\u51b3 \u5df2\u89e3\u51b3 \u5df2\u89e3\u51b3 \u5df2\u89e3\u51b3 \u4e13\u4e1a\u6280\u672f\u652f\u6301 \u6709 \u6709 \u6709 \u6709","title":"BLIKVM Overview"},{"location":"#_1","text":"HDMI\u89c6\u9891\u91c7\u96c6 (\u6700\u9ad8\u652f\u63011080P 60Hz) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 ATX\u5f00\u5173\u673a PWM\u98ce\u6247\u63a7\u5236 \u5168\u5c4f\u6a21\u5f0f \u4ece\u526a\u8d34\u677f\u7c98\u8d34\u6587\u672c VPN\u7ec4\u7f51\u652f\u6301 \u5927\u5bb9\u91cf\u5b58\u50a8\u9a71\u52a8\u5668 (\u6a21\u62dfCD-ROM\u6216\u95ea\u5b58\u9a71\u52a8\u5668) \u8fdc\u7a0b\u63a7\u5236\u591a\u53f0\u4e3b\u673a\uff08\u901a\u8fc7\u642d\u914dKVM\u5207\u6362\u5668\uff09 OLED\u5c4f\u5e55\u663e\u793a\u7cfb\u7edf\u4fe1\u606f\uff08\u6e29\u5ea6\u3001IP\u5730\u5740\uff0c\u8fd0\u884c\u65f6\u95f4\u7b49\uff09 \u8d26\u53f7\u5bc6\u7801\u8ba4\u8bc1","title":"\u529f\u80fd"},{"location":"#guide","text":"1.BliKVM v1 CM4 \u7248\u672c 2.BliKVM v2 PCIe \u7248\u672c 3.BliKVM v3 HAT \u7248\u672c 4.BliKVM v4 Allwinner \u7248\u672c","title":"Guide"},{"location":"BLIHAT-Installation/","text":"BLIHAT \u5b89\u88c5\u8bf4\u660e 1.\u62c6\u5f00\u5305\u88c5\uff0c\u6253\u5f00\u888b\u5b50\uff0c\u62ff\u51fa\u8bbe\u5907 2.\u5b89\u88c5\u4e3b\u4f53\u8bbe\u5907 \u5378\u4e0b\u5916\u58f3\u80cc\u9762\u7684\u5982\u56fe\u4e2d\u6240\u793a\u7684\u87ba\u4e1d \u6253\u5f00\u5916\u58f3 \u5378\u4e0b\u80cc\u9762\u5269\u4e0b\u7684\u87ba\u4e1d \u6253\u5f00\u914d\u4ef6\u5305\uff0c\u62ff\u51fa\u56fe\u7247\u4e2d\u7684\u8bbe\u5907 \u5b89\u88c5SD\u5361 \u5b89\u88c5FFC\u7ebf\u7f06 \u5b89\u88c5Hat\u5230\u6811\u8393\u6d3e4B\u4e0a \u5b89\u88c54\u9897\u94dc\u67f1 \u5b89\u88c5C790\u6a21\u5757\u5230Hat\u4e0a\uff0c\u4f7f\u7528\u4f60\u5378\u4e0b\u6765\u7684\u957f\u87ba\u4e1d \u5b89\u88c5\u97f3\u9891\u7ebf\u7f06 \u6495\u53bb\u7845\u80f6\u7247\u4e0a\u7684\u4fdd\u62a4\u819c\uff0c\u5c06\u5176\u8d34\u5230\u6811\u8393\u6d3e\u5982\u56fe\u6240\u793a\u7684\u4f4d\u7f6e Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"v3 HAT\u5b89\u88c5\u8bf4\u660e"},{"location":"BLIHAT-Installation/#blihat","text":"1.\u62c6\u5f00\u5305\u88c5\uff0c\u6253\u5f00\u888b\u5b50\uff0c\u62ff\u51fa\u8bbe\u5907 2.\u5b89\u88c5\u4e3b\u4f53\u8bbe\u5907 \u5378\u4e0b\u5916\u58f3\u80cc\u9762\u7684\u5982\u56fe\u4e2d\u6240\u793a\u7684\u87ba\u4e1d \u6253\u5f00\u5916\u58f3 \u5378\u4e0b\u80cc\u9762\u5269\u4e0b\u7684\u87ba\u4e1d \u6253\u5f00\u914d\u4ef6\u5305\uff0c\u62ff\u51fa\u56fe\u7247\u4e2d\u7684\u8bbe\u5907 \u5b89\u88c5SD\u5361 \u5b89\u88c5FFC\u7ebf\u7f06 \u5b89\u88c5Hat\u5230\u6811\u8393\u6d3e4B\u4e0a \u5b89\u88c54\u9897\u94dc\u67f1 \u5b89\u88c5C790\u6a21\u5757\u5230Hat\u4e0a\uff0c\u4f7f\u7528\u4f60\u5378\u4e0b\u6765\u7684\u957f\u87ba\u4e1d \u5b89\u88c5\u97f3\u9891\u7ebf\u7f06 \u6495\u53bb\u7845\u80f6\u7247\u4e0a\u7684\u4fdd\u62a4\u819c\uff0c\u5c06\u5176\u8d34\u5230\u6811\u8393\u6d3e\u5982\u56fe\u6240\u793a\u7684\u4f4d\u7f6e Install the HAT into the case Pay attention to the alignment of the holes Flip to back and install 4 screws Install five case screws Install the mounting ear as needed The main device installation is complete","title":"BLIHAT \u5b89\u88c5\u8bf4\u660e"},{"location":"BLIKVM-CM4-guide/","text":"BLIKVM v1 CM4\u4f7f\u7528\u8bf4\u660e BLIKVM CM4 v1\u8bc4\u6d4b\u89c6\u9891 BliKVM v1\u662f\u4e00\u6b3e\u751f\u4ea7\u5c31\u7eea\u3001\u5373\u63d2\u5373\u7528\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86\u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406\u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e\u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5\u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1\uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01 BliKVM v1 Datasheet \u529f\u80fd\u7279\u70b9 \u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@60Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 WiFi \uff08\u53ef\u9009\uff09 OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) \u5b89\u88c5\u8981\u6c42 \u5982\u679c\u4f60\u8d2d\u4e70\u7684\u662f\u9700\u81ea\u5df1\u7ec4\u88c5\u7684\u7248\u672c\uff08\u4e0d\u662fplug-n-play\u7248\u672c\uff09\uff0c\u4f60\u9700\u8981\u81ea\u5df1\u51c6\u5907\u4ee5\u4e0b\u8bbe\u5907 \u6811\u8393\u6d3eCM4\uff0c\u6700\u5c0f1Gb RAM. USB-C\u8f6cUSB-A\u7ebf\u7f06. HDMI\u7ebf\u7f06. \u7f51\u7ebf. \u7535\u6e90\u9002\u914d\u5668(5.1V 3A USB-C). \u7535\u6e90\u9002\u914d\u5668 \u5728BLIKVM CM4 V2.2\u7248\u672c\u4e2d\uff0c\u4f60\u5fc5\u987b\u4f7f\u7528USB-C\u8f6cUSB-A\u7ebf\u7f06\u8fdb\u884c\u4f9b\u7535\uff0c\u5982\u679c\u4f7f\u7528USB-C\u8f6cUSB-C\u7ebf\u7f06\u53ef\u80fd\u65e0\u6cd5\u4f9b\u7535\u3002\u8fd9\u662f\u8fd9\u4e2a\u7248\u672c\u786c\u4ef6\u8bbe\u8ba1\u7684bug\uff0c\u5728\u5b83\u540e\u9762\u7684\u7248\u672c \u4e2d\u6b64\u95ee\u9898\u5c06\u4f1a\u88ab\u4fee\u590d\u3002 \u57fa\u7840\u914d\u7f6e 1. \u51fa\u5382\u9ed8\u8ba4\u914d\u7684SD\u5361\u5df2\u70e7\u5f55\u955c\u50cf\uff0c\u65e0\u9700\u70e7\u5f55\u3002\u82e5\u60a8\u9700\u8981\u91cd\u5237\u7cfb\u7edf\u6216\u8005DIY\uff0c\u53ef\u53c2\u8003 \u70e7\u5f55\u955c\u50cf\u5230SD\u5361\u6216\u8005eMMC 2. \u5982\u679c\u60a8\u4e0d\u662fplug\u7248\u672c,\u53c2\u8003\u4e0b\u9762\u7684\u89c6\u9891\u548c\u8bf4\u660e\u8fdb\u884c\u8bbe\u5907\u5b89\u88c5: 1. \u7528\u5305\u88f9\u914d\u7684\u87ba\u4e1d\u5200\u6253\u5f00\u91d1\u5c5e\u5916\u58f3\uff0c\u62c6\u4e0bPCB\u4e3b\u677f\uff1b 2. \u5c06CM4\u5b89\u88c5\u5728PCB\u4e3b\u677f\u4e0a\uff0c\u6ce8\u610f\u5b89\u88c5CM4\u65f6\u4e24\u6392\u5361\u69fd\u8981\u5bf9\u9f50\uff0c\u7136\u540e\u5c06\u7845\u80f6\u5bfc\u70ed\u7247\u8d34\u5728CM4\u4e3b\u82af\u7247\u4e0a\uff0c\u4ece\u800c\u53ef\u4ee5\u4f7fCM4\u5229\u7528\u91d1\u5c5e\u5916\u58f3\u6563\u70ed\uff1b 3. \u98ce\u6247\u9ed8\u8ba4\u4e0d\u63a5\uff0c\u5916\u58f3\u6563\u70ed\u8db3\u591f\uff0c\u6839\u636e\u60a8\u7684CM4\u7248\u672c\u9009\u62e9\u6027\u5b89\u88c5Wi-Fi\u5929\u7ebf; 4. \u91cd\u65b0\u5b89\u88c5\u597dPCB\u4e3b\u677f\u548c\u91d1\u5c5e\u5916\u58f3\uff0c\u5373\u5b89\u88c5\u5b8c\u6210. \u5b8c\u6574\u62c6\u7bb1\u548c\u5b89\u88c5\u89c6\u9891 Ortimo\u4f7f\u7528BLIKVM CM4 eMMC\u7248\u672c\u6307\u5bfc 3. \u6839\u636e\u4e0b\u56fe\u63a5\u53e3\u5b9a\u4e49\u6240\u793a\uff0c\u8fde\u63a5\u88ab\u63a7\u7535\u8111\u5230BLIKVM\u4e0a: HDMI IN\u548cotg\u63a5\u53e3\u5fc5\u987b\u548c\u88ab\u63a7\u7535\u8111\u8fde\u63a5\uff0cATX\u662f\u53ef\u9009\u9879\u3002\u5efa\u8bae\u5728BLIKVM\u548c\u88ab\u63a7\u7535\u8111\u4e4b\u95f4\u6700\u597d\u4e0d\u8981\u6709USB\u6269\u5c55\u575e\uff0c\u56e0\u4e3a\u5728UEFI\u6216BIOS\u9636\u6bb5\uff0c\u53ef\u80fd\u68c0\u6d4b\u4e0d\u5230\u6269\u5c55\u575e\u3002 BLIKVM CM4\u7248\u672c\u6700\u9ad8\u652f\u63011080P60Hz\u7684\u8f93\u5165\u3002 \u901a\u8fc7Ethernet\u5c06BLIKVM\u8fde\u63a5\u5230\u7f51\u7edc\uff0c\u901a\u8fc7PWR IN\u7aef\u53e3\u5de5\u4f9b\u7535\u3002 4. ATX\u7535\u6e90\u63a7\u5236\u8fde\u63a5 \u4e3a\u4e86\u7ba1\u7406\u88ab\u63a7\u8ba1\u7b97\u673a\u7684\u7535\u6e90\uff0c\u4f60\u9700\u8981\u5c06CN-ATX\u7aef\u53e3\u548c\u88ab\u63a7\u7535\u8111\u8fde\u63a5\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528\u63d0\u4f9b\u7684ATX\u7ebf\u7f06(60\u5398\u7c73)\u6216\u8005\u675c\u90a6\u7ebf\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111\u7684\u4e3b\u677f\u4e0a\u3002 \u4e3a\u4e86\u517c\u5bb9\u7f51\u53e3\u5f62\u5f0f\u7684ATX\u63a7\u5236\u677f\uff0cv1\u6709\u4e13\u95e8\u7684ATX\u6269\u5c55\u5305\uff0c\u65b9\u4fbf\u5ba2\u6237\u76f4\u63a5\u901a\u8fc7\u7f51\u7ebf\u548c\u5b89\u88c5\u5230\u673a\u7bb1\u6321\u677f\u7684ATX\u677f\u8fde\u63a5\u3002 5. \u5728\u6240\u6709\u8fde\u63a5\u7ebf\u8fde\u63a5\u597d\u540e,\u5bf9BliKVM\u8fdb\u884c\u4e0a\u7535\uff0c\u76f4\u5230\u663e\u793a\u5c4f\u51fa\u73b0\u753b\u9762\uff0c\u5373\u8bbe\u5907\u6b63\u5e38\u542f\u52a8\u3002 6. \u4ed4\u7ec6\u9605\u8bfb \u201c\u7b2c\u4e00\u6b65\u201d \u6307\u5357-\u5982\u4f55\u5728\u7f51\u7edc\u4e0a\u67e5\u627e\u8bbe\u5907\u3001\u5982\u4f55\u767b\u5f55\u3001\u66f4\u6539\u5bc6\u7801\u7b49\u7b49\u3002\u6309\u7167\u4e0a\u9762\u63cf\u8ff0\u7684\u6b65\u9aa4\u64cd\u4f5c\uff0c\u7136\u540e\u8fd4\u56de\u672c\u9875\u3002 \u7531\u4e8eBliKVM v1\u4e5f\u652f\u6301PiKVM OS\uff0c\u82e5\u4f60\u624b\u4e0a\u7684v1\u51fa\u5382OS\u4e3aPiKVM\uff0c\u5173\u4e8eweb\u4f7f\u7528\u8bf4\u660e\u8bf7 \u53c2\u8003\u6587\u6863 \u3002 7. \u5c1d\u8bd5\u4f7f\u7528 Web \u754c\u9762\u7ba1\u7406\u8ba1\u7b97\u673a\u7684 BliKVM\u3002 \u786e\u4fdd\u60a8\u53ef\u4ee5\u770b\u5230\u56fe\u50cf\u5e76\u4e14\u952e\u76d8\u548c\u9f20\u6807\u90fd\u6b63\u5e38\u5de5\u4f5c\u3002\u5982\u679c\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u8bf7\u67e5\u770b\u6211\u4eec\u7684 \u5e38\u89c1\u95ee\u9898 \uff08\u5b83\u975e\u5e38\u6709\u7528\uff09\u3002\u5982\u679c\u6ca1\u6709\u4efb\u4f55\u5e2e\u52a9\uff0c\u8bf7\u5728\u6211\u4eec\u7684 Discord\u804a\u5929\u5ba4 \u5bfb\u6c42\u652f\u6301\u3002 8. \u60a8\u53ef\u4ee5\u67e5\u770bwiki\u5176\u4ed6\u7684\u9875\u9762\uff0c\u63a2\u7d22BliKVM\u7684\u66f4\u591a\u529f\u80fd\uff0c\u795d\u60a8\u73a9\u7684\u5f00\u5fc3\uff01 Wi-Fi\u5929\u7ebf\u8fde\u63a5 \u5982\u4f60\u7684CM4\u6709Wi-Fi\u529f\u80fd\uff0c\u62c6\u5f00v1\u7684\u91d1\u5c5e\u76d2\u5b50\uff0c\u8bf7\u5c06\u5305\u88f9\u4e2d\u7684Wi-Fi\u5929\u7ebf\uff0c\u5b89\u88c5\u5230CM4\u7684IPX\u63a5\u53e3\uff0c\u5373\u4e0b\u56fe\u4e2d\u7ea2\u6846\u7684\u63a5\u53e3\uff1b\u5176\u4e2d\u5916\u58f3\u5b89\u88c5\u5929\u7ebf\u4f4d\u7f6e\u4e3a\u63a5\u53e3\u5b9a\u4e49\u56fe\u4e2d\u768411\u5904\u3002 \u652f\u6301 1080p60hz HDMI\u8f93\u5165 \u5728V2.2\u7248\u672c\u4e2d\uff0c\u8fd9\u91cc\u6709\u4e00\u4e2aCSI\u901a\u9053\u5207\u6362\u5668\u3002\u786e\u8ba4\u5207\u6362\u5668\u57284\u901a\u9053\u4e00\u4fa7\u3002\u518d\u5176\u5b83\u7248\u672c\u4e2d\uff0c\u79fb\u9664\u4e86\u6b64\u5207\u6362\u5668\uff0c\u9ed8\u8ba44\u901a\u9053\u5168\u90e8\u4f7f\u80fd\u3002 \u53d1\u8d27\u6e05\u5355 BLIKVM v1 \u4e0d\u542b CM4 \u5916\u58f3 1 PCB\u4e3b\u677f 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 OLED\u5c4f\u5e55 1 BLIKVM v1\u542b CM4102000 \u5916\u58f3 1 PCB\u4e3b\u677f 1 CM4102000 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 OLED\u5c4f\u5e55 1 WiFi\u5929\u7ebf 1 BLIKVM v1 \u542b CM4002000 \u5916\u58f3 1 PCB\u4e3b\u677f 1 CM4002000 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 WiFi\u5929\u7ebf 1 \u8d2d\u4e70\u94fe\u63a5 v1\u6dd8\u5b9d\u5730\u5740","title":"BliKVM v1 CM4\u5bfc\u89c8"},{"location":"BLIKVM-CM4-guide/#blikvm-v1-cm4","text":"BLIKVM CM4 v1\u8bc4\u6d4b\u89c6\u9891 BliKVM v1\u662f\u4e00\u6b3e\u751f\u4ea7\u5c31\u7eea\u3001\u5373\u63d2\u5373\u7528\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86\u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406\u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e\u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5\u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1\uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01 BliKVM v1 Datasheet","title":"BLIKVM v1 CM4\u4f7f\u7528\u8bf4\u660e"},{"location":"BLIKVM-CM4-guide/#_1","text":"\u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@60Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 WiFi \uff08\u53ef\u9009\uff09 OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC)","title":"\u529f\u80fd\u7279\u70b9"},{"location":"BLIKVM-CM4-guide/#_2","text":"\u5982\u679c\u4f60\u8d2d\u4e70\u7684\u662f\u9700\u81ea\u5df1\u7ec4\u88c5\u7684\u7248\u672c\uff08\u4e0d\u662fplug-n-play\u7248\u672c\uff09\uff0c\u4f60\u9700\u8981\u81ea\u5df1\u51c6\u5907\u4ee5\u4e0b\u8bbe\u5907 \u6811\u8393\u6d3eCM4\uff0c\u6700\u5c0f1Gb RAM. USB-C\u8f6cUSB-A\u7ebf\u7f06. HDMI\u7ebf\u7f06. \u7f51\u7ebf. \u7535\u6e90\u9002\u914d\u5668(5.1V 3A USB-C). \u7535\u6e90\u9002\u914d\u5668 \u5728BLIKVM CM4 V2.2\u7248\u672c\u4e2d\uff0c\u4f60\u5fc5\u987b\u4f7f\u7528USB-C\u8f6cUSB-A\u7ebf\u7f06\u8fdb\u884c\u4f9b\u7535\uff0c\u5982\u679c\u4f7f\u7528USB-C\u8f6cUSB-C\u7ebf\u7f06\u53ef\u80fd\u65e0\u6cd5\u4f9b\u7535\u3002\u8fd9\u662f\u8fd9\u4e2a\u7248\u672c\u786c\u4ef6\u8bbe\u8ba1\u7684bug\uff0c\u5728\u5b83\u540e\u9762\u7684\u7248\u672c \u4e2d\u6b64\u95ee\u9898\u5c06\u4f1a\u88ab\u4fee\u590d\u3002","title":"\u5b89\u88c5\u8981\u6c42"},{"location":"BLIKVM-CM4-guide/#_3","text":"1. \u51fa\u5382\u9ed8\u8ba4\u914d\u7684SD\u5361\u5df2\u70e7\u5f55\u955c\u50cf\uff0c\u65e0\u9700\u70e7\u5f55\u3002\u82e5\u60a8\u9700\u8981\u91cd\u5237\u7cfb\u7edf\u6216\u8005DIY\uff0c\u53ef\u53c2\u8003 \u70e7\u5f55\u955c\u50cf\u5230SD\u5361\u6216\u8005eMMC 2. \u5982\u679c\u60a8\u4e0d\u662fplug\u7248\u672c,\u53c2\u8003\u4e0b\u9762\u7684\u89c6\u9891\u548c\u8bf4\u660e\u8fdb\u884c\u8bbe\u5907\u5b89\u88c5: 1. \u7528\u5305\u88f9\u914d\u7684\u87ba\u4e1d\u5200\u6253\u5f00\u91d1\u5c5e\u5916\u58f3\uff0c\u62c6\u4e0bPCB\u4e3b\u677f\uff1b 2. \u5c06CM4\u5b89\u88c5\u5728PCB\u4e3b\u677f\u4e0a\uff0c\u6ce8\u610f\u5b89\u88c5CM4\u65f6\u4e24\u6392\u5361\u69fd\u8981\u5bf9\u9f50\uff0c\u7136\u540e\u5c06\u7845\u80f6\u5bfc\u70ed\u7247\u8d34\u5728CM4\u4e3b\u82af\u7247\u4e0a\uff0c\u4ece\u800c\u53ef\u4ee5\u4f7fCM4\u5229\u7528\u91d1\u5c5e\u5916\u58f3\u6563\u70ed\uff1b 3. \u98ce\u6247\u9ed8\u8ba4\u4e0d\u63a5\uff0c\u5916\u58f3\u6563\u70ed\u8db3\u591f\uff0c\u6839\u636e\u60a8\u7684CM4\u7248\u672c\u9009\u62e9\u6027\u5b89\u88c5Wi-Fi\u5929\u7ebf; 4. \u91cd\u65b0\u5b89\u88c5\u597dPCB\u4e3b\u677f\u548c\u91d1\u5c5e\u5916\u58f3\uff0c\u5373\u5b89\u88c5\u5b8c\u6210. \u5b8c\u6574\u62c6\u7bb1\u548c\u5b89\u88c5\u89c6\u9891 Ortimo\u4f7f\u7528BLIKVM CM4 eMMC\u7248\u672c\u6307\u5bfc 3. \u6839\u636e\u4e0b\u56fe\u63a5\u53e3\u5b9a\u4e49\u6240\u793a\uff0c\u8fde\u63a5\u88ab\u63a7\u7535\u8111\u5230BLIKVM\u4e0a: HDMI IN\u548cotg\u63a5\u53e3\u5fc5\u987b\u548c\u88ab\u63a7\u7535\u8111\u8fde\u63a5\uff0cATX\u662f\u53ef\u9009\u9879\u3002\u5efa\u8bae\u5728BLIKVM\u548c\u88ab\u63a7\u7535\u8111\u4e4b\u95f4\u6700\u597d\u4e0d\u8981\u6709USB\u6269\u5c55\u575e\uff0c\u56e0\u4e3a\u5728UEFI\u6216BIOS\u9636\u6bb5\uff0c\u53ef\u80fd\u68c0\u6d4b\u4e0d\u5230\u6269\u5c55\u575e\u3002 BLIKVM CM4\u7248\u672c\u6700\u9ad8\u652f\u63011080P60Hz\u7684\u8f93\u5165\u3002 \u901a\u8fc7Ethernet\u5c06BLIKVM\u8fde\u63a5\u5230\u7f51\u7edc\uff0c\u901a\u8fc7PWR IN\u7aef\u53e3\u5de5\u4f9b\u7535\u3002 4. ATX\u7535\u6e90\u63a7\u5236\u8fde\u63a5 \u4e3a\u4e86\u7ba1\u7406\u88ab\u63a7\u8ba1\u7b97\u673a\u7684\u7535\u6e90\uff0c\u4f60\u9700\u8981\u5c06CN-ATX\u7aef\u53e3\u548c\u88ab\u63a7\u7535\u8111\u8fde\u63a5\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528\u63d0\u4f9b\u7684ATX\u7ebf\u7f06(60\u5398\u7c73)\u6216\u8005\u675c\u90a6\u7ebf\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111\u7684\u4e3b\u677f\u4e0a\u3002 \u4e3a\u4e86\u517c\u5bb9\u7f51\u53e3\u5f62\u5f0f\u7684ATX\u63a7\u5236\u677f\uff0cv1\u6709\u4e13\u95e8\u7684ATX\u6269\u5c55\u5305\uff0c\u65b9\u4fbf\u5ba2\u6237\u76f4\u63a5\u901a\u8fc7\u7f51\u7ebf\u548c\u5b89\u88c5\u5230\u673a\u7bb1\u6321\u677f\u7684ATX\u677f\u8fde\u63a5\u3002 5. \u5728\u6240\u6709\u8fde\u63a5\u7ebf\u8fde\u63a5\u597d\u540e,\u5bf9BliKVM\u8fdb\u884c\u4e0a\u7535\uff0c\u76f4\u5230\u663e\u793a\u5c4f\u51fa\u73b0\u753b\u9762\uff0c\u5373\u8bbe\u5907\u6b63\u5e38\u542f\u52a8\u3002 6. \u4ed4\u7ec6\u9605\u8bfb \u201c\u7b2c\u4e00\u6b65\u201d \u6307\u5357-\u5982\u4f55\u5728\u7f51\u7edc\u4e0a\u67e5\u627e\u8bbe\u5907\u3001\u5982\u4f55\u767b\u5f55\u3001\u66f4\u6539\u5bc6\u7801\u7b49\u7b49\u3002\u6309\u7167\u4e0a\u9762\u63cf\u8ff0\u7684\u6b65\u9aa4\u64cd\u4f5c\uff0c\u7136\u540e\u8fd4\u56de\u672c\u9875\u3002 \u7531\u4e8eBliKVM v1\u4e5f\u652f\u6301PiKVM OS\uff0c\u82e5\u4f60\u624b\u4e0a\u7684v1\u51fa\u5382OS\u4e3aPiKVM\uff0c\u5173\u4e8eweb\u4f7f\u7528\u8bf4\u660e\u8bf7 \u53c2\u8003\u6587\u6863 \u3002 7. \u5c1d\u8bd5\u4f7f\u7528 Web \u754c\u9762\u7ba1\u7406\u8ba1\u7b97\u673a\u7684 BliKVM\u3002 \u786e\u4fdd\u60a8\u53ef\u4ee5\u770b\u5230\u56fe\u50cf\u5e76\u4e14\u952e\u76d8\u548c\u9f20\u6807\u90fd\u6b63\u5e38\u5de5\u4f5c\u3002\u5982\u679c\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u8bf7\u67e5\u770b\u6211\u4eec\u7684 \u5e38\u89c1\u95ee\u9898 \uff08\u5b83\u975e\u5e38\u6709\u7528\uff09\u3002\u5982\u679c\u6ca1\u6709\u4efb\u4f55\u5e2e\u52a9\uff0c\u8bf7\u5728\u6211\u4eec\u7684 Discord\u804a\u5929\u5ba4 \u5bfb\u6c42\u652f\u6301\u3002 8. \u60a8\u53ef\u4ee5\u67e5\u770bwiki\u5176\u4ed6\u7684\u9875\u9762\uff0c\u63a2\u7d22BliKVM\u7684\u66f4\u591a\u529f\u80fd\uff0c\u795d\u60a8\u73a9\u7684\u5f00\u5fc3\uff01","title":"\u57fa\u7840\u914d\u7f6e"},{"location":"BLIKVM-CM4-guide/#wi-fi","text":"\u5982\u4f60\u7684CM4\u6709Wi-Fi\u529f\u80fd\uff0c\u62c6\u5f00v1\u7684\u91d1\u5c5e\u76d2\u5b50\uff0c\u8bf7\u5c06\u5305\u88f9\u4e2d\u7684Wi-Fi\u5929\u7ebf\uff0c\u5b89\u88c5\u5230CM4\u7684IPX\u63a5\u53e3\uff0c\u5373\u4e0b\u56fe\u4e2d\u7ea2\u6846\u7684\u63a5\u53e3\uff1b\u5176\u4e2d\u5916\u58f3\u5b89\u88c5\u5929\u7ebf\u4f4d\u7f6e\u4e3a\u63a5\u53e3\u5b9a\u4e49\u56fe\u4e2d\u768411\u5904\u3002","title":"Wi-Fi\u5929\u7ebf\u8fde\u63a5"},{"location":"BLIKVM-CM4-guide/#1080p60hz-hdmi","text":"\u5728V2.2\u7248\u672c\u4e2d\uff0c\u8fd9\u91cc\u6709\u4e00\u4e2aCSI\u901a\u9053\u5207\u6362\u5668\u3002\u786e\u8ba4\u5207\u6362\u5668\u57284\u901a\u9053\u4e00\u4fa7\u3002\u518d\u5176\u5b83\u7248\u672c\u4e2d\uff0c\u79fb\u9664\u4e86\u6b64\u5207\u6362\u5668\uff0c\u9ed8\u8ba44\u901a\u9053\u5168\u90e8\u4f7f\u80fd\u3002","title":"\u652f\u6301 1080p60hz HDMI\u8f93\u5165"},{"location":"BLIKVM-CM4-guide/#_4","text":"BLIKVM v1 \u4e0d\u542b CM4 \u5916\u58f3 1 PCB\u4e3b\u677f 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 OLED\u5c4f\u5e55 1 BLIKVM v1\u542b CM4102000 \u5916\u58f3 1 PCB\u4e3b\u677f 1 CM4102000 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 OLED\u5c4f\u5e55 1 WiFi\u5929\u7ebf 1 BLIKVM v1 \u542b CM4002000 \u5916\u58f3 1 PCB\u4e3b\u677f 1 CM4002000 1 \u98ce\u6247 1 SD\u5361 32G 1 ATX\u675c\u90a6\u7ebf\u7f06 1 WiFi\u5929\u7ebf 1","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"BLIKVM-CM4-guide/#_5","text":"v1\u6dd8\u5b9d\u5730\u5740","title":"\u8d2d\u4e70\u94fe\u63a5"},{"location":"BLIKVM-HAT-guide/","text":"BliKVM Hat \u4f7f\u7528\u8bf4\u660e \u4ecb\u7ecd BliKVM Hat 360\u5ea6 \u89c6\u9891 BliKVM Hat\u7248\u672c\u662f\u57fa\u4e8e\u6811\u8393\u6d3e4B\u5236\u4f5c\u7684\u4e00\u6b3e\u786c\u4ef6\uff0c\u7528\u4e8eKVM Over IP\u3002Hat\u5173\u952e\u529f\u80fd\u5305\u62ecHDMI\u89c6\u9891\u6355\u83b7\u3001ATX\u63a7\u5236\u3001PoE\u4f9b\u7535\u3001OLED\u5c4f\u5e55\u663e\u793a\u3001RTC\u65f6\u949f\u3002 Hat\u914d\u6709\u91d1\u5c5e\u5916\u58f3\uff0c\u7528\u4e8e\u4fdd\u62a4\u548c\u6563\u70ed\u3002Hat\u53ef\u4ee5\u88ab\u5b89\u88c5\u52301U\u7684\u673a\u67b6\u3002\u540c\u65f6\u652f\u6301blikvm\u955c\u50cf\u548cpikvm\u955c\u50cf\u3002 \u5b89\u88c5\u8981\u6c42 \u5982\u679c\u4f60\u8d2d\u4e70\u7684\u53ea\u662f\u4e00\u4e2aHat\uff0c\u4f60\u8fd8\u9700\u8981\u4e0b\u9762\u8bbe\u5907 \u6811\u8393\u6d3e4B\uff0c1GB RAM\u6216\u8005\u66f4\u591a MicroSD card (\u63a8\u8350\u6700\u5c1116Gb, class 10). HDMI \u7ebf\u7f06. \u7f51\u7ebf (\u7528\u4e8eHat\u548cATX\u7684\u8fde\u63a5). \u7535\u6e90\u9002\u914d\u5668\u548c\u7ebf\u7f06(5.1V 3A USB-C). \u529f\u80fd \u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@50Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE \u4f9b\u7535 \u652f\u6301\u4e32\u53e3\u7ec8\u7aef OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) PWM\u98ce\u6247 \u57fa\u7840\u8bbe\u7f6e 1. \u70e7\u5f55\u955c\u50cf 2.\u7ec4\u88c5Hat \u53c2\u8003\u4e0b\u9762\u7684\u89c6\u9891\u8bf4\u660e\u6216\u8005\u53c2\u8003 \u56fe\u6587\u8bf4\u660e : Hat \u89c6\u9891\u5b89\u88c5\u5bfc\u89c8: \u624b\u628a\u624b\u6559\u4f60\u5982\u4f55\u7ec4\u88c5Hat\u5230\u6811\u8393\u6d3e\u4e0a 3. \u5b89\u88c5 ATX \u6a21\u5757 ATX\u6a21\u5757\u914d\u6709\u4e00\u4e2a\u5168\u9ad8\u6216\u8005\u534a\u9ad8\u7684PCIe\u6321\u677f\uff0c\u4f60\u53ef\u4ee5\u6839\u636e\u9700\u6c42\u9009\u62e9\u5b89\u88c5 \u4f7f\u7528\u675c\u90a6\u7ebf\u8fde\u63a5ATX\u6a21\u5757\u548c\u673a\u7bb1\u91cc\u7684\u4e3b\u677f\uff0cATX\u6a21\u5757\u4e0a\u90fd\u6709\u6e05\u6670\u7684\u5f15\u811a\u5b9a\u4e49\u65b9\u4fbf\u4f60\u8fde\u63a5 \u5c06ATX\u6a21\u5757\u5b89\u88c5\u5230\u673a\u7bb1\u5916\u58f3\u4e0a \u4f7f\u7528RJ45\u7684\u7f51\u7ebf\u8fde\u63a5ATX\u548cHat 4. \u8fde\u63a5HDMI\u7ebf\u7f06 \u4f7f\u7528HDMI\u7ebf\u7f06\uff0c\u5c06\u88ab\u63a7\u7535\u8111\u7684HDMI\u548cHat\u7684HDMI IN\u7aef\u53e3\u8fde\u63a5\u3002HDMI\u6a21\u62df\u5668\u4e0d\u662f\u5fc5\u987b\u4f7f\u7528\u7684\uff0c\u5f53\u4f60\u7684\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8f93\u51fa\u753b\u9762\u65f6\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528HDMI\u6a21\u62df\u5668\u6765\u6821\u6b63\u7535\u8111\u7684HDMI\u8f93\u51fa 5. \u5b89\u88c5USB\u7ebf\u7f06 \u8bf7\u6ce8\u610f\u8fd9\u91cc\u4f7f\u7528USB\u5206\u7535\u677f\u4e0d\u662f\u5fc5\u987b\u7684\uff0c\u5982\u679c\u4f60\u4f7f\u7528PoE\u4f9b\u7535\u4e0d\u9700\u8981\u4f7f\u7528\u6b64\u6a21\u5757\uff0c\u5982\u679c\u4f60\u9700\u8981\u4f7f\u7528USB\u4f9b\u7535\u5219\u9700\u8981\u3002\u901a\u8fc7USB-C\u7ebf\u8fde\u63a5\u6811\u8393\u6d3e4B\u7684TYPE-C\u53e3\u5230\u5206\u7535\u677f\u7684RPI4\u7aef\u53e3 \u8fde\u63a5\u5206\u7535\u677f\u4e0a\u7684USB\u7aef\u53e3\u5230\u88ab\u63a7\u7535\u8111 \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u8bf7\u6ce8\u610f\u4e0d\u9700\u8981\u5728\u4f7f\u7528USB\u4f9b\u7535\u8bbe\u5907\u3002\u5f53\u4e0d\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u63a8\u8350\u4f7f\u75285V/3A\u7684\u7535\u6e90\u9002\u914d\u5668\u5230\u5206\u7535\u677f\u7684PWR\u7aef\u53e3 6. \u6d4b\u8bd5 \u56fe\u4e2d\u901a\u8fc7PoE\u4f9b\u7535\uff0cHat\u901a\u8fc7\u7f51\u7ebf\u8fde\u63a5\u5230\u7f51\u7edc\u4e2d OLED\u5c4f\u5e55\u5c06\u4f1a\u6b63\u5e38\u663e\u793a\u8bbe\u5907\u7684\u5de5\u4f5c\u72b6\u6001\uff0c\u5305\u62ec\u8bbe\u5907\u7684IP\u5730\u5740 \u6253\u5f00\u6d4f\u89c8\u5668\uff0c\u8f93\u5165\u8bbe\u5907\u7684IP\u5730\u5740\uff0c\u5373\u53ef\u6253\u5f00\u63a7\u5236\u7684WEB\u754c\u9762\uff0c\u73b0\u5728\u53bb\u4f7f\u7528\u5b83\u5427\uff01 \u6027\u80fd\u53c2\u6570 HDMI \u8f93\u5165 \u4f7f\u7528Toshiba TC358743\u4e3aHDMI\u8f6c\u6362\u7684\u4e3b\u82af\u7247\uff0c\u540c\u65f6\u652f\u6301\u89c6\u9891\u548c\u58f0\u97f3\u7684\u91c7\u96c6\uff0c\u652f\u6301\u89c6\u9891\u6700\u9ad8\u8f93\u5165\u4e3a1080P50Hz.\u89e3\u51b3\u4e86HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898\u3002 CN-ATX CN-ATX\u63a5\u53e3\u901a\u8fc7\u7f51\u7ebf\u8fde\u63a5ATX\u6a21\u5757\uff0c\u7528\u6765\u63a7\u5236\u88ab\u63a7\u7535\u8111\u7684\u5f00\u673a\u3001\u5173\u673a\u3001\u548c\u91cd\u542f\u64cd\u4f5c\u3002 \u663e\u793a\u5c4f \u914d\u6709\u767d\u8272\u7684\u663e\u793a\u5c4f\uff0c\u5206\u8fa8\u7387\u4e3a128x32\uff0c\u4f7f\u7528\u82af\u7247\u4e3aSSD1306\u3002\u663e\u793a\u5c4f\u4f1a\u663e\u793a\u5982\u6e29\u5ea6\u3001IP\u5730\u5740\u7b49\u6811\u8393\u6d3e\u7684\u4fe1\u606f\u3002 PoE \u6807\u51c6: IEEE 802.3af PoE \u8f93\u5165\u7535\u538b: 37-57 V DC \u8f93\u51fa\u7535\u538b: 5 V DC/2.4 A \u4f7f\u7528PoE\u6a21\u5757\u4f9b\u7535\uff0c\u9700\u8981\u5c06Hat\u4e0a\u7684PoE\u7684\u5f15\u811a\u4f7f\u7528\u8df3\u7ebf\u5e3d\u77ed\u63a5\u3002 \u98ce\u6247 \u98ce\u6247\u9ed8\u8ba4\u4f7f\u7528\u6811\u8393\u6d3e\u4e0a\u7684GPIO12\u63a7\u5236\u3002 RTC\u65f6\u949f RTC\u65f6\u949f\u4e3b\u82af\u7247\u4e3aPCF8563\uff0c\u901a\u8fc7I2C\u548c\u6811\u8393\u6d3e\u8fde\u63a5\u3002\u542f\u7528RTC\u65f6\u949f\u5de5\u4f5c\u7684\u7ebd\u6263\u7535\u6c60\u5b89\u88c5\u4f4d\u7f6e\u5728HDMI-IN\u6a21\u5757\u7684\u4e0b\u9762\u3002 \u914d\u4ef6 ATX\u6a21\u5757 ATX\u6a21\u5757\u901a\u8fc7\u675c\u90a6\u7ebf\u548c\u7535\u8111\u7684\u4e3b\u677f\u8fde\u63a5\u3002ATX\u6a21\u5757\u914d\u6709\u5168\u9ad8\u548c\u534a\u9ad8\u7684PCIe\u6321\u677f\u3002 USB/PWR \u5206\u7535\u677f RPI4\u7aef\u53e3\u7528\u4e8e\u8fde\u63a5\u5230\u6811\u8393\u6d3e4B. USB\u7aef\u53e3\u7528\u4e8e\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111. \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u4e0d\u9700\u8981\u4f7f\u7528\u5206\u7535\u677f. HDMI\u6a21\u62df\u5668 \u5982\u679c\u88ab\u63a7\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8f93\u51fa\u753b\u9762\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528\u6b64\u6a21\u5757\u6765\u89e3\u51b3\u3002\u5c06\u6b64\u6a21\u5757\u8fde\u63a5\u5230Hat\u4e0a\u540e\uff0c\u518d\u901a\u8fc7HDMI\u7ebf\u7f06\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111\u3002 \u91d1\u5c5e\u5916\u58f3 \u91d1\u5c5e\u5916\u58f3\u53ef\u4ee5\u4fdd\u62a4Hat\u548c\u7528\u4e8e\u6563\u70ed.\u5916\u58f3\u4e0a\u6bcf\u4e2a\u7aef\u53e3\u6709\u6e05\u6670\u7684\u4e1d\u5370\u6765\u8868\u793a\u6b64\u7aef\u53e3\u7528\u9014\u3002\u6b64\u5916\u58f3\u53ef\u4ee5\u65b9\u4fbf\u7684\u5b89\u88c5\u57281U\u7684\u673a\u67b6\u4e0a\u3002 List Product List BliKVM Hat \u6a21\u5757 1 ATX \u6a21\u5757 1 USB/PWR \u5206\u7535\u677f 1 HDMI\u6a21\u62df\u5668 1 \u91d1\u5c5e\u5916\u58f3 1 32G TF \u5361 1 USB Type-C \u8f6c USB Type-C \u7ebf\u7f06 30cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 \u5341\u5b57\u6273\u624b\u5957\u7b52 1 \u7528\u6237\u9700\u8981\u51c6\u5907\u8bbe\u5907\u7684\u6e05\u5355 \u6811\u8393\u6d3e4B 1 RJ45 \u7f51\u7ebf 2 USB Type-A \u8f6c USB Type-C \u7ebf\u7f06 2 HDMI \u7ebf\u7f06 1 PoE\u4f9b\u7535\u8bbe\u5907 or 5V/3A USB \u7535\u6e90\u9002\u914d\u5668 1 CR1220\u7ebd\u6263\u7535\u6c60 1 \u8d2d\u4e70\u94fe\u63a5 v3\u6dd8\u5b9d\u5730\u5740","title":"BliKVM v3 HAT\u5bfc\u89c8"},{"location":"BLIKVM-HAT-guide/#blikvm-hat","text":"","title":"BliKVM Hat \u4f7f\u7528\u8bf4\u660e"},{"location":"BLIKVM-HAT-guide/#_1","text":"BliKVM Hat 360\u5ea6 \u89c6\u9891 BliKVM Hat\u7248\u672c\u662f\u57fa\u4e8e\u6811\u8393\u6d3e4B\u5236\u4f5c\u7684\u4e00\u6b3e\u786c\u4ef6\uff0c\u7528\u4e8eKVM Over IP\u3002Hat\u5173\u952e\u529f\u80fd\u5305\u62ecHDMI\u89c6\u9891\u6355\u83b7\u3001ATX\u63a7\u5236\u3001PoE\u4f9b\u7535\u3001OLED\u5c4f\u5e55\u663e\u793a\u3001RTC\u65f6\u949f\u3002 Hat\u914d\u6709\u91d1\u5c5e\u5916\u58f3\uff0c\u7528\u4e8e\u4fdd\u62a4\u548c\u6563\u70ed\u3002Hat\u53ef\u4ee5\u88ab\u5b89\u88c5\u52301U\u7684\u673a\u67b6\u3002\u540c\u65f6\u652f\u6301blikvm\u955c\u50cf\u548cpikvm\u955c\u50cf\u3002","title":"\u4ecb\u7ecd"},{"location":"BLIKVM-HAT-guide/#_2","text":"\u5982\u679c\u4f60\u8d2d\u4e70\u7684\u53ea\u662f\u4e00\u4e2aHat\uff0c\u4f60\u8fd8\u9700\u8981\u4e0b\u9762\u8bbe\u5907 \u6811\u8393\u6d3e4B\uff0c1GB RAM\u6216\u8005\u66f4\u591a MicroSD card (\u63a8\u8350\u6700\u5c1116Gb, class 10). HDMI \u7ebf\u7f06. \u7f51\u7ebf (\u7528\u4e8eHat\u548cATX\u7684\u8fde\u63a5). \u7535\u6e90\u9002\u914d\u5668\u548c\u7ebf\u7f06(5.1V 3A USB-C).","title":"\u5b89\u88c5\u8981\u6c42"},{"location":"BLIKVM-HAT-guide/#_3","text":"\u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@50Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE \u4f9b\u7535 \u652f\u6301\u4e32\u53e3\u7ec8\u7aef OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) PWM\u98ce\u6247","title":"\u529f\u80fd"},{"location":"BLIKVM-HAT-guide/#_4","text":"1. \u70e7\u5f55\u955c\u50cf 2.\u7ec4\u88c5Hat \u53c2\u8003\u4e0b\u9762\u7684\u89c6\u9891\u8bf4\u660e\u6216\u8005\u53c2\u8003 \u56fe\u6587\u8bf4\u660e : Hat \u89c6\u9891\u5b89\u88c5\u5bfc\u89c8: \u624b\u628a\u624b\u6559\u4f60\u5982\u4f55\u7ec4\u88c5Hat\u5230\u6811\u8393\u6d3e\u4e0a 3. \u5b89\u88c5 ATX \u6a21\u5757 ATX\u6a21\u5757\u914d\u6709\u4e00\u4e2a\u5168\u9ad8\u6216\u8005\u534a\u9ad8\u7684PCIe\u6321\u677f\uff0c\u4f60\u53ef\u4ee5\u6839\u636e\u9700\u6c42\u9009\u62e9\u5b89\u88c5 \u4f7f\u7528\u675c\u90a6\u7ebf\u8fde\u63a5ATX\u6a21\u5757\u548c\u673a\u7bb1\u91cc\u7684\u4e3b\u677f\uff0cATX\u6a21\u5757\u4e0a\u90fd\u6709\u6e05\u6670\u7684\u5f15\u811a\u5b9a\u4e49\u65b9\u4fbf\u4f60\u8fde\u63a5 \u5c06ATX\u6a21\u5757\u5b89\u88c5\u5230\u673a\u7bb1\u5916\u58f3\u4e0a \u4f7f\u7528RJ45\u7684\u7f51\u7ebf\u8fde\u63a5ATX\u548cHat 4. \u8fde\u63a5HDMI\u7ebf\u7f06 \u4f7f\u7528HDMI\u7ebf\u7f06\uff0c\u5c06\u88ab\u63a7\u7535\u8111\u7684HDMI\u548cHat\u7684HDMI IN\u7aef\u53e3\u8fde\u63a5\u3002HDMI\u6a21\u62df\u5668\u4e0d\u662f\u5fc5\u987b\u4f7f\u7528\u7684\uff0c\u5f53\u4f60\u7684\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8f93\u51fa\u753b\u9762\u65f6\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528HDMI\u6a21\u62df\u5668\u6765\u6821\u6b63\u7535\u8111\u7684HDMI\u8f93\u51fa 5. \u5b89\u88c5USB\u7ebf\u7f06 \u8bf7\u6ce8\u610f\u8fd9\u91cc\u4f7f\u7528USB\u5206\u7535\u677f\u4e0d\u662f\u5fc5\u987b\u7684\uff0c\u5982\u679c\u4f60\u4f7f\u7528PoE\u4f9b\u7535\u4e0d\u9700\u8981\u4f7f\u7528\u6b64\u6a21\u5757\uff0c\u5982\u679c\u4f60\u9700\u8981\u4f7f\u7528USB\u4f9b\u7535\u5219\u9700\u8981\u3002\u901a\u8fc7USB-C\u7ebf\u8fde\u63a5\u6811\u8393\u6d3e4B\u7684TYPE-C\u53e3\u5230\u5206\u7535\u677f\u7684RPI4\u7aef\u53e3 \u8fde\u63a5\u5206\u7535\u677f\u4e0a\u7684USB\u7aef\u53e3\u5230\u88ab\u63a7\u7535\u8111 \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u8bf7\u6ce8\u610f\u4e0d\u9700\u8981\u5728\u4f7f\u7528USB\u4f9b\u7535\u8bbe\u5907\u3002\u5f53\u4e0d\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u63a8\u8350\u4f7f\u75285V/3A\u7684\u7535\u6e90\u9002\u914d\u5668\u5230\u5206\u7535\u677f\u7684PWR\u7aef\u53e3 6. \u6d4b\u8bd5 \u56fe\u4e2d\u901a\u8fc7PoE\u4f9b\u7535\uff0cHat\u901a\u8fc7\u7f51\u7ebf\u8fde\u63a5\u5230\u7f51\u7edc\u4e2d OLED\u5c4f\u5e55\u5c06\u4f1a\u6b63\u5e38\u663e\u793a\u8bbe\u5907\u7684\u5de5\u4f5c\u72b6\u6001\uff0c\u5305\u62ec\u8bbe\u5907\u7684IP\u5730\u5740 \u6253\u5f00\u6d4f\u89c8\u5668\uff0c\u8f93\u5165\u8bbe\u5907\u7684IP\u5730\u5740\uff0c\u5373\u53ef\u6253\u5f00\u63a7\u5236\u7684WEB\u754c\u9762\uff0c\u73b0\u5728\u53bb\u4f7f\u7528\u5b83\u5427\uff01","title":"\u57fa\u7840\u8bbe\u7f6e"},{"location":"BLIKVM-HAT-guide/#_5","text":"HDMI \u8f93\u5165 \u4f7f\u7528Toshiba TC358743\u4e3aHDMI\u8f6c\u6362\u7684\u4e3b\u82af\u7247\uff0c\u540c\u65f6\u652f\u6301\u89c6\u9891\u548c\u58f0\u97f3\u7684\u91c7\u96c6\uff0c\u652f\u6301\u89c6\u9891\u6700\u9ad8\u8f93\u5165\u4e3a1080P50Hz.\u89e3\u51b3\u4e86HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898\u3002 CN-ATX CN-ATX\u63a5\u53e3\u901a\u8fc7\u7f51\u7ebf\u8fde\u63a5ATX\u6a21\u5757\uff0c\u7528\u6765\u63a7\u5236\u88ab\u63a7\u7535\u8111\u7684\u5f00\u673a\u3001\u5173\u673a\u3001\u548c\u91cd\u542f\u64cd\u4f5c\u3002 \u663e\u793a\u5c4f \u914d\u6709\u767d\u8272\u7684\u663e\u793a\u5c4f\uff0c\u5206\u8fa8\u7387\u4e3a128x32\uff0c\u4f7f\u7528\u82af\u7247\u4e3aSSD1306\u3002\u663e\u793a\u5c4f\u4f1a\u663e\u793a\u5982\u6e29\u5ea6\u3001IP\u5730\u5740\u7b49\u6811\u8393\u6d3e\u7684\u4fe1\u606f\u3002 PoE \u6807\u51c6: IEEE 802.3af PoE \u8f93\u5165\u7535\u538b: 37-57 V DC \u8f93\u51fa\u7535\u538b: 5 V DC/2.4 A \u4f7f\u7528PoE\u6a21\u5757\u4f9b\u7535\uff0c\u9700\u8981\u5c06Hat\u4e0a\u7684PoE\u7684\u5f15\u811a\u4f7f\u7528\u8df3\u7ebf\u5e3d\u77ed\u63a5\u3002 \u98ce\u6247 \u98ce\u6247\u9ed8\u8ba4\u4f7f\u7528\u6811\u8393\u6d3e\u4e0a\u7684GPIO12\u63a7\u5236\u3002 RTC\u65f6\u949f RTC\u65f6\u949f\u4e3b\u82af\u7247\u4e3aPCF8563\uff0c\u901a\u8fc7I2C\u548c\u6811\u8393\u6d3e\u8fde\u63a5\u3002\u542f\u7528RTC\u65f6\u949f\u5de5\u4f5c\u7684\u7ebd\u6263\u7535\u6c60\u5b89\u88c5\u4f4d\u7f6e\u5728HDMI-IN\u6a21\u5757\u7684\u4e0b\u9762\u3002","title":"\u6027\u80fd\u53c2\u6570"},{"location":"BLIKVM-HAT-guide/#_6","text":"","title":"\u914d\u4ef6"},{"location":"BLIKVM-HAT-guide/#atx","text":"ATX\u6a21\u5757\u901a\u8fc7\u675c\u90a6\u7ebf\u548c\u7535\u8111\u7684\u4e3b\u677f\u8fde\u63a5\u3002ATX\u6a21\u5757\u914d\u6709\u5168\u9ad8\u548c\u534a\u9ad8\u7684PCIe\u6321\u677f\u3002","title":"ATX\u6a21\u5757"},{"location":"BLIKVM-HAT-guide/#usbpwr","text":"RPI4\u7aef\u53e3\u7528\u4e8e\u8fde\u63a5\u5230\u6811\u8393\u6d3e4B. USB\u7aef\u53e3\u7528\u4e8e\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111. \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u4e0d\u9700\u8981\u4f7f\u7528\u5206\u7535\u677f.","title":"USB/PWR \u5206\u7535\u677f"},{"location":"BLIKVM-HAT-guide/#hdmi","text":"\u5982\u679c\u88ab\u63a7\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8f93\u51fa\u753b\u9762\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528\u6b64\u6a21\u5757\u6765\u89e3\u51b3\u3002\u5c06\u6b64\u6a21\u5757\u8fde\u63a5\u5230Hat\u4e0a\u540e\uff0c\u518d\u901a\u8fc7HDMI\u7ebf\u7f06\u8fde\u63a5\u5230\u88ab\u63a7\u7535\u8111\u3002","title":"HDMI\u6a21\u62df\u5668"},{"location":"BLIKVM-HAT-guide/#_7","text":"\u91d1\u5c5e\u5916\u58f3\u53ef\u4ee5\u4fdd\u62a4Hat\u548c\u7528\u4e8e\u6563\u70ed.\u5916\u58f3\u4e0a\u6bcf\u4e2a\u7aef\u53e3\u6709\u6e05\u6670\u7684\u4e1d\u5370\u6765\u8868\u793a\u6b64\u7aef\u53e3\u7528\u9014\u3002\u6b64\u5916\u58f3\u53ef\u4ee5\u65b9\u4fbf\u7684\u5b89\u88c5\u57281U\u7684\u673a\u67b6\u4e0a\u3002","title":"\u91d1\u5c5e\u5916\u58f3"},{"location":"BLIKVM-HAT-guide/#list","text":"","title":"List"},{"location":"BLIKVM-HAT-guide/#product-list","text":"BliKVM Hat \u6a21\u5757 1 ATX \u6a21\u5757 1 USB/PWR \u5206\u7535\u677f 1 HDMI\u6a21\u62df\u5668 1 \u91d1\u5c5e\u5916\u58f3 1 32G TF \u5361 1 USB Type-C \u8f6c USB Type-C \u7ebf\u7f06 30cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 \u5341\u5b57\u6273\u624b\u5957\u7b52 1","title":"Product List"},{"location":"BLIKVM-HAT-guide/#_8","text":"\u6811\u8393\u6d3e4B 1 RJ45 \u7f51\u7ebf 2 USB Type-A \u8f6c USB Type-C \u7ebf\u7f06 2 HDMI \u7ebf\u7f06 1 PoE\u4f9b\u7535\u8bbe\u5907 or 5V/3A USB \u7535\u6e90\u9002\u914d\u5668 1 CR1220\u7ebd\u6263\u7535\u6c60 1","title":"\u7528\u6237\u9700\u8981\u51c6\u5907\u8bbe\u5907\u7684\u6e05\u5355"},{"location":"BLIKVM-HAT-guide/#_9","text":"v3\u6dd8\u5b9d\u5730\u5740","title":"\u8d2d\u4e70\u94fe\u63a5"},{"location":"BLIKVM-PCIE-guide-zh/","text":"BLIKVM PCIe \u4ecb\u7ecd BLIKVM PCIe\u662f\u4e00\u6b3e\u57fa\u4e8e\u6811\u8393\u6d3eCM4\u7684IPKVM\u6269\u5c55\u5361\uff0c\u53ef\u4ee5\u5b89\u88c5\u5230PC\u6216\u8005\u670d\u52a1\u5668\u7684PCIe\u63d2\u69fd\uff0c\u5b8c\u7f8e\u8fd0\u884cPiKVM\u9879\u76ee\u3002\u4e3b\u8981\u529f\u80fd\u6709\uff1aHDMI\u89c6\u9891\u91c7\u96c6\uff0c\u952e\u76d8\u9f20\u6807\u63a7\u5236\uff0cATX\u5f00\u5173\u673a\u63a7\u5236\uff0cPoE\u4f9b\u7535\uff0cOLED\u5c4f\u5e55\u663e\u793a\uff0c \u4e32\u53e3\u7ec8\u7aef\u8c03\u8bd5\u548cRTC\u65f6\u949f\u529f\u80fd\u3002\u6b64PCIe\u5361\u914d\u6709\u5168\u9ad8\u548c\u534a\u9ad8\u7684\u6321\u677f\u3002 BLIKVM PCIe\u7248\u672c\u652f\u6301blikvm\u548cpikvm\u7684\u7cfb\u7edf\u955c\u50cf\u3002 \u5b89\u88c5\u8981\u6c42 \u4f60\u9700\u8981\u4e0b\u9762\u7684\u8bbe\u5907 \u6811\u8393\u6d3eCM4(\u5982\u679c\u4f60\u53ea\u8ba2\u8d2d\u4e86PCIe\u5361). PoE\u4f9b\u7535\u8bbe\u5907\u62165V/3A USB\u4f9b\u7535\u8bbe\u5907. CR1220 \u7ebd\u6263\u7535\u6c60. \u529f\u80fd \u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@60Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE \u4f9b\u7535 \u652f\u6301\u4e32\u53e3\u7ec8\u7aef \u652f\u6301 WiFi \uff08\u53ef\u9009\uff09 OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) PWM\u98ce\u6247 \u5feb\u901f\u5b89\u88c5\u8bf4\u660e 1. \u5982\u679c\u4f60\u8d2d\u4e70\u7684\u662f\u9700\u8981\u81ea\u5df1\u7ec4\u88c5\u7684\u7248\u672c\uff0c\u70e7\u5f55\u7cfb\u7edf\u955c\u50cf\u53c2\u8003\u8bf7\u70b9\u51fb\u6b64\u5904 2.\u7ec4\u88c5 BLIKVM \u53c2\u8003\u7684 \u8bf4\u660e\u6587\u6863 Geerling\u7684\u6d4b\u8bd5\u89c6\u9891 Craft Computing: Never Pay For IPMI Again - BliKVM Review \u4ea7\u54c1\u7279\u6027 \u786c\u4ef6\u63a5\u53e3\u6e05\u5355 1 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 2 USB-PC \u7aef\u53e3 1 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 2 USB-PC \u7aef\u53e3 3 \u4f9b\u7535\u53e3 5V 3A 4 RJ45 100M \u7f51\u53e3 & PoE 5 ATX\u63a7\u5236\u7aef\u53e3 6 OLED \u663e\u793a\u5c4f\u63a5\u53e3 7 PWM \u98ce\u6247 8 BOOT 9 RTC\u65f6\u949f 10 \u4e32\u884c\u7ec8\u7aef\u7aef\u53e3 11 USB-PC\u7aef\u53e3 HDMI IN \u4f7f\u7528\u4e1c\u829d\u7684TC358743\u4f5c\u4e3aHDMI\u7684\u6865\u63a5\u82af\u7247\uff0c\u540c\u65f6\u652f\u6301\u89c6\u9891\u548c\u97f3\u9891\u91c7\u96c6\uff0c\u652f\u6301\u89c6\u9891\u8f93\u5165\u6700\u9ad8\u5206\u8fa8\u7387\u4e3a1080P60Hz\u3002 USB-PC BLIKVM PCIe\u5361\u63d0\u4f9b\u4e24\u4e2ausb\u63a5\u53e3\uff0c\u4e00\u4e2a\u662fPC-IN\uff08type c\u63a5\u53e3\uff09\uff0c\u53e6\u4e00\u4e2a\u662fUSB-PC2\uff08\u6392\u9488\u63a5\u53e3\uff09\u3002\u8fd9\u4e24\u4e2a\u63a5\u53e3\u7684\u4f5c\u7528\u90fd\u662f\u4e3a\u4e86\u8fde\u63a5\u88ab\u63a7\u7535\u8111\u7684usb\uff0c\u7528\u4e8e\u63a7\u5236\u9f20\u6807\u548c\u952e\u76d8\u3002\u540c\u65f6\u4e24\u4e2a\u63a5\u53e3\u53ea\u80fd\u4f7f\u7528\u4e00\u4e2a\uff0c\u8bbe\u8ba1\u4e24\u4e2a\u63a5\u53e3\u7684\u76ee\u7684\u662f\uff0c\u5f53\u7528\u6237pc\u4e3b\u673a\u5185\u6709\u6392\u9488\u7684usb\u63a5\u53e3\u65f6\uff0c\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528usb-pc2\uff0c\u8fd9\u6837\u63a5\u7ebf\u4f1a\u66f4\u52a0\u7b80\u6d01\u3002 POWER-IN \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u6539\u63a5\u53e3\u4e0d\u9700\u8981\u88ab\u4f7f\u7528\u3002\u5f53\u4e0d\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u8fde\u63a5\u8be5\u63a5\u53e3\u7684\u7535\u6e90\u9002\u914d\u5668\uff0c\u63a8\u8350\u4e3a5V/3A\u3002 \u4ee5\u592a\u7f51\u53e3-PoE Gigabit Ethernet port \u6807\u51c6: IEEE 802.3af PoE \u8f93\u5165\u7535\u538b: 37-57 V DC \u8f93\u51fa\u7535\u538b: 5 V DC/2.4 A ATX\u63a5\u53e3 \u6539\u63a5\u53e3\u901a\u8fc7\u675c\u90a6\u7ebf\u94fe\u63a5\u88ab\u63a7\u8ba1\u7b97\u673a\u4e3b\u677f\u7684\u7535\u6e90\u63a7\u5236\u63a5\u53e3\u3002ATX\u529f\u80fd\u53ef\u4ee5\u5f00\u542f\u6216\u8005\u91cd\u542f\u88ab\u63a7\u8ba1\u7b97\u673a\u3002 PCIe\u677f\u5b50\u4e0a\u7684BTN\u4e1d\u5370\u4e3abutton\u7684\u7f29\u5199\u3002 \u6839\u636e\u7535\u8111\u4e3b\u677f\u8bf4\u660e\uff0c\u9996\u5148\u627e\u5230\u4e3b\u677f\u4e0aATX\u529f\u80fd\u76f8\u5173\u5f15\u811a\u4f4d\u7f6e\uff0c\u62d4\u4e0b\u4e3b\u677f\u5df2\u7ecf\u63a5\u597d\u7684ATX\u7ebf\uff0c\u62d4\u4e0b\u540e\u7535\u8111\u7684\u7535\u6e90\u6309\u94ae\u5c06\u5931\u53bb\u4f5c\u7528\u3002PCIe\u4e3b\u677f\u5171\u6709\u4e24\u63928PIN\u5f15\u811a\uff0c\u4e24\u6392\u5f15\u811a\u529f\u80fd\u5b8c\u5168\u76f8\u540c\u4f7f\u7528\u65f6\u65e0\u9700\u533a\u5206\u3002\u5176\u4e2d\u4e00\u6392\u5f15\u811a\u7528\u4e8eKVM\u63a7\u5236ATX\u76f8\u5173\u529f\u80fd\uff0c\u53e6\u4e00\u6392\u5f15\u811a\u63a5\u4e3b\u677f\u4e0a\u62d4\u4e0b\u6765\u7684ATX\u675c\u90a6\u5934\uff0c\u4fdd\u6301\u539f\u6709\u673a\u7bb1\u7535\u6e90\u6309\u94ae\u529f\u80fd\u3002\u6839\u636e\u4e3b\u677f\u548cPCIe\u4e0a\u7684\u5177\u4f53\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u6bcf\u6839\u7ebf\u7684\u8fde\u63a5\uff0c\u8fde\u63a5\u5173\u7cfb\u53ef\u4ee5\u53c2\u8003\u4e0b\u56fe\uff1a OLED\u663e\u793a\u5c4f \u663e\u793a\u5c4f\u5206\u8fa8\u7387\u4e3a128x64\uff0c\u4e3b\u82af\u7247\u4e3aSSD1306\u3002\u901a\u8fc7\u6539\u5c4f\u5e55\u53ef\u4ee5\u5c55\u793aBLIKVM\u7684CPU\u7684\u6e29\u5ea6\u3001IP\u5730\u5740\u3001\u542f\u52a8\u65f6\u95f4\u7b49\u4fe1\u606f\u3002 \u98ce\u6247 \u98ce\u6247\u9ed8\u8ba4\u8bbe\u7f6e\u5de5\u4f5c\u6e29\u5ea6\u4e3a60\u6444\u6c0f\u5ea6\uff0c\u4e0e\u6811\u8393\u6d3eCM4\u7684\u901a\u8fc7GPIO12\u94fe\u63a5\u3002 BOOT Fit jumper to disable eMMC Boot \u901a\u8fc7\u8be5\u77ed\u63a5\u53e3\u53ef\u4ee5\u4f7f\u7528PCIe\u5361\u5bf9eMMC\u7248\u672c\u7684CM4\u8fdb\u884c\u955c\u50cf\u70e7\u5f55\u3002 \u5b9e\u65f6\u65f6\u949f (RTC) \u65f6\u949f\u82af\u7247\u4e3aPCF8563\uff0c\u4e0e\u6811\u8393\u6d3eCM4\u7684\u901a\u4fe1\u65b9\u5f0f\u4e3aI2C\u3002RTC\u5de5\u4f5c\u9700\u8981\u518d\u5b89\u88c5CR1220\u7535\u6c60\u540e\u3002 \u4e32\u53e3 \u53ef\u4ee5\u901a\u8fc7\u6539\u4e32\u53e3\u767b\u9646\u8bbe\u5907\u8fdb\u884c\u8c03\u8bd5\uff0c\u4e00\u822c\u5728\u5728\u7f51\u7edc\u94fe\u63a5\u6545\u969c\u7b49\u60c5\u51b5\u4e0b\u4f7f\u7528\u3002 \u6811\u8393\u6d3eCM4\u7684\u4e32\u53e3. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. \u5c06USB\u8f6cTTL\u6a21\u5757\u7684\u675c\u90a6\u5934\u8fde\u63a5\u5230PCIe\u7684 GTR \u53e3\uff0cUSB\u8f6cttl\u6a21\u5757\u4e0e GTR \u63a5\u7ebf\u5173\u7cfb\u4e3a\uff08\u9ed1\u8272\u7ebf-G, \u767d\u8272\u7ebf-T, \u7eff\u8272\u7ebf-R\uff09;\u5177\u4f53\u65b9\u6cd5\u53ef\u53c2\u8003 \u6b64\u6587\u6863 \u914d\u4ef6 HDMI EDID\u6a21\u62df\u5668 \u5982\u679c\u88ab\u63a7\u8ba1\u7b97\u673a\u4e0d\u80fd\u6b63\u786e\u7684\u8f93\u51faHDMI\u56fe\u50cf\uff0c\u53ef\u4ee5\u4f7f\u7528\u6b64\u8bbe\u5907\u8fdb\u884c\u6d4b\u8bd5\u3002\u5b89\u88c5\u5728\u88ab\u63a7\u8bbe\u5907\u7684HDMI\u8f93\u51fa\u63a5\u53e3\u4e0a\uff0c\u7136\u540e\u518d\u901a\u8fc7HDMI\u7ebf\u8fde\u63a5\u5230BLIKVM\u3002 VGA\u8f6cHDMI\u6a21\u5757 \u5f53\u88ab\u63a7\u8ba1\u7b97\u673a\u4e0d\u662fHDMI\u8f93\u51fa\u63a5\u53e3\uff0c\u800c\u662fVGA\u8f93\u51fa\u63a5\u53e3\uff0c\u8bf7\u4f7f\u7528\u8be5\u6a21\u5757\u5b8c\u6210VGA\u8f6cHDMI\u4fe1\u53f7\u8f6c\u6362\u3002 USB\u8f6cTTL\u6a21\u5757 \u901a\u8fc7\u6539\u6a21\u5757\uff0c\u53ef\u4ee5\u8fde\u63a5BLIKVM PCIe\u5361\u7684\u4e32\u53e3\uff0c\u7136\u540e\u4f7f\u7528\u4e32\u53e3\u8fdb\u5165\u8bbe\u5907\u8fdb\u884c\u8c03\u8bd5\u3002 \u98ce\u6247 Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card. \u4f7f\u7528\u98ce\u6247\u5bf9\u6811\u8393\u6d3eCM4\u8fdb\u884c\u964d\u6e29\uff0c\u4f46\u5b89\u88c5\u98ce\u6247\u540e\u4f1a\u4f7fBLIKVM PCIe\u5361\u7684\u539a\u5ea6\u539a\u4e8e\u6807\u51c6\u7684PCIe\u5361\u539a\u5ea6\u3002 \u5c3a\u5bf8 \u6d4b\u8bd5\u89c6\u9891 BLIKVM PCIe\u7248\u672c\u5b9e\u6d4b\u89c6\u9891\uff0c\u8f6f\u4ef6\u4f7f\u7528PiKVM \u53d1\u8d27\u6e05\u5355 BLIKVM only PCIe\u5361\u7248\u672c 1 BLIKVM PCIe\u5361 1 \u98ce\u6247 1 OLED\u663e\u793a\u5c4f 1 USB\u8f6cTTL\u6a21\u5757 1 HDMI EDID\u6a21\u62df\u5668 1 VGA\u8f6cHDMI\u6a21\u5757 1 32G Micro SD card 1 HDMI\u7ebf 0.5m 1 HDMI \u76f4\u901a\u5934 1 \u5343\u5146\u7f51\u7ebf 1m 1 USB-A\u8f6cUSB-C\u7ebf 1m 2 USB\u675c\u90a6\u7ebf 0.4m 1 WiFi\u5929\u7ebf 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u91d1\u5c5e\u6563\u70ed\u7247 1 \u5341\u5b57\u5957\u7b52 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 BLIKVM PCIe \u5230\u624b\u5373\u7528\u7248\u672c 1 BLIKVM PCIe\u5361 1 CM4 102000 1 \u98ce\u6247 1 OLED\u663e\u793a\u5c4f 1 USB\u8f6cTTL\u6a21\u5757 1 HDMI EDID\u6a21\u62df\u5668 1 VGA\u8f6cHDMI\u6a21\u5757 1 32G Micro SD card 1 HDMI\u7ebf 0.5m 1 HDMI \u76f4\u901a\u5934 1 \u5343\u5146\u7f51\u7ebf 1m 1 USB-A\u8f6cUSB-C\u7ebf 1m 2 USB\u675c\u90a6\u7ebf 0.4m 1 WiFi\u5929\u7ebf 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u91d1\u5c5e\u6563\u70ed\u7247 1 \u5341\u5b57\u5957\u7b52 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 \u5907\u6ce8\uff1a\u7531\u4e8e\u6811\u8393\u6d3eCM4\u4e00\u76f4\u7d27\u7f3a\uff0c\u5230\u624b\u5373\u7528\u7248\u672c\u4e2dCM4\u7248\u672c\u53ef\u80fd\u4f1a\u66f4\u6362\u4e3aeMMC\u7248\u672c\uff0c\u6b64\u4e2d\u60c5\u51b5\u4e0b\u5c06\u4e0d\u5e26SD\u5361\u3002 \u8d2d\u4e70\u94fe\u63a5 v2\u6dd8\u5b9d\u5730\u5740 3D\u5916\u58f3 \u4e00\u4e2a\u7b80\u5355\u7684PCIe\u5916\u58f3 Download file","title":"BliKVM v2 PCIe\u5bfc\u89c8"},{"location":"BLIKVM-PCIE-guide-zh/#blikvm-pcie","text":"","title":"BLIKVM PCIe"},{"location":"BLIKVM-PCIE-guide-zh/#_1","text":"BLIKVM PCIe\u662f\u4e00\u6b3e\u57fa\u4e8e\u6811\u8393\u6d3eCM4\u7684IPKVM\u6269\u5c55\u5361\uff0c\u53ef\u4ee5\u5b89\u88c5\u5230PC\u6216\u8005\u670d\u52a1\u5668\u7684PCIe\u63d2\u69fd\uff0c\u5b8c\u7f8e\u8fd0\u884cPiKVM\u9879\u76ee\u3002\u4e3b\u8981\u529f\u80fd\u6709\uff1aHDMI\u89c6\u9891\u91c7\u96c6\uff0c\u952e\u76d8\u9f20\u6807\u63a7\u5236\uff0cATX\u5f00\u5173\u673a\u63a7\u5236\uff0cPoE\u4f9b\u7535\uff0cOLED\u5c4f\u5e55\u663e\u793a\uff0c \u4e32\u53e3\u7ec8\u7aef\u8c03\u8bd5\u548cRTC\u65f6\u949f\u529f\u80fd\u3002\u6b64PCIe\u5361\u914d\u6709\u5168\u9ad8\u548c\u534a\u9ad8\u7684\u6321\u677f\u3002 BLIKVM PCIe\u7248\u672c\u652f\u6301blikvm\u548cpikvm\u7684\u7cfb\u7edf\u955c\u50cf\u3002","title":"\u4ecb\u7ecd"},{"location":"BLIKVM-PCIE-guide-zh/#_2","text":"\u4f60\u9700\u8981\u4e0b\u9762\u7684\u8bbe\u5907 \u6811\u8393\u6d3eCM4(\u5982\u679c\u4f60\u53ea\u8ba2\u8d2d\u4e86PCIe\u5361). PoE\u4f9b\u7535\u8bbe\u5907\u62165V/3A USB\u4f9b\u7535\u8bbe\u5907. CR1220 \u7ebd\u6263\u7535\u6c60.","title":"\u5b89\u88c5\u8981\u6c42"},{"location":"BLIKVM-PCIE-guide-zh/#_3","text":"\u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63011080P@60Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE \u4f9b\u7535 \u652f\u6301\u4e32\u53e3\u7ec8\u7aef \u652f\u6301 WiFi \uff08\u53ef\u9009\uff09 OLED \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) PWM\u98ce\u6247","title":"\u529f\u80fd"},{"location":"BLIKVM-PCIE-guide-zh/#_4","text":"1. \u5982\u679c\u4f60\u8d2d\u4e70\u7684\u662f\u9700\u8981\u81ea\u5df1\u7ec4\u88c5\u7684\u7248\u672c\uff0c\u70e7\u5f55\u7cfb\u7edf\u955c\u50cf\u53c2\u8003\u8bf7\u70b9\u51fb\u6b64\u5904 2.\u7ec4\u88c5 BLIKVM \u53c2\u8003\u7684 \u8bf4\u660e\u6587\u6863 Geerling\u7684\u6d4b\u8bd5\u89c6\u9891 Craft Computing: Never Pay For IPMI Again - BliKVM Review","title":"\u5feb\u901f\u5b89\u88c5\u8bf4\u660e"},{"location":"BLIKVM-PCIE-guide-zh/#_5","text":"\u786c\u4ef6\u63a5\u53e3\u6e05\u5355 1 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 2 USB-PC \u7aef\u53e3 1 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 2 USB-PC \u7aef\u53e3 3 \u4f9b\u7535\u53e3 5V 3A 4 RJ45 100M \u7f51\u53e3 & PoE 5 ATX\u63a7\u5236\u7aef\u53e3 6 OLED \u663e\u793a\u5c4f\u63a5\u53e3 7 PWM \u98ce\u6247 8 BOOT 9 RTC\u65f6\u949f 10 \u4e32\u884c\u7ec8\u7aef\u7aef\u53e3 11 USB-PC\u7aef\u53e3 HDMI IN \u4f7f\u7528\u4e1c\u829d\u7684TC358743\u4f5c\u4e3aHDMI\u7684\u6865\u63a5\u82af\u7247\uff0c\u540c\u65f6\u652f\u6301\u89c6\u9891\u548c\u97f3\u9891\u91c7\u96c6\uff0c\u652f\u6301\u89c6\u9891\u8f93\u5165\u6700\u9ad8\u5206\u8fa8\u7387\u4e3a1080P60Hz\u3002 USB-PC BLIKVM PCIe\u5361\u63d0\u4f9b\u4e24\u4e2ausb\u63a5\u53e3\uff0c\u4e00\u4e2a\u662fPC-IN\uff08type c\u63a5\u53e3\uff09\uff0c\u53e6\u4e00\u4e2a\u662fUSB-PC2\uff08\u6392\u9488\u63a5\u53e3\uff09\u3002\u8fd9\u4e24\u4e2a\u63a5\u53e3\u7684\u4f5c\u7528\u90fd\u662f\u4e3a\u4e86\u8fde\u63a5\u88ab\u63a7\u7535\u8111\u7684usb\uff0c\u7528\u4e8e\u63a7\u5236\u9f20\u6807\u548c\u952e\u76d8\u3002\u540c\u65f6\u4e24\u4e2a\u63a5\u53e3\u53ea\u80fd\u4f7f\u7528\u4e00\u4e2a\uff0c\u8bbe\u8ba1\u4e24\u4e2a\u63a5\u53e3\u7684\u76ee\u7684\u662f\uff0c\u5f53\u7528\u6237pc\u4e3b\u673a\u5185\u6709\u6392\u9488\u7684usb\u63a5\u53e3\u65f6\uff0c\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528usb-pc2\uff0c\u8fd9\u6837\u63a5\u7ebf\u4f1a\u66f4\u52a0\u7b80\u6d01\u3002 POWER-IN \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u6539\u63a5\u53e3\u4e0d\u9700\u8981\u88ab\u4f7f\u7528\u3002\u5f53\u4e0d\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u8fde\u63a5\u8be5\u63a5\u53e3\u7684\u7535\u6e90\u9002\u914d\u5668\uff0c\u63a8\u8350\u4e3a5V/3A\u3002 \u4ee5\u592a\u7f51\u53e3-PoE Gigabit Ethernet port \u6807\u51c6: IEEE 802.3af PoE \u8f93\u5165\u7535\u538b: 37-57 V DC \u8f93\u51fa\u7535\u538b: 5 V DC/2.4 A ATX\u63a5\u53e3 \u6539\u63a5\u53e3\u901a\u8fc7\u675c\u90a6\u7ebf\u94fe\u63a5\u88ab\u63a7\u8ba1\u7b97\u673a\u4e3b\u677f\u7684\u7535\u6e90\u63a7\u5236\u63a5\u53e3\u3002ATX\u529f\u80fd\u53ef\u4ee5\u5f00\u542f\u6216\u8005\u91cd\u542f\u88ab\u63a7\u8ba1\u7b97\u673a\u3002 PCIe\u677f\u5b50\u4e0a\u7684BTN\u4e1d\u5370\u4e3abutton\u7684\u7f29\u5199\u3002 \u6839\u636e\u7535\u8111\u4e3b\u677f\u8bf4\u660e\uff0c\u9996\u5148\u627e\u5230\u4e3b\u677f\u4e0aATX\u529f\u80fd\u76f8\u5173\u5f15\u811a\u4f4d\u7f6e\uff0c\u62d4\u4e0b\u4e3b\u677f\u5df2\u7ecf\u63a5\u597d\u7684ATX\u7ebf\uff0c\u62d4\u4e0b\u540e\u7535\u8111\u7684\u7535\u6e90\u6309\u94ae\u5c06\u5931\u53bb\u4f5c\u7528\u3002PCIe\u4e3b\u677f\u5171\u6709\u4e24\u63928PIN\u5f15\u811a\uff0c\u4e24\u6392\u5f15\u811a\u529f\u80fd\u5b8c\u5168\u76f8\u540c\u4f7f\u7528\u65f6\u65e0\u9700\u533a\u5206\u3002\u5176\u4e2d\u4e00\u6392\u5f15\u811a\u7528\u4e8eKVM\u63a7\u5236ATX\u76f8\u5173\u529f\u80fd\uff0c\u53e6\u4e00\u6392\u5f15\u811a\u63a5\u4e3b\u677f\u4e0a\u62d4\u4e0b\u6765\u7684ATX\u675c\u90a6\u5934\uff0c\u4fdd\u6301\u539f\u6709\u673a\u7bb1\u7535\u6e90\u6309\u94ae\u529f\u80fd\u3002\u6839\u636e\u4e3b\u677f\u548cPCIe\u4e0a\u7684\u5177\u4f53\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u6bcf\u6839\u7ebf\u7684\u8fde\u63a5\uff0c\u8fde\u63a5\u5173\u7cfb\u53ef\u4ee5\u53c2\u8003\u4e0b\u56fe\uff1a OLED\u663e\u793a\u5c4f \u663e\u793a\u5c4f\u5206\u8fa8\u7387\u4e3a128x64\uff0c\u4e3b\u82af\u7247\u4e3aSSD1306\u3002\u901a\u8fc7\u6539\u5c4f\u5e55\u53ef\u4ee5\u5c55\u793aBLIKVM\u7684CPU\u7684\u6e29\u5ea6\u3001IP\u5730\u5740\u3001\u542f\u52a8\u65f6\u95f4\u7b49\u4fe1\u606f\u3002 \u98ce\u6247 \u98ce\u6247\u9ed8\u8ba4\u8bbe\u7f6e\u5de5\u4f5c\u6e29\u5ea6\u4e3a60\u6444\u6c0f\u5ea6\uff0c\u4e0e\u6811\u8393\u6d3eCM4\u7684\u901a\u8fc7GPIO12\u94fe\u63a5\u3002 BOOT Fit jumper to disable eMMC Boot \u901a\u8fc7\u8be5\u77ed\u63a5\u53e3\u53ef\u4ee5\u4f7f\u7528PCIe\u5361\u5bf9eMMC\u7248\u672c\u7684CM4\u8fdb\u884c\u955c\u50cf\u70e7\u5f55\u3002 \u5b9e\u65f6\u65f6\u949f (RTC) \u65f6\u949f\u82af\u7247\u4e3aPCF8563\uff0c\u4e0e\u6811\u8393\u6d3eCM4\u7684\u901a\u4fe1\u65b9\u5f0f\u4e3aI2C\u3002RTC\u5de5\u4f5c\u9700\u8981\u518d\u5b89\u88c5CR1220\u7535\u6c60\u540e\u3002 \u4e32\u53e3 \u53ef\u4ee5\u901a\u8fc7\u6539\u4e32\u53e3\u767b\u9646\u8bbe\u5907\u8fdb\u884c\u8c03\u8bd5\uff0c\u4e00\u822c\u5728\u5728\u7f51\u7edc\u94fe\u63a5\u6545\u969c\u7b49\u60c5\u51b5\u4e0b\u4f7f\u7528\u3002 \u6811\u8393\u6d3eCM4\u7684\u4e32\u53e3. G for GND, T(GPIO 14) for TXD, R(GPIO 15) for RXD. \u5c06USB\u8f6cTTL\u6a21\u5757\u7684\u675c\u90a6\u5934\u8fde\u63a5\u5230PCIe\u7684 GTR \u53e3\uff0cUSB\u8f6cttl\u6a21\u5757\u4e0e GTR \u63a5\u7ebf\u5173\u7cfb\u4e3a\uff08\u9ed1\u8272\u7ebf-G, \u767d\u8272\u7ebf-T, \u7eff\u8272\u7ebf-R\uff09;\u5177\u4f53\u65b9\u6cd5\u53ef\u53c2\u8003 \u6b64\u6587\u6863","title":"\u4ea7\u54c1\u7279\u6027"},{"location":"BLIKVM-PCIE-guide-zh/#_6","text":"HDMI EDID\u6a21\u62df\u5668 \u5982\u679c\u88ab\u63a7\u8ba1\u7b97\u673a\u4e0d\u80fd\u6b63\u786e\u7684\u8f93\u51faHDMI\u56fe\u50cf\uff0c\u53ef\u4ee5\u4f7f\u7528\u6b64\u8bbe\u5907\u8fdb\u884c\u6d4b\u8bd5\u3002\u5b89\u88c5\u5728\u88ab\u63a7\u8bbe\u5907\u7684HDMI\u8f93\u51fa\u63a5\u53e3\u4e0a\uff0c\u7136\u540e\u518d\u901a\u8fc7HDMI\u7ebf\u8fde\u63a5\u5230BLIKVM\u3002 VGA\u8f6cHDMI\u6a21\u5757 \u5f53\u88ab\u63a7\u8ba1\u7b97\u673a\u4e0d\u662fHDMI\u8f93\u51fa\u63a5\u53e3\uff0c\u800c\u662fVGA\u8f93\u51fa\u63a5\u53e3\uff0c\u8bf7\u4f7f\u7528\u8be5\u6a21\u5757\u5b8c\u6210VGA\u8f6cHDMI\u4fe1\u53f7\u8f6c\u6362\u3002 USB\u8f6cTTL\u6a21\u5757 \u901a\u8fc7\u6539\u6a21\u5757\uff0c\u53ef\u4ee5\u8fde\u63a5BLIKVM PCIe\u5361\u7684\u4e32\u53e3\uff0c\u7136\u540e\u4f7f\u7528\u4e32\u53e3\u8fdb\u5165\u8bbe\u5907\u8fdb\u884c\u8c03\u8bd5\u3002 \u98ce\u6247 Use a cooling fan to cool the Raspberry Pi CM4, but installing a fan will make the product thicker than a standard PCIe add-in card. \u4f7f\u7528\u98ce\u6247\u5bf9\u6811\u8393\u6d3eCM4\u8fdb\u884c\u964d\u6e29\uff0c\u4f46\u5b89\u88c5\u98ce\u6247\u540e\u4f1a\u4f7fBLIKVM PCIe\u5361\u7684\u539a\u5ea6\u539a\u4e8e\u6807\u51c6\u7684PCIe\u5361\u539a\u5ea6\u3002","title":"\u914d\u4ef6"},{"location":"BLIKVM-PCIE-guide-zh/#_7","text":"","title":"\u5c3a\u5bf8"},{"location":"BLIKVM-PCIE-guide-zh/#_8","text":"BLIKVM PCIe\u7248\u672c\u5b9e\u6d4b\u89c6\u9891\uff0c\u8f6f\u4ef6\u4f7f\u7528PiKVM","title":"\u6d4b\u8bd5\u89c6\u9891"},{"location":"BLIKVM-PCIE-guide-zh/#_9","text":"BLIKVM only PCIe\u5361\u7248\u672c 1 BLIKVM PCIe\u5361 1 \u98ce\u6247 1 OLED\u663e\u793a\u5c4f 1 USB\u8f6cTTL\u6a21\u5757 1 HDMI EDID\u6a21\u62df\u5668 1 VGA\u8f6cHDMI\u6a21\u5757 1 32G Micro SD card 1 HDMI\u7ebf 0.5m 1 HDMI \u76f4\u901a\u5934 1 \u5343\u5146\u7f51\u7ebf 1m 1 USB-A\u8f6cUSB-C\u7ebf 1m 2 USB\u675c\u90a6\u7ebf 0.4m 1 WiFi\u5929\u7ebf 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u91d1\u5c5e\u6563\u70ed\u7247 1 \u5341\u5b57\u5957\u7b52 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 BLIKVM PCIe \u5230\u624b\u5373\u7528\u7248\u672c 1 BLIKVM PCIe\u5361 1 CM4 102000 1 \u98ce\u6247 1 OLED\u663e\u793a\u5c4f 1 USB\u8f6cTTL\u6a21\u5757 1 HDMI EDID\u6a21\u62df\u5668 1 VGA\u8f6cHDMI\u6a21\u5757 1 32G Micro SD card 1 HDMI\u7ebf 0.5m 1 HDMI \u76f4\u901a\u5934 1 \u5343\u5146\u7f51\u7ebf 1m 1 USB-A\u8f6cUSB-C\u7ebf 1m 2 USB\u675c\u90a6\u7ebf 0.4m 1 WiFi\u5929\u7ebf 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u6bcd 40cm 1 \u675c\u90a6\u7ebf 8pin \u6bcd\u5bf9\u516c 40cm 1 \u91d1\u5c5e\u6563\u70ed\u7247 1 \u5341\u5b57\u5957\u7b52 1 \u5341\u5b57\u87ba\u4e1d\u5200 1 \u5907\u6ce8\uff1a\u7531\u4e8e\u6811\u8393\u6d3eCM4\u4e00\u76f4\u7d27\u7f3a\uff0c\u5230\u624b\u5373\u7528\u7248\u672c\u4e2dCM4\u7248\u672c\u53ef\u80fd\u4f1a\u66f4\u6362\u4e3aeMMC\u7248\u672c\uff0c\u6b64\u4e2d\u60c5\u51b5\u4e0b\u5c06\u4e0d\u5e26SD\u5361\u3002","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"BLIKVM-PCIE-guide-zh/#_10","text":"v2\u6dd8\u5b9d\u5730\u5740","title":"\u8d2d\u4e70\u94fe\u63a5"},{"location":"BLIKVM-PCIE-guide-zh/#3d","text":"\u4e00\u4e2a\u7b80\u5355\u7684PCIe\u5916\u58f3 Download file","title":"3D\u5916\u58f3"},{"location":"BLIKVM-PCIe-installation-zh/","text":"BLIKVM PCIe \u5b89\u88c5\u8bf4\u660e 1.\u62c6\u5f00\u5305\u88c5\uff0c\u62ff\u51fa\u8bbe\u5907 \u4ea7\u54c1\u6e05\u5355 2.\u5b89\u88c5\u4e3b\u4f53\u8bbe\u5907 \u5b89\u88c5CM4\u548c4\u4e2a\u516d\u89d2\u87ba\u67f1(\u6b64\u6587\u7ae0\u4f7f\u7528\u7684\u662fCM4 lite\u4f5c\u4e3a\u5217\u5b50\uff0c\u955c\u50cf\u5728\u51fa\u5382\u7684SD\u5361\u91cc\u5df2\u7ecf\u88ab\u9884\u88c5\u8f7d\uff0c\u7528\u6237\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528\u3002\u82e5\u4f60\u7684CM4\u662fEMMc\u7248\u672c\uff0c\u5219\u4f60\u9700\u8981\u81ea\u5df1\u70e7\u5f55\u955c\u50cf \uff0c\u65e0\u6cd5\u76f4\u63a5\u4f7f\u7528SD\u5361\u542f\u52a8)\u3002\u7136\u540e\u5c06\u5bfc\u70ed\u7247\u6495\u4e0b\u4fdd\u62a4\u819c\uff0c\u7c98\u8d34\u5728CM4\u9876\u90e8\u3002 \u5b89\u88c5\u91d1\u5c5e\u6563\u70ed\u7247\u3002 \u4e3b\u4f53\u8bbe\u5907\u5df2\u5b89\u88c5\u5b8c\u6210 3.\u8fde\u63a5USB\u63a5\u53e3\u548cATX\u63a5\u53e3 \u6b64\u6587\u4e2d\u7684\u4e3b\u677f\u4f7f\u7528\u7684\u662fAsus H520M-E\uff0c\u4e0d\u540c\u7684\u4e3b\u677f\u63a5\u53e3\u5b9a\u4e49\u4e0d\u4e00\u5b9a\u76f8\u540c\uff0c\u8bf7\u53c2\u8003\u60a8\u7684\u4e3b\u677f\u76f8\u5173\u624b\u518c\u3002 4.\u94fe\u63a5OLED\u663e\u793a\u5c4f \u60a8\u6536\u5230\u7684OLED\u662f\u672a\u5b89\u88c5\u652f\u67b6\u7684\uff0c\u8bf7\u53c2\u8003\u56fe\u7247\u8fdb\u884c\u5b89\u88c5\u3002\u53e6\u5916OLED\u652f\u67b6\u4e3a\u4e9a\u514b\u529b\u6750\u6599\uff0c\u9700\u8981\u6495\u53bb\u8868\u9762\u7684\u4fdd\u62a4\u819c\u540e\u4f7f\u7528\u3002 \u4e0a\u9762\u7684\u5c31\u662f\u5b89\u88c5\u6b65\u9aa4\uff0c\u672a\u6495\u819c\u7684\u6548\u679c\uff0c\u5b9e\u9645\u4f7f\u7528\u8bf7\u6495\u53bb\u4fdd\u62a4\u819c\uff0c\u6548\u679c\u5982\u4e0b\uff1a 5.\u8fde\u63a5HDMI\u7ebf \u5c06\u60a8\u7535\u8111\u7684HDMI\u8f93\u51fa\u53e3\u901a\u8fc7HDMI\u7ebf\u76f4\u63a5\u8fde\u63a5\u5230BLIKVM PCIe\u5361\u7684HDMI IN\u63a5\u53e3\u3002HDMI EDID\u6a21\u62df\u5668\u4e0d\u662f\u5fc5\u987b\u8981\u662f\u7528\u7684\uff0c\u5f53\u60a8\u7684\u8ba1\u7b97\u673a\u4e0d\u80fd\u6b63\u786e\u8f93\u51faHDMI\u753b\u9762\u65f6\uff0c\u53ef\u4ee5\u901a\u8fc7\u5c1d\u8bd5\u4f7f\u7528\u6b64\u6a21\u5757\u63a5\u5728\u4f60\u7684\u8ba1\u7b97\u673a\u7684HDMI\u63a5\u53e3\u4e0a\uff0c\u4ece\u800c\u8ba9\u60a8\u7684\u8ba1\u7b97\u673a\u53ef\u4ee5\u8f93\u51fa\u4e00\u4e2a\u6b63\u786e\u627dHDMI\u753b\u9762 6.\u8fde\u63a5\u7f51\u7ebf \u6807\u51c6: IEEE 802.3af PoE\u8f93\u5165\u7535\u538b:37v-57v. \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u4e0d\u9700\u8981\u4f7f\u7528PWR-IN\u7aef\u53e3\u518d\u4f9b\u7535 7.\u8fde\u63a5USB\u4f9b\u7535\u63a5\u53e3 \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6, \u901a\u8fc7\u4f7f\u7528PWR-IN\u7aef\u53e3\u8fdb\u884c\u4f9b\u7535\u7684USB\u7535\u6e90\u9002\u914d\u5668\u9700\u89815V/3A\u3002 8.\u6d4b\u8bd5 OLED\u663e\u793a\u5c4f\u73b0\u5b9e\u8bbe\u5907IP\u5730\u5740\u548c\u5176\u5b83\u4fe1\u606f \u4f7f\u7528\u8be5IP\u5730\u5740\u5728\u6d4f\u89c8\u5668\u4e0a\u76f4\u63a5\u8f93\u5165\uff0c\u5373\u53ef\u6253\u5f00web\u63a7\u5236\u754c\u9762\u3002\u5982\u679c\u89c6\u9891\u9f20\u6807\u952e\u76d8\u4ee5\u53ca\u5176\u5b83\u4f60\u5173\u5fc3\u7684\u529f\u80fd\u6d4b\u8bd5\u4e00\u5207\u6b63\u5728\uff0c\u5c31\u53ef\u4ee5\u5c06BLIKVM PCIe\u5361\u5b89\u88c5\u5230\u4f60\u7684\u673a\u7bb1\u4e2d\u3002 9.\u5b89\u88c5BLIKVM PCIe\u5361\u5230\u673a\u7bb1\u4e2d \u65ad\u5f00\u7535\u6e90\u548c\u8fde\u63a5\u7ebf\uff0c\u5148\u5c06PCIe\u5361\u5b89\u88c5\u5230\u4e3b\u677f\u4e0a\uff0c\u7136\u540e\u91cd\u65b0\u5c06\u7ebf\u7f06\u8fde\u63a5\u597d\u3002\u4e0d\u540c\u6279\u6b21\u6536\u5230\u7684ATX\u7ebf\u989c\u8272\u53ef\u80fd\u4e0d\u4e00\u6837\uff0c\u8bf7\u76f4\u63a5\u53c2\u8003\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u8fde\u63a5\u3002 \u5230\u8fd9\u91cc\u4f60\u5c31\u53ef\u4ee5\u4eab\u53d7BLIKVM PCIe\u5361\u6765\u7ba1\u7406\u4f60\u7684\u8ba1\u7b97\u673a\u5566! \u9644\u5f55 1.\u5b89\u88c5\u534a\u9ad8\u7684PCIe\u6321\u677f Note \u9644\u5f55 2.\u5b89\u88c5\u6563\u70ed\u98ce\u6247 \u901a\u5e38\u4f7f\u7528\u91d1\u5c5e\u6563\u70ed\u7247\u5df2\u7ecf\u8db3\u591f\uff0c\u5b89\u88c5\u6563\u70ed\u98ce\u6247\u4e0d\u662f\u5fc5\u987b\u7684 \u98ce\u6247\u88ab\u6811\u8393\u6d3e\u7684GPIO12\u53e3\u63a7\u5236 \u9644\u5f55 3.\u5b89\u88c5wifi\u5929\u7ebf Note","title":"v2 PCIe\u5b89\u88c5\u8bf4\u660e"},{"location":"BLIKVM-PCIe-installation-zh/#blikvm-pcie","text":"","title":"BLIKVM PCIe \u5b89\u88c5\u8bf4\u660e"},{"location":"BLIKVM-PCIe-installation-zh/#1","text":"\u4ea7\u54c1\u6e05\u5355","title":"1.\u62c6\u5f00\u5305\u88c5\uff0c\u62ff\u51fa\u8bbe\u5907"},{"location":"BLIKVM-PCIe-installation-zh/#2","text":"\u5b89\u88c5CM4\u548c4\u4e2a\u516d\u89d2\u87ba\u67f1(\u6b64\u6587\u7ae0\u4f7f\u7528\u7684\u662fCM4 lite\u4f5c\u4e3a\u5217\u5b50\uff0c\u955c\u50cf\u5728\u51fa\u5382\u7684SD\u5361\u91cc\u5df2\u7ecf\u88ab\u9884\u88c5\u8f7d\uff0c\u7528\u6237\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528\u3002\u82e5\u4f60\u7684CM4\u662fEMMc\u7248\u672c\uff0c\u5219\u4f60\u9700\u8981\u81ea\u5df1\u70e7\u5f55\u955c\u50cf \uff0c\u65e0\u6cd5\u76f4\u63a5\u4f7f\u7528SD\u5361\u542f\u52a8)\u3002\u7136\u540e\u5c06\u5bfc\u70ed\u7247\u6495\u4e0b\u4fdd\u62a4\u819c\uff0c\u7c98\u8d34\u5728CM4\u9876\u90e8\u3002 \u5b89\u88c5\u91d1\u5c5e\u6563\u70ed\u7247\u3002 \u4e3b\u4f53\u8bbe\u5907\u5df2\u5b89\u88c5\u5b8c\u6210","title":"2.\u5b89\u88c5\u4e3b\u4f53\u8bbe\u5907"},{"location":"BLIKVM-PCIe-installation-zh/#3usbatx","text":"\u6b64\u6587\u4e2d\u7684\u4e3b\u677f\u4f7f\u7528\u7684\u662fAsus H520M-E\uff0c\u4e0d\u540c\u7684\u4e3b\u677f\u63a5\u53e3\u5b9a\u4e49\u4e0d\u4e00\u5b9a\u76f8\u540c\uff0c\u8bf7\u53c2\u8003\u60a8\u7684\u4e3b\u677f\u76f8\u5173\u624b\u518c\u3002","title":"3.\u8fde\u63a5USB\u63a5\u53e3\u548cATX\u63a5\u53e3"},{"location":"BLIKVM-PCIe-installation-zh/#4oled","text":"\u60a8\u6536\u5230\u7684OLED\u662f\u672a\u5b89\u88c5\u652f\u67b6\u7684\uff0c\u8bf7\u53c2\u8003\u56fe\u7247\u8fdb\u884c\u5b89\u88c5\u3002\u53e6\u5916OLED\u652f\u67b6\u4e3a\u4e9a\u514b\u529b\u6750\u6599\uff0c\u9700\u8981\u6495\u53bb\u8868\u9762\u7684\u4fdd\u62a4\u819c\u540e\u4f7f\u7528\u3002 \u4e0a\u9762\u7684\u5c31\u662f\u5b89\u88c5\u6b65\u9aa4\uff0c\u672a\u6495\u819c\u7684\u6548\u679c\uff0c\u5b9e\u9645\u4f7f\u7528\u8bf7\u6495\u53bb\u4fdd\u62a4\u819c\uff0c\u6548\u679c\u5982\u4e0b\uff1a","title":"4.\u94fe\u63a5OLED\u663e\u793a\u5c4f"},{"location":"BLIKVM-PCIe-installation-zh/#5hdmi","text":"\u5c06\u60a8\u7535\u8111\u7684HDMI\u8f93\u51fa\u53e3\u901a\u8fc7HDMI\u7ebf\u76f4\u63a5\u8fde\u63a5\u5230BLIKVM PCIe\u5361\u7684HDMI IN\u63a5\u53e3\u3002HDMI EDID\u6a21\u62df\u5668\u4e0d\u662f\u5fc5\u987b\u8981\u662f\u7528\u7684\uff0c\u5f53\u60a8\u7684\u8ba1\u7b97\u673a\u4e0d\u80fd\u6b63\u786e\u8f93\u51faHDMI\u753b\u9762\u65f6\uff0c\u53ef\u4ee5\u901a\u8fc7\u5c1d\u8bd5\u4f7f\u7528\u6b64\u6a21\u5757\u63a5\u5728\u4f60\u7684\u8ba1\u7b97\u673a\u7684HDMI\u63a5\u53e3\u4e0a\uff0c\u4ece\u800c\u8ba9\u60a8\u7684\u8ba1\u7b97\u673a\u53ef\u4ee5\u8f93\u51fa\u4e00\u4e2a\u6b63\u786e\u627dHDMI\u753b\u9762","title":"5.\u8fde\u63a5HDMI\u7ebf"},{"location":"BLIKVM-PCIe-installation-zh/#6","text":"\u6807\u51c6: IEEE 802.3af PoE\u8f93\u5165\u7535\u538b:37v-57v. \u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6\uff0c\u4e0d\u9700\u8981\u4f7f\u7528PWR-IN\u7aef\u53e3\u518d\u4f9b\u7535","title":"6.\u8fde\u63a5\u7f51\u7ebf"},{"location":"BLIKVM-PCIe-installation-zh/#7usb","text":"\u5f53\u4f7f\u7528PoE\u4f9b\u7535\u65f6, \u901a\u8fc7\u4f7f\u7528PWR-IN\u7aef\u53e3\u8fdb\u884c\u4f9b\u7535\u7684USB\u7535\u6e90\u9002\u914d\u5668\u9700\u89815V/3A\u3002","title":"7.\u8fde\u63a5USB\u4f9b\u7535\u63a5\u53e3"},{"location":"BLIKVM-PCIe-installation-zh/#8","text":"OLED\u663e\u793a\u5c4f\u73b0\u5b9e\u8bbe\u5907IP\u5730\u5740\u548c\u5176\u5b83\u4fe1\u606f \u4f7f\u7528\u8be5IP\u5730\u5740\u5728\u6d4f\u89c8\u5668\u4e0a\u76f4\u63a5\u8f93\u5165\uff0c\u5373\u53ef\u6253\u5f00web\u63a7\u5236\u754c\u9762\u3002\u5982\u679c\u89c6\u9891\u9f20\u6807\u952e\u76d8\u4ee5\u53ca\u5176\u5b83\u4f60\u5173\u5fc3\u7684\u529f\u80fd\u6d4b\u8bd5\u4e00\u5207\u6b63\u5728\uff0c\u5c31\u53ef\u4ee5\u5c06BLIKVM PCIe\u5361\u5b89\u88c5\u5230\u4f60\u7684\u673a\u7bb1\u4e2d\u3002","title":"8.\u6d4b\u8bd5"},{"location":"BLIKVM-PCIe-installation-zh/#9blikvm-pcie","text":"\u65ad\u5f00\u7535\u6e90\u548c\u8fde\u63a5\u7ebf\uff0c\u5148\u5c06PCIe\u5361\u5b89\u88c5\u5230\u4e3b\u677f\u4e0a\uff0c\u7136\u540e\u91cd\u65b0\u5c06\u7ebf\u7f06\u8fde\u63a5\u597d\u3002\u4e0d\u540c\u6279\u6b21\u6536\u5230\u7684ATX\u7ebf\u989c\u8272\u53ef\u80fd\u4e0d\u4e00\u6837\uff0c\u8bf7\u76f4\u63a5\u53c2\u8003\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u8fde\u63a5\u3002 \u5230\u8fd9\u91cc\u4f60\u5c31\u53ef\u4ee5\u4eab\u53d7BLIKVM PCIe\u5361\u6765\u7ba1\u7406\u4f60\u7684\u8ba1\u7b97\u673a\u5566!","title":"9.\u5b89\u88c5BLIKVM PCIe\u5361\u5230\u673a\u7bb1\u4e2d"},{"location":"BLIKVM-PCIe-installation-zh/#1pcie","text":"Note","title":"\u9644\u5f55 1.\u5b89\u88c5\u534a\u9ad8\u7684PCIe\u6321\u677f"},{"location":"BLIKVM-PCIe-installation-zh/#2_1","text":"\u901a\u5e38\u4f7f\u7528\u91d1\u5c5e\u6563\u70ed\u7247\u5df2\u7ecf\u8db3\u591f\uff0c\u5b89\u88c5\u6563\u70ed\u98ce\u6247\u4e0d\u662f\u5fc5\u987b\u7684 \u98ce\u6247\u88ab\u6811\u8393\u6d3e\u7684GPIO12\u53e3\u63a7\u5236","title":"\u9644\u5f55 2.\u5b89\u88c5\u6563\u70ed\u98ce\u6247"},{"location":"BLIKVM-PCIe-installation-zh/#3wifi","text":"Note","title":"\u9644\u5f55 3.\u5b89\u88c5wifi\u5929\u7ebf"},{"location":"BliKVM-v4-guide/","text":"BliKVM v4 Allwinner BliKVM v4\u662f\u4e00\u6b3e\u751f\u4ea7\u5c31\u7eea\u3001\u5373\u63d2\u5373\u7528\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86 \u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406 \u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e \u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5 \u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1 \uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01 BliKVM V4 Datasheet Craft Computing: Goodbye IPMI - Blicube BliKVM V4 \u6d4b\u8bc4 Lawrence Systems: Blicube BliKVM V4: Is This the Best Linux IP KVM Yet? RainCat: BliKVM V4 Allwinnner\u5b89\u88c5PiKVM\u6559\u7a0b \u529f\u80fd\u7279\u70b9 \u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63014K@30Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) HDMI\u89c6\u9891\u73af\u51fa ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE & DC \u652f\u6301 WiFi \u4e32\u53e3 \u63a7\u5236\u53f0\u7aef\u53e3 1.33\u82f1\u5bf8 \u5f69\u8272 \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) HDMI\u652f\u6301\u7684\u5206\u8fa8\u7387\u7c7b\u578b \u5b89\u88c5\u8981\u6c42 \u9664v4\u5957\u4ef6\u5916\uff0c\u60a8\u8fd8\u9700\u81ea\u5907\u4ee5\u4e0b\u8bbe\u5907 \u7535\u6e90\u9002\u914d\u5668\uff085V 3A, USB-C\u7aef\u53e3\u621612V 2ADC\u7aef\u53e3\uff09,\u82e5\u4f60\u8ba1\u5212\u4f7f\u7528PoE\u4f9b\u7535\uff0c\u6216\u8005\u6240\u7684\u88ab\u63a7\u8ba1\u7b97\u673aUSB\u53e3\u6709\u5145\u8db3\u7684\u4f9b\u7535\u80fd\u529b\uff0c\u5219\u4e5f\u4e0d\u9700\u8981\u5355\u72ec\u7684\u7535\u6e90\u9002\u914d\u5668\uff1b HDMI \u7ebf\u7f06(\u81f3\u5c11\u4e00\u6839)\uff0c\u82e5\u60a8\u540c\u65f6\u9700\u8981\u4f7f\u7528HDMI\u73af\u51fa\u63a5\u53e3\uff0c\u5219\u9700\u89812\u6839\uff1b \u7f51\u7ebf\uff08\u7ed3\u5408\u60a8\u9700\u6c42\u81ea\u5907\uff09,\u4f7f\u7528ATX\u5f00\u5173\u673a\u529f\u80fd\u9700\u4e00\u6839\uff0c\u4f7f\u7528\u7f51\u7ebf\u4e0a\u7f51\u529f\u80fd\u9700\u4e00\u6839\uff1b USB-C\u8f6cUSB-A\u7ebf\u7f06\u4e00\u6839\uff08\u7528\u4e8e\u9f20\u6807\u548c\u952e\u76d8\u6570\u636e\u4f20\u8f93\uff09. \u7ec8\u7aef\u5347\u7ea7\u6ce8\u610f\uff01 \u5728\u5347\u7ea7\u524d\uff0c\u9700\u6267\u884c\u4e0b\u9762\u547d\u4ee4\uff0c\u5426\u5219apt-get update \u548c apt-get upgrade\u540e\u955c\u50cf\u4f1a\u65e0\u6cd5\u542f\u52a8 apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64 BliKVM v4 \u62c6\u7bb1\uff0c\u8fde\u63a5\uff0c\u4f7f\u7528\u53c2\u8003\u89c6\u9891 \u5b89\u88c5\u6b65\u9aa4 1. \u6253\u5f00v4\u5957\u4ef6\u5305\u88c5\uff0c\u6839\u636e\u4e0b\u9762\u6240\u793a\u7684\u8fde\u63a5\u793a\u610f\u56fe\uff0c\u5c06BliKVM\u548c\u88ab\u63a7\u8ba1\u7b97\u673a\u8fde\u63a5\u8d77\u6765\uff1b ATX\u8fde\u63a5 \u8bf7\u53c2\u8003 ATX\u8fde\u63a5\u6307\u5357 \u3002 2. \u5728\u6240\u6709\u8fde\u63a5\u7ebf\u8fde\u63a5\u597d\u540e,\u5bf9BliKVM\u8fdb\u884c\u4e0a\u7535\uff0c\u76f4\u5230\u663e\u793a\u5c4f\u51fa\u73b0\u753b\u9762\uff0c\u5373\u8bbe\u5907\u6b63\u5e38\u542f\u52a8\u3002 3. \u4ed4\u7ec6\u9605\u8bfb \u201c\u7b2c\u4e00\u6b65\u201d \u6307\u5357-\u5982\u4f55\u5728\u7f51\u7edc\u4e0a\u67e5\u627e\u8bbe\u5907\u3001\u5982\u4f55\u767b\u5f55\u3001\u66f4\u6539\u5bc6\u7801\u7b49\u7b49\u3002\u6309\u7167\u4e0a\u9762\u63cf\u8ff0\u7684\u6b65\u9aa4\u64cd\u4f5c\uff0c\u7136\u540e\u8fd4\u56de\u672c\u9875\u3002 4. \u5c1d\u8bd5\u4f7f\u7528 Web \u754c\u9762\u7ba1\u7406\u8ba1\u7b97\u673a\u7684 BliKVM\u3002 \u786e\u4fdd\u60a8\u53ef\u4ee5\u770b\u5230\u56fe\u50cf\u5e76\u4e14\u952e\u76d8\u548c\u9f20\u6807\u90fd\u6b63\u5e38\u5de5\u4f5c\u3002\u5982\u679c\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u8bf7\u67e5\u770b\u6211\u4eec\u7684 \u5e38\u89c1\u95ee\u9898 \uff08\u5b83\u975e\u5e38\u6709\u7528\uff09\u3002\u5982\u679c\u6ca1\u6709\u4efb\u4f55\u5e2e\u52a9\uff0c\u8bf7\u5728\u6211\u4eec\u7684 Discord\u804a\u5929\u5ba4 \u5bfb\u6c42\u652f\u6301\u3002 5. \u60a8\u53ef\u4ee5\u67e5\u770bwiki\u5176\u4ed6\u7684\u9875\u9762\uff0c\u63a2\u7d22BliKVM\u7684\u66f4\u591a\u529f\u80fd\uff0c\u795d\u60a8\u73a9\u7684\u5f00\u5fc3\uff01 \u89c6\u9891\u6a21\u5f0f v4\u6700\u9ad8\u652f\u63014K30Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u4f20\u8f93\u5206\u8fa8\u7387\u9ed8\u8ba4\u4e3a1920x1080\u3002 \u53d1\u8d27\u6e05\u5355 BLIKVM v4 Allwinner\u7248\u672c 1 BLIKVM v4 1 WiFi\u5929\u7ebf 1 ATX\u9002\u914d\u677f 1 ATX\u675c\u90a6\u7ebf\u7f06 8pin \u6bcd\u5bf9\u6bcd 60cm 1 ATX\u675c\u90a6\u7ebf\u7f06 8pin \u6bcd\u5bf9\u516c 60cm 1 1U\u5b89\u88c5\u6302\u8033 2 M2.5x5\u87ba\u4e1d 8 \u7845\u80f6\u9632\u649e\u7c92 1 \u901a\u8fc75V\u7aef\u53e3\u8bbf\u95ee\u4e32\u884c\u63a7\u5236\u53f0 5V\u7aef\u53e3\u53ef\u4ee5\u540c\u65f6\u7528\u4e8e\u4f9b\u7535\u548c\u4e32\u884c\u63a7\u5236\u53f0\u8bbf\u95ee\uff0c\u9ed8\u8ba4\u6ce2\u7279\u7387\u4e3a115200\u3002BliKVM v4\u5185\u90e8\u6709\u4e00\u4e2a\u57fa\u4e8eCH341\u7684USB\u5230UART\u8f6c\u6362\u5668\uff0c\u5b83\u8fde\u63a5\u5230 mCore-H616 SoC \u7684UART0\uff0c\u6240\u4ee5\u4f60\u53ef\u4ee5\u5c06PC\u7684USB\u7aef\u53e3\u8fde\u63a5\u52305V\u7aef\u53e3\uff0c\u65e0\u9700\u5916\u90e8UART\u548cUSB-C\u5230\u675c\u90a6\u9002\u914d\u5668\u3002 PC USB\u7aef\u53e3\u7535\u6d41\u8f93\u51fa \u5c1d\u8bd5\u4f7f\u75285V\u7aef\u53e3\u65f6\u8981\u5c0f\u5fc3\uff0c\u56e0\u4e3a\u5355\u72ec\u7684PC USB\u7aef\u53e3\u53ef\u80fd\u65e0\u6cd5\u63d0\u4f9b3A\uff085V\uff09\uff0c\u8fd9\u662f\u677f\u5361\u5de5\u4f5c\u7684\u8981\u6c42\u3002\u53ef\u4ee5\u540c\u65f6\u4f7f\u752812V 2A DC\u7aef\u53e3\u4f9b\u7535\u548c5V\u7aef\u53e3\u8fdb\u884c\u4e32\u884c\u901a\u4fe1\uff0c\u65e0\u9700 USB\u5206\u7ebf\u5668\u677f \u3002\u6216\u8005\u4f7f\u7528\u5206\u7ebf\u5668\u677f\u5206\u79bb\u51faVCC\u5f15\u811a\uff0c\u5e76\u4f7f\u7528\u5355\u72ec\u76845V 3A\u7535\u6e90\u4e3a5V\u7aef\u53e3\u7684VCC\u5f15\u811a\u4f9b\u7535\u3002\u540c\u6837\uff0c\u5f53BliKVM\u901a\u7535\u65f6\u4ece12V 2A DC\u7aef\u53e3\u65ad\u5f00\u7535\u7f06\u65f6\uff0c\u8981\u786e\u4fdd\u5148\u4ece5V\u7aef\u53e3\u65ad\u5f00\u7535\u7f06\uff08\u56e0\u4e3a\u572812V 2A\u7535\u6e90\u65ad\u5f00\u540e\uff0c\u9664\u975e\u4f7f\u7528\u4e86\u5206\u7ebf\u5668\uff0c\u5426\u52195V\u7aef\u53e3\u5c06\u6210\u4e3aBliKVM v4\u7684\u7535\u6e90\uff09\u3002 \u5f53\u4f60\u5c06USB\u7535\u7f06\u8fde\u63a5\u5230BliKVM v4\u76845V\u7aef\u53e3\u65f6\uff0c\u4f60\u5e94\u8be5\u5728\u4e3b\u673a\u5185\u6838\u65e5\u5fd7\u4e2d\u770b\u5230\u7c7b\u4f3c\u8fd9\u6837\u7684\u5185\u5bb9\uff08\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662f\u57fa\u4e8eLinux\u7684\u64cd\u4f5c\u7cfb\u7edf\uff09: usb 1-1.2: new full-speed USB device number 12 using xhci_hcd usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34 usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.2: Product: USB Serial ch341 1-1.2:1.0: ch341-uart converter detected usb 1-1.2: ch341-uart converter now attached to ttyUSB0 \u7136\u540e\uff0c\u53ef\u4ee5\u4f7f\u7528 GNU screen \u6216 TIO \u8bbf\u95ee\u6b64\u7aef\u53e3: tio /dev/ttyUSB0 mangopimcore login: blikvm # ... \u5982\u679c\u4f60\u9700\u8981\u68c0\u67e5\u901a\u8fc7UART0\u63a5\u6536\u4e86\u591a\u5c11\u6570\u636e\uff0c\u53ef\u4ee5\u901a\u8fc7\u67e5\u770b\u901a\u8fc7proc\u516c\u5f00\u7684\u8ba1\u6570\u5668\u6765\u5b9e\u73b0\uff08\u5f53\u4ece\u5916\u90e8\u4e3b\u673a\u53d1\u9001\u6570\u636e\u65f6\uff0c\u5982\u679c\u5185\u7f6e\u7684USB\u5230UART\u8f6c\u6362\u5668\u5de5\u4f5c\u6b63\u5e38\uff0crx\u8ba1\u6570\u5668\u5e94\u8be5\u4f1a\u589e\u52a0\uff09\uff1a root@mangopimcore:~# grep '0: uart' /proc/tty/driver/serial 0: uart:16550A mmio:0x05000000 irq:284 tx:20306 rx:40 pe:1 RTS|DTR \u8d2d\u4e70\u94fe\u63a5 v4\u6dd8\u5b9d\u5730\u5740","title":"BliKVM v4 Allwinner\u5bfc\u89c8"},{"location":"BliKVM-v4-guide/#blikvm-v4-allwinner","text":"BliKVM v4\u662f\u4e00\u6b3e\u751f\u4ea7\u5c31\u7eea\u3001\u5373\u63d2\u5373\u7528\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86 \u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406 \u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e \u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5 \u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1 \uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01 BliKVM V4 Datasheet Craft Computing: Goodbye IPMI - Blicube BliKVM V4 \u6d4b\u8bc4 Lawrence Systems: Blicube BliKVM V4: Is This the Best Linux IP KVM Yet? RainCat: BliKVM V4 Allwinnner\u5b89\u88c5PiKVM\u6559\u7a0b","title":"BliKVM v4 Allwinner"},{"location":"BliKVM-v4-guide/#_1","text":"\u89c6\u9891\u6355\u83b7 (HDMI,\u6700\u9ad8\u652f\u63014K@30Hz\u8f93\u5165) \u952e\u76d8\u8f6c\u53d1 \u9f20\u6807\u8f6c\u53d1 \u865a\u62dfU\u76d8(\u91cd\u88c5\u7cfb\u7edf) HDMI\u89c6\u9891\u73af\u51fa ATX \u4f7f\u7528 ATX \u529f\u80fd\u63a7\u5236\u670d\u52a1\u5668\u7535\u6e90 \u5168\u5c4f\u6a21\u5f0f \u901a\u8fc7 Web UI \u8bbf\u95ee \u652f\u6301 \u591a\u8bed\u8a00 \u5207\u6362 \u652f\u6301 PoE & DC \u652f\u6301 WiFi \u4e32\u53e3 \u63a7\u5236\u53f0\u7aef\u53e3 1.33\u82f1\u5bf8 \u5f69\u8272 \u5c4f\u5e55 \u5b9e\u65f6\u65f6\u949f (RTC) HDMI\u652f\u6301\u7684\u5206\u8fa8\u7387\u7c7b\u578b","title":"\u529f\u80fd\u7279\u70b9"},{"location":"BliKVM-v4-guide/#_2","text":"\u9664v4\u5957\u4ef6\u5916\uff0c\u60a8\u8fd8\u9700\u81ea\u5907\u4ee5\u4e0b\u8bbe\u5907 \u7535\u6e90\u9002\u914d\u5668\uff085V 3A, USB-C\u7aef\u53e3\u621612V 2ADC\u7aef\u53e3\uff09,\u82e5\u4f60\u8ba1\u5212\u4f7f\u7528PoE\u4f9b\u7535\uff0c\u6216\u8005\u6240\u7684\u88ab\u63a7\u8ba1\u7b97\u673aUSB\u53e3\u6709\u5145\u8db3\u7684\u4f9b\u7535\u80fd\u529b\uff0c\u5219\u4e5f\u4e0d\u9700\u8981\u5355\u72ec\u7684\u7535\u6e90\u9002\u914d\u5668\uff1b HDMI \u7ebf\u7f06(\u81f3\u5c11\u4e00\u6839)\uff0c\u82e5\u60a8\u540c\u65f6\u9700\u8981\u4f7f\u7528HDMI\u73af\u51fa\u63a5\u53e3\uff0c\u5219\u9700\u89812\u6839\uff1b \u7f51\u7ebf\uff08\u7ed3\u5408\u60a8\u9700\u6c42\u81ea\u5907\uff09,\u4f7f\u7528ATX\u5f00\u5173\u673a\u529f\u80fd\u9700\u4e00\u6839\uff0c\u4f7f\u7528\u7f51\u7ebf\u4e0a\u7f51\u529f\u80fd\u9700\u4e00\u6839\uff1b USB-C\u8f6cUSB-A\u7ebf\u7f06\u4e00\u6839\uff08\u7528\u4e8e\u9f20\u6807\u548c\u952e\u76d8\u6570\u636e\u4f20\u8f93\uff09. \u7ec8\u7aef\u5347\u7ea7\u6ce8\u610f\uff01 \u5728\u5347\u7ea7\u524d\uff0c\u9700\u6267\u884c\u4e0b\u9762\u547d\u4ee4\uff0c\u5426\u5219apt-get update \u548c apt-get upgrade\u540e\u955c\u50cf\u4f1a\u65e0\u6cd5\u542f\u52a8 apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64 BliKVM v4 \u62c6\u7bb1\uff0c\u8fde\u63a5\uff0c\u4f7f\u7528\u53c2\u8003\u89c6\u9891","title":"\u5b89\u88c5\u8981\u6c42"},{"location":"BliKVM-v4-guide/#_3","text":"1. \u6253\u5f00v4\u5957\u4ef6\u5305\u88c5\uff0c\u6839\u636e\u4e0b\u9762\u6240\u793a\u7684\u8fde\u63a5\u793a\u610f\u56fe\uff0c\u5c06BliKVM\u548c\u88ab\u63a7\u8ba1\u7b97\u673a\u8fde\u63a5\u8d77\u6765\uff1b ATX\u8fde\u63a5 \u8bf7\u53c2\u8003 ATX\u8fde\u63a5\u6307\u5357 \u3002 2. \u5728\u6240\u6709\u8fde\u63a5\u7ebf\u8fde\u63a5\u597d\u540e,\u5bf9BliKVM\u8fdb\u884c\u4e0a\u7535\uff0c\u76f4\u5230\u663e\u793a\u5c4f\u51fa\u73b0\u753b\u9762\uff0c\u5373\u8bbe\u5907\u6b63\u5e38\u542f\u52a8\u3002 3. \u4ed4\u7ec6\u9605\u8bfb \u201c\u7b2c\u4e00\u6b65\u201d \u6307\u5357-\u5982\u4f55\u5728\u7f51\u7edc\u4e0a\u67e5\u627e\u8bbe\u5907\u3001\u5982\u4f55\u767b\u5f55\u3001\u66f4\u6539\u5bc6\u7801\u7b49\u7b49\u3002\u6309\u7167\u4e0a\u9762\u63cf\u8ff0\u7684\u6b65\u9aa4\u64cd\u4f5c\uff0c\u7136\u540e\u8fd4\u56de\u672c\u9875\u3002 4. \u5c1d\u8bd5\u4f7f\u7528 Web \u754c\u9762\u7ba1\u7406\u8ba1\u7b97\u673a\u7684 BliKVM\u3002 \u786e\u4fdd\u60a8\u53ef\u4ee5\u770b\u5230\u56fe\u50cf\u5e76\u4e14\u952e\u76d8\u548c\u9f20\u6807\u90fd\u6b63\u5e38\u5de5\u4f5c\u3002\u5982\u679c\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u8bf7\u67e5\u770b\u6211\u4eec\u7684 \u5e38\u89c1\u95ee\u9898 \uff08\u5b83\u975e\u5e38\u6709\u7528\uff09\u3002\u5982\u679c\u6ca1\u6709\u4efb\u4f55\u5e2e\u52a9\uff0c\u8bf7\u5728\u6211\u4eec\u7684 Discord\u804a\u5929\u5ba4 \u5bfb\u6c42\u652f\u6301\u3002 5. \u60a8\u53ef\u4ee5\u67e5\u770bwiki\u5176\u4ed6\u7684\u9875\u9762\uff0c\u63a2\u7d22BliKVM\u7684\u66f4\u591a\u529f\u80fd\uff0c\u795d\u60a8\u73a9\u7684\u5f00\u5fc3\uff01","title":"\u5b89\u88c5\u6b65\u9aa4"},{"location":"BliKVM-v4-guide/#_4","text":"v4\u6700\u9ad8\u652f\u63014K30Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u4f20\u8f93\u5206\u8fa8\u7387\u9ed8\u8ba4\u4e3a1920x1080\u3002","title":"\u89c6\u9891\u6a21\u5f0f"},{"location":"BliKVM-v4-guide/#_5","text":"BLIKVM v4 Allwinner\u7248\u672c 1 BLIKVM v4 1 WiFi\u5929\u7ebf 1 ATX\u9002\u914d\u677f 1 ATX\u675c\u90a6\u7ebf\u7f06 8pin \u6bcd\u5bf9\u6bcd 60cm 1 ATX\u675c\u90a6\u7ebf\u7f06 8pin \u6bcd\u5bf9\u516c 60cm 1 1U\u5b89\u88c5\u6302\u8033 2 M2.5x5\u87ba\u4e1d 8 \u7845\u80f6\u9632\u649e\u7c92 1","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"BliKVM-v4-guide/#5v","text":"5V\u7aef\u53e3\u53ef\u4ee5\u540c\u65f6\u7528\u4e8e\u4f9b\u7535\u548c\u4e32\u884c\u63a7\u5236\u53f0\u8bbf\u95ee\uff0c\u9ed8\u8ba4\u6ce2\u7279\u7387\u4e3a115200\u3002BliKVM v4\u5185\u90e8\u6709\u4e00\u4e2a\u57fa\u4e8eCH341\u7684USB\u5230UART\u8f6c\u6362\u5668\uff0c\u5b83\u8fde\u63a5\u5230 mCore-H616 SoC \u7684UART0\uff0c\u6240\u4ee5\u4f60\u53ef\u4ee5\u5c06PC\u7684USB\u7aef\u53e3\u8fde\u63a5\u52305V\u7aef\u53e3\uff0c\u65e0\u9700\u5916\u90e8UART\u548cUSB-C\u5230\u675c\u90a6\u9002\u914d\u5668\u3002 PC USB\u7aef\u53e3\u7535\u6d41\u8f93\u51fa \u5c1d\u8bd5\u4f7f\u75285V\u7aef\u53e3\u65f6\u8981\u5c0f\u5fc3\uff0c\u56e0\u4e3a\u5355\u72ec\u7684PC USB\u7aef\u53e3\u53ef\u80fd\u65e0\u6cd5\u63d0\u4f9b3A\uff085V\uff09\uff0c\u8fd9\u662f\u677f\u5361\u5de5\u4f5c\u7684\u8981\u6c42\u3002\u53ef\u4ee5\u540c\u65f6\u4f7f\u752812V 2A DC\u7aef\u53e3\u4f9b\u7535\u548c5V\u7aef\u53e3\u8fdb\u884c\u4e32\u884c\u901a\u4fe1\uff0c\u65e0\u9700 USB\u5206\u7ebf\u5668\u677f \u3002\u6216\u8005\u4f7f\u7528\u5206\u7ebf\u5668\u677f\u5206\u79bb\u51faVCC\u5f15\u811a\uff0c\u5e76\u4f7f\u7528\u5355\u72ec\u76845V 3A\u7535\u6e90\u4e3a5V\u7aef\u53e3\u7684VCC\u5f15\u811a\u4f9b\u7535\u3002\u540c\u6837\uff0c\u5f53BliKVM\u901a\u7535\u65f6\u4ece12V 2A DC\u7aef\u53e3\u65ad\u5f00\u7535\u7f06\u65f6\uff0c\u8981\u786e\u4fdd\u5148\u4ece5V\u7aef\u53e3\u65ad\u5f00\u7535\u7f06\uff08\u56e0\u4e3a\u572812V 2A\u7535\u6e90\u65ad\u5f00\u540e\uff0c\u9664\u975e\u4f7f\u7528\u4e86\u5206\u7ebf\u5668\uff0c\u5426\u52195V\u7aef\u53e3\u5c06\u6210\u4e3aBliKVM v4\u7684\u7535\u6e90\uff09\u3002 \u5f53\u4f60\u5c06USB\u7535\u7f06\u8fde\u63a5\u5230BliKVM v4\u76845V\u7aef\u53e3\u65f6\uff0c\u4f60\u5e94\u8be5\u5728\u4e3b\u673a\u5185\u6838\u65e5\u5fd7\u4e2d\u770b\u5230\u7c7b\u4f3c\u8fd9\u6837\u7684\u5185\u5bb9\uff08\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662f\u57fa\u4e8eLinux\u7684\u64cd\u4f5c\u7cfb\u7edf\uff09: usb 1-1.2: new full-speed USB device number 12 using xhci_hcd usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34 usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.2: Product: USB Serial ch341 1-1.2:1.0: ch341-uart converter detected usb 1-1.2: ch341-uart converter now attached to ttyUSB0 \u7136\u540e\uff0c\u53ef\u4ee5\u4f7f\u7528 GNU screen \u6216 TIO \u8bbf\u95ee\u6b64\u7aef\u53e3: tio /dev/ttyUSB0 mangopimcore login: blikvm # ... \u5982\u679c\u4f60\u9700\u8981\u68c0\u67e5\u901a\u8fc7UART0\u63a5\u6536\u4e86\u591a\u5c11\u6570\u636e\uff0c\u53ef\u4ee5\u901a\u8fc7\u67e5\u770b\u901a\u8fc7proc\u516c\u5f00\u7684\u8ba1\u6570\u5668\u6765\u5b9e\u73b0\uff08\u5f53\u4ece\u5916\u90e8\u4e3b\u673a\u53d1\u9001\u6570\u636e\u65f6\uff0c\u5982\u679c\u5185\u7f6e\u7684USB\u5230UART\u8f6c\u6362\u5668\u5de5\u4f5c\u6b63\u5e38\uff0crx\u8ba1\u6570\u5668\u5e94\u8be5\u4f1a\u589e\u52a0\uff09\uff1a root@mangopimcore:~# grep '0: uart' /proc/tty/driver/serial 0: uart:16550A mmio:0x05000000 irq:284 tx:20306 rx:40 pe:1 RTS|DTR","title":"\u901a\u8fc75V\u7aef\u53e3\u8bbf\u95ee\u4e32\u884c\u63a7\u5236\u53f0"},{"location":"BliKVM-v4-guide/#_6","text":"v4\u6dd8\u5b9d\u5730\u5740","title":"\u8d2d\u4e70\u94fe\u63a5"},{"location":"Datasheet-BliKVM-v4/","text":"BliKVM v4 \u786c\u4ef6\u624b\u518c \u63a5\u53e3\u5b9a\u4e49 1 USB 2.0 10 \u5929\u7ebf\u63a5\u53e3 2 \u4f9b\u7535\u53e3 5V 3A & UART 11 \u7f51\u53e3 100M & PoE 3 ATX \u63a7\u5236\u7aef\u53e3 12 1.33\u5bf8LCD\u5c4f\u5e55 4 HDMI \u89c6\u9891\u73af\u51fa\u7aef\u53e3 13 \u4f9b\u7535\u6307\u793a\u706f (\u7ea2\u8272) 5 USB-PC 14 \u7528\u6237\u81ea\u5b9a\u4e49\u6309\u94ae 6 \u4f9b\u7535\u53e3 12V 2A 5.5*2.1mm 15 \u72b6\u6001\u6307\u793a\u706f (\u7eff\u8272) 7 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 16 \u5c4f\u5e55\u663e\u793a\u6309\u94ae 8 HDMI \u8f93\u5165\u6307\u793a\u706f (\u7eff\u8272) 17 Micro SD \u5361\u69fd 9 HDMI \u8f93\u51fa\u6307\u793a\u706f (\u9ec4\u8272) \u53c2\u6570 \u53c2\u6570\u540d\u79f0 \u63cf\u8ff0 \u4f9b\u7535 5V 3A 5V \u7aef\u53e3, USB-PC \u7aef\u53e3 12V 2A 12V DC\u7aef\u53e3 PoE \u4ee5\u592a\u7f51\u4f9b\u7535 (IEEE802.3af\u534f\u8bae) 48V DC \u7aef\u53e3 HDMI-IN HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 HDMI-OUT HDMI \u89c6\u9891\u73af\u51fa\u7aef\u53e3 USB-PC \u6a21\u62df\u952e\u76d8\uff0c\u9f20\u6807\uff0c\u5927\u5bb9\u91cf\u5b58\u50a8\u5668\u6216\u5176\u4ed6USB\u8bbe\u5907 ATX \u5f00\u5173\u673a\u88ab\u63a7\u7535\u8111\uff0c\u8bfb\u53d6\u88ab\u63a7\u7535\u8111\u72b6\u6001\u6307\u793a\u706f WiFi&BT IEEE802.11 b/g/n + BLE4.2 Micro SD \u5361\u69fd \u5b89\u88c5\u955c\u50cf\u5185\u5b58\u5361 5V port 5V 3A \u7535\u6e90\u6216\u4e32\u884c\u63a7\u5236\u53f0\u7ba1\u7406\u7aef\u53e3 \u663e\u793a\u548c\u6307\u793a\u706f LED\u6307\u793a\u706f \u7535\u6e90\u6307\u793a\u706f\uff0c\u72b6\u6001\u6307\u793a\u706f\uff0cHDM\u8f93\u5165\u8f93\u51fa\u6307\u793a\u706f \u663e\u793a\u5c4f 1.33\u5bf8 TFT \u5f69\u8272\u5c4f\u5e55 \u7528\u6237\u81ea\u5b9a\u4e49\u6309\u94ae SW1 \u8702\u9e23\u5668 Find me \u89c6\u9891 \u5206\u8fa8\u7387 \u6700\u9ad8\u652f\u63014k@30Hz \u7f16\u7801\u683c\u5f0f MJPEG \u6838\u5fc3 \u82af\u7247 \u5168\u5fd7 H616/H313 RAM 1GB \u529f\u8017 \u6700\u9ad815W \u73af\u5883\u53c2\u6570 \u5de5\u4f5c\u6e29\u5ea6 0\u00b0C to 70\u00b0C \u5b58\u50a8\u6e29\u5ea6 -20\u00b0C to 60\u00b0C \u5c3a\u5bf8\u548c\u91cd\u91cf \u5c3a\u5bf8 100 (L) x 134 (W) x 44.4 (H) mm \u91cd\u91cf 0.45 kg BLIKVM CM4\u7248\u672c OLED\u663e\u793a\u5c4f \u8be5\u4ea7\u54c1\u6807\u914d\u4e00\u5757\u5206\u8fa8\u7387\u4e3a128x64\u7684\u5355\u8272OLED\u663e\u793a\u5c4f\uff0c\u82af\u7247\u578b\u53f7\u4e3aSSD1306\u3002 \u7528\u6237\u901a\u8fc7\u663e\u793a\u5c4f\u7684\u5e03\u7ebf\u5c06\u5176\u8fde\u63a5\u5230\u4ea7\u54c1\u3002 \u8be5\u6a21\u5757\u901a\u8fc7I^2^C\u63a5\u53e3\u8fde\u63a5\u5230CM4\u3002\u5e03\u7ebf\u5b9a\u4e49\u5982\u4e0b\u8868\u6240\u793a\u3002 \u8fd9\u662f\u4e00\u4e2a\u57fa\u4e8e SSD1306\u9a71\u52a8 \u7684\u5355\u8272OLED\u5e93\u3002 Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C) \u5916\u5f62\u5c3a\u5bf8","title":"BliKVM v4 \u786c\u4ef6\u624b\u518c"},{"location":"Datasheet-BliKVM-v4/#blikvm-v4","text":"","title":"BliKVM v4 \u786c\u4ef6\u624b\u518c"},{"location":"Datasheet-BliKVM-v4/#_1","text":"1 USB 2.0 10 \u5929\u7ebf\u63a5\u53e3 2 \u4f9b\u7535\u53e3 5V 3A & UART 11 \u7f51\u53e3 100M & PoE 3 ATX \u63a7\u5236\u7aef\u53e3 12 1.33\u5bf8LCD\u5c4f\u5e55 4 HDMI \u89c6\u9891\u73af\u51fa\u7aef\u53e3 13 \u4f9b\u7535\u6307\u793a\u706f (\u7ea2\u8272) 5 USB-PC 14 \u7528\u6237\u81ea\u5b9a\u4e49\u6309\u94ae 6 \u4f9b\u7535\u53e3 12V 2A 5.5*2.1mm 15 \u72b6\u6001\u6307\u793a\u706f (\u7eff\u8272) 7 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 16 \u5c4f\u5e55\u663e\u793a\u6309\u94ae 8 HDMI \u8f93\u5165\u6307\u793a\u706f (\u7eff\u8272) 17 Micro SD \u5361\u69fd 9 HDMI \u8f93\u51fa\u6307\u793a\u706f (\u9ec4\u8272)","title":"\u63a5\u53e3\u5b9a\u4e49"},{"location":"Datasheet-BliKVM-v4/#_2","text":"\u53c2\u6570\u540d\u79f0 \u63cf\u8ff0 \u4f9b\u7535 5V 3A 5V \u7aef\u53e3, USB-PC \u7aef\u53e3 12V 2A 12V DC\u7aef\u53e3 PoE \u4ee5\u592a\u7f51\u4f9b\u7535 (IEEE802.3af\u534f\u8bae) 48V DC \u7aef\u53e3 HDMI-IN HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 HDMI-OUT HDMI \u89c6\u9891\u73af\u51fa\u7aef\u53e3 USB-PC \u6a21\u62df\u952e\u76d8\uff0c\u9f20\u6807\uff0c\u5927\u5bb9\u91cf\u5b58\u50a8\u5668\u6216\u5176\u4ed6USB\u8bbe\u5907 ATX \u5f00\u5173\u673a\u88ab\u63a7\u7535\u8111\uff0c\u8bfb\u53d6\u88ab\u63a7\u7535\u8111\u72b6\u6001\u6307\u793a\u706f WiFi&BT IEEE802.11 b/g/n + BLE4.2 Micro SD \u5361\u69fd \u5b89\u88c5\u955c\u50cf\u5185\u5b58\u5361 5V port 5V 3A \u7535\u6e90\u6216\u4e32\u884c\u63a7\u5236\u53f0\u7ba1\u7406\u7aef\u53e3 \u663e\u793a\u548c\u6307\u793a\u706f LED\u6307\u793a\u706f \u7535\u6e90\u6307\u793a\u706f\uff0c\u72b6\u6001\u6307\u793a\u706f\uff0cHDM\u8f93\u5165\u8f93\u51fa\u6307\u793a\u706f \u663e\u793a\u5c4f 1.33\u5bf8 TFT \u5f69\u8272\u5c4f\u5e55 \u7528\u6237\u81ea\u5b9a\u4e49\u6309\u94ae SW1 \u8702\u9e23\u5668 Find me \u89c6\u9891 \u5206\u8fa8\u7387 \u6700\u9ad8\u652f\u63014k@30Hz \u7f16\u7801\u683c\u5f0f MJPEG \u6838\u5fc3 \u82af\u7247 \u5168\u5fd7 H616/H313 RAM 1GB \u529f\u8017 \u6700\u9ad815W \u73af\u5883\u53c2\u6570 \u5de5\u4f5c\u6e29\u5ea6 0\u00b0C to 70\u00b0C \u5b58\u50a8\u6e29\u5ea6 -20\u00b0C to 60\u00b0C \u5c3a\u5bf8\u548c\u91cd\u91cf \u5c3a\u5bf8 100 (L) x 134 (W) x 44.4 (H) mm \u91cd\u91cf 0.45 kg BLIKVM CM4\u7248\u672c OLED\u663e\u793a\u5c4f \u8be5\u4ea7\u54c1\u6807\u914d\u4e00\u5757\u5206\u8fa8\u7387\u4e3a128x64\u7684\u5355\u8272OLED\u663e\u793a\u5c4f\uff0c\u82af\u7247\u578b\u53f7\u4e3aSSD1306\u3002 \u7528\u6237\u901a\u8fc7\u663e\u793a\u5c4f\u7684\u5e03\u7ebf\u5c06\u5176\u8fde\u63a5\u5230\u4ea7\u54c1\u3002 \u8be5\u6a21\u5757\u901a\u8fc7I^2^C\u63a5\u53e3\u8fde\u63a5\u5230CM4\u3002\u5e03\u7ebf\u5b9a\u4e49\u5982\u4e0b\u8868\u6240\u793a\u3002 \u8fd9\u662f\u4e00\u4e2a\u57fa\u4e8e SSD1306\u9a71\u52a8 \u7684\u5355\u8272OLED\u5e93\u3002 Display(SSD1306) CM4 GND GND VCC 3.3V SCL GPIO3(SCL1,I^2^C) SDA GPIO2(SDA1,I^2^C)","title":"\u53c2\u6570"},{"location":"Datasheet-BliKVM-v4/#_3","text":"","title":"\u5916\u5f62\u5c3a\u5bf8"},{"location":"Expand_Filesystem/","text":"\u6811\u8393\u6d3e\u6269\u5bb9 \u7b80\u4ecb \u7531\u4e8e\u5728\u5236\u4f5c\u955c\u50cf\u8fc7\u7a0b\u4e2d\uff0c\u5bf9\u955c\u50cf\u8fdb\u884c\u4e86\u538b\u7f29\uff0c\u5982\u679c\u4f60\u53d1\u73b0\u6811\u8393\u6d3eSD\u5361\u6216\u8005eMMC\u7684\u53ef\u7528\u7a7a\u95f4\u5c0f\u4e8e\u5b9e\u9645SD\u5361\u6216\u8005eMMc\u7684\u5bb9\u91cf\uff0c\u4f60\u53ef\u80fd\u9700\u8981\u8fdb\u884c\u4ee5\u4e0b\u64cd\u4f5c\uff0c\u5bf9\u6811\u8393\u6d3e\u8fdb\u884c\u6269\u5bb9\u3002 \u5982\u679c\u4f60\u53d1\u73b0\u7cfb\u7edf\u5e76\u65e0raspi-config\u5de5\u5177\uff0c\u5219\u53ef\u4f7f\u7528\u65b9\u6cd5\u4e8c\uff08\u4f7f\u7528GParted\u5206\u533a\u5de5\u5177\uff09\u3002 \u65b9\u6cd5\u4e00 \u4f7f\u7528raspi-config\u5de5\u5177 \u5982\u679c\u4f60\u4f7f\u7528\u76842023\u5e746\u6708\u4efd\u540e\u7684\u955c\u50cf\uff0c\u56e0\u589e\u52a0\u4e86\u7b2c\u4e09\u4e2a\u53ef\u8bfb\u5199\u7684\u5206\u533a\uff0c\u6b64\u65b9\u6cd5\u5df2\u7ecf\u4e0d\u9002\u7528\uff0c\u8bf7\u53c2\u8003\u65b9\u6848\u4e8c\u548c\u65b9\u6848\u4e09\u3002 1. \u6253\u5f00raspi-config\u7cfb\u7edf\u914d\u7f6e\u5de5\u5177 sudo raspi-config 2. \u9009\u62e9Advancd Options\uff1a 3. \u9009\u62e9Expand Filesystem\uff1a 4. Ok: 5. \u7ec8\u7aef\u6267\u884c resize2fs /dev/mmcblk0p2 \u6b64\u547d\u4ee4\u5373\u53ef\u770b\u5230SD\u5361\u5df2\u7ecf\u6269\u5bb9\u6210\u529f\u3002 \u65b9\u6cd5\u4e8c \u4f7f\u7528GParted\u5206\u533a\u5de5\u5177 1. \u5c06\u70e7\u5f55\u597d\u955c\u50cf\u7684SD\u5361\u6216\u8005EMMc\u901a\u8fc7usb\u63a5\u5230\u7535\u8111\u4e0a\uff0c\u4ee5linux\u4e0bGParted\u5206\u533a\u5de5\u5177\u4e3a\u4f8b\uff0c\u5176\u5b83\u5e73\u53f0\u4e5f\u6709\u7c7b\u4f3c\u7684\u5206\u533a\u5de5\u5177\u3002\u6253\u5f00GParted\u8f6f\u4ef6\uff0c\u9009\u62e9SD\u5361\uff1a 2. \u89c2\u5bdf\u4e0a\u56feSD\u5361\u7684\u5206\u533a\u60c5\u51b5\uff0c\u53ef\u4ee5\u53d1\u73b0\u5728sdb3\u5206\u533a\u7684\u524d\u540e\u5404\u67092.01GB\u548c21.87GB\u7684\u7a7a\u95f4\u672a\u4f7f\u7528\uff0c\u8fd9\u90e8\u5206\u7a7a\u95f4\u5c31\u662f\u6211\u4eec\u8981\u6269\u5bb9\u7684\u7a7a\u95f4\u3002\u9009\u4e2dsdb3\u5206\u533a\uff0c\u70b9\u51fb\u8c03\u6574\u5927\u5c0f\u3002 3. \u53ef\u4ee5\u62d6\u52a8sdb3\u7684\u767d\u8272\u5206\u533a\u6269\u5927\u5230\u6700\u5de6\u548c\u6700\u53f3\uff0c\u6216\u8005\u586b\u5199\u201c\u4e4b\u524d\u7684\u53ef\u7528\u7a7a\u95f4\u201d\u4e3a\u201c0\u201d\uff0c\u201c\u65b0\u5927\u5c0f\u201d\u4e3a\u201c\u6700\u5927\u5927\u5c0f\u201d\u768425958\uff0c\u7136\u540e\u70b9\u51fb\u53f3\u4e0b\u89d2\u7684\u8c03\u6574\u5927\u5c0f\uff0c\u7136\u540e\u5f39\u51fa\u6765\u7684\u63d0\u9192\u70b9\u51fb\u786e\u8ba4\uff0c\u5373\u53ef\u770b\u5230sd\u7684\u6240\u6709\u672a\u4f7f\u7528\u7a7a\u95f4\u5168\u90e8\u7528\u4e0a\u4e86\u3002 4. \u5c06SD\u5361\u63d2\u5165\u8bbe\u5907\uff0c\u542f\u52a8\u5373\u53ef\u3002 \u65b9\u6cd5\u4e09: \u4f7f\u7528\u811a\u672c \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM\u955c\u50cf\uff0c\u53ef\u4ee5\u5728KVM\u4e0a\u8fd0\u884c\u4e0b\u9762\u7684\u811a\u672c\uff0c\u6765\u81ea\u52a8\u6269\u5927\u7a7a\u95f4\u3002 1. \u7ec8\u7aef\u767b\u5f55\u5230KVM\u4e0a\uff0c\u786e\u8ba4\u7cfb\u7edf\u6709\u53ef\u8bfb\u5199\u6743\u9650\uff0c\u5728\u4efb\u610f\u8def\u5f84\u8fd0\u884c vim expand.sh ,\u5c06\u4e0b\u9762\u5185\u5bb9\u5199\u5165\u5230expand.sh\u4e2d. \u5982\u679c\u4f60\u662fv1,v2,v3\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u4e0b\u9762\u5185\u5bb9\uff1a #!/bin/bash set -x resize_mmcblk0p3() { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100% resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" \u5982\u679c\u4f60\u662fv4\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u4e0b\u9762\u5185\u5bb9\uff1a #!/bin/bash set -x resize_mmcblk0p1() { echo \"Resizing mmcblk0p1 partition...\" parted /dev/mmcblk0 resizepart 1 100% resize2fs /dev/mmcblk0p1 echo \"mmcblk0p1 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p1 echo \"Partition resizing completed.\" 2. \u7ec8\u7aef\u6267\u884c bash expand.sh ,\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002 \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM\u7684\u955c\u50cf\uff0c\u53ef\u4ee5\u5728KVM\u4e0a\u8fd0\u884c\u4e0b\u9762\u7684\u811a\u672c\uff0c\u6765\u81ea\u52a8\u6269\u5927\u7a7a\u95f4\u3002 1. \u7ec8\u7aef\u767b\u5f55\u5230KVM\u4e0a\uff0c\u786e\u8ba4\u7cfb\u7edf\u6709\u53ef\u8bfb\u5199\u6743\u9650\uff0c\u5728\u4efb\u610f\u8def\u5f84\u8fd0\u884c vim expand.sh ,\u5c06\u4e0b\u9762\u5185\u5bb9\u5199\u5165\u5230expand.sh\u4e2d. #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab; then part=$(grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}') # shellcheck disable=SC2206 splitted=(${part//=/ }) if [ \"${splitted[0]}\" == LABEL ]; then label=${splitted[1]} part=$(blkid -c /dev/null -L \"$label\") else label=PIMSD fi unset splitted disk=/dev/$(lsblk -no pkname \"$part\") npart=$(cat \"/sys/class/block/${part//\\/dev\\//}/partition\") umount \"$part\" parted \"$disk\" -a optimal -s resizepart \"$npart\" 100% yes | mkfs.ext4 -L \"$label\" -F -m 0 \"$part\" mount \"$part\" unset disk part npart label fi 2. \u7ec8\u7aef\u6267\u884c bash expand.sh ,\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002","title":"\u5b58\u50a8\u5361\u6269\u5bb9"},{"location":"Expand_Filesystem/#_1","text":"","title":"\u6811\u8393\u6d3e\u6269\u5bb9"},{"location":"Expand_Filesystem/#_2","text":"\u7531\u4e8e\u5728\u5236\u4f5c\u955c\u50cf\u8fc7\u7a0b\u4e2d\uff0c\u5bf9\u955c\u50cf\u8fdb\u884c\u4e86\u538b\u7f29\uff0c\u5982\u679c\u4f60\u53d1\u73b0\u6811\u8393\u6d3eSD\u5361\u6216\u8005eMMC\u7684\u53ef\u7528\u7a7a\u95f4\u5c0f\u4e8e\u5b9e\u9645SD\u5361\u6216\u8005eMMc\u7684\u5bb9\u91cf\uff0c\u4f60\u53ef\u80fd\u9700\u8981\u8fdb\u884c\u4ee5\u4e0b\u64cd\u4f5c\uff0c\u5bf9\u6811\u8393\u6d3e\u8fdb\u884c\u6269\u5bb9\u3002 \u5982\u679c\u4f60\u53d1\u73b0\u7cfb\u7edf\u5e76\u65e0raspi-config\u5de5\u5177\uff0c\u5219\u53ef\u4f7f\u7528\u65b9\u6cd5\u4e8c\uff08\u4f7f\u7528GParted\u5206\u533a\u5de5\u5177\uff09\u3002","title":"\u7b80\u4ecb"},{"location":"Expand_Filesystem/#raspi-config","text":"\u5982\u679c\u4f60\u4f7f\u7528\u76842023\u5e746\u6708\u4efd\u540e\u7684\u955c\u50cf\uff0c\u56e0\u589e\u52a0\u4e86\u7b2c\u4e09\u4e2a\u53ef\u8bfb\u5199\u7684\u5206\u533a\uff0c\u6b64\u65b9\u6cd5\u5df2\u7ecf\u4e0d\u9002\u7528\uff0c\u8bf7\u53c2\u8003\u65b9\u6848\u4e8c\u548c\u65b9\u6848\u4e09\u3002 1. \u6253\u5f00raspi-config\u7cfb\u7edf\u914d\u7f6e\u5de5\u5177 sudo raspi-config 2. \u9009\u62e9Advancd Options\uff1a 3. \u9009\u62e9Expand Filesystem\uff1a 4. Ok: 5. \u7ec8\u7aef\u6267\u884c resize2fs /dev/mmcblk0p2 \u6b64\u547d\u4ee4\u5373\u53ef\u770b\u5230SD\u5361\u5df2\u7ecf\u6269\u5bb9\u6210\u529f\u3002","title":"\u65b9\u6cd5\u4e00 \u4f7f\u7528raspi-config\u5de5\u5177"},{"location":"Expand_Filesystem/#gparted","text":"1. \u5c06\u70e7\u5f55\u597d\u955c\u50cf\u7684SD\u5361\u6216\u8005EMMc\u901a\u8fc7usb\u63a5\u5230\u7535\u8111\u4e0a\uff0c\u4ee5linux\u4e0bGParted\u5206\u533a\u5de5\u5177\u4e3a\u4f8b\uff0c\u5176\u5b83\u5e73\u53f0\u4e5f\u6709\u7c7b\u4f3c\u7684\u5206\u533a\u5de5\u5177\u3002\u6253\u5f00GParted\u8f6f\u4ef6\uff0c\u9009\u62e9SD\u5361\uff1a 2. \u89c2\u5bdf\u4e0a\u56feSD\u5361\u7684\u5206\u533a\u60c5\u51b5\uff0c\u53ef\u4ee5\u53d1\u73b0\u5728sdb3\u5206\u533a\u7684\u524d\u540e\u5404\u67092.01GB\u548c21.87GB\u7684\u7a7a\u95f4\u672a\u4f7f\u7528\uff0c\u8fd9\u90e8\u5206\u7a7a\u95f4\u5c31\u662f\u6211\u4eec\u8981\u6269\u5bb9\u7684\u7a7a\u95f4\u3002\u9009\u4e2dsdb3\u5206\u533a\uff0c\u70b9\u51fb\u8c03\u6574\u5927\u5c0f\u3002 3. \u53ef\u4ee5\u62d6\u52a8sdb3\u7684\u767d\u8272\u5206\u533a\u6269\u5927\u5230\u6700\u5de6\u548c\u6700\u53f3\uff0c\u6216\u8005\u586b\u5199\u201c\u4e4b\u524d\u7684\u53ef\u7528\u7a7a\u95f4\u201d\u4e3a\u201c0\u201d\uff0c\u201c\u65b0\u5927\u5c0f\u201d\u4e3a\u201c\u6700\u5927\u5927\u5c0f\u201d\u768425958\uff0c\u7136\u540e\u70b9\u51fb\u53f3\u4e0b\u89d2\u7684\u8c03\u6574\u5927\u5c0f\uff0c\u7136\u540e\u5f39\u51fa\u6765\u7684\u63d0\u9192\u70b9\u51fb\u786e\u8ba4\uff0c\u5373\u53ef\u770b\u5230sd\u7684\u6240\u6709\u672a\u4f7f\u7528\u7a7a\u95f4\u5168\u90e8\u7528\u4e0a\u4e86\u3002 4. \u5c06SD\u5361\u63d2\u5165\u8bbe\u5907\uff0c\u542f\u52a8\u5373\u53ef\u3002","title":"\u65b9\u6cd5\u4e8c \u4f7f\u7528GParted\u5206\u533a\u5de5\u5177"},{"location":"Expand_Filesystem/#_3","text":"\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM\u955c\u50cf\uff0c\u53ef\u4ee5\u5728KVM\u4e0a\u8fd0\u884c\u4e0b\u9762\u7684\u811a\u672c\uff0c\u6765\u81ea\u52a8\u6269\u5927\u7a7a\u95f4\u3002 1. \u7ec8\u7aef\u767b\u5f55\u5230KVM\u4e0a\uff0c\u786e\u8ba4\u7cfb\u7edf\u6709\u53ef\u8bfb\u5199\u6743\u9650\uff0c\u5728\u4efb\u610f\u8def\u5f84\u8fd0\u884c vim expand.sh ,\u5c06\u4e0b\u9762\u5185\u5bb9\u5199\u5165\u5230expand.sh\u4e2d. \u5982\u679c\u4f60\u662fv1,v2,v3\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u4e0b\u9762\u5185\u5bb9\uff1a #!/bin/bash set -x resize_mmcblk0p3() { echo \"Resizing mmcblk0p3 partition...\" parted /dev/mmcblk0 resizepart 3 100% resize2fs /dev/mmcblk0p3 echo \"mmcblk0p3 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p3 echo \"Partition resizing completed.\" \u5982\u679c\u4f60\u662fv4\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u4e0b\u9762\u5185\u5bb9\uff1a #!/bin/bash set -x resize_mmcblk0p1() { echo \"Resizing mmcblk0p1 partition...\" parted /dev/mmcblk0 resizepart 1 100% resize2fs /dev/mmcblk0p1 echo \"mmcblk0p1 partition resized successfully.\" } echo \"Starting partition resizing...\" resize_mmcblk0p1 echo \"Partition resizing completed.\" 2. \u7ec8\u7aef\u6267\u884c bash expand.sh ,\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002 \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM\u7684\u955c\u50cf\uff0c\u53ef\u4ee5\u5728KVM\u4e0a\u8fd0\u884c\u4e0b\u9762\u7684\u811a\u672c\uff0c\u6765\u81ea\u52a8\u6269\u5927\u7a7a\u95f4\u3002 1. \u7ec8\u7aef\u767b\u5f55\u5230KVM\u4e0a\uff0c\u786e\u8ba4\u7cfb\u7edf\u6709\u53ef\u8bfb\u5199\u6743\u9650\uff0c\u5728\u4efb\u610f\u8def\u5f84\u8fd0\u884c vim expand.sh ,\u5c06\u4e0b\u9762\u5185\u5bb9\u5199\u5165\u5230expand.sh\u4e2d. #!/bin/bash set -x if grep -q 'X-kvmd\\.otgmsd' /etc/fstab; then part=$(grep 'X-kvmd\\.otgmsd' /etc/fstab | awk '{print $1}') # shellcheck disable=SC2206 splitted=(${part//=/ }) if [ \"${splitted[0]}\" == LABEL ]; then label=${splitted[1]} part=$(blkid -c /dev/null -L \"$label\") else label=PIMSD fi unset splitted disk=/dev/$(lsblk -no pkname \"$part\") npart=$(cat \"/sys/class/block/${part//\\/dev\\//}/partition\") umount \"$part\" parted \"$disk\" -a optimal -s resizepart \"$npart\" 100% yes | mkfs.ext4 -L \"$label\" -F -m 0 \"$part\" mount \"$part\" unset disk part npart label fi 2. \u7ec8\u7aef\u6267\u884c bash expand.sh ,\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002","title":"\u65b9\u6cd5\u4e09: \u4f7f\u7528\u811a\u672c"},{"location":"OLED-display/","text":"\u7b56\u7565 \u5728\u7248\u672c v1.5.0 \u4e4b\u540e, \u4e3a\u4e86\u907f\u514d OLED/LCD \u663e\u793a\u5c4f\u70e7\u5c4f\uff0c\u663e\u793a\u5c4f\u7684\u5f00\u542f\u65f6\u95f4\u4ec5\u6839\u636e\u5176\u914d\u7f6e\u8fdb\u884c\u63a7\u5236\u3002 \u914d\u7f6e // \u6240\u6709\u65f6\u95f4\u53c2\u6570\u5747\u4ee5\u79d2\u4e3a\u5355\u4f4d\uff0c\u4e14\u5fc5\u987b\u4e3a 5 \u7684\u6574\u6570\u500d\u3002 // \u914d\u7f6e\u6587\u4ef6\u8def\u5f84\u5728/mnt/exec/release/config/app.json \"display\":{ \"isActive\": true, \"mode\": 1, \"onBootTime\": 3600, \"cycleInterval\": 300, \"displayTime\": 30, } \u5f53 isActive : true \u6fc0\u6d3b\u663e\u793a\u5c4f \u3002\u5f53 \"isActive\": \"false\" \u65f6\uff0c\u663e\u793a\u5c4f\u5c06\u4e0d\u4f1a\u5de5\u4f5c\u3002 \u6240\u6709 BliKVM \u7248\u672c \u6a21\u5f0f \u63cf\u8ff0 0 \u59cb\u7ec8\u5f00\u542f\uff0c\u4e0d\u8003\u8651\u4efb\u4f55\u53c2\u6570 1 \u663e\u793a\u5c4f\u4fdd\u6301\u5f00\u542f onBootTime \u79d2\uff0c\u7136\u540e\u5173\u95ed\u3002\u53d6\u51b3\u4e8e \"onBootTime\" 2 \u6bcf\u4e2a cycleInterval \u5468\u671f\u5185\uff0c\u663e\u793a\u5c4f\u5f00\u542f displayTime \u79d2\uff0c\u7136\u540e\u5173\u95ed\u3002:rotating_light: \u53d6\u51b3\u4e8e \"cycleInterval\" \u548c \"displayTime\" \u4ec5 BliKVM v4 Allwinner \u7531\u4e8e v4 \u5177\u6709 sw1 \u6309\u94ae\uff0c\u5982\u679c\u8bbe\u7f6e\u6a21\u5f0f\u4e3a 1\u3002 \u884c\u4e3a\uff1a \u542f\u52a8\u65f6\uff1a\u663e\u793a\u5c4f\u5f00\u542f onBootTime \u79d2\uff0c\u7136\u540e\u81ea\u52a8\u5173\u95ed\u3002 \u6309\u4e0b\u6309\u94ae (sw1)\uff1a\u6309\u4e0b sw1 \u663e\u793a\u5c4f\u5f00\u542f displayTime \u79d2\u3002\u5982\u679c\u663e\u793a\u5c4f\u5df2\u7ecf\u5f00\u542f\uff0c\u6309\u4e0b sw1 \u5c06\u6ca1\u6709\u4efb\u4f55\u5f71\u54cd\u3002","title":"OLED\u663e\u793a\u5668"},{"location":"OLED-display/#_1","text":"\u5728\u7248\u672c v1.5.0 \u4e4b\u540e, \u4e3a\u4e86\u907f\u514d OLED/LCD \u663e\u793a\u5c4f\u70e7\u5c4f\uff0c\u663e\u793a\u5c4f\u7684\u5f00\u542f\u65f6\u95f4\u4ec5\u6839\u636e\u5176\u914d\u7f6e\u8fdb\u884c\u63a7\u5236\u3002","title":"\u7b56\u7565"},{"location":"OLED-display/#_2","text":"// \u6240\u6709\u65f6\u95f4\u53c2\u6570\u5747\u4ee5\u79d2\u4e3a\u5355\u4f4d\uff0c\u4e14\u5fc5\u987b\u4e3a 5 \u7684\u6574\u6570\u500d\u3002 // \u914d\u7f6e\u6587\u4ef6\u8def\u5f84\u5728/mnt/exec/release/config/app.json \"display\":{ \"isActive\": true, \"mode\": 1, \"onBootTime\": 3600, \"cycleInterval\": 300, \"displayTime\": 30, } \u5f53 isActive : true \u6fc0\u6d3b\u663e\u793a\u5c4f \u3002\u5f53 \"isActive\": \"false\" \u65f6\uff0c\u663e\u793a\u5c4f\u5c06\u4e0d\u4f1a\u5de5\u4f5c\u3002","title":"\u914d\u7f6e"},{"location":"OLED-display/#blikvm","text":"\u6a21\u5f0f \u63cf\u8ff0 0 \u59cb\u7ec8\u5f00\u542f\uff0c\u4e0d\u8003\u8651\u4efb\u4f55\u53c2\u6570 1 \u663e\u793a\u5c4f\u4fdd\u6301\u5f00\u542f onBootTime \u79d2\uff0c\u7136\u540e\u5173\u95ed\u3002\u53d6\u51b3\u4e8e \"onBootTime\" 2 \u6bcf\u4e2a cycleInterval \u5468\u671f\u5185\uff0c\u663e\u793a\u5c4f\u5f00\u542f displayTime \u79d2\uff0c\u7136\u540e\u5173\u95ed\u3002:rotating_light: \u53d6\u51b3\u4e8e \"cycleInterval\" \u548c \"displayTime\"","title":"\u6240\u6709 BliKVM \u7248\u672c"},{"location":"OLED-display/#blikvm-v4-allwinner","text":"\u7531\u4e8e v4 \u5177\u6709 sw1 \u6309\u94ae\uff0c\u5982\u679c\u8bbe\u7f6e\u6a21\u5f0f\u4e3a 1\u3002 \u884c\u4e3a\uff1a \u542f\u52a8\u65f6\uff1a\u663e\u793a\u5c4f\u5f00\u542f onBootTime \u79d2\uff0c\u7136\u540e\u81ea\u52a8\u5173\u95ed\u3002 \u6309\u4e0b\u6309\u94ae (sw1)\uff1a\u6309\u4e0b sw1 \u663e\u793a\u5c4f\u5f00\u542f displayTime \u79d2\u3002\u5982\u679c\u663e\u793a\u5c4f\u5df2\u7ecf\u5f00\u542f\uff0c\u6309\u4e0b sw1 \u5c06\u6ca1\u6709\u4efb\u4f55\u5f71\u54cd\u3002","title":"\u4ec5 BliKVM v4 Allwinner"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4-ZH/","text":"BliKVM v1 (RPI CM4) BliKVM v1\u662f\u4e00\u6b3e\u57fa\u4e8e\u6811\u8393\u6d3eCM4\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86 \u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406 \u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e \u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5 \u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1 \uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01 \u63a5\u53e3\u5b9a\u4e49 1 OTG \u7aef\u53e3 7 Micro SD \u5361\u69fd 1 OTG \u7aef\u53e3 7 Micro SD \u5361\u69fd 2 USB3.0 x2 8 \u72b6\u6001\u6307\u793a\u706f (\u7eff\u8272) 3 ATX \u63a7\u5236\u7aef\u53e3 9 \u7f51\u53e3 1000M 4 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 10 OLED \u663e\u793a\u5c4f 128x64 5 Type-C\u4f9b\u7535\u7aef\u53e3 5V3A 11 \u5929\u7ebf\u5b89\u88c5\u5b54 6 \u7535\u6e90\u6307\u793a\u706f (\u7ea2\u8272) \u53c2\u6570 \u53c2\u6570\u540d\u79f0 \u63cf\u8ff0 \u4f9b\u7535 5V 3A PWR IN \u7aef\u53e3 \u7aef\u53e3 HDMI IN HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 OTG \u6a21\u62df\u952e\u76d8\uff0c\u9f20\u6807\uff0c\u5927\u5bb9\u91cf\u5b58\u50a8\u5668\u6216\u5176\u4ed6USB\u8bbe\u5907 CN-ATX \u5f00\u5173\u673a\u88ab\u63a7\u7535\u8111\uff0c\u8bfb\u53d6\u88ab\u63a7\u7535\u8111\u72b6\u6001\u6307\u793a\u706f Micro SD \u5361\u69fd \u5b89\u88c5\u955c\u50cf\u5185\u5b58\u5361 PWR IN \u7aef\u53e3 5V3A \u7535\u6e90 \u663e\u793a\u548c\u6307\u793a\u706f LED \u6307\u793a\u706f \u7535\u6e90\u6307\u793a\u706f\uff08\u7ea2\u8272\uff09\uff0c\u72b6\u6001\u6307\u793a\u706f\uff08\u7eff\u8272\uff09 OLED \u663e\u793a\u5c4f OLED 128x64 0.96\u5bf8 \u89c6\u9891 \u5206\u8fa8\u7387 \u6700\u9ad8\u652f\u6301 1920x1200@60Hz \u7f16\u7801\u683c\u5f0f H.264, MJPEG \u6838\u5fc3 \u6a21\u5757 \u6811\u8393\u6d3eCM4\uff08\u81ea\u5907\uff09 \u529f\u8017 Up to 15W \u73af\u5883\u53c2\u6570 \u5de5\u4f5c\u6e29\u5ea6 0\u00b0C to 70\u00b0C \u5b58\u50a8\u6e29\u5ea6 -20\u00b0C to 60\u00b0C \u5c3a\u5bf8\u548c\u91cd\u91cf \u5c3a\u5bf8 120(L) x 70W) x 37(H) mm \u91cd\u91cf 0.45 kg \u5916\u5f62\u5c3a\u5bf8","title":"BliKVM v1 (RPI CM4)"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4-ZH/#blikvm-v1-rpi-cm4","text":"BliKVM v1\u662f\u4e00\u6b3e\u57fa\u4e8e\u6811\u8393\u6d3eCM4\u7684 KVM-over-IP \u8bbe\u5907\uff0c\u4e3a\u4e13\u4e1a\u7528\u6237\u63d0\u4f9b\u4e86 \u8fdc\u7a0b\u670d\u52a1\u5668\u6216\u5de5\u4f5c\u7ad9\u7ba1\u7406 \u7684\u4fbf\u6377\u89e3\u51b3\u65b9\u6848\u3002 \u5b83\u57fa\u4e8eLinux\u5e76\u4e14\u5b8c\u5168\u5f00\u6e90\u3002 \u501f\u52a9 BliKVM\uff0c\u60a8\u53ef\u4ee5\u8f7b\u677e \u6253\u5f00/\u5173\u95ed\u7535\u6e90\u3001\u91cd\u65b0\u542f\u52a8\u8ba1\u7b97\u673a\u3001\u914d\u7f6e UEFI/BIOS \u8bbe\u7f6e\u4ee5\u53ca\u4f7f\u7528\u6a21\u62df\u5927\u5bb9\u91cf\u5b58\u50a8\u8bbe\u5907\u6267\u884c\u64cd\u4f5c\u7cfb\u7edf\u91cd\u65b0\u5b89\u88c5 \u3002 BliKVM \u6a21\u62df\u952e\u76d8\u3001\u9f20\u6807\u548c\u663e\u793a\u5668\uff0c\u6240\u6709\u8fd9\u4e9b\u90fd\u53ef\u4ee5\u901a\u8fc7 Web \u6d4f\u89c8\u5668\u8bbf\u95ee\uff0c\u786e\u4fdd\u65e0\u7f1d\u7684\u7528\u6237\u4f53\u9a8c\u3002 \u5176\u786c\u4ef6\u7ea7\u8bbf\u95ee\u4fdd\u8bc1\u72ec\u7acb\u4e8e\u7279\u5b9a\u7684\u8fdc\u7a0b\u7aef\u53e3\u3001\u534f\u8bae\u6216\u670d\u52a1 \uff0c\u4f7f\u5176\u6210\u4e3a\u4e13\u4e1a\u4eba\u58eb\u9ad8\u5ea6\u7075\u6d3b\u4e14\u53ef\u9760\u7684\u8fdc\u7a0b\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\uff01","title":"BliKVM v1 (RPI CM4)"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4-ZH/#_1","text":"1 OTG \u7aef\u53e3 7 Micro SD \u5361\u69fd 1 OTG \u7aef\u53e3 7 Micro SD \u5361\u69fd 2 USB3.0 x2 8 \u72b6\u6001\u6307\u793a\u706f (\u7eff\u8272) 3 ATX \u63a7\u5236\u7aef\u53e3 9 \u7f51\u53e3 1000M 4 HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 10 OLED \u663e\u793a\u5c4f 128x64 5 Type-C\u4f9b\u7535\u7aef\u53e3 5V3A 11 \u5929\u7ebf\u5b89\u88c5\u5b54 6 \u7535\u6e90\u6307\u793a\u706f (\u7ea2\u8272)","title":"\u63a5\u53e3\u5b9a\u4e49"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4-ZH/#_2","text":"\u53c2\u6570\u540d\u79f0 \u63cf\u8ff0 \u4f9b\u7535 5V 3A PWR IN \u7aef\u53e3 \u7aef\u53e3 HDMI IN HDMI \u89c6\u9891\u8f93\u5165\u7aef\u53e3 OTG \u6a21\u62df\u952e\u76d8\uff0c\u9f20\u6807\uff0c\u5927\u5bb9\u91cf\u5b58\u50a8\u5668\u6216\u5176\u4ed6USB\u8bbe\u5907 CN-ATX \u5f00\u5173\u673a\u88ab\u63a7\u7535\u8111\uff0c\u8bfb\u53d6\u88ab\u63a7\u7535\u8111\u72b6\u6001\u6307\u793a\u706f Micro SD \u5361\u69fd \u5b89\u88c5\u955c\u50cf\u5185\u5b58\u5361 PWR IN \u7aef\u53e3 5V3A \u7535\u6e90 \u663e\u793a\u548c\u6307\u793a\u706f LED \u6307\u793a\u706f \u7535\u6e90\u6307\u793a\u706f\uff08\u7ea2\u8272\uff09\uff0c\u72b6\u6001\u6307\u793a\u706f\uff08\u7eff\u8272\uff09 OLED \u663e\u793a\u5c4f OLED 128x64 0.96\u5bf8 \u89c6\u9891 \u5206\u8fa8\u7387 \u6700\u9ad8\u652f\u6301 1920x1200@60Hz \u7f16\u7801\u683c\u5f0f H.264, MJPEG \u6838\u5fc3 \u6a21\u5757 \u6811\u8393\u6d3eCM4\uff08\u81ea\u5907\uff09 \u529f\u8017 Up to 15W \u73af\u5883\u53c2\u6570 \u5de5\u4f5c\u6e29\u5ea6 0\u00b0C to 70\u00b0C \u5b58\u50a8\u6e29\u5ea6 -20\u00b0C to 60\u00b0C \u5c3a\u5bf8\u548c\u91cd\u91cf \u5c3a\u5bf8 120(L) x 70W) x 37(H) mm \u91cd\u91cf 0.45 kg","title":"\u53c2\u6570"},{"location":"Product-Datasheet-BliKVM-v1-RPI-CM4-ZH/#_3","text":"","title":"\u5916\u5f62\u5c3a\u5bf8"},{"location":"atx-guide/","text":"ATXA guide 1. Introduction ATXA is an ATX adapter borad to manage the power of your computer. The product includes two modules A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable.Join to the Discord Community Chat for news, questions and support! ATXA_A ATXA_B 2. A-board A-board is connected to the Raspberry Pi. The following table is a typical connection method in BLIKVM and PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed 3. B-board The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B\u4e0e\u7535\u8111\u4e3b\u677f\u8fde\u63a5\u8bf4\u660e \u6839\u636e\u7535\u8111\u4e3b\u677f\u8bf4\u660e\uff0c\u9996\u5148\u627e\u5230\u4e3b\u677f\u4e0aATX\u529f\u80fd\u76f8\u5173\u5f15\u811a\u4f4d\u7f6e\uff0c\u62d4\u4e0b\u4e3b\u677f\u5df2\u7ecf\u63a5\u597d\u7684ATX\u7ebf\uff0c\u62d4\u4e0b\u540e\u7535\u8111\u7684\u7535\u6e90\u6309\u94ae\u5c06\u5931\u53bb\u4f5c\u7528\u3002ATXA-B\u4e3b\u677f\u5171\u6709\u4e24\u63928PIN\u5f15\u811a\uff0c\u4e24\u6392\u5f15\u811a\u529f\u80fd\u5b8c\u5168\u76f8\u540c\u4f7f\u7528\u65f6\u65e0\u9700\u533a\u5206\u3002\u5176\u4e2d\u4e00\u6392\u5f15\u811a\u7528\u4e8eKVM\u63a7\u5236ATX\u76f8\u5173\u529f\u80fd\uff0c\u53e6\u4e00\u6392\u5f15\u811a\u63a5\u4e3b\u677f\u4e0a\u62d4\u4e0b\u6765\u7684ATX\u675c\u90a6\u5934\uff0c\u4fdd\u6301\u539f\u6709\u673a\u7bb1\u7535\u6e90\u6309\u94ae\u529f\u80fd\u3002\u6839\u636e\u4e3b\u677f\u548cATX-B\u4e0a\u7684\u5177\u4f53\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u6bcf\u6839\u7ebf\u7684\u8fde\u63a5\uff0c\u8fde\u63a5\u5173\u7cfb\u53ef\u4ee5\u53c2\u8003\u4e0b\u56fe\uff1a 4.Mechanical Diagram 5.Test video youtube\uff1a ATX 6.More link Purchase\uff1a ATX","title":"ATX\u7528\u6237\u624b\u518c"},{"location":"atx-guide/#atxa-guide","text":"","title":"ATXA guide"},{"location":"atx-guide/#1-introduction","text":"ATXA is an ATX adapter borad to manage the power of your computer. The product includes two modules A-board and B-board. A-board is connected to the Raspberry Pi, B-board is connected to the computer's motherboard, and A-board is connected to B-board through a network cable.Join to the Discord Community Chat for news, questions and support! ATXA_A ATXA_B","title":"1. Introduction"},{"location":"atx-guide/#2-a-board","text":"A-board is connected to the Raspberry Pi. The following table is a typical connection method in BLIKVM and PiKVM application. A-board RPI4 GND GND 3V3 3V3 LED PWR GPIO24 LED HDD GPIO22 SW PWR GPIO23 SW RST GPIO27 A-board is connected to B-board through a network cable. The following table is the corresponding relationship between the pin status of A-board and B-board. Pins on A-board Pins on B-board LED PWR is HIGH LED PWR+ is HIGH, LED PWR- is LOW LED PWR is LOW LED PWR+ is LOW, LED PWR- is LOW LED HDD is HIGH LED HDD+ is HIGH, LED HDD- is LOW LED HDD is LOW LED HDD+ is LOW, LED HDD- is LOW SW PWR is HIGH BTN PWR+ and BTN PWR- connected, the power button is pressed SW PWR is LOW BTN PWR+ and BTN PWR- disconnected, the power button is unpressed SW RST is HIGH BTN RST+ and BTN RST- connected, the reset button is pressed SW RST is LOW BTN RST+ and BTN RST- disconnected, the reset button is unpressed","title":"2. A-board"},{"location":"atx-guide/#3-b-board","text":"The b-board has an adapted full-height and half-height metal PCI mounting plate, which can be installed on the computer case. The user connects the pins on the B-board to the ATX control interface on the computer motherboard using the color DuPont cables provided with the product. ATXA-B\u4e0e\u7535\u8111\u4e3b\u677f\u8fde\u63a5\u8bf4\u660e \u6839\u636e\u7535\u8111\u4e3b\u677f\u8bf4\u660e\uff0c\u9996\u5148\u627e\u5230\u4e3b\u677f\u4e0aATX\u529f\u80fd\u76f8\u5173\u5f15\u811a\u4f4d\u7f6e\uff0c\u62d4\u4e0b\u4e3b\u677f\u5df2\u7ecf\u63a5\u597d\u7684ATX\u7ebf\uff0c\u62d4\u4e0b\u540e\u7535\u8111\u7684\u7535\u6e90\u6309\u94ae\u5c06\u5931\u53bb\u4f5c\u7528\u3002ATXA-B\u4e3b\u677f\u5171\u6709\u4e24\u63928PIN\u5f15\u811a\uff0c\u4e24\u6392\u5f15\u811a\u529f\u80fd\u5b8c\u5168\u76f8\u540c\u4f7f\u7528\u65f6\u65e0\u9700\u533a\u5206\u3002\u5176\u4e2d\u4e00\u6392\u5f15\u811a\u7528\u4e8eKVM\u63a7\u5236ATX\u76f8\u5173\u529f\u80fd\uff0c\u53e6\u4e00\u6392\u5f15\u811a\u63a5\u4e3b\u677f\u4e0a\u62d4\u4e0b\u6765\u7684ATX\u675c\u90a6\u5934\uff0c\u4fdd\u6301\u539f\u6709\u673a\u7bb1\u7535\u6e90\u6309\u94ae\u529f\u80fd\u3002\u6839\u636e\u4e3b\u677f\u548cATX-B\u4e0a\u7684\u5177\u4f53\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u6bcf\u6839\u7ebf\u7684\u8fde\u63a5\uff0c\u8fde\u63a5\u5173\u7cfb\u53ef\u4ee5\u53c2\u8003\u4e0b\u56fe\uff1a","title":"3. B-board"},{"location":"atx-guide/#4mechanical-diagram","text":"","title":"4.Mechanical Diagram"},{"location":"atx-guide/#5test-video","text":"youtube\uff1a ATX","title":"5.Test video"},{"location":"atx-guide/#6more-link","text":"Purchase\uff1a ATX","title":"6.More link"},{"location":"atx/","text":"ATX\u63a7\u5236\u677f \u4e3a\u4e86\u7ba1\u7406\u60a8\u7684\u8ba1\u7b97\u673a\u7684\u7535\u6e90\uff0c\u60a8\u9700\u8981\u5728\u673a\u7bb1\u5185\u5b89\u88c5\u4e00\u4e2aATX\u9002\u914d\u677f\uff0c\u5e76\u5c06\u5176\u8fde\u63a5\u5230\u4e3b\u677f\u4e0a\uff08\u4e3a\u4e86KVM\u76f4\u63a5\u901a\u8fc7ATX\u63a7\u5236\u5f00\u5173\u673a\uff09\u3002\u6709\u4e00\u6839\u4ece\u4e3b\u677f\u5230ATX\u9002\u914d\u677f\u7684\u6bcd\u5bf9\u6bcd\u7ebf\u7f06\uff0c\u4ee5\u53ca\u4e00\u4e2a\u4eceATX\u9002\u914d\u677f\u5230\u524d\u9762\u677f\u7684\u516c\u5bf9\u6bcd\u7ebf\u7f06\uff08\u4e3a\u4e86\u4f7f\u673a\u7bb1\u7684\u5f00\u5173\u673a\u6309\u94ae\u4ecd\u7136\u6709\u6548\uff09\u3002ATX\u9002\u914d\u677f\u4e0a\u6709\u4e2a\u63a5\u53e3(TO CASE, TO MB)\uff0c\u4e24\u4e2a\u63a5\u53e3\u529f\u80fd\u4e00\u6a21\u4e00\u6837\uff0c\u4f7f\u7528\u65f6\u53ef\u4ee5\u4e0d\u7528\u533a\u5206\u3002 \u7b14\u8bb0\u672c\u7535\u8111\u4e0d\u517c\u5bb9ATX\uff0c\u56e0\u4e3a\u5b83\u4eec\u7f3a\u5c11\u6240\u9700\u7684ATX\u5f15\u811a\uff0c\u6b64\u65b9\u6cd5\u4ec5\u9002\u7528\u4e8ePC\u670d\u52a1\u5668\u548c\u53f0\u5f0f\u673a\u3002 \u8be6\u7ec6\u8bf4\u660e 1. \u5c06\u4e24\u6839\u7ebf\u7f06\u8fde\u63a5\u5230ATX\u9002\u914d\u677f, \u4e3a\u4e86\u56fa\u5b9aATX\u9002\u914d\u677f\u5728\u673a\u7bb1\u4e2d\uff0c\u60a8\u53ef\u4ee5\u9009\u62e9\u4f7f\u7528\u6321\u677f\u5c06ATX\u9002\u914d\u677f\u5b89\u88c5\u5728PCIe\u63d2\u69fd\u4e0a\u3002 Example 2. \u627e\u5230\u8d1f\u8d23\u8fde\u63a5\u673a\u7bb1\u524d\u9762\u677f\u6309\u94ae\u548cLED\u7684\u4e3b\u677f\u5f15\u811a\uff0c\u5e76\u5c06\u5176\u62d4\u51fa\u3002\u901a\u5e38\u4e3b\u677f\u4e0a\u7684\u7ebf\u7f06\u548c\u8fde\u63a5\u5668\u90fd\u6709\u6807\u8bc6\u3002\u5982\u679c\u60a8\u4e0d\u786e\u5b9a\uff0c\u53ef\u4ee5\u67e5\u9605\u60a8\u4e3b\u677f\u7684\u6587\u6863\u3002 Example 3. \u8fde\u63a5\u524d\u9762\u677f\u7684\u675c\u90a6\u6bcd\u5934\u548cATX\u7ebf\u7f06\u7684\u675c\u90a6\u516c\u5934\uff0c\u6309\u7167\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u8fde\u63a5\uff0c\u6ce8\u610f\u6807\u7b7e\u548c\u6781\u6027\uff08+\u6216-\uff09\u3002 Example 4. \u4f7f\u7528\u76f8\u540c\u7684\u65b9\u5f0f\uff0c\u5c06ATX\u677f\u7684\u6bcd\u5f15\u811a\u8fde\u63a5\u5230\u4e3b\u677f\u7684\u8fde\u63a5\u5668\u4e0a\u3002\u67e5\u9605\u60a8\u4e3b\u677f\u7684\u6587\u6863\u4ee5\u4e86\u89e3\u4e3b\u677f\u4e0a\u7684\u54ea\u4e2a\u5f15\u811a\u8fde\u63a5\u5230ATX\u9002\u914d\u677f\u7684\u54ea\u4e2a\u5f15\u811a\u3002\u6709\u65f6\u8fd9\u4e9b\u4fe1\u606f\u4f1a\u5370\u5728\u4e3b\u677f\u4e0a\u3002 Example 5. \u5c06ATX\u677f\u5b89\u88c5\u5230\u673a\u7bb1\u7684PCI\u63d2\u69fd\u4e2d\uff0c\u5e76\u7528\u87ba\u9489\u56fa\u5b9a\uff0c\u6216\u6839\u636e\u60a8\u7684\u559c\u597d\u4f7f\u7528\u5176\u4ed6\u5b89\u88c5\u65b9\u6cd5\u3002 Example 6. \u5c06\u7ebf\u7f06\u6574\u7406\u6210\u65b9\u4fbf\u7684\u65b9\u5f0f\uff0c\u5e76\u5728\u9700\u8981\u65f6\u56fa\u5b9a\u5b83\u4eec\u3002\u786e\u4fdd\u7ebf\u7f06\u4e0d\u4e0e\u673a\u7bb1\u5185\u7684\u4efb\u4f55\u98ce\u6247\u63a5\u89e6\u3002\u4f7f\u7528\u4ee5\u592a\u7f51\u7ebf\u5c06ATX\u677f\u4e0eBliKVM\u7684ATX\u63a5\u53e3\u8fde\u63a5\u8d77\u6765\u3002\u81f3\u6b64ATX\u9002\u914d\u677f\u786c\u4ef6\u90e8\u5206\u8fde\u63a5\u5df2\u5b8c\u6210\u3002","title":"ATX\u63a7\u5236\u677f"},{"location":"atx/#atx","text":"\u4e3a\u4e86\u7ba1\u7406\u60a8\u7684\u8ba1\u7b97\u673a\u7684\u7535\u6e90\uff0c\u60a8\u9700\u8981\u5728\u673a\u7bb1\u5185\u5b89\u88c5\u4e00\u4e2aATX\u9002\u914d\u677f\uff0c\u5e76\u5c06\u5176\u8fde\u63a5\u5230\u4e3b\u677f\u4e0a\uff08\u4e3a\u4e86KVM\u76f4\u63a5\u901a\u8fc7ATX\u63a7\u5236\u5f00\u5173\u673a\uff09\u3002\u6709\u4e00\u6839\u4ece\u4e3b\u677f\u5230ATX\u9002\u914d\u677f\u7684\u6bcd\u5bf9\u6bcd\u7ebf\u7f06\uff0c\u4ee5\u53ca\u4e00\u4e2a\u4eceATX\u9002\u914d\u677f\u5230\u524d\u9762\u677f\u7684\u516c\u5bf9\u6bcd\u7ebf\u7f06\uff08\u4e3a\u4e86\u4f7f\u673a\u7bb1\u7684\u5f00\u5173\u673a\u6309\u94ae\u4ecd\u7136\u6709\u6548\uff09\u3002ATX\u9002\u914d\u677f\u4e0a\u6709\u4e2a\u63a5\u53e3(TO CASE, TO MB)\uff0c\u4e24\u4e2a\u63a5\u53e3\u529f\u80fd\u4e00\u6a21\u4e00\u6837\uff0c\u4f7f\u7528\u65f6\u53ef\u4ee5\u4e0d\u7528\u533a\u5206\u3002 \u7b14\u8bb0\u672c\u7535\u8111\u4e0d\u517c\u5bb9ATX\uff0c\u56e0\u4e3a\u5b83\u4eec\u7f3a\u5c11\u6240\u9700\u7684ATX\u5f15\u811a\uff0c\u6b64\u65b9\u6cd5\u4ec5\u9002\u7528\u4e8ePC\u670d\u52a1\u5668\u548c\u53f0\u5f0f\u673a\u3002","title":"ATX\u63a7\u5236\u677f"},{"location":"atx/#_1","text":"1. \u5c06\u4e24\u6839\u7ebf\u7f06\u8fde\u63a5\u5230ATX\u9002\u914d\u677f, \u4e3a\u4e86\u56fa\u5b9aATX\u9002\u914d\u677f\u5728\u673a\u7bb1\u4e2d\uff0c\u60a8\u53ef\u4ee5\u9009\u62e9\u4f7f\u7528\u6321\u677f\u5c06ATX\u9002\u914d\u677f\u5b89\u88c5\u5728PCIe\u63d2\u69fd\u4e0a\u3002 Example 2. \u627e\u5230\u8d1f\u8d23\u8fde\u63a5\u673a\u7bb1\u524d\u9762\u677f\u6309\u94ae\u548cLED\u7684\u4e3b\u677f\u5f15\u811a\uff0c\u5e76\u5c06\u5176\u62d4\u51fa\u3002\u901a\u5e38\u4e3b\u677f\u4e0a\u7684\u7ebf\u7f06\u548c\u8fde\u63a5\u5668\u90fd\u6709\u6807\u8bc6\u3002\u5982\u679c\u60a8\u4e0d\u786e\u5b9a\uff0c\u53ef\u4ee5\u67e5\u9605\u60a8\u4e3b\u677f\u7684\u6587\u6863\u3002 Example 3. \u8fde\u63a5\u524d\u9762\u677f\u7684\u675c\u90a6\u6bcd\u5934\u548cATX\u7ebf\u7f06\u7684\u675c\u90a6\u516c\u5934\uff0c\u6309\u7167\u5f15\u811a\u5b9a\u4e49\u8fdb\u884c\u8fde\u63a5\uff0c\u6ce8\u610f\u6807\u7b7e\u548c\u6781\u6027\uff08+\u6216-\uff09\u3002 Example 4. \u4f7f\u7528\u76f8\u540c\u7684\u65b9\u5f0f\uff0c\u5c06ATX\u677f\u7684\u6bcd\u5f15\u811a\u8fde\u63a5\u5230\u4e3b\u677f\u7684\u8fde\u63a5\u5668\u4e0a\u3002\u67e5\u9605\u60a8\u4e3b\u677f\u7684\u6587\u6863\u4ee5\u4e86\u89e3\u4e3b\u677f\u4e0a\u7684\u54ea\u4e2a\u5f15\u811a\u8fde\u63a5\u5230ATX\u9002\u914d\u677f\u7684\u54ea\u4e2a\u5f15\u811a\u3002\u6709\u65f6\u8fd9\u4e9b\u4fe1\u606f\u4f1a\u5370\u5728\u4e3b\u677f\u4e0a\u3002 Example 5. \u5c06ATX\u677f\u5b89\u88c5\u5230\u673a\u7bb1\u7684PCI\u63d2\u69fd\u4e2d\uff0c\u5e76\u7528\u87ba\u9489\u56fa\u5b9a\uff0c\u6216\u6839\u636e\u60a8\u7684\u559c\u597d\u4f7f\u7528\u5176\u4ed6\u5b89\u88c5\u65b9\u6cd5\u3002 Example 6. \u5c06\u7ebf\u7f06\u6574\u7406\u6210\u65b9\u4fbf\u7684\u65b9\u5f0f\uff0c\u5e76\u5728\u9700\u8981\u65f6\u56fa\u5b9a\u5b83\u4eec\u3002\u786e\u4fdd\u7ebf\u7f06\u4e0d\u4e0e\u673a\u7bb1\u5185\u7684\u4efb\u4f55\u98ce\u6247\u63a5\u89e6\u3002\u4f7f\u7528\u4ee5\u592a\u7f51\u7ebf\u5c06ATX\u677f\u4e0eBliKVM\u7684ATX\u63a5\u53e3\u8fde\u63a5\u8d77\u6765\u3002\u81f3\u6b64ATX\u9002\u914d\u677f\u786c\u4ef6\u90e8\u5206\u8fde\u63a5\u5df2\u5b8c\u6210\u3002","title":"\u8be6\u7ec6\u8bf4\u660e"},{"location":"bliswitch-v1-guide/","text":"BliKVM switch v1 KVM\u5207\u6362\u5668\u624b\u518c BliKVM-Switch-V1.0\u5b9e\u9645\u4f7f\u7528\u548c\u6d4b\u8bd5\u89c6\u9891\uff0c\u652f\u6301BliKVM\u548cPiKVM \u7b80\u4ecb BliKVM-Switch-V1.0\u4e3a\u56db\u901a\u9053HDMI+USB\u5207\u6362\u5668\uff0c\u652f\u6301\u673a\u5668\u6309\u952e\u5207\u6362\uff0c\u684c\u9762\u63a7\u5236\u5668\u5207\u6362\uff0cKVM\u8fdc\u7a0b\u5207\u6362\uff0c3\u79cd\u5207\u6362\u6a21\u5f0f\u3002\u5207\u6362\u5668\u672c\u8eab\u6700\u9ad8\u652f\u63014K@60HZ\u7684\u8f93\u5165\uff0c\u5373\u63d2\u5373\u7528\uff0c\u514d\u9a71\u52a8\u3002 BliKVM-Switch-V1.0\u4f7f\u7528\u548cXH-HK4401\u76f8\u540c\u7684\u786c\u4ef6\u65b9\u6848,AG7210 HDMI\u5207\u6362\u82af\u7247\u6700\u9ad8\u652f\u6301\u52304K@60Hz\uff0cCH444G USB\u5207\u6362\u82af\u7247\u652f\u6301USB2.0\u3002\u4e0d\u540c\u7684\u662fBliKVM-Switch-V1.0\u914d\u5907\u6709KVM USB cable,\u53ef\u4ee5\u901a\u8fc7KVM USB cable\u8fde\u63a5BliKVM-Switch-V1.0,\u5b9e\u73b0\u5bf9KVM\u7aef\u53e3\u7684\u9009\u62e9\u3002BliKVM-Switch-V1.0\u9002\u914dBliKVM\u548cPiKVM\u3002 \u6ce8\u610f\u4e8b\u9879 switch\u53ef\u4ee5\u76f4\u63a5\u4ece\u8f93\u5165\u7535\u8111\u7684USB\u53d6\u7535\uff0c\u5373\u4e00\u822c\u4e0d\u9700\u8981\u7ed9switch\u4f9b\u7535\uff0c\u5373\u53ef\u6b63\u5e38\u5de5\u4f5c\uff1b \u82e5\u88ab\u63a7\u7535\u8111\u7684USB\u4f9b\u7535\u65e0\u6cd5\u4f7fswitch\u5de5\u4f5c\uff0c\u53ef\u4ee5\u5bf9switch\u8fdb\u884c\u5355\u72ec\u4f9b\u7535\u4f7f\u7528\uff1b switch\u5957\u88c5\u53ea\u63d0\u4f9b\u4e86USB\u7535\u6e90\u7ebf\uff0c\u5e76\u6ca1\u6709\u63d0\u4f9b\u7535\u6e90\u9002\u914d\u5668\uff0c\u9700\u8981\u5ba2\u6237\u81ea\u884c\u914d\u7f6e\u7535\u6e90\u9002\u914d\u5668\uff085V\uff09\uff1b \u684c\u9762\u63a7\u5236\u5668 \u53ef\u4ee5\u901a\u8fc7USB\u7535\u7f06\u63a7\u5236\u5207\u6362\uff0c\u5bf9\u4e8e\u4e0d\u4f7f\u7528KVM\u7684\u5ba2\u6237\uff0c\u5f53\u60a8\u5728\u8bbe\u5907\u65c1\u8fb9\u65f6\uff0c\u8fd9\u662f\u9664\u4f7f\u7528switch\u8bbe\u5907\u4e0a\u6309\u94ae\u5207\u6362\u4e4b\u5916\u7684\u53e6\u4e00\u79cd\u5207\u6362\u65b9\u5f0f\uff1b HDMI\u8f93\u5165\u6700\u9ad8\u652f\u6301 4096x2160/60Hz \uff1b 4K 60Hz\u7684HDMI\u8f93\u5165, \u529f\u7387\u5927\u6982\u662f200mW; \u63a5\u53e3\u793a\u610f\u56fe \u8fd9\u91cc\u9700\u8981\u4e24\u6839USB\u7ebf\uff0c\u8fde\u63a5switch\u548ckvm\u786c\u4ef6\uff0c\u4e00\u6839\u7528\u4e8e\u4f20\u8f93\u63a7\u5236\u5207\u6362\u901a\u9053\u4fe1\u606f\uff0c\u4e00\u6839\u7528\u4e8e\u4f20\u8f93\u9f20\u6807\u952e\u76d8\u6570\u636e\uff0c\u5177\u4f53\u8fde\u63a5\u53ef\u4ee5\u53c2\u8003\u9762\u8bf4\u660e\u3002 \u6b63\u9762\u548c\u53cd\u9762\u63a5\u53e3\u793a\u610f\u56fe\uff0c\u53f3\u4fa7\u56fe\u4e2d\u7684control\u63a5\u53e3\u5373\u4e3a\u8fdc\u7a0b\u63a7\u5236\u63a5\u53e3, \u4e00\u5934\u4e3aUSB-A\uff0c\u53e6\u4e00\u5934\u4e3amicro usb\u5e76\u4e14\u6807\u7b7e\u5e26\u6709kvm\u5b57\u6837\u7684\u7ebf\uff0c\u4e3a\u63a7\u5236\u7ebf\uff0c\u5176\u4e2dmicro usb\u53e3\u4e0eswitch\u7684control\u63a5\u53e3\u8fde\u63a5\uff0cUSB-A\u63a5\u53e3\u4e0eKVM\u7684USB\u53e3\u8fde\u63a5\u3002 \u4fa7\u9762\u63a5\u53e3\u793a\u610f\u56fe \u8bbe\u5907\u8fde\u63a5\u793a\u610f\u56fe \u8f6f\u4ef6\u914d\u7f6e !!! info \"\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM\u8f6f\u4ef6\uff0c\u5728BliKVM\u542f\u52a8\u524d\u5148\u628aswitch\u901a\u7535\u5e76\u63a5\u597d\u7ebf\uff0c\u901a\u8fc7\u7ec8\u7aef\u786e\u8ba4switch\u63d2\u5165BliKVM\u540e\uff0c\u8bc6\u522b\u5230\u7684\u8bbe\u5907\u63cf\u8ff0\u7b26\u540d\u79f0\uff0c\u5982 /dev/ttyUSB0 ,\u7136\u540e\u7f16\u8f91 /usr/bin/blikvm/package.json \u4e2d\u7684 switch_handle \u5b57\u6bb5\uff0c\u5c06switch_enable\u8d4b\u503c\u4e3a1, switch_path\u8d4b\u503c\u4e3a /dev/ttyUSB0 \uff0c\u7136\u540e\u91cd\u542fBliKVM\u5373\u53ef\u3002 \u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u5148\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u7cfb\u7edf\u53d8\u4e3a\u53ef\u8bfb\u5199\u7cfb\u7edf\u3002\u7f16\u8f91\u914d\u7f6e\u6587\u4ef6\u53ef\u4ee5\u53c2\u8003\u4e0b\u547d\u4ee4: sudo vim /usr/bin/blikvm/package.json \u70b9\u51fb\u5de6\u4e0b\u89d2\u7684MORE\uff0c\u627e\u5230BliKVM switch\u8fd9\u4e00\u680f\uff0c\u8fdb\u884c\u5207\u6362\u9009\u62e9\u5373\u53ef\u3002\u6ce8\u610f\u5bf9\u5e94\u901a\u9053\u84dd\u8272\u5c0f\u70b9\u95ea\u52a8\u8868\u793a\u8bc6\u522b\u5230\u4e86switch\u63d2\u5165\uff0c\u5e76\u4e14\u6b63\u5904\u4e8e\u5f53\u524d\u901a\u9053\uff0c\u82e5\u65e0\u84dd\u8272\u5c0f\u70b9\u5219\u8868\u793a\u672a\u8bc6\u522b\u5230switch\u63d2\u5165\u3002\" \u82e5\u60a8\u4f7f\u7528\u7684PiKVM\u8f6f\u4ef6\uff0c\u8bf7\u6309\u7167\u4e0b\u9762\u7684\u8bf4\u660e\u8fdb\u884c\u914d\u7f6e \u901a\u8fc7SSH\u767b\u9646PiKVM\uff0c\u7528\u6237\u540d\u548c\u5bc6\u7801\u5747\u4e3aroot; \u7ec8\u7aef\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u7cfb\u7edf\u6539\u4e3a\u53ef\u8bfb\u5199\u7cfb\u7edf; \u7f16\u8f91 /etc/kvmd/override.yaml \u6b64\u6587\u4ef6\uff0c\u4f7f\u6539\u6587\u4ef6\u5305\u542b\u4e0b\u9762\u7684\u5185\u5bb9\uff0c\u5373\u5728\u539f\u6709\u5185\u5bb9\u540e\u8ffd\u52a0. kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] !!! warning \"\u4e0a\u8ff0\u914d\u7f6e\u57fa\u4e8e2022 pikvm\u56fe\u50cf\u3002\u5982\u679c\u60a8\u4f7f\u7528\u7684\u662f\u6700\u65b0\u7684pikvm\u6620\u50cf\u6216\u6700\u65b0\u7684\u8f6f\u4ef6\u7248\u672c\uff0c\u8bf7\u7f16\u8f91\u6587\u4ef6/etc/kvmd/override.yaml\u5e76\u6dfb\u52a0\u884c\uff1aprotocol:2\uff0c\u4f8b\u5b50\u5982\u4e0b:\" kvmd: gpio: drivers: hk: type: xh_hk4401 protocol: 2 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk ... \u7ec8\u7aef\u4f7f\u7528 ro \u547d\u4ee4\u5c06\u7cfb\u7edf\u91cd\u65b0\u8bbe\u7f6e\u4e3a\u53ea\u8bfb\u7cfb\u7edf\uff1b \u7ec8\u7aef\u4f7f\u7528 systemctl restart kvmd \u91cd\u542f\u670d\u52a1\u3002 \u8fdb\u5165PiKVM web\u754c\u9762\uff0c\u5e76\u5355\u51fb\u201cGPIO\u201d\u83dc\u5355\u3002\u60a8\u5e94\u8be5\u770b\u52304\u4e2a\u8f93\u5165\uff0c\u5176\u4e2d\u4e00\u4e2a\u8f93\u5165\u6709\u4e00\u4e2a\u7eff\u8272\u5706\u5708\uff0c\u8868\u793a\u5f53\u524d\u5df2\u9009\u4e2d\u3002\u5355\u51fb\u5176\u4ed6\u8f93\u5165\u4ee5\u66f4\u6539\u9009\u5b9a\u7684\u4e3b\u673a\u3002 \u63a7\u5236\u534f\u8bae \u82e5\u60a8\u5e0c\u671b\u5c06blicube\u7684switch\u7528\u5728\u5176\u5b83\u5e73\u53f0\u4e0a\uff0c\u8bf7\u53c2\u8003\u4e0b\u9762\u7684\u534f\u8bae \u901a\u4fe1\u6ce2\u7279\u7387\u4e3a19200 \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW1\\r\\nG01gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW2\\r\\nG02gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW3\\r\\nG03gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW4\\r\\nG04gA switch\u8fd4\u56de\u5f53\u524d\u6240\u5728\u901a\u9053\u6d88\u606f\u4e3a: G01gA , G02gA , G03gA , G04gA \u53d1\u8d27\u6e05\u5355 \u4ea7\u54c1 \u6570\u91cf \u5907\u6ce8\uff5c KVM Switch\u5207\u6362\u5668\uff084\u901a\u9053) 1 110mm * 60mm * 33mm USB\u684c\u9762\u63a7\u5236\u5668 1 USB\u6570\u636e\u7ebf 4 \u957f\u5ea6: 1.2m HDMI\uff08\u6807\u51c6\u63a5\u5934\uff09\u7ebf 4 \u957f\u5ea6: 1.5m USB\u7535\u6e90\u7ebf 1 \u957f\u5ea6: 0.8m KVM USB\u7ebf 1 \u957f\u5ea6: 1.5m USB\u684c\u9762\u63a7\u5236\u7ebf 1 \u957f\u5ea6: 1m","title":"switchV1\u5207\u6362\u5668\u624b\u518c"},{"location":"bliswitch-v1-guide/#blikvm-switch-v1-kvm","text":"BliKVM-Switch-V1.0\u5b9e\u9645\u4f7f\u7528\u548c\u6d4b\u8bd5\u89c6\u9891\uff0c\u652f\u6301BliKVM\u548cPiKVM","title":"BliKVM switch v1 KVM\u5207\u6362\u5668\u624b\u518c"},{"location":"bliswitch-v1-guide/#_1","text":"BliKVM-Switch-V1.0\u4e3a\u56db\u901a\u9053HDMI+USB\u5207\u6362\u5668\uff0c\u652f\u6301\u673a\u5668\u6309\u952e\u5207\u6362\uff0c\u684c\u9762\u63a7\u5236\u5668\u5207\u6362\uff0cKVM\u8fdc\u7a0b\u5207\u6362\uff0c3\u79cd\u5207\u6362\u6a21\u5f0f\u3002\u5207\u6362\u5668\u672c\u8eab\u6700\u9ad8\u652f\u63014K@60HZ\u7684\u8f93\u5165\uff0c\u5373\u63d2\u5373\u7528\uff0c\u514d\u9a71\u52a8\u3002 BliKVM-Switch-V1.0\u4f7f\u7528\u548cXH-HK4401\u76f8\u540c\u7684\u786c\u4ef6\u65b9\u6848,AG7210 HDMI\u5207\u6362\u82af\u7247\u6700\u9ad8\u652f\u6301\u52304K@60Hz\uff0cCH444G USB\u5207\u6362\u82af\u7247\u652f\u6301USB2.0\u3002\u4e0d\u540c\u7684\u662fBliKVM-Switch-V1.0\u914d\u5907\u6709KVM USB cable,\u53ef\u4ee5\u901a\u8fc7KVM USB cable\u8fde\u63a5BliKVM-Switch-V1.0,\u5b9e\u73b0\u5bf9KVM\u7aef\u53e3\u7684\u9009\u62e9\u3002BliKVM-Switch-V1.0\u9002\u914dBliKVM\u548cPiKVM\u3002 \u6ce8\u610f\u4e8b\u9879 switch\u53ef\u4ee5\u76f4\u63a5\u4ece\u8f93\u5165\u7535\u8111\u7684USB\u53d6\u7535\uff0c\u5373\u4e00\u822c\u4e0d\u9700\u8981\u7ed9switch\u4f9b\u7535\uff0c\u5373\u53ef\u6b63\u5e38\u5de5\u4f5c\uff1b \u82e5\u88ab\u63a7\u7535\u8111\u7684USB\u4f9b\u7535\u65e0\u6cd5\u4f7fswitch\u5de5\u4f5c\uff0c\u53ef\u4ee5\u5bf9switch\u8fdb\u884c\u5355\u72ec\u4f9b\u7535\u4f7f\u7528\uff1b switch\u5957\u88c5\u53ea\u63d0\u4f9b\u4e86USB\u7535\u6e90\u7ebf\uff0c\u5e76\u6ca1\u6709\u63d0\u4f9b\u7535\u6e90\u9002\u914d\u5668\uff0c\u9700\u8981\u5ba2\u6237\u81ea\u884c\u914d\u7f6e\u7535\u6e90\u9002\u914d\u5668\uff085V\uff09\uff1b \u684c\u9762\u63a7\u5236\u5668 \u53ef\u4ee5\u901a\u8fc7USB\u7535\u7f06\u63a7\u5236\u5207\u6362\uff0c\u5bf9\u4e8e\u4e0d\u4f7f\u7528KVM\u7684\u5ba2\u6237\uff0c\u5f53\u60a8\u5728\u8bbe\u5907\u65c1\u8fb9\u65f6\uff0c\u8fd9\u662f\u9664\u4f7f\u7528switch\u8bbe\u5907\u4e0a\u6309\u94ae\u5207\u6362\u4e4b\u5916\u7684\u53e6\u4e00\u79cd\u5207\u6362\u65b9\u5f0f\uff1b HDMI\u8f93\u5165\u6700\u9ad8\u652f\u6301 4096x2160/60Hz \uff1b 4K 60Hz\u7684HDMI\u8f93\u5165, \u529f\u7387\u5927\u6982\u662f200mW;","title":"\u7b80\u4ecb"},{"location":"bliswitch-v1-guide/#_2","text":"\u8fd9\u91cc\u9700\u8981\u4e24\u6839USB\u7ebf\uff0c\u8fde\u63a5switch\u548ckvm\u786c\u4ef6\uff0c\u4e00\u6839\u7528\u4e8e\u4f20\u8f93\u63a7\u5236\u5207\u6362\u901a\u9053\u4fe1\u606f\uff0c\u4e00\u6839\u7528\u4e8e\u4f20\u8f93\u9f20\u6807\u952e\u76d8\u6570\u636e\uff0c\u5177\u4f53\u8fde\u63a5\u53ef\u4ee5\u53c2\u8003\u9762\u8bf4\u660e\u3002 \u6b63\u9762\u548c\u53cd\u9762\u63a5\u53e3\u793a\u610f\u56fe\uff0c\u53f3\u4fa7\u56fe\u4e2d\u7684control\u63a5\u53e3\u5373\u4e3a\u8fdc\u7a0b\u63a7\u5236\u63a5\u53e3, \u4e00\u5934\u4e3aUSB-A\uff0c\u53e6\u4e00\u5934\u4e3amicro usb\u5e76\u4e14\u6807\u7b7e\u5e26\u6709kvm\u5b57\u6837\u7684\u7ebf\uff0c\u4e3a\u63a7\u5236\u7ebf\uff0c\u5176\u4e2dmicro usb\u53e3\u4e0eswitch\u7684control\u63a5\u53e3\u8fde\u63a5\uff0cUSB-A\u63a5\u53e3\u4e0eKVM\u7684USB\u53e3\u8fde\u63a5\u3002 \u4fa7\u9762\u63a5\u53e3\u793a\u610f\u56fe \u8bbe\u5907\u8fde\u63a5\u793a\u610f\u56fe","title":"\u63a5\u53e3\u793a\u610f\u56fe"},{"location":"bliswitch-v1-guide/#_3","text":"!!! info \"\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM\u8f6f\u4ef6\uff0c\u5728BliKVM\u542f\u52a8\u524d\u5148\u628aswitch\u901a\u7535\u5e76\u63a5\u597d\u7ebf\uff0c\u901a\u8fc7\u7ec8\u7aef\u786e\u8ba4switch\u63d2\u5165BliKVM\u540e\uff0c\u8bc6\u522b\u5230\u7684\u8bbe\u5907\u63cf\u8ff0\u7b26\u540d\u79f0\uff0c\u5982 /dev/ttyUSB0 ,\u7136\u540e\u7f16\u8f91 /usr/bin/blikvm/package.json \u4e2d\u7684 switch_handle \u5b57\u6bb5\uff0c\u5c06switch_enable\u8d4b\u503c\u4e3a1, switch_path\u8d4b\u503c\u4e3a /dev/ttyUSB0 \uff0c\u7136\u540e\u91cd\u542fBliKVM\u5373\u53ef\u3002 \u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u5148\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u7cfb\u7edf\u53d8\u4e3a\u53ef\u8bfb\u5199\u7cfb\u7edf\u3002\u7f16\u8f91\u914d\u7f6e\u6587\u4ef6\u53ef\u4ee5\u53c2\u8003\u4e0b\u547d\u4ee4: sudo vim /usr/bin/blikvm/package.json \u70b9\u51fb\u5de6\u4e0b\u89d2\u7684MORE\uff0c\u627e\u5230BliKVM switch\u8fd9\u4e00\u680f\uff0c\u8fdb\u884c\u5207\u6362\u9009\u62e9\u5373\u53ef\u3002\u6ce8\u610f\u5bf9\u5e94\u901a\u9053\u84dd\u8272\u5c0f\u70b9\u95ea\u52a8\u8868\u793a\u8bc6\u522b\u5230\u4e86switch\u63d2\u5165\uff0c\u5e76\u4e14\u6b63\u5904\u4e8e\u5f53\u524d\u901a\u9053\uff0c\u82e5\u65e0\u84dd\u8272\u5c0f\u70b9\u5219\u8868\u793a\u672a\u8bc6\u522b\u5230switch\u63d2\u5165\u3002\" \u82e5\u60a8\u4f7f\u7528\u7684PiKVM\u8f6f\u4ef6\uff0c\u8bf7\u6309\u7167\u4e0b\u9762\u7684\u8bf4\u660e\u8fdb\u884c\u914d\u7f6e \u901a\u8fc7SSH\u767b\u9646PiKVM\uff0c\u7528\u6237\u540d\u548c\u5bc6\u7801\u5747\u4e3aroot; \u7ec8\u7aef\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u7cfb\u7edf\u6539\u4e3a\u53ef\u8bfb\u5199\u7cfb\u7edf; \u7f16\u8f91 /etc/kvmd/override.yaml \u6b64\u6587\u4ef6\uff0c\u4f7f\u6539\u6587\u4ef6\u5305\u542b\u4e0b\u9762\u7684\u5185\u5bb9\uff0c\u5373\u5728\u539f\u6709\u5185\u5bb9\u540e\u8ffd\u52a0. kvmd: gpio: drivers: hk: type: xh_hk4401 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk pin: 0 mode: input ch1_led: driver: hk pin: 1 mode: input ch2_led: driver: hk pin: 2 mode: input ch3_led: driver: hk pin: 3 mode: input ch0_button: driver: hk pin: 0 mode: output switch: false ch1_button: driver: hk pin: 1 mode: output switch: false ch2_button: driver: hk pin: 2 mode: output switch: false ch3_button: driver: hk pin: 3 mode: output switch: false view: table: - [\"#Input 1\", ch0_led, ch0_button] - [\"#Input 2\", ch1_led, ch1_button] - [\"#Input 3\", ch2_led, ch2_button] - [\"#Input 4\", ch3_led, ch3_button] !!! warning \"\u4e0a\u8ff0\u914d\u7f6e\u57fa\u4e8e2022 pikvm\u56fe\u50cf\u3002\u5982\u679c\u60a8\u4f7f\u7528\u7684\u662f\u6700\u65b0\u7684pikvm\u6620\u50cf\u6216\u6700\u65b0\u7684\u8f6f\u4ef6\u7248\u672c\uff0c\u8bf7\u7f16\u8f91\u6587\u4ef6/etc/kvmd/override.yaml\u5e76\u6dfb\u52a0\u884c\uff1aprotocol:2\uff0c\u4f8b\u5b50\u5982\u4e0b:\" kvmd: gpio: drivers: hk: type: xh_hk4401 protocol: 2 device: /dev/ttyUSB0 scheme: ch0_led: driver: hk ... \u7ec8\u7aef\u4f7f\u7528 ro \u547d\u4ee4\u5c06\u7cfb\u7edf\u91cd\u65b0\u8bbe\u7f6e\u4e3a\u53ea\u8bfb\u7cfb\u7edf\uff1b \u7ec8\u7aef\u4f7f\u7528 systemctl restart kvmd \u91cd\u542f\u670d\u52a1\u3002 \u8fdb\u5165PiKVM web\u754c\u9762\uff0c\u5e76\u5355\u51fb\u201cGPIO\u201d\u83dc\u5355\u3002\u60a8\u5e94\u8be5\u770b\u52304\u4e2a\u8f93\u5165\uff0c\u5176\u4e2d\u4e00\u4e2a\u8f93\u5165\u6709\u4e00\u4e2a\u7eff\u8272\u5706\u5708\uff0c\u8868\u793a\u5f53\u524d\u5df2\u9009\u4e2d\u3002\u5355\u51fb\u5176\u4ed6\u8f93\u5165\u4ee5\u66f4\u6539\u9009\u5b9a\u7684\u4e3b\u673a\u3002","title":"\u8f6f\u4ef6\u914d\u7f6e"},{"location":"bliswitch-v1-guide/#_4","text":"\u82e5\u60a8\u5e0c\u671b\u5c06blicube\u7684switch\u7528\u5728\u5176\u5b83\u5e73\u53f0\u4e0a\uff0c\u8bf7\u53c2\u8003\u4e0b\u9762\u7684\u534f\u8bae \u901a\u4fe1\u6ce2\u7279\u7387\u4e3a19200 \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW1\\r\\nG01gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW2\\r\\nG02gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW3\\r\\nG03gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3a SW4\\r\\nG04gA switch\u8fd4\u56de\u5f53\u524d\u6240\u5728\u901a\u9053\u6d88\u606f\u4e3a: G01gA , G02gA , G03gA , G04gA","title":"\u63a7\u5236\u534f\u8bae"},{"location":"bliswitch-v1-guide/#_5","text":"\u4ea7\u54c1 \u6570\u91cf \u5907\u6ce8\uff5c KVM Switch\u5207\u6362\u5668\uff084\u901a\u9053) 1 110mm * 60mm * 33mm USB\u684c\u9762\u63a7\u5236\u5668 1 USB\u6570\u636e\u7ebf 4 \u957f\u5ea6: 1.2m HDMI\uff08\u6807\u51c6\u63a5\u5934\uff09\u7ebf 4 \u957f\u5ea6: 1.5m USB\u7535\u6e90\u7ebf 1 \u957f\u5ea6: 0.8m KVM USB\u7ebf 1 \u957f\u5ea6: 1.5m USB\u684c\u9762\u63a7\u5236\u7ebf 1 \u957f\u5ea6: 1m","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"bliswitch-v2-guide/","text":"8\u53e3KVM+ATX\u5207\u6362\u5668 BliSwitch v2 BliSwitch v2\u662f\u4e00\u6b3e8\u901a\u9053KVM+ATX\u5207\u6362\u5668\uff0c\u4f7f8\u53f0\u4e3b\u673a\u5171\u4eab\u4e00\u5957\u952e\u76d8\u3001\u9f20\u6807\u548cHDMI\u5c4f\u5e55\uff0c\u4e14\u5b9e\u73b0\u5bf98\u53f0\u4e3b\u673a\u7684\u5f00\u5173\u673a\u63a7\u5236\u3002 \u7aef\u53e3\u5b9a\u4e49 \u4ea7\u54c1\u53c2\u6570 \u54c1\u724c BLI \u54c1\u540d 8\u53e3KVM+ATX\u5207\u6362\u5668 \u578b\u53f7 BliSwitch v2 \u529f\u80fd \u516b\u53f0\u4e3b\u673a\u5171\u4eab\u4e00\u5957\u952e\u9f20\u548c\u663e\u793a\u5668\uff0c8\u53f0\u4e3b\u673a\u5f00\u5173\u673a\u63a7\u5236 \u6750\u8d28 \u5168\u91d1\u5c5e \u5206\u8fa8\u7387 1080P60Hz \u5207\u6362\u65b9\u5f0f \u6309\u952e\u5207\u6362 \u6216 USB\u63a7\u5236\u6a21\u5757\u5207\u6362 \u4f9b\u7535 5V1A \u63a7\u5236\u534f\u8bae \u82e5\u60a8\u5e0c\u671b\u5c06blicube\u7684switch\u7528\u5728\u5176\u5b83\u5e73\u53f0\u4e0a\uff0c\u8bf7\u53c2\u8003\u4e0b\u9762\u7684\u534f\u8bae \u901a\u4fe1\u6ce2\u7279\u7387\u4e3a19200 \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW1\\r\\nG01gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW2\\r\\nG02gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW3\\r\\nG03gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW4\\r\\nG04gA \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW5\\r\\nG05gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW6\\r\\nG06gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW7\\r\\nG07gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW8\\r\\nG07gA switch\u8fd4\u56de\u5f53\u524d\u6240\u5728\u901a\u9053\u6d88\u606f\u4e3a:G01gA,G02gA,G03gA,G04gA,G05gA,G06gA,G07gA,G08gA \u8fde\u63a5\u53c2\u8003 \u5c3a\u5bf8 \u53d1\u8d27\u6e05\u5355 \u4ea7\u54c1 \u6570\u91cf \u5907\u6ce8\uff5c BliSwitch v4\u5207\u6362\u5668 1 \u6302\u8033 2 ATX\u7ebf \u516c\u5934 8 ATX\u7ebf \u6bcd\u5934 8 \u5168\u9ad8PCIe\u6321\u677f 8 \u534a\u9ad8PCIe\u6321\u677f 8 ATX\u677f 8 \u63a7\u5236\u7ebf 1 USB\u7ebf 1 \u80f6\u57ab 4 M2.5x5 \u6c89\u5934\u87ba\u9489 10","title":"switchV2\u5207\u6362\u5668\u624b\u518c"},{"location":"bliswitch-v2-guide/#8kvmatx-bliswitch-v2","text":"BliSwitch v2\u662f\u4e00\u6b3e8\u901a\u9053KVM+ATX\u5207\u6362\u5668\uff0c\u4f7f8\u53f0\u4e3b\u673a\u5171\u4eab\u4e00\u5957\u952e\u76d8\u3001\u9f20\u6807\u548cHDMI\u5c4f\u5e55\uff0c\u4e14\u5b9e\u73b0\u5bf98\u53f0\u4e3b\u673a\u7684\u5f00\u5173\u673a\u63a7\u5236\u3002","title":"8\u53e3KVM+ATX\u5207\u6362\u5668 BliSwitch v2"},{"location":"bliswitch-v2-guide/#_1","text":"","title":"\u7aef\u53e3\u5b9a\u4e49"},{"location":"bliswitch-v2-guide/#_2","text":"\u54c1\u724c BLI \u54c1\u540d 8\u53e3KVM+ATX\u5207\u6362\u5668 \u578b\u53f7 BliSwitch v2 \u529f\u80fd \u516b\u53f0\u4e3b\u673a\u5171\u4eab\u4e00\u5957\u952e\u9f20\u548c\u663e\u793a\u5668\uff0c8\u53f0\u4e3b\u673a\u5f00\u5173\u673a\u63a7\u5236 \u6750\u8d28 \u5168\u91d1\u5c5e \u5206\u8fa8\u7387 1080P60Hz \u5207\u6362\u65b9\u5f0f \u6309\u952e\u5207\u6362 \u6216 USB\u63a7\u5236\u6a21\u5757\u5207\u6362 \u4f9b\u7535 5V1A","title":"\u4ea7\u54c1\u53c2\u6570"},{"location":"bliswitch-v2-guide/#_3","text":"\u82e5\u60a8\u5e0c\u671b\u5c06blicube\u7684switch\u7528\u5728\u5176\u5b83\u5e73\u53f0\u4e0a\uff0c\u8bf7\u53c2\u8003\u4e0b\u9762\u7684\u534f\u8bae \u901a\u4fe1\u6ce2\u7279\u7387\u4e3a19200 \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW1\\r\\nG01gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW2\\r\\nG02gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW3\\r\\nG03gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW4\\r\\nG04gA \u5207\u6362\u52301\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW5\\r\\nG05gA \u5207\u6362\u52302\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW6\\r\\nG06gA \u5207\u6362\u52303\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW7\\r\\nG07gA \u5207\u6362\u52304\u901a\u9053\u53d1\u9001\u7ed9switch\u7684\u6d88\u606f\u4e3aSW8\\r\\nG07gA switch\u8fd4\u56de\u5f53\u524d\u6240\u5728\u901a\u9053\u6d88\u606f\u4e3a:G01gA,G02gA,G03gA,G04gA,G05gA,G06gA,G07gA,G08gA","title":"\u63a7\u5236\u534f\u8bae"},{"location":"bliswitch-v2-guide/#_4","text":"","title":"\u8fde\u63a5\u53c2\u8003"},{"location":"bliswitch-v2-guide/#_5","text":"","title":"\u5c3a\u5bf8"},{"location":"bliswitch-v2-guide/#_6","text":"\u4ea7\u54c1 \u6570\u91cf \u5907\u6ce8\uff5c BliSwitch v4\u5207\u6362\u5668 1 \u6302\u8033 2 ATX\u7ebf \u516c\u5934 8 ATX\u7ebf \u6bcd\u5934 8 \u5168\u9ad8PCIe\u6321\u677f 8 \u534a\u9ad8PCIe\u6321\u677f 8 ATX\u677f 8 \u63a7\u5236\u7ebf 1 USB\u7ebf 1 \u80f6\u57ab 4 M2.5x5 \u6c89\u5934\u87ba\u9489 10","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"dev-v4/","text":"\u9700\u6267\u884c\u4e0b\u9762\u547d\u4ee4\uff0c\u5426\u5219apt-get update \u548c apt-get upgrade\u540e\u955c\u50cf\u4f1a\u65e0\u6cd5\u542f\u52a8 apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64","title":"Dev v4"},{"location":"dev-v4/#apt-get-update-apt-get-upgrade","text":"apt-mark hold linux-dtb-edge-sunxi64 linux-image-edge-sunxi64","title":"\u9700\u6267\u884c\u4e0b\u9762\u547d\u4ee4\uff0c\u5426\u5219apt-get update \u548c apt-get upgrade\u540e\u955c\u50cf\u4f1a\u65e0\u6cd5\u542f\u52a8"},{"location":"dev_api/","text":"API \u7533\u660e: \u6b64API\u4e3a\u5b9e\u9a8c\u6027\u7684\uff0c\u4efb\u4f55\u65f6\u5019\u90fd\u6709\u53ef\u80fd\u88ab\u6539\u53d8!\u6b64\u6587\u6863\u53ea\u5728v1.4.0\u548c\u4e4b\u524d\u7248\u672c\u6709\u6548\uff0c\u5373\u5c06\u66f4\u65b0. \u6b64\u6587\u6863\u4e3aBLIKVM OS\u7684http API\u5f00\u53d1\u624b\u518c\uff0c\u82e5\u60a8\u6709\u65b0\u7684API\u9700\u6c42\u4e0d\u5728\u6b64\u6587\u6863\u4e2d\uff0c\u53ef\u4ee5\u5728github\u4e2d\u63d0pr\u83b7\u5f97\u652f\u6301\u3002\u8bf7\u6c42URL\u4e2d\u7684kvmip\u9700\u6839\u636e\u4f60kvm\u7684ip\u5b9e\u9645\u66ff\u6362\u3002 \u767b\u5f55\u8ba4\u8bc1 \u6b64API\u7528\u4e8e\u7528\u6237\u767b\u5f55\uff0c\u5e76\u8fd4\u56de\u8bbf\u95ee\u4ee4\u724c\u3002\u540e\u7eed\u6709\u7684api\u5747\u9700\u8981token\u4ee4\u724c\u3002 \u8bf7\u6c42URL: http://kvmip/login_api \u8bf7\u6c42\u65b9\u6cd5: GET \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f,\u5982: { \"username\": \"admin\", \"password\": \"admin\" } \u54cd\u5e94\u7ed3\u679c\u5982\u4e0b\uff0c\u82e5status\u4e0d\u4e3a1\uff0c\u5219\u8ba4\u8bc1\u5931\u8d25\u3002 { \"status\": 1, \"info\": \"login success\", \"data\": { \"token\": \"2sscdada6a97a774fcd4714c\" } } ATX\u5f00\u5173\u673a \u6b64API\u7528\u4e8e\u63a7\u5236\u76ee\u6807\u8bbe\u5907\u5f00\u5173\u673a\uff0c\u548c\u91cd\u542f\u3002 - \u8bf7\u6c42URL: http://kvmip/atx - \u8bf7\u6c42\u65b9\u6cd5: POST - \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f: 1. \u5176\u4e2dcmd\u4e3a128\u4e3a\u5f00\u5173\u673a(\u5373\u5f00\u673a\u7684\u60c5\u51b5\u4e0b\u6a21\u62df\u7684\u4e3a\u77ed\u6309\u5173\u673a\uff0c\u5173\u673a\u7684\u60c5\u51b5\u4e0b\u4e3a\u77ed\u6309\u5f00\u673a); 2. 192\u4e3a\u5f3a\u5236\u5173\u673a(\u6a21\u62df\u957f\u6309\u5f3a\u5236\u5173\u673a); 3. cmd\u4e3a8\u8868\u793a\u91cd\u542f\u3002\u5982: { \"cmd\": 128 } \u54cd\u5e94\u7ed3\u679c\u5982\u4e0b\uff0c\u82e5status\u4e0d\u4e3a1\uff0c\u5219\u5931\u8d25\u3002 { \"status\": 1, \"info\": \"success\", } mjepg\u56fe\u50cf \u6b64API\u7528\u4e8e\u5728\u56fe\u50cf\u6a21\u5f0f\u4e3amjepg\u7684\u6a21\u5f0f\u4e0b\uff0c\u62ff\u5230mjpeg\u7684\u89c6\u5c4f\u6d41\u3002 - \u8bf7\u6c42URL: http://kvmip:8008/stream \uff0c\u6b64API\u7528\u4e8e\u5728\u56fe\u50cf\u6a21\u5f0f\u4e3amjepg\u7684\u6a21\u5f0f\u4e0b\uff0c\u62ff\u5230mjpeg\u7684\u4e00\u5e27\u56fe\u7247\u3002 - \u8bf7\u6c42URL: http://kvmip:8008/snapshot - \u8bf7\u6c42\u65b9\u6cd5: GET \u952e\u76d8 \u952e\u76d8\u5177\u4f53\u7f16\u7801\u53ef\u53c2\u8003 \"KeyA\"=> 4, \"KeyB\"=> 5, \"KeyC\"=> 6, \"KeyD\"=> 7, \"KeyE\"=> 8, \"KeyF\"=> 9, \"KeyG\"=> 10, \"KeyH\"=> 11, \"KeyI\"=> 12, \"KeyJ\"=> 13, \"KeyK\"=> 14, \"KeyL\"=> 15, \"KeyM\"=> 16, \"KeyN\"=> 17, \"KeyO\"=> 18, \"KeyP\"=> 19, \"KeyQ\"=> 20, \"KeyR\"=> 21, \"KeyS\"=> 22, \"KeyT\"=> 23, \"KeyU\"=> 24, \"KeyV\"=> 25, \"KeyW\"=> 26, \"KeyX\"=> 27, \"KeyY\"=> 28, \"KeyZ\"=> 29, \"Digit1\"=> 30, \"Digit2\"=> 31, \"Digit3\"=> 32, \"Digit4\"=> 33, \"Digit5\"=> 34, \"Digit6\"=> 35, \"Digit7\"=> 36, \"Digit8\"=> 37, \"Digit9\"=> 38, \"Digit0\"=> 39, \"Enter\"=> 40, \"Escape\"=> 41, \"Backspace\"=> 42, \"Tab\"=> 43, \"Space\"=> 44, \"Minus\"=> 45, \"Equal\"=> 46, \"BracketLeft\"=> 47, \"BracketRight\"=> 48, \"Backslash\"=> 49, \"Semicolon\"=> 51, \"Quote\"=> 52, \"Backquote\"=> 53, \"Comma\"=> 54, \"Period\"=> 55, \"Slash\"=> 56, \"CapsLock\"=> 57, \"F1\"=> 58, \"F2\"=> 59, \"F3\"=> 60, \"F4\"=> 61, \"F5\"=> 62, \"F6\"=> 63, \"F7\"=> 64, \"F8\"=> 65, \"F9\"=> 66, \"F10\"=> 67, \"F11\"=> 68, \"F12\"=> 69, \"PrtSc\"=> 70, \"ScrollLock\"=> 71, \"Pause\"=> 72, \"Insert\"=> 73, \"Home\"=> 74, \"PageUp\"=> 75, \"Delete\"=> 76, \"End\"=> 77, \"PageDown\"=> 78, \"ArrowRight\"=> 79, \"ArrowLeft\"=> 80, \"ArrowDown\"=> 81, \"ArrowUp\"=> 82, \"NumLock\"=> 83, \"NumpadDivide\"=> 84, \"NumpadMultiply\"=> 85, \"NumpadSubtract\"=> 86, \"NumpadAdd\"=> 87, \"NumpadEnter\"=> 88, \"Numpad1\"=> 89, \"Numpad2\"=> 90, \"Numpad3\"=> 91, \"Numpad4\"=> 92, \"Numpad5\"=> 93, \"Numpad6\"=> 94, \"Numpad7\"=> 95, \"Numpad8\"=> 96, \"Numpad9\"=> 97, \"Numpad0\"=> 98, \"NumpadDecimal\"=> 99 \u8bf7\u6c42URL: http://kvmip/keyboard \u8bf7\u6c42\u65b9\u6cd5: GET \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f,keycodes\u4e3a\u5b57\u7b26\u4e32\u6570\u7ec4\uff0c\u652f\u6301\u4e00\u6b21\u8f93\u5165\u591a\u4e2a,\u5982: { \"keycodes\": [\"Digit1\"] } \u54cd\u5e94\u7ed3\u679c\u5982: { \"status\": 1, \"info\": \"key input success\", \"data\": [] }","title":"http API"},{"location":"dev_api/#api","text":"\u7533\u660e: \u6b64API\u4e3a\u5b9e\u9a8c\u6027\u7684\uff0c\u4efb\u4f55\u65f6\u5019\u90fd\u6709\u53ef\u80fd\u88ab\u6539\u53d8!\u6b64\u6587\u6863\u53ea\u5728v1.4.0\u548c\u4e4b\u524d\u7248\u672c\u6709\u6548\uff0c\u5373\u5c06\u66f4\u65b0. \u6b64\u6587\u6863\u4e3aBLIKVM OS\u7684http API\u5f00\u53d1\u624b\u518c\uff0c\u82e5\u60a8\u6709\u65b0\u7684API\u9700\u6c42\u4e0d\u5728\u6b64\u6587\u6863\u4e2d\uff0c\u53ef\u4ee5\u5728github\u4e2d\u63d0pr\u83b7\u5f97\u652f\u6301\u3002\u8bf7\u6c42URL\u4e2d\u7684kvmip\u9700\u6839\u636e\u4f60kvm\u7684ip\u5b9e\u9645\u66ff\u6362\u3002","title":"API"},{"location":"dev_api/#_1","text":"\u6b64API\u7528\u4e8e\u7528\u6237\u767b\u5f55\uff0c\u5e76\u8fd4\u56de\u8bbf\u95ee\u4ee4\u724c\u3002\u540e\u7eed\u6709\u7684api\u5747\u9700\u8981token\u4ee4\u724c\u3002 \u8bf7\u6c42URL: http://kvmip/login_api \u8bf7\u6c42\u65b9\u6cd5: GET \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f,\u5982: { \"username\": \"admin\", \"password\": \"admin\" } \u54cd\u5e94\u7ed3\u679c\u5982\u4e0b\uff0c\u82e5status\u4e0d\u4e3a1\uff0c\u5219\u8ba4\u8bc1\u5931\u8d25\u3002 { \"status\": 1, \"info\": \"login success\", \"data\": { \"token\": \"2sscdada6a97a774fcd4714c\" } }","title":"\u767b\u5f55\u8ba4\u8bc1"},{"location":"dev_api/#atx","text":"\u6b64API\u7528\u4e8e\u63a7\u5236\u76ee\u6807\u8bbe\u5907\u5f00\u5173\u673a\uff0c\u548c\u91cd\u542f\u3002 - \u8bf7\u6c42URL: http://kvmip/atx - \u8bf7\u6c42\u65b9\u6cd5: POST - \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f: 1. \u5176\u4e2dcmd\u4e3a128\u4e3a\u5f00\u5173\u673a(\u5373\u5f00\u673a\u7684\u60c5\u51b5\u4e0b\u6a21\u62df\u7684\u4e3a\u77ed\u6309\u5173\u673a\uff0c\u5173\u673a\u7684\u60c5\u51b5\u4e0b\u4e3a\u77ed\u6309\u5f00\u673a); 2. 192\u4e3a\u5f3a\u5236\u5173\u673a(\u6a21\u62df\u957f\u6309\u5f3a\u5236\u5173\u673a); 3. cmd\u4e3a8\u8868\u793a\u91cd\u542f\u3002\u5982: { \"cmd\": 128 } \u54cd\u5e94\u7ed3\u679c\u5982\u4e0b\uff0c\u82e5status\u4e0d\u4e3a1\uff0c\u5219\u5931\u8d25\u3002 { \"status\": 1, \"info\": \"success\", }","title":"ATX\u5f00\u5173\u673a"},{"location":"dev_api/#mjepg","text":"\u6b64API\u7528\u4e8e\u5728\u56fe\u50cf\u6a21\u5f0f\u4e3amjepg\u7684\u6a21\u5f0f\u4e0b\uff0c\u62ff\u5230mjpeg\u7684\u89c6\u5c4f\u6d41\u3002 - \u8bf7\u6c42URL: http://kvmip:8008/stream \uff0c\u6b64API\u7528\u4e8e\u5728\u56fe\u50cf\u6a21\u5f0f\u4e3amjepg\u7684\u6a21\u5f0f\u4e0b\uff0c\u62ff\u5230mjpeg\u7684\u4e00\u5e27\u56fe\u7247\u3002 - \u8bf7\u6c42URL: http://kvmip:8008/snapshot - \u8bf7\u6c42\u65b9\u6cd5: GET","title":"mjepg\u56fe\u50cf"},{"location":"dev_api/#_2","text":"\u952e\u76d8\u5177\u4f53\u7f16\u7801\u53ef\u53c2\u8003 \"KeyA\"=> 4, \"KeyB\"=> 5, \"KeyC\"=> 6, \"KeyD\"=> 7, \"KeyE\"=> 8, \"KeyF\"=> 9, \"KeyG\"=> 10, \"KeyH\"=> 11, \"KeyI\"=> 12, \"KeyJ\"=> 13, \"KeyK\"=> 14, \"KeyL\"=> 15, \"KeyM\"=> 16, \"KeyN\"=> 17, \"KeyO\"=> 18, \"KeyP\"=> 19, \"KeyQ\"=> 20, \"KeyR\"=> 21, \"KeyS\"=> 22, \"KeyT\"=> 23, \"KeyU\"=> 24, \"KeyV\"=> 25, \"KeyW\"=> 26, \"KeyX\"=> 27, \"KeyY\"=> 28, \"KeyZ\"=> 29, \"Digit1\"=> 30, \"Digit2\"=> 31, \"Digit3\"=> 32, \"Digit4\"=> 33, \"Digit5\"=> 34, \"Digit6\"=> 35, \"Digit7\"=> 36, \"Digit8\"=> 37, \"Digit9\"=> 38, \"Digit0\"=> 39, \"Enter\"=> 40, \"Escape\"=> 41, \"Backspace\"=> 42, \"Tab\"=> 43, \"Space\"=> 44, \"Minus\"=> 45, \"Equal\"=> 46, \"BracketLeft\"=> 47, \"BracketRight\"=> 48, \"Backslash\"=> 49, \"Semicolon\"=> 51, \"Quote\"=> 52, \"Backquote\"=> 53, \"Comma\"=> 54, \"Period\"=> 55, \"Slash\"=> 56, \"CapsLock\"=> 57, \"F1\"=> 58, \"F2\"=> 59, \"F3\"=> 60, \"F4\"=> 61, \"F5\"=> 62, \"F6\"=> 63, \"F7\"=> 64, \"F8\"=> 65, \"F9\"=> 66, \"F10\"=> 67, \"F11\"=> 68, \"F12\"=> 69, \"PrtSc\"=> 70, \"ScrollLock\"=> 71, \"Pause\"=> 72, \"Insert\"=> 73, \"Home\"=> 74, \"PageUp\"=> 75, \"Delete\"=> 76, \"End\"=> 77, \"PageDown\"=> 78, \"ArrowRight\"=> 79, \"ArrowLeft\"=> 80, \"ArrowDown\"=> 81, \"ArrowUp\"=> 82, \"NumLock\"=> 83, \"NumpadDivide\"=> 84, \"NumpadMultiply\"=> 85, \"NumpadSubtract\"=> 86, \"NumpadAdd\"=> 87, \"NumpadEnter\"=> 88, \"Numpad1\"=> 89, \"Numpad2\"=> 90, \"Numpad3\"=> 91, \"Numpad4\"=> 92, \"Numpad5\"=> 93, \"Numpad6\"=> 94, \"Numpad7\"=> 95, \"Numpad8\"=> 96, \"Numpad9\"=> 97, \"Numpad0\"=> 98, \"NumpadDecimal\"=> 99 \u8bf7\u6c42URL: http://kvmip/keyboard \u8bf7\u6c42\u65b9\u6cd5: GET \u8bf7\u6c42\u4f53: JSON \u683c\u5f0f,keycodes\u4e3a\u5b57\u7b26\u4e32\u6570\u7ec4\uff0c\u652f\u6301\u4e00\u6b21\u8f93\u5165\u591a\u4e2a,\u5982: { \"keycodes\": [\"Digit1\"] } \u54cd\u5e94\u7ed3\u679c\u5982: { \"status\": 1, \"info\": \"key input success\", \"data\": [] }","title":"\u952e\u76d8"},{"location":"edid/","text":"EDID EDID\u6587\u4ef6\u5728BliKVM\u4e2d\u7684\u4f5c\u7528\u662f\u544a\u8bc9\u88ab\u63a7\u8ba1\u7b97\u673a\u671f\u671b\u8f93\u51fa\u7684HDMI\u5206\u8fa8\u7387\uff0c\u5373\u5982\u4f55\u4f7f\u7528\u7684\u662f1080P60Hz\u7684EDID\uff0c\u82e5\u88ab\u63a7\u8ba1\u7b97\u673a\u652f\u6301\u8f93\u51fa\u6b64\u5206\u8fa8\u7387\uff0c\u88ab\u63a7\u8ba1\u7b97\u673a\u5c31\u4f1a\u63091080P60Hz\u8f93\u51fa\u3002\u53e6\u5916\u901a\u8fc7EDID\u8fd8\u53ef\u4ee5\u5c4f\u853d\u58f0\u97f3\uff0c\u4fee\u6539\u663e\u793a\u5668\u578b\u53f7\uff0c\u540d\u5b57\uff0c\u5382\u5546\u7b49\u4fe1\u606f\u3002\u901a\u5e38\u60c5\u51b5\u4e0b\uff0c\u60a8\u4e0d\u9700\u8981\u66f4\u6539\u5b83\uff0c\u4f46\u6709\u65f6\uff0c\u4f8b\u5982\u5bf9\u4e8e\u5947\u602a\u7684 UEFI/BIOS\uff0c\u53ef\u80fd\u9700\u8981\u66f4\u6539\u5b83\u3002 Note BliKVM v1 v2 v3\u4f7f\u7528\u7684\u4e3aCSI\u89c6\u9891\u91c7\u96c6\u65b9\u6848\uff0c\u652f\u6301EDID\u8bbe\u7f6e\uff0cv4\u4f7f\u7528\u7684\u662fUSB\u89c6\u9891\u91c7\u96c6\u65b9\u6848\uff0c\u4e0d\u652f\u6301EDID\u8bbe\u7f6e\uff1b \u5176\u4e2dv3 HAT\u53d7\u6811\u8393\u6d3e4B\u53ea\u67092\u901a\u9053CSI\u9650\u5236\uff0c\u6700\u9ad8\u53ea\u80fd\u91c7\u96c61080P50Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u56e0\u6b64\u82e5\u5bf9v3\u8bbe\u7f6e1080P60Hz\u7684EDID\uff0cv3\u4f1a\u65e0\u6cd5\u6355\u83b7\u5230\u56fe\u50cf\uff1b \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM OS\uff0c\u53ef\u4ee5\u53c2\u7167 \u6b64\u94fe\u63a5 \u8fdb\u884c\u4fee\u6539; \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM OS\uff0cEDID\u6587\u4ef6\u5728 /usr/bin/blikvm/edid.txt ,\u6253\u5f00\u6b64\u6587\u4ef6\uff0c\u66ff\u6362\u4e0b\u9762\u4f60\u60f3\u8981\u5206\u8fa8\u7387\u7684EDID\u6587\u4ef6\u5373\u53ef\uff1b EDID \u4f8b\u5b50 1080P60Hz \u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u548cv2\u786c\u4ef6\u3002 1920x1080 60Hz, \u5e26\u97f3\u9891 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C EDID \u4f8b\u5b50 1080P50Hz \u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u3001v2\u3001v3\u786c\u4ef6\uff0c\u5c24\u5176\u5f53\u5e0c\u671bv3 HAT\u6355\u83b71080P\u5206\u8fa8\u7387\u65f6\u53ef\u4ee5\u4f7f\u7528\u5b83\u3002 1920x1080 50Hz, \u5e26\u97f3\u9891 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028 EDID \u4f8b\u5b50 720P60Hz \u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u3001v2\u3001v3\u786c\u4ef6\u3002 1280x720 60Hz, \u5e26\u97f3\u9891 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 \u81ea\u5b9a\u4e49EDID \u6700\u597d\u4f7f\u7528\u7b2c\u4e09\u65b9\u5de5\u5177\u6765\u7f16\u8f91EDID\uff0c\u6bd4\u5982\u63a8\u8350\u7684\u9ad8\u7ea7 AW EDID Editor \uff08Windows\u73af\u5883\u4e0b\u8fd0\u884c\u826f\u597d\uff0c\u4e5f\u53ef\u5728wine\u4e2d\u4f7f\u7528\uff09\u6216\u8005 wxEDID \u3002\u8fd9\u4e24\u4e2a\u7f16\u8f91\u5668\u90fd\u53ef\u4ee5\u5904\u7406\u4e8c\u8fdb\u5236\u7684EDID\u683c\u5f0f\u3002 \u4f7f\u7528\u8fd9\u4e9b\u5de5\u5177\uff0c\u60a8\u53ef\u4ee5\u50cf\u7f16\u8f91\u6587\u4ef6\u4e00\u6837\u4fee\u6539EDID\u4fe1\u606f\uff0c\u7c7b\u4f3c\u4e8e\u66f4\u6539\u8eab\u4efd\u8bc1\u4fe1\u606f\u3002\u901a\u8fc7\u7f16\u8f91EDID\uff0c\u60a8\u53ef\u4ee5\u8c03\u6574\u663e\u793a\u5668\u7684\u53c2\u6570\u548c\u7279\u6027\uff0c\u4ee5\u9002\u5e94\u4e0d\u540c\u7684\u4f7f\u7528\u9700\u6c42\uff0c\u4ece\u800c\u83b7\u5f97\u66f4\u597d\u7684\u663e\u793a\u6548\u679c\u3002","title":"HDMI EDID\u8bbe\u7f6e"},{"location":"edid/#edid","text":"EDID\u6587\u4ef6\u5728BliKVM\u4e2d\u7684\u4f5c\u7528\u662f\u544a\u8bc9\u88ab\u63a7\u8ba1\u7b97\u673a\u671f\u671b\u8f93\u51fa\u7684HDMI\u5206\u8fa8\u7387\uff0c\u5373\u5982\u4f55\u4f7f\u7528\u7684\u662f1080P60Hz\u7684EDID\uff0c\u82e5\u88ab\u63a7\u8ba1\u7b97\u673a\u652f\u6301\u8f93\u51fa\u6b64\u5206\u8fa8\u7387\uff0c\u88ab\u63a7\u8ba1\u7b97\u673a\u5c31\u4f1a\u63091080P60Hz\u8f93\u51fa\u3002\u53e6\u5916\u901a\u8fc7EDID\u8fd8\u53ef\u4ee5\u5c4f\u853d\u58f0\u97f3\uff0c\u4fee\u6539\u663e\u793a\u5668\u578b\u53f7\uff0c\u540d\u5b57\uff0c\u5382\u5546\u7b49\u4fe1\u606f\u3002\u901a\u5e38\u60c5\u51b5\u4e0b\uff0c\u60a8\u4e0d\u9700\u8981\u66f4\u6539\u5b83\uff0c\u4f46\u6709\u65f6\uff0c\u4f8b\u5982\u5bf9\u4e8e\u5947\u602a\u7684 UEFI/BIOS\uff0c\u53ef\u80fd\u9700\u8981\u66f4\u6539\u5b83\u3002 Note BliKVM v1 v2 v3\u4f7f\u7528\u7684\u4e3aCSI\u89c6\u9891\u91c7\u96c6\u65b9\u6848\uff0c\u652f\u6301EDID\u8bbe\u7f6e\uff0cv4\u4f7f\u7528\u7684\u662fUSB\u89c6\u9891\u91c7\u96c6\u65b9\u6848\uff0c\u4e0d\u652f\u6301EDID\u8bbe\u7f6e\uff1b \u5176\u4e2dv3 HAT\u53d7\u6811\u8393\u6d3e4B\u53ea\u67092\u901a\u9053CSI\u9650\u5236\uff0c\u6700\u9ad8\u53ea\u80fd\u91c7\u96c61080P50Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u56e0\u6b64\u82e5\u5bf9v3\u8bbe\u7f6e1080P60Hz\u7684EDID\uff0cv3\u4f1a\u65e0\u6cd5\u6355\u83b7\u5230\u56fe\u50cf\uff1b \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM OS\uff0c\u53ef\u4ee5\u53c2\u7167 \u6b64\u94fe\u63a5 \u8fdb\u884c\u4fee\u6539; \u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fBliKVM OS\uff0cEDID\u6587\u4ef6\u5728 /usr/bin/blikvm/edid.txt ,\u6253\u5f00\u6b64\u6587\u4ef6\uff0c\u66ff\u6362\u4e0b\u9762\u4f60\u60f3\u8981\u5206\u8fa8\u7387\u7684EDID\u6587\u4ef6\u5373\u53ef\uff1b","title":"EDID"},{"location":"edid/#edid-1080p60hz","text":"\u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u548cv2\u786c\u4ef6\u3002 1920x1080 60Hz, \u5e26\u97f3\u9891 00FFFFFFFFFFFF0031D8888800888888 1C150103800000780AEE91A3544C9926 0F50543FCD0001000101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0050 694B564D0A20202020202020000000FD 003B3D0F2E0F1E0A202020202020013C 02031E434F041303021211012021A23C 3D3E1F1066030C00300080E2007F8C0A D08A20E02D10103E9600C48E21000018 8C0AD08A20E02D10103E9600138E2100 00189729A0D051842230509816009A01 11000018000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000001C","title":"EDID \u4f8b\u5b50 1080P60Hz"},{"location":"edid/#edid-1080p50hz","text":"\u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u3001v2\u3001v3\u786c\u4ef6\uff0c\u5c24\u5176\u5f53\u5e0c\u671bv3 HAT\u6355\u83b71080P\u5206\u8fa8\u7387\u65f6\u53ef\u4ee5\u4f7f\u7528\u5b83\u3002 1920x1080 50Hz, \u5e26\u97f3\u9891 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a202020202020014f 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000028","title":"EDID \u4f8b\u5b50 1080P50Hz"},{"location":"edid/#edid-720p60hz","text":"\u4e0b\u9762\u7684edid\u9002\u7528\u4e8ev1\u3001v2\u3001v3\u786c\u4ef6\u3002 1280x720 60Hz, \u5e26\u97f3\u9891 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000","title":"EDID \u4f8b\u5b50 720P60Hz"},{"location":"edid/#edid_1","text":"\u6700\u597d\u4f7f\u7528\u7b2c\u4e09\u65b9\u5de5\u5177\u6765\u7f16\u8f91EDID\uff0c\u6bd4\u5982\u63a8\u8350\u7684\u9ad8\u7ea7 AW EDID Editor \uff08Windows\u73af\u5883\u4e0b\u8fd0\u884c\u826f\u597d\uff0c\u4e5f\u53ef\u5728wine\u4e2d\u4f7f\u7528\uff09\u6216\u8005 wxEDID \u3002\u8fd9\u4e24\u4e2a\u7f16\u8f91\u5668\u90fd\u53ef\u4ee5\u5904\u7406\u4e8c\u8fdb\u5236\u7684EDID\u683c\u5f0f\u3002 \u4f7f\u7528\u8fd9\u4e9b\u5de5\u5177\uff0c\u60a8\u53ef\u4ee5\u50cf\u7f16\u8f91\u6587\u4ef6\u4e00\u6837\u4fee\u6539EDID\u4fe1\u606f\uff0c\u7c7b\u4f3c\u4e8e\u66f4\u6539\u8eab\u4efd\u8bc1\u4fe1\u606f\u3002\u901a\u8fc7\u7f16\u8f91EDID\uff0c\u60a8\u53ef\u4ee5\u8c03\u6574\u663e\u793a\u5668\u7684\u53c2\u6570\u548c\u7279\u6027\uff0c\u4ee5\u9002\u5e94\u4e0d\u540c\u7684\u4f7f\u7528\u9700\u6c42\uff0c\u4ece\u800c\u83b7\u5f97\u66f4\u597d\u7684\u663e\u793a\u6548\u679c\u3002","title":"\u81ea\u5b9a\u4e49EDID"},{"location":"faq/","text":"FAQ & \u6545\u969c\u6392\u9664 \u4f5c\u4e3a\u7b2c\u4e00\u6b65\uff0c\u6211\u4eec\u5efa\u8bae\u4ed4\u7ec6\u9605\u8bfb\u6211\u4eec\u7684\u6587\u6863\u3002\u5927\u90e8\u5206\u8bbe\u7f6eBLIKVM\u6240\u9700\u7684\u6b65\u9aa4\u5df2\u7ecf\u5728\u6587\u6863\u4e2d\u63cf\u8ff0\u4e86\u3002\u5982\u679c\u60a8\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u60a8\u53ef\u4ee5\u67e5\u770b\u672c\u9875\uff0c\u5176\u4e2d\u5217\u51fa\u4e86\u5e38\u89c1\u9519\u8bef\u3002\u5982\u679c\u4ecd\u7136\u65e0\u6cd5\u89e3\u51b3\u95ee\u9898\uff0c\u6b22\u8fce\u63d0\u4ea4 \u95ee\u9898\u53cd\u9988 \u6216 \u52a0\u5165\u6211\u4eec\u7684Discord \u5bfb\u6c42\u8fdb\u4e00\u6b65\u5e2e\u52a9\u3002 \u5e38\u89c1\u95ee\u9898 \u6211\u53ef\u4ee5\u5c06\u591a\u53f0\u670d\u52a1\u5668\u8fde\u63a5\u5230\u5355\u4e2aBLIKVM\u5417\uff1f \u53ef\u4ee5\uff0c\u4f46\u9700\u8981\u8fdb\u884c\u989d\u5916\u7684\u8bbe\u7f6e\u5de5\u4f5c\u3002\u8bf7\u53c2\u8003 \u6b64\u9875\u9762 \u3002 \u5982\u4f55\u5728\u672c\u5730\u7f51\u7edc\u4e0a\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95eeBliKVM\uff1f \u5982\u679c\u60a8\u7684\u8def\u7531\u5668\u5177\u6709\u5916\u90e8IP\u5730\u5740\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u7aef\u53e3\u8f6c\u53d1\u6765\u8f6c\u53d180\u7aef\u53e3(Web),8008\u7aef\u53e3(mjpeg)\uff0c8188\u7aef\u53e3\uff08webrtc\uff09\u3002\u5728\u5176\u4ed6\u60c5\u51b5\u4e0b\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u51fa\u8272\u7684\u514d\u8d39VPN\u670d\u52a1Tailscale\u3002 BLiKVM\u6709\u591a\u6b3e\u786c\u4ef6\uff0c\u5982BliKVM V1 CM4\u3001BliKVM V2 PCIe\u3001BliKVM V3 Hat\uff0c\u6211\u5e94\u8be5\u9009\u54ea\u6b3e\uff1f \u9996\u5148\u5404\u4e2a\u7248\u672c\u7684\u4e3b\u8981\u53c2\u6570\u5bf9\u6bd4\u8bf7\u53c2\u8003 \u6b64\u9875\u9762 \u3002 V1\u548cV3\u5c5e\u4e8e\u5916\u7f6e\u65b9\u6848\uff0cV2\u5c5e\u4e8e\u5185\u7f6e\u673a\u7bb1\u65b9\u6848\u3002\u5982\u679c\u60a8\u662f\u673a\u7bb1\u5f62\u5f0f\uff0c\u5e76\u4e14\u673a\u7bb1\u5185\u90e8\u6709\u7a7a\u95f4\uff0c\u90a3\u4e48\u6beb\u65e0\u7591\u95ee\u9009\u62e9V2 PCIe\u7248\u672c\u662f\u8f83\u597d\u7684\u9009\u62e9\u3002 \u90a3\u4e48V1\u548cV3\u4e24\u4e2a\u5916\u7f6e\u65b9\u6848\u5982\u4f55\u9009\u62e9\u5462\uff0cV1\u57fa\u4e8eCM4\u7684\u65b9\u6848\uff0c\u96c6\u6210\u5ea6\u66f4\u9ad8\uff0c\u6709\u5230\u624b\u53ef\u7528\u7248\u672c\u3002V3\u57fa\u4e8e\u6811\u8393\u6d3e4B\u65b9\u6848\uff0c\u6240\u6709IO\u53e3\u5747\u5f15\u51fa\uff0c\u53ef\u6269\u5c55\u6027\u66f4\u5f3a\u3002\u4e24\u8005\u7684\u53e6\u4e00\u4e2a\u6838\u5fc3\u533a\u522b\u5c31\u662fV1\u6700\u9ad8\u652f\u63011080P60Hz\u8f93\u5165\uff0cV3\u6700\u9ad8\u652f\u63011080P50Hz\u8f93\u5165\u3002\u5f53\u7136\u540c\u65f6\u9700\u8981\u8003\u8651\u60a8\u662f\u5df2\u5426\u6709CM4\u6216\u80054B\uff0c\u5982\u679c\u6709\u7684\u8bdd\u53ea\u4e70\u5bf9\u5e94\u7684\u5e95\u677f\uff0c\u6027\u4ef7\u6bd4\u66f4\u9ad8\u3002 \u6211\u53ef\u4ee5\u7528BLIKVM\u8fdb\u884c\u6e38\u620f\u5417\uff1f \u4e0d\u53ef\u4ee5\uff0c\u539f\u56e0\u5982\u4e0b\uff1a \u5bf9\u4e8eHDMI-CSI\u6865\u63a5\u5668\uff0c\u603b\u7ebf\u5e26\u5bbd\u4e0d\u8db3\u4ee5\u4f20\u8f93\u8d85\u8fc71080p60\u7684\u89c6\u9891\u3002 \u5bf9\u4e8eHDMI-USB\u8f6c\u6362\u5668\uff0c\u5ef6\u8fdf\u8f83\u9ad8\u4e14\u89c6\u9891\u8d28\u91cf\u8f83\u4f4e\u3002 \u4e00\u822c\u7684\u786c\u4ef6\u89c6\u9891\u6355\u83b7\u4e0e\u8f6f\u4ef6\u6d41\u5a92\u4f53\u6709\u6240\u4e0d\u540c\uff0c\u4f1a\u5f15\u5165\u989d\u5916\u7684\u5ef6\u8fdf\u3002 BLIKVM\u652f\u63014K\u89c6\u9891\u5417\uff1f \u5bf9\u4e8eHDMI-CSI\u6865\u63a5\u5668\uff0c\u4e0d\u652f\u6301\u3002CSI\u603b\u7ebf\u7684\u5e26\u5bbd\u4e0d\u8db3\u4ee5\u5904\u7406\u5982\u6b64\u5927\u91cf\u7684\u6570\u636e\u30021080p60\u662f\u5e26\u5bbd\u7684\u4e0a\u9650\u3002 \u5bf9\u4e8eUSB\u6355\u83b7\u8bbe\u5907\uff1a\u4ece\u6280\u672f\u4e0a\u8bb2\uff0c\u662f\u53ef\u4ee5\u7684\uff0c\u4f46\u5b83\u4eec\u4f1a\u964d\u4f4e\u5206\u8fa8\u7387\u4ee5\u9002\u5e94USB 2.0\u7684\u5e26\u5bbd\u9650\u5236\uff0c\u56e0\u6b64\u6d41\u5a92\u4f53\u7684\u5206\u8fa8\u7387\u4e0d\u4f1a\u662f4K\u3002 \u65e0\u8bba\u5982\u4f55\uff0c4K\u5b9e\u65f6\u89c6\u9891\u4e5f\u65e0\u6cd5\u901a\u8fc7\u7f51\u7edc\u4f20\u8f93\u3002 \u5149\u6807/\u89c6\u9891\u5ef6\u8fdf\u662f\u7531\u4ec0\u4e48\u5f15\u8d77\u7684\uff1f \u56fe\u50cf\u4f20\u8f93\u5230\u6d4f\u89c8\u5668\u6216VNC\u5ba2\u6237\u7aef\u7684\u8fc7\u7a0b\u5982\u4e0b\uff1a \u6355\u83b7\u8bbe\u5907 -> \u538b\u7f29 -> \u7f51\u7edc -> \u89e3\u538b\u7f29 -> \u6e32\u67d3 \u5728\u6b64\u8fc7\u7a0b\u4e2d\uff0c100-200ms\u7684\u5ef6\u8fdf\u5df2\u7ecf\u975e\u5e38\u5feb\u901f\u4e86\u3002\u4f46\u6211\u4eec\u6b63\u5728\u52aa\u529b\u8fdb\u4e00\u6b65\u63d0\u9ad8\u901f\u5ea6\u3002 BLIKVM\u652f\u6301\u97f3\u9891\u5417\uff1f BliKVM v1 CM4, v2 PCIe, v3 HAT\u7248\u672c\u652f\u6301\uff0c v4 Allwinner\u7248\u672c\u4e0d\u652f\u6301\u3002 \u6211\u53ef\u4ee5\u901a\u8fc7PoE\u7ed9Pi\u4f9b\u7535\u5417\uff1f \u53ef\u4ee5\uff01Hat\u7248\u672c\u548cPCIe\u7248\u672c\u90fd\u652f\u6301PoE\u3002 \u7b2c\u4e00\u6b65 \u9ed8\u8ba4\u5bc6\u7801\u662f\u4ec0\u4e48\uff1f\u5982\u4f55\u66f4\u6539\u5bc6\u7801\uff1f \u5982\u679c\u60a8\u4f7f\u7528PiKVM\uff0c\u6709\u4e24\u79cd\u7c7b\u578b\u7684\u5e10\u6237\uff1a\u64cd\u4f5c\u7cfb\u7edf\u5e10\u6237\u548cPiKVM\uff08Web\u754c\u9762\uff09\u5e10\u6237\u3002\u7cfb\u7edf\u5e10\u6237 root \u53ef\u7528\u4e8eSSH/UART\u8bbf\u95ee\uff0c\u5bc6\u7801\u4e3a root \u3002Web\u754c\u9762\u5e10\u6237\u79f0\u4e3a admin \uff0c\u5bc6\u7801\u4e3a admin \u3002PiKVM\u5e10\u6237\u4e0d\u80fd\u7528\u4e8eSSH\u8bbf\u95ee\uff0c\u53cd\u4e4b\u4ea6\u7136\u3002 \u8981\u66f4\u6539\u5bc6\u7801\uff0c\u8bf7\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\uff08\u5728root\u7528\u6237\u4e0b\uff09\uff1a su - # \u5982\u679c\u60a8\u5728Webterm\u4e2d rw # \u5207\u6362\u6587\u4ef6\u7cfb\u7edf\u4e3a\u8bfb\u5199\u6a21\u5f0f passwd root # \u66f4\u6539\u64cd\u4f5c\u7cfb\u7edfroot\u5bc6\u7801 kvmd-htpasswd set admin # \u66f4\u6539Web\u754c\u9762\u7ba1\u7406\u5458\u5bc6\u7801 ro # \u5207\u6362\u56de\u53ea\u8bfb\u6a21\u5f0f \u5982\u679c\u60a8\u4f7f\u7528\u7684\u662fBliKVM\uff0cWeb\u754c\u9762\u5e10\u6237\u79f0\u4e3a admin \uff0c\u5bc6\u7801\u4e3a admin ,\u7ec8\u7aef\u7528\u6237\u540d\u79f0\u4e3a blikvm \uff0c\u5bc6\u7801\u4e3a blikvm \u3002 \u5982\u4f55\u6dfb\u52a0\u53e6\u4e00\u4e2a\u7528\u6237\uff1f \u5982\u679c\u60a8\u4f7f\u7528PiKVM\u8f6f\u4ef6\uff0c\u5982\u4e0a\u6240\u8ff0\uff0c\u60a8\u9700\u8981\u521b\u5efa2\u4e2a\u5e10\u6237\uff0c\u4e00\u4e2a\u7528\u4e8eShell\uff0c\u53e6\u4e00\u4e2a\u7528\u4e8ePiKVM Web\u754c\u9762\u3002 \u5982\u679c\u60a8\u9700\u8981\u4e3aPiKVM Web\u754c\u9762\u6dfb\u52a0\u5176\u4ed6\u7528\u6237\uff0c\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\uff1a # rw # su - # kvmd-htpasswd set  # \u6dfb\u52a0\u65b0\u7528\u6237 # kvmd-htpasswd set  # \u8bbe\u7f6e\u5bc6\u7801\uff08\u53ea\u8981\u7528\u6237\u5b58\u5728\uff09 # kvmd-htpasswd del  # \u5220\u9664\u7528\u6237 \u8981\u6dfb\u52a0Shell/\u7ec8\u7aef\u5e10\u6237\uff1a # rw # su - # adduser  # passwd  \u8bf7\u6ce8\u610f\uff0c\u6dfb\u52a0\u7684\u7528\u6237\u8d8a\u591a\uff0c\u8bbf\u95ee\u6d41\u5a92\u4f53\u65f6\u5e27\u7387\u4f1a\u964d\u4f4e\u3002 \u89c6\u9891\u95ee\u9898 BLIKVM\u6839\u672c\u6ca1\u6709\u663e\u793a\u6765\u81ea\u8ba1\u7b97\u673a\u7684\u89c6\u9891 \u8bf7\u4ed4\u7ec6\u68c0\u67e5\u89c6\u9891\u6355\u83b7\u8bbe\u5907\u7684\u8fde\u63a5\u60c5\u51b5\u3002\u5bf9\u4e8eCSI\u6865\u63a5\u5668\uff0c\u5e94\u8fde\u63a5\u5230\u76f8\u673a\u7aef\u53e3\u3002 \u6709\u4e9b\u7b14\u8bb0\u672c\u7535\u8111\u5728\u60a8\u5207\u6362\u8f93\u51fa\u4e4b\u524d\uff08\u901a\u5e38\u901a\u8fc7\u952e\u76d8\u4e0a\u7684FN +\u548cF5\u952e\uff09\u4e0d\u4f1a\u8f93\u51fa\u4efb\u4f55\u4fe1\u53f7\u3002 \u60a8\u7684\u8ba1\u7b97\u673a\u53ef\u80fd\u5df2\u7ecf\u5c06\u663e\u793a\u5668\u8bbe\u7f6e\u4e3a\u7761\u7720\u6a21\u5f0f\u3002\u79fb\u52a8\u9f20\u6807\u4ee5\u5173\u95ed\u7761\u7720\u6a21\u5f0f\u3002 \u5bf9\u4e8eWindows\u7cfb\u7edf\uff0c\u60a8\u53ef\u80fd\u9700\u8981\u68c0\u67e5\u6d3b\u52a8\u4fe1\u53f7\u5206\u8fa8\u7387\u3002\u8981\u66f4\u6539\u6d3b\u52a8\u4fe1\u53f7\u5206\u8fa8\u7387\uff0c\u8bf7\u8f6c\u5230\u201c\u8bbe\u7f6e\u201d>\u201c\u7cfb\u7edf\u201d>\u201c\u663e\u793a\u201d>\u201c\u9ad8\u7ea7\u663e\u793a\u8bbe\u7f6e\u201d>\u201c\u663e\u793a\u9002\u914d\u5668\u5c5e\u6027\u201d\uff0c\u7136\u540e\u70b9\u51fb\u201c\u5217\u51fa\u6240\u6709\u6a21\u5f0f\u201d\uff0c\u9009\u62e9\u6240\u9700\u7684\u6a21\u5f0f\u3002\u5c1d\u8bd5\u4e0d\u540c\u7684\u5237\u65b0\u7387\u8bbe\u7f6e\u3002 \u5728\u5df2\u542f\u52a8\u7684\u64cd\u4f5c\u7cfb\u7edf\u4e2d\u53ef\u4ee5\u770b\u5230\u89c6\u9891\uff0c\u4f46\u5728BIOS/UEFI\u4e2d\u770b\u4e0d\u5230 \u5f53\u4f7f\u7528CSI\u6865\u63a5\u5668\u65f6\uff0cIntel NUC\u3001GA-H77-DS3H\u548c\u4e00\u4e9b\u5176\u4ed6\u8bbe\u5907\u4e0a\u4f1a\u51fa\u73b0\u6b64\u95ee\u9898\u3002\u60a8\u53ea\u9700\u8981\u66f4\u6539EDID\u6570\u636e\uff0c\u8fd9\u662fCSI\u6865\u63a5\u5668\u5411\u8ba1\u7b97\u673a\u62a5\u544a\u7684\u652f\u6301\u7684\u5206\u8fa8\u7387\u4fe1\u606f\u3002 BIOS/UEFI\u5206\u8fa8\u7387\u51fa\u73b0\u6545\u969c\u6216\u9519\u8bef \u5728\u67d0\u4e9b\u4e3b\u677f\u4e0a\uff0cBIOS\u53ef\u80fd\u4ee5\u8f83\u4f4e\u7684\u5206\u8fa8\u7387\u663e\u793a\uff0c\u6216\u51fa\u73b0\u4e00\u4e9b\u6e32\u67d3\u95ee\u9898/\u6545\u969c\uff0c\u7279\u522b\u662f\u5728\u8f83\u65b0\u7684ASUS\u4e3b\u677f\u4e0a\u3002\u5982\u4e0b\u56fe\u6240\u793a\uff1a \u60a8\u53ef\u4ee5\u901a\u8fc7\u5728BIOS\u4e2d\u542f\u7528 \u517c\u5bb9\u6027\u652f\u6301\u6a21\u5757\uff08CSM\uff09 \u6765\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u901a\u5e38\u4f4d\u4e8e \u5f15\u5bfc \u9009\u9879\u4e0b\u3002 \u5982\u679c\u60a8\u65e0\u6cd5\u6216\u4e0d\u60f3\u542f\u7528CSM\uff0c\u60a8\u53ef\u4ee5\u5c1d\u8bd5\u8fde\u63a5\u4e00\u4e2aDisplayPort\uff08DP\uff09\u663e\u793a\u5668\u6216 \u865a\u62df\u63d2\u5934 \u3002\u5982\u679c\u62d4\u6389DP\u7535\u7f06/\u8f6c\u63a5\u5668\uff0c\u95ee\u9898\u5c06\u91cd\u65b0\u51fa\u73b0\u3002 \u5982\u679c\u4e0a\u8ff0\u65b9\u6cd5\u90fd\u4e0d\u8d77\u4f5c\u7528\uff0c\u8bf7\u5c1d\u8bd5\u5148\u8fde\u63a5DP\u7535\u7f06\uff0c\u7136\u540e\u542f\u52a8\u5230BIOS\uff0c\u7981\u7528CSM\u5e76\u5173\u673a\uff08\u4e0d\u8981\u91cd\u65b0\u542f\u52a8\uff09\u60a8\u7684\u8ba1\u7b97\u673a\u3002\u7136\u540e\uff0c\u5728\u518d\u6b21\u542f\u52a8\u5230BIOS\u5e76\u542f\u7528CSM\u4e4b\u524d\uff0c\u8fde\u63a5HDMI\u5e76\u518d\u6b21\u6253\u5f00\u8ba1\u7b97\u673a\u3002 GRUB2\u4e2d\u6ca1\u6709\u89c6\u9891\uff0c\u4f46\u4e4b\u524d\u548c\u4e4b\u540e\u90fd\u6709 \u6709\u65f6\u8fd9\u53ef\u80fd\u662f\u7531\u4e8eBIOS/UEFI\u7684\u7279\u5b9a\u95ee\u9898\u4ee5\u53caGRUB2\u4e0e\u89c6\u9891\u7684\u5de5\u4f5c\u65b9\u5f0f\u6240\u5bfc\u81f4\u7684\u3002 \u60a8\u53ef\u4ee5\u901a\u8fc7\u5728BIOS\u4e2d\u542f\u7528 \u517c\u5bb9\u6027\u652f\u6301\u6a21\u5757\uff08CSM\uff09 \u6765\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u901a\u5e38\u4f4d\u4e8e \u5f15\u5bfc \u9009\u9879\u4e0b\u3002\u89c6\u9891\u6a21\u5f0f\u4e5f\u4f4d\u4e8e\u540c\u4e00\u90e8\u5206\u3002\u5c06 \u89c6\u9891 \u6a21\u5f0f\u4ece UEFI \u5207\u6362\u4e3a Legacy \u3002 Linux + Awesome WM\u6ca1\u6709\u8ba1\u7b97\u673a\u56fe\u50cf \u6709\u65f6\uff0c\u5728Linux\u4e0a\u4f7f\u7528Awesome WM\u53ef\u80fd\u65e0\u6cd5\u8bc6\u522b\u7535\u7f06\u7684\u89c6\u9891\u8f93\u51fa\u66f4\u6539\u3002\u4e5f\u5c31\u662f\u8bf4\uff0c\u5982\u679c\u7535\u7f06\u5148\u63d2\u5165\u663e\u793a\u5668\uff0c\u7136\u540e\u518d\u8fde\u63a5\u5230BLIKVM\uff0c\u53ef\u80fd\u4f1a\u5bfc\u81f4\u60a8\u770b\u4e0d\u5230\u56fe\u50cf\u3002\u8fd9\u4f3c\u4e4e\u662fAwesome WM\u7684\u95ee\u9898\uff0c\u56e0\u4e3a\u4f8b\u5982\u5728KDE\u4e2d\uff0c\u8fd9\u79cd\u60c5\u51b5\u65e0\u6cd5\u590d\u73b0\u3002\u5982\u679c\u60a8\u5728\u8fde\u63a5BLIKVM\u540e\u542f\u52a8\u5de5\u4f5c\u7ad9\uff0c\u4e00\u5207\u90fd\u5c06\u6b63\u5e38\u5de5\u4f5c\u3002 USB\u95ee\u9898\uff08\u952e\u76d8\u3001\u9f20\u6807\u3001U\u76d8\u7b49\uff09 USB OTG\u7aef\u53e3\u7684\u901f\u5ea6\u662f\u591a\u5c11\uff1f \u6839\u636e\u5b98\u65b9\u7684RPI\u6587\u6863\uff0c\u8fd9\u662fSoC\u7684\u9650\u5236\u3002OTG\u7aef\u53e3\u53ea\u652f\u6301USB 2.0\uff0c\u56e0\u6b64\u901f\u5ea6\u9650\u5236\u4e3a455 Mbit/s\u3002 \u4e3a\u4ec0\u4e48\u65e0\u6cd5\u6355\u83b7\u67d0\u4e9b\u5b9e\u4f53\u952e\u76d8\u7684\u952e\u76d8\u5feb\u6377\u952e\uff0c\u4f46\u53ef\u4ee5\u6355\u83b7\u865a\u62df\u952e\u76d8\u7684\u952e\u76d8\u5feb\u6377\u952e\uff1f\u4f8b\u5982\uff0c\u65e0\u6cd5\u6355\u83b7Mac\u7535\u8111\u7684F11\u6309\u952e \u8fd9\u662f\u56e0\u4e3a\u4e00\u4e9b\u5feb\u6377\u952e\u5df2\u7ecf\u88ab\u64cd\u4f5c\u7cfb\u7edf\u4f7f\u7528\u4e86\uff0c\u4f8b\u5982\u5728 macOS \u4e2d\uff0cF11 \u88ab\u9ed8\u8ba4\u5206\u914d\u7ed9\u4e86\u201c\u663e\u793a\u684c\u9762\u201d\u7684\u529f\u80fd\u3002\u5f53\u60a8\u5728Web\u754c\u9762\u6309\u4e0bF11\u65f6\uff0c\u952e\u76d8\u4e8b\u4ef6\u9996\u5148\u88ab\u64cd\u4f5c\u7cfb\u7edf\u6355\u83b7\uff0c\u5982\u679c\u64cd\u4f5c\u7cfb\u7edf\u6ce8\u518c\u4e86\u56de\u8c03\u51fd\u6570\uff0c\u952e\u76d8\u4e8b\u4ef6\u5c06\u4e0d\u4f1a\u4f20\u9012\u7ed9\u5e94\u7528\u7a0b\u5e8f\u3002\u8981\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u60a8\u53ef\u4ee5\u5173\u95ed\u64cd\u4f5c\u7cfb\u7edf\u8bbe\u7f6e\u4e2d\u7684\u5feb\u6377\u952e\uff0c\u6216\u8005\u4f7f\u7528\u865a\u62df\u952e\u76d8\u3002 \u786c\u4ef6\u95ee\u9898\uff08Wi-Fi\u3001ATX\u7b49\uff09 \u5982\u679c\u4f7f\u7528PiKVM\u8f6f\u4ef6\uff0cWeb\u754c\u9762\u663e\u793a FAN \u9519\u8bef\uff01 \u7531\u4e8eBLIKVM\u786c\u4ef6\u4f7f\u7528\u7684\u98ce\u6247\u578b\u53f7\u4e0ePIKVM\u786c\u4ef6\u4e0d\u540c\uff0c\u56e0\u6b64\u5728pikvm\u7684\u6700\u65b0\u7cfb\u7edf\u4e2d\uff0c\u901a\u8fc7Web\u754c\u9762\u67e5\u770b\u98ce\u6247\u72b6\u6001\u53ef\u80fd\u4f1a\u5931\u8d25\u3002\u4f46\u8fd9\u4e0d\u4f1a\u5f71\u54cdBLIKVM\u98ce\u6247\u7684\u6b63\u5e38\u8fd0\u884c\u3002\u56e0\u6b64\uff0c\u5728\u4f7f\u7528PIKVM\u955c\u50cf\u65f6\uff0c\u53ea\u8981\u786e\u4fdd \u5b89\u88c5\u811a\u672c \u663e\u793aOK\uff0c\u5c31\u8868\u793akvmd\u98ce\u6247\u7a0b\u5e8f\u7684\u66f4\u65b0\u6210\u529f\u3002\u9ed8\u8ba4\u7a0b\u5e8f\u8bbe\u7f6e\u7684\u6e29\u5ea6\u9608\u503c\u4e3a\u6444\u6c0f60\u5ea6\u3002\u5f53\u68c0\u6d4b\u5230CPU\u6e29\u5ea6\u8d85\u8fc760\u6444\u6c0f\u5ea6\u65f6\uff0c\u98ce\u6247\u5c06\u4ee585%\u7684\u901f\u5ea6\u5f00\u59cb\u65cb\u8f6c\u3002\u5982\u679c\u8981\u4fee\u6539\u6e29\u5ea6\u9608\u503c\u548c\u901f\u5ea6\uff0c\u53ef\u4ee5\u4fee\u6539kvmd-fan.py\u811a\u672c\uff0c\u7136\u540e\u91cd\u65b0\u6267\u884cinstall.sh\u3002 \u6211\u6839\u672c\u65e0\u6cd5\u8fde\u63a5\u5230Wi-Fi\uff01 \u5982\u679c\u60a8\u7684\u8bbe\u5907\u65e0\u6cd5\u8fde\u63a5\u5230\u60a8\u8bbe\u7f6e\u7684Wi-Fi\u7f51\u7edc\uff0c\u8bf7\u68c0\u67e5\u60a8\u7684Wi-Fi\u63a5\u5165\u70b9\u4f7f\u7528\u76842.4GHz Wi-Fi\u4fe1\u9053\u3002\u5982\u679c\u4f7f\u7528\u4e8612\u523014\u4fe1\u9053\uff08\u67d0\u4e9b\u56fd\u5bb6\u7981\u6b62\u4f7f\u7528\u8fd9\u4e9b\u4fe1\u9053\uff09\uff0c\u8bf7\u5c1d\u8bd5\u4f7f\u75281\u523011\u4e4b\u95f4\u7684\u4fe1\u9053\u3002 BLIKVM\u663e\u793a\u4f4e\u7535\u538b\u8b66\u544a \u60a8\u662f\u5426\u4f7f\u7528\u4e86\u201c\u6b63\u786e\u201d\u7684\u7535\u6e90\u9002\u914d\u5668\uff1f\u800c\u4e0d\u662f\u81ea\u5df1\u62fc\u51d1\u7684\u9002\u914d\u5668\uff1f \u4e00\u4e9bUSB\u7535\u6e90\u9002\u914d\u5668\u5ba3\u4f20\u4e3a5V 2.1A\u6216\u66f4\u9ad8\uff0c\u4f46\u65e0\u6cd5\u63d0\u4f9b\u7a33\u5b9a\u76845V\u7535\u538b\u3002\u6700\u597d\u4f7f\u7528\u6811\u8393\u6d3e\u57fa\u91d1\u4f1a\u63a8\u8350\u7684\u7535\u6e90\u9002\u914d\u5668\u3002\u5176\u8f93\u51fa\u5e94\u4e3a5.1V\u548c3A\u76f4\u6d41\u7535\u538b\u3002 \u5f53\u6211\u4f7f\u7528PoE\u65f6\uff0c\u662f\u5426\u4ecd\u7136\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u6765\u9632\u6b62\u673a\u5668USB\u7684\u53cd\u5411\u4f9b\u7535\uff1f \u53ea\u6709HAT\u7248\u672c\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u6765\u9632\u6b62\u53cd\u5411\u4f9b\u7535\u3002\u901a\u5e38\uff0c\u5927\u591a\u6570\u4e3b\u673a\u8ba1\u7b97\u673a\u90fd\u6709\u53cd\u5411\u4f9b\u7535\u4fdd\u62a4\uff0c\u56e0\u6b64\u5728\u8fd9\u79cd\u60c5\u51b5\u4e0b\u4e0d\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u3002 BLIKVM-CM4-V2.2\u548cBLIKVM-PCIe\u7248\u672c\u4e0d\u9700\u8981\u3002 \u5728\u4e00\u4e9b\u50cfBLIKVM-PCIe\u6216BLIKVM-CM4-V2.2\u8fd9\u6837\u7684\u677f\u5b50\u4e0a\u6709\u5f15\u5bfc\u5f15\u811a\uff0c\u5982\u4f55\u8fde\u63a5\uff1f \u5982\u679c\u5c06\u5b83\u4eec\u8fde\u63a5\u77ed\u8def\uff0cCM4\u5c06\u65e0\u6cd5\u6b63\u5e38\u542f\u52a8\uff0c\u800c\u5c06\u8fdb\u5165\u70e7\u5f55\u6620\u50cf\u6a21\u5f0f\u3002\u5982\u679c\u60a8\u7684\u786c\u4ef6\u7248\u672c\u7684\u5f15\u5bfc\u5f15\u811a\u53ea\u6709\u4e24\u4e2a\u5f15\u811a\uff0c\u4f7f\u7528\u8df3\u7ebf\u5e3d\u5c06\u8fd9\u4e24\u4e2a\u5f15\u811a\u8fde\u63a5\u8d77\u6765\uff0c\u5f62\u6210\u77ed\u8def\u3002\u5982\u679c\u60a8\u4e0d\u4f7f\u7528\u8df3\u7ebf\u5e3d\u6216\u53ea\u5c06\u5176\u63d2\u5165\u4e00\u4e2a\u5f15\u811a\uff0cCM4\u5c06\u6b63\u5e38\u542f\u52a8\u3002\u5982\u679c\u60a8\u4f7f\u7528\u7684\u662f\u4e09\u4e2a\u5f15\u5bfc\u5f15\u811a\u7684\u786c\u4ef6\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u8df3\u7ebf\u5e3d\u5c06GND\u548c\u53e6\u4e00\u4e2a\u975eGND\u5f15\u811a\u8fde\u63a5\u8d77\u6765\u4ee5\u793a\u77ed\u8def\uff0c\u5e76\u5c06\u8df3\u7ebf\u5e3d\u63d2\u5728\u4e24\u4e2aGND\u5f15\u811a\u4e0a\u6216\u4e0d\u4f7f\u7528\u8df3\u7ebf\u5e3d\uff0cCM4\u5c06\u6b63\u5e38\u542f\u52a8\u3002 Web\u95ee\u9898 BliKVM OS\u5360\u7528\u7684\u7aef\u53e3\u6709\u54ea\u4e9b\uff0c\u5728\u7528\u516c\u7f51\u670d\u52a1\u5668\u8f6c\u53d1\u65f6\uff0c\u5e94\u8be5\u600e\u4e48\u505a\uff1f Web\u754c\u9762\u4e3ahttp\u534f\u8bae\uff0c\u5360\u7528\u7684\u662f80\u7aef\u53e3\uff1b \u5982\u679c\u60a8\u7684\u786c\u4ef6\u662fV1 V2 V3\uff0c\u4f7f\u7528\u7684\u662f\u662fweb-rtc\u4f20\u8f93\uff0c\u7aef\u53e3\u662f8188\uff1b \u5982\u679c\u60a8\u7684\u786c\u4ef6\u662fV4\uff0c\u4f7f\u7528\u7684\u662fmjepg\u4f20\u8f93\uff0c\u7aef\u53e3\u662f8008\uff1b \u6ce8\u610f\u7aef\u53e3\u4e0d\u652f\u6301\u88ab\u4fee\u6539\uff0c\u53ea\u80fd\u914d\u7f6e\u8f6c\u53d1\uff1b \u6811\u8393\u6d3e\u76f8\u5173\u95ee\u9898 \u6211\u662f\u5426\u53ef\u4ee5\u540c\u65f6\u4f7f\u7528\u5e26eMMC\u7248\u672c\u7684CM4\u548cSD\u5361? \u4e0d\u53ef\u4ee5\uff0c\u56e0\u4e3a\u5728CM4\u786c\u4ef6\u8bbe\u8ba1\u4e0a\uff0c\u51e0\u4e2aSD\u5361\u7684\u5f15\u811a\u53ea\u5728lite\u7248\u672c\u4e2d\u662f\u53ef\u7528\u7684\uff0c\u4f60\u53ef\u4ee5\u5728\u6811\u8393\u6d3e\u5b98\u7f51\u627e\u5230\u8bf4\u660e\u3002","title":"\u5e38\u89c1\u95ee\u9898\u89e3\u7b54"},{"location":"faq/#faq","text":"\u4f5c\u4e3a\u7b2c\u4e00\u6b65\uff0c\u6211\u4eec\u5efa\u8bae\u4ed4\u7ec6\u9605\u8bfb\u6211\u4eec\u7684\u6587\u6863\u3002\u5927\u90e8\u5206\u8bbe\u7f6eBLIKVM\u6240\u9700\u7684\u6b65\u9aa4\u5df2\u7ecf\u5728\u6587\u6863\u4e2d\u63cf\u8ff0\u4e86\u3002\u5982\u679c\u60a8\u9047\u5230\u4efb\u4f55\u95ee\u9898\uff0c\u60a8\u53ef\u4ee5\u67e5\u770b\u672c\u9875\uff0c\u5176\u4e2d\u5217\u51fa\u4e86\u5e38\u89c1\u9519\u8bef\u3002\u5982\u679c\u4ecd\u7136\u65e0\u6cd5\u89e3\u51b3\u95ee\u9898\uff0c\u6b22\u8fce\u63d0\u4ea4 \u95ee\u9898\u53cd\u9988 \u6216 \u52a0\u5165\u6211\u4eec\u7684Discord \u5bfb\u6c42\u8fdb\u4e00\u6b65\u5e2e\u52a9\u3002","title":"FAQ & \u6545\u969c\u6392\u9664"},{"location":"faq/#_1","text":"\u6211\u53ef\u4ee5\u5c06\u591a\u53f0\u670d\u52a1\u5668\u8fde\u63a5\u5230\u5355\u4e2aBLIKVM\u5417\uff1f \u53ef\u4ee5\uff0c\u4f46\u9700\u8981\u8fdb\u884c\u989d\u5916\u7684\u8bbe\u7f6e\u5de5\u4f5c\u3002\u8bf7\u53c2\u8003 \u6b64\u9875\u9762 \u3002 \u5982\u4f55\u5728\u672c\u5730\u7f51\u7edc\u4e0a\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95eeBliKVM\uff1f \u5982\u679c\u60a8\u7684\u8def\u7531\u5668\u5177\u6709\u5916\u90e8IP\u5730\u5740\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u7aef\u53e3\u8f6c\u53d1\u6765\u8f6c\u53d180\u7aef\u53e3(Web),8008\u7aef\u53e3(mjpeg)\uff0c8188\u7aef\u53e3\uff08webrtc\uff09\u3002\u5728\u5176\u4ed6\u60c5\u51b5\u4e0b\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u51fa\u8272\u7684\u514d\u8d39VPN\u670d\u52a1Tailscale\u3002 BLiKVM\u6709\u591a\u6b3e\u786c\u4ef6\uff0c\u5982BliKVM V1 CM4\u3001BliKVM V2 PCIe\u3001BliKVM V3 Hat\uff0c\u6211\u5e94\u8be5\u9009\u54ea\u6b3e\uff1f \u9996\u5148\u5404\u4e2a\u7248\u672c\u7684\u4e3b\u8981\u53c2\u6570\u5bf9\u6bd4\u8bf7\u53c2\u8003 \u6b64\u9875\u9762 \u3002 V1\u548cV3\u5c5e\u4e8e\u5916\u7f6e\u65b9\u6848\uff0cV2\u5c5e\u4e8e\u5185\u7f6e\u673a\u7bb1\u65b9\u6848\u3002\u5982\u679c\u60a8\u662f\u673a\u7bb1\u5f62\u5f0f\uff0c\u5e76\u4e14\u673a\u7bb1\u5185\u90e8\u6709\u7a7a\u95f4\uff0c\u90a3\u4e48\u6beb\u65e0\u7591\u95ee\u9009\u62e9V2 PCIe\u7248\u672c\u662f\u8f83\u597d\u7684\u9009\u62e9\u3002 \u90a3\u4e48V1\u548cV3\u4e24\u4e2a\u5916\u7f6e\u65b9\u6848\u5982\u4f55\u9009\u62e9\u5462\uff0cV1\u57fa\u4e8eCM4\u7684\u65b9\u6848\uff0c\u96c6\u6210\u5ea6\u66f4\u9ad8\uff0c\u6709\u5230\u624b\u53ef\u7528\u7248\u672c\u3002V3\u57fa\u4e8e\u6811\u8393\u6d3e4B\u65b9\u6848\uff0c\u6240\u6709IO\u53e3\u5747\u5f15\u51fa\uff0c\u53ef\u6269\u5c55\u6027\u66f4\u5f3a\u3002\u4e24\u8005\u7684\u53e6\u4e00\u4e2a\u6838\u5fc3\u533a\u522b\u5c31\u662fV1\u6700\u9ad8\u652f\u63011080P60Hz\u8f93\u5165\uff0cV3\u6700\u9ad8\u652f\u63011080P50Hz\u8f93\u5165\u3002\u5f53\u7136\u540c\u65f6\u9700\u8981\u8003\u8651\u60a8\u662f\u5df2\u5426\u6709CM4\u6216\u80054B\uff0c\u5982\u679c\u6709\u7684\u8bdd\u53ea\u4e70\u5bf9\u5e94\u7684\u5e95\u677f\uff0c\u6027\u4ef7\u6bd4\u66f4\u9ad8\u3002 \u6211\u53ef\u4ee5\u7528BLIKVM\u8fdb\u884c\u6e38\u620f\u5417\uff1f \u4e0d\u53ef\u4ee5\uff0c\u539f\u56e0\u5982\u4e0b\uff1a \u5bf9\u4e8eHDMI-CSI\u6865\u63a5\u5668\uff0c\u603b\u7ebf\u5e26\u5bbd\u4e0d\u8db3\u4ee5\u4f20\u8f93\u8d85\u8fc71080p60\u7684\u89c6\u9891\u3002 \u5bf9\u4e8eHDMI-USB\u8f6c\u6362\u5668\uff0c\u5ef6\u8fdf\u8f83\u9ad8\u4e14\u89c6\u9891\u8d28\u91cf\u8f83\u4f4e\u3002 \u4e00\u822c\u7684\u786c\u4ef6\u89c6\u9891\u6355\u83b7\u4e0e\u8f6f\u4ef6\u6d41\u5a92\u4f53\u6709\u6240\u4e0d\u540c\uff0c\u4f1a\u5f15\u5165\u989d\u5916\u7684\u5ef6\u8fdf\u3002 BLIKVM\u652f\u63014K\u89c6\u9891\u5417\uff1f \u5bf9\u4e8eHDMI-CSI\u6865\u63a5\u5668\uff0c\u4e0d\u652f\u6301\u3002CSI\u603b\u7ebf\u7684\u5e26\u5bbd\u4e0d\u8db3\u4ee5\u5904\u7406\u5982\u6b64\u5927\u91cf\u7684\u6570\u636e\u30021080p60\u662f\u5e26\u5bbd\u7684\u4e0a\u9650\u3002 \u5bf9\u4e8eUSB\u6355\u83b7\u8bbe\u5907\uff1a\u4ece\u6280\u672f\u4e0a\u8bb2\uff0c\u662f\u53ef\u4ee5\u7684\uff0c\u4f46\u5b83\u4eec\u4f1a\u964d\u4f4e\u5206\u8fa8\u7387\u4ee5\u9002\u5e94USB 2.0\u7684\u5e26\u5bbd\u9650\u5236\uff0c\u56e0\u6b64\u6d41\u5a92\u4f53\u7684\u5206\u8fa8\u7387\u4e0d\u4f1a\u662f4K\u3002 \u65e0\u8bba\u5982\u4f55\uff0c4K\u5b9e\u65f6\u89c6\u9891\u4e5f\u65e0\u6cd5\u901a\u8fc7\u7f51\u7edc\u4f20\u8f93\u3002 \u5149\u6807/\u89c6\u9891\u5ef6\u8fdf\u662f\u7531\u4ec0\u4e48\u5f15\u8d77\u7684\uff1f \u56fe\u50cf\u4f20\u8f93\u5230\u6d4f\u89c8\u5668\u6216VNC\u5ba2\u6237\u7aef\u7684\u8fc7\u7a0b\u5982\u4e0b\uff1a \u6355\u83b7\u8bbe\u5907 -> \u538b\u7f29 -> \u7f51\u7edc -> \u89e3\u538b\u7f29 -> \u6e32\u67d3 \u5728\u6b64\u8fc7\u7a0b\u4e2d\uff0c100-200ms\u7684\u5ef6\u8fdf\u5df2\u7ecf\u975e\u5e38\u5feb\u901f\u4e86\u3002\u4f46\u6211\u4eec\u6b63\u5728\u52aa\u529b\u8fdb\u4e00\u6b65\u63d0\u9ad8\u901f\u5ea6\u3002 BLIKVM\u652f\u6301\u97f3\u9891\u5417\uff1f BliKVM v1 CM4, v2 PCIe, v3 HAT\u7248\u672c\u652f\u6301\uff0c v4 Allwinner\u7248\u672c\u4e0d\u652f\u6301\u3002 \u6211\u53ef\u4ee5\u901a\u8fc7PoE\u7ed9Pi\u4f9b\u7535\u5417\uff1f \u53ef\u4ee5\uff01Hat\u7248\u672c\u548cPCIe\u7248\u672c\u90fd\u652f\u6301PoE\u3002","title":"\u5e38\u89c1\u95ee\u9898"},{"location":"faq/#_2","text":"\u9ed8\u8ba4\u5bc6\u7801\u662f\u4ec0\u4e48\uff1f\u5982\u4f55\u66f4\u6539\u5bc6\u7801\uff1f \u5982\u679c\u60a8\u4f7f\u7528PiKVM\uff0c\u6709\u4e24\u79cd\u7c7b\u578b\u7684\u5e10\u6237\uff1a\u64cd\u4f5c\u7cfb\u7edf\u5e10\u6237\u548cPiKVM\uff08Web\u754c\u9762\uff09\u5e10\u6237\u3002\u7cfb\u7edf\u5e10\u6237 root \u53ef\u7528\u4e8eSSH/UART\u8bbf\u95ee\uff0c\u5bc6\u7801\u4e3a root \u3002Web\u754c\u9762\u5e10\u6237\u79f0\u4e3a admin \uff0c\u5bc6\u7801\u4e3a admin \u3002PiKVM\u5e10\u6237\u4e0d\u80fd\u7528\u4e8eSSH\u8bbf\u95ee\uff0c\u53cd\u4e4b\u4ea6\u7136\u3002 \u8981\u66f4\u6539\u5bc6\u7801\uff0c\u8bf7\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\uff08\u5728root\u7528\u6237\u4e0b\uff09\uff1a su - # \u5982\u679c\u60a8\u5728Webterm\u4e2d rw # \u5207\u6362\u6587\u4ef6\u7cfb\u7edf\u4e3a\u8bfb\u5199\u6a21\u5f0f passwd root # \u66f4\u6539\u64cd\u4f5c\u7cfb\u7edfroot\u5bc6\u7801 kvmd-htpasswd set admin # \u66f4\u6539Web\u754c\u9762\u7ba1\u7406\u5458\u5bc6\u7801 ro # \u5207\u6362\u56de\u53ea\u8bfb\u6a21\u5f0f \u5982\u679c\u60a8\u4f7f\u7528\u7684\u662fBliKVM\uff0cWeb\u754c\u9762\u5e10\u6237\u79f0\u4e3a admin \uff0c\u5bc6\u7801\u4e3a admin ,\u7ec8\u7aef\u7528\u6237\u540d\u79f0\u4e3a blikvm \uff0c\u5bc6\u7801\u4e3a blikvm \u3002 \u5982\u4f55\u6dfb\u52a0\u53e6\u4e00\u4e2a\u7528\u6237\uff1f \u5982\u679c\u60a8\u4f7f\u7528PiKVM\u8f6f\u4ef6\uff0c\u5982\u4e0a\u6240\u8ff0\uff0c\u60a8\u9700\u8981\u521b\u5efa2\u4e2a\u5e10\u6237\uff0c\u4e00\u4e2a\u7528\u4e8eShell\uff0c\u53e6\u4e00\u4e2a\u7528\u4e8ePiKVM Web\u754c\u9762\u3002 \u5982\u679c\u60a8\u9700\u8981\u4e3aPiKVM Web\u754c\u9762\u6dfb\u52a0\u5176\u4ed6\u7528\u6237\uff0c\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\uff1a # rw # su - # kvmd-htpasswd set  # \u6dfb\u52a0\u65b0\u7528\u6237 # kvmd-htpasswd set  # \u8bbe\u7f6e\u5bc6\u7801\uff08\u53ea\u8981\u7528\u6237\u5b58\u5728\uff09 # kvmd-htpasswd del  # \u5220\u9664\u7528\u6237 \u8981\u6dfb\u52a0Shell/\u7ec8\u7aef\u5e10\u6237\uff1a # rw # su - # adduser  # passwd  \u8bf7\u6ce8\u610f\uff0c\u6dfb\u52a0\u7684\u7528\u6237\u8d8a\u591a\uff0c\u8bbf\u95ee\u6d41\u5a92\u4f53\u65f6\u5e27\u7387\u4f1a\u964d\u4f4e\u3002","title":"\u7b2c\u4e00\u6b65"},{"location":"faq/#_3","text":"BLIKVM\u6839\u672c\u6ca1\u6709\u663e\u793a\u6765\u81ea\u8ba1\u7b97\u673a\u7684\u89c6\u9891 \u8bf7\u4ed4\u7ec6\u68c0\u67e5\u89c6\u9891\u6355\u83b7\u8bbe\u5907\u7684\u8fde\u63a5\u60c5\u51b5\u3002\u5bf9\u4e8eCSI\u6865\u63a5\u5668\uff0c\u5e94\u8fde\u63a5\u5230\u76f8\u673a\u7aef\u53e3\u3002 \u6709\u4e9b\u7b14\u8bb0\u672c\u7535\u8111\u5728\u60a8\u5207\u6362\u8f93\u51fa\u4e4b\u524d\uff08\u901a\u5e38\u901a\u8fc7\u952e\u76d8\u4e0a\u7684FN +\u548cF5\u952e\uff09\u4e0d\u4f1a\u8f93\u51fa\u4efb\u4f55\u4fe1\u53f7\u3002 \u60a8\u7684\u8ba1\u7b97\u673a\u53ef\u80fd\u5df2\u7ecf\u5c06\u663e\u793a\u5668\u8bbe\u7f6e\u4e3a\u7761\u7720\u6a21\u5f0f\u3002\u79fb\u52a8\u9f20\u6807\u4ee5\u5173\u95ed\u7761\u7720\u6a21\u5f0f\u3002 \u5bf9\u4e8eWindows\u7cfb\u7edf\uff0c\u60a8\u53ef\u80fd\u9700\u8981\u68c0\u67e5\u6d3b\u52a8\u4fe1\u53f7\u5206\u8fa8\u7387\u3002\u8981\u66f4\u6539\u6d3b\u52a8\u4fe1\u53f7\u5206\u8fa8\u7387\uff0c\u8bf7\u8f6c\u5230\u201c\u8bbe\u7f6e\u201d>\u201c\u7cfb\u7edf\u201d>\u201c\u663e\u793a\u201d>\u201c\u9ad8\u7ea7\u663e\u793a\u8bbe\u7f6e\u201d>\u201c\u663e\u793a\u9002\u914d\u5668\u5c5e\u6027\u201d\uff0c\u7136\u540e\u70b9\u51fb\u201c\u5217\u51fa\u6240\u6709\u6a21\u5f0f\u201d\uff0c\u9009\u62e9\u6240\u9700\u7684\u6a21\u5f0f\u3002\u5c1d\u8bd5\u4e0d\u540c\u7684\u5237\u65b0\u7387\u8bbe\u7f6e\u3002 \u5728\u5df2\u542f\u52a8\u7684\u64cd\u4f5c\u7cfb\u7edf\u4e2d\u53ef\u4ee5\u770b\u5230\u89c6\u9891\uff0c\u4f46\u5728BIOS/UEFI\u4e2d\u770b\u4e0d\u5230 \u5f53\u4f7f\u7528CSI\u6865\u63a5\u5668\u65f6\uff0cIntel NUC\u3001GA-H77-DS3H\u548c\u4e00\u4e9b\u5176\u4ed6\u8bbe\u5907\u4e0a\u4f1a\u51fa\u73b0\u6b64\u95ee\u9898\u3002\u60a8\u53ea\u9700\u8981\u66f4\u6539EDID\u6570\u636e\uff0c\u8fd9\u662fCSI\u6865\u63a5\u5668\u5411\u8ba1\u7b97\u673a\u62a5\u544a\u7684\u652f\u6301\u7684\u5206\u8fa8\u7387\u4fe1\u606f\u3002 BIOS/UEFI\u5206\u8fa8\u7387\u51fa\u73b0\u6545\u969c\u6216\u9519\u8bef \u5728\u67d0\u4e9b\u4e3b\u677f\u4e0a\uff0cBIOS\u53ef\u80fd\u4ee5\u8f83\u4f4e\u7684\u5206\u8fa8\u7387\u663e\u793a\uff0c\u6216\u51fa\u73b0\u4e00\u4e9b\u6e32\u67d3\u95ee\u9898/\u6545\u969c\uff0c\u7279\u522b\u662f\u5728\u8f83\u65b0\u7684ASUS\u4e3b\u677f\u4e0a\u3002\u5982\u4e0b\u56fe\u6240\u793a\uff1a \u60a8\u53ef\u4ee5\u901a\u8fc7\u5728BIOS\u4e2d\u542f\u7528 \u517c\u5bb9\u6027\u652f\u6301\u6a21\u5757\uff08CSM\uff09 \u6765\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u901a\u5e38\u4f4d\u4e8e \u5f15\u5bfc \u9009\u9879\u4e0b\u3002 \u5982\u679c\u60a8\u65e0\u6cd5\u6216\u4e0d\u60f3\u542f\u7528CSM\uff0c\u60a8\u53ef\u4ee5\u5c1d\u8bd5\u8fde\u63a5\u4e00\u4e2aDisplayPort\uff08DP\uff09\u663e\u793a\u5668\u6216 \u865a\u62df\u63d2\u5934 \u3002\u5982\u679c\u62d4\u6389DP\u7535\u7f06/\u8f6c\u63a5\u5668\uff0c\u95ee\u9898\u5c06\u91cd\u65b0\u51fa\u73b0\u3002 \u5982\u679c\u4e0a\u8ff0\u65b9\u6cd5\u90fd\u4e0d\u8d77\u4f5c\u7528\uff0c\u8bf7\u5c1d\u8bd5\u5148\u8fde\u63a5DP\u7535\u7f06\uff0c\u7136\u540e\u542f\u52a8\u5230BIOS\uff0c\u7981\u7528CSM\u5e76\u5173\u673a\uff08\u4e0d\u8981\u91cd\u65b0\u542f\u52a8\uff09\u60a8\u7684\u8ba1\u7b97\u673a\u3002\u7136\u540e\uff0c\u5728\u518d\u6b21\u542f\u52a8\u5230BIOS\u5e76\u542f\u7528CSM\u4e4b\u524d\uff0c\u8fde\u63a5HDMI\u5e76\u518d\u6b21\u6253\u5f00\u8ba1\u7b97\u673a\u3002 GRUB2\u4e2d\u6ca1\u6709\u89c6\u9891\uff0c\u4f46\u4e4b\u524d\u548c\u4e4b\u540e\u90fd\u6709 \u6709\u65f6\u8fd9\u53ef\u80fd\u662f\u7531\u4e8eBIOS/UEFI\u7684\u7279\u5b9a\u95ee\u9898\u4ee5\u53caGRUB2\u4e0e\u89c6\u9891\u7684\u5de5\u4f5c\u65b9\u5f0f\u6240\u5bfc\u81f4\u7684\u3002 \u60a8\u53ef\u4ee5\u901a\u8fc7\u5728BIOS\u4e2d\u542f\u7528 \u517c\u5bb9\u6027\u652f\u6301\u6a21\u5757\uff08CSM\uff09 \u6765\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u901a\u5e38\u4f4d\u4e8e \u5f15\u5bfc \u9009\u9879\u4e0b\u3002\u89c6\u9891\u6a21\u5f0f\u4e5f\u4f4d\u4e8e\u540c\u4e00\u90e8\u5206\u3002\u5c06 \u89c6\u9891 \u6a21\u5f0f\u4ece UEFI \u5207\u6362\u4e3a Legacy \u3002 Linux + Awesome WM\u6ca1\u6709\u8ba1\u7b97\u673a\u56fe\u50cf \u6709\u65f6\uff0c\u5728Linux\u4e0a\u4f7f\u7528Awesome WM\u53ef\u80fd\u65e0\u6cd5\u8bc6\u522b\u7535\u7f06\u7684\u89c6\u9891\u8f93\u51fa\u66f4\u6539\u3002\u4e5f\u5c31\u662f\u8bf4\uff0c\u5982\u679c\u7535\u7f06\u5148\u63d2\u5165\u663e\u793a\u5668\uff0c\u7136\u540e\u518d\u8fde\u63a5\u5230BLIKVM\uff0c\u53ef\u80fd\u4f1a\u5bfc\u81f4\u60a8\u770b\u4e0d\u5230\u56fe\u50cf\u3002\u8fd9\u4f3c\u4e4e\u662fAwesome WM\u7684\u95ee\u9898\uff0c\u56e0\u4e3a\u4f8b\u5982\u5728KDE\u4e2d\uff0c\u8fd9\u79cd\u60c5\u51b5\u65e0\u6cd5\u590d\u73b0\u3002\u5982\u679c\u60a8\u5728\u8fde\u63a5BLIKVM\u540e\u542f\u52a8\u5de5\u4f5c\u7ad9\uff0c\u4e00\u5207\u90fd\u5c06\u6b63\u5e38\u5de5\u4f5c\u3002","title":"\u89c6\u9891\u95ee\u9898"},{"location":"faq/#usbu","text":"USB OTG\u7aef\u53e3\u7684\u901f\u5ea6\u662f\u591a\u5c11\uff1f \u6839\u636e\u5b98\u65b9\u7684RPI\u6587\u6863\uff0c\u8fd9\u662fSoC\u7684\u9650\u5236\u3002OTG\u7aef\u53e3\u53ea\u652f\u6301USB 2.0\uff0c\u56e0\u6b64\u901f\u5ea6\u9650\u5236\u4e3a455 Mbit/s\u3002 \u4e3a\u4ec0\u4e48\u65e0\u6cd5\u6355\u83b7\u67d0\u4e9b\u5b9e\u4f53\u952e\u76d8\u7684\u952e\u76d8\u5feb\u6377\u952e\uff0c\u4f46\u53ef\u4ee5\u6355\u83b7\u865a\u62df\u952e\u76d8\u7684\u952e\u76d8\u5feb\u6377\u952e\uff1f\u4f8b\u5982\uff0c\u65e0\u6cd5\u6355\u83b7Mac\u7535\u8111\u7684F11\u6309\u952e \u8fd9\u662f\u56e0\u4e3a\u4e00\u4e9b\u5feb\u6377\u952e\u5df2\u7ecf\u88ab\u64cd\u4f5c\u7cfb\u7edf\u4f7f\u7528\u4e86\uff0c\u4f8b\u5982\u5728 macOS \u4e2d\uff0cF11 \u88ab\u9ed8\u8ba4\u5206\u914d\u7ed9\u4e86\u201c\u663e\u793a\u684c\u9762\u201d\u7684\u529f\u80fd\u3002\u5f53\u60a8\u5728Web\u754c\u9762\u6309\u4e0bF11\u65f6\uff0c\u952e\u76d8\u4e8b\u4ef6\u9996\u5148\u88ab\u64cd\u4f5c\u7cfb\u7edf\u6355\u83b7\uff0c\u5982\u679c\u64cd\u4f5c\u7cfb\u7edf\u6ce8\u518c\u4e86\u56de\u8c03\u51fd\u6570\uff0c\u952e\u76d8\u4e8b\u4ef6\u5c06\u4e0d\u4f1a\u4f20\u9012\u7ed9\u5e94\u7528\u7a0b\u5e8f\u3002\u8981\u89e3\u51b3\u6b64\u95ee\u9898\uff0c\u60a8\u53ef\u4ee5\u5173\u95ed\u64cd\u4f5c\u7cfb\u7edf\u8bbe\u7f6e\u4e2d\u7684\u5feb\u6377\u952e\uff0c\u6216\u8005\u4f7f\u7528\u865a\u62df\u952e\u76d8\u3002","title":"USB\u95ee\u9898\uff08\u952e\u76d8\u3001\u9f20\u6807\u3001U\u76d8\u7b49\uff09"},{"location":"faq/#wi-fiatx","text":"\u5982\u679c\u4f7f\u7528PiKVM\u8f6f\u4ef6\uff0cWeb\u754c\u9762\u663e\u793a FAN \u9519\u8bef\uff01 \u7531\u4e8eBLIKVM\u786c\u4ef6\u4f7f\u7528\u7684\u98ce\u6247\u578b\u53f7\u4e0ePIKVM\u786c\u4ef6\u4e0d\u540c\uff0c\u56e0\u6b64\u5728pikvm\u7684\u6700\u65b0\u7cfb\u7edf\u4e2d\uff0c\u901a\u8fc7Web\u754c\u9762\u67e5\u770b\u98ce\u6247\u72b6\u6001\u53ef\u80fd\u4f1a\u5931\u8d25\u3002\u4f46\u8fd9\u4e0d\u4f1a\u5f71\u54cdBLIKVM\u98ce\u6247\u7684\u6b63\u5e38\u8fd0\u884c\u3002\u56e0\u6b64\uff0c\u5728\u4f7f\u7528PIKVM\u955c\u50cf\u65f6\uff0c\u53ea\u8981\u786e\u4fdd \u5b89\u88c5\u811a\u672c \u663e\u793aOK\uff0c\u5c31\u8868\u793akvmd\u98ce\u6247\u7a0b\u5e8f\u7684\u66f4\u65b0\u6210\u529f\u3002\u9ed8\u8ba4\u7a0b\u5e8f\u8bbe\u7f6e\u7684\u6e29\u5ea6\u9608\u503c\u4e3a\u6444\u6c0f60\u5ea6\u3002\u5f53\u68c0\u6d4b\u5230CPU\u6e29\u5ea6\u8d85\u8fc760\u6444\u6c0f\u5ea6\u65f6\uff0c\u98ce\u6247\u5c06\u4ee585%\u7684\u901f\u5ea6\u5f00\u59cb\u65cb\u8f6c\u3002\u5982\u679c\u8981\u4fee\u6539\u6e29\u5ea6\u9608\u503c\u548c\u901f\u5ea6\uff0c\u53ef\u4ee5\u4fee\u6539kvmd-fan.py\u811a\u672c\uff0c\u7136\u540e\u91cd\u65b0\u6267\u884cinstall.sh\u3002 \u6211\u6839\u672c\u65e0\u6cd5\u8fde\u63a5\u5230Wi-Fi\uff01 \u5982\u679c\u60a8\u7684\u8bbe\u5907\u65e0\u6cd5\u8fde\u63a5\u5230\u60a8\u8bbe\u7f6e\u7684Wi-Fi\u7f51\u7edc\uff0c\u8bf7\u68c0\u67e5\u60a8\u7684Wi-Fi\u63a5\u5165\u70b9\u4f7f\u7528\u76842.4GHz Wi-Fi\u4fe1\u9053\u3002\u5982\u679c\u4f7f\u7528\u4e8612\u523014\u4fe1\u9053\uff08\u67d0\u4e9b\u56fd\u5bb6\u7981\u6b62\u4f7f\u7528\u8fd9\u4e9b\u4fe1\u9053\uff09\uff0c\u8bf7\u5c1d\u8bd5\u4f7f\u75281\u523011\u4e4b\u95f4\u7684\u4fe1\u9053\u3002 BLIKVM\u663e\u793a\u4f4e\u7535\u538b\u8b66\u544a \u60a8\u662f\u5426\u4f7f\u7528\u4e86\u201c\u6b63\u786e\u201d\u7684\u7535\u6e90\u9002\u914d\u5668\uff1f\u800c\u4e0d\u662f\u81ea\u5df1\u62fc\u51d1\u7684\u9002\u914d\u5668\uff1f \u4e00\u4e9bUSB\u7535\u6e90\u9002\u914d\u5668\u5ba3\u4f20\u4e3a5V 2.1A\u6216\u66f4\u9ad8\uff0c\u4f46\u65e0\u6cd5\u63d0\u4f9b\u7a33\u5b9a\u76845V\u7535\u538b\u3002\u6700\u597d\u4f7f\u7528\u6811\u8393\u6d3e\u57fa\u91d1\u4f1a\u63a8\u8350\u7684\u7535\u6e90\u9002\u914d\u5668\u3002\u5176\u8f93\u51fa\u5e94\u4e3a5.1V\u548c3A\u76f4\u6d41\u7535\u538b\u3002 \u5f53\u6211\u4f7f\u7528PoE\u65f6\uff0c\u662f\u5426\u4ecd\u7136\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u6765\u9632\u6b62\u673a\u5668USB\u7684\u53cd\u5411\u4f9b\u7535\uff1f \u53ea\u6709HAT\u7248\u672c\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u6765\u9632\u6b62\u53cd\u5411\u4f9b\u7535\u3002\u901a\u5e38\uff0c\u5927\u591a\u6570\u4e3b\u673a\u8ba1\u7b97\u673a\u90fd\u6709\u53cd\u5411\u4f9b\u7535\u4fdd\u62a4\uff0c\u56e0\u6b64\u5728\u8fd9\u79cd\u60c5\u51b5\u4e0b\u4e0d\u9700\u8981\u4f7f\u7528\u7535\u6e90OTG\u5206\u7ebf\u5668\u3002 BLIKVM-CM4-V2.2\u548cBLIKVM-PCIe\u7248\u672c\u4e0d\u9700\u8981\u3002 \u5728\u4e00\u4e9b\u50cfBLIKVM-PCIe\u6216BLIKVM-CM4-V2.2\u8fd9\u6837\u7684\u677f\u5b50\u4e0a\u6709\u5f15\u5bfc\u5f15\u811a\uff0c\u5982\u4f55\u8fde\u63a5\uff1f \u5982\u679c\u5c06\u5b83\u4eec\u8fde\u63a5\u77ed\u8def\uff0cCM4\u5c06\u65e0\u6cd5\u6b63\u5e38\u542f\u52a8\uff0c\u800c\u5c06\u8fdb\u5165\u70e7\u5f55\u6620\u50cf\u6a21\u5f0f\u3002\u5982\u679c\u60a8\u7684\u786c\u4ef6\u7248\u672c\u7684\u5f15\u5bfc\u5f15\u811a\u53ea\u6709\u4e24\u4e2a\u5f15\u811a\uff0c\u4f7f\u7528\u8df3\u7ebf\u5e3d\u5c06\u8fd9\u4e24\u4e2a\u5f15\u811a\u8fde\u63a5\u8d77\u6765\uff0c\u5f62\u6210\u77ed\u8def\u3002\u5982\u679c\u60a8\u4e0d\u4f7f\u7528\u8df3\u7ebf\u5e3d\u6216\u53ea\u5c06\u5176\u63d2\u5165\u4e00\u4e2a\u5f15\u811a\uff0cCM4\u5c06\u6b63\u5e38\u542f\u52a8\u3002\u5982\u679c\u60a8\u4f7f\u7528\u7684\u662f\u4e09\u4e2a\u5f15\u5bfc\u5f15\u811a\u7684\u786c\u4ef6\u7248\u672c\uff0c\u8bf7\u4f7f\u7528\u8df3\u7ebf\u5e3d\u5c06GND\u548c\u53e6\u4e00\u4e2a\u975eGND\u5f15\u811a\u8fde\u63a5\u8d77\u6765\u4ee5\u793a\u77ed\u8def\uff0c\u5e76\u5c06\u8df3\u7ebf\u5e3d\u63d2\u5728\u4e24\u4e2aGND\u5f15\u811a\u4e0a\u6216\u4e0d\u4f7f\u7528\u8df3\u7ebf\u5e3d\uff0cCM4\u5c06\u6b63\u5e38\u542f\u52a8\u3002","title":"\u786c\u4ef6\u95ee\u9898\uff08Wi-Fi\u3001ATX\u7b49\uff09"},{"location":"faq/#web","text":"BliKVM OS\u5360\u7528\u7684\u7aef\u53e3\u6709\u54ea\u4e9b\uff0c\u5728\u7528\u516c\u7f51\u670d\u52a1\u5668\u8f6c\u53d1\u65f6\uff0c\u5e94\u8be5\u600e\u4e48\u505a\uff1f Web\u754c\u9762\u4e3ahttp\u534f\u8bae\uff0c\u5360\u7528\u7684\u662f80\u7aef\u53e3\uff1b \u5982\u679c\u60a8\u7684\u786c\u4ef6\u662fV1 V2 V3\uff0c\u4f7f\u7528\u7684\u662f\u662fweb-rtc\u4f20\u8f93\uff0c\u7aef\u53e3\u662f8188\uff1b \u5982\u679c\u60a8\u7684\u786c\u4ef6\u662fV4\uff0c\u4f7f\u7528\u7684\u662fmjepg\u4f20\u8f93\uff0c\u7aef\u53e3\u662f8008\uff1b \u6ce8\u610f\u7aef\u53e3\u4e0d\u652f\u6301\u88ab\u4fee\u6539\uff0c\u53ea\u80fd\u914d\u7f6e\u8f6c\u53d1\uff1b","title":"Web\u95ee\u9898"},{"location":"faq/#_4","text":"\u6211\u662f\u5426\u53ef\u4ee5\u540c\u65f6\u4f7f\u7528\u5e26eMMC\u7248\u672c\u7684CM4\u548cSD\u5361? \u4e0d\u53ef\u4ee5\uff0c\u56e0\u4e3a\u5728CM4\u786c\u4ef6\u8bbe\u8ba1\u4e0a\uff0c\u51e0\u4e2aSD\u5361\u7684\u5f15\u811a\u53ea\u5728lite\u7248\u672c\u4e2d\u662f\u53ef\u7528\u7684\uff0c\u4f60\u53ef\u4ee5\u5728\u6811\u8393\u6d3e\u5b98\u7f51\u627e\u5230\u8bf4\u660e\u3002","title":"\u6811\u8393\u6d3e\u76f8\u5173\u95ee\u9898"},{"location":"first_steps/","text":"\u521d\u6b65\u64cd\u4f5c \u9996\u6b21\u4e0a\u7535 \u53ef\u9009\uff1a\u8bbe\u7f6eWi-Fi\u8fde\u63a5 \u8bf7\u9605\u8bfb\u4ee5\u4e0b\u6ce8\u610f\u4e8b\u9879 \u6709\u7ebf\u4ee5\u592a\u7f51\u8fde\u63a5\u662f\u6700\u53ef\u9760\u7684\u65b9\u5f0f\uff0c\u56e0\u6b64\u6700\u597d\u4f7f\u7528 \u6709\u7ebf\u7535\u7f06 \u3002\u4f46\u6211\u4eec\u4e0d\u80fd\u963b\u6b62\u60a8\u4f7f\u7528\u65e0\u7ebf\u8fde\u63a5... :) \u786e\u8ba4\u60a8\u4f7f\u7528\u7684\u7248\u672c\u542b\u6709Wi-Fi\u529f\u80fd\uff0c\u5e76\u4e14Wi-Fi\u5929\u7ebf\u5df2\u5b89\u88c5. \u8bf7\u53c2\u8003 Wi-Fi\u8fde\u63a5\u6307\u5357 \uff0c\u5bf9\u60a8\u7684\u8bbe\u5907\u8fdb\u884cWi-Fi\u8bbe\u7f6e\uff1b \u7ed9\u8bbe\u5907\u4f9b\u7535\u3002 \u5728\u8bbe\u5907\u5b8c\u5168\u542f\u52a8\u524d\uff0c\u8bf7\u52ff\u5173\u95ed\u7535\u6e90 \u8bbf\u95eeBliKVM \u9ed8\u8ba4\u60c5\u51b5\u4e0b\uff0cBliKVM\u901a\u8fc7DHCP\u63a5\u6536\u52a8\u6001IP\u5730\u5740\u3002\u4f1a\u5728BliKVM\u663e\u793a\u5668\u4e0a\u663e\u793aIP\u5730\u5740\u3002\u5982\u679c\u60a8\u662fDIY\u786c\u4ef6\u6ca1\u6709\u663e\u793a\u5668\uff0c\u8bf7\u4f7f\u7528\u4ee5\u4e0b\u63d0\u793a\uff1a \u5728\u7f51\u7edc\u4e2d\u67e5\u627eBliKVM \u60a8\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u65b9\u6cd5\u786e\u5b9aBliKVM\u7684IP\u5730\u5740\uff1a \u5e38\u7528\u65b9\u6cd5\uff1a \u6253\u5f00\u8def\u7531\u5668\u7684Web\u754c\u9762\uff0c\u5e76\u67e5\u627e\u5df2\u5206\u914d\u7684IP\u5730\u5740\u5217\u8868\u3002\u5177\u4f53\u65b9\u6cd5\u53d6\u51b3\u4e8e\u8def\u7531\u5668\u578b\u53f7\u3002 \u4ec5\u9650Linux\uff1a \u4f7f\u7528\u547d\u4ee4 arp-scan --localnet \u3002 Linux\u3001MacOS\u3001Windows\uff1a \u4e0b\u8f7d\u5e76\u8fd0\u884c Angry IP Scanner \u3002 Windows PowerShell\uff1a \u4f7f\u7528\u547d\u4ee4 arp -a \u3002 \u5728\u4e0b\u9762\u7684\u793a\u4f8b\u4e2d\uff0c\u8ba9\u6211\u4eec\u5047\u8bbe\u60a8\u7684BliKVM\u5df2\u83b7\u5f97\u5730\u5740 192.168.0.100 \uff0c\u60a8\u5df2\u7ecf\u6210\u529f\u4f7f\u7528\u4e0a\u8ff0\u6307\u793a\u627e\u5230\u4e86\u8be5\u5730\u5740\u3002 \u8bbf\u95eeBliKVM Web\u754c\u9762 \u5728 \u5927\u591a\u6570 \u7f51\u7edc\u4e2d\uff0c\u60a8\u53ef\u4ee5\u5728\u4efb\u4f55\u6d4f\u89c8\u5668\u4e2d\u4f7f\u7528\u4ee5\u4e0bURL\u8bbf\u95eeBliKVM\uff1a http://192.168.0.100/ \u3002Google Chrome\uff08Chromium\uff09\u3001Firefox\u548cSafari\u4e0e\u542f\u75280\u4e2a\u6269\u5c55\u7684\u60c5\u51b5\u4e0b\u6548\u679c\u6700\u4f73\uff0c\u5982\u679c\u5176\u4e2d\u4e00\u4e2a\u53ef\u4ee5\u6b63\u5e38\u5de5\u4f5c\u800c\u53e6\u4e00\u4e2a\u65e0\u6cd5\u6b63\u5e38\u5de5\u4f5c\uff0c\u5219\u53ef\u80fd\u662f\u6d4f\u89c8\u5668/\u6269\u5c55\u7684\u95ee\u9898\u3002\u5efa\u8bae\u60a8\u4f7f\u7528\u79c1\u5bc6\u6d4f\u89c8\u7a97\u53e3\u6216\u65e0\u75d5\u6a21\u5f0f\u3002\u4e0d\u652f\u6301Internet Explorer\u548c\u65e9\u671f\u7248\u672c\u7684Microsoft Edge\uff08\u975eChromium\u7248\u672c\uff09\u3002 \u9ed8\u8ba4\u7528\u6237\u540d\u4e3a admin \uff0c\u5bc6\u7801\u4e5f\u4e3a admin \u3002 \u767b\u5f55\u540e\uff0c\u60a8\u5c06\u83b7\u5f97\u8bbf\u95ee\u4e3b\u8981\u529f\u80fd\u83dc\u5355\u7684\u6743\u9650\u3002\u4f7f\u7528Web\u7684\u4fee\u6539\u8d26\u53f7\u5bc6\u7801\u529f\u80fd\uff0c\u60a8\u53ef\u4ee5\u66f4\u6539\u7cfb\u7edf\u8bbe\u7f6e\u548c\u5bc6\u7801\u3002 \u6ce8\u610f\u5f53\u524d\u8bbf\u95eeBliKVM web\u662fhttp\uff0c\u800c\u975ehttps \u901a\u8fc7SSH\u8bbf\u95eeBliKVM SSH\u662fLinux\u4e16\u754c\u4e2d\u6700\u5e38\u7528\u7684\u8fdc\u7a0b\u8bbf\u95ee\u65b9\u6cd5\u3002\u60a8\u53ef\u4ee5\u901a\u8fc7SSH\u8bbf\u95eeBliKVM\u3002\u6b64\u65b9\u6cd5\u7528\u4e8e\u7ba1\u7406\u8bbe\u5907\uff1a Linux\u3001MacOS\uff1a \u6253\u5f00\u4efb\u4f55\u7ec8\u7aef\u5e94\u7528\u7a0b\u5e8f\uff0c\u7136\u540e\u8fd0\u884c\uff1a ssh blikvm@192.168.0.100 \u3002 Windows\uff1a \u4f7f\u7528 PuTTY \u8fdb\u884c\u64cd\u4f5c\u3002 \u9ed8\u8ba4\u7684 blikvm \u7528\u6237\u5bc6\u7801\u4e3a blikvm \u3002 \u60a8\u53ef\u4ee5\u4f7f\u7528 sudo -i \u83b7\u5f97root\u6743\u9650\u3002 \u53ef\u9009\uff1a\u66f4\u65b0BliKVM\u8f6f\u4ef6 \u8fd9\u90e8\u5206\u4e0d\u662f\u5fc5\u9700\u7684\uff0c\u4ec5\u5728\u60a8\u5728BliKVM\u65c1\u8fb9\u4ee5\u4fbf\u6062\u590d\u5b83\u65f6\u624d\u5e94\u6267\u884c\uff0c\u53ef\u4ee5\u53c2\u8003 \u66f4\u65b0\u8f6f\u4ef6\u6307\u5357 \u5b8c\u6210\uff1b BliKVM OS\u7ec8\u7aef\u4f7f\u7528\u6ce8\u610f\u4e8b\u9879 \u4e00\u4e9b\u914d\u7f6e\u66f4\u6539\u90fd\u5fc5\u987b\u5728 root \u7528\u6237\uff08\u5373\u7ba1\u7406\u5458\uff09\u4e0b\u8fdb\u884c\u3002 \u83b7\u53d6root\u6743\u9650 \u5982\u679c\u60a8\u901a\u8fc7SSH\u767b\u5f55\uff0c\u9700\u4f7f\u7528 sudo -i \u83b7\u5f97root\u6743\u9650\uff1b v1\u3001v2\u3001v3\u7248\u672c\u7684BliKVM\u5b58\u50a8\u5361\u4ee5\u53ea\u8bfb\u6a21\u5f0f\u6302\u8f7d\u3002\u8fd9\u6837\u53ef\u4ee5\u5728\u7a81\u7136\u505c\u7535\u65f6\u4fdd\u62a4\u6587\u4ef6\u7cfb\u7edf\u514d\u53d7\u635f\u574f\u3002\u8981\u7f16\u8f91\u4efb\u4f55\u6587\u4ef6\u5e76\u8fdb\u884c\u66f4\u6539\uff0c\u9700\u8981\u5c06\u6587\u4ef6\u7cfb\u7edf\u91cd\u65b0\u6302\u8f7d\u4e3a\u8bfb\u5199\u6a21\u5f0f\u3002\u60a8\u53ef\u4ee5\u901a\u8fc7\u7ec8\u7aef\u662f\u6709\u6709ro\u6216rw\u5b57\u6837\u6765\u5224\u65ad\u5f53\u524d\u7cfb\u7edf\u6a21\u5f0f\u3002 \u542f\u7528\u5199\u5165\u6a21\u5f0f \u8981\u542f\u7528\u5199\u5165\u6a21\u5f0f\uff0c\u8bf7\u8fd0\u884c rw \u547d\u4ee4\u3002 \u8981\u7981\u7528\u5199\u5165\u6a21\u5f0f\uff0c\u8bf7\u8fd0\u884c ro \u547d\u4ee4\u3002 \u5982\u679c\u6536\u5230 \"Device is busy\"\uff08\u8bbe\u5907\u5fd9\uff09\u7684\u6d88\u606f\uff0c\u8bf7\u6267\u884c reboot \u547d\u4ee4\u3002 \u4e0b\u4e00\u6b65\u662f\u4ec0\u4e48\uff1f \u4f7f\u7528 \u7aef\u53e3\u8f6c\u53d1 \u6216 Tailscale VPN \u8bbe\u7f6e\u4e92\u8054\u7f51\u8bbf\u95ee\u3002 \u4f7f\u7528\u5de6\u4fa7\u7684\u76ee\u5f55\u5bfc\u822a\u63a2\u7d22BliKVM\u7684\u529f\u80fd\u3002 \u52a0\u5165\u6211\u4eec\u7684 Discord \u4e0e\u793e\u533a\u548c\u5f00\u53d1\u4eba\u5458\u4ea4\u6d41\u3002 \u67e5\u770b GitHub - BliKVM \u662f\u4e00\u4e2a\u5f00\u6e90\u7684\u9879\u76ee\uff01 \u5e38\u89c1\u95ee\u9898\u548c\u6545\u969c\u6392\u9664 \u5982\u679c\u60a8\u6709\u4efb\u4f55\u95ee\u9898\u6216\u9047\u5230\u95ee\u9898\uff0c\u8bf7\u67e5\u770b \u5e38\u89c1\u95ee\u9898 \u3002 \u771f\u7684\uff0c\u5b83\u975e\u5e38\u6709\u7528\uff01\u6211\u4eec\u53ef\u80fd\u5df2\u7ecf\u4e3a\u60a8\u627e\u5230\u89e3\u51b3\u65b9\u6848\u4e86 :) \u5982\u679c\u9700\u8981\u4efb\u4f55\u5176\u4ed6\u5e2e\u52a9\u548c\u652f\u6301\uff0c\u60a8\u53ef\u4ee5\u901a\u8fc7 Discord\u804a\u5929 \u4e0e\u6211\u4eec\u8054\u7cfb\u3002","title":"\u7b2c\u4e00\u6b65"},{"location":"first_steps/#_1","text":"","title":"\u521d\u6b65\u64cd\u4f5c"},{"location":"first_steps/#_2","text":"\u53ef\u9009\uff1a\u8bbe\u7f6eWi-Fi\u8fde\u63a5 \u8bf7\u9605\u8bfb\u4ee5\u4e0b\u6ce8\u610f\u4e8b\u9879 \u6709\u7ebf\u4ee5\u592a\u7f51\u8fde\u63a5\u662f\u6700\u53ef\u9760\u7684\u65b9\u5f0f\uff0c\u56e0\u6b64\u6700\u597d\u4f7f\u7528 \u6709\u7ebf\u7535\u7f06 \u3002\u4f46\u6211\u4eec\u4e0d\u80fd\u963b\u6b62\u60a8\u4f7f\u7528\u65e0\u7ebf\u8fde\u63a5... :) \u786e\u8ba4\u60a8\u4f7f\u7528\u7684\u7248\u672c\u542b\u6709Wi-Fi\u529f\u80fd\uff0c\u5e76\u4e14Wi-Fi\u5929\u7ebf\u5df2\u5b89\u88c5. \u8bf7\u53c2\u8003 Wi-Fi\u8fde\u63a5\u6307\u5357 \uff0c\u5bf9\u60a8\u7684\u8bbe\u5907\u8fdb\u884cWi-Fi\u8bbe\u7f6e\uff1b \u7ed9\u8bbe\u5907\u4f9b\u7535\u3002 \u5728\u8bbe\u5907\u5b8c\u5168\u542f\u52a8\u524d\uff0c\u8bf7\u52ff\u5173\u95ed\u7535\u6e90","title":"\u9996\u6b21\u4e0a\u7535"},{"location":"first_steps/#blikvm","text":"\u9ed8\u8ba4\u60c5\u51b5\u4e0b\uff0cBliKVM\u901a\u8fc7DHCP\u63a5\u6536\u52a8\u6001IP\u5730\u5740\u3002\u4f1a\u5728BliKVM\u663e\u793a\u5668\u4e0a\u663e\u793aIP\u5730\u5740\u3002\u5982\u679c\u60a8\u662fDIY\u786c\u4ef6\u6ca1\u6709\u663e\u793a\u5668\uff0c\u8bf7\u4f7f\u7528\u4ee5\u4e0b\u63d0\u793a\uff1a \u5728\u7f51\u7edc\u4e2d\u67e5\u627eBliKVM \u60a8\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u65b9\u6cd5\u786e\u5b9aBliKVM\u7684IP\u5730\u5740\uff1a \u5e38\u7528\u65b9\u6cd5\uff1a \u6253\u5f00\u8def\u7531\u5668\u7684Web\u754c\u9762\uff0c\u5e76\u67e5\u627e\u5df2\u5206\u914d\u7684IP\u5730\u5740\u5217\u8868\u3002\u5177\u4f53\u65b9\u6cd5\u53d6\u51b3\u4e8e\u8def\u7531\u5668\u578b\u53f7\u3002 \u4ec5\u9650Linux\uff1a \u4f7f\u7528\u547d\u4ee4 arp-scan --localnet \u3002 Linux\u3001MacOS\u3001Windows\uff1a \u4e0b\u8f7d\u5e76\u8fd0\u884c Angry IP Scanner \u3002 Windows PowerShell\uff1a \u4f7f\u7528\u547d\u4ee4 arp -a \u3002 \u5728\u4e0b\u9762\u7684\u793a\u4f8b\u4e2d\uff0c\u8ba9\u6211\u4eec\u5047\u8bbe\u60a8\u7684BliKVM\u5df2\u83b7\u5f97\u5730\u5740 192.168.0.100 \uff0c\u60a8\u5df2\u7ecf\u6210\u529f\u4f7f\u7528\u4e0a\u8ff0\u6307\u793a\u627e\u5230\u4e86\u8be5\u5730\u5740\u3002 \u8bbf\u95eeBliKVM Web\u754c\u9762 \u5728 \u5927\u591a\u6570 \u7f51\u7edc\u4e2d\uff0c\u60a8\u53ef\u4ee5\u5728\u4efb\u4f55\u6d4f\u89c8\u5668\u4e2d\u4f7f\u7528\u4ee5\u4e0bURL\u8bbf\u95eeBliKVM\uff1a http://192.168.0.100/ \u3002Google Chrome\uff08Chromium\uff09\u3001Firefox\u548cSafari\u4e0e\u542f\u75280\u4e2a\u6269\u5c55\u7684\u60c5\u51b5\u4e0b\u6548\u679c\u6700\u4f73\uff0c\u5982\u679c\u5176\u4e2d\u4e00\u4e2a\u53ef\u4ee5\u6b63\u5e38\u5de5\u4f5c\u800c\u53e6\u4e00\u4e2a\u65e0\u6cd5\u6b63\u5e38\u5de5\u4f5c\uff0c\u5219\u53ef\u80fd\u662f\u6d4f\u89c8\u5668/\u6269\u5c55\u7684\u95ee\u9898\u3002\u5efa\u8bae\u60a8\u4f7f\u7528\u79c1\u5bc6\u6d4f\u89c8\u7a97\u53e3\u6216\u65e0\u75d5\u6a21\u5f0f\u3002\u4e0d\u652f\u6301Internet Explorer\u548c\u65e9\u671f\u7248\u672c\u7684Microsoft Edge\uff08\u975eChromium\u7248\u672c\uff09\u3002 \u9ed8\u8ba4\u7528\u6237\u540d\u4e3a admin \uff0c\u5bc6\u7801\u4e5f\u4e3a admin \u3002 \u767b\u5f55\u540e\uff0c\u60a8\u5c06\u83b7\u5f97\u8bbf\u95ee\u4e3b\u8981\u529f\u80fd\u83dc\u5355\u7684\u6743\u9650\u3002\u4f7f\u7528Web\u7684\u4fee\u6539\u8d26\u53f7\u5bc6\u7801\u529f\u80fd\uff0c\u60a8\u53ef\u4ee5\u66f4\u6539\u7cfb\u7edf\u8bbe\u7f6e\u548c\u5bc6\u7801\u3002 \u6ce8\u610f\u5f53\u524d\u8bbf\u95eeBliKVM web\u662fhttp\uff0c\u800c\u975ehttps \u901a\u8fc7SSH\u8bbf\u95eeBliKVM SSH\u662fLinux\u4e16\u754c\u4e2d\u6700\u5e38\u7528\u7684\u8fdc\u7a0b\u8bbf\u95ee\u65b9\u6cd5\u3002\u60a8\u53ef\u4ee5\u901a\u8fc7SSH\u8bbf\u95eeBliKVM\u3002\u6b64\u65b9\u6cd5\u7528\u4e8e\u7ba1\u7406\u8bbe\u5907\uff1a Linux\u3001MacOS\uff1a \u6253\u5f00\u4efb\u4f55\u7ec8\u7aef\u5e94\u7528\u7a0b\u5e8f\uff0c\u7136\u540e\u8fd0\u884c\uff1a ssh blikvm@192.168.0.100 \u3002 Windows\uff1a \u4f7f\u7528 PuTTY \u8fdb\u884c\u64cd\u4f5c\u3002 \u9ed8\u8ba4\u7684 blikvm \u7528\u6237\u5bc6\u7801\u4e3a blikvm \u3002 \u60a8\u53ef\u4ee5\u4f7f\u7528 sudo -i \u83b7\u5f97root\u6743\u9650\u3002 \u53ef\u9009\uff1a\u66f4\u65b0BliKVM\u8f6f\u4ef6 \u8fd9\u90e8\u5206\u4e0d\u662f\u5fc5\u9700\u7684\uff0c\u4ec5\u5728\u60a8\u5728BliKVM\u65c1\u8fb9\u4ee5\u4fbf\u6062\u590d\u5b83\u65f6\u624d\u5e94\u6267\u884c\uff0c\u53ef\u4ee5\u53c2\u8003 \u66f4\u65b0\u8f6f\u4ef6\u6307\u5357 \u5b8c\u6210\uff1b","title":"\u8bbf\u95eeBliKVM"},{"location":"first_steps/#blikvm-os","text":"\u4e00\u4e9b\u914d\u7f6e\u66f4\u6539\u90fd\u5fc5\u987b\u5728 root \u7528\u6237\uff08\u5373\u7ba1\u7406\u5458\uff09\u4e0b\u8fdb\u884c\u3002 \u83b7\u53d6root\u6743\u9650 \u5982\u679c\u60a8\u901a\u8fc7SSH\u767b\u5f55\uff0c\u9700\u4f7f\u7528 sudo -i \u83b7\u5f97root\u6743\u9650\uff1b v1\u3001v2\u3001v3\u7248\u672c\u7684BliKVM\u5b58\u50a8\u5361\u4ee5\u53ea\u8bfb\u6a21\u5f0f\u6302\u8f7d\u3002\u8fd9\u6837\u53ef\u4ee5\u5728\u7a81\u7136\u505c\u7535\u65f6\u4fdd\u62a4\u6587\u4ef6\u7cfb\u7edf\u514d\u53d7\u635f\u574f\u3002\u8981\u7f16\u8f91\u4efb\u4f55\u6587\u4ef6\u5e76\u8fdb\u884c\u66f4\u6539\uff0c\u9700\u8981\u5c06\u6587\u4ef6\u7cfb\u7edf\u91cd\u65b0\u6302\u8f7d\u4e3a\u8bfb\u5199\u6a21\u5f0f\u3002\u60a8\u53ef\u4ee5\u901a\u8fc7\u7ec8\u7aef\u662f\u6709\u6709ro\u6216rw\u5b57\u6837\u6765\u5224\u65ad\u5f53\u524d\u7cfb\u7edf\u6a21\u5f0f\u3002 \u542f\u7528\u5199\u5165\u6a21\u5f0f \u8981\u542f\u7528\u5199\u5165\u6a21\u5f0f\uff0c\u8bf7\u8fd0\u884c rw \u547d\u4ee4\u3002 \u8981\u7981\u7528\u5199\u5165\u6a21\u5f0f\uff0c\u8bf7\u8fd0\u884c ro \u547d\u4ee4\u3002 \u5982\u679c\u6536\u5230 \"Device is busy\"\uff08\u8bbe\u5907\u5fd9\uff09\u7684\u6d88\u606f\uff0c\u8bf7\u6267\u884c reboot \u547d\u4ee4\u3002","title":"BliKVM OS\u7ec8\u7aef\u4f7f\u7528\u6ce8\u610f\u4e8b\u9879"},{"location":"first_steps/#_3","text":"\u4f7f\u7528 \u7aef\u53e3\u8f6c\u53d1 \u6216 Tailscale VPN \u8bbe\u7f6e\u4e92\u8054\u7f51\u8bbf\u95ee\u3002 \u4f7f\u7528\u5de6\u4fa7\u7684\u76ee\u5f55\u5bfc\u822a\u63a2\u7d22BliKVM\u7684\u529f\u80fd\u3002 \u52a0\u5165\u6211\u4eec\u7684 Discord \u4e0e\u793e\u533a\u548c\u5f00\u53d1\u4eba\u5458\u4ea4\u6d41\u3002 \u67e5\u770b GitHub - BliKVM \u662f\u4e00\u4e2a\u5f00\u6e90\u7684\u9879\u76ee\uff01","title":"\u4e0b\u4e00\u6b65\u662f\u4ec0\u4e48\uff1f"},{"location":"first_steps/#_4","text":"\u5982\u679c\u60a8\u6709\u4efb\u4f55\u95ee\u9898\u6216\u9047\u5230\u95ee\u9898\uff0c\u8bf7\u67e5\u770b \u5e38\u89c1\u95ee\u9898 \u3002 \u771f\u7684\uff0c\u5b83\u975e\u5e38\u6709\u7528\uff01\u6211\u4eec\u53ef\u80fd\u5df2\u7ecf\u4e3a\u60a8\u627e\u5230\u89e3\u51b3\u65b9\u6848\u4e86 :) \u5982\u679c\u9700\u8981\u4efb\u4f55\u5176\u4ed6\u5e2e\u52a9\u548c\u652f\u6301\uff0c\u60a8\u53ef\u4ee5\u901a\u8fc7 Discord\u804a\u5929 \u4e0e\u6211\u4eec\u8054\u7cfb\u3002","title":"\u5e38\u89c1\u95ee\u9898\u548c\u6545\u969c\u6392\u9664"},{"location":"flashing_os/","text":"\u70e7\u5f55\u955c\u50cf Micro-SD\u5361\u914d\u7f6e \u6700\u5c0f\u5efa\u8bae 16 Gb \u4ee5\u4e0a \u63a8\u8350\u4f7f\u7528 Class 10 \u4e3a\u4ec0\u4e48\u8f6f\u4ef6\u6709BLIKVM\u548cPiKVM\u4e24\u4e2a\u7248\u672c\uff1f\u4e24\u4e2a\u7248\u672c\u6709\u4ec0\u4e48\u533a\u522b\uff1f\u6211\u5e94\u8be5\u9009\u62e9\u54ea\u4e2a\uff1f\u6211\u53ef\u4ee5\u7528PiKVM\u5b98\u65b9\u955c\u50cf\u5417\uff1f BLIKVM\u9879\u76ee\u8bde\u751f\u4e4b\u521d\u5148\u7814\u53d1\u4e86\u786c\u4ef6\uff0c\u8f6f\u4ef6\u76f4\u63a5\u4f7f\u7528\u4e86PiKVM\u3002\u968f\u7740\u9879\u76ee\u7684\u4e0d\u65ad\u8fdb\u884c\uff0cBLIKVM\u81ea\u7814\u4e86\u81ea\u5df1\u7684\u5168\u65b0\u67b6\u6784\u7684\u8f6f\u4ef6\u7248\u672c\uff0c\u4e5f\u540c\u65f6\u4e3a\u66f4\u6df1\u5ea6\u7684\u548c\u81ea\u5df1\u7684\u786c\u4ef6\u914d\u5408\u505a\u597d\u57fa\u7840\uff1b BLIKVM\u548cPiKVM\u6700\u6838\u5fc3\u7684\u529f\u80fd\u5bf9\u7528\u6237\u6765\u8bf4\u662f\u4e00\u81f4\u7684\uff0c\u4e00\u4e9b\u7ec6\u5206\u529f\u80fd\u4e0d\u592a\u4e00\u6837\uff0c\u5982BLIKVM\u652f\u6301\u591a\u8bed\u8a00\uff1b \u9700\u6839\u636e\u60a8\u81ea\u5df1\u4f7f\u7528\u611f\u53d7\u53bb\u9009\u62e9\uff1b \u53ef\u4ee5\u4f7f\u7528PiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u4f46\u9700\u8981\u60a8\u6839\u636e\u786c\u4ef6\u7684\u4e0d\u540c\u505a\u4e00\u4e9b\u9002\u914d\uff0c\u4e3b\u8981\u6d89\u53ca\u5230\u7684\u6709\u5c4f\u5e55\u3001\u98ce\u6247\u7b49\uff0c\u56e0PiKVM\u5b98\u7f51\u955c\u50cf\u4e00\u76f4\u518d\u66f4\u65b0\uff0c\u6240\u4ee5\u5177\u4f53\u9002\u914d\u60c5\u51b5\u9700\u6839\u636e\u5f53\u65f6\u60a8\u4f7f\u7528\u5177\u4f53\u9047\u5230\u7684\u60c5\u51b5\u518d\u770b\uff1b \u4e0b\u8f7d\u955c\u50cf \u9700\u8981\u5728v4\u4e0a\u8fd0\u884c\u81ea\u884c\u5b89\u88c5PiKVM\u7684\u7528\u6237\u53ef\u4ee5\u53c2\u8003\u6b64 \u8bf4\u660e \u3002 BliKVM \u7248\u672c\u548c\u8f6f\u4ef6\u955c\u50cf\u517c\u5bb9\u6027 \u4ee5\u4e0b BliKVM \u7248\u672c\u4f7f\u7528\u76f8\u540c\u7684 BliKVM v1-3 \u8f6f\u4ef6\u955c\u50cf\uff1a BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 Allwinner \u4f7f\u7528\u5355\u72ec\u7684 Allwinner BliKVM \u955c\u50cf\u3002 BliKVM v4 Web UI \u6240\u6709\u652f\u6301\u7684\u7248\u672c\u7684 Web UI \u90fd\u4fdd\u6301\u4e00\u81f4\uff0c\u4fbf\u4e8e\u8fdc\u7a0b\u7ba1\u7406\u3002 \u57fa\u4e8e PiKVM \u7684\u8f6f\u4ef6 \u57fa\u4e8ePiKVM\u7684\u955c\u50cf\uff0c\u6811\u8393\u6d3e4B\u548cCM4\u4e0d\u516c\u7528\u4e00\u4e2a\u955c\u50cf\uff0c\u8fdb\u5165\u94fe\u63a5\u540e\u53ef\u770b\u5230\u4ee5\u5404\u786c\u4ef6\u7248\u672c(HAT CM4 PCIe)\u547d\u540d\u7684\u955c\u50cf\u3002 PiKVM \u955c\u50cf \u70e7\u5f55\u955c\u50cf Tip \u5ffd\u7565\u683c\u5f0f\u5316SD\u5361\u7684\u8bf7\u6c42\uff0c\u8fd9\u4e00\u6b65\u4e0d\u662f\u5fc5\u987b\u7684\u3002\u9009\u62e9\u6700\u9002\u5408\u4f60\u7684\u65b9\u6cd5\u3002 \u5982\u4f55\u5728\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u57574\u4e0a\u70e7\u5f55eMMC \u677f\u5b50\u94fe\u63a5 \u5982\u679c\u4f60\u4f7f\u7528\u7684CM4\u662f\u542beMMC\u7684\u7248\u672c\uff0c\u5982CM4102016\u578b\u53f7\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528v1\u548cv2\u786c\u4ef6\u76f4\u63a5\u5bf9CM4\u7684eMMC\u8fdb\u884c\u70e7\u5f55\u3002\u5982\u679c\u4f60\u7684CM4\u4e0d\u5e26eMMC\uff0c\u800c\u662f\u4f7f\u7528SD\u5361\uff0c\u4f60\u5219\u4e0d\u9700\u8981\u770b\u6b64\u7ae0\u8282\u3002\u9996\u5148\u5728blikvm\u786c\u4ef6\u4e0a\u5bf9CM4\u7684eMMC\u8fdb\u884c\u70e7\u5f55\uff0c\u4f60\u9700\u8981\u5148\u77ed\u63a5boot\u5f15\u811a\u3002 \u5982\u679c\u4f60\u4f7f\u7528 BLIKVM CM4 \u7248\u672c \u7136\u540e\u5c06\u6570\u636e\u7ebf\u8fde\u63a5\u5230USB OTG\u63a5\u53e3\u3002\u6253\u5f00blikvm\u7535\u6e90\u5e76\u89c2\u5bdfact\u706f\uff0c\u7eff\u706f\u5e38\u4eae\u3002 \u5982\u679c\u4f60\u4f7f\u7528 BLIKVM PCIe \u7248\u672c \u7136\u540e\u5c06\u6570\u636e\u7ebf\u8fde\u63a5\u5230USB-PC\u63a5\u53e3\u3002\u6253\u5f00blikvm\u7535\u6e90\u5e76\u89c2\u5bdfACT\u548cPWR LED\u706f\u4e0d\u4eae\u3002 \u901a\u8fc7usbboot/rpiboot\u521d\u59cb\u5316EMMC\u540e\uff0cACT\u548cPWR LED\u706f\u5e38\u4eae\u3002 EMMC \u77e5\u8bc6 \u5982\u679c\u4f60\u4f7f\u7528\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u5757\u5982CM3\u6216CM4 EMMC\uff0c\u4f60\u53ef\u4ee5\u901a\u8fc7usbboot\u521d\u59cb\u5316EMMC\u3002\u6ce8\u610fEMMC\u7248\u672c\u4e0d\u80fd\u76f4\u63a5\u4f7f\u7528SD\u5361\u542f\u52a8\u955c\u50cf\u3002 \u4ece\u8fd9\u4e2a\u89c6\u9891\u4e2d\u4f60\u53ef\u4ee5\u5feb\u901f\u5b66\u4e60\u5982\u4f55\u70e7\u5f55\u955c\u50cf\u3002 \u5982\u4f55\u5728\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u57574\u4e0a\u70e7\u5f55eMMC\u89c6\u9891 \u4ee5Ubuntu\u7cfb\u7edf\u4e3a\u53c2\u8003\u4f8b\u5b50 Linux usbboot \u5982\u679c\u4f60\u4f7f\u7528Micro-SD\u5361\uff0c\u4f60\u4e0d\u9700\u8981\u5173\u5fc3\u8fd9\u4e2a\u3002 # sudo apt-get install libusb-1.0-0-dev # git clone --depth=1 https://github.com/raspberrypi/usbboot # cd usbboot # make # sudo ./rpiboot \u5982\u679c\u51fa\u73b0\u4e0b\u56fe\u6240\u793a\u7684\u5185\u5bb9\uff0c\u5219\u8868\u793aEMMC\u521d\u59cb\u5316\u6210\u529f\u3002 \u4f7f\u7528 RPi Imager (Linux, MacOS \u548c Windows) \u8bf7\u6ce8\u610f\u4e0d\u8981\u5728RPi Imager\u5bf9\u955c\u50cf\u8fdb\u884c\u4efb\u4f55\u989d\u5916\u8bbe\u7f6e\uff0c\u5426\u5219\u5927\u6982\u7387\u4f1a\u5bfc\u81f4\u955c\u50cf\u542f\u52a8\u4e0d\u4e86\u6216\u8005\u53cd\u590d\u91cd\u542f\u95ee\u9898\u3002 \u4e0b\u8f7d\u5e76\u5b89\u88c5 \u6700\u65b0\u7248\u672c \u7684 RPi Imager \u3002 \u8fd0\u884c RPi Imager: \u6309 CHOOSE OS \u5e76\u5728\u5217\u8868\u5e95\u90e8\u9009\u62e9 Use custom \u955c\u50cf: \u70b9\u51fb\u6b64\u9879\u540e\uff0c\u9009\u62e9\u955c\u50cf\u6587\u4ef6 ( .img.xz )\uff0c\u7136\u540e\u70b9\u51fb CHOOSE STORAGE : \u5c06\u5185\u5b58\u5361\u63d2\u5165\u8bfb\u5361\u5668\u3002\u4ece\u6b64\u5217\u8868\u4e2d\u9009\u62e9\u8bfb\u5361\u5668\u3002 \u5c0f\u5fc3 \u5e76\u9009\u62e9\u6b63\u786e\u7684\u8bbe\u5907: \u9009\u62e9\u5185\u5b58\u5361\u540e\uff0c\u6309 WRITE \u6309\u94ae\u3002\u5f53\u88ab\u8be2\u95ee\u65f6\u786e\u8ba4\u64cd\u4f5c: \u7b49\u5f85\u8fc7\u7a0b\u5b8c\u6210\u3002\u559d\u676f\u5496\u5561\u6216\u505a\u4e9b\u4f38\u5c55\u8fd0\u52a8 :) Tip \u8fc7\u7a0b\u53ef\u80fd\u4f1a\u572899%\u65f6\u6302\u8d77\u5f88\u957f\u65f6\u95f4\uff0c\u8fd9\u6ca1\u5173\u7cfb\uff0c\u53ea\u9700\u7b49\u5f85\u5b8c\u6210 \u6210\u529f\u5b8c\u6210\u540e\u53d6\u51fa\u5185\u5b58\u5361: Tip \u5982\u679c\u5728\u70e7\u5f55\u6216\u542f\u52a8PiKVM\u65f6\u53d1\u751f\u9519\u8bef\uff0c\u8bf7\u91cd\u590d\u6b64\u8fc7\u7a0b\u3002","title":"\u70e7\u5f55\u955c\u50cf"},{"location":"flashing_os/#_1","text":"Micro-SD\u5361\u914d\u7f6e \u6700\u5c0f\u5efa\u8bae 16 Gb \u4ee5\u4e0a \u63a8\u8350\u4f7f\u7528 Class 10 \u4e3a\u4ec0\u4e48\u8f6f\u4ef6\u6709BLIKVM\u548cPiKVM\u4e24\u4e2a\u7248\u672c\uff1f\u4e24\u4e2a\u7248\u672c\u6709\u4ec0\u4e48\u533a\u522b\uff1f\u6211\u5e94\u8be5\u9009\u62e9\u54ea\u4e2a\uff1f\u6211\u53ef\u4ee5\u7528PiKVM\u5b98\u65b9\u955c\u50cf\u5417\uff1f BLIKVM\u9879\u76ee\u8bde\u751f\u4e4b\u521d\u5148\u7814\u53d1\u4e86\u786c\u4ef6\uff0c\u8f6f\u4ef6\u76f4\u63a5\u4f7f\u7528\u4e86PiKVM\u3002\u968f\u7740\u9879\u76ee\u7684\u4e0d\u65ad\u8fdb\u884c\uff0cBLIKVM\u81ea\u7814\u4e86\u81ea\u5df1\u7684\u5168\u65b0\u67b6\u6784\u7684\u8f6f\u4ef6\u7248\u672c\uff0c\u4e5f\u540c\u65f6\u4e3a\u66f4\u6df1\u5ea6\u7684\u548c\u81ea\u5df1\u7684\u786c\u4ef6\u914d\u5408\u505a\u597d\u57fa\u7840\uff1b BLIKVM\u548cPiKVM\u6700\u6838\u5fc3\u7684\u529f\u80fd\u5bf9\u7528\u6237\u6765\u8bf4\u662f\u4e00\u81f4\u7684\uff0c\u4e00\u4e9b\u7ec6\u5206\u529f\u80fd\u4e0d\u592a\u4e00\u6837\uff0c\u5982BLIKVM\u652f\u6301\u591a\u8bed\u8a00\uff1b \u9700\u6839\u636e\u60a8\u81ea\u5df1\u4f7f\u7528\u611f\u53d7\u53bb\u9009\u62e9\uff1b \u53ef\u4ee5\u4f7f\u7528PiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u4f46\u9700\u8981\u60a8\u6839\u636e\u786c\u4ef6\u7684\u4e0d\u540c\u505a\u4e00\u4e9b\u9002\u914d\uff0c\u4e3b\u8981\u6d89\u53ca\u5230\u7684\u6709\u5c4f\u5e55\u3001\u98ce\u6247\u7b49\uff0c\u56e0PiKVM\u5b98\u7f51\u955c\u50cf\u4e00\u76f4\u518d\u66f4\u65b0\uff0c\u6240\u4ee5\u5177\u4f53\u9002\u914d\u60c5\u51b5\u9700\u6839\u636e\u5f53\u65f6\u60a8\u4f7f\u7528\u5177\u4f53\u9047\u5230\u7684\u60c5\u51b5\u518d\u770b\uff1b","title":"\u70e7\u5f55\u955c\u50cf"},{"location":"flashing_os/#_2","text":"\u9700\u8981\u5728v4\u4e0a\u8fd0\u884c\u81ea\u884c\u5b89\u88c5PiKVM\u7684\u7528\u6237\u53ef\u4ee5\u53c2\u8003\u6b64 \u8bf4\u660e \u3002","title":"\u4e0b\u8f7d\u955c\u50cf"},{"location":"flashing_os/#blikvm","text":"\u4ee5\u4e0b BliKVM \u7248\u672c\u4f7f\u7528\u76f8\u540c\u7684 BliKVM v1-3 \u8f6f\u4ef6\u955c\u50cf\uff1a BliKVM v1 CM4 BliKVM v2 PCIe BliKVM v3 HAT BliKVM v4 Allwinner \u4f7f\u7528\u5355\u72ec\u7684 Allwinner BliKVM \u955c\u50cf\u3002 BliKVM v4 Web UI \u6240\u6709\u652f\u6301\u7684\u7248\u672c\u7684 Web UI \u90fd\u4fdd\u6301\u4e00\u81f4\uff0c\u4fbf\u4e8e\u8fdc\u7a0b\u7ba1\u7406\u3002","title":"BliKVM \u7248\u672c\u548c\u8f6f\u4ef6\u955c\u50cf\u517c\u5bb9\u6027"},{"location":"flashing_os/#pikvm","text":"\u57fa\u4e8ePiKVM\u7684\u955c\u50cf\uff0c\u6811\u8393\u6d3e4B\u548cCM4\u4e0d\u516c\u7528\u4e00\u4e2a\u955c\u50cf\uff0c\u8fdb\u5165\u94fe\u63a5\u540e\u53ef\u770b\u5230\u4ee5\u5404\u786c\u4ef6\u7248\u672c(HAT CM4 PCIe)\u547d\u540d\u7684\u955c\u50cf\u3002 PiKVM \u955c\u50cf","title":"\u57fa\u4e8e PiKVM \u7684\u8f6f\u4ef6"},{"location":"flashing_os/#_3","text":"Tip \u5ffd\u7565\u683c\u5f0f\u5316SD\u5361\u7684\u8bf7\u6c42\uff0c\u8fd9\u4e00\u6b65\u4e0d\u662f\u5fc5\u987b\u7684\u3002\u9009\u62e9\u6700\u9002\u5408\u4f60\u7684\u65b9\u6cd5\u3002 \u5982\u4f55\u5728\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u57574\u4e0a\u70e7\u5f55eMMC","title":"\u70e7\u5f55\u955c\u50cf"},{"location":"flashing_os/#_4","text":"\u5982\u679c\u4f60\u4f7f\u7528\u7684CM4\u662f\u542beMMC\u7684\u7248\u672c\uff0c\u5982CM4102016\u578b\u53f7\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528v1\u548cv2\u786c\u4ef6\u76f4\u63a5\u5bf9CM4\u7684eMMC\u8fdb\u884c\u70e7\u5f55\u3002\u5982\u679c\u4f60\u7684CM4\u4e0d\u5e26eMMC\uff0c\u800c\u662f\u4f7f\u7528SD\u5361\uff0c\u4f60\u5219\u4e0d\u9700\u8981\u770b\u6b64\u7ae0\u8282\u3002\u9996\u5148\u5728blikvm\u786c\u4ef6\u4e0a\u5bf9CM4\u7684eMMC\u8fdb\u884c\u70e7\u5f55\uff0c\u4f60\u9700\u8981\u5148\u77ed\u63a5boot\u5f15\u811a\u3002 \u5982\u679c\u4f60\u4f7f\u7528 BLIKVM CM4 \u7248\u672c \u7136\u540e\u5c06\u6570\u636e\u7ebf\u8fde\u63a5\u5230USB OTG\u63a5\u53e3\u3002\u6253\u5f00blikvm\u7535\u6e90\u5e76\u89c2\u5bdfact\u706f\uff0c\u7eff\u706f\u5e38\u4eae\u3002 \u5982\u679c\u4f60\u4f7f\u7528 BLIKVM PCIe \u7248\u672c \u7136\u540e\u5c06\u6570\u636e\u7ebf\u8fde\u63a5\u5230USB-PC\u63a5\u53e3\u3002\u6253\u5f00blikvm\u7535\u6e90\u5e76\u89c2\u5bdfACT\u548cPWR LED\u706f\u4e0d\u4eae\u3002 \u901a\u8fc7usbboot/rpiboot\u521d\u59cb\u5316EMMC\u540e\uff0cACT\u548cPWR LED\u706f\u5e38\u4eae\u3002 EMMC \u77e5\u8bc6 \u5982\u679c\u4f60\u4f7f\u7528\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u5757\u5982CM3\u6216CM4 EMMC\uff0c\u4f60\u53ef\u4ee5\u901a\u8fc7usbboot\u521d\u59cb\u5316EMMC\u3002\u6ce8\u610fEMMC\u7248\u672c\u4e0d\u80fd\u76f4\u63a5\u4f7f\u7528SD\u5361\u542f\u52a8\u955c\u50cf\u3002 \u4ece\u8fd9\u4e2a\u89c6\u9891\u4e2d\u4f60\u53ef\u4ee5\u5feb\u901f\u5b66\u4e60\u5982\u4f55\u70e7\u5f55\u955c\u50cf\u3002 \u5982\u4f55\u5728\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u57574\u4e0a\u70e7\u5f55eMMC\u89c6\u9891 \u4ee5Ubuntu\u7cfb\u7edf\u4e3a\u53c2\u8003\u4f8b\u5b50","title":"\u677f\u5b50\u94fe\u63a5"},{"location":"flashing_os/#linux-usbboot","text":"\u5982\u679c\u4f60\u4f7f\u7528Micro-SD\u5361\uff0c\u4f60\u4e0d\u9700\u8981\u5173\u5fc3\u8fd9\u4e2a\u3002 # sudo apt-get install libusb-1.0-0-dev # git clone --depth=1 https://github.com/raspberrypi/usbboot # cd usbboot # make # sudo ./rpiboot \u5982\u679c\u51fa\u73b0\u4e0b\u56fe\u6240\u793a\u7684\u5185\u5bb9\uff0c\u5219\u8868\u793aEMMC\u521d\u59cb\u5316\u6210\u529f\u3002","title":"Linux usbboot"},{"location":"flashing_os/#rpi-imager-linux-macos-windows","text":"\u8bf7\u6ce8\u610f\u4e0d\u8981\u5728RPi Imager\u5bf9\u955c\u50cf\u8fdb\u884c\u4efb\u4f55\u989d\u5916\u8bbe\u7f6e\uff0c\u5426\u5219\u5927\u6982\u7387\u4f1a\u5bfc\u81f4\u955c\u50cf\u542f\u52a8\u4e0d\u4e86\u6216\u8005\u53cd\u590d\u91cd\u542f\u95ee\u9898\u3002 \u4e0b\u8f7d\u5e76\u5b89\u88c5 \u6700\u65b0\u7248\u672c \u7684 RPi Imager \u3002 \u8fd0\u884c RPi Imager: \u6309 CHOOSE OS \u5e76\u5728\u5217\u8868\u5e95\u90e8\u9009\u62e9 Use custom \u955c\u50cf: \u70b9\u51fb\u6b64\u9879\u540e\uff0c\u9009\u62e9\u955c\u50cf\u6587\u4ef6 ( .img.xz )\uff0c\u7136\u540e\u70b9\u51fb CHOOSE STORAGE : \u5c06\u5185\u5b58\u5361\u63d2\u5165\u8bfb\u5361\u5668\u3002\u4ece\u6b64\u5217\u8868\u4e2d\u9009\u62e9\u8bfb\u5361\u5668\u3002 \u5c0f\u5fc3 \u5e76\u9009\u62e9\u6b63\u786e\u7684\u8bbe\u5907: \u9009\u62e9\u5185\u5b58\u5361\u540e\uff0c\u6309 WRITE \u6309\u94ae\u3002\u5f53\u88ab\u8be2\u95ee\u65f6\u786e\u8ba4\u64cd\u4f5c: \u7b49\u5f85\u8fc7\u7a0b\u5b8c\u6210\u3002\u559d\u676f\u5496\u5561\u6216\u505a\u4e9b\u4f38\u5c55\u8fd0\u52a8 :) Tip \u8fc7\u7a0b\u53ef\u80fd\u4f1a\u572899%\u65f6\u6302\u8d77\u5f88\u957f\u65f6\u95f4\uff0c\u8fd9\u6ca1\u5173\u7cfb\uff0c\u53ea\u9700\u7b49\u5f85\u5b8c\u6210 \u6210\u529f\u5b8c\u6210\u540e\u53d6\u51fa\u5185\u5b58\u5361: Tip \u5982\u679c\u5728\u70e7\u5f55\u6216\u542f\u52a8PiKVM\u65f6\u53d1\u751f\u9519\u8bef\uff0c\u8bf7\u91cd\u590d\u6b64\u8fc7\u7a0b\u3002","title":"\u4f7f\u7528 RPi Imager (Linux, MacOS \u548c Windows)"},{"location":"hdmi-csi-i2s/","text":"HDMI\u8f6cCSI&I2S\u6a21\u5757\u624b\u518c \u5c06HDMI\u4fe1\u53f7\u8f6c\u6362\u6210CSI\u89c6\u9891\u4fe1\u53f7\u548cI2S\u97f3\u9891\u4fe1\u53f7, \u76ee\u524d\u5168\u5e73\u53f0\u652f\u6301(zero, Pi3B, Pi4B, CM4, Pi5B),\u5176\u4e2d\u6700\u9ad8\u91c7\u96c6\u5206\u8fa8\u7387\u4e0d\u4ec5\u4ec5\u53d6\u51b3\u4e8eHDMI\u8f6cCSI\u8f6c\u6362\u677f\uff0c\u540c\u65f6\u4e5f\u53d6\u51b3\u4e8e\u4f60\u4f7f\u7528\u7684\u6811\u8393\u6d3e\u786c\u4ef6\u7248\u672c\uff0c\u6811\u8393\u6d3e\u786c\u4ef6\u7248\u76ee\u524d\u4e3b\u8981\u5206\u4e24\u4e2a\u7cfb\u5217\uff0c\u6700\u9ad8\u652f\u63011080P60Hz\uff0c\u548c\u6700\u9ad8\u652f\u63011080P50Hz\u3002 \u6700\u9ad8\u652f\u63011080P60Hz\u7684Pi\u7248\u672c(CM3\uff0cCM4\uff0cPi5B) \u6700\u9ad8\u652f\u63011080P50Hz\u7684Pi\u7248\u672c(zero, zero2, Pi3B, Pi4B\u7b49) \u7b80\u4ecb \u6b64\u6a21\u5757\u5c06HDMI\u4fe1\u53f7\u8f6c\u6362\u6210CSI\u89c6\u9891\u4fe1\u53f7\u548cI2S\u97f3\u9891\u4fe1\u53f7\uff0c\u6700\u9ad8\u652f\u63011080P60Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u5728\u6811\u8393\u6d3e\u4e0a\u5de5\u4f5c\u7684\u5f88\u597d\uff0c\u76ee\u524d\u5171\u67093\u4e2a\u7248\u672c(C779\u3001C780\u3001C790). C790\u662f\u76ee\u524d\u6700\u65b0\u7684\u7248\u672c\uff0c\u89e3\u51b3\u4e86\u6240\u6709\u5df2\u77e5\u7684\u95ee\u9898\uff0c\u540c\u662f\u6709CSI 2\u901a\u9053\u548c4\u901a\u9053\u63a5\u53e3\uff0cI2S\u97f3\u9891\u63a5\u53e3\uff0c\u4fee\u590d\u4e86HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898\u3002 \u6027\u80fd\u53c2\u6570 C790 \u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u5728\u6811\u8393\u6d3e\u4e0a\u6b64\u6a21\u5757\u6700\u9ad8\u652f\u63011080P60Hz\u8f93\u5165\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG 4\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f CSI-2\u63a5\u53e31: 15 pin FPC, \u95f4\u8ddd1.0 mm, \u5728C790\u6a21\u5757\u7684\u6b63\u9762. CSI-2\u63a5\u53e32, 22 pin FPC, \u95f4\u8ddd0.5 mm, \u5728C790\u6a21\u5757\u7684\u80cc\u9762. \u5c3a\u5bf8: 30 x 45 mm \u5b89\u88c5\u5b54\u4f4d:4 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u6811\u8393\u6d3e4B\u53ea\u652f\u63011080P50Hz(\u56e0\u4e3a4B\u53ea\u6709\u4e24\u4e2aCSI-2\u901a\u9053) ,\u6811\u8393\u6d3eCM4\u53ea\u652f\u63011080P60Hz,\u6240\u4ee5\u5982\u679c\u4f60\u7684\u8f93\u5165\u8bbe\u5907\u4e00\u5b9a\u8981\u662f1080P60Hz\uff0c\u8bf7\u540c\u65f6\u4f7f\u7528CM4\u548cC790. \u63a5\u53e3 C790\u6709\u4e24\u4e2aCSI\u8f93\u51fa\u63a5\u53e3: \u63a5\u53e31\uff0c\u5728C790\u6b63\u9762\uff0c15 pin FPC, \u95f4\u8ddd1.0 mm; \u63a5\u53e31\uff0c\u5728C790\u80cc\u9762,22 pin FPC, \u95f4\u8ddd0.5 mm\u3002 \u5c3a\u5bf8 \u5b89\u88c5\u53c2\u8003 C780 C780A\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P50Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 2\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 15 pin FPC, \u95f4\u8ddd 1.0 mm\uff1b \u5c3a\u5bf8: 30 x 65 mm (\u6298\u65ad\u524d); 30 x 45 mm (\u6298\u65ad\u540e) \u5b89\u88c5\u5b54\u4f4d:6 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g C780B\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P60Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 4\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 22 pin FPC, \u95f4\u8ddd 0.5 mm\uff1b \u5c3a\u5bf8: 30 x 65 mm (\u6298\u65ad\u524d); 30 x 45 mm (\u6298\u65ad\u540e) \u5b89\u88c5\u5b54\u4f4d:6 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u63a5\u53e3 \u97f3\u9891\u5f15\u811a\u5b9a\u4e49\u5982\u4e0b\u56fe\u6240\u793a: \u5c3a\u5bf8 \u5c3a\u5bf8\u5982\u4e0b\u56fe\u6240\u793a. \u67096\u4e2a\u76f4\u5f84\u4e3a2\u300275mm\u7684\u5b54\u4f4d\u7528\u4e8e\u5b89\u88c5\uff0c\u5b89\u88c5\u87ba\u9489\u53ef\u4ee5\u9009\u62e9M2.5\u3002 \u5982\u4e0b\u56fe\u6240\u793a\uff0cC780\u88ab\u8bbe\u8ba1\u6210\u53ef\u6298\u65ad\u5f0f\u7684\uff0cC780\u6a21\u5757\u5728\u672a\u88ab\u6298\u65ad\u524d\u53ef\u4ee5\u5b8c\u7f8e\u7684\u5b89\u88c5\u5728zero\u4e0a\u3002 C779 \u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P50Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 2\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 15 pin FPC, \u95f4\u8ddd 1.0 mm\uff1b \u5c3a\u5bf8: 35 x 50 mm \u5b89\u88c5\u5b54\u4f4d:4 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u5c3a\u5bf8 \u5c3a\u5bf8\u5982\u4e0b\u56fe\u6240\u793a. \u67094\u4e2a\u76f4\u5f84\u4e3a2.75mm\u7684\u5b54\u4f4d\u7528\u4e8e\u5b89\u88c5\uff0c\u5b89\u88c5\u87ba\u9489\u53ef\u4ee5\u9009\u62e9M2.5\u3002 CSI\u63a5\u53e3\u5b9a\u4e49 \u5176\u4e2dC779\uff0cC780A\u53ea\u670915PIN\u5f15\u811a\uff0cC780B\u53ea\u670922PIN\u5f15\u811a\uff0cC790\u540c\u65f6\u670915\u548c22PIN\u5f15\u811a\u3002 \u8f6f\u4ef6\u4f7f\u7528demo \u4e0b\u6587\u4e2d\u7684\u8f6f\u4ef6\u4f7f\u7528\u65b9\u6cd5\u8ddf\u4f60\u4f7f\u7528\u7684\u6811\u8393\u6d3e\u955c\u50cf\u7248\u672c\u6709\u5173\uff0c\u53ef\u80fd\u5b58\u5728\u4e0d\u540c\u3002\u5982\u679c\u4f60\u6709\u4efb\u4f55\u7591\u95ee\uff0c\u8bf7\u52a0\u5165 BLIKVM Discord \u793e\u533a \u83b7\u5f97\u652f\u6301\u3001\u89e3\u7b54\u548c\u65b0\u95fb\u3002 \u4ee5\u4e0b\u8bf4\u660e\u9002\u7528\u4e8e\u5185\u6838\u4e3a5.4\u6216\u8005\u66f4\u9ad8\u7248\u672c\u3002\u5982\u679c\u4f60\u7684\u6811\u8393\u6d3e\u955c\u50cf\u4f4e\u4e8e\u6b64\u7248\u672c\uff0c\u8bf7\u5347\u7ea7\u3002\u7ec8\u7aef\u4f7f\u7528\u4f7f\u7528\u201cuname-a\u201d\u53ef\u4ee5\u67e5\u770b\u4f60\u7cfb\u7edf\u7684\u5185\u6838\u7248\u672c\u3002 pi@raspberrypi:~ $ uname -a Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. \u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u8fdb\u884c\u5347\u7ea7 (\u4e0d\u662f\u5fc5\u987b\u7684\uff0c\u5728\u67d0\u4e9b\u56fd\u5bb6\u8fd9\u4e2a\u82b1\u8d39\u7684\u65f6\u95f4\u53ef\u80fd\u5f88\u957f) sudo apt-get update sudo apt-get upgrade 2. \u4f7f\u80fd\u76f8\u673a\u6a21\u5757(\u5728\u6811\u8393\u6d3eBullseys OS\u7cfb\u7edf\u4e2d\uff0c\u76f8\u673a\u5df2\u9ed8\u8ba4\u88ab\u4f7f\u80fd) sudo raspi-config sudo reboot \u79fb\u52a8\u5149\u6807\u5230\u2018Interfacing Options\u2019\uff0c\u7136\u540e\u6309Enter\u952e\u8fdb\u5165\u3002\u7136\u540e\u9009\u62e9\u2018Camera\u2019\u9009\u9879\uff0c\u6309Enter\u952e\u8fdb\u5165\u540e\uff0c\u4f7f\u80fd\u76f8\u673a\u3002\u7136\u540e\u9009\u62e9\u201cFinish\u201d\u540e\uff0c \u9009\u62e9\u201creboot\u201d\u3002 \u91cd\u542f\u975e\u5e38\u91cd\u8981!! \u7531\u4e8ePi5B\u53d6\u6d88\u4e86\u786c\u7f16\u7801\u5668\uff0c\u4e0b\u9762\u8f6f\u4ef6\u4f7f\u7528\u65b9\u6cd5\u5728Pi\u5e73\u53f0\u76ee\u524d\u5206\u4e3a\u4e24\u4e2a\u90e8\u5206\uff0cPi5B\u914d\u7f6e\uff0c\u548c\u5176\u5b83Pi\u5e73\u53f0\u914d\u7f6e\u3002 \u5728zero, zero2,Pi3B,Pi4B\u7b49\u5e73\u53f0HDMI\u8f6cCSI\u6a21\u5757\u6d4b\u8bd5demo\u53c2\u8003 \u7f16\u8f91 /boot/config.txt (\u9700\u8981sudo\u6743\u9650) sudo nano /boot/config.txt \u6dfb\u52a0\u4e0b\u9762\u7684\u5185\u5bb9 dtoverlay=tc358743 \u5982\u679c\u4f60\u7684\u6a21\u5757(C780\u548cC790)\u652f\u6301\u58f0\u97f3\uff0c\u6dfb\u52a0\u4e0b\u9762\u5185\u5bb9\u652f\u6301\u58f0\u97f3 dtoverlay=tc358743-audio \u5982\u679c\u4f60\u662f\u7528\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u7ec4(CM3\u3001CM4)\uff0c\u53ef\u4ee5\u901a\u8fc7\u4e0b\u5217\u914d\u7f6e\uff0c\u4f7f\u80fdCSI\u76844\u4e2a\u901a\u9053\u3002 dtoverlay=tc358743,4lane=1 \u4f7f\u7528\u201cdmesg | grep cma\u201d\u68c0\u67e5\u5206\u914d\u7ed9CMA\u5806\u7684\u5185\u5b58\u91cf\uff0c\u7ec8\u7aef\u51fa\u73b0\u7684\u7b2c\u4e00\u884c\u5185\u5bb9\u5e94\u8be5\u5982\u4e0b\u6240\u793a: pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 \u5982\u679c\u663e\u793a\u5c11\u4e8e96MB\uff0c\u7f16\u8f91/boot/cmdline.txt\uff0c\u6dfb\u52a0\u4e0b\u9762\u4e00\u884c\u3002 cma=96M \u91cd\u542f\u6811\u8393\u6d3e\uff0c\u5982\u679c\u914d\u7f6e\u6210\u529f\uff0c\u4f60\u5c06\u4f1a\u770b\u5230/dev/video0\u8bbe\u5907\u63cf\u8ff0\u7b26\u51fa\u73b0\u3002\u53ef\u4ee5\u4f7f\u7528\u201cv4l2-ctl \u2013list-devices\u201d \u547d\u4ee4\u5217\u51fa\u6240\u6709\u7684video\u63cf\u8ff0\u7b26\u3002\u518d\u5c06\u6811\u8393\u6d3e\u4e0e\u6a21\u5757\u6b63\u786e\u8fde\u63a5\u540e\uff0c\u6811\u8393\u6d3e\u4e0a\u7535\uff0c\u4f60\u53ef\u4ee5\u770b\u5230C790\u6a21\u5757\u4e0a\u6709\u4e00\u4e2a\u7eff\u8272\u706f\u5e38\u4eae\uff0c\u7136\u540e\u53ef\u4ee5\u6309\u7167\u4e0b\u9762\u7684\u547d\u4ee4\uff0c\u68c0\u67e5\u662f\u5426\u5df2\u7ecf\u6b63\u5e38\u51fa\u73b0\u4e86video0\u3002 pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 \u9ed8\u8ba4\u6ca1\u6709\u52a0\u8f7dEDID,\u5982\u679c\u4f60\u6709EDID\u7f16\u8f91\u5668\uff0c\u4f60\u53ef\u4ee5\u81ea\u5df1\u7f16\u8f91\u4f60\u6240\u9700\u8981\u7684\u5206\u8fa8\u7387\uff0c\u6216\u8005\u4f7f\u7528\u4e0b\u9762\u63d0\u4f9b\u7684EDID\u5206\u8fa8\u7387\uff08720p60hz\uff09\u3002 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt # \u62f7\u8d1d\u4e0a\u95e8\u7684\u5185\u5bb9\u5230edid.txt\u6587\u4ef6\u4e2d\uff0c\u7136\u540e\u4fdd\u5b58\u9000\u51fa\u3002\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u8bbe\u7f6e\u52a0\u8f7dedid\uff0c\u5982\u679c\u6b63\u786e\u8bbe\u7f6e\uff0c\u53ef\u4ee5\u770b\u5230\u5982\u4e0b\u7684\u8f93\u51fa\u3002 pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan \u9a71\u52a8\u7a0b\u5e8f\u4e0d\u4f1a\u81ea\u52a8\u5207\u6362\u5230\u68c0\u6d4b\u5230\u7684\u5206\u8fa8\u7387\u3002\u662f\u7528\u4e0b\u5217\u547d\u4ee4\u68c0\u67e5\u76ee\u524dHDMI\u7684\u8f93\u5165 pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: \u4f60\u5fc5\u987b\u4f7f\u7528\u201cv4l2-ctl \u2013set-dv-bt-timings\u201d\u547d\u4ee4\u8bbe\u7f6e\u9a71\u52a8\u7a0b\u5e8f\u4f7f\u7528\u76ee\u524d\u7684\u8f93\u5165\u5206\u8fa8\u7387 v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. \u82af\u7247\u652f\u6301\u4e24\u79cd\u683c\u5f0f(BGR3\u548cUYVY)\uff0cBGR3\u50cf\u7d20\u6df1\u5ea6\u4e3a24bpp\uff0cUYVY\u4e3aYUV4:2:2 16bpp\u3002\u5982\u679c\u4f7f\u7528CSI 2\u901a\u9053\uff0cBGR3\u683c\u5f0f\u6700\u5927\u652f\u63011080P30Hz\u7684\u8f93\u5165\uff0c\u4f7f\u7528UYVY\u5219\u6700\u5927\u652f\u63011080P60Hz\u7684\u8f93\u5165\u3002\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u8bbe\u7f6e\u4e3aUYVY\u683c\u5f0f\u3002 v4l2-ctl -v pixelformat=UYVY \u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\uff0c\u68c0\u67e5\u97f3\u9891\u786c\u4ef6\u548c\u9a71\u52a8\u662f\u5426\u6b63\u5e38\u3002 pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1: tc358743\u610f\u5473\u7740\u97f3\u9891\u76f8\u5173\u786c\u4ef6\u5df2\u88ab\u6b63\u786e\u52a0\u8f7d\uff0c\u6ce8\u610f\u8fd9\u91cc\u76841\u53ef\u80fd\u4e0d\u540c\u3002 \u5b89\u88c5GStreamer\u5de5\u5177. sudo apt install gstreamer1.0-tools sudo apt-get install gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-plugins-bad sudo apt-get install gstreamer1.0-plugins-base \u68c0\u67e5gstreamer\u5de5\u5177\u7248\u672c: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note:\u4e0d\u540c\u7684\u7248\u672c\u8fd9\u91cc\u8f93\u51fa\u53ef\u80fd\u4e0d\u540c. \u4f7f\u7528gstreamer\u53bb\u5f55\u5236\u89c6\u9891\u6216\u8005\u58f0\u97f3 #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. \u4f60\u4f1a\u5f97\u5230\u4e00\u4e2afoo.mkv\u6587\u4ef6. \u5982\u679c\u4f60\u7684gstreamer\u662f1.8\u6216\u8005\u66f4\u9ad8\u7248\u672c\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u3002\u5176\u4e2ddevice=hw:1\u8868\u793a\u7684\u662fTC358743\u58f0\u5361\u3002 #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: \u8fd9\u91cc\u6211\u4eec\u5efa\u8bae\u4f60\u4f7f\u7528\u5b9e\u9645\u7684\u8f93\u5165\u5e27\u7387\u53bb\u91c7\u96c6HDMI\u4fe1\u53f7\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528 \u2018v4l2-ctl \u2013query-dv-timings\u2019\u53bb\u68c0\u67e5\u5b9e\u9645\u8f93\u5165\u5e27\u7387\u3002 \u5982\u4e0a\u56fe\u4e2d\u7684HDMI\u8f93\u5165\u8bbe\u5907\uff0c\u5e27\u7387\u662f60Hz\uff0c\u6240\u4ee5\u6211\u4eec\u53ef\u4ee5\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u53bb\u5f55\u5236\u89c6\u9891\uff1a gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv \u5f55\u5236\u89c6\u9891\u548c\u97f3\u9891: (\u5982\u679c\u4f60\u7684\u8bbe\u5907\u652f\u6301\u97f3\u9891\u7684\u8bdd) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9) Pi5B\u7b49\u5e73\u53f0HDMI\u8f6cCSI\u6a21\u5757\u6d4b\u8bd5demo\u53c2\u8003 \u4e0b\u9762\u6d4b\u8bd5\u4e2d\uff0c\u4f7f\u7528cam1\u901a\u9053\u8fdb\u884c\u6d4b\u8bd5\uff0c\u6d4b\u8bd5\u8f93\u5165\u5206\u8fa8\u7387\u4e3a1080P24Hz\u3002\u6811\u8393\u6d3e5b\u6d4b\u8bd5\u8fc7\u7a0b\u4e2d\u53d1\u73b0edid\u8bbe\u7f6e\u65e0\u6548\uff0c\u56e0\u6b64\u9700\u8981\u901a\u8fc7\u6dfb\u52a0HDMI\u8bf1\u9a97\u5668\u6765\u5f3a\u5236\u76ee\u6807\u8bbe\u7f6e\u8f93\u51faHDMI\uff0c\u5426\u5219\u6811\u8393\u6d3e5b\u5f88\u6709\u53ef\u80fd\u83b7\u53d6\u4e0d\u5230\u4efb\u4f55\u8f93\u5165\u3002\u7531\u4e8e\u6811\u8393\u6d3e5b\u6ca1\u6709\u5bf9\u5e94\u7684\u786c\u7f16\u7801\u786c\u4ef6\uff0c\u6240\u4ee5\u6811\u8393\u6d3e5b+C790\u56fe\u50cf\u91c7\u96c6\u80fd\u529b\u6027\u80fd\u4e00\u822c\uff0c\u4e0d\u5982\u7528\u6811\u8393\u6d3e4b \u7f16\u8f91 /boot/config.txt (\u9700\u8981sudo\u6743\u9650) sudo nano /boot/config.txt \u6dfb\u52a0\u4e0b\u9762\u7684\u5185\u5bb9 dtoverlay=tc358743 \u5982\u679c\u4f60\u7684\u6a21\u5757(C780\u548cC790)\u652f\u6301\u58f0\u97f3\uff0c\u6dfb\u52a0\u4e0b\u9762\u5185\u5bb9\u652f\u6301\u58f0\u97f3 dtoverlay=tc358743-audio \u91cd\u542f\u6811\u8393\u6d3e,\u6267\u884c\u4e0b\u9762\u6307\u4ee4\uff0c\u627e\u5230csi\u5bf9\u5e94\u7684media\u8282\u70b9\u4e3amedia0,\u5373rp1-cfe (platform:1f00128000.csi)\u5b57\u6bb5\u4e0b\u7684media\u8bbe\u5907: blikvm@blikvm:~ $ v4l2-ctl --list-devices pispbe (platform:1000880000.pisp_be): /dev/video20 /dev/video21 /dev/video22 /dev/video23 /dev/video24 /dev/video25 /dev/video26 /dev/video27 /dev/video28 /dev/video29 /dev/video30 /dev/video31 /dev/video32 /dev/video33 /dev/video34 /dev/video35 /dev/video36 /dev/video37 /dev/media1 /dev/media2 rp1-cfe (platform:1f00128000.csi): /dev/video0 /dev/video1 /dev/video2 /dev/video3 /dev/video4 /dev/video5 /dev/video6 /dev/video7 /dev/media0 rpivid (platform:rpivid): /dev/video19 /dev/media3 \u627e\u5230tc358743\u5bf9\u5e94\u8282\u70b9\u4e3av4l-subdev2\uff0crp1-cfe-csi2_ch0\u7684pad0\u4e3avideo0: blikvm@blikvm:~ $ media-ctl -d /dev/media0 -p Media controller API version 6.1.63 Media device information ------------------------ driver rp1-cfe model rp1-cfe serial bus info platform:1f00128000.csi hw revision 0x114666 driver version 6.1.63 Device topology - entity 1: csi2 (8 pads, 8 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"tc358743 4-000f\":0 [ENABLED,IMMUTABLE] pad1: Sink [fmt:unknown/8192x1 field:none] pad2: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad3: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad4: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch0\":0 [] -> \"pisp-fe\":0 [] pad5: Source [fmt:unknown/8192x1 field:none] -> \"rp1-cfe-embedded\":0 [] pad6: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch2\":0 [] -> \"pisp-fe\":0 [] pad7: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch3\":0 [] -> \"pisp-fe\":0 [] - entity 10: pisp-fe (5 pads, 7 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: Sink [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"csi2\":4 [] <- \"csi2\":6 [] <- \"csi2\":7 [] pad1: Sink [fmt:FIXED/8192x1 field:none] <- \"rp1-cfe-fe_config\":0 [] pad2: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image0\":0 [] pad3: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image1\":0 [] pad4: Source [fmt:FIXED/8192x1 field:none] -> \"rp1-cfe-fe_stats\":0 [] - entity 16: tc358743 4-000f (1 pad, 1 link) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev2 pad0: Source [fmt:RGB888_1X24/640x480 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:640x350@13000000 max:1920x1200@165000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom] [dv.detect:BT.656/1120 1920x1080p24 (2750x1125) stds: flags:] [dv.current:BT.656/1120 640x480p59 (800x525) stds:CEA-861,DMT flags:has-cea861-vic] -> \"csi2\":0 [ENABLED,IMMUTABLE] - entity 18: rp1-cfe-csi2_ch0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 pad0: Sink <- \"csi2\":4 [] - entity 22: rp1-cfe-embedded (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- \"csi2\":5 [] - entity 26: rp1-cfe-csi2_ch2 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: Sink <- \"csi2\":6 [] - entity 30: rp1-cfe-csi2_ch3 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video3 pad0: Sink <- \"csi2\":7 [] - entity 34: rp1-cfe-fe_image0 (1 pad, 1 link) type Node subtype V4L flags 1 device node name /dev/video4 pad0: Sink <- \"pisp-fe\":2 [] - entity 38: rp1-cfe-fe_image1 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video5 pad0: Sink <- \"pisp-fe\":3 [] - entity 42: rp1-cfe-fe_stats (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video6 pad0: Sink <- \"pisp-fe\":4 [] - entity 46: rp1-cfe-fe_config (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video7 pad0: Source -> \"pisp-fe\":1 [] \u67e5\u8be2\u5f53\u524d\u8f93\u5165\u6e90\u4fe1\u606f,\u82e5\u5206\u8fa8\u7387\u663e\u793a0\u5219\u8868\u793a\u4e3a\u68c0\u67e5\u5230\u8f93\u5165\u6e90\u4fe1\u53f7\uff0c\u9700\u8981\u68c0\u67e5\u786c\u4ef6\u8fde\u63a5\u548c\u4e0a\u8ff0\u6b65\u9aa4\u6392\u67e5\u3002 blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --query-dv-timings Active width: 1920 Active height: 1080 Total width: 2750 Total height: 1125 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (24.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 830 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 45 Vertical backporch: 0 Standards: Flags: \u786e\u8ba4\u5f53\u524d\u8f93\u5165\u6e90\u4fe1\u606f blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --set-dv-bt-timings query BT timings set \u521d\u59cb\u5316media0 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -r \u628acsi2\u7684pad4\u8fde\u63a5\u5230rp1-cfe-csi2_ch0\u7684pad0 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -l ''\\''csi2'\\'':4 -> '\\''rp1-cfe-csi2_ch0'\\'':0 [1]' \u914d\u7f6emedia\u8282\u70b9 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':0 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':4 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' \u8bbe\u7f6e\u8f93\u51fa\u683c\u5f0f v4l2-ctl -v width=1920,height=1080,pixelformat=RGB3 \u91c7\u96c6\u4e24\u5e27\u753b\u9762\u7528\u4e8e\u6d4b\u8bd5tc358743\u662f\u5426\u53ef\u4ee5\u5de5\u4f5c\uff0c\u5176\u5b83\u5982\u4f7f\u7528gstreamer\u7684\u65b9\u6cd5\u6682\u65f6\u672a v4l2-ctl --verbose -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat='RGB3' --stream-mmap=4 --stream-skip=3 --stream-count=2 --stream-to=hdmiin.yuv --stream-poll Pi\u5982\u679c\u5b89\u88c5\u7684\u662f\u5e26\u684c\u9762\u7684\u7cfb\u7edf\uff0c\u53ef\u4ee5\u4f7f\u7528ffplay\u76f4\u63a5\u64ad\u653eyuv\u6587\u4ef6\u3002 ffplay -f rawvideo -video_size 1920x1080 -pixel_format bgr24 hdmiin.yuv windows\u7535\u8111\u53ef\u4ee5\u4f7f\u75287yuv\u7b49\u8f6f\u4ef6\u67e5\u770b.yuv\u6587\u4ef6\uff0c\u6559\u7a0b\u8f93\u5165\u683c\u5f0f\u4e3a1920 1080\uff0c\u6240\u4ee5\u57287yuv\u53f3\u4e0a\u89d2\u683c\u5f0f\u9009\u62e9BGR888\uff0c\u5206\u8fa8\u7387\u8bbe\u7f6e1920 1080\uff0c\u5373\u53ef\u770b\u5230\u4e24\u5e27\u521a\u91c7\u96c6\u5230\u7684\u753b\u9762 \u82af\u7247\u8d44\u6599 tc358743\u82af\u7247\u8d44\u6599 \u53d1\u8d27\u6e05\u5355 C790 \u6d4b\u8bd5\u89c6\u9891 C780A \u6d4b\u8bd5:https://www.youtube.com/watch?v=ecqyINoiHNQ C780B \u6d4b\u8bd5:https://www.youtube.com/watch?v=nc-hwPT2Uak&t=15s \u91c7\u8d2d\u8fde\u63a5 \u4e2d\u56fd\u5ba2\u6237\u91c7\u8d2d\u94fe\u63a5\uff1a C790 & C780 \u5176\u5b83\u56fd\u5bb6\u5ba2\u6237\u91c7\u8d2d\u8fde\u63a5\uff1a C779","title":"HDMI\u8f6cCSI & Audio\u6a21\u5757\u7528\u6237\u624b\u518c"},{"location":"hdmi-csi-i2s/#hdmicsii2s","text":"\u5c06HDMI\u4fe1\u53f7\u8f6c\u6362\u6210CSI\u89c6\u9891\u4fe1\u53f7\u548cI2S\u97f3\u9891\u4fe1\u53f7, \u76ee\u524d\u5168\u5e73\u53f0\u652f\u6301(zero, Pi3B, Pi4B, CM4, Pi5B),\u5176\u4e2d\u6700\u9ad8\u91c7\u96c6\u5206\u8fa8\u7387\u4e0d\u4ec5\u4ec5\u53d6\u51b3\u4e8eHDMI\u8f6cCSI\u8f6c\u6362\u677f\uff0c\u540c\u65f6\u4e5f\u53d6\u51b3\u4e8e\u4f60\u4f7f\u7528\u7684\u6811\u8393\u6d3e\u786c\u4ef6\u7248\u672c\uff0c\u6811\u8393\u6d3e\u786c\u4ef6\u7248\u76ee\u524d\u4e3b\u8981\u5206\u4e24\u4e2a\u7cfb\u5217\uff0c\u6700\u9ad8\u652f\u63011080P60Hz\uff0c\u548c\u6700\u9ad8\u652f\u63011080P50Hz\u3002 \u6700\u9ad8\u652f\u63011080P60Hz\u7684Pi\u7248\u672c(CM3\uff0cCM4\uff0cPi5B) \u6700\u9ad8\u652f\u63011080P50Hz\u7684Pi\u7248\u672c(zero, zero2, Pi3B, Pi4B\u7b49)","title":"HDMI\u8f6cCSI&I2S\u6a21\u5757\u624b\u518c"},{"location":"hdmi-csi-i2s/#_1","text":"\u6b64\u6a21\u5757\u5c06HDMI\u4fe1\u53f7\u8f6c\u6362\u6210CSI\u89c6\u9891\u4fe1\u53f7\u548cI2S\u97f3\u9891\u4fe1\u53f7\uff0c\u6700\u9ad8\u652f\u63011080P60Hz\u7684\u89c6\u9891\u8f93\u5165\uff0c\u5728\u6811\u8393\u6d3e\u4e0a\u5de5\u4f5c\u7684\u5f88\u597d\uff0c\u76ee\u524d\u5171\u67093\u4e2a\u7248\u672c(C779\u3001C780\u3001C790). C790\u662f\u76ee\u524d\u6700\u65b0\u7684\u7248\u672c\uff0c\u89e3\u51b3\u4e86\u6240\u6709\u5df2\u77e5\u7684\u95ee\u9898\uff0c\u540c\u662f\u6709CSI 2\u901a\u9053\u548c4\u901a\u9053\u63a5\u53e3\uff0cI2S\u97f3\u9891\u63a5\u53e3\uff0c\u4fee\u590d\u4e86HDMI\u53cd\u5411\u4f9b\u7535\u95ee\u9898\u3002","title":"\u7b80\u4ecb"},{"location":"hdmi-csi-i2s/#_2","text":"","title":"\u6027\u80fd\u53c2\u6570"},{"location":"hdmi-csi-i2s/#c790","text":"\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u5728\u6811\u8393\u6d3e\u4e0a\u6b64\u6a21\u5757\u6700\u9ad8\u652f\u63011080P60Hz\u8f93\u5165\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG 4\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f CSI-2\u63a5\u53e31: 15 pin FPC, \u95f4\u8ddd1.0 mm, \u5728C790\u6a21\u5757\u7684\u6b63\u9762. CSI-2\u63a5\u53e32, 22 pin FPC, \u95f4\u8ddd0.5 mm, \u5728C790\u6a21\u5757\u7684\u80cc\u9762. \u5c3a\u5bf8: 30 x 45 mm \u5b89\u88c5\u5b54\u4f4d:4 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u6811\u8393\u6d3e4B\u53ea\u652f\u63011080P50Hz(\u56e0\u4e3a4B\u53ea\u6709\u4e24\u4e2aCSI-2\u901a\u9053) ,\u6811\u8393\u6d3eCM4\u53ea\u652f\u63011080P60Hz,\u6240\u4ee5\u5982\u679c\u4f60\u7684\u8f93\u5165\u8bbe\u5907\u4e00\u5b9a\u8981\u662f1080P60Hz\uff0c\u8bf7\u540c\u65f6\u4f7f\u7528CM4\u548cC790. \u63a5\u53e3 C790\u6709\u4e24\u4e2aCSI\u8f93\u51fa\u63a5\u53e3: \u63a5\u53e31\uff0c\u5728C790\u6b63\u9762\uff0c15 pin FPC, \u95f4\u8ddd1.0 mm; \u63a5\u53e31\uff0c\u5728C790\u80cc\u9762,22 pin FPC, \u95f4\u8ddd0.5 mm\u3002 \u5c3a\u5bf8 \u5b89\u88c5\u53c2\u8003","title":"C790"},{"location":"hdmi-csi-i2s/#c780","text":"C780A\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P50Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 2\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 15 pin FPC, \u95f4\u8ddd 1.0 mm\uff1b \u5c3a\u5bf8: 30 x 65 mm (\u6298\u65ad\u524d); 30 x 45 mm (\u6298\u65ad\u540e) \u5b89\u88c5\u5b54\u4f4d:6 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g C780B\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P60Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 4\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 22 pin FPC, \u95f4\u8ddd 0.5 mm\uff1b \u5c3a\u5bf8: 30 x 65 mm (\u6298\u65ad\u524d); 30 x 45 mm (\u6298\u65ad\u540e) \u5b89\u88c5\u5b54\u4f4d:6 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u63a5\u53e3 \u97f3\u9891\u5f15\u811a\u5b9a\u4e49\u5982\u4e0b\u56fe\u6240\u793a: \u5c3a\u5bf8 \u5c3a\u5bf8\u5982\u4e0b\u56fe\u6240\u793a. \u67096\u4e2a\u76f4\u5f84\u4e3a2\u300275mm\u7684\u5b54\u4f4d\u7528\u4e8e\u5b89\u88c5\uff0c\u5b89\u88c5\u87ba\u9489\u53ef\u4ee5\u9009\u62e9M2.5\u3002 \u5982\u4e0b\u56fe\u6240\u793a\uff0cC780\u88ab\u8bbe\u8ba1\u6210\u53ef\u6298\u65ad\u5f0f\u7684\uff0cC780\u6a21\u5757\u5728\u672a\u88ab\u6298\u65ad\u524d\u53ef\u4ee5\u5b8c\u7f8e\u7684\u5b89\u88c5\u5728zero\u4e0a\u3002","title":"C780"},{"location":"hdmi-csi-i2s/#c779","text":"\u786c\u4ef6\u53c2\u6570 HDMI\u8f93\u5165: \u6700\u9ad8\u652f\u6301080P50Hz\u5728\u6811\u8393\u6d3e\u4e0a\uff1b HDMI\u8f6cCSI-2\u6865\u63a5\u82af\u7247:Toshiba TC358743XBG\uff1b 2\u8defCSI-2\u901a\u9053\u548c\u65f6\u949f\uff1b CSI-2\u63a5\u53e3: 15 pin FPC, \u95f4\u8ddd 1.0 mm\uff1b \u5c3a\u5bf8: 35 x 50 mm \u5b89\u88c5\u5b54\u4f4d:4 x M2.5 \u4f9b\u7535\u7535\u538b:3.3V \u91cd\u91cf: 10g \u5c3a\u5bf8 \u5c3a\u5bf8\u5982\u4e0b\u56fe\u6240\u793a. \u67094\u4e2a\u76f4\u5f84\u4e3a2.75mm\u7684\u5b54\u4f4d\u7528\u4e8e\u5b89\u88c5\uff0c\u5b89\u88c5\u87ba\u9489\u53ef\u4ee5\u9009\u62e9M2.5\u3002","title":"C779"},{"location":"hdmi-csi-i2s/#csi","text":"\u5176\u4e2dC779\uff0cC780A\u53ea\u670915PIN\u5f15\u811a\uff0cC780B\u53ea\u670922PIN\u5f15\u811a\uff0cC790\u540c\u65f6\u670915\u548c22PIN\u5f15\u811a\u3002","title":"CSI\u63a5\u53e3\u5b9a\u4e49"},{"location":"hdmi-csi-i2s/#demo","text":"\u4e0b\u6587\u4e2d\u7684\u8f6f\u4ef6\u4f7f\u7528\u65b9\u6cd5\u8ddf\u4f60\u4f7f\u7528\u7684\u6811\u8393\u6d3e\u955c\u50cf\u7248\u672c\u6709\u5173\uff0c\u53ef\u80fd\u5b58\u5728\u4e0d\u540c\u3002\u5982\u679c\u4f60\u6709\u4efb\u4f55\u7591\u95ee\uff0c\u8bf7\u52a0\u5165 BLIKVM Discord \u793e\u533a \u83b7\u5f97\u652f\u6301\u3001\u89e3\u7b54\u548c\u65b0\u95fb\u3002 \u4ee5\u4e0b\u8bf4\u660e\u9002\u7528\u4e8e\u5185\u6838\u4e3a5.4\u6216\u8005\u66f4\u9ad8\u7248\u672c\u3002\u5982\u679c\u4f60\u7684\u6811\u8393\u6d3e\u955c\u50cf\u4f4e\u4e8e\u6b64\u7248\u672c\uff0c\u8bf7\u5347\u7ea7\u3002\u7ec8\u7aef\u4f7f\u7528\u4f7f\u7528\u201cuname-a\u201d\u53ef\u4ee5\u67e5\u770b\u4f60\u7cfb\u7edf\u7684\u5185\u6838\u7248\u672c\u3002 pi@raspberrypi:~ $ uname -a Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux 1. \u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u8fdb\u884c\u5347\u7ea7 (\u4e0d\u662f\u5fc5\u987b\u7684\uff0c\u5728\u67d0\u4e9b\u56fd\u5bb6\u8fd9\u4e2a\u82b1\u8d39\u7684\u65f6\u95f4\u53ef\u80fd\u5f88\u957f) sudo apt-get update sudo apt-get upgrade 2. \u4f7f\u80fd\u76f8\u673a\u6a21\u5757(\u5728\u6811\u8393\u6d3eBullseys OS\u7cfb\u7edf\u4e2d\uff0c\u76f8\u673a\u5df2\u9ed8\u8ba4\u88ab\u4f7f\u80fd) sudo raspi-config sudo reboot \u79fb\u52a8\u5149\u6807\u5230\u2018Interfacing Options\u2019\uff0c\u7136\u540e\u6309Enter\u952e\u8fdb\u5165\u3002\u7136\u540e\u9009\u62e9\u2018Camera\u2019\u9009\u9879\uff0c\u6309Enter\u952e\u8fdb\u5165\u540e\uff0c\u4f7f\u80fd\u76f8\u673a\u3002\u7136\u540e\u9009\u62e9\u201cFinish\u201d\u540e\uff0c \u9009\u62e9\u201creboot\u201d\u3002 \u91cd\u542f\u975e\u5e38\u91cd\u8981!! \u7531\u4e8ePi5B\u53d6\u6d88\u4e86\u786c\u7f16\u7801\u5668\uff0c\u4e0b\u9762\u8f6f\u4ef6\u4f7f\u7528\u65b9\u6cd5\u5728Pi\u5e73\u53f0\u76ee\u524d\u5206\u4e3a\u4e24\u4e2a\u90e8\u5206\uff0cPi5B\u914d\u7f6e\uff0c\u548c\u5176\u5b83Pi\u5e73\u53f0\u914d\u7f6e\u3002 \u5728zero, zero2,Pi3B,Pi4B\u7b49\u5e73\u53f0HDMI\u8f6cCSI\u6a21\u5757\u6d4b\u8bd5demo\u53c2\u8003 \u7f16\u8f91 /boot/config.txt (\u9700\u8981sudo\u6743\u9650) sudo nano /boot/config.txt \u6dfb\u52a0\u4e0b\u9762\u7684\u5185\u5bb9 dtoverlay=tc358743 \u5982\u679c\u4f60\u7684\u6a21\u5757(C780\u548cC790)\u652f\u6301\u58f0\u97f3\uff0c\u6dfb\u52a0\u4e0b\u9762\u5185\u5bb9\u652f\u6301\u58f0\u97f3 dtoverlay=tc358743-audio \u5982\u679c\u4f60\u662f\u7528\u6811\u8393\u6d3e\u8ba1\u7b97\u6a21\u7ec4(CM3\u3001CM4)\uff0c\u53ef\u4ee5\u901a\u8fc7\u4e0b\u5217\u914d\u7f6e\uff0c\u4f7f\u80fdCSI\u76844\u4e2a\u901a\u9053\u3002 dtoverlay=tc358743,4lane=1 \u4f7f\u7528\u201cdmesg | grep cma\u201d\u68c0\u67e5\u5206\u914d\u7ed9CMA\u5806\u7684\u5185\u5b58\u91cf\uff0c\u7ec8\u7aef\u51fa\u73b0\u7684\u7b2c\u4e00\u884c\u5185\u5bb9\u5e94\u8be5\u5982\u4e0b\u6240\u793a: pi@raspberrypi:~ $ dmesg | grep cma [0.000000] cma: Reserved 256 MiB at 0x000000001ec00000 \u5982\u679c\u663e\u793a\u5c11\u4e8e96MB\uff0c\u7f16\u8f91/boot/cmdline.txt\uff0c\u6dfb\u52a0\u4e0b\u9762\u4e00\u884c\u3002 cma=96M \u91cd\u542f\u6811\u8393\u6d3e\uff0c\u5982\u679c\u914d\u7f6e\u6210\u529f\uff0c\u4f60\u5c06\u4f1a\u770b\u5230/dev/video0\u8bbe\u5907\u63cf\u8ff0\u7b26\u51fa\u73b0\u3002\u53ef\u4ee5\u4f7f\u7528\u201cv4l2-ctl \u2013list-devices\u201d \u547d\u4ee4\u5217\u51fa\u6240\u6709\u7684video\u63cf\u8ff0\u7b26\u3002\u518d\u5c06\u6811\u8393\u6d3e\u4e0e\u6a21\u5757\u6b63\u786e\u8fde\u63a5\u540e\uff0c\u6811\u8393\u6d3e\u4e0a\u7535\uff0c\u4f60\u53ef\u4ee5\u770b\u5230C790\u6a21\u5757\u4e0a\u6709\u4e00\u4e2a\u7eff\u8272\u706f\u5e38\u4eae\uff0c\u7136\u540e\u53ef\u4ee5\u6309\u7167\u4e0b\u9762\u7684\u547d\u4ee4\uff0c\u68c0\u67e5\u662f\u5426\u5df2\u7ecf\u6b63\u5e38\u51fa\u73b0\u4e86video0\u3002 pi@raspberrypi:~ $ ls /dev/video0 /dev/video0 pi@raspberrypi:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/media1 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/media0 unicam (platform:fe801000.csi): /dev/video0 /dev/video1 /dev/media2 \u9ed8\u8ba4\u6ca1\u6709\u52a0\u8f7dEDID,\u5982\u679c\u4f60\u6709EDID\u7f16\u8f91\u5668\uff0c\u4f60\u53ef\u4ee5\u81ea\u5df1\u7f16\u8f91\u4f60\u6240\u9700\u8981\u7684\u5206\u8fa8\u7387\uff0c\u6216\u8005\u4f7f\u7528\u4e0b\u9762\u63d0\u4f9b\u7684EDID\u5206\u8fa8\u7387\uff08720p60hz\uff09\u3002 00ffffffffffff005262888800888888 1c150103800000780aEE91A3544C9926 0F505400000001010101010101010101 010101010101011d007251d01e206e28 5500c48e2100001e8c0ad08a20e02d10 103e9600138e2100001e000000fc0054 6f73686962612d4832430a20000000FD 003b3d0f2e0f1e0a2020202020200100 020321434e041303021211012021a23c 3d3e1f2309070766030c00300080E300 7F8c0ad08a20e02d10103e9600c48e21 0000188c0ad08a20e02d10103e960013 8e210000188c0aa01451f01600267c43 00138e21000098000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 cd ~ sudo nano edid.txt # \u62f7\u8d1d\u4e0a\u95e8\u7684\u5185\u5bb9\u5230edid.txt\u6587\u4ef6\u4e2d\uff0c\u7136\u540e\u4fdd\u5b58\u9000\u51fa\u3002\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u8bbe\u7f6e\u52a0\u8f7dedid\uff0c\u5982\u679c\u6b63\u786e\u8bbe\u7f6e\uff0c\u53ef\u4ee5\u770b\u5230\u5982\u4e0b\u7684\u8f93\u51fa\u3002 pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums CTA-861 Header IT Formats Underscanned: yes Audio: yes YCbCr 4:4:4: no YCbCr 4:2:2: no HDMI Vendor-Specific Data Block Physical Address: 3.0.0.0 YCbCr 4:4:4 Deep Color: no 30-bit: no 36-bit: no 48-bit: no CTA-861 Video Capability Descriptor RGB Quantization Range: yes YCC Quantization Range: no PT: Supports both over- and underscan IT: Supports both over- and underscan CE: Supports both over- and underscan \u9a71\u52a8\u7a0b\u5e8f\u4e0d\u4f1a\u81ea\u52a8\u5207\u6362\u5230\u68c0\u6d4b\u5230\u7684\u5206\u8fa8\u7387\u3002\u662f\u7528\u4e0b\u5217\u547d\u4ee4\u68c0\u67e5\u76ee\u524dHDMI\u7684\u8f93\u5165 pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings Active width: 1280 Active height: 720 Total width: 1650 Total height: 750 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (60.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 370 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 30 Vertical backporch: 0 Standards: Flags: \u4f60\u5fc5\u987b\u4f7f\u7528\u201cv4l2-ctl \u2013set-dv-bt-timings\u201d\u547d\u4ee4\u8bbe\u7f6e\u9a71\u52a8\u7a0b\u5e8f\u4f7f\u7528\u76ee\u524d\u7684\u8f93\u5165\u5206\u8fa8\u7387 v4l2-ctl --set-dv-bt-timings query to select the currently detected timings. v4l2-ctl -V should now reflect the resolution detected. \u82af\u7247\u652f\u6301\u4e24\u79cd\u683c\u5f0f(BGR3\u548cUYVY)\uff0cBGR3\u50cf\u7d20\u6df1\u5ea6\u4e3a24bpp\uff0cUYVY\u4e3aYUV4:2:2 16bpp\u3002\u5982\u679c\u4f7f\u7528CSI 2\u901a\u9053\uff0cBGR3\u683c\u5f0f\u6700\u5927\u652f\u63011080P30Hz\u7684\u8f93\u5165\uff0c\u4f7f\u7528UYVY\u5219\u6700\u5927\u652f\u63011080P60Hz\u7684\u8f93\u5165\u3002\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u8bbe\u7f6e\u4e3aUYVY\u683c\u5f0f\u3002 v4l2-ctl -v pixelformat=UYVY \u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\uff0c\u68c0\u67e5\u97f3\u9891\u786c\u4ef6\u548c\u9a71\u52a8\u662f\u5426\u6b63\u5e38\u3002 pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 1: tc358743 [tc358743], device 0: bcm2835-i2s-dir-hifi dir-hifi-0 [bcm2835-i2s-dir-hifi dir-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Note: card 1: tc358743\u610f\u5473\u7740\u97f3\u9891\u76f8\u5173\u786c\u4ef6\u5df2\u88ab\u6b63\u786e\u52a0\u8f7d\uff0c\u6ce8\u610f\u8fd9\u91cc\u76841\u53ef\u80fd\u4e0d\u540c\u3002 \u5b89\u88c5GStreamer\u5de5\u5177. sudo apt install gstreamer1.0-tools sudo apt-get install gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-plugins-bad sudo apt-get install gstreamer1.0-plugins-base \u68c0\u67e5gstreamer\u5de5\u5177\u7248\u672c: pi@raspberrypi:~ $ gst-launch-1.0 --version gst-launch-1.0 version 1.18.4 GStreamer 1.18.4 http://packages.qa.debian.org/gstreamer1.0 Note:\u4e0d\u540c\u7684\u7248\u672c\u8fd9\u91cc\u8f93\u51fa\u53ef\u80fd\u4e0d\u540c. \u4f7f\u7528gstreamer\u53bb\u5f55\u5236\u89c6\u9891\u6216\u8005\u58f0\u97f3 #GStreamer v1.14 command gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. \u4f60\u4f1a\u5f97\u5230\u4e00\u4e2afoo.mkv\u6587\u4ef6. \u5982\u679c\u4f60\u7684gstreamer\u662f1.8\u6216\u8005\u66f4\u9ad8\u7248\u672c\uff0c\u53ef\u4ee5\u5c1d\u8bd5\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\u3002\u5176\u4e2ddevice=hw:1\u8868\u793a\u7684\u662fTC358743\u58f0\u5361\u3002 #The command to recode a video with audio. (GStreamer 1.18.4) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. #The sample command to recode a video without audio. (C779 doesn't support audio) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=30/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv Press CTRL+C to end recording. PS: \u8fd9\u91cc\u6211\u4eec\u5efa\u8bae\u4f60\u4f7f\u7528\u5b9e\u9645\u7684\u8f93\u5165\u5e27\u7387\u53bb\u91c7\u96c6HDMI\u4fe1\u53f7\u3002\u4f60\u53ef\u4ee5\u4f7f\u7528 \u2018v4l2-ctl \u2013query-dv-timings\u2019\u53bb\u68c0\u67e5\u5b9e\u9645\u8f93\u5165\u5e27\u7387\u3002 \u5982\u4e0a\u56fe\u4e2d\u7684HDMI\u8f93\u5165\u8bbe\u5907\uff0c\u5e27\u7387\u662f60Hz\uff0c\u6240\u4ee5\u6211\u4eec\u53ef\u4ee5\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u53bb\u5f55\u5236\u89c6\u9891\uff1a gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv \u5f55\u5236\u89c6\u9891\u548c\u97f3\u9891: (\u5982\u679c\u4f60\u7684\u8bbe\u5907\u652f\u6301\u97f3\u9891\u7684\u8bdd) gst-launch-1.0 -vvv v4l2src ! \"video/x-raw,framerate=60/1,format=UYVY\" ! v4l2h264enc extra-controls=\"controls,h264_profile=4,h264_level=13,video_bitrate=256000;\" ! \"video/x-h264,profile=high, level=(string)4.2\" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux. Note: alsasrc device=hw:1 \u2013 \u201c1\u201d means the audio card number, You must change to correct audio card number. (Query the car number via \u2018arecord \u2013l\u2019, refer to step 9) Pi5B\u7b49\u5e73\u53f0HDMI\u8f6cCSI\u6a21\u5757\u6d4b\u8bd5demo\u53c2\u8003 \u4e0b\u9762\u6d4b\u8bd5\u4e2d\uff0c\u4f7f\u7528cam1\u901a\u9053\u8fdb\u884c\u6d4b\u8bd5\uff0c\u6d4b\u8bd5\u8f93\u5165\u5206\u8fa8\u7387\u4e3a1080P24Hz\u3002\u6811\u8393\u6d3e5b\u6d4b\u8bd5\u8fc7\u7a0b\u4e2d\u53d1\u73b0edid\u8bbe\u7f6e\u65e0\u6548\uff0c\u56e0\u6b64\u9700\u8981\u901a\u8fc7\u6dfb\u52a0HDMI\u8bf1\u9a97\u5668\u6765\u5f3a\u5236\u76ee\u6807\u8bbe\u7f6e\u8f93\u51faHDMI\uff0c\u5426\u5219\u6811\u8393\u6d3e5b\u5f88\u6709\u53ef\u80fd\u83b7\u53d6\u4e0d\u5230\u4efb\u4f55\u8f93\u5165\u3002\u7531\u4e8e\u6811\u8393\u6d3e5b\u6ca1\u6709\u5bf9\u5e94\u7684\u786c\u7f16\u7801\u786c\u4ef6\uff0c\u6240\u4ee5\u6811\u8393\u6d3e5b+C790\u56fe\u50cf\u91c7\u96c6\u80fd\u529b\u6027\u80fd\u4e00\u822c\uff0c\u4e0d\u5982\u7528\u6811\u8393\u6d3e4b \u7f16\u8f91 /boot/config.txt (\u9700\u8981sudo\u6743\u9650) sudo nano /boot/config.txt \u6dfb\u52a0\u4e0b\u9762\u7684\u5185\u5bb9 dtoverlay=tc358743 \u5982\u679c\u4f60\u7684\u6a21\u5757(C780\u548cC790)\u652f\u6301\u58f0\u97f3\uff0c\u6dfb\u52a0\u4e0b\u9762\u5185\u5bb9\u652f\u6301\u58f0\u97f3 dtoverlay=tc358743-audio \u91cd\u542f\u6811\u8393\u6d3e,\u6267\u884c\u4e0b\u9762\u6307\u4ee4\uff0c\u627e\u5230csi\u5bf9\u5e94\u7684media\u8282\u70b9\u4e3amedia0,\u5373rp1-cfe (platform:1f00128000.csi)\u5b57\u6bb5\u4e0b\u7684media\u8bbe\u5907: blikvm@blikvm:~ $ v4l2-ctl --list-devices pispbe (platform:1000880000.pisp_be): /dev/video20 /dev/video21 /dev/video22 /dev/video23 /dev/video24 /dev/video25 /dev/video26 /dev/video27 /dev/video28 /dev/video29 /dev/video30 /dev/video31 /dev/video32 /dev/video33 /dev/video34 /dev/video35 /dev/video36 /dev/video37 /dev/media1 /dev/media2 rp1-cfe (platform:1f00128000.csi): /dev/video0 /dev/video1 /dev/video2 /dev/video3 /dev/video4 /dev/video5 /dev/video6 /dev/video7 /dev/media0 rpivid (platform:rpivid): /dev/video19 /dev/media3 \u627e\u5230tc358743\u5bf9\u5e94\u8282\u70b9\u4e3av4l-subdev2\uff0crp1-cfe-csi2_ch0\u7684pad0\u4e3avideo0: blikvm@blikvm:~ $ media-ctl -d /dev/media0 -p Media controller API version 6.1.63 Media device information ------------------------ driver rp1-cfe model rp1-cfe serial bus info platform:1f00128000.csi hw revision 0x114666 driver version 6.1.63 Device topology - entity 1: csi2 (8 pads, 8 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"tc358743 4-000f\":0 [ENABLED,IMMUTABLE] pad1: Sink [fmt:unknown/8192x1 field:none] pad2: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad3: Sink [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] pad4: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch0\":0 [] -> \"pisp-fe\":0 [] pad5: Source [fmt:unknown/8192x1 field:none] -> \"rp1-cfe-embedded\":0 [] pad6: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch2\":0 [] -> \"pisp-fe\":0 [] pad7: Source [fmt:SRGGB10_1X10/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-csi2_ch3\":0 [] -> \"pisp-fe\":0 [] - entity 10: pisp-fe (5 pads, 7 links) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: Sink [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] <- \"csi2\":4 [] <- \"csi2\":6 [] <- \"csi2\":7 [] pad1: Sink [fmt:FIXED/8192x1 field:none] <- \"rp1-cfe-fe_config\":0 [] pad2: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image0\":0 [] pad3: Source [fmt:SRGGB16_1X16/640x480 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range] -> \"rp1-cfe-fe_image1\":0 [] pad4: Source [fmt:FIXED/8192x1 field:none] -> \"rp1-cfe-fe_stats\":0 [] - entity 16: tc358743 4-000f (1 pad, 1 link) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev2 pad0: Source [fmt:RGB888_1X24/640x480 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:640x350@13000000 max:1920x1200@165000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom] [dv.detect:BT.656/1120 1920x1080p24 (2750x1125) stds: flags:] [dv.current:BT.656/1120 640x480p59 (800x525) stds:CEA-861,DMT flags:has-cea861-vic] -> \"csi2\":0 [ENABLED,IMMUTABLE] - entity 18: rp1-cfe-csi2_ch0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 pad0: Sink <- \"csi2\":4 [] - entity 22: rp1-cfe-embedded (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- \"csi2\":5 [] - entity 26: rp1-cfe-csi2_ch2 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: Sink <- \"csi2\":6 [] - entity 30: rp1-cfe-csi2_ch3 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video3 pad0: Sink <- \"csi2\":7 [] - entity 34: rp1-cfe-fe_image0 (1 pad, 1 link) type Node subtype V4L flags 1 device node name /dev/video4 pad0: Sink <- \"pisp-fe\":2 [] - entity 38: rp1-cfe-fe_image1 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video5 pad0: Sink <- \"pisp-fe\":3 [] - entity 42: rp1-cfe-fe_stats (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video6 pad0: Sink <- \"pisp-fe\":4 [] - entity 46: rp1-cfe-fe_config (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video7 pad0: Source -> \"pisp-fe\":1 [] \u67e5\u8be2\u5f53\u524d\u8f93\u5165\u6e90\u4fe1\u606f,\u82e5\u5206\u8fa8\u7387\u663e\u793a0\u5219\u8868\u793a\u4e3a\u68c0\u67e5\u5230\u8f93\u5165\u6e90\u4fe1\u53f7\uff0c\u9700\u8981\u68c0\u67e5\u786c\u4ef6\u8fde\u63a5\u548c\u4e0a\u8ff0\u6b65\u9aa4\u6392\u67e5\u3002 blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --query-dv-timings Active width: 1920 Active height: 1080 Total width: 2750 Total height: 1125 Frame format: progressive Polarities: -vsync -hsync Pixelclock: 74250000 Hz (24.00 frames per second) Horizontal frontporch: 0 Horizontal sync: 830 Horizontal backporch: 0 Vertical frontporch: 0 Vertical sync: 45 Vertical backporch: 0 Standards: Flags: \u786e\u8ba4\u5f53\u524d\u8f93\u5165\u6e90\u4fe1\u606f blikvm@blikvm:~ $ v4l2-ctl -d /dev/v4l-subdev2 --set-dv-bt-timings query BT timings set \u521d\u59cb\u5316media0 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -r \u628acsi2\u7684pad4\u8fde\u63a5\u5230rp1-cfe-csi2_ch0\u7684pad0 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -l ''\\''csi2'\\'':4 -> '\\''rp1-cfe-csi2_ch0'\\'':0 [1]' \u914d\u7f6emedia\u8282\u70b9 blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':0 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' blikvm@blikvm:~ $ media-ctl -d /dev/media0 -V ''\\''csi2'\\'':4 [fmt:RGB888_1X24/1920x1080 field:none colorspace:srgb]' \u8bbe\u7f6e\u8f93\u51fa\u683c\u5f0f v4l2-ctl -v width=1920,height=1080,pixelformat=RGB3 \u91c7\u96c6\u4e24\u5e27\u753b\u9762\u7528\u4e8e\u6d4b\u8bd5tc358743\u662f\u5426\u53ef\u4ee5\u5de5\u4f5c\uff0c\u5176\u5b83\u5982\u4f7f\u7528gstreamer\u7684\u65b9\u6cd5\u6682\u65f6\u672a v4l2-ctl --verbose -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat='RGB3' --stream-mmap=4 --stream-skip=3 --stream-count=2 --stream-to=hdmiin.yuv --stream-poll Pi\u5982\u679c\u5b89\u88c5\u7684\u662f\u5e26\u684c\u9762\u7684\u7cfb\u7edf\uff0c\u53ef\u4ee5\u4f7f\u7528ffplay\u76f4\u63a5\u64ad\u653eyuv\u6587\u4ef6\u3002 ffplay -f rawvideo -video_size 1920x1080 -pixel_format bgr24 hdmiin.yuv windows\u7535\u8111\u53ef\u4ee5\u4f7f\u75287yuv\u7b49\u8f6f\u4ef6\u67e5\u770b.yuv\u6587\u4ef6\uff0c\u6559\u7a0b\u8f93\u5165\u683c\u5f0f\u4e3a1920 1080\uff0c\u6240\u4ee5\u57287yuv\u53f3\u4e0a\u89d2\u683c\u5f0f\u9009\u62e9BGR888\uff0c\u5206\u8fa8\u7387\u8bbe\u7f6e1920 1080\uff0c\u5373\u53ef\u770b\u5230\u4e24\u5e27\u521a\u91c7\u96c6\u5230\u7684\u753b\u9762","title":"\u8f6f\u4ef6\u4f7f\u7528demo"},{"location":"hdmi-csi-i2s/#_3","text":"tc358743\u82af\u7247\u8d44\u6599","title":"\u82af\u7247\u8d44\u6599"},{"location":"hdmi-csi-i2s/#_4","text":"C790","title":"\u53d1\u8d27\u6e05\u5355"},{"location":"hdmi-csi-i2s/#_5","text":"C780A \u6d4b\u8bd5:https://www.youtube.com/watch?v=ecqyINoiHNQ C780B \u6d4b\u8bd5:https://www.youtube.com/watch?v=nc-hwPT2Uak&t=15s","title":"\u6d4b\u8bd5\u89c6\u9891"},{"location":"hdmi-csi-i2s/#_6","text":"\u4e2d\u56fd\u5ba2\u6237\u91c7\u8d2d\u94fe\u63a5\uff1a C790 & C780 \u5176\u5b83\u56fd\u5bb6\u5ba2\u6237\u91c7\u8d2d\u8fde\u63a5\uff1a C779","title":"\u91c7\u8d2d\u8fde\u63a5"},{"location":"hid/","text":"\u89c6\u9891 \u952e\u76d8 \u9f20\u6807 \u5feb\u6377\u952e \u5728v1.4.5\u7248\u672c\u540e\uff0c\u652f\u6301\u81ea\u5b9a\u4e49\u5feb\u6377\u952e,\u627e\u5230shortcuts\u914d\u7f6e\u9879\u76ee, \u5176\u4e2dkey\u4e3aweb ui\u4e0a\u7684\u6309\u94ae\u540d\u79f0\uff0cvalue\u4e3a\u5177\u4f53\u7684\u6309\u952e\u3002 sudo -s vim /mnt/exec/release/config/app.json ## \u9ed8\u8ba4\u914d\u7f6e\u5982\u4e0b\uff1a \"shortcuts\": { \"Ctrl+Alt+Del\": [\"ControlLeft\",\"AltLeft\",\"Delete\"], \"Alt+Tab\": [\"AltLeft\",\"Tab\"], \"Alt+F4\": [\"AltLeft\",\"F4\"], \"Alt+Enter\": [\"AltLeft\",\"Enter\"], \"Ctrl+W\": [\"ControlLeft\",\"KeyW\"] } \u5176\u4e2d\u6309\u952e\u540d\u79f0\u5177\u6709\u552f\u4e00\u6027\uff0c\u4e0b\u9762\u63d0\u4f9b\u5177\u4f53\u7684\u6309\u952e\u540d\u79f0 \"{backspace}\": \"Backspace\", \"{tab}\": \"Tab\", \"{enter}\": \"Enter\", \"{shiftleft}\": \"ShiftLeft\", \"{shiftright}\": \"ShiftRight\", \"{altleft}\": \"AltLeft\", \"{altright}\": \"AltRight\", \"{prtscr}\": \"PrtScr\", \"{pause}\": \"Pause\", \"{scrolllock}\": \"ScrollLock\", \"{controlleft}\": \"ControlLeft\", \"{controlright}\": \"ControlRight\", \"{metaleft}\": \"MetaLeft\", \"{metaright}\": \"MetaRight\", \"{capslock}\": \"CapsLock\", \"{escape}\": \"Escape\", \"{space}\": \"Space\", \"{pageup}\": \"PageUp\", \"{pagedown}\": \"PageDown\", \"{end}\": \"End\", \"{home}\": \"Home\", \"{arrowleft}\": \"ArrowLeft\", \"{arrowup}\": \"ArrowUp\", \"{arrowright}\": \"ArrowRight\", \"{arrowdown}\": \"ArrowDown\", \"{insert}\": \"Insert\", \"{delete}\": \"Delete\", // Digits keys 1: \"Digit1\", 2: \"Digit2\", 3: \"Digit3\", 4: \"Digit4\", 5: \"Digit5\", 6: \"Digit6\", 7: \"Digit7\", 8: \"Digit8\", 9: \"Digit9\", 0: \"Digit0\", // \"!\": \"Digit1\", // ! maps to the '1' key \"@\": \"Digit2\", // @ maps to the '2' key \"#\": \"Digit3\", // # maps to the '3' key $: \"Digit4\", // $ maps to the '4' key \"%\": \"Digit5\", // % maps to the '5' key \"^\": \"Digit6\", // ^ maps to the '6' key \"&\": \"Digit7\", // & maps to the '7' key \"*\": \"Digit8\", // * maps to the '8' key \"(\": \"Digit9\", // ( maps to the '9' key \")\": \"Digit0\", // ) maps to the '0' key a: \"KeyA\", b: \"KeyB\", c: \"KeyC\", d: \"KeyD\", e: \"KeyE\", f: \"KeyF\", g: \"KeyG\", h: \"KeyH\", i: \"KeyI\", j: \"KeyJ\", k: \"KeyK\", l: \"KeyL\", m: \"KeyM\", n: \"KeyN\", o: \"KeyO\", p: \"KeyP\", q: \"KeyQ\", r: \"KeyR\", s: \"KeyS\", t: \"KeyT\", u: \"KeyU\", v: \"KeyV\", w: \"KeyW\", x: \"KeyX\", y: \"KeyY\", z: \"KeyZ\", // A: \"KeyA\", B: \"KeyB\", C: \"KeyC\", D: \"KeyD\", E: \"KeyE\", F: \"KeyF\", G: \"KeyG\", H: \"KeyH\", I: \"KeyI\", J: \"KeyJ\", K: \"KeyK\", L: \"KeyL\", M: \"KeyM\", N: \"KeyN\", O: \"KeyO\", P: \"KeyP\", Q: \"KeyQ\", R: \"KeyR\", S: \"KeyS\", T: \"KeyT\", U: \"KeyU\", V: \"KeyV\", W: \"KeyW\", X: \"KeyX\", Y: \"KeyY\", Z: \"KeyZ\", \"-\": \"Minus\", _: \"Minus\", \"=\": \"Equal\", \"+\": \"Equal\", \"[\": \"BracketLeft\", \"{\": \"BracketLeft\", \"]\": \"BracketRight\", \"}\": \"BracketRight\", \"|\": \"Backslash\", \"\\\\\": \"Backslash\", \"`\": \"Backquote\", \"~\": \"Backquote\", \";\": \"Semicolon\", \":\": \"Semicolon\", \"'\": \"Quote\", '\"': \"Quote\", \",\": \"Comma\", \"<\": \"Comma\", \".\": \"Period\", \">\": \"Period\", \"/\": \"Slash\", \"?\": \"Slash\", // Numpad keys \"{numpad0}\": \"Numpad0\", \"{numpad1}\": \"Numpad1\", \"{numpad2}\": \"Numpad2\", \"{numpad3}\": \"Numpad3\", \"{numpad4}\": \"Numpad4\", \"{numpad5}\": \"Numpad5\", \"{numpad6}\": \"Numpad6\", \"{numpad7}\": \"Numpad7\", \"{numpad8}\": \"Numpad8\", \"{numpad9}\": \"Numpad9\", \"{numlock}\": \"numlock\", \"{numpadmultiply}\": \"NumpadMultiply\", \"{numpadadd}\": \"NumpadAdd\", \"{numpadsubtract}\": \"NumpadSubtract\", \"{numpaddecimal}\": \"NumpadDecimal\", \"{numpaddivide}\": \"NumpadDivide\", \"{numpadenter}\": \"NumpadEnter\", // Function keys \"{f1}\": \"F1\", \"{f2}\": \"F2\", \"{f3}\": \"F3\", \"{f4}\": \"F4\", \"{f5}\": \"F5\", \"{f6}\": \"F6\", \"{f7}\": \"F7\", \"{f8}\": \"F8\", \"{f9}\": \"F9\", \"{f10}\": \"F10\", \"{f11}\": \"F11\", \"{f12}\": \"F12\"","title":"\u89c6\u9891&\u952e\u9f20"},{"location":"hid/#_1","text":"","title":"\u89c6\u9891 \u952e\u76d8 \u9f20\u6807"},{"location":"hid/#_2","text":"\u5728v1.4.5\u7248\u672c\u540e\uff0c\u652f\u6301\u81ea\u5b9a\u4e49\u5feb\u6377\u952e,\u627e\u5230shortcuts\u914d\u7f6e\u9879\u76ee, \u5176\u4e2dkey\u4e3aweb ui\u4e0a\u7684\u6309\u94ae\u540d\u79f0\uff0cvalue\u4e3a\u5177\u4f53\u7684\u6309\u952e\u3002 sudo -s vim /mnt/exec/release/config/app.json ## \u9ed8\u8ba4\u914d\u7f6e\u5982\u4e0b\uff1a \"shortcuts\": { \"Ctrl+Alt+Del\": [\"ControlLeft\",\"AltLeft\",\"Delete\"], \"Alt+Tab\": [\"AltLeft\",\"Tab\"], \"Alt+F4\": [\"AltLeft\",\"F4\"], \"Alt+Enter\": [\"AltLeft\",\"Enter\"], \"Ctrl+W\": [\"ControlLeft\",\"KeyW\"] } \u5176\u4e2d\u6309\u952e\u540d\u79f0\u5177\u6709\u552f\u4e00\u6027\uff0c\u4e0b\u9762\u63d0\u4f9b\u5177\u4f53\u7684\u6309\u952e\u540d\u79f0 \"{backspace}\": \"Backspace\", \"{tab}\": \"Tab\", \"{enter}\": \"Enter\", \"{shiftleft}\": \"ShiftLeft\", \"{shiftright}\": \"ShiftRight\", \"{altleft}\": \"AltLeft\", \"{altright}\": \"AltRight\", \"{prtscr}\": \"PrtScr\", \"{pause}\": \"Pause\", \"{scrolllock}\": \"ScrollLock\", \"{controlleft}\": \"ControlLeft\", \"{controlright}\": \"ControlRight\", \"{metaleft}\": \"MetaLeft\", \"{metaright}\": \"MetaRight\", \"{capslock}\": \"CapsLock\", \"{escape}\": \"Escape\", \"{space}\": \"Space\", \"{pageup}\": \"PageUp\", \"{pagedown}\": \"PageDown\", \"{end}\": \"End\", \"{home}\": \"Home\", \"{arrowleft}\": \"ArrowLeft\", \"{arrowup}\": \"ArrowUp\", \"{arrowright}\": \"ArrowRight\", \"{arrowdown}\": \"ArrowDown\", \"{insert}\": \"Insert\", \"{delete}\": \"Delete\", // Digits keys 1: \"Digit1\", 2: \"Digit2\", 3: \"Digit3\", 4: \"Digit4\", 5: \"Digit5\", 6: \"Digit6\", 7: \"Digit7\", 8: \"Digit8\", 9: \"Digit9\", 0: \"Digit0\", // \"!\": \"Digit1\", // ! maps to the '1' key \"@\": \"Digit2\", // @ maps to the '2' key \"#\": \"Digit3\", // # maps to the '3' key $: \"Digit4\", // $ maps to the '4' key \"%\": \"Digit5\", // % maps to the '5' key \"^\": \"Digit6\", // ^ maps to the '6' key \"&\": \"Digit7\", // & maps to the '7' key \"*\": \"Digit8\", // * maps to the '8' key \"(\": \"Digit9\", // ( maps to the '9' key \")\": \"Digit0\", // ) maps to the '0' key a: \"KeyA\", b: \"KeyB\", c: \"KeyC\", d: \"KeyD\", e: \"KeyE\", f: \"KeyF\", g: \"KeyG\", h: \"KeyH\", i: \"KeyI\", j: \"KeyJ\", k: \"KeyK\", l: \"KeyL\", m: \"KeyM\", n: \"KeyN\", o: \"KeyO\", p: \"KeyP\", q: \"KeyQ\", r: \"KeyR\", s: \"KeyS\", t: \"KeyT\", u: \"KeyU\", v: \"KeyV\", w: \"KeyW\", x: \"KeyX\", y: \"KeyY\", z: \"KeyZ\", // A: \"KeyA\", B: \"KeyB\", C: \"KeyC\", D: \"KeyD\", E: \"KeyE\", F: \"KeyF\", G: \"KeyG\", H: \"KeyH\", I: \"KeyI\", J: \"KeyJ\", K: \"KeyK\", L: \"KeyL\", M: \"KeyM\", N: \"KeyN\", O: \"KeyO\", P: \"KeyP\", Q: \"KeyQ\", R: \"KeyR\", S: \"KeyS\", T: \"KeyT\", U: \"KeyU\", V: \"KeyV\", W: \"KeyW\", X: \"KeyX\", Y: \"KeyY\", Z: \"KeyZ\", \"-\": \"Minus\", _: \"Minus\", \"=\": \"Equal\", \"+\": \"Equal\", \"[\": \"BracketLeft\", \"{\": \"BracketLeft\", \"]\": \"BracketRight\", \"}\": \"BracketRight\", \"|\": \"Backslash\", \"\\\\\": \"Backslash\", \"`\": \"Backquote\", \"~\": \"Backquote\", \";\": \"Semicolon\", \":\": \"Semicolon\", \"'\": \"Quote\", '\"': \"Quote\", \",\": \"Comma\", \"<\": \"Comma\", \".\": \"Period\", \">\": \"Period\", \"/\": \"Slash\", \"?\": \"Slash\", // Numpad keys \"{numpad0}\": \"Numpad0\", \"{numpad1}\": \"Numpad1\", \"{numpad2}\": \"Numpad2\", \"{numpad3}\": \"Numpad3\", \"{numpad4}\": \"Numpad4\", \"{numpad5}\": \"Numpad5\", \"{numpad6}\": \"Numpad6\", \"{numpad7}\": \"Numpad7\", \"{numpad8}\": \"Numpad8\", \"{numpad9}\": \"Numpad9\", \"{numlock}\": \"numlock\", \"{numpadmultiply}\": \"NumpadMultiply\", \"{numpadadd}\": \"NumpadAdd\", \"{numpadsubtract}\": \"NumpadSubtract\", \"{numpaddecimal}\": \"NumpadDecimal\", \"{numpaddivide}\": \"NumpadDivide\", \"{numpadenter}\": \"NumpadEnter\", // Function keys \"{f1}\": \"F1\", \"{f2}\": \"F2\", \"{f3}\": \"F3\", \"{f4}\": \"F4\", \"{f5}\": \"F5\", \"{f6}\": \"F6\", \"{f7}\": \"F7\", \"{f8}\": \"F8\", \"{f9}\": \"F9\", \"{f10}\": \"F10\", \"{f11}\": \"F11\", \"{f12}\": \"F12\"","title":"\u5feb\u6377\u952e"},{"location":"https/","text":"\u52a0\u5bc6\u8bc1\u4e66 blikvm v1.4.9\u7248\u672c\u540e,\u9ed8\u8ba4\u4e3ahttps\u542f\u52a8\uff0c\u5373\u4f7f\u8bbf\u95eehttp\u4e5f\u4f1a\u81ea\u52a8\u88ab\u91cd\u5b9a\u5411\u5230https: sudo -s vim /mnt/exec/release/config/app.json \u627e\u5230\u4e0b\u9762\u914d\u7f6e\u5185\u5bb9\uff0c\u5176\u4e2dkey\u548ccert\u5728 /mnt/exec/release/lib/https/ \u6b64\u8def\u5f84\uff0c\u7528\u6237\u53ef\u4ee5\u81ea\u5df1\u8fdb\u884c\u66ff\u6362\u3002 \"server\": { \"ssl\": { \"key\": \"./lib/https/key.pem\", \"cert\": \"./lib/https/cert.pem\" } Let's Encrypt\u7533\u8bf7\u5408\u6cd5\u8bc1\u4e66: Info \u4f60\u9700\u8981\u6709\u4e00\u4e2a\u516c\u7f51\u5408\u6cd5\u7684\u57df\u540d\u624d\u80fd\u4f7f\u7528Let's Encrypt,\u672c\u8bf4\u660e\u4ee5blikvm.space\u57df\u540d\u4e3a\u4f8b \u5f00\u59cb\u7533\u8bf7\u8bc1\u4e66 \u6267\u884c\u5982\u4e0b\u547d\u4ee4\u5f00\u59cb\u7533\u8bf7\u8bc1\u4e66\uff1a certbot certonly --manual --preferred-challenges dns -d example.com \u5728\u57df\u540d\u63a7\u5236\u53f0\u4e2d\u6dfb\u52a0\u89e3\u6790\u8bb0\u5f55. Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator manual, Installer None Requesting a certificate for blikvm.space Performing the following challenges: dns-01 challenge for blikvm.space - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Please deploy a DNS TXT record under the name _acme-challenge.blikvm.space with the following value: UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc Before continuing, verify the record is deployed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Press Enter to Continue \u6267\u884c\u5b8c\u4e0a\u9762\u547d\u4ee4\u540e,\u4f1a\u6709\u5982\u4e0a\u7c7b\u4f3c\u8f93\u51fa\uff0c\u6839\u636e\u4e0a\u9762\u63d0\u793a\uff0c\u767b\u5f55\u57df\u540d\u540e\u53f0\uff08\u6bd4\u5982\u4e9a\u9a6c\u900a\u4e91\uff0c\u963f\u91cc\u4e91\u3001\u817e\u8baf\u4e91\u7b49\u7b49\uff09\uff0c\u6dfb\u52a0\u540d\u4e3a _acme-challenge.example.com \u7684 TXT \u8bb0\u5f55\uff0c\u5e76\u4f7f\u7528 UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc \u4f5c\u4e3a\u8bb0\u5f55\u503c\u3002 \u5f53DNS\u8bb0\u5f55\u751f\u6548\u540e\uff0c\u70b9\u51fb\u56de\u8f66\u7ee7\u7eed Warn \u7531\u4e8e DNS \u8bb0\u5f55\u4e0d\u4f1a\u9a6c\u4e0a\u751f\u6548\uff0c\u6240\u4ee5\u7a0d\u540e\u518d\u6309\u56de\u8f66\u952e\u3002 \u4f7f\u7528 nslookup -type=TXT _acme-challenge.blikvm.space \u547d\u4ee4\u9a8c\u8bc1 DNS \u662f\u5426\u751f\u6548\uff0c\u751f\u6548\u5982\u4e0b: root@blikvm(rw):/mnt/tmp# nslookup -type=TXT _acme-challenge.blikvm.space Server: 192.168.8.1 Address: 192.168.8.1#53 Non-authoritative answer: _acme-challenge.blikvm.space text = \"UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc\" Authoritative answers can be found from: \u5c06\u4f1a\u6536\u5230\u8bc1\u4e66\u7533\u8bf7\u6210\u529f\u7684\u63d0\u793a\uff08\u7c7b\u4f3c\u5982\u4e0b\u5185\u5bb9\uff09\uff1a Waiting for verification... Cleaning up challenges Subscribe to the EFF mailing list (email: info@blicube.com). IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/blikvm.space/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/blikvm.space/privkey.pem Your certificate will expire on 2025-03-04. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run \"certbot renew\" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le 4. \u4f7f\u7528\u8bc1\u4e66 \u6839\u636e\u6b65\u9aa43\u53ef\u4ee5\u770b\u5230\u8bc1\u4e66\u8def\u5f84\u5728/etc/letsencrypt/live/blikvm.space/\uff0c\u4fee\u6539\u914d\u7f6e\u6587\u4ef6\uff1a vim /mnt/exec/release/config/app.json \u5c06\u4e0b\u9762key\u548ccert\u66ff\u6362\u4e3a \"server\": { \"ssl\": { \"key\": \"/etc/letsencrypt/live/blikvm.space/privkey.pem\", \"cert\": \"/etc/letsencrypt/live/blikvm.space/fullchain.pem\" } 5. \u8bbe\u7f6eblikvm\u7684\u5c40\u57df\u7f51\u57df\u540d\uff0c\u5728pc\u4e0a\u6253\u5f00/etc/hosts,\u5982\u53ef\u4ee5\u589e\u52a0\u4e0b\u9762\u8fd9\u4e00\u884c\uff0c\u8fd9\u91cc\u7684ip\u548c\u57df\u540d\u6839\u636e\u4f60\u7684\u5b9e\u9645\u60c5\u51b5\u800c\u5b9a 192.168.8.16 blikvm.space \u7136\u540e\u4f60\u5c31\u53ef\u4ee5\u76f4\u63a5\u7528\u57df\u540d\u8bbf\u95eeblikvm\u3002","title":"\u52a0\u5bc6\u8bc1\u4e66"},{"location":"https/#_1","text":"blikvm v1.4.9\u7248\u672c\u540e,\u9ed8\u8ba4\u4e3ahttps\u542f\u52a8\uff0c\u5373\u4f7f\u8bbf\u95eehttp\u4e5f\u4f1a\u81ea\u52a8\u88ab\u91cd\u5b9a\u5411\u5230https: sudo -s vim /mnt/exec/release/config/app.json \u627e\u5230\u4e0b\u9762\u914d\u7f6e\u5185\u5bb9\uff0c\u5176\u4e2dkey\u548ccert\u5728 /mnt/exec/release/lib/https/ \u6b64\u8def\u5f84\uff0c\u7528\u6237\u53ef\u4ee5\u81ea\u5df1\u8fdb\u884c\u66ff\u6362\u3002 \"server\": { \"ssl\": { \"key\": \"./lib/https/key.pem\", \"cert\": \"./lib/https/cert.pem\" }","title":"\u52a0\u5bc6\u8bc1\u4e66"},{"location":"https/#lets-encrypt","text":"Info \u4f60\u9700\u8981\u6709\u4e00\u4e2a\u516c\u7f51\u5408\u6cd5\u7684\u57df\u540d\u624d\u80fd\u4f7f\u7528Let's Encrypt,\u672c\u8bf4\u660e\u4ee5blikvm.space\u57df\u540d\u4e3a\u4f8b \u5f00\u59cb\u7533\u8bf7\u8bc1\u4e66 \u6267\u884c\u5982\u4e0b\u547d\u4ee4\u5f00\u59cb\u7533\u8bf7\u8bc1\u4e66\uff1a certbot certonly --manual --preferred-challenges dns -d example.com \u5728\u57df\u540d\u63a7\u5236\u53f0\u4e2d\u6dfb\u52a0\u89e3\u6790\u8bb0\u5f55. Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator manual, Installer None Requesting a certificate for blikvm.space Performing the following challenges: dns-01 challenge for blikvm.space - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Please deploy a DNS TXT record under the name _acme-challenge.blikvm.space with the following value: UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc Before continuing, verify the record is deployed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Press Enter to Continue \u6267\u884c\u5b8c\u4e0a\u9762\u547d\u4ee4\u540e,\u4f1a\u6709\u5982\u4e0a\u7c7b\u4f3c\u8f93\u51fa\uff0c\u6839\u636e\u4e0a\u9762\u63d0\u793a\uff0c\u767b\u5f55\u57df\u540d\u540e\u53f0\uff08\u6bd4\u5982\u4e9a\u9a6c\u900a\u4e91\uff0c\u963f\u91cc\u4e91\u3001\u817e\u8baf\u4e91\u7b49\u7b49\uff09\uff0c\u6dfb\u52a0\u540d\u4e3a _acme-challenge.example.com \u7684 TXT \u8bb0\u5f55\uff0c\u5e76\u4f7f\u7528 UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc \u4f5c\u4e3a\u8bb0\u5f55\u503c\u3002 \u5f53DNS\u8bb0\u5f55\u751f\u6548\u540e\uff0c\u70b9\u51fb\u56de\u8f66\u7ee7\u7eed Warn \u7531\u4e8e DNS \u8bb0\u5f55\u4e0d\u4f1a\u9a6c\u4e0a\u751f\u6548\uff0c\u6240\u4ee5\u7a0d\u540e\u518d\u6309\u56de\u8f66\u952e\u3002 \u4f7f\u7528 nslookup -type=TXT _acme-challenge.blikvm.space \u547d\u4ee4\u9a8c\u8bc1 DNS \u662f\u5426\u751f\u6548\uff0c\u751f\u6548\u5982\u4e0b: root@blikvm(rw):/mnt/tmp# nslookup -type=TXT _acme-challenge.blikvm.space Server: 192.168.8.1 Address: 192.168.8.1#53 Non-authoritative answer: _acme-challenge.blikvm.space text = \"UyC2WAhvG9zDuyDPKAHovW6y-RxpZ1_KB8XnT4UyAnc\" Authoritative answers can be found from: \u5c06\u4f1a\u6536\u5230\u8bc1\u4e66\u7533\u8bf7\u6210\u529f\u7684\u63d0\u793a\uff08\u7c7b\u4f3c\u5982\u4e0b\u5185\u5bb9\uff09\uff1a Waiting for verification... Cleaning up challenges Subscribe to the EFF mailing list (email: info@blicube.com). IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/blikvm.space/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/blikvm.space/privkey.pem Your certificate will expire on 2025-03-04. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run \"certbot renew\" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le 4. \u4f7f\u7528\u8bc1\u4e66 \u6839\u636e\u6b65\u9aa43\u53ef\u4ee5\u770b\u5230\u8bc1\u4e66\u8def\u5f84\u5728/etc/letsencrypt/live/blikvm.space/\uff0c\u4fee\u6539\u914d\u7f6e\u6587\u4ef6\uff1a vim /mnt/exec/release/config/app.json \u5c06\u4e0b\u9762key\u548ccert\u66ff\u6362\u4e3a \"server\": { \"ssl\": { \"key\": \"/etc/letsencrypt/live/blikvm.space/privkey.pem\", \"cert\": \"/etc/letsencrypt/live/blikvm.space/fullchain.pem\" } 5. \u8bbe\u7f6eblikvm\u7684\u5c40\u57df\u7f51\u57df\u540d\uff0c\u5728pc\u4e0a\u6253\u5f00/etc/hosts,\u5982\u53ef\u4ee5\u589e\u52a0\u4e0b\u9762\u8fd9\u4e00\u884c\uff0c\u8fd9\u91cc\u7684ip\u548c\u57df\u540d\u6839\u636e\u4f60\u7684\u5b9e\u9645\u60c5\u51b5\u800c\u5b9a 192.168.8.16 blikvm.space \u7136\u540e\u4f60\u5c31\u53ef\u4ee5\u76f4\u63a5\u7528\u57df\u540d\u8bbf\u95eeblikvm\u3002","title":"Let's Encrypt\u7533\u8bf7\u5408\u6cd5\u8bc1\u4e66:"},{"location":"jetson_nano_tc358743/","text":"\u5728jstson nano\u4e0a\u4f7f\u7528C790 C779 C780 C790\u5168\u90e8\u9002\u7528\u6b64\u6587\u6863\uff0c\u672c\u6587\u6d4b\u8bd5\u5e95\u677f\u4e3ajetson nano b01\uff0c\u82e5\u4f60\u5176\u5b83\u5e95\u677f\u6709\u4e00\u4e9b\u8bbe\u8ba1\u5230\u8ddf\u677f\u5b50\u578b\u53f7\u76f8\u5173\u7684\u6b65\u9aa4\uff0c\u9700\u8981\u5bf9\u5e94\u6539\u53d8\uff0c\u8bf7\u6ce8\u610f\u3002 \u73b0\u5728\u5185\u6838\u6e90\u7801 wget https://developer.nvidia.com/embedded/l4t/r32_release_v7.2/sources/t210/public_sources.tbz2 tar -xf public_sources.tbz2 Linux_for_Tegra/source/public/kernel_src.tbz2 --strip-components=3 tar xf kernel_src.tbz2 \u6839\u636e\u4ed3\u5e93\u91cc\u7684\u76ee\u5f55\u7ed3\u6784\u8fdb\u884c\u6587\u4ef6\u66ff\u6362\uff0c\u8981\u5168\u90e8\u66ff\u6362 git clone https://github.com/ThomasVon2021/jetson_tc358743 cp ~/jetson_tc358743/* ./ -r . \u2514\u2500\u2500 jetson_tc358743-main \u251c\u2500\u2500 hardware \u2502 \u2514\u2500\u2500 nvidia \u2502 \u2514\u2500\u2500 platform \u2502 \u2514\u2500\u2500 t210 \u2502 \u251c\u2500\u2500 batuu \u2502 \u2502 \u2514\u2500\u2500 kernel-dts \u2502 \u2502 \u2514\u2500\u2500 tegra210-p3448-0003-p3542-0000.dts \u2502 \u2514\u2500\u2500 porg \u2502 \u2514\u2500\u2500 kernel-dts \u2502 \u251c\u2500\u2500 Makefile \u2502 \u251c\u2500\u2500 porg-platforms \u2502 \u2502 \u251c\u2500\u2500 tegra210-dual-tc358743.dtsi \u2502 \u2502 \u251c\u2500\u2500 tegra210-porg-dual-tc358743.dtsi \u2502 \u2502 \u251c\u2500\u2500 tegra210-porg-tc358743.dtsi \u2502 \u2502 \u2514\u2500\u2500 tegra210-tc358743.dtsi \u2502 \u251c\u2500\u2500 tegra210-p3448-0000-p3449-0000-b00.dts \u2502 \u251c\u2500\u2500 tegra210-p3448-all-p3449-0000-camera-tc358743-dual.dts \u2502 \u2514\u2500\u2500 tegra210-p3448-common-tc358743.dts \u251c\u2500\u2500 kernel \u2502 \u2514\u2500\u2500 kernel-4.9 \u2502 \u251c\u2500\u2500 drivers \u2502 \u2502 \u2514\u2500\u2500 media \u2502 \u2502 \u2514\u2500\u2500 i2c \u2502 \u2502 \u251c\u2500\u2500 tc358743.c \u2502 \u2502 \u2514\u2500\u2500 tc358743_regs.h \u2502 \u2514\u2500\u2500 include \u2502 \u2514\u2500\u2500 media \u2502 \u2514\u2500\u2500 i2c \u2502 \u2514\u2500\u2500 tc358743.h \u2514\u2500\u2500 README.md \u4ea4\u53c9\u7f16\u8bd1\u94fe\u4e0b\u8f7d,\u540e\u9762make\u65f6\uff0c\u4f60\u9700\u8981\u6307\u5b9a\u7f16\u8bd1\u94fe wget http://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/aarch64-linux-gnu/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz tar xf gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz \u8fdb\u5165\u5230kernel/kernel-4.9/\uff0c\u5148\u914d\u7f6e\u518d\u7f16\u8bd1\uff0c make ARCH=arm64 tegra_defconfig menuconfig Device Drivers > Multimedia Support > I2C Encoders, decoders, sensors and other helper chips Toshiba TC358743 decoder should be * (press y or space on the option) grep -i tc358743 .config #checking if its really enabled make ARCH=arm64 CROSS_COMPILE=/root/work/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu- -j4 \u5c06\u7f16\u8bd1\u51fa\u6765\u7684Image\u548cdtb\u6587\u4ef6\u5206\u522b\u62f7\u8d1d\u5230nano\u7684\u7cfb\u7edf\u7684\u4e0b\u9762\u8def\u5f84\u4e0b,\u82e5\u4f60\u7684\u8f7d\u677f\u4e0d\u662fB01\uff0c\u9700\u8981\u66f4\u6362\u5bf9\u5e94\u7684dtb\u6587\u4ef6\uff0cdtb\u6587\u4ef6\u4e0e\u4f60\u7684\u677f\u5b50\u578b\u53f7\u5bf9\u5e94\u5173\u7cfb\uff0c\u53ef\u4ee5\u67e5\u627e wiki kernel/kernel-4.9/arch/arm64/boot/Image ==> /boot/Image kernel/kernel-4.9/arch/arm64/boot/dts/tegra210-p3448-0000-p3449-0000-b00.dtb ==> /boot/veyecam/ #\u5176\u4e2d\u4f60\u7684nano\u8def\u5f84\u5982\u679c\u4e0d\u5b58\u5728veyecam\u6587\u4ef6\u5939\uff0c\u5148\u521b\u5efa sudo mkdir /boot/veyecam/ sudo cp / /boot/veyecam/ -f \u5148\u5907\u4efd extlinux.conf \u6587\u4ef6\uff0c\u7136\u540e\u7f16\u8f91/boot/extlinux/extlinux.conf\u6587\u4ef6\uff0c\u5728\u8be5\u6587\u4ef6\u4e0b\u589e\u52a0\uff1a FDT /boot/veyecam/ \u6ce8\u610f \u4e3a\u4f60\u7248\u672c\u7f16\u8bd1\u51fa\u6765\u7684dtb\u5b9e\u9645\u6587\u4ef6\u540d\uff0c \u91cd\u542f\u540e\u751f\u6548","title":"\u5728jstson nano\u4e0a\u4f7f\u7528C790"},{"location":"jetson_nano_tc358743/#jstson-nanoc790","text":"C779 C780 C790\u5168\u90e8\u9002\u7528\u6b64\u6587\u6863\uff0c\u672c\u6587\u6d4b\u8bd5\u5e95\u677f\u4e3ajetson nano b01\uff0c\u82e5\u4f60\u5176\u5b83\u5e95\u677f\u6709\u4e00\u4e9b\u8bbe\u8ba1\u5230\u8ddf\u677f\u5b50\u578b\u53f7\u76f8\u5173\u7684\u6b65\u9aa4\uff0c\u9700\u8981\u5bf9\u5e94\u6539\u53d8\uff0c\u8bf7\u6ce8\u610f\u3002 \u73b0\u5728\u5185\u6838\u6e90\u7801 wget https://developer.nvidia.com/embedded/l4t/r32_release_v7.2/sources/t210/public_sources.tbz2 tar -xf public_sources.tbz2 Linux_for_Tegra/source/public/kernel_src.tbz2 --strip-components=3 tar xf kernel_src.tbz2 \u6839\u636e\u4ed3\u5e93\u91cc\u7684\u76ee\u5f55\u7ed3\u6784\u8fdb\u884c\u6587\u4ef6\u66ff\u6362\uff0c\u8981\u5168\u90e8\u66ff\u6362 git clone https://github.com/ThomasVon2021/jetson_tc358743 cp ~/jetson_tc358743/* ./ -r . \u2514\u2500\u2500 jetson_tc358743-main \u251c\u2500\u2500 hardware \u2502 \u2514\u2500\u2500 nvidia \u2502 \u2514\u2500\u2500 platform \u2502 \u2514\u2500\u2500 t210 \u2502 \u251c\u2500\u2500 batuu \u2502 \u2502 \u2514\u2500\u2500 kernel-dts \u2502 \u2502 \u2514\u2500\u2500 tegra210-p3448-0003-p3542-0000.dts \u2502 \u2514\u2500\u2500 porg \u2502 \u2514\u2500\u2500 kernel-dts \u2502 \u251c\u2500\u2500 Makefile \u2502 \u251c\u2500\u2500 porg-platforms \u2502 \u2502 \u251c\u2500\u2500 tegra210-dual-tc358743.dtsi \u2502 \u2502 \u251c\u2500\u2500 tegra210-porg-dual-tc358743.dtsi \u2502 \u2502 \u251c\u2500\u2500 tegra210-porg-tc358743.dtsi \u2502 \u2502 \u2514\u2500\u2500 tegra210-tc358743.dtsi \u2502 \u251c\u2500\u2500 tegra210-p3448-0000-p3449-0000-b00.dts \u2502 \u251c\u2500\u2500 tegra210-p3448-all-p3449-0000-camera-tc358743-dual.dts \u2502 \u2514\u2500\u2500 tegra210-p3448-common-tc358743.dts \u251c\u2500\u2500 kernel \u2502 \u2514\u2500\u2500 kernel-4.9 \u2502 \u251c\u2500\u2500 drivers \u2502 \u2502 \u2514\u2500\u2500 media \u2502 \u2502 \u2514\u2500\u2500 i2c \u2502 \u2502 \u251c\u2500\u2500 tc358743.c \u2502 \u2502 \u2514\u2500\u2500 tc358743_regs.h \u2502 \u2514\u2500\u2500 include \u2502 \u2514\u2500\u2500 media \u2502 \u2514\u2500\u2500 i2c \u2502 \u2514\u2500\u2500 tc358743.h \u2514\u2500\u2500 README.md \u4ea4\u53c9\u7f16\u8bd1\u94fe\u4e0b\u8f7d,\u540e\u9762make\u65f6\uff0c\u4f60\u9700\u8981\u6307\u5b9a\u7f16\u8bd1\u94fe wget http://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/aarch64-linux-gnu/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz tar xf gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz \u8fdb\u5165\u5230kernel/kernel-4.9/\uff0c\u5148\u914d\u7f6e\u518d\u7f16\u8bd1\uff0c make ARCH=arm64 tegra_defconfig menuconfig Device Drivers > Multimedia Support > I2C Encoders, decoders, sensors and other helper chips Toshiba TC358743 decoder should be * (press y or space on the option) grep -i tc358743 .config #checking if its really enabled make ARCH=arm64 CROSS_COMPILE=/root/work/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu- -j4 \u5c06\u7f16\u8bd1\u51fa\u6765\u7684Image\u548cdtb\u6587\u4ef6\u5206\u522b\u62f7\u8d1d\u5230nano\u7684\u7cfb\u7edf\u7684\u4e0b\u9762\u8def\u5f84\u4e0b,\u82e5\u4f60\u7684\u8f7d\u677f\u4e0d\u662fB01\uff0c\u9700\u8981\u66f4\u6362\u5bf9\u5e94\u7684dtb\u6587\u4ef6\uff0cdtb\u6587\u4ef6\u4e0e\u4f60\u7684\u677f\u5b50\u578b\u53f7\u5bf9\u5e94\u5173\u7cfb\uff0c\u53ef\u4ee5\u67e5\u627e wiki kernel/kernel-4.9/arch/arm64/boot/Image ==> /boot/Image kernel/kernel-4.9/arch/arm64/boot/dts/tegra210-p3448-0000-p3449-0000-b00.dtb ==> /boot/veyecam/ #\u5176\u4e2d\u4f60\u7684nano\u8def\u5f84\u5982\u679c\u4e0d\u5b58\u5728veyecam\u6587\u4ef6\u5939\uff0c\u5148\u521b\u5efa sudo mkdir /boot/veyecam/ sudo cp / /boot/veyecam/ -f \u5148\u5907\u4efd extlinux.conf \u6587\u4ef6\uff0c\u7136\u540e\u7f16\u8f91/boot/extlinux/extlinux.conf\u6587\u4ef6\uff0c\u5728\u8be5\u6587\u4ef6\u4e0b\u589e\u52a0\uff1a FDT /boot/veyecam/ \u6ce8\u610f \u4e3a\u4f60\u7248\u672c\u7f16\u8bd1\u51fa\u6765\u7684dtb\u5b9e\u9645\u6587\u4ef6\u540d\uff0c \u91cd\u542f\u540e\u751f\u6548","title":"\u5728jstson nano\u4e0a\u4f7f\u7528C790"},{"location":"make-image/","text":"Make your owner image \u5f53\u4f60\u5bf9\u955c\u50cf\u8fdb\u884c\u4e86\u4fee\u6539\uff0c\u60f3\u5236\u4f5c\u81ea\u5df1\u7684\u955c\u50cf\u65f6\uff0c\u53ef\u4ee5\u53c2\u8003\u4e0b\u9762\u5728linux\u4e0b\u7684\u65b9\u6cd5\uff0c\u5236\u4f5c\u4e00\u4e2a\u6700\u5c0f\u955c\u50cf\u3002 \u9996\u5148\u4f7f\u7528gparted\u8f6f\u4ef6\uff0c\u6253\u5f00\u6240\u8981\u5236\u4f5c\u7684\u955c\u50cf\u7684sd\u5361\u3002\u5c06\u672a\u4f7f\u7528\u7684\u7a7a\u95f4\u901a\u8fc7gparted\u8f6f\u4ef6\u5c06\u5176\u5206\u5272\u51fa\u6765\uff0c\u5e76\u5c06\u5176\u8bbe\u7f6e\u4e3a\u672a\u5206\u914d\u3002\u8fd9\u6837\u5236\u4f5c\u955c\u50cf\u65f6\uff0c\u8fd9\u90e8\u5206\u65e0\u4efb\u4f55\u6709\u6548\u5185\u5bb9\u7684\u7a7a\u95f4\u5c31\u4e0d\u4f1a\u88ab\u5236\u4f5c\u4e86\u3002 \u7136\u540e\u4f7f\u7528\u9996\u5148\u4f7f\u7528fdisk\u547d\u4ee4\u67e5\u770b\u6709\u6548\u7a7a\u95f4\u7684\u5927\u5c0f\uff0c\u5982\u4e0b\u56fe,\u537310151935\u3002 \u7136\u540e\u4f7f\u7528dd\u547d\u4ee4\u5f80\u4e00\u4e2a\u7a7a\u7684img\u6587\u4ef6\u91cc\u5199\u5165\u5373\u53ef,\u5176\u4e2dcount\u7684\u5927\u5c0f\u6bd4fdisk\u770b\u5230\u7684\u5377\u5c3e\u5927\u5c0f\u5927\u4e8e1\u5373\u53ef\u3002 touch blikvm-armbian-v4-20230623.img sudo dd if=/dev/sdb of=./blikvm-armbian-v4-20230623.img bs=512 count=10151936 \u7b49\u5f85dd\u547d\u4ee4\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002","title":"\u5236\u4f5c\u955c\u50cf"},{"location":"make-image/#make-your-owner-image","text":"\u5f53\u4f60\u5bf9\u955c\u50cf\u8fdb\u884c\u4e86\u4fee\u6539\uff0c\u60f3\u5236\u4f5c\u81ea\u5df1\u7684\u955c\u50cf\u65f6\uff0c\u53ef\u4ee5\u53c2\u8003\u4e0b\u9762\u5728linux\u4e0b\u7684\u65b9\u6cd5\uff0c\u5236\u4f5c\u4e00\u4e2a\u6700\u5c0f\u955c\u50cf\u3002 \u9996\u5148\u4f7f\u7528gparted\u8f6f\u4ef6\uff0c\u6253\u5f00\u6240\u8981\u5236\u4f5c\u7684\u955c\u50cf\u7684sd\u5361\u3002\u5c06\u672a\u4f7f\u7528\u7684\u7a7a\u95f4\u901a\u8fc7gparted\u8f6f\u4ef6\u5c06\u5176\u5206\u5272\u51fa\u6765\uff0c\u5e76\u5c06\u5176\u8bbe\u7f6e\u4e3a\u672a\u5206\u914d\u3002\u8fd9\u6837\u5236\u4f5c\u955c\u50cf\u65f6\uff0c\u8fd9\u90e8\u5206\u65e0\u4efb\u4f55\u6709\u6548\u5185\u5bb9\u7684\u7a7a\u95f4\u5c31\u4e0d\u4f1a\u88ab\u5236\u4f5c\u4e86\u3002 \u7136\u540e\u4f7f\u7528\u9996\u5148\u4f7f\u7528fdisk\u547d\u4ee4\u67e5\u770b\u6709\u6548\u7a7a\u95f4\u7684\u5927\u5c0f\uff0c\u5982\u4e0b\u56fe,\u537310151935\u3002 \u7136\u540e\u4f7f\u7528dd\u547d\u4ee4\u5f80\u4e00\u4e2a\u7a7a\u7684img\u6587\u4ef6\u91cc\u5199\u5165\u5373\u53ef,\u5176\u4e2dcount\u7684\u5927\u5c0f\u6bd4fdisk\u770b\u5230\u7684\u5377\u5c3e\u5927\u5c0f\u5927\u4e8e1\u5373\u53ef\u3002 touch blikvm-armbian-v4-20230623.img sudo dd if=/dev/sdb of=./blikvm-armbian-v4-20230623.img bs=512 count=10151936 \u7b49\u5f85dd\u547d\u4ee4\u6267\u884c\u5b8c\u6210\u5373\u53ef\u3002","title":"Make your owner image"},{"location":"modify_pikvm_image/","text":"\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u9700\u8981\u505a\u4ee5\u4e0b\u4fee\u6539\u6765\u9002\u914dBLIKVM\u786c\u4ef6 \u56e0\u4e3ablikvm\u786c\u4ef6\u5b9e\u73b0\u65b9\u6848\u548cPiKVM\u786c\u4ef6\u5b9e\u73b0\u65b9\u6848\u5e76\u4e0d\u5b8c\u5168\u76f8\u540c\uff0c\u56e0\u6b64\u9488\u5bf9PiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u60a8\u9700\u8981\u901a\u8fc7\u4e0b\u5217\u914d\u7f6e\u4fee\u6539\u4e00\u4e9b\u9519\u8bef\u3002\u5f53\u7136\u60a8\u53ef\u4ee5\u4f7f\u7528\u6211\u4eec\u5df2\u7ecf\u505a\u597d\u914d\u7f6e\u7684 \u955c\u50cf \u98ce\u6247 \u56e0BLIKVM\u786c\u4ef6\u4e0ePiKVM\u4f7f\u7528\u98ce\u6247\u4e0d\u540c\uff0c\u9996\u5148\u9700\u66ff\u6362\u63a7\u5236\u98ce\u6247\u811a\u672c\uff0c\u4e0b\u5217\u9ed8\u8ba4\u5f00\u59cb\u98ce\u6247\u6e29\u5ea6\u4e3a40\u6444\u6c0f\u5ea6 su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro \u7f16\u8f91/etc/kvmd/override.yaml\u6587\u4ef6\uff0c\u6dfb\u52a0\u4e0b\u5217\u5185\u5bb9\u5df2\u53bb\u9664Web UI\u5173\u4e8e\u98ce\u6247\u7684\u9519\u8bef\u8b66\u544a\u3002 kvmd: info: fan: unix: '' 2. EDID\u6587\u4ef6\u66f4\u6362 EDID\u6587\u4ef6\u4f5c\u7528\u4e3a\uff0c\u8bbe\u7f6e\u88ab\u63a7\u8ba1\u7b97\u673a\u6309\u7167\u671f\u671b\u7684\u5206\u8fa8\u7387\u8fdb\u884c\u8f93\u5165\uff0c\u7531\u4e8ePiKVM\u4e0d\u540c\u65f6\u671f\u7684\u955c\u50cfEDID\u6587\u4ef6\u4e0d\u4e00\u5b9a\u662f\u6ee1\u8db31080P60Hz, \u5f53\u4f60\u4f7f\u7528\u7684\u786c\u4ef6\u4e3aCM4\u7248\u672c\uff0c\u53d1\u73b0\u88ab\u63a7\u7535\u8111\u9ed8\u8ba4\u8f93\u51fa\u4e0d\u662f1080P60Hz\uff0c\u53ef\u4ee5\u901a\u8fc7\u4fee\u6539/etc/kvmd/tc358743-edid.hex\u4e3a\u4e0b\u5217\u5185\u5bb9\uff1a 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 \u786e\u8ba4 /boot/config.txt \u6dfb\u52a0\u4e86\u4e0b\u5217\u914d\u7f6e\uff0c\u4ece\u800c\u652f\u63011080p60hz\u89c6\u9891\u8f93\u5165\u548c\u58f0\u97f3\u8f93\u5165\uff0c\u76f8\u5173\u914d\u7f6e\u53c2\u8003\u5982\u4e0b\uff1a # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio \u5982\u679c\u4f60\u4f7f\u7528webrtc\u6ca1\u6709\u58f0\u97f3\uff0c\u5c1d\u8bd5\u5728/etc/kvmd/janus/janus.plugin.ustreamer.jcfg\u6b64\u6587\u4ef6\u4e2d\u6dfb\u52a0\u4e0b\u5217\u5185\u5bb9 audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" } 3. OLED\u542f\u7528 PiKVM\u955c\u50cf\uff0c\u6309\u7167\u4e0b\u9762\u7684\u65b9\u6cd5\u542f\u7528OLED\u3002 \u5982\u679c\u60a8\u4f7f\u7528PiKVM\u955c\u50cf\uff0c\u8bf7\u767b\u5f55\u5230PiKVM\u5e76\u8fd0\u884c\u4ee5\u4e0b\u547d\u4ee4\uff1a # rw # systemctl enable --now kvmd-oled //\u542f\u7528OLED # ro \u5982\u679cOLED\u4ecd\u7136\u65e0\u6cd5\u5de5\u4f5c\uff0c\u60a8\u9700\u8981\u68c0\u67e5\"/boot/config.txt\"\u6587\u4ef6\u4e2d\u662f\u5426\u6709\"dtparam=i2c_arm=on\"\uff0c\u4ee5\u53ca\"/etc/modules-load.d/i2c.conf\"\u6587\u4ef6\u4e2d\u662f\u5426\u6709\"i2c-dev\"\u3002\u5982\u679c\u6ca1\u6709\uff0c\u8bf7\u521b\u5efa\u5e76\u6dfb\u52a0\u5b83\u4eec\u3002 \u5982\u679c\u5728\u4e0a\u8ff0\u914d\u7f6e\u4e4b\u540e\u4ecd\u7136\u65e0\u6cd5\u5de5\u4f5c\uff0c\u8bf7\u523b\u5f55 blikvm\u63d0\u4f9b\u7684\u6d4b\u8bd5\u955c\u50cf \u6765\u68c0\u67e5OLED\u786c\u4ef6\u662f\u5426\u635f\u574f\u3002 4. \u5173\u4e8e v4mini \u955c\u50cf\u7684\u914d\u7f6e \u5982\u679c\u4f60\u60f3\u5728 blikvm v1 \u548c v2 \u4e0a\u4f7f\u7528 PiKVM v4mini \u955c\u50cf\uff0c\u7531\u4e8e v4mini \u955c\u50cf\u4f7f\u7528\u4e86\u4e0d\u540c\u7684 GPIO \u5f15\u811a\u6765\u63a7\u5236 ATX\uff0c\u56e0\u6b64\u4f60\u9700\u8981\u8fdb\u884c\u4ee5\u4e0b\u8986\u76d6\u914d\u7f6e\u3002\u5982\u679c\u4f60\u5e0c\u671b\u5728 blikvm v1 \u6216 v2 \u7248\u672c\u4e0a\u8fd0\u884c v4mini \u955c\u50cf\u5e76\u80fd\u591f\u4f7f\u7528 ATX \u63a7\u5236\uff0c\u4f60\u5fc5\u987b\u8fdb\u884c\u8fd9\u4e9b\u4fee\u6539\uff1b\u5982\u679c\u4e0d\u8fdb\u884c\u66f4\u6539\uff0cATX \u63a7\u5236\u5c06\u65e0\u6cd5\u6b63\u5e38\u5de5\u4f5c\uff08LED \u5f15\u811a\u4e0d\u540c\uff09\u3002 \u7f16\u8f91 /etc/kvmd/override.yaml \u6587\u4ef6\uff0c\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff1a kvmd: ### \u7981\u7528\u98ce\u6247\u63d2\u5ea7\u68c0\u67e5 ### info: fan: unix: '' atx: hdd_led_pin: 22 power_led_pin: 24 power_switch_pin: 23 reset_switch_pin: 27 type: gpio gpio: scheme: __v3_usb_breaker__: pin: 5 mode: output initial: false pulse: delay: 0","title":"\u914d\u7f6ePiKVM OS"},{"location":"modify_pikvm_image/#pikvmblikvm","text":"\u56e0\u4e3ablikvm\u786c\u4ef6\u5b9e\u73b0\u65b9\u6848\u548cPiKVM\u786c\u4ef6\u5b9e\u73b0\u65b9\u6848\u5e76\u4e0d\u5b8c\u5168\u76f8\u540c\uff0c\u56e0\u6b64\u9488\u5bf9PiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u60a8\u9700\u8981\u901a\u8fc7\u4e0b\u5217\u914d\u7f6e\u4fee\u6539\u4e00\u4e9b\u9519\u8bef\u3002\u5f53\u7136\u60a8\u53ef\u4ee5\u4f7f\u7528\u6211\u4eec\u5df2\u7ecf\u505a\u597d\u914d\u7f6e\u7684 \u955c\u50cf","title":"\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fPiKVM\u5b98\u65b9\u955c\u50cf\uff0c\u9700\u8981\u505a\u4ee5\u4e0b\u4fee\u6539\u6765\u9002\u914dBLIKVM\u786c\u4ef6"},{"location":"modify_pikvm_image/#_1","text":"\u56e0BLIKVM\u786c\u4ef6\u4e0ePiKVM\u4f7f\u7528\u98ce\u6247\u4e0d\u540c\uff0c\u9996\u5148\u9700\u66ff\u6362\u63a7\u5236\u98ce\u6247\u811a\u672c\uff0c\u4e0b\u5217\u9ed8\u8ba4\u5f00\u59cb\u98ce\u6247\u6e29\u5ea6\u4e3a40\u6444\u6c0f\u5ea6 su - rw git clone https://github.com/ThomasVon2021/blikvm.git cd blikvm/package/kvmd-fan bash install-kvmd-fan.sh ro \u7f16\u8f91/etc/kvmd/override.yaml\u6587\u4ef6\uff0c\u6dfb\u52a0\u4e0b\u5217\u5185\u5bb9\u5df2\u53bb\u9664Web UI\u5173\u4e8e\u98ce\u6247\u7684\u9519\u8bef\u8b66\u544a\u3002 kvmd: info: fan: unix: ''","title":"\u98ce\u6247"},{"location":"modify_pikvm_image/#2-edid","text":"EDID\u6587\u4ef6\u4f5c\u7528\u4e3a\uff0c\u8bbe\u7f6e\u88ab\u63a7\u8ba1\u7b97\u673a\u6309\u7167\u671f\u671b\u7684\u5206\u8fa8\u7387\u8fdb\u884c\u8f93\u5165\uff0c\u7531\u4e8ePiKVM\u4e0d\u540c\u65f6\u671f\u7684\u955c\u50cfEDID\u6587\u4ef6\u4e0d\u4e00\u5b9a\u662f\u6ee1\u8db31080P60Hz, \u5f53\u4f60\u4f7f\u7528\u7684\u786c\u4ef6\u4e3aCM4\u7248\u672c\uff0c\u53d1\u73b0\u88ab\u63a7\u7535\u8111\u9ed8\u8ba4\u8f93\u51fa\u4e0d\u662f1080P60Hz\uff0c\u53ef\u4ee5\u901a\u8fc7\u4fee\u6539/etc/kvmd/tc358743-edid.hex\u4e3a\u4e0b\u5217\u5185\u5bb9\uff1a 00FFFFFFFFFFFF005262888800888888 1C150103800000780AEE91A3544C9926 0F505400000001010101010101010101 010101010101011D007251D01E206E28 5500C48E2100001E8C0AD08A20E02D10 103E9600138E2100001E000000FC0054 6F73686962612D4832430A20000000FD 003B3D0F2E0F1E0A202020202020014F 020323454F041303021211012021A23C 3D3E1F102309070766030C00300080E3 007F8C8C0AD08A20E02D10103E9600C4 8E210000188C0AD08A20E02D10103E96 00138E210000188C0AA01451F0160026 7C4300138E2100009800000000000000 00000000000000000000000000000000 00000000000000000000000000000087 \u786e\u8ba4 /boot/config.txt \u6dfb\u52a0\u4e86\u4e0b\u5217\u914d\u7f6e\uff0c\u4ece\u800c\u652f\u63011080p60hz\u89c6\u9891\u8f93\u5165\u548c\u58f0\u97f3\u8f93\u5165\uff0c\u76f8\u5173\u914d\u7f6e\u53c2\u8003\u5982\u4e0b\uff1a # Video and audio dtoverlay=tc358743,4lane=1 dtoverlay=tc358743-audio \u5982\u679c\u4f60\u4f7f\u7528webrtc\u6ca1\u6709\u58f0\u97f3\uff0c\u5c1d\u8bd5\u5728/etc/kvmd/janus/janus.plugin.ustreamer.jcfg\u6b64\u6587\u4ef6\u4e2d\u6dfb\u52a0\u4e0b\u5217\u5185\u5bb9 audio: { device = \"hw:0,0\" tc358743 = \"/dev/kvmd-video\" }","title":"2. EDID\u6587\u4ef6\u66f4\u6362"},{"location":"modify_pikvm_image/#3-oled","text":"PiKVM\u955c\u50cf\uff0c\u6309\u7167\u4e0b\u9762\u7684\u65b9\u6cd5\u542f\u7528OLED\u3002 \u5982\u679c\u60a8\u4f7f\u7528PiKVM\u955c\u50cf\uff0c\u8bf7\u767b\u5f55\u5230PiKVM\u5e76\u8fd0\u884c\u4ee5\u4e0b\u547d\u4ee4\uff1a # rw # systemctl enable --now kvmd-oled //\u542f\u7528OLED # ro \u5982\u679cOLED\u4ecd\u7136\u65e0\u6cd5\u5de5\u4f5c\uff0c\u60a8\u9700\u8981\u68c0\u67e5\"/boot/config.txt\"\u6587\u4ef6\u4e2d\u662f\u5426\u6709\"dtparam=i2c_arm=on\"\uff0c\u4ee5\u53ca\"/etc/modules-load.d/i2c.conf\"\u6587\u4ef6\u4e2d\u662f\u5426\u6709\"i2c-dev\"\u3002\u5982\u679c\u6ca1\u6709\uff0c\u8bf7\u521b\u5efa\u5e76\u6dfb\u52a0\u5b83\u4eec\u3002 \u5982\u679c\u5728\u4e0a\u8ff0\u914d\u7f6e\u4e4b\u540e\u4ecd\u7136\u65e0\u6cd5\u5de5\u4f5c\uff0c\u8bf7\u523b\u5f55 blikvm\u63d0\u4f9b\u7684\u6d4b\u8bd5\u955c\u50cf \u6765\u68c0\u67e5OLED\u786c\u4ef6\u662f\u5426\u635f\u574f\u3002","title":"3. OLED\u542f\u7528"},{"location":"modify_pikvm_image/#4-v4mini","text":"\u5982\u679c\u4f60\u60f3\u5728 blikvm v1 \u548c v2 \u4e0a\u4f7f\u7528 PiKVM v4mini \u955c\u50cf\uff0c\u7531\u4e8e v4mini \u955c\u50cf\u4f7f\u7528\u4e86\u4e0d\u540c\u7684 GPIO \u5f15\u811a\u6765\u63a7\u5236 ATX\uff0c\u56e0\u6b64\u4f60\u9700\u8981\u8fdb\u884c\u4ee5\u4e0b\u8986\u76d6\u914d\u7f6e\u3002\u5982\u679c\u4f60\u5e0c\u671b\u5728 blikvm v1 \u6216 v2 \u7248\u672c\u4e0a\u8fd0\u884c v4mini \u955c\u50cf\u5e76\u80fd\u591f\u4f7f\u7528 ATX \u63a7\u5236\uff0c\u4f60\u5fc5\u987b\u8fdb\u884c\u8fd9\u4e9b\u4fee\u6539\uff1b\u5982\u679c\u4e0d\u8fdb\u884c\u66f4\u6539\uff0cATX \u63a7\u5236\u5c06\u65e0\u6cd5\u6b63\u5e38\u5de5\u4f5c\uff08LED \u5f15\u811a\u4e0d\u540c\uff09\u3002 \u7f16\u8f91 /etc/kvmd/override.yaml \u6587\u4ef6\uff0c\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff1a kvmd: ### \u7981\u7528\u98ce\u6247\u63d2\u5ea7\u68c0\u67e5 ### info: fan: unix: '' atx: hdd_led_pin: 22 power_led_pin: 24 power_switch_pin: 23 reset_switch_pin: 27 type: gpio gpio: scheme: __v3_usb_breaker__: pin: 5 mode: output initial: false pulse: delay: 0","title":"4.\u5173\u4e8e v4mini \u955c\u50cf\u7684\u914d\u7f6e"},{"location":"msd/","text":"U\u76d8\u8bbe\u5907\u6a21\u62df \u91cd\u88c5\u7cfb\u7edf\u89c6\u9891 BliKVM\u652f\u6301U\u76d8\u8bbe\u5907\u6a21\u62df\uff0c\u901a\u8fc7\u6b64\u529f\u80fd\u53ef\u4ee5\u8fdb\u884c\u8fdc\u7a0b\u6302\u8f7d\u955c\u50cf\uff0c\u8fdb\u884c\u91cd\u88c5\u7cfb\u7edf\u3002 Web UI msd\u865a\u62dfU\u76d8\u5165\u53e3\u4e3a: \u4f7f\u7528web\u4e0a\u4f20\u955c\u50cf\u548c\u5236\u4f5c\u542f\u52a8\u76d8\uff0c\u5747\u662f\u540c\u6b65\u7ebf\u7a0b\uff0c\u4e0a\u4f20\u955c\u50cf\u9000\u51faMSD\u7684UI\u754c\u9762\u540e\uff0c\u4e0b\u6b21\u518d\u9009\u62e9\u76f8\u540c\u955c\u50cf\u53ef\u65ad\u70b9\u7eed\u4f20\u3002\u5236\u4f5c\u542f\u52a8\u76d8\u63a8\u51fa\u540e\u4e0d\u53ef\u65ad\u70b9\u91cd\u505a\uff0c\u9700\u91cd\u65b0\u5f00\u59cb\u3002 \u4e0a\u4f20\u955c\u50cf\u9ed8\u8ba4\u8def\u5f84\u4e3a/mnt/upload,\u82e5\u51fa\u73b0\u4e0a\u4f20\u5931\u8d25\uff0c\u5220\u9664\u4e3a\u6210\u529f\u7684\u7f13\u5b58\u6587\u4ef6\uff0c\u53ef\u624b\u52a8\u5220\u9664\u6b64\u6587\u4ef6\u5939\uff1b \u56e0\u90e8\u5206\u955c\u50cf\u6587\u4ef6\u5927\u5c0f\u8f83\u5927\uff0c\u91c7\u53d6\u4e0a\u4f20\u955c\u50cf\u65b9\u6848\u4e3a\u5207\u7247\u4e0a\u4f20\u548c\u5408\u5e76\uff0c\u5408\u5e76\u8fc7\u7a0b\u4e0d\u80fd\u65ad\u70b9\u91cd\u6765\uff0c\u5207\u8bb0\u7b49\u5f85\u5408\u5e76\u5b8c\u6210\u540e(\u65f6\u95f4\u8f83\u957f)\uff0c\u518d\u8fdb\u5165\u4e0b\u4e00\u6b65\uff1b \u5236\u4f5c\u542f\u52a8\u76d8\u4e5f\u5f88\u4e3a\u4e24\u4e2a\u6b65\u9aa4\uff0c\u5236\u4f5c\u865a\u62dfU\u76d8\uff0c\u5c06\u9009\u62e9\u7684iso\u955c\u50cf\u62f7\u8d1d\u5230\u5236\u4f5c\u597d\u7684\u865a\u62dfU\u76d8\u91cc\uff0c\u4e24\u4e2a\u6b65\u9aa4\u5747\u6709\u8fdb\u5ea6\uff0c\u8bf7\u7b49\u4e24\u8005\u8fdb\u5ea6\u5747100%\u540e\u518d\u70b9\u51fb\u4e0b\u4e00\u6b65\u6309\u94ae\u3002 \u624b\u52a8 (\u4e0d\u4f7f\u7528Web UI) 1. \u786e\u8ba4\u7cfb\u7edf\u5b58\u5728\u4e0b\u97624\u4e2a\u8def\u5f84\u3002\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662f\u6700\u65b0\u7684BliKVM\u955c\u50cf\uff0c\u65e0\u9700\u8fdb\u884c\u68c0\u67e5\u3002\u5176\u4e2d/opt/bin/msd/user\u8def\u5f84\u7528\u4e8e\u5b58\u653e\u7cfb\u7edf\u955c\u50cf\u3002 /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy 2. \u901a\u8fc7SSH\u767b\u9646\u5230BliKVM\u7ec8\u7aef\uff0c\u7528\u6237\u540d\u548c\u5bc6\u7801\u5747\u4e3ablikvm\uff0c\u901a\u8fc7rw\u547d\u4ee4\uff0c\u4f7f\u53ea\u8bfb\u7cfb\u7edf\u53d8\u4e3a\u53ef\u5199\u7cfb\u7edf\u3002 sudo rw 3. \u5728\u4f60\u63a7\u5236\u7aef\u7684\u7535\u8111\uff0c\u53ef\u4ee5\u5728\u7ec8\u7aef\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06iso\u955c\u50cf\u6587\u4ef6\u62f7\u8d1d\u5230BliKVM\u955c\u50cf\u7684\u6307\u5b9a\u8def\u5f84\u4e0b\u3002 scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ \u5f53\u7136\uff0c\u4f60\u4e5f\u53ef\u4ee5\u901a\u8fc7\u5176\u4ed6\u4efb\u4f55\u4f60\u719f\u6089\u7684\u65b9\u5f0f\u5c06iso\u955c\u50cf\u6587\u4ef6\u62f7\u8d1d\u5230\u6307\u5b9a\u8def\u5f84\u4e0b\u3002 4. \u901a\u8fc7\u4f7f\u7528\u4e0b\u5217\u4e24\u79cd\u547d\u4ee4\u4e2d\u7684\u4e00\u4e2a\uff0c\u5c06\u955c\u50cf\u62f7\u8d1d\u5230\u6a21\u62df\u7684U\u76d8\u4e2d\u3002U\u76d8\u9ed8\u8ba4\u5927\u5c0f\u8bbe\u7f6e\u7684\u4e3a5GB\uff0c\u5982\u679c\u4f60\u9700\u8981\u66f4\u5927\u7684\u7a7a\u95f4\uff0c\u4f60\u9700\u8981\u4fee\u6539kvmd-msd.sh\u811a\u672c\u3002 \u5982\u679c /mnt/msd/user \u8def\u5f84\u4e0b\u53ea\u6709\u4e00\u4e2a\u955c\u50cf\u6587\u4ef6, \u4f60\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528\u6b64\u547d\u4ee4. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make \u5982\u679c /mnt/msd/user \u8def\u5f84\u4e0b\u6709\u4e0d\u6b62\u4e00\u4e2a\u955c\u50cf\u6587\u4ef6, \u4f60\u53ef\u4ee5\u4f7f\u7528\u4e0b\u5217\u6587\u4ef6\u6307\u5b9a. xxx.iso \u8868\u793a\u955c\u50cf\u7684\u540d\u79f0.\u5176\u4e2d-s\u540e\u8ddf\u7684\u6570\u5b57\u5373\u662f\u5236\u4f5c\u7684U\u76d8\u7684\u5927\u5c0f\uff0c\u5355\u4f4d\u662fG\uff0c\u7528\u6237\u53ef\u4ee5\u6839\u636e\u81ea\u5df1\u9700\u6c42\u4fee\u6539\u3002-n\u540e\u8ddf\u7684\u5b57\u7b26\u4e32\u662fu\u76d8\u540d\u79f0\u3002 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso cp\u8fc7\u7a0b\u975e\u5e38\u6162\uff0c\u8bf7\u8010\u5fc3\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u3002 5. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06\u6a21\u62df\u7684U\u76d8\u8fde\u63a5\u5230\u5230\u4f60\u7684\u88ab\u63a7\u8bbe\u5907\u4e0a sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn 6. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06\u6a21\u62df\u7684U\u76d8\u4ece\u4f60\u7684\u88ab\u63a7\u8bbe\u5907\u4e0a\u5f39\u51fa sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn 7. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u6e05\u9664\u6389\u6a21\u62df\u7684U\u76d8\uff0c\u5c06\u4f1a\u91ca\u653e\u6389\u5bf9\u5e94\u7684\u7a7a\u95f4 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean 8. \u4e00\u5207\u6b63\u786e\u7684\u8bdd\uff0c\u6b64\u65f6\u4f60\u53ef\u4ee5\u5728\u4e00\u4e2aPC\u7cfb\u7edf\u91cc\u770b\u5230\u4f60\u6a21\u62df\u51fa\u7684U\u76d8\u3002\u901a\u8fc7WEB\u91cd\u542f\u7684\u4f60\u7684PC\uff0c\u7136\u540e\u4f7f\u7528\u5feb\u6377\u952e\uff08\u5f88\u591a\u7535\u8111\u662f\u6309F2\uff09\u8fdb\u5165BIOS\uff0c\u4fee\u6539boot\u542f\u52a8\u4f18\u5148\u7ea7\uff0c\u5c06\u6a21\u62df\u51fa\u7684U\u76d8\u8bbe\u5907\u4f18\u5148\u7ea7\u8bbe\u7f6e\u5728\u6700\u524d\u9762\u3002 9. \u6839\u636ebios\u7cfb\u7edf\u63d0\u793a\uff0c\u4fdd\u5b58\u91cd\u542f\uff0c\u5373\u53ef\u8fdb\u884cventoy\u7684\u5f15\u5bfc\u754c\u9762\u8fdb\u884c\u91cd\u88c5\u7cfb\u7edf\u3002 \u901a\u7528U\u76d8 \u4f20\u9012\u901a\u7528\u6587\u4ef6\uff0c\u6ce8\u610f\u6587\u4ef6\u540d\u9700\u547d\u540d\u4e3a\u82f1\u6587\uff0c\u4e2d\u6587\u4f1a\u4e71\u7801\u3002 conn\uff0c disconn, clean\u547d\u4ee4\u9488\u5bf9\u901a\u7528U\u76d8\u4f9d\u65e7\u6709\u6548\u3002 \u5236\u4f5c\u901a\u7528U\u76d8 -s\u540e\u8ddf\u7684\u662f\u5236\u4f5c\u901a\u7528U\u76d8\u7684\u5927\u5c0f\uff0c\u5355\u4f4d\u4e3aGb\uff0c\u5bb9\u91cf\u8d8a\u5927\uff0c\u5236\u4f5c\u65f6\u95f4\u8d8a\u957f\uff0c\u8bf7\u7ed3\u5408\u5b9e\u9645\u60c5\u51b5\u8bbe\u7f6e\u3002 -t \u5fc5\u987b\u4e3aother sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 4 -t other \u6587\u4ef6\u4ece\u7528\u6237\u7535\u8111==\u300bKVM==\u300b\u88ab\u63a7\u7535\u8111 \u9996\u5148\u4f60\u9700\u8981\u5c06\u6587\u4ef6\u4ece\u7528\u6237\u63a7\u5236\u7535\u8111\u53d1\u9001\u5230kvm scp xxx blikvm@xxxx:/mnt/msd/user/ \u5c06\u6587\u4ef6\u540c\u6b65\u5230\u88ab\u63a7\u7535\u8111\uff0c\u5e76\u8fde\u63a5\u4e0a\u7535\u8111 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c forward \u540e\u9762\u6709\u9700\u8981\u65b0\u7684\u5185\u5bb9\u4ece\u7528\u6237\u7535\u8111\uff0c\u4f20\u9012\u5230\u88ab\u63a7\u7535\u8111\uff0c\u91cd\u590d\u7b2c1\u548c\u7b2c2\u6b65\u5373\u53ef \u6587\u4ef6\u4ece\u88ab\u63a7\u7535\u8111==\u300bKVM==\u7528\u6237\u7535\u8111 \u9996\u5148\u5728\u88ab\u63a7\u7535\u8111\u4e0a\u5c06\u6587\u4ef6\u62f7\u8d1d\u5230\u6a21\u62df\u7684\u865a\u62dfU\u76d8\u91cc\uff0c\u7136\u540e\u6267\u884c\u4e0b\u9762\u7684\u6307\u4ee4\uff0c\u5c06\u6587\u4ef6\u62f7\u8d1d\u5230kvm\u7684/mnt/msd/user/\u76ee\u5f55\u4e0b sudo bash /usr/bin/blikvm/kvmd-msd.sh -c rever \u5c06\u6587\u4ef6\u4ecekvm\u62f7\u8d1d\u5230\u7528\u6237\u7535\u8111 scp blikvm@xxxx:/mnt/msd/user/* .","title":"U\u76d8\u9a71\u52a8"},{"location":"msd/#u","text":"\u91cd\u88c5\u7cfb\u7edf\u89c6\u9891 BliKVM\u652f\u6301U\u76d8\u8bbe\u5907\u6a21\u62df\uff0c\u901a\u8fc7\u6b64\u529f\u80fd\u53ef\u4ee5\u8fdb\u884c\u8fdc\u7a0b\u6302\u8f7d\u955c\u50cf\uff0c\u8fdb\u884c\u91cd\u88c5\u7cfb\u7edf\u3002","title":"U\u76d8\u8bbe\u5907\u6a21\u62df"},{"location":"msd/#web-ui","text":"msd\u865a\u62dfU\u76d8\u5165\u53e3\u4e3a: \u4f7f\u7528web\u4e0a\u4f20\u955c\u50cf\u548c\u5236\u4f5c\u542f\u52a8\u76d8\uff0c\u5747\u662f\u540c\u6b65\u7ebf\u7a0b\uff0c\u4e0a\u4f20\u955c\u50cf\u9000\u51faMSD\u7684UI\u754c\u9762\u540e\uff0c\u4e0b\u6b21\u518d\u9009\u62e9\u76f8\u540c\u955c\u50cf\u53ef\u65ad\u70b9\u7eed\u4f20\u3002\u5236\u4f5c\u542f\u52a8\u76d8\u63a8\u51fa\u540e\u4e0d\u53ef\u65ad\u70b9\u91cd\u505a\uff0c\u9700\u91cd\u65b0\u5f00\u59cb\u3002 \u4e0a\u4f20\u955c\u50cf\u9ed8\u8ba4\u8def\u5f84\u4e3a/mnt/upload,\u82e5\u51fa\u73b0\u4e0a\u4f20\u5931\u8d25\uff0c\u5220\u9664\u4e3a\u6210\u529f\u7684\u7f13\u5b58\u6587\u4ef6\uff0c\u53ef\u624b\u52a8\u5220\u9664\u6b64\u6587\u4ef6\u5939\uff1b \u56e0\u90e8\u5206\u955c\u50cf\u6587\u4ef6\u5927\u5c0f\u8f83\u5927\uff0c\u91c7\u53d6\u4e0a\u4f20\u955c\u50cf\u65b9\u6848\u4e3a\u5207\u7247\u4e0a\u4f20\u548c\u5408\u5e76\uff0c\u5408\u5e76\u8fc7\u7a0b\u4e0d\u80fd\u65ad\u70b9\u91cd\u6765\uff0c\u5207\u8bb0\u7b49\u5f85\u5408\u5e76\u5b8c\u6210\u540e(\u65f6\u95f4\u8f83\u957f)\uff0c\u518d\u8fdb\u5165\u4e0b\u4e00\u6b65\uff1b \u5236\u4f5c\u542f\u52a8\u76d8\u4e5f\u5f88\u4e3a\u4e24\u4e2a\u6b65\u9aa4\uff0c\u5236\u4f5c\u865a\u62dfU\u76d8\uff0c\u5c06\u9009\u62e9\u7684iso\u955c\u50cf\u62f7\u8d1d\u5230\u5236\u4f5c\u597d\u7684\u865a\u62dfU\u76d8\u91cc\uff0c\u4e24\u4e2a\u6b65\u9aa4\u5747\u6709\u8fdb\u5ea6\uff0c\u8bf7\u7b49\u4e24\u8005\u8fdb\u5ea6\u5747100%\u540e\u518d\u70b9\u51fb\u4e0b\u4e00\u6b65\u6309\u94ae\u3002","title":"Web UI"},{"location":"msd/#web-ui_1","text":"1. \u786e\u8ba4\u7cfb\u7edf\u5b58\u5728\u4e0b\u97624\u4e2a\u8def\u5f84\u3002\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662f\u6700\u65b0\u7684BliKVM\u955c\u50cf\uff0c\u65e0\u9700\u8fdb\u884c\u68c0\u67e5\u3002\u5176\u4e2d/opt/bin/msd/user\u8def\u5f84\u7528\u4e8e\u5b58\u653e\u7cfb\u7edf\u955c\u50cf\u3002 /usr/bin/blikvm/ventoy-1.0.88 /usr/bin/blikvm/kvmd-msd.sh /mnt/msd/user /mnt/msd/ventoy 2. \u901a\u8fc7SSH\u767b\u9646\u5230BliKVM\u7ec8\u7aef\uff0c\u7528\u6237\u540d\u548c\u5bc6\u7801\u5747\u4e3ablikvm\uff0c\u901a\u8fc7rw\u547d\u4ee4\uff0c\u4f7f\u53ea\u8bfb\u7cfb\u7edf\u53d8\u4e3a\u53ef\u5199\u7cfb\u7edf\u3002 sudo rw 3. \u5728\u4f60\u63a7\u5236\u7aef\u7684\u7535\u8111\uff0c\u53ef\u4ee5\u5728\u7ec8\u7aef\u4f7f\u7528\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06iso\u955c\u50cf\u6587\u4ef6\u62f7\u8d1d\u5230BliKVM\u955c\u50cf\u7684\u6307\u5b9a\u8def\u5f84\u4e0b\u3002 scp ***.iso blikvm@xxx.xxx.xxx.xxx:/mnt/msd/user/ \u5f53\u7136\uff0c\u4f60\u4e5f\u53ef\u4ee5\u901a\u8fc7\u5176\u4ed6\u4efb\u4f55\u4f60\u719f\u6089\u7684\u65b9\u5f0f\u5c06iso\u955c\u50cf\u6587\u4ef6\u62f7\u8d1d\u5230\u6307\u5b9a\u8def\u5f84\u4e0b\u3002 4. \u901a\u8fc7\u4f7f\u7528\u4e0b\u5217\u4e24\u79cd\u547d\u4ee4\u4e2d\u7684\u4e00\u4e2a\uff0c\u5c06\u955c\u50cf\u62f7\u8d1d\u5230\u6a21\u62df\u7684U\u76d8\u4e2d\u3002U\u76d8\u9ed8\u8ba4\u5927\u5c0f\u8bbe\u7f6e\u7684\u4e3a5GB\uff0c\u5982\u679c\u4f60\u9700\u8981\u66f4\u5927\u7684\u7a7a\u95f4\uff0c\u4f60\u9700\u8981\u4fee\u6539kvmd-msd.sh\u811a\u672c\u3002 \u5982\u679c /mnt/msd/user \u8def\u5f84\u4e0b\u53ea\u6709\u4e00\u4e2a\u955c\u50cf\u6587\u4ef6, \u4f60\u53ef\u4ee5\u76f4\u63a5\u4f7f\u7528\u6b64\u547d\u4ee4. sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make \u5982\u679c /mnt/msd/user \u8def\u5f84\u4e0b\u6709\u4e0d\u6b62\u4e00\u4e2a\u955c\u50cf\u6587\u4ef6, \u4f60\u53ef\u4ee5\u4f7f\u7528\u4e0b\u5217\u6587\u4ef6\u6307\u5b9a. xxx.iso \u8868\u793a\u955c\u50cf\u7684\u540d\u79f0.\u5176\u4e2d-s\u540e\u8ddf\u7684\u6570\u5b57\u5373\u662f\u5236\u4f5c\u7684U\u76d8\u7684\u5927\u5c0f\uff0c\u5355\u4f4d\u662fG\uff0c\u7528\u6237\u53ef\u4ee5\u6839\u636e\u81ea\u5df1\u9700\u6c42\u4fee\u6539\u3002-n\u540e\u8ddf\u7684\u5b57\u7b26\u4e32\u662fu\u76d8\u540d\u79f0\u3002 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 5 -n ventoy -f xxx.iso cp\u8fc7\u7a0b\u975e\u5e38\u6162\uff0c\u8bf7\u8010\u5fc3\u7b49\u5f85\u6267\u884c\u5b8c\u6210\u3002 5. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06\u6a21\u62df\u7684U\u76d8\u8fde\u63a5\u5230\u5230\u4f60\u7684\u88ab\u63a7\u8bbe\u5907\u4e0a sudo bash /usr/bin/blikvm/kvmd-msd.sh -c conn 6. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u5c06\u6a21\u62df\u7684U\u76d8\u4ece\u4f60\u7684\u88ab\u63a7\u8bbe\u5907\u4e0a\u5f39\u51fa sudo bash /usr/bin/blikvm/kvmd-msd.sh -c disconn 7. \u8fd0\u884c\u4e0b\u5217\u547d\u4ee4\uff0c\u6e05\u9664\u6389\u6a21\u62df\u7684U\u76d8\uff0c\u5c06\u4f1a\u91ca\u653e\u6389\u5bf9\u5e94\u7684\u7a7a\u95f4 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c clean 8. \u4e00\u5207\u6b63\u786e\u7684\u8bdd\uff0c\u6b64\u65f6\u4f60\u53ef\u4ee5\u5728\u4e00\u4e2aPC\u7cfb\u7edf\u91cc\u770b\u5230\u4f60\u6a21\u62df\u51fa\u7684U\u76d8\u3002\u901a\u8fc7WEB\u91cd\u542f\u7684\u4f60\u7684PC\uff0c\u7136\u540e\u4f7f\u7528\u5feb\u6377\u952e\uff08\u5f88\u591a\u7535\u8111\u662f\u6309F2\uff09\u8fdb\u5165BIOS\uff0c\u4fee\u6539boot\u542f\u52a8\u4f18\u5148\u7ea7\uff0c\u5c06\u6a21\u62df\u51fa\u7684U\u76d8\u8bbe\u5907\u4f18\u5148\u7ea7\u8bbe\u7f6e\u5728\u6700\u524d\u9762\u3002 9. \u6839\u636ebios\u7cfb\u7edf\u63d0\u793a\uff0c\u4fdd\u5b58\u91cd\u542f\uff0c\u5373\u53ef\u8fdb\u884cventoy\u7684\u5f15\u5bfc\u754c\u9762\u8fdb\u884c\u91cd\u88c5\u7cfb\u7edf\u3002","title":"\u624b\u52a8 (\u4e0d\u4f7f\u7528Web UI)"},{"location":"msd/#u_1","text":"\u4f20\u9012\u901a\u7528\u6587\u4ef6\uff0c\u6ce8\u610f\u6587\u4ef6\u540d\u9700\u547d\u540d\u4e3a\u82f1\u6587\uff0c\u4e2d\u6587\u4f1a\u4e71\u7801\u3002 conn\uff0c disconn, clean\u547d\u4ee4\u9488\u5bf9\u901a\u7528U\u76d8\u4f9d\u65e7\u6709\u6548\u3002","title":"\u901a\u7528U\u76d8"},{"location":"msd/#u_2","text":"-s\u540e\u8ddf\u7684\u662f\u5236\u4f5c\u901a\u7528U\u76d8\u7684\u5927\u5c0f\uff0c\u5355\u4f4d\u4e3aGb\uff0c\u5bb9\u91cf\u8d8a\u5927\uff0c\u5236\u4f5c\u65f6\u95f4\u8d8a\u957f\uff0c\u8bf7\u7ed3\u5408\u5b9e\u9645\u60c5\u51b5\u8bbe\u7f6e\u3002 -t \u5fc5\u987b\u4e3aother sudo bash /usr/bin/blikvm/kvmd-msd.sh -c make -s 4 -t other","title":"\u5236\u4f5c\u901a\u7528U\u76d8"},{"location":"msd/#kvm","text":"\u9996\u5148\u4f60\u9700\u8981\u5c06\u6587\u4ef6\u4ece\u7528\u6237\u63a7\u5236\u7535\u8111\u53d1\u9001\u5230kvm scp xxx blikvm@xxxx:/mnt/msd/user/ \u5c06\u6587\u4ef6\u540c\u6b65\u5230\u88ab\u63a7\u7535\u8111\uff0c\u5e76\u8fde\u63a5\u4e0a\u7535\u8111 sudo bash /usr/bin/blikvm/kvmd-msd.sh -c forward \u540e\u9762\u6709\u9700\u8981\u65b0\u7684\u5185\u5bb9\u4ece\u7528\u6237\u7535\u8111\uff0c\u4f20\u9012\u5230\u88ab\u63a7\u7535\u8111\uff0c\u91cd\u590d\u7b2c1\u548c\u7b2c2\u6b65\u5373\u53ef","title":"\u6587\u4ef6\u4ece\u7528\u6237\u7535\u8111==\u300bKVM==\u300b\u88ab\u63a7\u7535\u8111"},{"location":"msd/#kvm_1","text":"\u9996\u5148\u5728\u88ab\u63a7\u7535\u8111\u4e0a\u5c06\u6587\u4ef6\u62f7\u8d1d\u5230\u6a21\u62df\u7684\u865a\u62dfU\u76d8\u91cc\uff0c\u7136\u540e\u6267\u884c\u4e0b\u9762\u7684\u6307\u4ee4\uff0c\u5c06\u6587\u4ef6\u62f7\u8d1d\u5230kvm\u7684/mnt/msd/user/\u76ee\u5f55\u4e0b sudo bash /usr/bin/blikvm/kvmd-msd.sh -c rever \u5c06\u6587\u4ef6\u4ecekvm\u62f7\u8d1d\u5230\u7528\u6237\u7535\u8111 scp blikvm@xxxx:/mnt/msd/user/* .","title":"\u6587\u4ef6\u4ece\u88ab\u63a7\u7535\u8111==\u300bKVM==\u7528\u6237\u7535\u8111"},{"location":"port-forwarding/","text":"\u7aef\u53e3\u8f6c\u53d1 \u5728v1.4.7\u7248\u672c\u540e,\u5982\u679c\u60a8\u7684ISP\u4e3a\u8def\u7531\u5668\u63d0\u4f9b\u4e86\u5916\u90e8IP\u5730\u5740\uff0c\u60a8\u53ef\u4ee5\u914d\u7f6e\u7aef\u53e3\u8f6c\u53d1\u4ee5\u8bbf\u95eeBliKVM\u3002 Web\u5982\u679c\u9009\u62e9\u4e3ahttp\u534f\u8bae\uff0c\u5360\u7528\u7684\u662f80\u7aef\u53e3\uff0c\u5982\u679c\u9009\u62e9\u7684\u4e3ahttps\u534f\u8bae\u5360\u7528\u7684\u662f443\uff1b \u5982\u679c\u60a8\u6ca1\u6709\u5916\u90e8IP\u5730\u5740\uff0c\u6211\u4eec\u5efa\u8bae\u5c1d\u8bd5\u4f7f\u7528 Tailscale VPN \u3002","title":"\u7aef\u53e3\u8f6c\u53d1"},{"location":"port-forwarding/#_1","text":"\u5728v1.4.7\u7248\u672c\u540e,\u5982\u679c\u60a8\u7684ISP\u4e3a\u8def\u7531\u5668\u63d0\u4f9b\u4e86\u5916\u90e8IP\u5730\u5740\uff0c\u60a8\u53ef\u4ee5\u914d\u7f6e\u7aef\u53e3\u8f6c\u53d1\u4ee5\u8bbf\u95eeBliKVM\u3002 Web\u5982\u679c\u9009\u62e9\u4e3ahttp\u534f\u8bae\uff0c\u5360\u7528\u7684\u662f80\u7aef\u53e3\uff0c\u5982\u679c\u9009\u62e9\u7684\u4e3ahttps\u534f\u8bae\u5360\u7528\u7684\u662f443\uff1b \u5982\u679c\u60a8\u6ca1\u6709\u5916\u90e8IP\u5730\u5740\uff0c\u6211\u4eec\u5efa\u8bae\u5c1d\u8bd5\u4f7f\u7528 Tailscale VPN \u3002","title":"\u7aef\u53e3\u8f6c\u53d1"},{"location":"rtc/","text":"RTC\u65f6\u949f RTC\uff08Real-Time Clock\uff0c\u5b9e\u65f6\u65f6\u949f\uff09\u7684\u4f5c\u7528\u662f\u63d0\u4f9b\u8bbe\u5907\u6216\u7cfb\u7edf\u7684\u5b9e\u65f6\u65f6\u95f4\u548c\u65e5\u671f\u4fe1\u606f\u3002\u5b83\u662f\u4e00\u4e2a\u72ec\u7acb\u7684\u65f6\u949f\u82af\u7247\u6216\u6a21\u5757\uff0c\u5177\u6709\u81ea\u5df1\u7684\u7535\u6e90\uff0c\u53ef\u4ee5\u5728\u8bbe\u5907\u5173\u95ed\u6216\u65ad\u7535\u65f6\u4ecd\u7136\u4fdd\u6301\u65f6\u95f4\u7684\u51c6\u786e\u6027\u3002\u56e0\u56fd\u9645\u5feb\u9012\u7535\u6c60\u4e0d\u65b9\u4fbf\u90ae\u5bc4\u95ee\u9898\uff0c\u51fa\u5382\u786c\u4ef6\u65e0\u7535\u6c60\uff0c\u9700\u7528\u6237\u81ea\u5df1\u8d2d\u4e70(\u7ebd\u6263\u7535\u6c60\u578b\u53f7CR1220)\u3002BliKVM\u4e0d\u540c\u786c\u4ef6\u7248\u672c\u4e0a\u4f7f\u7528\u7684RTC\u65f6\u949f\u578b\u53f7\u4e0d\u5b8c\u5168\u4e00\u6837\uff0c\u4f7f\u7528\u65b9\u6cd5\u4e5f\u7565\u6709\u4e0d\u540c\u3002 BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563 1. \u68c0\u67e5i2c\u603b\u7ebf\u4e0a\u662f\u5426\u6b63\u5e38\u8bc6\u522b\u5230\u4e86pcf8563 RTC\u65f6\u949f\u786c\u4ef6\uff0cpcf8563\u7684i2c\u5730\u5740\u662fx51\uff0c\u672c\u8282\u6240\u6709\u547d\u4ee4\u5747\u9700\u5728root\u6743\u9650\u4e0b\uff0c\u6267\u884c\u4e0b\u9762\u7684\u547d\u4ee4\u80fd\u6b63\u786e\u67e5\u770b\u5230x51\u5373\u8bc1\u660ertc\u65f6\u949f\u5df2\u88abi2c\u603b\u7ebf\u6b63\u786e\u8bc6\u522b\u5230\u3002 root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. \u5411Linux \u7cfb\u7edf\u7684i2c\u5b50\u7cfb\u7edf\u6ce8\u518c\u4e00\u4e2a\u65b0\u7684i2c\u8bbe\u5907\uff0c\u8be5\u8bbe\u5907\u7684\u578b\u53f7\u662f pcf8563\uff0c\u8bbe\u5907\u7684i2c\u5730\u5740\u4e3a 0x51\u3002\u518d\u4f7f\u7528 ls /dev | grep rtc \u547d\u4ee4\u67e5\u770b\u662f\u5426\u6b63\u786e\u51fa\u73b0rtc1\u8bbe\u5907\uff0c\u51fa\u73b0\u5373\u6ce8\u518c\u6210\u529f\u3002 echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. \u5c06\u5f53\u524d\u7cfb\u7edf\u65f6\u95f4\u8bbe\u7f6e\u4e3artc\u65f6\u949f\u65f6\u95f4\u3002 hwclock -f /dev/rtc0 -w 4. \u4ecertc\u65f6\u949f\u8bfb\u53d6\u65f6\u95f4\uff0c\u5982\u679c\u80fd\u8bfb\u53d6\u5230\u65f6\u95f4\u5373\u8868\u660ertc\u6a21\u5757\u6b63\u5e38\u3002 root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30 BliKVM V4 - pcf8563 1. \u68c0\u67e5i2c\u603b\u7ebf\u4e0a\u662f\u5426\u6b63\u5e38\u8bc6\u522b\u5230\u4e86pcf8563 RTC\u65f6\u949f\u786c\u4ef6\uff0cpcf8563\u7684i2c\u5730\u5740\u662fx51\uff0c\u672c\u8282\u6240\u6709\u547d\u4ee4\u5747\u9700\u5728root\u6743\u9650\u4e0b\uff0c\u6267\u884c\u4e0b\u9762\u7684\u547d\u4ee4\u80fd\u6b63\u786e\u67e5\u770b\u5230x51\u5373\u8bc1\u660ertc\u65f6\u949f\u5df2\u88abi2c\u603b\u7ebf\u6b63\u786e\u8bc6\u522b\u5230\u3002 root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. \u5411Linux \u7cfb\u7edf\u7684i2c\u5b50\u7cfb\u7edf\u6ce8\u518c\u4e00\u4e2a\u65b0\u7684i2c\u8bbe\u5907\uff0c\u8be5\u8bbe\u5907\u7684\u578b\u53f7\u662f pcf8563\uff0c\u8bbe\u5907\u7684i2c\u5730\u5740\u4e3a 0x51\u3002\u518d\u4f7f\u7528 ls /dev | grep rtc \u547d\u4ee4\u67e5\u770b\u662f\u5426\u6b63\u786e\u51fa\u73b0rtc1\u8bbe\u5907\uff0c\u51fa\u73b0\u5373\u6ce8\u518c\u6210\u529f\u3002 echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. \u5c06\u5f53\u524d\u7cfb\u7edf\u65f6\u95f4\u8bbe\u7f6e\u4e3artc\u65f6\u949f\u65f6\u95f4\u3002 hwclock -f /dev/rtc1 -w 4. \u4ecertc\u65f6\u949f\u8bfb\u53d6\u65f6\u95f4\uff0c\u5982\u679c\u80fd\u8bfb\u53d6\u5230\u65f6\u95f4\u5373\u8868\u660ertc\u6a21\u5757\u6b63\u5e38\u3002 root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"RTC\u65f6\u949f"},{"location":"rtc/#rtc","text":"RTC\uff08Real-Time Clock\uff0c\u5b9e\u65f6\u65f6\u949f\uff09\u7684\u4f5c\u7528\u662f\u63d0\u4f9b\u8bbe\u5907\u6216\u7cfb\u7edf\u7684\u5b9e\u65f6\u65f6\u95f4\u548c\u65e5\u671f\u4fe1\u606f\u3002\u5b83\u662f\u4e00\u4e2a\u72ec\u7acb\u7684\u65f6\u949f\u82af\u7247\u6216\u6a21\u5757\uff0c\u5177\u6709\u81ea\u5df1\u7684\u7535\u6e90\uff0c\u53ef\u4ee5\u5728\u8bbe\u5907\u5173\u95ed\u6216\u65ad\u7535\u65f6\u4ecd\u7136\u4fdd\u6301\u65f6\u95f4\u7684\u51c6\u786e\u6027\u3002\u56e0\u56fd\u9645\u5feb\u9012\u7535\u6c60\u4e0d\u65b9\u4fbf\u90ae\u5bc4\u95ee\u9898\uff0c\u51fa\u5382\u786c\u4ef6\u65e0\u7535\u6c60\uff0c\u9700\u7528\u6237\u81ea\u5df1\u8d2d\u4e70(\u7ebd\u6263\u7535\u6c60\u578b\u53f7CR1220)\u3002BliKVM\u4e0d\u540c\u786c\u4ef6\u7248\u672c\u4e0a\u4f7f\u7528\u7684RTC\u65f6\u949f\u578b\u53f7\u4e0d\u5b8c\u5168\u4e00\u6837\uff0c\u4f7f\u7528\u65b9\u6cd5\u4e5f\u7565\u6709\u4e0d\u540c\u3002","title":"RTC\u65f6\u949f"},{"location":"rtc/#blikvm-v2-pcie-and-blikvm-v3-hat-pcf8563","text":"1. \u68c0\u67e5i2c\u603b\u7ebf\u4e0a\u662f\u5426\u6b63\u5e38\u8bc6\u522b\u5230\u4e86pcf8563 RTC\u65f6\u949f\u786c\u4ef6\uff0cpcf8563\u7684i2c\u5730\u5740\u662fx51\uff0c\u672c\u8282\u6240\u6709\u547d\u4ee4\u5747\u9700\u5728root\u6743\u9650\u4e0b\uff0c\u6267\u884c\u4e0b\u9762\u7684\u547d\u4ee4\u80fd\u6b63\u786e\u67e5\u770b\u5230x51\u5373\u8bc1\u660ertc\u65f6\u949f\u5df2\u88abi2c\u603b\u7ebf\u6b63\u786e\u8bc6\u522b\u5230\u3002 root@mangopimcore:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. \u5411Linux \u7cfb\u7edf\u7684i2c\u5b50\u7cfb\u7edf\u6ce8\u518c\u4e00\u4e2a\u65b0\u7684i2c\u8bbe\u5907\uff0c\u8be5\u8bbe\u5907\u7684\u578b\u53f7\u662f pcf8563\uff0c\u8bbe\u5907\u7684i2c\u5730\u5740\u4e3a 0x51\u3002\u518d\u4f7f\u7528 ls /dev | grep rtc \u547d\u4ee4\u67e5\u770b\u662f\u5426\u6b63\u786e\u51fa\u73b0rtc1\u8bbe\u5907\uff0c\u51fa\u73b0\u5373\u6ce8\u518c\u6210\u529f\u3002 echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-1/new_device 3. \u5c06\u5f53\u524d\u7cfb\u7edf\u65f6\u95f4\u8bbe\u7f6e\u4e3artc\u65f6\u949f\u65f6\u95f4\u3002 hwclock -f /dev/rtc0 -w 4. \u4ecertc\u65f6\u949f\u8bfb\u53d6\u65f6\u95f4\uff0c\u5982\u679c\u80fd\u8bfb\u53d6\u5230\u65f6\u95f4\u5373\u8868\u660ertc\u6a21\u5757\u6b63\u5e38\u3002 root@mangopimcore:~# hwclock -f /dev/rtc0 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V2 PCIe and BliKVM V3 Hat - pcf8563"},{"location":"rtc/#blikvm-v4-pcf8563","text":"1. \u68c0\u67e5i2c\u603b\u7ebf\u4e0a\u662f\u5426\u6b63\u5e38\u8bc6\u522b\u5230\u4e86pcf8563 RTC\u65f6\u949f\u786c\u4ef6\uff0cpcf8563\u7684i2c\u5730\u5740\u662fx51\uff0c\u672c\u8282\u6240\u6709\u547d\u4ee4\u5747\u9700\u5728root\u6743\u9650\u4e0b\uff0c\u6267\u884c\u4e0b\u9762\u7684\u547d\u4ee4\u80fd\u6b63\u786e\u67e5\u770b\u5230x51\u5373\u8bc1\u660ertc\u65f6\u949f\u5df2\u88abi2c\u603b\u7ebf\u6b63\u786e\u8bc6\u522b\u5230\u3002 root@mangopimcore:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 2. \u5411Linux \u7cfb\u7edf\u7684i2c\u5b50\u7cfb\u7edf\u6ce8\u518c\u4e00\u4e2a\u65b0\u7684i2c\u8bbe\u5907\uff0c\u8be5\u8bbe\u5907\u7684\u578b\u53f7\u662f pcf8563\uff0c\u8bbe\u5907\u7684i2c\u5730\u5740\u4e3a 0x51\u3002\u518d\u4f7f\u7528 ls /dev | grep rtc \u547d\u4ee4\u67e5\u770b\u662f\u5426\u6b63\u786e\u51fa\u73b0rtc1\u8bbe\u5907\uff0c\u51fa\u73b0\u5373\u6ce8\u518c\u6210\u529f\u3002 echo pcf8563 0x51 > /sys/class/i2c-adapter/i2c-0/new_device 3. \u5c06\u5f53\u524d\u7cfb\u7edf\u65f6\u95f4\u8bbe\u7f6e\u4e3artc\u65f6\u949f\u65f6\u95f4\u3002 hwclock -f /dev/rtc1 -w 4. \u4ecertc\u65f6\u949f\u8bfb\u53d6\u65f6\u95f4\uff0c\u5982\u679c\u80fd\u8bfb\u53d6\u5230\u65f6\u95f4\u5373\u8868\u660ertc\u6a21\u5757\u6b63\u5e38\u3002 root@mangopimcore:~# hwclock -f /dev/rtc1 -r 2023-05-28 05:04:08.679152-02:30","title":"BliKVM V4 - pcf8563"},{"location":"serial_over_usb/","text":"\u4e32\u53e3\u7ec8\u7aef\u8fde\u63a5 \u53ef\u4ee5\u901a\u8fc7\u4e32\u53e3\u7ec8\u7aef\u5bf9BliKVM\u8bbe\u5907\u8fdb\u884c\u8bbf\u95ee\u3002 1.\u786c\u4ef6\u8fde\u63a5\uff0c\u60a8\u5e94\u8be5\u4f7f\u7528USB\u8f6cttl\u6a21\u5757\u5c06\u8ba1\u7b97\u673a\u7684USB\u8fde\u63a5\u5230BliKVM\u7684uart\u3002\u5176\u4e2d\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fHat\u7248\u672c\uff0c\u8bf7\u6ce8\u610f\u8fde\u63a5GPIO14\u548cGPIO15\u8fd9\u4e2a\u4e32\u53e3\uff0c\u82e5\u662fPCIe\u7248\u672c\uff0c\u8fde\u63a5\u4e1d\u5370\u6807\u6ce8\u7684 GRT \u5f15\u811a\u5373\u53ef 2.\u7535\u8111\u4e0a\u5b89\u88c5\u53ef\u7ec8\u7aef\u767b\u9646\u7684\u5de5\u5177\uff0c\u5982\u5728windows\u4e0a\u53ef\u4ee5\u5b89\u88c5putty\u5de5\u5177 3. putty\u4f7f\u7528\u8bf4\u660e,\u8f93\u5165\u6b63\u786e\u7684COM\u53e3\uff0c\u9ed8\u8ba4\u6ce2\u7279\u7387115200\uff0c\u9009\u62e9\u8fde\u63a5\u65b9\u5f0f\u4e3aserial,\u7136\u540e\u70b9\u51fbopen\u5373\u53ef\uff08\u4ee5\u4f7f\u7528PiKVM\u56fa\u4ef6\u4e3a\u4f8b\uff09 \u5982\u679c\u4f60\u7684\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8bc6\u522busb\u8f6cttl\u6a21\u5757\uff0c\u8bf7\u6309\u7167\u4e0b\u5217\u6b65\u9aa4\u5bf9\u7535\u8111\u5b89\u88c5\u9a71\u52a8 \u5c06usb-a\u5934\u8fde\u63a5\u5230\u60a8\u7684\u4e3b\u673a\uff08\u5728\u672c\u4f8b\u4e2d\uff0c\u5b83\u4f4d\u4e8ewindows\u4e3b\u673a\u4e0a\uff09\u3002\u56e0\u6b64\uff0c\u8bbe\u5907\u7ba1\u7406\u5668\u5c06\u5728\u5176\u4ed6\u8bbe\u5907\u4e2d\u663e\u793a\u4e00\u4e2a\u65b0\u7684USB\u4e32\u884c\u8bbe\u5907\u3002 \u4e0b\u8f7d\u5e76\u63d0\u53d6/\u8fd0\u884c\u9a71\u52a8\u7a0b\u5e8f\u3002\u5728\u8fd9\u4e2a\u4f8b\u5b50\u4e2d\uff0c\u6211\u4e0b\u8f7d\u5e76\u63d0\u53d6\u4e86ZIP\u6587\u4ef6\u3002 https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all \u66f4\u65b0\u65b0USB\u4e32\u884c\u8bbe\u5907\u7684\u9a71\u52a8\u7a0b\u5e8f\uff0c\u5c06\u5176\u6307\u5411\u63d0\u53d6\u6587\u4ef6\u7684\u4f4d\u7f6e\uff0c\u7136\u540e\u5355\u51fb\u4e0b\u4e00\u6b65\uff0c\u7136\u540e\u5355\u51fb\u5173\u95ed\u3002 \u5982\u679c\u4e00\u5207\u6b63\u786e\uff0c\u65b0\u7684USB\u4e32\u884c\u8bbe\u5907\u73b0\u5728\u5e94\u8be5\u663e\u793a\u5728\u7aef\u53e3\u4e0b\u7684USB-serial CH340\uff08COMX\uff09\u3002","title":"\u4e32\u53e3\u7ec8\u7aef"},{"location":"serial_over_usb/#_1","text":"\u53ef\u4ee5\u901a\u8fc7\u4e32\u53e3\u7ec8\u7aef\u5bf9BliKVM\u8bbe\u5907\u8fdb\u884c\u8bbf\u95ee\u3002 1.\u786c\u4ef6\u8fde\u63a5\uff0c\u60a8\u5e94\u8be5\u4f7f\u7528USB\u8f6cttl\u6a21\u5757\u5c06\u8ba1\u7b97\u673a\u7684USB\u8fde\u63a5\u5230BliKVM\u7684uart\u3002\u5176\u4e2d\u5982\u679c\u4f60\u4f7f\u7528\u7684\u662fHat\u7248\u672c\uff0c\u8bf7\u6ce8\u610f\u8fde\u63a5GPIO14\u548cGPIO15\u8fd9\u4e2a\u4e32\u53e3\uff0c\u82e5\u662fPCIe\u7248\u672c\uff0c\u8fde\u63a5\u4e1d\u5370\u6807\u6ce8\u7684 GRT \u5f15\u811a\u5373\u53ef 2.\u7535\u8111\u4e0a\u5b89\u88c5\u53ef\u7ec8\u7aef\u767b\u9646\u7684\u5de5\u5177\uff0c\u5982\u5728windows\u4e0a\u53ef\u4ee5\u5b89\u88c5putty\u5de5\u5177 3. putty\u4f7f\u7528\u8bf4\u660e,\u8f93\u5165\u6b63\u786e\u7684COM\u53e3\uff0c\u9ed8\u8ba4\u6ce2\u7279\u7387115200\uff0c\u9009\u62e9\u8fde\u63a5\u65b9\u5f0f\u4e3aserial,\u7136\u540e\u70b9\u51fbopen\u5373\u53ef\uff08\u4ee5\u4f7f\u7528PiKVM\u56fa\u4ef6\u4e3a\u4f8b\uff09 \u5982\u679c\u4f60\u7684\u7535\u8111\u4e0d\u80fd\u6b63\u786e\u8bc6\u522busb\u8f6cttl\u6a21\u5757\uff0c\u8bf7\u6309\u7167\u4e0b\u5217\u6b65\u9aa4\u5bf9\u7535\u8111\u5b89\u88c5\u9a71\u52a8 \u5c06usb-a\u5934\u8fde\u63a5\u5230\u60a8\u7684\u4e3b\u673a\uff08\u5728\u672c\u4f8b\u4e2d\uff0c\u5b83\u4f4d\u4e8ewindows\u4e3b\u673a\u4e0a\uff09\u3002\u56e0\u6b64\uff0c\u8bbe\u5907\u7ba1\u7406\u5668\u5c06\u5728\u5176\u4ed6\u8bbe\u5907\u4e2d\u663e\u793a\u4e00\u4e2a\u65b0\u7684USB\u4e32\u884c\u8bbe\u5907\u3002 \u4e0b\u8f7d\u5e76\u63d0\u53d6/\u8fd0\u884c\u9a71\u52a8\u7a0b\u5e8f\u3002\u5728\u8fd9\u4e2a\u4f8b\u5b50\u4e2d\uff0c\u6211\u4e0b\u8f7d\u5e76\u63d0\u53d6\u4e86ZIP\u6587\u4ef6\u3002 https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all \u66f4\u65b0\u65b0USB\u4e32\u884c\u8bbe\u5907\u7684\u9a71\u52a8\u7a0b\u5e8f\uff0c\u5c06\u5176\u6307\u5411\u63d0\u53d6\u6587\u4ef6\u7684\u4f4d\u7f6e\uff0c\u7136\u540e\u5355\u51fb\u4e0b\u4e00\u6b65\uff0c\u7136\u540e\u5355\u51fb\u5173\u95ed\u3002 \u5982\u679c\u4e00\u5207\u6b63\u786e\uff0c\u65b0\u7684USB\u4e32\u884c\u8bbe\u5907\u73b0\u5728\u5e94\u8be5\u663e\u793a\u5728\u7aef\u53e3\u4e0b\u7684USB-serial CH340\uff08COMX\uff09\u3002","title":"\u4e32\u53e3\u7ec8\u7aef\u8fde\u63a5"},{"location":"ssh/","text":"SSH\u914d\u7f6e \u57281.4.7\u7248\u672c\u53ca\u4ee5\u540e\uff0cweb\u652f\u6301\u76f4\u63a5\u8fdb\u5165blikvm\u7684ssh\u7ec8\u7aef\uff0c\u9ed8\u8ba4\u8fdb\u5165\u7ec8\u7aef\u7684\u8d26\u53f7\u5bc6\u7801\u4e3a blikvm/blikvm\uff0c \u5982\u679c\u4fee\u6539\u4e86\u6b64\u7528\u6237\u7684\u5bc6\u7801\u4fe1\u606f\uff0c\u9700\u8981\u5728app.json\u6587\u4ef6\u4e2d\u4fee\u6539\u5bf9\u5e94\u7684\u8d26\u53f7\u5bc6\u7801 sudo -s vim /mnt/exec/release/config/app.json // \u627e\u5230\u4e0b\u9762\u914d\u7f6e\uff0c\u4fee\u6539\u6210\u4f60\u4fee\u6539\u540e\u7684\u3002 \"sshUser\": \"blikvm\", \"sshPassword\": \"blikvm\"","title":"SSH\u7ec8\u7aef"},{"location":"ssh/#ssh","text":"\u57281.4.7\u7248\u672c\u53ca\u4ee5\u540e\uff0cweb\u652f\u6301\u76f4\u63a5\u8fdb\u5165blikvm\u7684ssh\u7ec8\u7aef\uff0c\u9ed8\u8ba4\u8fdb\u5165\u7ec8\u7aef\u7684\u8d26\u53f7\u5bc6\u7801\u4e3a blikvm/blikvm\uff0c \u5982\u679c\u4fee\u6539\u4e86\u6b64\u7528\u6237\u7684\u5bc6\u7801\u4fe1\u606f\uff0c\u9700\u8981\u5728app.json\u6587\u4ef6\u4e2d\u4fee\u6539\u5bf9\u5e94\u7684\u8d26\u53f7\u5bc6\u7801 sudo -s vim /mnt/exec/release/config/app.json // \u627e\u5230\u4e0b\u9762\u914d\u7f6e\uff0c\u4fee\u6539\u6210\u4f60\u4fee\u6539\u540e\u7684\u3002 \"sshUser\": \"blikvm\", \"sshPassword\": \"blikvm\"","title":"SSH\u914d\u7f6e"},{"location":"static_ip/","text":"BliKVM OS\u8bbe\u7f6e\u9759\u6001IP v1 v2 v3\u53c2\u8003 \u4f7f\u7528SSH\u8fde\u63a5\u5230BliKVM\u7684\u7ec8\u7aef,\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\u3002 \u6253\u5f00\u7f51\u7edc\u914d\u7f6e\u6587\u4ef6 /etc/dhcpcd.conf \u4ee5\u8fdb\u884c\u7f16\u8f91\uff1a sudo vim /etc/dhcpcd.conf \u5728\u6587\u4ef6\u672b\u5c3e\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff0c\u66ff\u6362\u4e3a\u60a8\u60f3\u8981\u8bbe\u7f6e\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\uff1a interface eth0 static ip_address=192.168.0.100/24 static routers=192.168.0.1 static domain_name_servers=192.168.0.1 \u6ce8\u610f\uff1a\u6839\u636e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\uff0c\u53ef\u80fd\u9700\u8981\u4fee\u6539\u4e0a\u8ff0\u793a\u4f8b\u4e2d\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u503c\u3002 \u4fdd\u5b58\u6587\u4ef6\u5e76\u9000\u51fa\u7f16\u8f91\u5668\u3002 \u91cd\u65b0\u542f\u52a8BliKVM\u4ee5\u4f7f\u9759\u6001IP\u8bbe\u7f6e\u751f\u6548\uff1a sudo reboot v4\u53c2\u8003 \u4f7f\u7528SSH\u8fde\u63a5\u5230BliKVM\u7684\u7ec8\u7aef,\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\u3002 \u6253\u5f00\u7f51\u7edc\u914d\u7f6e\u6587\u4ef6 /etc/network/interfaces \u4ee5\u8fdb\u884c\u7f16\u8f91\uff1a sudo vim /etc/network/interfaces \u5728\u6587\u4ef6\u672b\u5c3e\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff0c\u66ff\u6362\u4e3a\u60a8\u60f3\u8981\u8bbe\u7f6e\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\uff1a source /etc/network/interfaces.d/* auto eth0 allow-hotplug eth0 iface eth0 inet static address 192.168.0.100 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 192.168.0.1 \u6ce8\u610f\uff1a\u6839\u636e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\uff0c\u53ef\u80fd\u9700\u8981\u4fee\u6539\u4e0a\u8ff0\u793a\u4f8b\u4e2d\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u503c\u3002 \u4fdd\u5b58\u6587\u4ef6\u5e76\u9000\u51fa\u7f16\u8f91\u5668, \u91cd\u65b0\u542f\u52a8NetworkManager\u4ee5\u4f7f\u9759\u6001IP\u8bbe\u7f6e\u751f\u6548\uff1a sudo systemctl restart NetworkManager \u6839\u636e\u60a8\u7684\u7f51\u7edc\u73af\u5883\u548c\u9700\u6c42\uff0c\u60a8\u53ef\u4ee5\u6839\u636e\u4e0a\u8ff0\u6b65\u9aa4\u81ea\u5b9a\u4e49\u914d\u7f6e\u9759\u6001IP\u5730\u5740\u3002\u8bf7\u786e\u4fddIP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u8bbe\u7f6e\u4e0e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\u76f8\u5339\u914d\u3002","title":"\u8bbe\u7f6e\u9759\u6001IP"},{"location":"static_ip/#blikvm-osip","text":"","title":"BliKVM OS\u8bbe\u7f6e\u9759\u6001IP"},{"location":"static_ip/#v1-v2-v3","text":"\u4f7f\u7528SSH\u8fde\u63a5\u5230BliKVM\u7684\u7ec8\u7aef,\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\u3002 \u6253\u5f00\u7f51\u7edc\u914d\u7f6e\u6587\u4ef6 /etc/dhcpcd.conf \u4ee5\u8fdb\u884c\u7f16\u8f91\uff1a sudo vim /etc/dhcpcd.conf \u5728\u6587\u4ef6\u672b\u5c3e\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff0c\u66ff\u6362\u4e3a\u60a8\u60f3\u8981\u8bbe\u7f6e\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\uff1a interface eth0 static ip_address=192.168.0.100/24 static routers=192.168.0.1 static domain_name_servers=192.168.0.1 \u6ce8\u610f\uff1a\u6839\u636e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\uff0c\u53ef\u80fd\u9700\u8981\u4fee\u6539\u4e0a\u8ff0\u793a\u4f8b\u4e2d\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u503c\u3002 \u4fdd\u5b58\u6587\u4ef6\u5e76\u9000\u51fa\u7f16\u8f91\u5668\u3002 \u91cd\u65b0\u542f\u52a8BliKVM\u4ee5\u4f7f\u9759\u6001IP\u8bbe\u7f6e\u751f\u6548\uff1a sudo reboot","title":"v1 v2 v3\u53c2\u8003"},{"location":"static_ip/#v4","text":"\u4f7f\u7528SSH\u8fde\u63a5\u5230BliKVM\u7684\u7ec8\u7aef,\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\u3002 \u6253\u5f00\u7f51\u7edc\u914d\u7f6e\u6587\u4ef6 /etc/network/interfaces \u4ee5\u8fdb\u884c\u7f16\u8f91\uff1a sudo vim /etc/network/interfaces \u5728\u6587\u4ef6\u672b\u5c3e\u6dfb\u52a0\u4ee5\u4e0b\u5185\u5bb9\uff0c\u66ff\u6362\u4e3a\u60a8\u60f3\u8981\u8bbe\u7f6e\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\uff1a source /etc/network/interfaces.d/* auto eth0 allow-hotplug eth0 iface eth0 inet static address 192.168.0.100 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 192.168.0.1 \u6ce8\u610f\uff1a\u6839\u636e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\uff0c\u53ef\u80fd\u9700\u8981\u4fee\u6539\u4e0a\u8ff0\u793a\u4f8b\u4e2d\u7684IP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u503c\u3002 \u4fdd\u5b58\u6587\u4ef6\u5e76\u9000\u51fa\u7f16\u8f91\u5668, \u91cd\u65b0\u542f\u52a8NetworkManager\u4ee5\u4f7f\u9759\u6001IP\u8bbe\u7f6e\u751f\u6548\uff1a sudo systemctl restart NetworkManager \u6839\u636e\u60a8\u7684\u7f51\u7edc\u73af\u5883\u548c\u9700\u6c42\uff0c\u60a8\u53ef\u4ee5\u6839\u636e\u4e0a\u8ff0\u6b65\u9aa4\u81ea\u5b9a\u4e49\u914d\u7f6e\u9759\u6001IP\u5730\u5740\u3002\u8bf7\u786e\u4fddIP\u5730\u5740\u3001\u7f51\u5173\u548cDNS\u670d\u52a1\u5668\u7684\u8bbe\u7f6e\u4e0e\u60a8\u7684\u7f51\u7edc\u8bbe\u7f6e\u76f8\u5339\u914d\u3002","title":"v4\u53c2\u8003"},{"location":"tailscale/","text":"Tailscale VPN Tailscale \u53ef\u4ee5\u7528\u4e8e\u5c06\u60a8\u7684\u4e3b\u673a\u548cBliKVM\u5728\u516c\u7f51\u4e0b\u8fdb\u884c\u8bbf\u95ee\u3002\u8fd9\u662f\u4e00\u4e2a\u65b9\u4fbf\u4e14\u514d\u8d39\u7684\u7ec4\u7f51\u5de5\u5177\uff0c\u7528\u4e8e\u7ec4\u7ec7\u5c0f\u578bVPN\u7f51\u7edc\u3002\u672c\u6587\u6863\u63d0\u4f9b\u4e86\u4e00\u4e2a\u793a\u4f8b\uff0c\u7528\u4e8e\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95ee\u60a8\u7684BliKVM\uff0c\u4f46\u60a8\u4e5f\u53ef\u4ee5\u4f7f\u7528Zerotier\u6216\u8005\u5176\u5b83VPN\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u57fa\u672c\u652f\u6301\u7684\u793a\u4f8b\uff0c\u9047\u5230\u4efb\u4f55\u95ee\u9898\u53ef\u4ee5\u53bbTailscale\u5b98\u7f51\u67e5\u627e\u3002 BliKVM\u5b89\u88c5Tailscale \u9996\u5148\u786e\u8ba4\u5f53\u524d\u7cfb\u7edf\u662f\u8bfb\u5199\u6743\u9650\uff0c\u82e5\u662f\u53ea\u8bfb\u7cfb\u7edf\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\uff0c\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u8fdb\u884c \u5b89\u88c5 : curl -fsSL https://tailscale.com/install.sh | sh \u6709\u4e00\u4e9b\u5730\u533a\u5982\u4e2d\u56fd\uff0c\u6709\u53ef\u80fd\u4f1a\u56e0\u4e3a\u7f51\u7edc\u539f\u56e0\u65e0\u6cd5\u987a\u5229\u4e0b\u8f7d\uff0c\u8bf7\u6b63\u786e\u914d\u7f6e\u7f51\u7edc \u4f7fBliKVM\u52a0\u5165\u5230\u4f60\u7684Tailscale\u5c40\u57df\u7f51\u4e2d \u5728\u5b98\u7f51\u6ce8\u518c\u4f60\u7684tailscale\u8d26\u6237\uff0c\u5e76\u5728\u8bbe\u7f6e\u4e2d\u751f\u6210\u4f60\u81ea\u5df1\u7684keys\uff0c\u5728BliKVM\u7ec8\u7aef\u4e0a\uff0c\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\uff0c\u5373\u53ef\u5c06BliKVM\u52a0\u5165\u5230tailscale\u751f\u6210\u7684\u5c40\u57df\u7f51\u4e2d\u3002 sudo tailscale up --authkey=your-auth-key --accept-routes \u82e5\u4e00\u5207\u987a\u5229\uff0c\u4f60\u5728BliKMV\u7ec8\u7aef\u8fd0\u884c ip addr show tailscale0 \uff0c\u5373\u53ef\u67e5\u770b\u5230tailscale0\u751f\u6210\u7684\u865a\u62df\u5c40\u57df\u7f51\u7684ip\u5730\u5740\uff0c\u4e00\u4e2a\u4f8b\u5b50\u5982\u4e0b\uff1a 3: tailscale0:  mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100.126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever \u5176\u4e2d100.126.223.28\u5c31\u662f\u53ef\u4ee5\u7528\u6765\u5728\u4e3b\u673a\u4e0a\u8bbf\u95eeBliKVM web\u754c\u9762\u7684UI\u5730\u5740\u3002 \u4e3b\u673a\u5b89\u88c5Tailscale \u5c06Tailscale \u4e0b\u8f7d \u5e76\u5b89\u88c5\u5230\u60a8\u7684\u63a7\u5236\u4e3b\u673a\u4e0a\uff0c\u767b\u5f55\u5bf9\u5e94\u7684\u8d26\u6237\uff0c\u7136\u540e\u60a8\u53ef\u4ee5\u5728Tailscale\u7684 \u63a7\u5236\u754c\u9762 \uff0c\u67e5\u770b\u60a8\u7684\u4e24\u53f0\u673a\u5668\u662f\u5426\u90fd\u5728\u7ebf\uff0c\u5982\u679c\u90fd\u5728\u7ebf\uff0c\u5373\u53ef\u4f7f\u7528\u4e0b\u9762\u5730\u5740\uff0c\u5728\u60a8\u7684\u63a7\u5236\u4e3b\u673a\u4e0a\u8bbf\u95eeBliKVM http://","title":"Tailscale VPN"},{"location":"tailscale/#tailscale-vpn","text":"Tailscale \u53ef\u4ee5\u7528\u4e8e\u5c06\u60a8\u7684\u4e3b\u673a\u548cBliKVM\u5728\u516c\u7f51\u4e0b\u8fdb\u884c\u8bbf\u95ee\u3002\u8fd9\u662f\u4e00\u4e2a\u65b9\u4fbf\u4e14\u514d\u8d39\u7684\u7ec4\u7f51\u5de5\u5177\uff0c\u7528\u4e8e\u7ec4\u7ec7\u5c0f\u578bVPN\u7f51\u7edc\u3002\u672c\u6587\u6863\u63d0\u4f9b\u4e86\u4e00\u4e2a\u793a\u4f8b\uff0c\u7528\u4e8e\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95ee\u60a8\u7684BliKVM\uff0c\u4f46\u60a8\u4e5f\u53ef\u4ee5\u4f7f\u7528Zerotier\u6216\u8005\u5176\u5b83VPN\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u57fa\u672c\u652f\u6301\u7684\u793a\u4f8b\uff0c\u9047\u5230\u4efb\u4f55\u95ee\u9898\u53ef\u4ee5\u53bbTailscale\u5b98\u7f51\u67e5\u627e\u3002","title":"Tailscale VPN"},{"location":"tailscale/#blikvmtailscale","text":"\u9996\u5148\u786e\u8ba4\u5f53\u524d\u7cfb\u7edf\u662f\u8bfb\u5199\u6743\u9650\uff0c\u82e5\u662f\u53ea\u8bfb\u7cfb\u7edf\u4f7f\u7528 rw \u547d\u4ee4\u4f7f\u7cfb\u7edf\u53ef\u5199\uff0c\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\u8fdb\u884c \u5b89\u88c5 : curl -fsSL https://tailscale.com/install.sh | sh \u6709\u4e00\u4e9b\u5730\u533a\u5982\u4e2d\u56fd\uff0c\u6709\u53ef\u80fd\u4f1a\u56e0\u4e3a\u7f51\u7edc\u539f\u56e0\u65e0\u6cd5\u987a\u5229\u4e0b\u8f7d\uff0c\u8bf7\u6b63\u786e\u914d\u7f6e\u7f51\u7edc","title":"BliKVM\u5b89\u88c5Tailscale"},{"location":"tailscale/#blikvmtailscale_1","text":"\u5728\u5b98\u7f51\u6ce8\u518c\u4f60\u7684tailscale\u8d26\u6237\uff0c\u5e76\u5728\u8bbe\u7f6e\u4e2d\u751f\u6210\u4f60\u81ea\u5df1\u7684keys\uff0c\u5728BliKVM\u7ec8\u7aef\u4e0a\uff0c\u4f7f\u7528\u4e0b\u9762\u547d\u4ee4\uff0c\u5373\u53ef\u5c06BliKVM\u52a0\u5165\u5230tailscale\u751f\u6210\u7684\u5c40\u57df\u7f51\u4e2d\u3002 sudo tailscale up --authkey=your-auth-key --accept-routes \u82e5\u4e00\u5207\u987a\u5229\uff0c\u4f60\u5728BliKMV\u7ec8\u7aef\u8fd0\u884c ip addr show tailscale0 \uff0c\u5373\u53ef\u67e5\u770b\u5230tailscale0\u751f\u6210\u7684\u865a\u62df\u5c40\u57df\u7f51\u7684ip\u5730\u5740\uff0c\u4e00\u4e2a\u4f8b\u5b50\u5982\u4e0b\uff1a 3: tailscale0:  mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500 link/none inet 100.126.223.28/32 scope global tailscale0 valid_lft forever preferred_lft forever inet6 fd7a:115c:a1e0:ab12:4843:cd96:627e:df1c/128 scope global valid_lft forever preferred_lft forever inet6 fe80::8955:99dc:4e7d:b08b/64 scope link stable-privacy valid_lft forever preferred_lft forever \u5176\u4e2d100.126.223.28\u5c31\u662f\u53ef\u4ee5\u7528\u6765\u5728\u4e3b\u673a\u4e0a\u8bbf\u95eeBliKVM web\u754c\u9762\u7684UI\u5730\u5740\u3002","title":"\u4f7fBliKVM\u52a0\u5165\u5230\u4f60\u7684Tailscale\u5c40\u57df\u7f51\u4e2d"},{"location":"tailscale/#tailscale","text":"\u5c06Tailscale \u4e0b\u8f7d \u5e76\u5b89\u88c5\u5230\u60a8\u7684\u63a7\u5236\u4e3b\u673a\u4e0a\uff0c\u767b\u5f55\u5bf9\u5e94\u7684\u8d26\u6237\uff0c\u7136\u540e\u60a8\u53ef\u4ee5\u5728Tailscale\u7684 \u63a7\u5236\u754c\u9762 \uff0c\u67e5\u770b\u60a8\u7684\u4e24\u53f0\u673a\u5668\u662f\u5426\u90fd\u5728\u7ebf\uff0c\u5982\u679c\u90fd\u5728\u7ebf\uff0c\u5373\u53ef\u4f7f\u7528\u4e0b\u9762\u5730\u5740\uff0c\u5728\u60a8\u7684\u63a7\u5236\u4e3b\u673a\u4e0a\u8bbf\u95eeBliKVM http://","title":"\u4e3b\u673a\u5b89\u88c5Tailscale"},{"location":"update/","text":"\u8f6f\u4ef6\u66f4\u65b0\u4ecb\u7ecd \u5982\u679c\u60a8\u8fd0\u884c\u7684\u662f\u975e\u5e38\u65e7\u7684\u7248\u672c\uff0c\u6211\u4eec\u5efa\u8bae\u60a8\u5148\u91cd\u65b0\u5237\u673a\uff0c\u7136\u540e\u5728\u9760\u8fd1\u60a8\u7684BliKVM\u8bbe\u5907\u65f6\u8fd0\u884c\u66f4\u65b0\u8fc7\u7a0b\u3002 \u4ecb\u7ecd BLIKVM\u9879\u76ee\u76ee\u524d\u53ef\u7528\u7248\u672c\u6258\u7ba1\u5728github\u4ed3\u5e93\u7684release\u5305\u91cc\uff0c\u66f4\u65b0\u8f6f\u4ef6\u529f\u80fd\u9700\u4fdd\u6301\u8bbe\u5907\u8054\u7f51\uff0c\u66f4\u65b0\u8f6f\u4ef6\u76ee\u524d\u63d0\u4f9b\u4e24\u79cd\u65b9\u5f0f \u65b9\u5f0f1\uff0c\u901a\u8fc7web\u754c\u9762\u70b9\u51fb\u66f4\u65b0\u6309\u94ae\uff0c\u7a0b\u5e8f\u81ea\u52a8\u8fdb\u884c\u66f4\u65b0,\u66f4\u65b0\u5b8c\u9700\u8981\u91cd\u542f\u3002 \u65b9\u5f0f2\uff0c\u624b\u52a8\u5728KVM\u7ec8\u7aef\u4e0a\u8fd0\u884c\u811a\u672c\u8fdb\u884c\u66f4\u65b0\uff0c\u66f4\u65b0\u5b8c\u540e\u9700\u8981\u91cd\u542f\u3002 \u5347\u7ea7\u9519\u8bef\u5e38\u89c1\u539f\u56e0 \u8bbe\u5907\u672a\u8054\u7f51; \u7f51\u7edc\u8bbf\u95eegithub\u53d7\u9650; \u6211\u4eec\u5f3a\u70c8\u5efa\u8bae\u60a8\u5728\u9760\u8fd1\u8981\u5347\u7ea7\u7684BliKVM\u786c\u4ef6\u65f6\u6267\u884c\u66f4\u65b0\u3002\u539f\u56e0\u662f\uff0c\u5982\u679c\u51fa\u73b0\u4efb\u4f55\u95ee\u9898\uff0c\u4f60\u53ef\u4ee5\u8fdb\u884c\u5e72\u9884\u3002 \u5982\u679c\u60a8\u719f\u6089\u547d\u4ee4\u884c\u64cd\u4f5c\uff0c\u5efa\u8bae\u60a8\u624b\u52a8\u66f4\u65b0\u53ef\u4ee5\u5b9e\u65f6\u67e5\u770b\u547d\u4ee4\u884c\u72b6\u6001\u3002 \u82e5\u66f4\u65b0\u5f02\u5e38\uff0cweb\u754c\u9762\u65e0\u6cd5\u9000\u51fa\u66f4\u65b0\u72b6\u6001\uff0c\u53ef\u4ee5\u7ec8\u7aefssh\u8fdb\u5165kvm\u540e\u91cd\u542f\u6062\u590d\u3002 \u624b\u52a8\u8fd0\u884c\u811a\u672c\u66f4\u65b0 ssh\u8fdb\u5165\u8bbe\u5907\u7ec8\u7aef\u3002\u82e5\u5f53\u524d\u7cfb\u7edf\u7ec8\u7aef\u53ef\u4ee5\u770b\u5230ro\u5173\u952e\u5b57\uff0c\u4e3a\u53ea\u8bfb\u7cfb\u7edf\uff0c\u9700\u4f7f\u7528 rw \u8ba9\u7cfb\u7edf\u4e3a\u53ef\u5199\u6743\u9650\u3002 sudo -i curl -L https://raw.githubusercontent.com/ThomasVon2021/blikvm/master/script/update.py -o /tmp/update.py && python3 /tmp/update.py \u89c2\u5bdf\u7ec8\u7aef\u8f93\u51fa\uff0c\u5f53\u770b\u5230\u5347\u7ea7\u5347\u7ea7\u6210\u529f\u6d88\u606f\u63d0\u9192\u65f6\uff0c\u7ec8\u7aef\u8f93\u5165reboot\uff0c\u91cd\u542f\u751f\u6548\u3002 \u82e5\u60a8\u56e0\u7f51\u7edc\u539f\u56e0\uff0c\u4e00\u76f4\u65e0\u6cd5\u66f4\u65b0\u6210\u529f\uff0c\u53ef\u4ee5\u91c7\u7528\u5728\u5176\u5b83\u7f51\u7edcok\u7684PC\u4e0a\u4e0b\u8f7d\u6700\u65b0\u7684release\u5305\uff0c\u7136\u540e\u6309\u7167\u4ee5\u4e0b\u547d\u4ee4\u8fdb\u884c\u5b89\u88c5\u3002 \u4e0b\u8f7d\u5730\u5740: https://github.com/ThomasVon2021/blikvm/releases \u5176\u4e2dv1 v2 v3\u786c\u4ef6\u4f7f\u7528 release.tar.gz v4\u786c\u4ef6\u4f7f\u7528 release-h616-v4.tar.gz ssh\u8fdb\u5165\u8bbe\u5907\u7ec8\u7aef\uff0c\u5e76\u4f7f\u7528 tar -zxvf release.tar.gz \u89e3\u538brelease.tar.gz\u3002 sudo -i cd /your release path/ python3 install_release.py --releasepath=./ \u53ef\u4ee5\u89c2\u5bdf/usr/bin/blikvm/package.json\u524d\u540e\u7684\u7248\u672c\u5bf9\u6bd4\uff0c\u82e5\u5347\u7ea7\u5230\u4e86\u6307\u5b9a\u7248\u672c\uff0c\u5219\u6210\u529f\uff0c\u91cd\u542f\u751f\u6548\u3002","title":"\u66f4\u65b0\u8f6f\u4ef6"},{"location":"update/#_1","text":"\u5982\u679c\u60a8\u8fd0\u884c\u7684\u662f\u975e\u5e38\u65e7\u7684\u7248\u672c\uff0c\u6211\u4eec\u5efa\u8bae\u60a8\u5148\u91cd\u65b0\u5237\u673a\uff0c\u7136\u540e\u5728\u9760\u8fd1\u60a8\u7684BliKVM\u8bbe\u5907\u65f6\u8fd0\u884c\u66f4\u65b0\u8fc7\u7a0b\u3002","title":"\u8f6f\u4ef6\u66f4\u65b0\u4ecb\u7ecd"},{"location":"update/#_2","text":"BLIKVM\u9879\u76ee\u76ee\u524d\u53ef\u7528\u7248\u672c\u6258\u7ba1\u5728github\u4ed3\u5e93\u7684release\u5305\u91cc\uff0c\u66f4\u65b0\u8f6f\u4ef6\u529f\u80fd\u9700\u4fdd\u6301\u8bbe\u5907\u8054\u7f51\uff0c\u66f4\u65b0\u8f6f\u4ef6\u76ee\u524d\u63d0\u4f9b\u4e24\u79cd\u65b9\u5f0f \u65b9\u5f0f1\uff0c\u901a\u8fc7web\u754c\u9762\u70b9\u51fb\u66f4\u65b0\u6309\u94ae\uff0c\u7a0b\u5e8f\u81ea\u52a8\u8fdb\u884c\u66f4\u65b0,\u66f4\u65b0\u5b8c\u9700\u8981\u91cd\u542f\u3002 \u65b9\u5f0f2\uff0c\u624b\u52a8\u5728KVM\u7ec8\u7aef\u4e0a\u8fd0\u884c\u811a\u672c\u8fdb\u884c\u66f4\u65b0\uff0c\u66f4\u65b0\u5b8c\u540e\u9700\u8981\u91cd\u542f\u3002 \u5347\u7ea7\u9519\u8bef\u5e38\u89c1\u539f\u56e0 \u8bbe\u5907\u672a\u8054\u7f51; \u7f51\u7edc\u8bbf\u95eegithub\u53d7\u9650; \u6211\u4eec\u5f3a\u70c8\u5efa\u8bae\u60a8\u5728\u9760\u8fd1\u8981\u5347\u7ea7\u7684BliKVM\u786c\u4ef6\u65f6\u6267\u884c\u66f4\u65b0\u3002\u539f\u56e0\u662f\uff0c\u5982\u679c\u51fa\u73b0\u4efb\u4f55\u95ee\u9898\uff0c\u4f60\u53ef\u4ee5\u8fdb\u884c\u5e72\u9884\u3002 \u5982\u679c\u60a8\u719f\u6089\u547d\u4ee4\u884c\u64cd\u4f5c\uff0c\u5efa\u8bae\u60a8\u624b\u52a8\u66f4\u65b0\u53ef\u4ee5\u5b9e\u65f6\u67e5\u770b\u547d\u4ee4\u884c\u72b6\u6001\u3002 \u82e5\u66f4\u65b0\u5f02\u5e38\uff0cweb\u754c\u9762\u65e0\u6cd5\u9000\u51fa\u66f4\u65b0\u72b6\u6001\uff0c\u53ef\u4ee5\u7ec8\u7aefssh\u8fdb\u5165kvm\u540e\u91cd\u542f\u6062\u590d\u3002","title":"\u4ecb\u7ecd"},{"location":"update/#_3","text":"ssh\u8fdb\u5165\u8bbe\u5907\u7ec8\u7aef\u3002\u82e5\u5f53\u524d\u7cfb\u7edf\u7ec8\u7aef\u53ef\u4ee5\u770b\u5230ro\u5173\u952e\u5b57\uff0c\u4e3a\u53ea\u8bfb\u7cfb\u7edf\uff0c\u9700\u4f7f\u7528 rw \u8ba9\u7cfb\u7edf\u4e3a\u53ef\u5199\u6743\u9650\u3002 sudo -i curl -L https://raw.githubusercontent.com/ThomasVon2021/blikvm/master/script/update.py -o /tmp/update.py && python3 /tmp/update.py \u89c2\u5bdf\u7ec8\u7aef\u8f93\u51fa\uff0c\u5f53\u770b\u5230\u5347\u7ea7\u5347\u7ea7\u6210\u529f\u6d88\u606f\u63d0\u9192\u65f6\uff0c\u7ec8\u7aef\u8f93\u5165reboot\uff0c\u91cd\u542f\u751f\u6548\u3002 \u82e5\u60a8\u56e0\u7f51\u7edc\u539f\u56e0\uff0c\u4e00\u76f4\u65e0\u6cd5\u66f4\u65b0\u6210\u529f\uff0c\u53ef\u4ee5\u91c7\u7528\u5728\u5176\u5b83\u7f51\u7edcok\u7684PC\u4e0a\u4e0b\u8f7d\u6700\u65b0\u7684release\u5305\uff0c\u7136\u540e\u6309\u7167\u4ee5\u4e0b\u547d\u4ee4\u8fdb\u884c\u5b89\u88c5\u3002 \u4e0b\u8f7d\u5730\u5740: https://github.com/ThomasVon2021/blikvm/releases \u5176\u4e2dv1 v2 v3\u786c\u4ef6\u4f7f\u7528 release.tar.gz v4\u786c\u4ef6\u4f7f\u7528 release-h616-v4.tar.gz ssh\u8fdb\u5165\u8bbe\u5907\u7ec8\u7aef\uff0c\u5e76\u4f7f\u7528 tar -zxvf release.tar.gz \u89e3\u538brelease.tar.gz\u3002 sudo -i cd /your release path/ python3 install_release.py --releasepath=./ \u53ef\u4ee5\u89c2\u5bdf/usr/bin/blikvm/package.json\u524d\u540e\u7684\u7248\u672c\u5bf9\u6bd4\uff0c\u82e5\u5347\u7ea7\u5230\u4e86\u6307\u5b9a\u7248\u672c\uff0c\u5219\u6210\u529f\uff0c\u91cd\u542f\u751f\u6548\u3002","title":"\u624b\u52a8\u8fd0\u884c\u811a\u672c\u66f4\u65b0"},{"location":"usb-splitter-guide/","text":"USB\u548c\u7535\u6e90\u5206\u7ebf\u677f 1. \u7b80\u4ecb The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage. 2.\u5c3a\u5bf8\u56fe 3.\u6d4b\u8bd5\u89c6\u9891 USB splitter Video 4.3D \u6253\u5370\u5916\u58f3 A simple snap fit case for the USB splitter. \u4e0b\u8f7d\u6587\u4ef6","title":"USB\u4e00\u5206\u4e8c\u7528\u6237\u624b\u518c"},{"location":"usb-splitter-guide/#usb","text":"","title":"USB\u548c\u7535\u6e90\u5206\u7ebf\u677f"},{"location":"usb-splitter-guide/#1","text":"The adaptor allows the Raspberry Pi 4 to be used with a Pi USB-C power supply while allowing access to USB OTG data over a separate USB-C connection. USB-C (RPI4) <> USB-C (USB) and USB-C (PWR) USB-C(RPI4) USB Type-C(USB) USB Type-C(PWR) 5V 5V D- D- D+ D+ CC1 10k to 5V CC1 5.1k to GND CC1 5.1k to GND CC2 10k to 5V CC2 5.1k to GND CC2 5.1k to GND GND GND GND To use the adaptor with the Raspberry Pi 4 you need. USB-C to USB-C cable[1] between Pi4 and the adaptor board USB-C to USB-C or Type-A between adaptor board and PC Power[2] via Official Raspberry Pi USB Type-C Power Supply. [1] Whilst USB-C cables are generally designed for higher current I still advise using short power cable to the Pi where possible to reduce voltage drop. [2] PLEASE NOTE With the Pu/Pd resistors on this board it can only be used with 5V supply to power a 5V device. An adaptor of this kind does not fall within the USB specification. It's designed for use with the official Raspberry Pi USB-C power supply and raspberry pi, use with other power supplies/chargers and devices may cause issues/damage.","title":"1. \u7b80\u4ecb"},{"location":"usb-splitter-guide/#2","text":"","title":"2.\u5c3a\u5bf8\u56fe"},{"location":"usb-splitter-guide/#3","text":"USB splitter Video","title":"3.\u6d4b\u8bd5\u89c6\u9891"},{"location":"usb-splitter-guide/#43d","text":"A simple snap fit case for the USB splitter. \u4e0b\u8f7d\u6587\u4ef6","title":"4.3D \u6253\u5370\u5916\u58f3"},{"location":"wake-on-lan/","text":"Wake-on-LAN \u4ecb\u7ecd Wake-on-LAN\u7b80\u79f0WOL\u6216WoL\uff0c\u529f\u80fd\u4e3a\u8ba9\u5df2\u7ecf\u8fdb\u5165\u4f11\u7720\u72b6\u6001\u6216\u5173\u673a\u72b6\u6001\u7684\u8ba1\u7b97\u673a\uff0cKVM\u901a\u8fc7\u5c40\u57df\u7f51\u53d1\u9001\u7279\u5b9a\u6d88\u606f\uff0c\u4f7f\u88ab\u63a7\u7535\u8111\u4ece\u4f11\u7720\u72b6\u6001\u6216\u5173\u673a\u72b6\u6001\u6539\u4e3a\u5f00\u673a\u72b6\u6001\u3002WoL\u9700\u88ab\u63a7\u7535\u8111\u652f\u6301\uff0c\u5426\u5219\u8be5\u529f\u80fd\u65e0\u6548\uff0c\u53e6\u5916\u9700\u786e\u8ba4WoL\u5df2\u88ab\u5f00\u542f\u548c\u6b63\u786e\u914d\u7f6e\u3002\u4f7f\u7528\u6b64\u529f\u80fd\uff0c\u4e0d\u9700\u8981\u4f7f\u7528atx\u529f\u80fd\u4e5f\u53ef\u4ee5\u5b9e\u73b0\u5f00\u673a\u3002\u82e5\u7528\u6237\u5728\u4f7f\u7528kvm\u7684WoL\u7684\u9047\u5230\u5f02\u5e38\uff0c\u53ef\u5c1d\u8bd5\u4f7f\u7528\u652f\u6301WoL\u7684\u8f6f\u4ef6\u8fdb\u884c\u6d4b\u8bd5\u3002 \u4f7f\u7528\u65b9\u6cd5","title":"Wake-on-LAN"},{"location":"wake-on-lan/#wake-on-lan","text":"","title":"Wake-on-LAN"},{"location":"wake-on-lan/#_1","text":"Wake-on-LAN\u7b80\u79f0WOL\u6216WoL\uff0c\u529f\u80fd\u4e3a\u8ba9\u5df2\u7ecf\u8fdb\u5165\u4f11\u7720\u72b6\u6001\u6216\u5173\u673a\u72b6\u6001\u7684\u8ba1\u7b97\u673a\uff0cKVM\u901a\u8fc7\u5c40\u57df\u7f51\u53d1\u9001\u7279\u5b9a\u6d88\u606f\uff0c\u4f7f\u88ab\u63a7\u7535\u8111\u4ece\u4f11\u7720\u72b6\u6001\u6216\u5173\u673a\u72b6\u6001\u6539\u4e3a\u5f00\u673a\u72b6\u6001\u3002WoL\u9700\u88ab\u63a7\u7535\u8111\u652f\u6301\uff0c\u5426\u5219\u8be5\u529f\u80fd\u65e0\u6548\uff0c\u53e6\u5916\u9700\u786e\u8ba4WoL\u5df2\u88ab\u5f00\u542f\u548c\u6b63\u786e\u914d\u7f6e\u3002\u4f7f\u7528\u6b64\u529f\u80fd\uff0c\u4e0d\u9700\u8981\u4f7f\u7528atx\u529f\u80fd\u4e5f\u53ef\u4ee5\u5b9e\u73b0\u5f00\u673a\u3002\u82e5\u7528\u6237\u5728\u4f7f\u7528kvm\u7684WoL\u7684\u9047\u5230\u5f02\u5e38\uff0c\u53ef\u5c1d\u8bd5\u4f7f\u7528\u652f\u6301WoL\u7684\u8f6f\u4ef6\u8fdb\u884c\u6d4b\u8bd5\u3002","title":"\u4ecb\u7ecd"},{"location":"wake-on-lan/#_2","text":"","title":"\u4f7f\u7528\u65b9\u6cd5"},{"location":"wifi/","text":"Wifi\u529f\u80fd \u7531\u4e8eBLIKVM\u6709\u591a\u6b3e\u786c\u4ef6\uff0c\u652f\u6301\u4e0d\u540c\u7684OS\uff0c\u5982BLIKVM OS\u548cPiKVM OS\uff0c\u4e0d\u540cOS\u94fe\u63a5wifi\u65b9\u5f0f\u4e0d\u4e00\u5b9a\u76f8\u540c\uff0c\u8bf7\u5728\u4f7f\u7528\u672c\u6587\u6863\u65b9\u6cd5\u524d\uff0c\u8bf7\u786e\u8ba4\u81ea\u5df1\u786c\u4ef6\u548c\u4f7f\u7528OS\u7684\u60c5\u51b5\u3002 \u8bf7\u786e\u8ba4\u4f60\u4f7f\u7528\u7684\u786c\u4ef6\u652f\u6301wifi\u529f\u80fd\uff0c\u5982CM400200\u7248\u672c\u4e0d\u5e26wifi\u529f\u80fd\uff1b \u82e5KVM\u786c\u4ef6\u7684SOC\u4e3aCM4\uff0c\u8bf7\u786e\u8ba4\u662f\u5426\u8fde\u63a5\u4e86wifi\u5929\u7ebf\uff1b PiKVM OS\u4e3aarch linux\uff1b BLIKVM OS\u6811\u8393\u6d3e\u7cfb\u5217\u4e3adebian\u7cfb\u7edf\uff0cv4\u7cfb\u5217\u4e3aarmbian\u7cfb\u7edf\uff1b v1\uff0cv2\uff0cv3\u786c\u4ef6\u4f7f\u7528\u7684\u4e3a\u6811\u8393\u6d3edebian\u7cfb\u7edf\uff0c\u4f7f\u7528raspi-config\u8fdb\u884cwifi\u94fe\u63a5 \u767b\u5f55ssh,\u547d\u4ee4: ssh blikvm@ip \u7cfb\u7edf\u91cd\u52a0\u8f7d\u4e3a\u53ef\u5199, \u547d\u4ee4: rw \u542f\u52a8raspi-config, \u547d\u4ee4: sudo raspi-config \u9009\u62e9 System Options \u9009\u62e9 Wireless LAN \u9009\u62e9wifi\u6240\u5728\u56fd\u5bb6,\u4e2d\u56fd\u9009CN, \u5982\u679c\u4ee5\u524d\u8bbe\u7f6e\u8fc7,\u8fd9\u4e00\u6b65\u4f1a\u8df3\u8fc7\u76f4\u63a5\u52307 \u8f93\u5165Wi-Fi\u7684ssid(\u540d\u79f0) \u8f93\u5165Wi-Fi\u7684\u5bc6\u7801,\u5982\u679c\u6ca1\u6709\u5bc6\u7801\u76f4\u63a5\u56de\u8f66 \u8fd9\u65f6\u4f1a\u56de\u5230\u6b65\u9aa44\u7684\u754c\u9762,\u6309tab\u952e\u9009\u62e9 ,\u56de\u8f66 \u67e5\u770b\u662f\u5426\u8fde\u4e0awifi, \u547d\u4ee4: ifconfig wlan0 ,\u5982\u679c\u770b\u5230\u83b7\u53d6\u5230ip\u5c31\u662f\u5df2\u7ecf\u8fde\u4e0a\u4e86 \u5c06\u7cfb\u7edf\u6302\u8f7d\u4e3a\u53ea\u8bfb, \u547d\u4ee4: ro v4\u786c\u4ef6\u4f7f\u7528\u7684\u4e3aarmbian\u7cfb\u7edf\uff0c\u4f7f\u7528armbian-config \u767b\u5f55ssh,\u547d\u4ee4: ssh blikvm@ip\uff0c\u767b\u5f55\u5230 Armbian \u7cfb\u7edf\u3002 \u8f93\u5165\u4ee5\u4e0b\u547d\u4ee4\u4ee5\u542f\u52a8 armbian-config \u5de5\u5177\uff1a sudo armbian-config \u5728 armbian-config \u83dc\u5355\u4e2d\uff0c\u4f7f\u7528\u65b9\u5411\u952e\u548c\u56de\u8f66\u952e\u5bfc\u822a\u548c\u9009\u62e9\u9009\u9879\u3002 \u4f7f\u7528\u65b9\u5411\u952e\u5411\u4e0b\u6eda\u52a8\u5230 \"Network\" \u9009\u9879\uff0c\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165\u5b50\u83dc\u5355\u3002 \u5728 \"Network\" \u5b50\u83dc\u5355\u4e2d\uff0c\u9009\u62e9 \"Wireless\" \u9009\u9879\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165 Wi-Fi \u914d\u7f6e\u83dc\u5355\u3002 \u5728 Wi-Fi \u914d\u7f6e\u83dc\u5355\u4e2d\uff0c\u9009\u62e9 \"Connect to Wi-Fi\" \u9009\u9879\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165 Wi-Fi \u8fde\u63a5\u8bbe\u7f6e\u3002 armbian-config \u5c06\u5217\u51fa\u53ef\u7528\u7684\u65e0\u7ebf\u7f51\u7edc\u63a5\u53e3\u548c\u5df2\u914d\u7f6e\u7684\u7f51\u7edc\u3002\u9009\u62e9\u8981\u8fde\u63a5\u7684\u65e0\u7ebf\u7f51\u7edc\u63a5\u53e3\u5e76\u6309\u56de\u8f66\u952e\u3002 armbian-config \u5c06\u663e\u793a\u53ef\u7528\u7684 Wi-Fi \u7f51\u7edc\u5217\u8868\u3002\u4f7f\u7528\u65b9\u5411\u952e\u9009\u62e9\u8981\u8fde\u63a5\u7684 Wi-Fi \u7f51\u7edc\u5e76\u6309\u56de\u8f66\u952e\u3002 \u5982\u679c Wi-Fi \u7f51\u7edc\u53d7\u5230\u5bc6\u7801\u4fdd\u62a4\uff0c armbian-config \u5c06\u63d0\u793a\u60a8\u8f93\u5165 Wi-Fi \u5bc6\u7801\u3002\u8f93\u5165\u5bc6\u7801\u5e76\u6309\u56de\u8f66\u952e\u3002 \u7b49\u5f85\u7247\u523b\uff0cArmbian \u7cfb\u7edf\u5c06\u5c1d\u8bd5\u8fde\u63a5\u5230\u6307\u5b9a\u7684 Wi-Fi \u7f51\u7edc\u3002\u5982\u679c\u8fde\u63a5\u6210\u529f\uff0c\u60a8\u5c06\u5728\u5c4f\u5e55\u4e0a\u770b\u5230\u76f8\u5e94\u7684\u6d88\u606f\u3002 \u9000\u51fa armbian-config \u5de5\u5177\u3002 \u8bf7\u6ce8\u610f\uff0c\u4e0a\u8ff0\u6b65\u9aa4\u4e2d\u7684\u83dc\u5355\u9009\u9879\u548c\u914d\u7f6e\u53ef\u80fd\u4f1a\u6839\u636e\u4e0d\u540c\u7248\u672c\u7684 Armbian \u7cfb\u7edf\u7565\u6709\u4e0d\u540c\u3002\u786e\u4fdd\u6839\u636e\u60a8\u7684\u7cfb\u7edf\u7248\u672c\u548c\u914d\u7f6e\u8fdb\u884c\u76f8\u5e94\u7684\u64cd\u4f5c\u3002","title":"Wifi\u914d\u7f6e"},{"location":"wifi/#wifi","text":"\u7531\u4e8eBLIKVM\u6709\u591a\u6b3e\u786c\u4ef6\uff0c\u652f\u6301\u4e0d\u540c\u7684OS\uff0c\u5982BLIKVM OS\u548cPiKVM OS\uff0c\u4e0d\u540cOS\u94fe\u63a5wifi\u65b9\u5f0f\u4e0d\u4e00\u5b9a\u76f8\u540c\uff0c\u8bf7\u5728\u4f7f\u7528\u672c\u6587\u6863\u65b9\u6cd5\u524d\uff0c\u8bf7\u786e\u8ba4\u81ea\u5df1\u786c\u4ef6\u548c\u4f7f\u7528OS\u7684\u60c5\u51b5\u3002 \u8bf7\u786e\u8ba4\u4f60\u4f7f\u7528\u7684\u786c\u4ef6\u652f\u6301wifi\u529f\u80fd\uff0c\u5982CM400200\u7248\u672c\u4e0d\u5e26wifi\u529f\u80fd\uff1b \u82e5KVM\u786c\u4ef6\u7684SOC\u4e3aCM4\uff0c\u8bf7\u786e\u8ba4\u662f\u5426\u8fde\u63a5\u4e86wifi\u5929\u7ebf\uff1b PiKVM OS\u4e3aarch linux\uff1b BLIKVM OS\u6811\u8393\u6d3e\u7cfb\u5217\u4e3adebian\u7cfb\u7edf\uff0cv4\u7cfb\u5217\u4e3aarmbian\u7cfb\u7edf\uff1b","title":"Wifi\u529f\u80fd"},{"location":"wifi/#v1v2v3debianraspi-configwifi","text":"\u767b\u5f55ssh,\u547d\u4ee4: ssh blikvm@ip \u7cfb\u7edf\u91cd\u52a0\u8f7d\u4e3a\u53ef\u5199, \u547d\u4ee4: rw \u542f\u52a8raspi-config, \u547d\u4ee4: sudo raspi-config \u9009\u62e9 System Options \u9009\u62e9 Wireless LAN \u9009\u62e9wifi\u6240\u5728\u56fd\u5bb6,\u4e2d\u56fd\u9009CN, \u5982\u679c\u4ee5\u524d\u8bbe\u7f6e\u8fc7,\u8fd9\u4e00\u6b65\u4f1a\u8df3\u8fc7\u76f4\u63a5\u52307 \u8f93\u5165Wi-Fi\u7684ssid(\u540d\u79f0) \u8f93\u5165Wi-Fi\u7684\u5bc6\u7801,\u5982\u679c\u6ca1\u6709\u5bc6\u7801\u76f4\u63a5\u56de\u8f66 \u8fd9\u65f6\u4f1a\u56de\u5230\u6b65\u9aa44\u7684\u754c\u9762,\u6309tab\u952e\u9009\u62e9 ,\u56de\u8f66 \u67e5\u770b\u662f\u5426\u8fde\u4e0awifi, \u547d\u4ee4: ifconfig wlan0 ,\u5982\u679c\u770b\u5230\u83b7\u53d6\u5230ip\u5c31\u662f\u5df2\u7ecf\u8fde\u4e0a\u4e86 \u5c06\u7cfb\u7edf\u6302\u8f7d\u4e3a\u53ea\u8bfb, \u547d\u4ee4: ro","title":"v1\uff0cv2\uff0cv3\u786c\u4ef6\u4f7f\u7528\u7684\u4e3a\u6811\u8393\u6d3edebian\u7cfb\u7edf\uff0c\u4f7f\u7528raspi-config\u8fdb\u884cwifi\u94fe\u63a5"},{"location":"wifi/#v4armbianarmbian-config","text":"\u767b\u5f55ssh,\u547d\u4ee4: ssh blikvm@ip\uff0c\u767b\u5f55\u5230 Armbian \u7cfb\u7edf\u3002 \u8f93\u5165\u4ee5\u4e0b\u547d\u4ee4\u4ee5\u542f\u52a8 armbian-config \u5de5\u5177\uff1a sudo armbian-config \u5728 armbian-config \u83dc\u5355\u4e2d\uff0c\u4f7f\u7528\u65b9\u5411\u952e\u548c\u56de\u8f66\u952e\u5bfc\u822a\u548c\u9009\u62e9\u9009\u9879\u3002 \u4f7f\u7528\u65b9\u5411\u952e\u5411\u4e0b\u6eda\u52a8\u5230 \"Network\" \u9009\u9879\uff0c\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165\u5b50\u83dc\u5355\u3002 \u5728 \"Network\" \u5b50\u83dc\u5355\u4e2d\uff0c\u9009\u62e9 \"Wireless\" \u9009\u9879\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165 Wi-Fi \u914d\u7f6e\u83dc\u5355\u3002 \u5728 Wi-Fi \u914d\u7f6e\u83dc\u5355\u4e2d\uff0c\u9009\u62e9 \"Connect to Wi-Fi\" \u9009\u9879\u5e76\u6309\u56de\u8f66\u952e\u8fdb\u5165 Wi-Fi \u8fde\u63a5\u8bbe\u7f6e\u3002 armbian-config \u5c06\u5217\u51fa\u53ef\u7528\u7684\u65e0\u7ebf\u7f51\u7edc\u63a5\u53e3\u548c\u5df2\u914d\u7f6e\u7684\u7f51\u7edc\u3002\u9009\u62e9\u8981\u8fde\u63a5\u7684\u65e0\u7ebf\u7f51\u7edc\u63a5\u53e3\u5e76\u6309\u56de\u8f66\u952e\u3002 armbian-config \u5c06\u663e\u793a\u53ef\u7528\u7684 Wi-Fi \u7f51\u7edc\u5217\u8868\u3002\u4f7f\u7528\u65b9\u5411\u952e\u9009\u62e9\u8981\u8fde\u63a5\u7684 Wi-Fi \u7f51\u7edc\u5e76\u6309\u56de\u8f66\u952e\u3002 \u5982\u679c Wi-Fi \u7f51\u7edc\u53d7\u5230\u5bc6\u7801\u4fdd\u62a4\uff0c armbian-config \u5c06\u63d0\u793a\u60a8\u8f93\u5165 Wi-Fi \u5bc6\u7801\u3002\u8f93\u5165\u5bc6\u7801\u5e76\u6309\u56de\u8f66\u952e\u3002 \u7b49\u5f85\u7247\u523b\uff0cArmbian \u7cfb\u7edf\u5c06\u5c1d\u8bd5\u8fde\u63a5\u5230\u6307\u5b9a\u7684 Wi-Fi \u7f51\u7edc\u3002\u5982\u679c\u8fde\u63a5\u6210\u529f\uff0c\u60a8\u5c06\u5728\u5c4f\u5e55\u4e0a\u770b\u5230\u76f8\u5e94\u7684\u6d88\u606f\u3002 \u9000\u51fa armbian-config \u5de5\u5177\u3002 \u8bf7\u6ce8\u610f\uff0c\u4e0a\u8ff0\u6b65\u9aa4\u4e2d\u7684\u83dc\u5355\u9009\u9879\u548c\u914d\u7f6e\u53ef\u80fd\u4f1a\u6839\u636e\u4e0d\u540c\u7248\u672c\u7684 Armbian \u7cfb\u7edf\u7565\u6709\u4e0d\u540c\u3002\u786e\u4fdd\u6839\u636e\u60a8\u7684\u7cfb\u7edf\u7248\u672c\u548c\u914d\u7f6e\u8fdb\u884c\u76f8\u5e94\u7684\u64cd\u4f5c\u3002","title":"v4\u786c\u4ef6\u4f7f\u7528\u7684\u4e3aarmbian\u7cfb\u7edf\uff0c\u4f7f\u7528armbian-config"},{"location":"zerotier/","text":"ZeroTier VPN ZeroTier \u5141\u8bb8\u901a\u8fc7 NAT \u5728\u53cc\u65b9\u4e4b\u95f4\u5b89\u5168\u8bbf\u95ee\u60a8\u7684 BliKVM\u3002\u5b83\u5141\u8bb8\u60a8\u6784\u5efa\u51e0\u4e4e\u4efb\u4f55\u7c7b\u578b\u7684\u73b0\u4ee3\u3001\u5b89\u5168\u7684\u591a\u70b9\u865a\u62df\u5316\u7f51\u7edc\u3002\u672c\u6587\u63d0\u4f9b\u4e86\u4e00\u4e2a\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95ee\u60a8\u7684 BliKVM \u7684\u793a\u4f8b\uff0c\u4f46\u60a8\u4e5f\u53ef\u4ee5\u4f7f\u7528 Tailscale \u6216\u5176\u4ed6 VPN \u89e3\u51b3\u65b9\u6848\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u57fa\u672c\u793a\u4f8b\uff0c\u5982\u9700\u4efb\u4f55\u7279\u5b9a\u8bbe\u7f6e\u6216\u529f\u80fd\uff0c\u8bf7\u53c2\u9605 ZeroTier\u6587\u6863 \u3002 \u5728 BliKVM \u4e0a\u5b89\u88c5 ZeroTier \u9996\u5148\uff0c\u5728 ZeroTier \u4e0a\u51c6\u5907\u8d26\u6237\u548c VPN \u7f51\u7edc\uff0c\u5177\u4f53\u64cd\u4f5c\u8bf7\u53c2\u89c1\u8fd9\u91cc\uff1a \u521b\u5efa\u7f51\u7edc \uff0c\u4fdd\u5b58\u7f51\u7edc ID \u4ee5\u4f9b\u4ee5\u540e\u4f7f\u7528\u3002\u63a5\u4e0b\u6765\uff0c\u4f7f\u7528 SSH \u534f\u8bae\u8fde\u63a5\u5230 BliKVM \u7ec8\u7aef\uff0c\u5e76\u68c0\u67e5\u8bfb\u5199\u6743\u9650\u3002\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u5176\u8bbe\u7f6e\u4e3a\u53ef\u5199\u3002 \u73b0\u5728\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\u5b89\u88c5 ZeroTier \u5ba2\u6237\u7aef\uff1a curl -s https://install.zerotier.com | sudo bash \u8bf7\u6ce8\u610f\uff0c\u5728\u67d0\u4e9b\u5730\u533a\uff0c\u5982\u4e2d\u56fd\uff0c\u76f4\u63a5\u4e0b\u8f7d ZeroTier \u53ef\u80fd\u4f1a\u53d7\u5230\u7f51\u7edc\u9650\u5236\u7684\u5f71\u54cd\u3002\u8bf7\u76f8\u5e94\u914d\u7f6e\u60a8\u7684\u7f51\u7edc\u3002 \u5c06 BliKVM \u6dfb\u52a0\u5230\u60a8\u7684 ZeroTier \u7f51\u7edc \u5728 BliKVM \u7ec8\u7aef\u4e0a\uff0c\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\u5c06 BliKVM \u6dfb\u52a0\u5230\u60a8\u7684 ZeroTier \u7f51\u7edc\uff08\u4f7f\u7528 ZeroTier \u7f51\u7edc ID\uff0c\u4f8b\u5982 d5e04297a16fa690\uff09\uff1a sudo zerotier-cli join d5e04297a16fa690 \u5982\u679c\u4e00\u5207\u987a\u5229\uff0c\u60a8\u53ef\u4ee5\u5728 BliKVM \u7ec8\u7aef\u4e0a\u8fd0\u884c ip addr show zerotier \u7f51\u7edc\u8bbe\u5907\uff08\u540d\u79f0\u4ee5 zt \u5f00\u5934\uff09\u4ee5\u67e5\u770b ZeroTier \u4e3a\u865a\u62df\u7f51\u7edc\u5206\u914d\u7684 IP \u5730\u5740\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u793a\u4f8b\u8f93\u51fa\uff1a 3: zt6ovrlscs:  mtu 2800 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether d6:e4:eb:ae:db:64 brd ff:ff:ff:ff:ff:ff inet 172.25.96.75/16 brd 172.25.255.255 scope global zt6ovrlscs valid_lft forever preferred_lft forever inet6 fe80::d4e4:ebff:feae:db64/64 scope link valid_lft forever preferred_lft forever IP \u5730\u5740\uff0c\u4f8b\u5982 172.25.96.75\uff0c\u53ef\u7528\u4e8e\u4ece\u4e3b\u673a\u673a\u5668\u8bbf\u95ee BliKVM Web \u754c\u9762\u3002 \u5728\u5ba2\u6237\u8ba1\u7b97\u673a\u4e0a\u5b89\u88c5 ZeroTier \u8f6c\u5230\u4e0b\u8f7d\u9875\u9762\uff0c\u5728 ZeroTier \u7f51\u7ad9\u4e0a\u5b89\u88c5 ZeroTier \u5230\u63a7\u5236\u4e3b\u673a\u3002\u52a0\u5165\u60a8\u7684 ZeroTier \u7f51\u7edc ID\uff0c\u7136\u540e\u60a8\u53ef\u4ee5\u68c0\u67e5\u60a8\u7684\u7f51\u7edc\u9875\u9762\uff0c\u9a8c\u8bc1\u4e24\u53f0\u673a\u5668\u662f\u5426\u5728\u7ebf\u3002\u68c0\u67e5\u5b83\u4eec\u662f\u5426\u88ab\u6388\u6743\u8fde\u63a5\u5230\u7f51\u7edc\uff08Auth? \u5217\uff09\u3002\u4e00\u65e6\u5b83\u4eec\u5728\u7ebf\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u5730\u5740\u4ece\u63a7\u5236\u4e3b\u673a\u673a\u5668\u8bbf\u95ee BliKVM\uff1a http://","title":"Zerotier VPN"},{"location":"zerotier/#zerotier-vpn","text":"ZeroTier \u5141\u8bb8\u901a\u8fc7 NAT \u5728\u53cc\u65b9\u4e4b\u95f4\u5b89\u5168\u8bbf\u95ee\u60a8\u7684 BliKVM\u3002\u5b83\u5141\u8bb8\u60a8\u6784\u5efa\u51e0\u4e4e\u4efb\u4f55\u7c7b\u578b\u7684\u73b0\u4ee3\u3001\u5b89\u5168\u7684\u591a\u70b9\u865a\u62df\u5316\u7f51\u7edc\u3002\u672c\u6587\u63d0\u4f9b\u4e86\u4e00\u4e2a\u901a\u8fc7\u4e92\u8054\u7f51\u8bbf\u95ee\u60a8\u7684 BliKVM \u7684\u793a\u4f8b\uff0c\u4f46\u60a8\u4e5f\u53ef\u4ee5\u4f7f\u7528 Tailscale \u6216\u5176\u4ed6 VPN \u89e3\u51b3\u65b9\u6848\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u57fa\u672c\u793a\u4f8b\uff0c\u5982\u9700\u4efb\u4f55\u7279\u5b9a\u8bbe\u7f6e\u6216\u529f\u80fd\uff0c\u8bf7\u53c2\u9605 ZeroTier\u6587\u6863 \u3002","title":"ZeroTier VPN"},{"location":"zerotier/#blikvm-zerotier","text":"\u9996\u5148\uff0c\u5728 ZeroTier \u4e0a\u51c6\u5907\u8d26\u6237\u548c VPN \u7f51\u7edc\uff0c\u5177\u4f53\u64cd\u4f5c\u8bf7\u53c2\u89c1\u8fd9\u91cc\uff1a \u521b\u5efa\u7f51\u7edc \uff0c\u4fdd\u5b58\u7f51\u7edc ID \u4ee5\u4f9b\u4ee5\u540e\u4f7f\u7528\u3002\u63a5\u4e0b\u6765\uff0c\u4f7f\u7528 SSH \u534f\u8bae\u8fde\u63a5\u5230 BliKVM \u7ec8\u7aef\uff0c\u5e76\u68c0\u67e5\u8bfb\u5199\u6743\u9650\u3002\u5982\u679c\u662f\u53ea\u8bfb\u7cfb\u7edf\uff0c\u8bf7\u4f7f\u7528 rw \u547d\u4ee4\u5c06\u5176\u8bbe\u7f6e\u4e3a\u53ef\u5199\u3002 \u73b0\u5728\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\u5b89\u88c5 ZeroTier \u5ba2\u6237\u7aef\uff1a curl -s https://install.zerotier.com | sudo bash \u8bf7\u6ce8\u610f\uff0c\u5728\u67d0\u4e9b\u5730\u533a\uff0c\u5982\u4e2d\u56fd\uff0c\u76f4\u63a5\u4e0b\u8f7d ZeroTier \u53ef\u80fd\u4f1a\u53d7\u5230\u7f51\u7edc\u9650\u5236\u7684\u5f71\u54cd\u3002\u8bf7\u76f8\u5e94\u914d\u7f6e\u60a8\u7684\u7f51\u7edc\u3002","title":"\u5728 BliKVM \u4e0a\u5b89\u88c5 ZeroTier"},{"location":"zerotier/#blikvm-zerotier_1","text":"\u5728 BliKVM \u7ec8\u7aef\u4e0a\uff0c\u4f7f\u7528\u4ee5\u4e0b\u547d\u4ee4\u5c06 BliKVM \u6dfb\u52a0\u5230\u60a8\u7684 ZeroTier \u7f51\u7edc\uff08\u4f7f\u7528 ZeroTier \u7f51\u7edc ID\uff0c\u4f8b\u5982 d5e04297a16fa690\uff09\uff1a sudo zerotier-cli join d5e04297a16fa690 \u5982\u679c\u4e00\u5207\u987a\u5229\uff0c\u60a8\u53ef\u4ee5\u5728 BliKVM \u7ec8\u7aef\u4e0a\u8fd0\u884c ip addr show zerotier \u7f51\u7edc\u8bbe\u5907\uff08\u540d\u79f0\u4ee5 zt \u5f00\u5934\uff09\u4ee5\u67e5\u770b ZeroTier \u4e3a\u865a\u62df\u7f51\u7edc\u5206\u914d\u7684 IP \u5730\u5740\u3002\u4ee5\u4e0b\u662f\u4e00\u4e2a\u793a\u4f8b\u8f93\u51fa\uff1a 3: zt6ovrlscs:  mtu 2800 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether d6:e4:eb:ae:db:64 brd ff:ff:ff:ff:ff:ff inet 172.25.96.75/16 brd 172.25.255.255 scope global zt6ovrlscs valid_lft forever preferred_lft forever inet6 fe80::d4e4:ebff:feae:db64/64 scope link valid_lft forever preferred_lft forever IP \u5730\u5740\uff0c\u4f8b\u5982 172.25.96.75\uff0c\u53ef\u7528\u4e8e\u4ece\u4e3b\u673a\u673a\u5668\u8bbf\u95ee BliKVM Web \u754c\u9762\u3002","title":"\u5c06 BliKVM \u6dfb\u52a0\u5230\u60a8\u7684 ZeroTier \u7f51\u7edc"},{"location":"zerotier/#zerotier","text":"\u8f6c\u5230\u4e0b\u8f7d\u9875\u9762\uff0c\u5728 ZeroTier \u7f51\u7ad9\u4e0a\u5b89\u88c5 ZeroTier \u5230\u63a7\u5236\u4e3b\u673a\u3002\u52a0\u5165\u60a8\u7684 ZeroTier \u7f51\u7edc ID\uff0c\u7136\u540e\u60a8\u53ef\u4ee5\u68c0\u67e5\u60a8\u7684\u7f51\u7edc\u9875\u9762\uff0c\u9a8c\u8bc1\u4e24\u53f0\u673a\u5668\u662f\u5426\u5728\u7ebf\u3002\u68c0\u67e5\u5b83\u4eec\u662f\u5426\u88ab\u6388\u6743\u8fde\u63a5\u5230\u7f51\u7edc\uff08Auth? \u5217\uff09\u3002\u4e00\u65e6\u5b83\u4eec\u5728\u7ebf\uff0c\u60a8\u53ef\u4ee5\u4f7f\u7528\u4ee5\u4e0b\u5730\u5740\u4ece\u63a7\u5236\u4e3b\u673a\u673a\u5668\u8bbf\u95ee BliKVM\uff1a http://","title":"\u5728\u5ba2\u6237\u8ba1\u7b97\u673a\u4e0a\u5b89\u88c5 ZeroTier"}]}
\ No newline at end of file
diff --git a/generated/zh/sitemap.xml b/generated/zh/sitemap.xml
index 346fa216..45f2a71d 100644
--- a/generated/zh/sitemap.xml
+++ b/generated/zh/sitemap.xml
@@ -2,197 +2,197 @@
 
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
     
          None
-         2024-11-28
+         2024-12-04
          daily
     
 
\ No newline at end of file
diff --git a/generated/zh/sitemap.xml.gz b/generated/zh/sitemap.xml.gz
index 44354680..d3c5c11b 100644
Binary files a/generated/zh/sitemap.xml.gz and b/generated/zh/sitemap.xml.gz differ
diff --git a/generated/zh/static_ip/index.html b/generated/zh/static_ip/index.html
index 2b37c817..8a4ee83d 100644
--- a/generated/zh/static_ip/index.html
+++ b/generated/zh/static_ip/index.html
@@ -515,9 +515,9 @@ 
v4参考

 dns-nameservers 192.168.0.1
注意：根据您的网络设置，可能需要修改上述示例中的IP地址、网关和DNS服务器的值。 -
  • 保存文件并退出编辑器。
    • -
  • 重新启动BliKVM以使静态IP设置生效： - 
    sudo reboot
+
  • 保存文件并退出编辑器, 
    • 
+
  • 重新启动NetworkManager以使静态IP设置生效：
+   
    sudo systemctl restart NetworkManager
 
    • 
 
 
    根据您的网络环境和需求，您可以根据上述步骤自定义配置静态IP地址。请确保IP地址、网关和DNS服务器的设置与您的网络设置相匹配。
    
diff --git a/generated/zh/update/index.html b/generated/zh/update/index.html
index a9efb801..e6072a7c 100644
--- a/generated/zh/update/index.html
+++ b/generated/zh/update/index.html
@@ -532,7 +532,7 @@ 
    手动运行脚本更新
    
 
     
       Last update:
-      November 15, 2024
+      November 28, 2024
 
    
         Created:
         January 21, 2023
diff --git a/overrides/assets/images/https/letsencrypt.png b/overrides/assets/images/https/letsencrypt.png
new file mode 100644
index 00000000..c78a1782
Binary files /dev/null and b/overrides/assets/images/https/letsencrypt.png differ