4.4.97-1-ARCH - no sensors recognised on Zyxel NSA310

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

4.4.97-1-ARCH - no sensors recognised on Zyxel NSA310

Postby arti74 » Wed Apr 25, 2018 4:48 pm

Hello users
The logs:
Code: Select all
# sensors-detect
# sensors-detect revision $Revision$
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
# Kernel: 4.4.97-1-ARCH armv5tel
Use of uninitialized value in concatenation (.) or string at /usr/bin/sensors-detect line 2867.
Use of uninitialized value in concatenation (.) or string at /usr/bin/sensors-detect line 2867.
Use of uninitialized value in concatenation (.) or string at /usr/bin/sensors-detect line 2867.
# Processor: Feroceon 88FR131 rev 1 (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: FATAL: Module cpuid not found in directory /lib/modules/4.4.97-1-ARCH
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 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

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   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 0x2e
Probing for `Myson MTP008'...                               No
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM96080'...             No
Probing for `TI / National Semiconductor ADC128D818'...     No
Probing for `National Semiconductor LM85'...                No
Probing for `National Semiconductor LM96000 or PC8374L'...  No
Probing for `Analog Devices ADM1027'...                     No
Probing for `Analog Devices ADT7460 or ADT7463'...          No
Probing for `SMSC EMC6D100 or EMC6D101'...                  No
Probing for `SMSC EMC6D102'...                              No
Probing for `SMSC EMC6D103'...                              No
Probing for `SMSC EMC6D103S or EMC2300'...                  No
Probing for `SMSC EMC6W201'...                              No
Probing for `Winbond WPCD377I'...                           No
Probing for `Analog Devices ADT7467 or ADT7468'...          No
Probing for `Analog Devices ADT7470'...                     No
Probing for `Analog Devices ADT7473'...                     No
Probing for `Analog Devices ADT7475'...                     No
Probing for `Analog Devices ADT7476'...                     Success!
    (confidence 7, driver `adt7475')
Probing for `Analog Devices ADT7490'...                     No
Probing for `Andigilog aSC7611'...                          No
Probing for `Andigilog aSC7621'...                          No
Probing for `National Semiconductor LM87'...                No
Probing for `Analog Devices ADM1024'...                     No
Probing for `National Semiconductor LM93'...                No
Probing for `National Semiconductor LM94 or LM96194'...     No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83791D'...                            No
Probing for `Winbond W83792D'...                            No
Probing for `Winbond W83793R/G'...                          No
Probing for `Nuvoton W83795G/ADG'...                        No
Probing for `Nuvoton NCT7802Y'...                           No
Probing for `Nuvoton NCT7904D'...                           No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Winbond W83L786NR/NG/R/G'...                   No
Probing for `Winbond W83L785TS-S'...                        No
Probing for `Analog Devices ADM9240'...                     No
Probing for `Dallas Semiconductor DS1780'...                No
Probing for `National Semiconductor LM81'...                No
Probing for `Analog Devices ADM1026'...                     No
Probing for `Analog Devices ADM1025'...                     No
Probing for `Maxim MAX6639'...                              No
Probing for `Texas Instruments AMC6821'...                  No
Probing for `Analog Devices ADM1029'...                     No
Probing for `Analog Devices ADM1030'...                     No
Probing for `Analog Devices ADM1031'...                     No
Probing for `Analog Devices ADM1022'...                     No
Probing for `Texas Instruments THMC50'...                   No
Probing for `Analog Devices ADM1028'...                     No
Probing for `Texas Instruments THMC51'...                   No
Probing for `ITE IT8712F'...                                No
Probing for `SMSC DME1737'...                               No
Probing for `SMSC SCH5027D-NW'...                           No
Probing for `SMSC EMC2103'...                               No
Probing for `Fintek F75373S/SG'...                          No
Probing for `Fintek F75375S/SP'...                          No
Probing for `Fintek F75387SG/RG'...                         No
Probing for `Winbond W83791SD'...                           No


Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `adt7475':
  * Bus `mv64xxx_i2c adapter'
    Busdriver `UNKNOWN', I2C address 0x2e
    Chip `Analog Devices ADT7476' (confidence: 7)

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
Job for lm_sensors.service failed because the control process exited with error code.
See "systemctl status lm_sensors.service" and "journalctl -xe" for details.

Code: Select all
sudo systemctl status lm_sensors.service
* lm_sensors.service - Initialize hardware monitoring sensors
   Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2018-04-25 18:37:55 CEST; 21s ago
  Process: 450 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE)
  Process: 445 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE)
 Main PID: 450 (code=exited, status=1/FAILURE)

Apr 25 18:37:55 alarm systemd[1]: Starting Initialize hardware monitoring sensors...
Apr 25 18:37:55 alarm sensors[450]: No sensors found!
Apr 25 18:37:55 alarm sensors[450]: Make sure you loaded all the kernel drivers you need.
Apr 25 18:37:55 alarm sensors[450]: Try sensors-detect to find out which these are.
Apr 25 18:37:55 alarm systemd[1]: lm_sensors.service: Main process exited, code=exited, status=1/FAILURE
Apr 25 18:37:55 alarm systemd[1]: lm_sensors.service: Failed with result 'exit-code'.
Apr 25 18:37:55 alarm systemd[1]: Failed to start Initialize hardware monitoring sensors.

after restart:
Code: Select all
# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

Anybody has some ideas what to do to make it work?
Thank you in advance.
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: 4.4.97-1-ARCH - no sensors recognised on Zyxel NSA310

Postby arti74 » Mon May 21, 2018 7:45 pm

All my problems with the NSA310 solved with great contribution of @summers, @bodhi, and finally @moonman!
First upgrade to the new dt-kernel and uboot - check this thread viewtopic.php?f=15&t=12732, some problems with environment and migration to the new kernel/disk/uboot solved here https://forum.doozan.com/read.php?3,58144,page=1
And finally contact with @moonman (thank you!) who implemented the required driver for my sensor in the new 4.16.9-2-ARCH kernel:
modprobe i2c_mv64xxx adt7475 hwmon_vid i2c-dev
Code: Select all
lsmod
Module                  Size  Used by
adt7475                17772  0
hwmon_vid               2046  1 adt7475
hwmon                   7939  1 adt7475
marvell_cesa           30938  0
i2c_mv64xxx             8014  0
ip_tables              11115  0
x_tables               15664  1 ip_tables
ipv6                  396408  34
ses                     6935  0
enclosure               6801  1 ses

Code: Select all
(…)
Next adapter: mv64xxx_i2c adapter (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x2e
Handled by driver `adt7475' (already loaded), chip type `adt7476'

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `adt7475':
  * Bus `mv64xxx_i2c adapter'
    Busdriver `i2c_mv64xxx', I2C address 0x2e
    Chip `adt7476' (confidence: 6)

