mirror of
https://github.com/sipeed/sipeed_wiki.git
synced 2026-09-11 00:22:49 -05:00
Merge pull request #973 from compile-js/fix-kvm
Rearranged the FAQ content of NanoKVM Cube
This commit is contained in:
BuGu
@@ -5,86 +5,96 @@ keywords: NanoKVM, Remote desktop, Lichee, PiKVM, RISCV, tool
|
||||
|
||||
## Exception Fixes
|
||||
|
||||
Please use the table of contents on the right to locate the issue that matches your situation.
|
||||
|
||||
**The following solutions are based on the latest application version. If you encounter issues, please update the application first. If you cannot update via the web interface, please follow the steps below for a forced update:**
|
||||
|
||||
1. Refer to [this link](https://wiki.sipeed.com/hardware/zh/kvm/NanoKVM/system/updating.html#%E8%8E%B7%E5%8F%96-IP) to connect the development board.
|
||||
2. Execute: `python /etc/kvm/update-nanokvm.py`
|
||||
> Users outside of China may experience download failures due to DNS issues. Please refer to [Detailed DNS Configuration Guide for NanoKVM Cube/Lite/PCIe](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/user_guide.html#Setting-DNS) to add recommended DNS servers and try again.
|
||||
> Earlier versions of the application may not have this script file. Please download [here](https://github.com/sipeed/NanoKVM/blob/main/kvmapp/system/update-nanokvm.py), extract it, and grant execute permissions before trying again.
|
||||
1. Refer to [this link](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/system/updating.html#%E8%8E%B7%E5%8F%96-IP) to connect to the development board.
|
||||
2. Run: `python /etc/kvm/update-nanokvm.py`
|
||||
|
||||
### About Password
|
||||
> Users outside China may experience download failures due to DNS issues. Please refer to [Detailed DNS Configuration Guide for NanoKVM Cube/Lite/PCIe](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/user_guide.html#设置DNS) and add the recommended DNS servers before trying again.
|
||||
> Early application versions may not include this script. In that case, download it from https://github.com/sipeed/NanoKVM/blob/main/kvmapp/system/update-nanokvm.py, extract it, grant execute permission, and try again.
|
||||
|
||||
1. After updating to version 2.1.5, if you haven't set a web password before, you will be prompted to change the password upon logging in. When you change the password, the backend `root` password will also be synchronized to the web password. If you have already changed the web password before, the backend `root` password will not be changed automatically. You can modify it using `passwd` in the terminal or click "Reset Password" in the web settings.
|
||||
2. If the application version is greater than 2.1.5 and you forget the password, you can press the `BOOT` button on the device for more than 10 seconds (the BOOT button for the NanoKVM-Cube is located next to the USB-HID interface, while the PCIe version can be found on the panel. Older versions of the NanoKVM Full may not have a hole in the corresponding location and require disassembly). For detailed instructions, please refer to [Reset Password](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/reset.html).
|
||||
3. If holding down the button does not reset the password, it may be because the application version is less than 2.1.5. Please refer to [here](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/system/flashing.html) to reflash the image. Note that reflashing the image will erase all configuration information.
|
||||
### About Resetting the Web Password and SSH Password
|
||||
|
||||
#### Default Passwords
|
||||
|
||||
- **Web interface:** `username`/`password` = `admin` / `admin`
|
||||
- **SSH:** `username`/`password` = `root` / `root`
|
||||
|
||||
#### Changing or Resetting the Password
|
||||
|
||||
1. Starting from version `2.1.5`, if you have never set a web password before, you will be prompted to change it after login. After changing it, the SSH `root` password will also be synchronized to the new web password.
|
||||
2. Starting from version `2.1.5`, if you forget the password, press and hold the `BOOT` button on the device for more than 10 seconds.
|
||||
- On **NanoKVM-Cube**, the `BOOT` button is located to the right of the USB-HID port.
|
||||
- On the **PCIe version**, the `BOOT` button is accessible on the panel.
|
||||
- On some older **NanoKVM Full** versions, there may be no opening at the corresponding location, so disassembly may be required.
|
||||
3. If holding the button does not reset the password, the application version may be lower than `2.1.5`. Please refer to [this link](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/system/flashing.html) to reflash the image. Note that reflashing will erase all configuration data.
|
||||
|
||||
### HID Keyboard and Mouse Not Working
|
||||
1. Use the "Reset HID" feature in the web interface.
|
||||
2. Some host systems have high requirements for USB keyboards and mice, needing to use "HID Only" mode. In this mode, USB only simulates keyboard and mouse devices. Please switch to this mode using the mouse icon in the web interface.
|
||||
3. Some motherboard systems require HID keyboard and mouse devices to have a BIOS identifier. NanoKVM can create a BIOS in `/boot` to enable this feature. Execute `touch /boot/BIOS && restart`.
|
||||
4. Check if the USB connection is stable. You can see if the HID icon on the OLED is lit, or use `cat /sys/class/udc/4340000.usb/state` in the web terminal. If it shows "not connected," then the USB cable may be faulty. Please replace the USB cable and try again.
|
||||
|
||||
### BIOS Does Not Recognize HID Keyboard and Mouse
|
||||
1. Some host systems have high requirements for USB keyboards and mice, needing to use "HID Only" mode. In this mode, USB only simulates keyboard and mouse devices that support BIOS. Please switch to this mode using the mouse icon in the web interface.
|
||||
2. Use the "Reset HID" feature in the web interface.
|
||||
1. Use the **Reset HID** function in the web interface.
|
||||
2. Some host systems have strict requirements for USB keyboards and mice and require **HID Only** mode. In this mode, USB simulates only keyboard and mouse devices. Switch to this mode using the mouse icon in the web interface.
|
||||
3. Some motherboards require HID keyboard and mouse devices to include a BIOS identifier. NanoKVM can enable this by creating `BIOS` under `/boot`. Run: `touch /boot/BIOS && restart`
|
||||
4. Check whether the USB connection is stable. You can verify whether the HID icon on the OLED is lit, or run the following command in the web terminal: `cat /sys/class/udc/4340000.usb/state`
|
||||
If it shows `not connected`, the USB cable may have poor contact. Replace the USB cable and try again.
|
||||
|
||||
### BIOS Does Not Recognize the HID Keyboard and Mouse
|
||||
|
||||
1. Some host systems require **HID Only** mode. In this mode, USB simulates only BIOS-compatible keyboard and mouse devices. Switch this mode using the mouse icon in the web interface.
|
||||
2. Use the **Reset HID** function in the web interface.
|
||||
3. On some Dell models, due to very poor motherboard driver compatibility, the keyboard and mouse may not be recognized in BIOS. There is currently no solution for this.
|
||||
|
||||
### Incorrect Key Mapping for Non-English Keyboards
|
||||
+ The keyboard layout needs to be modified in the controlled host system settings. For example, to modify a French keyboard in Ubuntu:
|
||||
Settings -> Keyboard -> Input Sources -> ‘+’ -> Add -> Search "French," then add.
|
||||
|
||||
### STA LED Not Flashing Normally
|
||||
- The keyboard layout must be changed in the settings of the controlled host system. For example, to set a French keyboard layout in Ubuntu:
|
||||
|
||||
The STA LED indicates the operating status of the NanoKVM. When functioning properly, the STA LED should flash irregularly. If the STA LED is continuously on or off, or exhibits regular intermittent extinguishing, the NanoKVM may be malfunctioning.
|
||||
`Settings -> Keyboard -> Input Sources -> '+' -> Add -> Search "French" -> Add`
|
||||
|
||||
1. If the STA LED intermittently extinguishes after powering on: The system did not detect the system on the TF card. Please check if the TF card is properly inserted and reflash the TF image.
|
||||
2. If the STA LED is off for an extended period: This is usually due to a lack of power. Please check the power supply status.
|
||||
### STA LED (Blue LED) Not Flashing Normally
|
||||
|
||||
> If powered only by USB-HID, the USB power may disconnect when the computer is shut down. Please refer to relevant documentation to set USB to always supply power in the BIOS, or use auxiliary power.
|
||||
> Connecting to an unconventional power supply may damage the NanoKVM and cause the STA LED to extinguish.
|
||||
The STA LED indicates the running status of NanoKVM.
|
||||
|
||||
3. If the STA LED remains on for an extended period without flashing: This situation generally should not occur with the official system and applications. If custom functions are configured within the NanoKVM system, there is a chance it may cause the system to freeze, leaving the STA LED lit. It is recommended to reflash the image.
|
||||
- **Normal state:** irregular flashing
|
||||
- **Regular intermittent off state after power-on:** the system did not detect a valid system on the TF card. Check whether the TF card is inserted correctly and reflash the TF image.
|
||||
- **Off for a long time:** usually caused by lack of power. Check the power supply.
|
||||
|
||||
### Unable to Obtain IP Address
|
||||
> If powered only through USB-HID, USB power may be cut off when the host computer shuts down. Please refer to your BIOS documentation and configure USB to stay powered, or use auxiliary power.
|
||||
> If connected to an abnormal or unsupported power source, NanoKVM may be damaged, which can also cause the STA LED to stay off.
|
||||
|
||||
1. Lite users should first check if a TF card is inserted. The Lite version is shipped without a card by default, so users need to provide their own TF card. Please follow the instructions [here](https://wiki.sipeed.com/hardware/zh/kvm/NanoKVM/system/flashing.html) to flash the card and retry.
|
||||
2. Check if the network switch supports 100M. Some newer switches do not support 100M connections; please replace the switch and try again.
|
||||
3. The NanoKVM Cube (including NanoKVM Full and NanoKVM Lite) may be unable to obtain an IP address when connecting to certain power sources/HDMI. Please confirm the following:
|
||||
> Disconnect all interfaces and power the device using a power bank, then connect the network cable to see if an IP can be obtained.
|
||||
> If an IP can be obtained, reconnect HDMI/computer USB to check if the IP exists.
|
||||
> If the IP exists only when powered by the power bank, but disappears after connecting HDMI/computer USB, this indicates the issue. Please contact customer service to purchase an isolator to resolve it.
|
||||
- **On continuously without flashing:** this normally should not happen with the official system and application. If custom features have been configured inside NanoKVM, the system may freeze and leave the STA LED constantly on. Reflashing the image is recommended.
|
||||
|
||||
### Unable to get an IP via DHCP and the IP address shows as 192.168.70.70
|
||||
### Unable to Obtain an IP Address
|
||||
|
||||
Please refer to [NanoKVM Static IP Fix](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/static_ip_fix.html).
|
||||
- **Lite users** should first check whether a TF card is inserted. The Lite version does not include a TF card by default, so users must prepare one themselves. Please follow the instructions [here](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/system/flashing.html) to flash the TF card and try again.
|
||||
- On **NanoKVM Cube** devices (including **NanoKVM Full** and **NanoKVM Lite**), certain power supplies or HDMI connections may prevent the device from obtaining an IP address. Please verify the following:
|
||||
|
||||
### No Display After Logging into the Browser Interface
|
||||
> Disconnect all cables, power the device using a power bank, and connect the network cable to see whether it can obtain an IP address.
|
||||
> If it can, reconnect HDMI and/or the host USB cable and check whether the IP address remains available.
|
||||
> If the IP address exists only when powered by the power bank, but disappears after connecting HDMI or the host USB, then this issue is confirmed. Please contact customer service to purchase an isolator.
|
||||
|
||||
- Check whether the network switch supports **100M Ethernet**. Some newer switches do not support 100M links. Replace the switch and try again.
|
||||
|
||||
### Unable to Obtain an IP Address via DHCP, and the Device Shows `192.168.70.70`
|
||||
|
||||
Please refer to [Static IP Fix](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/static_ip_fix.html).
|
||||
|
||||
### No Display After Logging In to the Browser Interface
|
||||
|
||||
#### Default Resolution Error
|
||||
NanoKVM only supports 1080P resolution, but the host may occasionally output video signals with specifications higher than 1080P. It is recommended to modify the default EDID to resolve this issue. Before proceeding, please upgrade to the latest APP (version 2.3.2 or above) in the web interface.
|
||||
> When using the Cube/Lite version, on-site operation is mandatory. After modification, please power cycle the device to apply the new configuration; otherwise, HDMI capture anomalies may occur.
|
||||
Access the web terminal and execute the command: `/kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin`. Confirm on-site operation for Cube/Lite.
|
||||
``` shell
|
||||
## PCIe Version Normal Flashing Output:
|
||||
# /kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin
|
||||
Chip Version: LT6911UXC
|
||||
Product Version : PCIE_A
|
||||
|
||||
=========================================================
|
||||
Incorrect EDID may cause issues such as
|
||||
inability to display images, please modify with caution
|
||||
=========================================================
|
||||
NanoKVM supports up to **1080P** resolution only, but the host may sometimes output a resolution higher than 1080P. It is recommended to modify the default EDID to solve this problem. Before doing so, please update the APP to the latest version (`2.3.2` or above) in the web interface.
|
||||
|
||||
EDID data loaded successfully from /kvmapp/system/tool/E21_NanoKVM.bin
|
||||
Writing EDID....
|
||||
EDID write completed
|
||||
Reading EDID...
|
||||
EDID data verified successfully
|
||||
##### Cube Version
|
||||
|
||||
=========================================================
|
||||
✅ EDID update successful!
|
||||
=========================================================
|
||||
On-site operation is required. After modification, you must power cycle the device to apply the new configuration. Otherwise, HDMI capture may behave abnormally.
|
||||
|
||||
## Cube/Lite Normal Flashing Output:
|
||||
Open the web terminal and run:
|
||||
|
||||
`/kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin`
|
||||
|
||||
```shell
|
||||
## Normal output for Cube/Lite:
|
||||
# /kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin
|
||||
Chip Version: LT6911UXC
|
||||
Product Version: CUBE_B
|
||||
@@ -117,91 +127,160 @@ Please manually power cycle the device to apply changes.
|
||||
=========================================================
|
||||
```
|
||||
|
||||
#### Other Issues
|
||||
1. The controlled host may be in sleep mode. Try pressing any key on the keyboard to wake it up.
|
||||
2. Non-Chrome browsers may experience issues with H264 not displaying, while MJPEG mode works normally. Please try again using Chrome.
|
||||
3. For the PCIe version, try clicking the reset HDMI option under the "Video" icon.
|
||||
4. For the Cube version, you can try unplugging and replugging the HDMI cable after opening the webpage.
|
||||
5. Check the resolution on the OLED or enter `echo "$(cat /kvmapp/kvm/width) * $(cat /kvmapp/kvm/height)"` in the web terminal, and compare it with the resolution of the controlled host. If they differ, you can manually set the resolution using `echo xxx > /kvmapp/kvm/width && echo xxx > /kvmapp/kvm/height`.
|
||||
> If the host system is Windows, the resolution shown in display settings may not match the actual resolution. Check in Advanced -> Active Signal Resolution.
|
||||
6. The early test version of Full NanoKVM uses standard cables to connect to the HDMI capture board, which may not detect the HDMI signal due to poor connections. You can reconnect the cable as shown in the image below or contact customer service to purchase dedicated cables.
|
||||
[](./../../../assets/NanoKVM/guide/Old_fix.png)
|
||||
7. Try restarting to resolve the issue: execute `reboot` in the web terminal.
|
||||
8. If the above methods do not identify the problem, execute `cat /proc/cvitek/vi_dbg` in the web terminal.
|
||||
> If `VIDevFPS` is 0, it means NanoKVM cannot get HDMI input. Check the following issues: Is the host outputting a video signal? Is the HDMI cable damaged? Is the Cube an early version with possible connection issues?
|
||||
> If `VIDevFPS` is not 0 and `VIFPS` is 0, it indicates that NanoKVM is not correctly configured for HDMI parameters. The Cube can replug the HDMI to auto-detect, while PCIe can click `Reset HDMI` under `Video` to auto-detect.
|
||||
> Check if `VIInImgWidth` and `VIInImgHeight` match the actual HDMI resolution. If they are different, it means NanoKVM did not auto-detect the correct HDMI parameters. Manually configure the resolution parameters as described in point 4.
|
||||
##### PCIe Version
|
||||
|
||||
### No Display After Host Wakes from Sleep
|
||||
After modification, power cycle the device to apply the new configuration. Otherwise, HDMI capture may behave abnormally.
|
||||
|
||||
1. Check if you are using a cheap DP to HDMI (passive adapter). These types of adapters lack a proper wake mechanism and cannot notify the NanoKVM that the display has been restored.
|
||||
2. For PCIe versions, you can click the "Reset HDMI" button to forcefully retrieve the display.
|
||||
3. The Cube/Lite versions lack a reset function; please switch to an active DP adapter.
|
||||
Open the web terminal and run:
|
||||
|
||||
### Serious screen delay in internal network environment
|
||||
`/kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin`
|
||||
|
||||
1. Try replacing the switch or power supply
|
||||
2. If it is invalid, please contact after-sales service
|
||||
```shell
|
||||
## Normal output for PCIe:
|
||||
# /kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin
|
||||
Chip Version: LT6911UXC
|
||||
Product Version : PCIE_A
|
||||
|
||||
### OLED Displaying Information Normally, But Unable to Open Webpage
|
||||
=========================================================
|
||||
Incorrect EDID may cause issues such as
|
||||
inability to display images, please modify with caution
|
||||
=========================================================
|
||||
|
||||
1. Please force update the application.
|
||||
EDID data loaded successfully from /kvmapp/system/tool/E21_NanoKVM.bin
|
||||
Writing EDID....
|
||||
EDID write completed
|
||||
Reading EDID...
|
||||
EDID data verified successfully
|
||||
|
||||
### OLED Not Lighting Up
|
||||
=========================================================
|
||||
✅ EDID update successful!
|
||||
=========================================================
|
||||
```
|
||||
|
||||
The NanoKVM Full and PCIe versions come with an OLED to display information such as IP. If the OLED does not light up, please follow these steps to troubleshoot:
|
||||
#### Other Possible Causes
|
||||
|
||||
1. Version `2.1.4` added an OLED sleep function; pressing the BOOT button can temporarily turn on the OLED.
|
||||
2. If the STA LED is flashing abnormally, first check whether the system is booting normally, and follow the steps outlined in “STA LED Not Flashing Normally” to troubleshoot.
|
||||
1. The controlled host may be in sleep mode. Press any key on the keyboard to try waking it up.
|
||||
2. Some non-Chrome browsers may fail to display H264 video while MJPEG works normally. Please try again using Chrome.
|
||||
3. On the **PCIe version**, try clicking **Reset HDMI** under the **Video** icon.
|
||||
4. On the **Cube version**, try unplugging and reconnecting the HDMI cable after opening the web page.
|
||||
5. Check the resolution shown on the OLED, or run the following command in the web terminal:
|
||||
|
||||
`echo "$(cat /kvmapp/kvm/width) * $(cat /kvmapp/kvm/height)"`
|
||||
|
||||
Compare it with the actual resolution of the controlled host. If they differ, you can manually set the resolution using:
|
||||
|
||||
`echo xxx > /kvmapp/kvm/width && echo xxx > /kvmapp/kvm/height`
|
||||
|
||||
> If the host system is Windows, the resolution shown in Display Settings may not match the actual output resolution. Please check **Advanced Display Settings -> Active Signal Resolution**.
|
||||
|
||||
6. Early internal test versions of **Full NanoKVM** used standard ribbon cables to connect the HDMI capture board. Poor cable contact may prevent HDMI signal detection. You can reconnect the cable as shown below, or contact customer service to purchase the dedicated cable.
|
||||
|
||||
|
||||
|
||||
7. Try rebooting the device by running: `reboot` in the web terminal.
|
||||
8. **If the methods above still cannot identify the problem**, run the following in the web terminal:
|
||||
|
||||
`cat /proc/cvitek/vi_dbg`
|
||||
|
||||
> If `VIDevFPS` is `0`, NanoKVM is not receiving HDMI input. Check whether the host is outputting a video signal, whether the HDMI cable is damaged, or whether the Cube is an early version with poor connector contact.
|
||||
> If `VIDevFPS` is not `0` but `VIFPS` is `0`, NanoKVM failed to configure the HDMI parameters correctly. On Cube, unplug and reconnect HDMI to trigger auto-detection. On PCIe, click **Reset HDMI** under **Video**.
|
||||
> Check whether `VIInImgWidth` and `VIInImgHeight` match the actual HDMI resolution. If not, NanoKVM did not auto-detect the correct HDMI parameters, and you should manually set the resolution as described above.
|
||||
|
||||
### No Display After the Host Wakes from Sleep
|
||||
|
||||
1. Check whether you are using a cheap **DP-to-HDMI passive adapter**. These adapters often lack a proper wake-up mechanism and cannot notify NanoKVM when the display is restored.
|
||||
2. On the **PCIe version**, click **Reset HDMI** to force reacquisition of the video signal.
|
||||
3. The **Cube/Lite versions** do not have a reset function for this. Please switch to an **active DP adapter**.
|
||||
|
||||
### Severe Video Delay in a Local Network Environment
|
||||
|
||||
1. Try replacing the network switch or power supply.
|
||||
2. If the issue persists, please contact after-sales support.
|
||||
|
||||
### OLED Displays Information Normally, but the Web Page Cannot Be Opened
|
||||
|
||||
1. Please perform a forced application update.
|
||||
|
||||
### OLED Does Not Light Up
|
||||
|
||||
NanoKVM Full and PCIe versions include an OLED screen for displaying information such as the IP address. If the OLED does not light up, follow these steps:
|
||||
|
||||
1. Application version `2.1.4` added an OLED sleep function. Press the `BOOT` button to temporarily wake the OLED.
|
||||
2. If the STA LED is flashing abnormally, first check whether the system has booted normally. Refer to the section **STA LED (Blue LED) Not Flashing Normally** above.
|
||||
3. Try a forced update or reflash the system.
|
||||
|
||||
### About Memory
|
||||
|
||||
1. The total memory (RAM) space of NanoKVM is 256MB, with a dedicated ion memory area used for video image processing. The memory viewed in user space will be less than 256MB.
|
||||
2. Firmware versions lower than 1.3.0 reserve only 128MB of memory for user space. All images from version 1.3.0 and later increase the memory size to 158MB, which is beneficial for Tailscale to run for long periods. Users in need should update the image according to the steps [here].
|
||||
3. Enable "Memory Optimization" in the settings.
|
||||
1. NanoKVM has a total of **256MB RAM**. Part of it is reserved as a dedicated **ION memory area** for video/image processing, so the memory visible in user space will be less than 256MB.
|
||||
2. Firmware versions earlier than `1.3.0` reserve only **128MB** for user space. All images from version `1.3.0` onward increase user-space memory to **158MB**, which is better for long-term Tailscale usage. If needed, please update the image according to the instructions [here](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/system/flashing.html).
|
||||
3. Enable **Memory Optimization** in Settings.
|
||||
|
||||
### Host Abnormal Restart
|
||||
+ In the early beta version, when the Full NanoKVM ATX board is connected to the host's RESET pin, the host may restart when the NanoKVM is rebooted. Please disconnect the RESET jumper or contact customer service to purchase stable version accessories.
|
||||
### Host Reboots Unexpectedly
|
||||
|
||||
### Current Backflow
|
||||
+ The early beta version of the Full NanoKVM has a current backflow issue: When the host is powered off and the USB has no power output, current will flow back into the host when connecting the auxiliary power supply.
|
||||
1. It is recommended to set the USB to remain powered after the host is shut down.
|
||||
2. For Full version users: Use a soldering iron to disconnect the 5V resistor or header short-circuit at the indicated position in the image below, supplying power only through the auxiliary power port.
|
||||
|
||||
- In early internal test versions, if the **Full NanoKVM ATX board** is connected to the host's **RESET** pin, rebooting NanoKVM may also reboot the host. Please disconnect the RESET jumper or contact customer service to obtain stable-version accessories.
|
||||
|
||||
### Reverse Current / Backfeeding
|
||||
|
||||
- Early internal test versions of **Full NanoKVM** have a reverse-current issue: when the host is powered off and USB no longer provides power, connecting auxiliary power may feed current back into the host.
|
||||
|
||||
1. It is recommended to configure the host so that USB remains powered after shutdown.
|
||||
2. For **Full version** users: use a soldering iron to disconnect the 5V resistor or the shorted header at the location shown below, and power the unit only through the auxiliary power port.
|
||||
|
||||
|
||||
|
||||
### Try Power Cycling to Solve Unknown Issues
|
||||
|
||||
### If there are network disconnections or other abnormal situations during the update, it may lead to a failed update. Please refer to the following solutions:
|
||||
### If the Update Fails Due to Network Disconnection or Other Abnormal Conditions During the Update Process
|
||||
|
||||
1. Refer to [here](https://wiki.sipeed.com/hardware/zh/kvm/NanoKVM/system/updating.html#%E8%8E%B7%E5%8F%96-IP) to connect the development board.
|
||||
2. Execute `rm -r /kvmapp && cp -r /root/old/ / && mv /old/kvmapp && reboot` to restore the previous version.
|
||||
3. Manually force the update using the method outlined above.
|
||||
1. Refer to [this page](https://wiki.sipeed.com/hardware/en/kvm/NanoKVM/system/updating.html#%E8%8E%B7%E5%8F%96-IP) to connect to the development board.
|
||||
2. Run the following command to restore the previous version:
|
||||
|
||||
`rm -r /kvmapp && cp -r /root/old/ / && mv /old/kvmapp && reboot`
|
||||
|
||||
3. Manually perform a forced update using the method described at the top of this page.
|
||||
4. Reflash the system.
|
||||
|
||||
### If the Above Methods Do Not Resolve the Issue, Please Describe Your Model and Problems Encountered in the Forum, GitHub, or QQ Group. We Will Respond Patiently.
|
||||
+ When providing feedback, please specify the version of your NanoKVM, the environment in which you are using it (motherboard model, system name, etc.), and the system configuration (e.g., image version 1.4.0; application version 2.2.5; H264; 1080P; high quality; frame rate 30). This information will help us reproduce and resolve the issue.
|
||||
+ If there is a problem with no image display, please execute the following commands during the anomaly and paste the output logs into the issue:
|
||||
```shell
|
||||
cat /etc/kvm/hw
|
||||
cat /etc/kvm/hdmi_version
|
||||
cat /etc/kvm/hdmi_mode
|
||||
```
|
||||
+ Some issues require collecting runtime application logs. Please follow these steps:
|
||||
```shell
|
||||
# Enable SSH functionality in the web interface (Settings -> Devices -> SSH)
|
||||
# Log in to SSH using the password set in the web interface. If no password is set, the default password is root.
|
||||
ssh root@xxx.xxx.xxx.xxx
|
||||
# Change the log level: /etc/kvm/server.yaml -> logger -> level: info to debug
|
||||
vi /etc/kvm/server.yaml
|
||||
# Use ‘i’ to edit; use ‘Esc’ + :wq to exit
|
||||
# Restart the KVM service
|
||||
/etc/init.d/S95nanokvm restart
|
||||
# Copy the log
|
||||
```
|
||||
### If the Methods Above Do Not Solve the Problem
|
||||
|
||||
Please describe your NanoKVM model and the issue you encountered in the forum, GitHub, or QQ group. We will respond patiently.
|
||||
|
||||
- When reporting an issue, please specify:
|
||||
- your NanoKVM version,
|
||||
- the usage environment (motherboard model, operating system, etc.),
|
||||
- and the system configuration (for example: image version `1.4.0`, application version `2.2.5`, H264, 1080P, high quality, frame rate 30).
|
||||
|
||||
This information helps us reproduce and solve the issue more efficiently.
|
||||
|
||||
- If there is a **no image display** problem, please run the following commands while the issue is occurring and paste the output into the issue:
|
||||
|
||||
```shell
|
||||
cat /etc/kvm/hw
|
||||
cat /etc/kvm/hdmi_version
|
||||
cat /etc/kvm/hdmi_mode
|
||||
```
|
||||
|
||||
- Some issues require collecting runtime application logs. Please follow these steps:
|
||||
|
||||
```shell
|
||||
# Enable SSH in the web interface (Settings -> Devices -> SSH)
|
||||
# Log in via SSH using the password configured in the web interface.
|
||||
# If no password has been set, the default password is root.
|
||||
ssh root@xxx.xxx.xxx.xxx
|
||||
|
||||
# Change the log level in /etc/kvm/server.yaml:
|
||||
# logger -> level: change info to debug
|
||||
vi /etc/kvm/server.yaml
|
||||
|
||||
# Press 'i' to edit; use 'Esc' + :wq to save and exit
|
||||
|
||||
# Restart the KVM service
|
||||
/etc/init.d/S95nanokvm restart
|
||||
|
||||
# Copy the log
|
||||
```
|
||||
|
||||
## Feedback Methods
|
||||
|
||||
* MaixHub Forum: [https://maixhub.com/discussion/nanokvm](https://maixhub.com/discussion/nanokvm)
|
||||
* GitHub: [https://github.com/sipeed/NanoKVM](https://github.com/sipeed/NanoKVM)
|
||||
* QQ Group: 703230713
|
||||
- MaixHub Forum: https://maixhub.com/discussion/nanokvm
|
||||
- GitHub: https://github.com/sipeed/NanoKVM
|
||||
- QQ Group: 703230713
|
||||
|
||||
@@ -3,20 +3,28 @@ title: F&Q
|
||||
keywords: NanoKVM, Remote desktop, Lichee, PiKVM, RISCV, tool
|
||||
---
|
||||
|
||||
## 异常修复
|
||||
|
||||
|
||||
## 异常修复
|
||||
请查看右侧目录栏对应到自己对应的问题
|
||||
**以下解决方法都基于最新的应用，如果遇到问题，请先更新应用，若无法在网页端更新，请参照以下步骤完成强制更新：**
|
||||
1. 参考[这里](https://wiki.sipeed.com/hardware/zh/kvm/NanoKVM/system/updating.html#%E8%8E%B7%E5%8F%96-IP)连接开发板
|
||||
2. 执行：`python /etc/kvm/update-nanokvm.py`
|
||||
> 国外用户可能因为DNS原因下载失败，请参考[NanoKVM Cube/Lite/PCIe操作DNS的详细说明](https://wiki.sipeed.com/hardware/zh/kvm/NanoKVM/user_guide.html#设置DNS)添加推荐的DNS后再试
|
||||
> 早期版本应用可能不存在该脚本文件，请下载 https://github.com/sipeed/NanoKVM/blob/main/kvmapp/system/update-nanokvm.py 解压赋予执行权限后再试
|
||||
|
||||
### 关于密码
|
||||
|
||||
1. 更新至 2.1.5 版本应用后，若之前没有设置过网页密码，登录后会提示修改密码，修改密码时，后台的`root`密码也会同步修改成网页密码，若之前已经修改过网页密码，后台`root`密码不会主动修改，请在终端使用`passwd`或网页设置中点击重置密码以修改;
|
||||
2. 应用版本大于 2.1.5 时，若忘记密码，可以按下机身`BOOT`按键10s以上（NanoKVM-Cube的BOOT按键位于USB-HID接口右边，PCIe版本BOOT按键可在面板上找到，较老版本的NanoKVM Full可能没有在对应位置开孔，需要拆机操作），详细操作指引请参考[重置密码](https://wiki.sipeed.com/hardware/zh/kvm/NanoKVM/reset.html)
|
||||
### 关于网页密码和ssh密码如何重置
|
||||
#### 默认密码
|
||||
- **网页端：** `账号`/`密码` - `admin`/`admin`
|
||||
- **ssh ：** `账号`/`密码` - `root`/`root`
|
||||
#### 更改密码
|
||||
|
||||
1. 版本2.1.5 之后，若之前没有设置过网页密码，登录后会提示修改密码，修改密码后，SSH端的`root`密码也会同步修改成网页密码;
|
||||
2. 版本2.1.5 之后，若忘记密码，可以按下机身`BOOT`按键10s以上（NanoKVM-Cube的BOOT按键位于USB-HID接口右边，PCIe版本BOOT按键可在面板上找到，较老版本的NanoKVM Full可能没有在对应位置开孔，需要拆机操作）
|
||||
3. 若长按无法重置密码，可能是应用版本小于 2.1.5 ，参考[这里](https://wiki.sipeed.com/hardware/zh/kvm/NanoKVM/system/flashing.html)重新烧录镜像，注意，重烧镜像后会丢失所有配置信息。
|
||||
|
||||
|
||||
### HID键鼠不工作
|
||||
1. 使用网页中 "重置HID" 功能
|
||||
2. 部分主机系统对USB键鼠要求较高，需要使用“仅HID”模式，该模式下USB仅模拟键鼠设备，请通过网页鼠标图标中切换该模式
|
||||
@@ -26,31 +34,32 @@ keywords: NanoKVM, Remote desktop, Lichee, PiKVM, RISCV, tool
|
||||
### BIOS 不识别HID键鼠
|
||||
1. 部分主机系统对USB键鼠要求较高，需要使用“仅HID”模式，该模式下USB仅模拟支持BIOS的键鼠设备，请通过网页鼠标图标中切换该模式
|
||||
2. 使用网页中 "重置HID" 功能
|
||||
3. dell部分机型由于主板驱动兼容性非常差，bios端可能无法识别。暂时无法解决。
|
||||
|
||||
### 非英文键盘键位错误
|
||||
+ 键盘的键盘布局需要在被控主机系统设置中修改，以Ubuntu+修改法语键盘为例：
|
||||
设置->键盘->输入源->‘+’->添加->搜索"French"，添加
|
||||
|
||||
### STA LED 无法正常闪烁
|
||||
|
||||
STA灯用于指示NanoKVM的运行状态，正常工作时，STA灯在不规律闪烁，当STA灯出现长亮/长灭或者 规律性间断熄灭时认为NanoKVM出现故障
|
||||
1. 上电后 STA LED 规律性间断熄灭：系统未检测到TF卡中的系统，请检查TF卡是否正确插入，重新烧录TF镜像
|
||||
2. STA LED 长时间熄灭：一般在无供电情况下导致，请查看电源状况
|
||||
### STA LED（蓝灯）无法正常闪烁
|
||||
STA灯用于指示NanoKVM的运行状态，STA灯在，当STA灯出现长亮/长灭或者 规律性间断熄灭时认为NanoKVM出现故障
|
||||
- **正常工作** : 不规律闪烁
|
||||
- **上电后 STA LED 规律性间断熄灭** : 系统未检测到TF卡中的系统，请检查TF卡是否正确插入，重新烧录TF镜像
|
||||
- **长时间熄灭** : 一般在无供电情况下导致，请查看电源状况
|
||||
|
||||
> 若仅使用 USB-HID 供电，在电脑关机时可能会断开USB电源，请参考相关资料，在BIOS中设置USB常供电，或使用辅助供电。
|
||||
> 当不慎接入非常规电源后，NanoKVM 可能会烧坏，也会导致 STA LED 熄灭
|
||||
|
||||
3. STA LED 长时间亮起，不闪烁：NanoKVM 正式系统和应用一般不会出现该情况，若在NanoKVM系统内配置其他自定义功能，有概率导致系统卡死，STA LED长亮，建议重新烧录镜像
|
||||
- **长时间亮起，不闪烁** : NanoKVM 正式系统和应用一般不会出现该情况，若在NanoKVM系统内配置其他自定义功能，有概率导致系统卡死，STA LED长亮，建议重新烧录镜像
|
||||
|
||||
### 无法获取IP地址
|
||||
|
||||
1. Lite用户首先检查有无插卡, Lite 版本默认不带卡出货,需用户自备TF卡,按照[此处](https://wiki.sipeed.com/hardware/zh/kvm/NanoKVM/system/flashing.html)的说明烧卡后重试;
|
||||
2. 检查网络交换机是否支持100M, 部分新交换机不支持100M的连接, 请更换交换机后重试
|
||||
3. NanoKVM Cube（包括NanoKVM Full 和 NanoKVM Lite）在接入少数电源/HDMI时会导致无法获取IP，请进行以下确认：
|
||||
- Lite用户首先检查有无插卡, Lite 版本默认不带卡出货,需用户自备TF卡,按照[此处](https://wiki.sipeed.com/hardware/zh/kvm/NanoKVM/system/flashing.html)的说明烧卡后重试;
|
||||
- NanoKVM Cube（包括NanoKVM Full 和 NanoKVM Lite）在接入少数电源/HDMI时会导致无法获取IP，请进行以下确认：
|
||||
> 拔出所有接口，使用充电宝供电，接入网线，查看是否能获取IP
|
||||
> 若可以获取IP，插入HDMI/电脑USB查看IP是否存在
|
||||
> 若仅充电宝供电时IP存在，插入HDMI/电脑USB后IP消失则确认出现了该问题，请联系客服购买隔离器以解决
|
||||
|
||||
- 检查网络交换机是否支持100M, 部分新交换机不支持100M的连接, 请更换交换机后重试
|
||||
|
||||
### 无法通过 DHCP 获取 IP 且显示为 192.168.70.70
|
||||
|
||||
可参考[静态IP地址修复](https://wiki.sipeed.com/hardware/zh/kvm/NanoKVM/static_ip_fix.html)。
|
||||
@@ -59,29 +68,10 @@ keywords: NanoKVM, Remote desktop, Lichee, PiKVM, RISCV, tool
|
||||
|
||||
#### 默认分辨率错误
|
||||
NanoKVM仅支持1080P分辨率，但主机有概率输出了1080P以上规格的画面，推荐修改默认EDID来解决该问题，在此之前请在网页中升级到最新的APP（2.3.2以上）
|
||||
> 使用 Cube/Lite 版本时，必须现场操作。修改后请重新上电以应用新配置，否则可能导致 HDMI 采集异常。
|
||||
进入网页终端，执行命令：`/kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin`, Cube/Lite需要确认现场操作
|
||||
``` shell
|
||||
## PCIe版本 正常烧录输出：
|
||||
# /kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin
|
||||
Chip Version: LT6911UXC
|
||||
Product Version : PCIE_A
|
||||
|
||||
=========================================================
|
||||
Incorrect EDID may cause issues such as
|
||||
inability to display images, please modify with caution
|
||||
=========================================================
|
||||
|
||||
EDID data loaded successfully from /kvmapp/system/tool/E21_NanoKVM.bin
|
||||
Writing EDID....
|
||||
EDID write completed
|
||||
Reading EDID...
|
||||
EDID data verified successfully
|
||||
|
||||
=========================================================
|
||||
✅ EDID update successful!
|
||||
=========================================================
|
||||
|
||||
##### Cube 版本
|
||||
必须现场操作。修改后请重新上电以应用新配置，否则可能导致 HDMI 采集异常。
|
||||
进入网页终端，执行命令：`/kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin`
|
||||
```shell
|
||||
## Cube/Lite 正常烧录输出：
|
||||
# /kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin
|
||||
Chip Version: LT6911UXC
|
||||
@@ -113,6 +103,31 @@ EDID data verified successfully
|
||||
✅ EDID update successful!
|
||||
Please manually power cycle the device to apply changes.
|
||||
=========================================================
|
||||
```
|
||||
##### PCIE 版本
|
||||
修改后请重新上电以应用新配置，否则可能导致 HDMI 采集异常。
|
||||
进入网页终端，执行命令：`/kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin`
|
||||
``` shell
|
||||
## PCIe版本 正常烧录输出：
|
||||
# /kvmapp/system/tool/nanokvm_update_edid /kvmapp/system/tool/E21_NanoKVM.bin
|
||||
Chip Version: LT6911UXC
|
||||
Product Version : PCIE_A
|
||||
|
||||
=========================================================
|
||||
Incorrect EDID may cause issues such as
|
||||
inability to display images, please modify with caution
|
||||
=========================================================
|
||||
|
||||
EDID data loaded successfully from /kvmapp/system/tool/E21_NanoKVM.bin
|
||||
Writing EDID....
|
||||
EDID write completed
|
||||
Reading EDID...
|
||||
EDID data verified successfully
|
||||
|
||||
=========================================================
|
||||
✅ EDID update successful!
|
||||
=========================================================
|
||||
|
||||
```
|
||||
|
||||
#### 其他问题
|
||||
@@ -125,7 +140,7 @@ Please manually power cycle the device to apply changes.
|
||||
6. 早期内测版 Full NanoKVM 使用普通排线连接 HDMI 采集板，可能因接触不良导致检测不到 HDMI 信号，可按下图所示重新连接排线，或联系客服购买专用排线
|
||||
|
||||
7. 尝试重启解决：在网页终端中执行`reboot`
|
||||
8. 若上述方式无法锁定问题，请在网页终端中执行`cat /proc/cvitek/vi_dbg`
|
||||
8. **若上述方式无法锁定问题**，请在网页终端中执行`cat /proc/cvitek/vi_dbg`
|
||||
> 若 `VIDevFPS` 为0，则认为NanoKVM无法获取到HDMI输入，排查以下问题：主机是否输出视频信号、HDMI线缆损坏、Cube是否为早期版本，存在接触不良的情况
|
||||
> 若 `VIDevFPS` 非0 、`VIFPS` 为0 ，则认为NanoKVM没有正确配置HDMI参数，Cube可以重新插拔HDMI重新自动获取，PCIe可点击`视频`下`重置HDMI`自动获取
|
||||
> 查看 `VIInImgWidth` 和 `VIInImgHeight`与实际HDMI分辨率是否一致，若不同，则认为NanoKVM没有自动获取到正确的HDMI参数，按照第4点手动配置分辨率参数
|
||||
@@ -197,4 +212,4 @@ Please manually power cycle the device to apply changes.
|
||||
|
||||
* MaixHub 论坛：https://maixhub.com/discussion/nanokvm
|
||||
* GitHub ：https://github.com/sipeed/NanoKVM
|
||||
* QQ 群: 703230713
|
||||
* QQ 群: 703230713
|
||||
|
||||
Reference in New Issue
Block a user