Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- bash-5.0$ sudo /usr/sbin/sensors-detect
- # sensors-detect revision $Revision$
- # Board: ASUSTeK COMPUTER INC. PRIME H270M-PLUS
- # Kernel: 4.19.19 x86_64
- # Processor: Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz (6/158/9)
- 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):
- 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... Success!
- (driver `coretemp')
- 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'... Yes
- Found `Nuvoton NCT6793D Super IO Sensors' Success!
- (address 0x290, driver `nct6775')
- 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): y
- 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):
- Using driver `i2c-i801' for device 0000:00:1f.4: Kaby Lake (PCH)
- Module i2c-dev loaded successfully.
- Next adapter: SMBus I801 adapter at f040 (i2c-0)
- Do you want to scan it? (YES/no/selectively):
- Client found at address 0x50
- Probing for `Analog Devices ADM1033'... No
- Probing for `Analog Devices ADM1034'... No
- Probing for `SPD EEPROM'... Yes
- (confidence 8, not a hardware monitoring chip)
- Probing for `EDID EEPROM'... No
- Next adapter: i915 gmbus dpc (i2c-1)
- Do you want to scan it? (yes/NO/selectively):
- Next adapter: i915 gmbus dpb (i2c-2)
- Do you want to scan it? (yes/NO/selectively): y
- Next adapter: i915 gmbus dpd (i2c-3)
- Do you want to scan it? (yes/NO/selectively): y
- Client found at address 0x4a
- Probing for `National Semiconductor LM75'... No
- Probing for `National Semiconductor LM75A'... No
- Probing for `Dallas Semiconductor DS75'... No
- Probing for `National Semiconductor LM77'... No
- Probing for `Analog Devices ADT7410/ADT7420'... No
- Probing for `Analog Devices ADT7411'... No
- Probing for `Maxim MAX6642'... No
- Probing for `Texas Instruments TMP435'... No
- Probing for `National Semiconductor LM73'... No
- Probing for `National Semiconductor LM92'... No
- Probing for `National Semiconductor LM76'... No
- Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
- Probing for `NXP/Philips SA56004'... No
- Client found at address 0x4b
- Probing for `National Semiconductor LM75'... No
- Probing for `National Semiconductor LM75A'... No
- Probing for `Dallas Semiconductor DS75'... No
- Probing for `National Semiconductor LM77'... No
- Probing for `Analog Devices ADT7410/ADT7420'... No
- Probing for `Analog Devices ADT7411'... No
- Probing for `Maxim MAX6642'... No
- Probing for `Texas Instruments TMP435'... No
- Probing for `National Semiconductor LM92'... No
- Probing for `National Semiconductor LM76'... No
- Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
- Probing for `NXP/Philips SA56004'... No
- Probing for `Analog Devices ADT7481'... No
- Next adapter: DPDDC-E (i2c-4)
- Do you want to scan it? (yes/NO/selectively): y
- Now follows a summary of the probes I have just done.
- Just press ENTER to continue:
- Driver `nct6775':
- * ISA bus, address 0x290
- Chip `Nuvoton NCT6793D Super IO Sensors' (confidence: 9)
- Driver `coretemp':
- * Chip `Intel digital thermal sensor' (confidence: 9)
- Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
- Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
- for initialization at boot time.
- You should now start the lm_sensors service to load the required
- kernel modules.
- Unloading i2c-dev... OK
- bash-5.0$ sudo /usr/sbin/sensors-detect
- # sensors-detect revision $Revision$
- # Board: ASUSTeK COMPUTER INC. PRIME H270M-PLUS
- # Kernel: 4.19.19 x86_64
- # Processor: Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz (6/158/9)
- 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):
- 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... Success!
- (driver `coretemp')
- 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'... Yes
- Found `Nuvoton NCT6793D Super IO Sensors' Success!
- (address 0x290, driver `nct6775')
- 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): y
- 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):
- Using driver `i2c-i801' for device 0000:00:1f.4: Kaby Lake (PCH)
- Module i2c-dev loaded successfully.
- Next adapter: SMBus I801 adapter at f040 (i2c-0)
- Do you want to scan it? (YES/no/selectively):
- Client found at address 0x50
- Probing for `Analog Devices ADM1033'... No
- Probing for `Analog Devices ADM1034'... No
- Probing for `SPD EEPROM'... Yes
- (confidence 8, not a hardware monitoring chip)
- Probing for `EDID EEPROM'... No
- Next adapter: i915 gmbus dpc (i2c-1)
- Do you want to scan it? (yes/NO/selectively): y
- Next adapter: i915 gmbus dpb (i2c-2)
- Do you want to scan it? (yes/NO/selectively): y
- Next adapter: i915 gmbus dpd (i2c-3)
- Do you want to scan it? (yes/NO/selectively): y
- Client found at address 0x4a
- Probing for `National Semiconductor LM75'... No
- Probing for `National Semiconductor LM75A'... No
- Probing for `Dallas Semiconductor DS75'... No
- Probing for `National Semiconductor LM77'... No
- Probing for `Analog Devices ADT7410/ADT7420'... No
- Probing for `Analog Devices ADT7411'... No
- Probing for `Maxim MAX6642'... No
- Probing for `Texas Instruments TMP435'... No
- Probing for `National Semiconductor LM73'... No
- Probing for `National Semiconductor LM92'... No
- Probing for `National Semiconductor LM76'... No
- Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
- Probing for `NXP/Philips SA56004'... No
- Client found at address 0x4b
- Probing for `National Semiconductor LM75'... No
- Probing for `National Semiconductor LM75A'... No
- Probing for `Dallas Semiconductor DS75'... No
- Probing for `National Semiconductor LM77'... No
- Probing for `Analog Devices ADT7410/ADT7420'... No
- Probing for `Analog Devices ADT7411'... No
- Probing for `Maxim MAX6642'... No
- Probing for `Texas Instruments TMP435'... No
- Probing for `National Semiconductor LM92'... No
- Probing for `National Semiconductor LM76'... No
- Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
- Probing for `NXP/Philips SA56004'... No
- Probing for `Analog Devices ADT7481'... No
- Next adapter: DPDDC-E (i2c-4)
- Do you want to scan it? (yes/NO/selectively): y
- Now follows a summary of the probes I have just done.
- Just press ENTER to continue:
- Driver `coretemp':
- * Chip `Intel digital thermal sensor' (confidence: 9)
- Driver `nct6775':
- * ISA bus, address 0x290
- Chip `Nuvoton NCT6793D Super IO Sensors' (confidence: 9)
- Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
- Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
- for initialization at boot time.
- You should now start the lm_sensors service to load the required
- kernel modules.
- Unloading i2c-dev... OK
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement