|
| 1 | +# FAQ |
| 2 | + |
| 3 | +English Version | [中文版](./FAQ.md) |
| 4 | + |
| 5 | +## 1. Unable to connect to the network after configuring a custom network |
| 6 | + |
| 7 | +```sh |
| 8 | +# Remove the default route |
| 9 | +sudo ip route del default via 192.168.123.1 dev eth0 |
| 10 | +``` |
| 11 | + |
| 12 | + |
| 13 | +## 2. 'colcon build' shows system clock warning |
| 14 | + |
| 15 | +``` |
| 16 | +make[2]: warning: Clock skew detected. Your build may be incomplete. |
| 17 | +``` |
| 18 | + |
| 19 | +```sh |
| 20 | +# Check system time |
| 21 | +date |
| 22 | +``` |
| 23 | +If it shows 1970, it may be because the system cannot update the clock automatically due to no network connection. |
| 24 | + |
| 25 | +```sh |
| 26 | +# Remove default route |
| 27 | +sudo ip route del default via 192.168.123.1 dev eth0 |
| 28 | +``` |
| 29 | + |
| 30 | +Close and reopen the terminal. |
| 31 | +```sh |
| 32 | +# Check time synchronization status |
| 33 | +timedatectl status |
| 34 | +``` |
| 35 | + |
| 36 | +If the time is updated successfully, delete previous build/install/log files and rebuild: |
| 37 | +```sh |
| 38 | +# Make sure you are in the correct workspace |
| 39 | +rm -rf build install log |
| 40 | +colcon build |
| 41 | +``` |
| 42 | +The warning should no longer appear. |
| 43 | + |
| 44 | + |
| 45 | +## 3. not found |
| 46 | +``` |
| 47 | +ros2: command not found |
| 48 | +Package 'XXX' not found |
| 49 | +``` |
| 50 | +These issues usually occur when the correct setup files are not sourced. |
| 51 | + |
| 52 | + |
| 53 | + |
| 54 | +## 4. General ROS troubleshooting |
| 55 | + |
| 56 | +1. Close all terminals and open a new one. |
| 57 | +2. Delete `build`, `install`, `log` folders and rebuild: |
| 58 | + |
| 59 | +## 5. Network configuration issues |
| 60 | +```sh |
| 61 | +unitree@ubuntu:~$ sudo ifconfig wlan0 up |
| 62 | +# Error: SIOCSIFFLAGS: Operation not possible due to RF-kill |
| 63 | +``` |
| 64 | + |
| 65 | +Solution: |
| 66 | +```sh |
| 67 | +# Check RF-kill status |
| 68 | +unitree@ubuntu:~$ rfkill list |
| 69 | +# 0: phy0: Wireless LAN |
| 70 | +# Soft blocked: yes |
| 71 | +# Hard blocked: no |
| 72 | + |
| 73 | +unitree@ubuntu:~$ sudo rfkill unblock wifi |
| 74 | + |
| 75 | +# 再查看 |
| 76 | +unitree@ubuntu:~$ rfkill list |
| 77 | +# 0: phy0: Wireless LAN |
| 78 | +# Soft blocked: no |
| 79 | +# Hard blocked: no |
| 80 | + |
| 81 | +# 重新运行不再报错 |
| 82 | +unitree@ubuntu:~$ sudo ifconfig wlan0 up |
| 83 | +``` |
| 84 | + |
| 85 | +## 6. SSH works but VS Code Remote fails |
| 86 | +Make sure the Download Server has network access and the local network is working. |
| 87 | + |
| 88 | +If VS Code repeatedly asks for a password and shows: |
| 89 | +``` |
| 90 | +Failed to connect to the remote extension host server (Error: ExtensionInstallFailed(ExtensionInstallFailed("Error while installing extensions: getaddrinfo EAI_AGAIN marketplace.visualstudio.com\ngetaddrinfo EAI_AGAIN marketplace.visualstudio.com\n") |
| 91 | +``` |
| 92 | +This is a typical network issue where the Linux server cannot access `marketplace.visualstudio.com` due to DNS failure or timeout. |
| 93 | + |
| 94 | +Solution: |
| 95 | +1. Connect via SSH using Windows PowerShell or Linux terminal: |
| 96 | +```sh |
| 97 | + |
| 98 | +``` |
| 99 | + |
| 100 | +2. On the Linux server, check network: |
| 101 | +```sh |
| 102 | +unitree@ubuntu:~$ ping marketplace.visualstudio.com |
| 103 | +``` |
| 104 | +If it fails, the Linux server cannot reach the Internet. |
| 105 | + |
| 106 | +3. Check DNS configuration: |
| 107 | +```sh |
| 108 | +unitree@ubuntu:~$ cat /etc/resolv.conf |
| 109 | +``` |
| 110 | +If it shows something like: |
| 111 | +``` |
| 112 | +nameserver 127.0.0.53 |
| 113 | +search Huawei.Local |
| 114 | +``` |
| 115 | + |
| 116 | +Ubuntu is using `systemd-resolved` local DNS stub which cannot resolve external domains. |
| 117 | + |
| 118 | +4. Edit `resolved.conf`: |
| 119 | +```sh |
| 120 | +unitree@ubuntu:~$ sudo vim /etc/systemd/resolved.conf |
| 121 | +``` |
| 122 | + |
| 123 | +Uncomment or add: |
| 124 | +``` |
| 125 | +[Resolve] DNS=8.8.8.8 1.1.1.1 |
| 126 | +FallbackDNS=114.114.114.114 |
| 127 | +DNSStubListener=yes |
| 128 | +``` |
| 129 | +Save the file. |
| 130 | + |
| 131 | +5. Restart the DNS service: |
| 132 | +```sh |
| 133 | +unitree@ubuntu:~$ sudo systemctl restart systemd-resolved |
| 134 | +``` |
| 135 | + |
| 136 | +6. Verify DNS: |
| 137 | +```sh |
| 138 | +unitree@ubuntu:~$ systemd-resolve --status |
| 139 | +``` |
| 140 | + |
| 141 | +Should show: |
| 142 | +``` |
| 143 | +DNS Servers: 8.8.8.8 1.1.1.1 |
| 144 | +Fallback DNS Servers: 114.114.114.114 8.8.8.8 |
| 145 | +``` |
| 146 | +press `q` to exit. |
| 147 | + |
| 148 | +7. Test network connectivity: |
| 149 | + |
| 150 | +```sh |
| 151 | +unitree@ubuntu:~$ ping 8.8.8.8 |
| 152 | +unitree@ubuntu:~$ ping marketplace.visualstudio.com |
| 153 | +``` |
| 154 | +If successful, VS Code Remote SSH should now work properly. |
0 commit comments