Skip to content

Instantly share code, notes, and snippets.

@Cloud-Mak
Created October 23, 2024 18:59
Show Gist options
  • Save Cloud-Mak/eae99615d65b9174ec4d4cec3b459a44 to your computer and use it in GitHub Desktop.
Save Cloud-Mak/eae99615d65b9174ec4d4cec3b459a44 to your computer and use it in GitHub Desktop.
sensors-detect-azom laptop
makrand@zmint:~$ sudo sensors-detect
# sensors-detect version 3.6.0
# System: Notebook X170KM-G [Not Applicable] (laptop)
# Kernel: 6.8.0-47-generic x86_64
# Processor: Intel(R) Core(TM) i9-10850K CPU @ 3.60GHz (6/165/5)
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): y
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
Hygon Family 18h thermal 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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... Yes
Found unknown chip with ID 0x5570
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 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): y
Found unknown SMBus adapter 8086:43a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Next adapter: SMBus I801 adapter at efa0 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x4e
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... No
Probing for `Maxim MAX1617A'... No
Probing for `Maxim MAX1668'... No
Probing for `Maxim MAX1805'... No
Probing for `Maxim MAX1989'... No
Probing for `Maxim MAX6642'... No
Probing for `Maxim MAX6655/MAX6656'... No
Probing for `TI THMC10'... No
Probing for `National Semiconductor LM84'... No
Probing for `Genesys Logic GL523SM'... No
Probing for `Onsemi MC1066'... No
Probing for `Maxim MAX1618'... No
Probing for `Maxim MAX1619'... No
Probing for `National Semiconductor LM82/LM83'... No
Probing for `Maxim MAX6654'... No
Probing for `Maxim MAX6690'... No
Probing for `Maxim MAX6659'... No
Probing for `Maxim MAX6647'... No
Probing for `Maxim MAX6680/MAX6681'... No
Probing for `Maxim MAX6695/MAX6696'... No
Probing for `Texas Instruments TMP400'... No
Probing for `Texas Instruments TMP411C'... No
Probing for `Texas Instruments TMP421'... No
Probing for `Texas Instruments TMP422'... No
Probing for `Texas Instruments TMP435'... No
Probing for `Texas Instruments TMP441'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `National Semiconductor LM95234'... No
Probing for `National Semiconductor LM64'... No
Probing for `National Semiconductor LM73'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Probing for `Fintek F75121R/F75122R/RG (VID+GPIO)'... No
Probing for `Fintek F75111R/RG/N (GPIO)'... No
Probing for `ITE IT8201R/IT8203R/IT8206R/IT8266R'... No
Client found at address 0x4f
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `Maxim MAX6642'... No
Probing for `Texas Instruments TMP421'... No
Probing for `Texas Instruments TMP422'... No
Probing for `Texas Instruments TMP435'... No
Probing for `Texas Instruments TMP441'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Client found at address 0x50
Handled by driver `ee1004' (already loaded), chip type `ee1004'
(note: this is probably NOT a sensor chip!)
Client found at address 0x52
Handled by driver `ee1004' (already loaded), chip type `ee1004'
(note: this is probably NOT a sensor chip!)
Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Client at address 0x2c can not be probed - unload all client drivers first!
Next adapter: Synopsys DesignWare I2C adapter (i2c-2)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: Synopsys DesignWare I2C adapter (i2c-3)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: Synopsys DesignWare I2C adapter (i2c-4)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-5)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 3 at 1:00.0 (i2c-6)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 4 at 1:00.0 (i2c-7)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-8)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 6 at 1:00.0 (i2c-9)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 7 at 1:00.0 (i2c-10)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: NVIDIA i2c adapter 8 at 1:00.0 (i2c-11)
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)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)y
Successful!
Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.
Unloading cpuid... OK
makrand@zmint:~$ sudo systemctl status lm-sensors.service
● lm-sensors.service - Initialize hardware monitoring sensors
Loaded: loaded (/lib/systemd/system/lm-sensors.service; enabled; vendor preset: enabled)
Active: active (exited) since Wed 2024-10-23 22:02:17 IST; 2h 20min ago
Process: 1048 ExecStart=/usr/bin/sensors -s (code=exited, status=0/SUCCESS)
Process: 1115 ExecStart=/usr/bin/sensors (code=exited, status=0/SUCCESS)
Main PID: 1115 (code=exited, status=0/SUCCESS)
CPU: 7ms
Oct 23 22:02:17 zmint sensors[1115]: Adapter: Virtual device
Oct 23 22:02:17 zmint sensors[1115]: temp1: N/A
Oct 23 22:02:17 zmint sensors[1115]: nvme-pci-0200
Oct 23 22:02:17 zmint sensors[1115]: Adapter: PCI adapter
Oct 23 22:02:17 zmint sensors[1115]: Composite: +30.9°C (low = -5.2°C, high = +79.8°C)
Oct 23 22:02:17 zmint sensors[1115]: (crit = +84.8°C)
Oct 23 22:02:17 zmint sensors[1115]: acpitz-acpi-0
Oct 23 22:02:17 zmint sensors[1115]: Adapter: ACPI interface
Oct 23 22:02:17 zmint sensors[1115]: temp1: +43.0°C
Oct 23 22:02:17 zmint systemd[1]: Finished Initialize hardware monitoring sensors.
makrand@zmint:~$ sudo systemctl status kmod
kmod.service kmod-static-nodes.service
makrand@zmint:~$ sudo systemctl status kmod
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
Active: active (exited) since Wed 2024-10-23 22:02:15 IST; 2h 20min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 500 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
Main PID: 500 (code=exited, status=0/SUCCESS)
CPU: 11ms
Notice: journal has been rotated since unit was started, output may be incomplete.
makrand@zmint:~$ /etc/init.d/kmod start
Starting kmod (via systemctl): kmod.service.
makrand@zmint:~$ sudo systemctl status kmod
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
Active: active (exited) since Wed 2024-10-23 22:02:15 IST; 2h 21min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 500 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
Main PID: 500 (code=exited, status=0/SUCCESS)
CPU: 11ms
Notice: journal has been rotated since unit was started, output may be incomplete.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment