plugout.net

Hi team,

do you know https://github.com/groeck/lm-sensors ? Do you use on our boxes with fvdw-sl firmware ?

Thanks in advance !

Best regards,

No, some are part of the kernel setup but this package we did not include.

Hi fvdw,

could you implement this in fvdw-sl firmware. It Will be amazing to know CPU's temperatura.

Thanks !!!

Best regards,

I compiled the package, the 5big1 kernel has the required configuration enabbles

The package requires Perl, so you need to instalkl the fvdw-sl addon containing Perl. (see download section of the forum how to install addons)

The file addon-lm-sensor-17jul18-archive.tar attched to thios post must be installed in the fvdw/addons folder

To do that put in the fvdw/addons folder and connect via ssh go to /direct-usb/fvdw/addons folder and extract the archive

Code: Select all

cd /direct-usb/fvdw/addons
tar -xvf addon-lm-sensor-17jul18-archive.tar

The second file "sensors3.zip" contains the default configuration file coming with the package, you need to put it /etc folder

I did not test the package so hopefully this info is enough to get to work, let us know your results ;)

Hi fvdw,

i've not seen perl addon, could you tell me where it is ?

Thanks in advance !

Best regards,

Hi fvdw,

sorry for my last message. I've found perl addon in Logitech Media Server add-on.

Thanks in advance !

Best regards,

Hi fvdw,

the output of sensors-detect and sensors

Code: Select all

root@Osiris:/direct-usb/fvdw/addons/sbin # ./sensors-detect
# sensors-detect revision $Revision$
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
# Kernel: 3.14.2 armv5tel
Use of uninitialized value in concatenation (.) or string at ./sensors-detect line 3122.
Use of uninitialized value in concatenation (.) or string at ./sensors-detect line 3122.
Use of uninitialized value in concatenation (.) or string at ./sensors-detect line 3122.
# Processor: Feroceon rev 0 (v5l) (//)

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):
modprobe: module 'cpuid' not found
Module cpuid loaded successfully.
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
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: mv64xxx_i2c adapter (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Handled by driver `at24' (built-in), chip type `24c08'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver `dummy' (built-in), chip type `dummy'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x52
Handled by driver `dummy' (built-in), chip type `dummy'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x53
Handled by driver `dummy' (built-in), chip type `dummy'
    (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
http://www.lm-sensors.org/wiki/Devices for driver status.
root@Osiris:/direct-usb/fvdw/addons/sbin # sensors
g762-i2c-0-3e
Adapter: mv64xxx_i2c adapter
fan1:           0 RPM  (div = 8)  ALARM


Thanks in advance !

Best regards,