root@np2:~# opkg list-installed | grep sensor
libsensors5 - 3.6.0-r1
lm-sensors - 3.6.0-r1
lm-sensors-detect - 3.6.0-r1
root@np2:~# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
root@np2:~#
Hi,
I did this, please correct me if I did it in not correct way:
root@np2:~# sensors -u
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
root@np2:~#
root@np2:~# sensors-detect
# sensors-detect version 3.6.0
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
# Kernel: 6.6.44 aarch64
# Cannot show processor info on aarch64 architecture.
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
failed to find a module named cpuid
Failed to load module cpuid.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 16h thermal sensors... No
AMD Family 17h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Hygon Family 18h thermal sensors... No
Intel digital thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
Intel 5500/5520/X58 thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Sorry, no supported PCI bus adapters found.
Next adapter: rk3x-i2c (i2c-0)
Do you want to scan it? (YES/no/selectively):
Next adapter: rk3x-i2c (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: rk3x-i2c (i2c-6)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x51
Handled by driver `rtc-hym8563' (built-in), chip type `hym8563'
(note: this is probably NOT a sensor chip!)
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.
root@np2:~#
I noted that eth0 (RTL8211F Gigabit Ethernet) is not working properly with VLAN configuration.
Maybe I have some error in the configuration, or there is some bug.
Not all VLANs related eth0 are created (created are first 3 VLANs, 4 VLANS are missing).
VID
eth0
eth2
eth1
br-eth
200
u
u
u
201
t
t
t
202
t
t
t
203
t
t
t
204
t
t
t
205
t
t
t
206
t
t
t
207
t
t
t
100
t
t
101
t
t
103
t
t
1500
t
t
root@np2:~# cat /etc/config/network
...
config device
option name 'eth0'
option macaddr 'b2:be:02:75:52:f1'
config device
option name 'eth2'
option macaddr 'b2:be:02:75:52:f1'
config device
option name 'eth1'
option macaddr 'b2:be:02:75:52:f0'
...
config device
option name 'br-eth'
option type 'bridge'
option igmp_snooping '1'
option vlan_filtering '1'
option bridge_empty '1'
list ports 'eth0'
list ports 'eth1'
list ports 'eth2'
...
config bridge-vlan
option device 'br-eth'
option vlan '200'
list ports 'eth0:u*'
list ports 'eth2:u*'
config bridge-vlan
option device 'br-eth'
option vlan '201'
list ports 'eth0:t'
list ports 'eth2:t'
config bridge-vlan
option device 'br-eth'
option vlan '202'
list ports 'eth0:t'
list ports 'eth2:t'
config bridge-vlan
option device 'br-eth'
option vlan '203'
list ports 'eth0:t'
list ports 'eth2:t'
config bridge-vlan
option device 'br-eth'
option vlan '204'
list ports 'eth0:t'
list ports 'eth2:t'
config bridge-vlan
option device 'br-eth'
option vlan '205'
list ports 'eth0:t'
list ports 'eth2:t'
config bridge-vlan
option device 'br-eth'
option vlan '206'
list ports 'eth0:t'
list ports 'eth2:t'
config bridge-vlan
option device 'br-eth'
option vlan '207'
list ports 'eth0:t'
list ports 'eth2:t'
config bridge-vlan
option device 'br-eth'
option vlan '100'
list ports 'eth1:t'
config bridge-vlan
option device 'br-eth'
option vlan '101'
list ports 'eth1:t'
config bridge-vlan
option device 'br-eth'
option vlan '103'
list ports 'eth1:t'
config bridge-vlan
option device 'br-eth'
option vlan '1500'
list ports 'eth1:t'
...
root@np2:~#
I feel strange that I never heard from people using those multi-port x86 mini PC having such random NIC mapping issue (also didn't heard the same thing for R5S), why is this only happening on R6S?