Difference between revisions of "Template:OfficialUbuntuCore"
(updated by API) |
(updated by API) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 31: | Line 31: | ||
eth1: 192.168.2.1<br/> | eth1: 192.168.2.1<br/> | ||
eth2: 192.168.3.1 (Note: if there are three network ports)<br/> | eth2: 192.168.3.1 (Note: if there are three network ports)<br/> | ||
| + | | NanoPi-R6C | ||
| + | | NanoPC-T6 | ||
| NanoPi-R5C = | | NanoPi-R5C = | ||
The other ethernet port are set up with static IP addresses, as follows:<br/> | The other ethernet port are set up with static IP addresses, as follows:<br/> | ||
| Line 92: | Line 94: | ||
| NanoPi-R2C | | NanoPi-R2C | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
| + | | NanoPi-R2S-Plus | ||
| NanoPi-R5C | | NanoPi-R5C | ||
| NanoPi-R5S | | NanoPi-R5S | ||
| + | | NanoPi-R6C | ||
| + | | NanoPC-T6 | ||
| NanoPi-R6S = | | NanoPi-R6S = | ||
====WiFi models supported==== | ====WiFi models supported==== | ||
=====M.2 WiFi Module===== | =====M.2 WiFi Module===== | ||
| − | * | + | * RTL8822CE |
=====Usb Dongle===== | =====Usb Dongle===== | ||
| + | * RTL8821CU (Vid: 0BDA, Pid: C811) (Test sample:TP-Link TL-WDN5200H) | ||
* RTL8812AU (Vid: 0BDA, Pid: 8812) | * RTL8812AU (Vid: 0BDA, Pid: 8812) | ||
| − | * MediaTek MT7662 (Vid: 0E8D, Pid: 7612) | + | * MediaTek MT7662 (Vid: 0E8D, Pid: 7612) (Test sample:COMFAST CF-WU782AC V2) |
| #default = | | #default = | ||
}} | }} | ||
| Line 115: | Line 121: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
| + | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
===Build kernel-header deb package=== | ===Build kernel-header deb package=== | ||
| Line 126: | Line 133: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
| + | | NanoPi-R2S-Plus | ||
| NanoPi-R5C | | NanoPi-R5C | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
| Line 181: | Line 189: | ||
echo eth2 > /sys/class/leds/lan2_led/device_name | echo eth2 > /sys/class/leds/lan2_led/device_name | ||
echo 1 > /sys/class/leds/lan2_led/link | echo 1 > /sys/class/leds/lan2_led/link | ||
| + | </syntaxhighlight> | ||
| + | | NanoPi-R6C = | ||
| + | ===Config status LEDs=== | ||
| + | First determine whether the system already exists the leds initialization service: | ||
| + | <syntaxhighlight lang="bash"> | ||
| + | sudo systemctl status leds | ||
| + | </syntaxhighlight> | ||
| + | If the leds service already exists, change the default behavior of the LEDs by editing the following file: | ||
| + | <syntaxhighlight lang="bash"> | ||
| + | /etc/init.d/leds.sh | ||
| + | </syntaxhighlight> | ||
| + | Since there is no leds service in the early firmware, you need to refer to the following guide to manually configure the LEDs. First, set the following kernel modules to be automatically loaded at boot:<br /> | ||
| + | <syntaxhighlight lang="bash"> | ||
| + | modprobe ledtrig-netdev | ||
| + | echo ledtrig-netdev > /etc/modules-load.d/ledtrig-netdev.conf | ||
| + | </syntaxhighlight> | ||
| + | Put the following into the autorun script to associate the status leds with the ethernet interface, and you can configure it to behave in other ways by referring to these content:<br /> | ||
| + | <syntaxhighlight lang="bash"> | ||
| + | echo netdev > /sys/class/leds/wan_led/trigger | ||
| + | echo eth0 > /sys/class/leds/wan_led/device_name | ||
| + | echo 1 > /sys/class/leds/wan_led/link | ||
| + | |||
| + | echo netdev > /sys/class/leds/lan1_led/trigger | ||
| + | echo eth1 > /sys/class/leds/lan1_led/device_name | ||
| + | echo 1 > /sys/class/leds/lan1_led/link | ||
| + | </syntaxhighlight> | ||
| + | The onboard LED1 can be configured as needed, the node is /sys/class/leds/usr_led. | ||
| + | | NanoPC-T6 = | ||
| + | ===Config status LEDs=== | ||
| + | First determine whether the system already exists the leds initialization service: | ||
| + | <syntaxhighlight lang="bash"> | ||
| + | sudo systemctl status leds | ||
| + | </syntaxhighlight> | ||
| + | If the leds service already exists, change the default behavior of the LEDs by editing the following file: | ||
| + | <syntaxhighlight lang="bash"> | ||
| + | /etc/init.d/leds.sh | ||
| + | </syntaxhighlight> | ||
| + | Since there is no leds service in the early firmware, you need to refer to the following guide to manually configure the LEDs. First, set the following kernel modules to be automatically loaded at boot:<br /> | ||
| + | <syntaxhighlight lang="bash"> | ||
| + | modprobe ledtrig-netdev | ||
| + | echo ledtrig-netdev > /etc/modules-load.d/ledtrig-netdev.conf | ||
| + | </syntaxhighlight> | ||
| + | Put the following into the autorun script to associate the status leds with the ethernet interface, and you can configure it to behave in other ways by referring to these content:<br /> | ||
| + | <syntaxhighlight lang="bash"> | ||
| + | echo netdev > /sys/class/leds/usr_led/trigger | ||
| + | echo eth0 > /sys/class/leds/usr_led/device_name | ||
| + | echo 1 > /sys/class/leds/usr_led/link | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| #default = | | #default = | ||
}} | }} | ||
Latest revision as of 10:53, 4 December 2023
Contents
1 Work with FriendlyCore
1.1 FriendlyCore User Account
- Non-root User:
User Name: pi Password: pi
- Root:
User Name: root Password: fa
1.2 Update Software Packages
$ sudo apt-get update
1.3 Setup Network Configurations
1.3.1 Set static IP address
By default "eth0" is assigned an IP address obtained via dhcp. If you want to change the setting you need to change the following file:
vi /etc/network/interfaces.d/eth0
For example if you want to assign a static IP to it you can run the following commands:
auto eth0
iface eth0 inet static
address 192.168.1.231
netmask 255.255.255.0
gateway 192.168.1.11.3.2 Set a DNS
You also need to modify the following file to add the DNS configuration:
vi /etc/systemd/resolved.conf
For example, set to 192.168.1.1:
[Resolve] DNS=192.168.1.1
Restart the systemd-resolved service with the following command:
sudo systemctl restart systemd-resolved.service sudo systemctl enable systemd-resolved.service
1.3.3 Set up to use another network interface
To change the setting of "eth1" you can add a new file similar to eth0's configuration file under the /etc/network/interfaces.d/ directory.
1.4 Setup Wi-Fi
First, use the following command to check if Network-Manager is installed on your system:
which nmcliIf you have installed it, refer to this link to connect to WiFi: Use NetworkManager to configure network settings, If you do not have Network-Manager installed on your system, please refer to the following method to configure WiFi,
By default the WiFi device is "wlan0". You need to create a configuration file under "/etc/network/interfaces.d/" for WiFi:
vi /etc/network/interfaces.d/wlan0
Here is a sample wlan0 file:
auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid YourWiFiESSID
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk YourWiFiPasswordPlease replace "YourWiFiESSID" and "YourWiFiPassword" with your WiFiESSID and password. After save and close the file you can connect to your WiFi source by running the following command:
sudo systemctl daemon-reload sudo systemctl restart networking
After you power on your board it will automatically connect to your WiFi source.
Please note that if you use one TF card to boot multiple boards the WiFi device name will likely be named to "wlan1", "wlan2" and etc. You can reset it to "wlan0" by deleting the contents of the following file and reboot your board:
/etc/udev/rules.d/70-persistent-net.rules
1.5 Install the kernel-header package
sudo dpkg -i /opt/linux-headers-*.deb
