+
-***
+---
## 左侧导航栏说明
@@ -122,11 +126,15 @@ sidebar_position: 2
- 退出登录
- 消息通知
-
+
下面逐项说明。
-***
+---
## 常用工具
@@ -137,15 +145,19 @@ sidebar_position: 2
- 选择哪些配置作为常用工具
- 拖拽已选工具排序
- 全选 / 反选 / 清空
-
+
-***
+---
## 网络设置
包含四块：以太网、USB 网卡、WiFi、WiFi 热点。
-
+
### 以太网
@@ -157,9 +169,9 @@ sidebar_position: 2
- 网关
- DNS
-
- 
- 
+
+
作用：
@@ -205,7 +221,7 @@ sidebar_position: 2
- 手动添加网络（SSID、安全方式、密码、自动连接）
- 网络高级设置（DHCP/手动 IP、DNS 列表）
-
+
作用：
@@ -230,7 +246,7 @@ sidebar_position: 2
- 隐藏热点
- 热点网段
-
+
作用：
@@ -245,14 +261,17 @@ sidebar_position: 2
:::
-***
+---
## 画面设置
包含：全屏、缩放模式、EDID、图像质量、视频模式。
-
-
+
### 全屏
@@ -310,14 +329,17 @@ sidebar_position: 2
- 常规远程控制优先 H.264
- 特殊兼容场景可切 MJPEG
-***
+---
## 键盘与鼠标
包含：屏幕键盘、快捷粘贴、快捷键、鼠标设置。
-
-
+
### 屏幕键盘
@@ -336,7 +358,7 @@ sidebar_position: 2
- 历史粘贴记录复用
- 支持清空历史
-
+
作用：
@@ -355,7 +377,7 @@ sidebar_position: 2
- 快速触发常用组合（例如系统快捷操作）
- 降低复杂按键输入失败率
-
+
### 鼠标设置
@@ -369,14 +391,18 @@ sidebar_position: 2
- 滚动速率
- 防止休眠（鼠标抖动）
-
+
作用：
- 适配不同远控场景下的鼠标手感与行为
- 防止目标设备因长时间静止而休眠
-***
+---
## 虚拟设备
@@ -404,7 +430,7 @@ sidebar_position: 2
:::
-***
+---
## 系统设置
@@ -438,7 +464,7 @@ sidebar_position: 2
作用：
-- 供脚本/自动化工具访问接口时使用，详细文档请参考 [这里](/linkr/linkr/access-token)
+- 供脚本/自动化工具访问接口时使用，详细文档请参考 [这里](/linkr/linkr-kvm/access-token)
:::warning
@@ -467,7 +493,6 @@ sidebar_position: 2
:::
-
### 设备重置
作用：
@@ -483,7 +508,6 @@ sidebar_position: 2
:::
-
### 系统更新
当前可用升级方案：本地升级
@@ -499,11 +523,11 @@ sidebar_position: 2
- 页面提供发布地址跳转（GitHub Releases）
- 在线升级代码有预留，但当前主流程以本地升级为主
-***
+---
## 关于
-包含：设备信息、用户协议、瑞莎灵控介绍、日志下载。
+包含：设备信息、用户协议、Radxa Linkr 介绍、日志下载。
### 设备信息
@@ -522,7 +546,7 @@ sidebar_position: 2
- 在线查看最终用户许可协议内容
-### 瑞莎灵控（Radxa Linkr）介绍
+### Radxa Linkr 介绍
作用：
@@ -535,26 +559,28 @@ sidebar_position: 2
- 导出日志压缩包（`linkr_log.tar.gz`）
- 用于故障排查与技术支持
-***
-
+---
## 高级设置
包含：Tailscale，MAC 设备唤醒
-
+
### Tailscale
作用：
-- 配置 Tailscale 网络，实现跨设备安全通信，详细文档请参考 [这里](/linkr/linkr/advanced-usage/remote-access)
+- 配置 Tailscale 网络，实现跨设备安全通信，详细文档请参考 [这里](/linkr/linkr-kvm/advanced-usage/remote-access)
- 用于远程访问、文件共享、VPN 等场景
-
:::tip
-使用 Tailscale 之前请确认灵控能连接外部网络，通过 USB-C 转 RJ45 线或者 WiFi 连接路由器
+使用 Tailscale 之前请确认 Linkr 能连接外部网络，通过 USB-C 转 RJ45 线或者 WiFi 连接路由器
:::
@@ -562,11 +588,10 @@ sidebar_position: 2
作用：
-- 配置 MAC 设备唤醒，实现远程启动，详细文档请参考 [这里](/linkr/linkr/advanced-usage/wake-on-lan)
+- 配置 MAC 设备唤醒，实现远程启动，详细文档请参考 [这里](/linkr/linkr-kvm/advanced-usage/wake-on-lan)
- 用于在无电源时唤醒设备，保持连接状态
-***
-
+---
## 侧边栏底部功能
@@ -583,7 +608,7 @@ sidebar_position: 2
- 打开通知列表查看任务与状态消息
-***
+---
## 新用户推荐上手路径
@@ -596,7 +621,7 @@ sidebar_position: 2
5. 需要装系统时使用虚拟磁盘上传并挂载镜像
6. 最后在系统设置中完成密码、设备名、API Key 管理
-***
+---
## 常见注意事项（非常重要）
@@ -607,13 +632,12 @@ sidebar_position: 2
- 修改登录密码后通常需要重新登录
- MJPEG 在高分辨率下性能压力更大，常规建议优先 H.264
-***
+---
## 一句话总结
-如果你把这个系统当成网页里的远程键鼠画面控制台 + 设备管理中心，就能快速理解所有页面：
+如果你把这个系统当成网页里的远程 KVM 控制台 + 设备管理中心，就能快速理解所有页面：
- 中间看画面
- 下方做即时控制
- 左侧做系统配置与维护
-
diff --git a/docs/linkr/linkr/README.md b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/README.md
similarity index 50%
rename from docs/linkr/linkr/README.md
rename to i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/README.md
index 92d2b67252..b7a633adab 100644
--- a/docs/linkr/linkr/README.md
+++ b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/README.md
@@ -2,6 +2,6 @@
sidebar_position: 2
---
-# 瑞莎灵控
+# Linkr KVM
-` with Linkr's actual IP address or domain name (a LAN IP, Tailscale IP, etc. are all fine).
+Replace `` with the KVM's actual IP address or domain name (a LAN IP, Tailscale IP, etc. are all fine).
### Available Public APIs
@@ -113,7 +113,7 @@ curl -X POST \
"https://192.168.1.100/api/public/control"
```
-The format of the control data depends on the Linkr control protocol. Refer to the API documentation or the integration SDK for the specific fields.
+The format of the control data depends on the KVM control protocol. Refer to the API documentation or the integration SDK for the specific fields.
### Authentication Failure
@@ -122,7 +122,7 @@ If the response is `403 No Permission`, please check:
- The `Authorization` header is in the format `token ` (note there is a single space between `token` and the token)
- The token is complete and not truncated
- The token has not been deleted
-- The Linkr device's IP address or network is reachable
+- The KVM device's IP address or network is reachable
## Token Format
@@ -137,7 +137,7 @@ The name of each token must be unique on the device. You cannot create two token
1. **Principle of least privilege**: Create tokens with different names for different purposes so they can be revoked individually.
2. **Rotate regularly**: Periodically delete old tokens and generate new ones, especially after personnel changes or script migrations.
3. **Secure storage**: Use environment variables or secrets management tools to store tokens. Do not hardcode them in source code.
-4. **HTTPS access**: In production, access the Linkr API over HTTPS to prevent tokens from being intercepted in transit.
+4. **HTTPS access**: In production, access the KVM API over HTTPS to prevent tokens from being intercepted in transit.
5. **Revoke promptly**: If a token is leaked or no longer used, delete it in System Settings immediately.
## FAQ
@@ -152,7 +152,7 @@ The secret name does not follow the rules. Please make sure that:
### "Wrong Password" Message
-The user password entered when generating the token is not the Linkr login password. Use the correct password of the current management account.
+The user password entered when generating the token is not the KVM login password. Use the correct password of the current management account.
### "Name Already Exists" Message
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/advanced-usage/README.md b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/advanced-usage/README.md
similarity index 100%
rename from i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/advanced-usage/README.md
rename to i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/advanced-usage/README.md
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/advanced-usage/remote-access.mdx b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/advanced-usage/remote-access.mdx
similarity index 81%
rename from i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/advanced-usage/remote-access.mdx
rename to i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/advanced-usage/remote-access.mdx
index e64233bfdc..35d79b4ee5 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/advanced-usage/remote-access.mdx
+++ b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/advanced-usage/remote-access.mdx
@@ -4,7 +4,7 @@ sidebar_position: 1
# Tailscale Remote Access
-Radxa Linkr has a built-in [Tailscale](https://tailscale.com/) client that can join the device to your Tailscale virtual private network (VPN), allowing you to securely access the Linkr management interface from anywhere over an encrypted tunnel, with no public IP or manual port forwarding required.
+Linkr KVM has a built-in [Tailscale](https://tailscale.com/) client that can join the device to your Tailscale virtual private network (VPN), allowing you to securely access the KVM management interface from anywhere over an encrypted tunnel, with no public IP or manual port forwarding required.
Tailscale is based on the WireGuard protocol. The Tailscale coordination server handles node discovery and key exchange, and devices establish point-to-point encrypted connections with each other.
@@ -13,21 +13,21 @@ Tailscale is based on the WireGuard protocol. The Tailscale coordination server
| Capability | Description |
| --- | --- |
| Built-in client | The firmware pre-installs the `tailscale` / `tailscaled` binaries; no extra installation is required |
-| Web UI management | Enable, log in, and unbind the Tailscale account in the Linkr management interface |
+| Web UI management | Enable, log in, and unbind the Tailscale account in the KVM management interface |
| Auto-start on boot | Once enabled, the configuration persists and `tailscaled` starts automatically after the device reboots |
| Secure networking | Traffic is encrypted by WireGuard; only devices within the same Tailnet can communicate with each other |
## Before You Start
1. **Tailscale account**: Register a personal or team account on [tailscale.com](https://tailscale.com/) (the free plan is sufficient for personal use).
-2. **Network connection**: The Linkr device must be able to access the Internet (RJ45 wired or Wi-Fi is fine) in order to communicate with the Tailscale coordination server.
+2. **Network connection**: The KVM device must be able to access the Internet (RJ45 wired or Wi-Fi is fine) in order to communicate with the Tailscale coordination server.
3. **Browser**: When binding an account, you need to complete Tailscale authorization in a browser. Please make sure the management browser allows pop-ups.
## Operation Steps
### 1. Go to the Settings Page
-1. Open the Linkr management web interface and log in.
+1. Open the KVM management web interface and log in.
2. In the left sidebar, go to **System** → **Advanced Settings**.
3. Find the **Tailscale** option.
@@ -53,11 +53,11 @@ If the pop-up is blocked by the browser, please allow pop-ups for the current si
-### 4. Access Linkr via Tailscale
+### 4. Access the KVM via Tailscale
After a successful binding, you can view the Tailscale IP assigned to the device (usually in the `100.x.x.x` range) in the [Tailscale admin console](https://login.tailscale.com/admin/machines).
-On any device within the same Tailnet, use the following address to access Linkr:
+On any device within the same Tailnet, use the following address to access the KVM:
```
https://
@@ -70,7 +70,7 @@ https://..ts.net
```
:::tip Note
-When accessing through Tailscale, you still need to use Linkr's local login credentials (username and password). Tailscale only provides network-layer connectivity and does not replace Linkr authentication.
+When accessing through Tailscale, you still need to use the KVM's local login credentials (username and password). Tailscale only provides network-layer connectivity and does not replace KVM authentication.
:::
### 5. Unbind the Account
@@ -98,13 +98,13 @@ The Tailscale client is packaged into the firmware as built-in binaries:
### Relationship with Local Access
-Enabling Tailscale does not affect Linkr's local network access. The device can still be accessed through the LAN IP, Wi-Fi, or USB network, and Tailscale works as an additional remote access channel on top of these.
+Enabling Tailscale does not affect the KVM's local network access. The device can still be accessed through the LAN IP, Wi-Fi, or USB network, and Tailscale works as an additional remote access channel on top of these.
## FAQ
### Binding Fails or Has No Response for a Long Time
-- Confirm that the Linkr device is connected to the Internet.
+- Confirm that the KVM device is connected to the Internet.
- Check whether the browser has blocked pop-ups.
- Confirm that the Tailscale coordination server (`controlplane.tailscale.com`) is not blocked by a firewall.
- Try turning Tailscale off and on again, then re-bind.
@@ -112,7 +112,7 @@ Enabling Tailscale does not affect Linkr's local network access. The device can
### Cannot Access via the Tailscale IP After Enabling
- In the Tailscale admin console, confirm the device is online.
-- Confirm that the accessing client and Linkr are in the same Tailnet.
+- Confirm that the accessing client and the KVM are in the same Tailnet.
- Check that the Tailscale client on the accessing device is connected.
- Confirm that you are using the `https://` protocol and the correct Tailscale IP.
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/advanced-usage/wake-on-lan.mdx b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/advanced-usage/wake-on-lan.mdx
similarity index 70%
rename from i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/advanced-usage/wake-on-lan.mdx
rename to i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/advanced-usage/wake-on-lan.mdx
index 44dc11696f..b42137e7f6 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/advanced-usage/wake-on-lan.mdx
+++ b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/advanced-usage/wake-on-lan.mdx
@@ -4,9 +4,9 @@ sidebar_position: 2
# Wake on LAN Device Wakeup
-Radxa Linkr supports **Wake on LAN (WOL)**, which lets you remotely power on a target computer that is shut down or in sleep mode by sending a Magic Packet from Linkr to the target's network card — no need to press the power button in person.
+Linkr KVM supports **Wake on LAN (WOL)**, which lets you remotely power on a target computer that is shut down or in sleep mode by sending a Magic Packet from the KVM to the target's network card — no need to press the power button in person.
-Linkr and the target computer are usually in the same LAN through a network cable or a switch. After the wake-up packet is sent, the target machine will start up once it receives a broadcast packet that matches its MAC address.
+The KVM and the target computer are usually in the same LAN through a network cable or a switch. After the wake-up packet is sent, the target machine will start up once it receives a broadcast packet that matches its MAC address.
## Feature Overview
@@ -18,7 +18,7 @@ Linkr and the target computer are usually in the same LAN through a network cabl
## Before You Start
-Before using Linkr to wake up the target computer, please confirm that WOL has been correctly configured on the target machine:
+Before using the KVM to wake up the target computer, please confirm that WOL has been correctly configured on the target machine:
### 1. Enable Wake on LAN in BIOS/UEFI
@@ -49,8 +49,8 @@ sudo ethtool -s eth0 wol g
### 3. Network Connection Requirements
-- After the target computer is powered off, the **wired network card** must remain physically connected to the network (network cable, switch, or the same LAN segment as Linkr).
-- Linkr and the target computer should be in the **same Layer 2 broadcast domain** (same LAN or VLAN); the wake-up packet is sent as a UDP broadcast.
+- After the target computer is powered off, the **wired network card** must remain physically connected to the network (network cable, switch, or the same LAN segment as the KVM).
+- The KVM and the target computer should be in the **same Layer 2 broadcast domain** (same LAN or VLAN); the wake-up packet is sent as a UDP broadcast.
- Wireless network cards generally have poor WOL support. It is recommended to use the MAC address of the wired network port.
### 4. Get the Target MAC Address
@@ -61,13 +61,13 @@ With the target computer powered on, view the network card MAC address through a
- Linux: `ip link show`
- macOS: `ifconfig`
-Write down the MAC address of the network card that is connected to Linkr's LAN.
+Write down the MAC address of the network card that is connected to the KVM's LAN.
## Operation Steps
### 1. Go to Advanced Settings
-1. Open the Linkr management web interface and log in.
+1. Open the KVM management web interface and log in.
2. Click **Advanced Settings** (the gear icon) at the bottom of the left sidebar.
3. Find and expand the **Device Wakeup** collapsible panel on the page.
@@ -93,7 +93,7 @@ Each section has two hexadecimal digits, for a total of 6 sections, separated by
- **Send failed**: Please check the network connection and the WOL configuration on the target side, then try again.
:::tip Note
-"Sent successfully" means Linkr has successfully sent the Magic Packet. It does not guarantee that the target computer will start. If the target side has not correctly configured WOL or is not in the same broadcast domain, the computer may still not wake up.
+"Sent successfully" means the KVM has successfully sent the Magic Packet. It does not guarantee that the target computer will start. If the target side has not correctly configured WOL or is not in the same broadcast domain, the computer may still not wake up.
:::
## How It Works
@@ -101,11 +101,11 @@ Each section has two hexadecimal digits, for a total of 6 sections, separated by
Wake on LAN uses the standard Magic Packet format:
1. The packet body consists of 6 bytes of `0xFF` header followed by 16 repetitions of the target MAC address, for a total of 102 bytes.
-2. Linkr broadcasts the packet via UDP to `255.255.255.255:9` (the standard WOL port).
+2. The KVM broadcasts the packet via UDP to `255.255.255.255:9` (the standard WOL port).
3. The target network card listens for link-layer traffic in a powered-off / sleeping state. Once it identifies its own MAC, the motherboard powers on.
```
-Linkr management interface → Enter MAC → Click "Wake Up"
+KVM management interface → Enter MAC → Click "Wake Up"
↓
Construct Magic Packet (102 bytes)
↓
@@ -128,21 +128,21 @@ Linkr management interface → Enter MAC → Click "Wake Up"
- Confirm that you are using the **wired network card** MAC, and the network cable remains connected to the same LAN after power-off.
- Check whether the motherboard has disabled power to the network card after shutdown (ErP, EuP, and other energy-saving options).
- Some computers only support wake from **sleep / hibernation**, not from a full power-off (S5) state.
-- If Linkr and the target computer are not in the same network segment or VLAN, the broadcast packet may not reach the target network card.
+- If the KVM and the target computer are not in the same network segment or VLAN, the broadcast packet may not reach the target network card.
### Send Failed
-- Confirm the Linkr device's network is normal. Being able to access the management interface indicates basic connectivity.
-- Check whether switches and routers between Linkr and the target device allow broadcast traffic to pass through.
-- Try again later. If it continues to fail, restart Linkr's network service or check the firmware version.
+- Confirm the KVM device's network is normal. Being able to access the management interface indicates basic connectivity.
+- Check whether switches and routers between the KVM and the target device allow broadcast traffic to pass through.
+- Try again later. If it continues to fail, restart the KVM's network service or check the firmware version.
### How to Confirm Which Network Card's MAC Is Being Used
-If the computer has multiple network cards (wired, wireless, virtual), use the **MAC of the wired network card that is actually connected to Linkr's LAN**. You can temporarily disable other network cards and run `ipconfig` / `ip link` to confirm.
+If the computer has multiple network cards (wired, wireless, virtual), use the **MAC of the wired network card that is actually connected to the KVM's LAN**. You can temporarily disable other network cards and run `ipconfig` / `ip link` to confirm.
## Difference from the "Prevent Sleep" Feature
-Linkr also provides a **Prevent Sleep** feature: when connected to a remote computer, it periodically sends a tiny mouse movement to prevent the system from going to sleep. This feature applies to a scenario where **the computer is already powered on and connected through Linkr**.
+The KVM also provides a **Prevent Sleep** feature: when connected to a remote computer, it periodically sends a tiny mouse movement to prevent the system from going to sleep. This feature applies to a scenario where **the computer is already powered on and connected through the KVM**.
**Wake on LAN (Device Wakeup)** is used to **remotely power on a computer that is already shut down or in deep sleep** by sending a magic packet over the network. The two features have different uses; choose the one that fits your scenario.
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/develop-guide.mdx b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/develop-guide.mdx
similarity index 93%
rename from i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/develop-guide.mdx
rename to i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/develop-guide.mdx
index c9da2bf124..fe3c6cc823 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/develop-guide.mdx
+++ b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/develop-guide.mdx
@@ -6,7 +6,7 @@ sidebar_position: 7
## AI Agent Interface
-By calling the HTTP interfaces provided by Radxa Linkr (including screenshots, keyboard, and mouse control), you can remotely automate operations on the target machine.
+By calling the HTTP interfaces provided by Linkr (including screenshots, keyboard, and mouse control), you can remotely automate operations on the target machine.
**Refer to the "How to generate an API Token" section in the user guide to obtain an API Token.**
@@ -205,12 +205,12 @@ Only the following ASCII characters are supported:
**Parameter description:**
-- Index 0: The fixed string `"delay"`, indicating a pause to ensure that Linkr completes the previous operation. For example, used to ensure that a long text input completes.
+- Index 0: The fixed string `"delay"`, indicating a pause to ensure that the IPKVM completes the previous operation. For example, used to ensure that a long text input completes.
- Index 1: Field type: Number. The duration of the pause, in milliseconds.
**Note:**
-A delay event is usually required after a text input event to ensure that Linkr has enough time to fully process long text input. If Linkr needs a longer time to perform the operation, multiple delay events may be required. As a general rule, when the input text length is 30, a delay of 1000 milliseconds is needed.
+A delay event is usually required after a text input event to ensure that the IPKVM has enough time to fully process long text input. If the IPKVM needs a longer time to perform the operation, multiple delay events may be required. As a general rule, when the input text length is 30, a delay of 1000 milliseconds is needed.
**Example:**
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/firmware-update.mdx b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/firmware-update.mdx
similarity index 90%
rename from i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/firmware-update.mdx
rename to i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/firmware-update.mdx
index a0870bcd93..f1eadfd1ff 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/firmware-update.mdx
+++ b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/firmware-update.mdx
@@ -6,7 +6,7 @@ title: Firmware Update
# Firmware Update
-Radxa Linkr supports **local upgrade** by uploading a firmware package through the web management interface, which is used to obtain new features, bug fixes, and security updates. The firmware file is downloaded from GitHub Releases, and the device automatically verifies, decrypts, and installs it after upload.
+Linkr KVM supports **local upgrade** by uploading a firmware package through the web management interface, which is used to obtain new features, bug fixes, and security updates. The firmware file is downloaded from GitHub Releases, and the device automatically verifies, decrypts, and installs it after upload.
:::info Current Version
Firmware download page: [https://github.com/radxa-linkr/linkr/releases](https://github.com/radxa-linkr/linkr/releases)
@@ -18,7 +18,7 @@ Latest release example: `linkr-ota-1.0.1.bin` (the version number in the file na
1. **Check the current version**: In **About → Device Information**, view the "Current Firmware Version" and compare it with the version to be installed to make sure it is a higher version.
2. **Download the firmware package**: Visit [GitHub Releases](https://github.com/radxa-linkr/linkr/releases), and download the `linkr-ota-.bin` file from the **Assets** section of the corresponding version to your local computer.
-3. **Keep the network stable**: Please keep the connection between the browser and Linkr during the upgrade process; do not close the page or disconnect the network.
+3. **Keep the network stable**: Please keep the connection between the browser and the KVM during the upgrade process; do not close the page or disconnect the network.
4. **Reserve storage space**: The firmware package is about 50-60 MB, and the device needs to have enough free space. If space is insufficient, the message "Insufficient storage space" will be displayed.
5. **Avoid interruption**: During the upgrade, the device's system indicator LED is **flashing white** (see [Product Overview](./product-introduction)). Do not power off or unplug cables.
@@ -26,7 +26,7 @@ Latest release example: `linkr-ota-1.0.1.bin` (the version number in the file na
### 1. Go to System Update
-1. Open the Linkr management web interface and log in.
+1. Open the KVM management web interface and log in.
2. Click **System Settings** (the settings icon) in the left sidebar.
3. Find the **System Update** row, and click the **Update** button on the right.
@@ -52,7 +52,7 @@ The upgrade is divided into the following stages:
| Stage | UI Message | Description |
| --- | --- | --- |
-| Uploading | Uploading... | The firmware file is transferred from the browser to the Linkr device |
+| Uploading | Uploading... | The firmware file is transferred from the browser to the KVM device |
| Upgrading | Upgrading... | The device verifies the signature, decrypts, and writes the firmware |
| Complete | Upgraded, please restart the device | The installation is complete; takes effect after restart |
@@ -67,7 +67,7 @@ When the progress reaches 100% and the message **Upgraded, please restart the de
3. In **About → Device Information**, confirm that the firmware version has been updated.
:::caution Note
-A restart will briefly interrupt the Linkr service and remote connection. Please perform the upgrade in an appropriate time window, and make sure that the target host will not be affected by the Linkr restart.
+A restart will briefly interrupt the KVM service and remote connection. Please perform the upgrade in an appropriate time window, and make sure that the target host will not be affected by the KVM restart.
:::
## Download the Firmware
@@ -130,7 +130,7 @@ The firmware package needs to be written to the device's local storage. Please d
### Upload or Upgrade Failed
- Confirm that the downloaded `linkr-ota-*.bin` file is complete and not corrupted. Try downloading it again.
-- Check whether the network connection between the browser and Linkr is stable.
+- Check whether the network connection between the browser and the KVM is stable.
- Refresh the page and re-upload. Avoid running multiple upgrade tasks at the same time.
- After an upgrade failure, the device usually still runs the original firmware. If there is an abnormality, you can long-press the FN key for 10 seconds to restore factory settings (this will clear all configuration).
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/getting-started.mdx b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/getting-started.mdx
similarity index 79%
rename from i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/getting-started.mdx
rename to i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/getting-started.mdx
index 6b47bd82d8..8b06262fa3 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/getting-started.mdx
+++ b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/getting-started.mdx
@@ -6,7 +6,7 @@ title: Getting Started Guide
# Getting Started Guide
-This guide helps you complete the initial wiring of your Radxa Linkr, access the management interface, configure the account, and view the remote desktop of the target computer within **10 to 15 minutes**.
+This guide helps you complete the initial wiring of your Linkr KVM, access the management interface, configure the account, and view the remote desktop of the target computer within **10 to 15 minutes**.
For a more complete interface description, see the [Linkr Web User Guide](./usage). For hardware details, see [Product Overview](./product-introduction).
@@ -14,7 +14,7 @@ For a more complete interface description, see the [Linkr Web User Guide](./usag
| Item | Description |
| --- | --- |
-| Radxa Linkr device | Includes an HDMI cable and a USB Type-C data cable |
+| Linkr KVM device | Includes an HDMI cable and a USB Type-C data cable |
| Target computer | Has an HDMI output and a USB port (used for power and keyboard/mouse) |
| Management computer / phone | Install Chrome or Edge browser (latest version recommended) |
| Network | The same LAN, or connect via the device's hotspot first |
@@ -31,16 +31,16 @@ Method 2 (USB to RJ45, long distance):
Wire everything up as follows:
-1. **HDMI**: Linkr's HDMI male port → target computer's HDMI output port (capture the video).
-2. **USB Type-C (OTG)**: Linkr's tail OTG port → target computer's USB port (power + emulate keyboard/mouse).
+1. **HDMI**: KVM's HDMI male port → target computer's HDMI output port (capture the video).
+2. **USB Type-C (OTG)**: KVM's tail OTG port → target computer's USB port (power + emulate keyboard/mouse).
3. **Network** (choose one of the following):
- **USB Type-C (network)** → management computer (direct connection, no router needed); or
- **USB Type-C (network)** → router / switch (wired LAN); or
- Configure **Wi-Fi** later through the web interface; or
- - Use the device's **hotspot** to let the management computer connect to Linkr first.
+ - Use the device's **hotspot** to let the management computer connect to the KVM first.
:::tip Wiring Tips
-The OTG port is responsible for both powering Linkr and injecting keyboard/mouse signals into the target machine, so please use a reliable data cable. The network Type-C port is used for communication between Linkr and the management computer or router. When directly connected to a management computer, it can be accessed via `linkr-usb.local` (see below).
+The OTG port is responsible for both powering the KVM and injecting keyboard/mouse signals into the target machine, so please use a reliable data cable. The network Type-C port is used for communication between the KVM and the management computer or router. When directly connected to a management computer, it can be accessed via `linkr-usb.local` (see below).
:::
## Step 2: Confirm the Device Is Ready
@@ -63,8 +63,8 @@ We recommend using [linkr.now](https://linkr.now) to discover the device on the
1. Open **https://linkr.now** in the browser on the management computer.
2. Follow the on-page prompts to **grant local network access** (the browser needs to allow mDNS / local network discovery).
-3. (Optional) **Short-press the FN key once** on Linkr to help the page identify your device.
-4. Select your Linkr in the device list and enter the management interface.
+3. (Optional) **Short-press the FN key once** on the KVM to help the page identify your device.
+4. Select your KVM in the device list and enter the management interface.
@@ -79,15 +79,15 @@ If linkr.now cannot discover the device, try the following:
| mDNS (LAN) | `https://linkr.local` | The network Type-C is connected to a router, or already connected to the same LAN via Wi-Fi |
| mDNS (USB direct) | `https://linkr-usb.local` | The network Type-C is directly connected to a management computer, no router required |
| mDNS (initialized) | `https://linkr-.local` | After the initial configuration is complete, this address can also be used in LAN mode |
-| Device IP | `https://` | Direct access when the IP is known |
+| Device IP | `https://` | Direct access when the IP is known |
| Hotspot | Connect to the Wi-Fi `linkr-` and then use the address above | Initial configuration when no router network is available |
#### mDNS Domain Name Description
-Linkr automatically switches the mDNS hostname according to how the network Type-C is connected:
+The KVM automatically switches the mDNS hostname according to how the network Type-C is connected:
- **Connected to a router / switch, or joined the LAN via Wi-Fi**: Uses `linkr.local` (factory default); after the initial configuration is complete, `linkr-.local` is also available.
-- **Directly connected to a management computer**: Linkr communicates with the management computer over the USB network, and the mDNS domain name is **`linkr-usb.local`**, which is suitable for out-of-the-box use without a router.
+- **Directly connected to a management computer**: The KVM communicates with the management computer over the USB network, and the mDNS domain name is **`linkr-usb.local`**, which is suitable for out-of-the-box use without a router.
:::tip USB Direct Connection Access
After plugging the network Type-C into a management computer, enter `https://linkr-usb.local` in the browser address bar to open the management interface (no need to go through linkr.now).
@@ -97,7 +97,7 @@ After plugging the network Type-C into a management computer, enter `https://lin
When accessing over HTTPS, the browser may warn that the certificate is not trusted (self-signed certificate). Just choose to continue.
:::
-If the page shows "Connection Lost", please check: whether Linkr's blue LED is solid on, whether the management computer and Linkr are on the same network, and whether the network cable / Wi-Fi is working. See [FAQ](#faq) below for details.
+If the page shows "Connection Lost", please check: whether the KVM's blue LED is solid on, whether the management computer and the KVM are on the same network, and whether the network cable / Wi-Fi is working. See [FAQ](#faq) below for details.
## Step 4: Initial Configuration (New Device)
@@ -171,16 +171,16 @@ Configure network, Tailscale, firmware, etc. as needed
### linkr.now Cannot Find the Device
-- Confirm the Linkr system LED is solid blue.
-- Confirm the management computer and Linkr are on the same LAN (or connected via hotspot).
+- Confirm the KVM system LED is solid blue.
+- Confirm the management computer and the KVM are on the same LAN (or connected via hotspot).
- The browser needs to allow local network access. Try a short press of the FN key and then refresh the page.
- LAN mode: Use `https://linkr.local` or `https://linkr-.local` instead.
- USB direct mode: Use `https://linkr-usb.local` instead.
-- Or enter Linkr's IP address directly.
+- Or enter the KVM's IP address directly.
### Page Shows "Connection Lost"
-- Check that Linkr's power and network are normal.
+- Check that the KVM's power and network are normal.
- Make sure the network cable is plugged in tightly, or Wi-Fi is properly configured.
- Click **Refresh** on the page to retry.
@@ -188,7 +188,7 @@ Configure network, Tailscale, firmware, etc. as needed
- Confirm the target computer is powered on and has HDMI output.
- Check that the HDMI cable is firmly connected.
-- Observe whether Linkr's **video status LED** is on; flashing means the signal is abnormal.
+- Observe whether the KVM's **video status LED** is on; flashing means the signal is abnormal.
### Mouse and Keyboard Are Not Responding
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/product-introduction.mdx b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/product-introduction.mdx
similarity index 79%
rename from i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/product-introduction.mdx
rename to i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/product-introduction.mdx
index c21a7e4854..42ebc98f39 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/product-introduction.mdx
+++ b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/product-introduction.mdx
@@ -6,19 +6,19 @@ title: Product Overview
# Product Overview
-Radxa Linkr is a web-based remote control tool that delivers a keyboard/mouse-driven remote display solution. It captures the video output of a target host over HDMI and emulates keyboard/mouse input over USB, allowing you to remotely view and control the target computer from any browser-equipped terminal — no dedicated client software required.
+Linkr KVM (Radxa Linkr KVM) is a web-based IP KVM device that captures the video output of a target host over HDMI and emulates keyboard/mouse input over USB, allowing you to remotely view and control the target computer from any browser-equipped terminal — no dedicated client software required.
The device is compact, supports wired Ethernet, Wi-Fi, and hotspot connectivity, and ships with built-in capabilities such as Tailscale, Wake on LAN, and access tokens. It is well suited for home labs, remote operations and maintenance, and embedded development scenarios.
## Product Positioning
-Radxa Linkr is positioned as a **lightweight, ready-to-use hardware solution for remote keyboard/mouse display**:
+Linkr KVM is positioned as a **lightweight, ready-to-use hardware KVM-over-IP solution**:
- **Plug and play**: Connect to the target host via HDMI + USB Type-C and use it directly from a browser-based management page.
- **Web-first**: Remote video, keyboard/mouse control, networking, and system management are all unified in the web console.
- **Scenario-friendly**: Equally suitable for remote maintenance of desktop PCs, development boards, and headless servers.
-Compared with traditional rack-mount remote control appliances or pure-software remote desktop solutions, Radxa Linkr strikes a balance between cost, deployment complexity, and ease of use, making it ideal for individual developers, small teams, and educational scenarios.
+Compared with traditional rack-mount KVM appliances or pure-software remote desktop solutions, Linkr KVM strikes a balance between cost, deployment complexity, and ease of use, making it ideal for individual developers, small teams, and educational scenarios.
## Target Users
@@ -38,7 +38,7 @@ Compared with traditional rack-mount remote control appliances or pure-software
## Product Appearance
-Linkr uses a compact design, with the HDMI port, USB Type-C ports, the FN function key, and status indicator LEDs distributed on the front and side panels. The actual appearance is subject to the physical product. Refer to the product packaging or official materials for illustrative diagrams.
+Linkr KVM uses a compact design, with the HDMI port, USB Type-C ports, the FN function key, and status indicator LEDs distributed on the front and side panels. The actual appearance is subject to the physical product. Refer to the product packaging or official materials for illustrative diagrams.
@@ -56,9 +56,9 @@ Linkr uses a compact design, with the HDMI port, USB Type-C ports, the FN functi
1. **HDMI male port**: Connects to the HDMI video output of the target host to capture the video.
2. **USB Type-C (OTG)**: Provides both power and a data channel; emulates USB HID devices (keyboard/mouse) on the target machine.
-3. **USB Type-C (network)**: 100 Mbps wired network for the Linkr device's own network communication.
+3. **USB Type-C (network)**: 100 Mbps wired network for the KVM device's own network communication.
4. **Wi-Fi**: Connects to an existing wireless network, eliminating the need for cabling.
-5. **Hotspot**: Linkr can act as a hotspot for other terminals to access the management interface or share the network.
+5. **Hotspot**: The KVM can act as a hotspot for other terminals to access the management interface or share the network.
Typical wiring: the HDMI port connects to the target machine's video output; the OTG Type-C port connects to the target machine's USB port (power + keyboard/mouse); the network Type-C port or Wi-Fi provides network connectivity.
@@ -115,7 +115,7 @@ A long-press reset of the FN key clears all local configuration (including netwo
## Software Capabilities Overview
-In addition to the hardware remote control capabilities, the Linkr firmware and the web management interface also provide:
+In addition to the hardware KVM capabilities, the Linkr KVM firmware and the web management interface also provide:
| Feature | Description | Documentation |
| --- | --- | --- |
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/usage.mdx b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/usage.mdx
similarity index 96%
rename from i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/usage.mdx
rename to i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/usage.mdx
index 6c2707a9ab..ce55099c7b 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr/usage.mdx
+++ b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/usage.mdx
@@ -17,7 +17,7 @@ The Linkr Web is a web-based console for remotely managing target devices (compu
- Manage virtual disk mounts `ISO/IMG`
- Perform system-level management `user, password, device name, upgrade, reset, API Key`
-In short: it combines a **remote keyboard/mouse video client and a device management backend** into a single web page.
+In short: it combines a **remote KVM client and a device management backend** into a single web page.
***
@@ -437,7 +437,7 @@ Functions:
Purpose:
-- Used by scripts / automation tools to access the API. For detailed documentation, see [here](/linkr/linkr/access-token)
+- Used by scripts / automation tools to access the API. For detailed documentation, see [here](/linkr/linkr-kvm/access-token)
:::warning
@@ -544,7 +544,7 @@ Includes: Tailscale, MAC device wakeup
Purpose:
-- Configure the Tailscale network for secure cross-device communication. For detailed documentation, see [here](/linkr/linkr/advanced-usage/remote-access)
+- Configure the Tailscale network for secure cross-device communication. For detailed documentation, see [here](/linkr/linkr-kvm/advanced-usage/remote-access)
- Used for remote access, file sharing, VPN, and other scenarios
:::tip
@@ -557,7 +557,7 @@ Before using Tailscale, make sure Linkr can connect to the external network via
Purpose:
-- Configure MAC device wakeup to start the device remotely. For detailed documentation, see [here](/linkr/linkr/advanced-usage/wake-on-lan)
+- Configure MAC device wakeup to start the device remotely. For detailed documentation, see [here](/linkr/linkr-kvm/advanced-usage/wake-on-lan)
- Used to wake the device when no power is available, keeping the connection alive
***
@@ -605,7 +605,7 @@ We recommend getting familiar with the system in this order:
## One-Sentence Summary
-If you treat this system as a web-based remote keyboard/mouse video console and a device management center combined, you can quickly understand all the pages:
+If you treat this system as a web-based remote KVM console and a device management center combined, you can quickly understand all the pages:
- Middle: view the screen
- Bottom: instant control
diff --git a/i18n/en/docusaurus-theme-classic/navbar.json b/i18n/en/docusaurus-theme-classic/navbar.json
index ab10bd366e..978927c193 100644
--- a/i18n/en/docusaurus-theme-classic/navbar.json
+++ b/i18n/en/docusaurus-theme-classic/navbar.json
@@ -227,9 +227,9 @@
"message": "Single Board Computers",
"description": "Navbar item with label 主板"
},
- "item.label.灵控": {
- "message": "Linkr",
- "description": "Navbar item with label 灵控"
+ "item.label.远程控制工具": {
+ "message": "Linkr KVM",
+ "description": "Navbar item with label 远程控制工具"
},
"logo.alt": {
"message": "Radxa",
-
+
+
+
作用：
@@ -181,7 +193,11 @@ sidebar_position: 2
- USB 网卡网段（CIDR，如 `192.168.x.0/24`）
-
+
+
作用：
@@ -205,7 +221,7 @@ sidebar_position: 2
- 手动添加网络（SSID、安全方式、密码、自动连接）
- 网络高级设置（DHCP/手动 IP、DNS 列表）
-
+
作用：
@@ -230,7 +246,7 @@ sidebar_position: 2
- 隐藏热点
- 热点网段
-
+
作用：
@@ -245,14 +261,17 @@ sidebar_position: 2
:::
-***
+---
## 画面设置
包含：全屏、缩放模式、EDID、图像质量、视频模式。
-
-
+
### 全屏
@@ -310,14 +329,17 @@ sidebar_position: 2
- 常规远程控制优先 H.264
- 特殊兼容场景可切 MJPEG
-***
+---
## 键盘与鼠标
包含：屏幕键盘、快捷粘贴、快捷键、鼠标设置。
-
-
+
### 屏幕键盘
@@ -336,7 +358,7 @@ sidebar_position: 2
- 历史粘贴记录复用
- 支持清空历史
-
+
作用：
@@ -355,7 +377,7 @@ sidebar_position: 2
- 快速触发常用组合（例如系统快捷操作）
- 降低复杂按键输入失败率
-
+
### 鼠标设置
@@ -369,14 +391,18 @@ sidebar_position: 2
- 滚动速率
- 防止休眠（鼠标抖动）
-
+
作用：
- 适配不同远控场景下的鼠标手感与行为
- 防止目标设备因长时间静止而休眠
-***
+---
## 虚拟设备
@@ -404,7 +430,7 @@ sidebar_position: 2
:::
-***
+---
## 系统设置
@@ -438,7 +464,7 @@ sidebar_position: 2
作用：
-- 供脚本/自动化工具访问接口时使用，详细文档请参考 [这里](/linkr/linkr/access-token)
+- 供脚本/自动化工具访问接口时使用，详细文档请参考 [这里](/linkr/linkr-kvm/access-token)
:::warning
@@ -467,7 +493,6 @@ sidebar_position: 2
:::
-
### 设备重置
作用：
@@ -483,7 +508,6 @@ sidebar_position: 2
:::
-
### 系统更新
当前可用升级方案：本地升级
@@ -499,11 +523,11 @@ sidebar_position: 2
- 页面提供发布地址跳转（GitHub Releases）
- 在线升级代码有预留，但当前主流程以本地升级为主
-***
+---
## 关于
-包含：设备信息、用户协议、瑞莎灵控介绍、日志下载。
+包含：设备信息、用户协议、Radxa Linkr 介绍、日志下载。
### 设备信息
@@ -522,7 +546,7 @@ sidebar_position: 2
- 在线查看最终用户许可协议内容
-### 瑞莎灵控（Radxa Linkr）介绍
+### Radxa Linkr 介绍
作用：
@@ -535,26 +559,28 @@ sidebar_position: 2
- 导出日志压缩包（`linkr_log.tar.gz`）
- 用于故障排查与技术支持
-***
-
+---
## 高级设置
包含：Tailscale，MAC 设备唤醒
-
+
### Tailscale
作用：
-- 配置 Tailscale 网络，实现跨设备安全通信，详细文档请参考 [这里](/linkr/linkr/advanced-usage/remote-access)
+- 配置 Tailscale 网络，实现跨设备安全通信，详细文档请参考 [这里](/linkr/linkr-kvm/advanced-usage/remote-access)
- 用于远程访问、文件共享、VPN 等场景
-
:::tip
-使用 Tailscale 之前请确认灵控能连接外部网络，通过 USB-C 转 RJ45 线或者 WiFi 连接路由器
+使用 Tailscale 之前请确认 Linkr 能连接外部网络，通过 USB-C 转 RJ45 线或者 WiFi 连接路由器
:::
@@ -562,11 +588,10 @@ sidebar_position: 2
作用：
-- 配置 MAC 设备唤醒，实现远程启动，详细文档请参考 [这里](/linkr/linkr/advanced-usage/wake-on-lan)
+- 配置 MAC 设备唤醒，实现远程启动，详细文档请参考 [这里](/linkr/linkr-kvm/advanced-usage/wake-on-lan)
- 用于在无电源时唤醒设备，保持连接状态
-***
-
+---
## 侧边栏底部功能
@@ -583,7 +608,7 @@ sidebar_position: 2
- 打开通知列表查看任务与状态消息
-***
+---
## 新用户推荐上手路径
@@ -596,7 +621,7 @@ sidebar_position: 2
5. 需要装系统时使用虚拟磁盘上传并挂载镜像
6. 最后在系统设置中完成密码、设备名、API Key 管理
-***
+---
## 常见注意事项（非常重要）
@@ -607,13 +632,12 @@ sidebar_position: 2
- 修改登录密码后通常需要重新登录
- MJPEG 在高分辨率下性能压力更大，常规建议优先 H.264
-***
+---
## 一句话总结
-如果你把这个系统当成网页里的远程键鼠画面控制台 + 设备管理中心，就能快速理解所有页面：
+如果你把这个系统当成网页里的远程 KVM 控制台 + 设备管理中心，就能快速理解所有页面：
- 中间看画面
- 下方做即时控制
- 左侧做系统配置与维护
-
diff --git a/docs/linkr/linkr/README.md b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/README.md
similarity index 50%
rename from docs/linkr/linkr/README.md
rename to i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/README.md
index 92d2b67252..b7a633adab 100644
--- a/docs/linkr/linkr/README.md
+++ b/i18n/en/docusaurus-plugin-content-docs/current/linkr/linkr-kvm/README.md
@@ -2,6 +2,6 @@
sidebar_position: 2
---
-# 瑞莎灵控
+# Linkr KVM
-