Driver `to-be-written':
  * ISA bus, address 0xca0
    Chip `IPMI BMC KCS' (confidence: 4)
  * ISA bus, address 0xca8
    Chip `IPMI BMC SMIC' (confidence: 4)

Note: there is no driver for IPMI BMC KCS yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):

Code: Select all
sensors
adt7476-i2c-0-2e
Adapter: mv64xxx_i2c adapter
in0:          +1.82 V  (min =  +0.00 V, max =  +3.31 V)
Vcore:        +1.08 V  (min =  +0.00 V, max =  +2.99 V)
+3.3V:        +3.24 V  (min =  +2.96 V, max =  +3.61 V)
+5V:          +5.12 V  (min =  +4.48 V, max =  +5.50 V)
+12V:        +11.92 V  (min =  +0.00 V, max = +15.69 V)
fan1:        4990 RPM  (min =    0 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:           0 RPM  (min =    0 RPM)
temp1:        +36.5 C  (low  = -127.0 C, high = +127.0 C)
                       (crit = +100.0 C, hyst = +96.0 C)
M/B Temp:     +37.5 C  (low  = -127.0 C, high = +127.0 C)
                       (crit = +100.0 C, hyst = +96.0 C)
temp3:        +43.0 C  (low  = -127.0 C, high = +127.0 C)
                       (crit = +100.0 C, hyst = +96.0 C)
cpu0_vid:    +0.000 V

:D
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: 4.4.97-1-ARCH - no sensors recognised on Zyxel NSA310

Postby summers » Tue May 22, 2018 7:55 am

Interesting. Guess that was the one device you found on i2c that had info in many registers. I didn't have a similar device on my nsa325 - so guess that chip was just used on the nsa310 - guess I should have looked when I had the box open.

I remember trying lm-sensors a few years back - it didn't find anything on my nsa325 - so I deinstalled it ....
summers
 
Posts: 923
Joined: Sat Sep 06, 2014 12:56 pm


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 5 guests