$ sudo sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Acer Predator G9-791 [V1.06] (laptop)
# Board: Acer Challenger_SLS
# Kernel: 4.4.0-31-generic x86_64
# Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (6/94/3)

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):
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 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'...               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 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):
Found unknown SMBus adapter 8086:a123 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

Next adapter: i915 gmbus dpc (i2c-0)
Do you want to scan it? (yes/NO/selectively):

Next adapter: i915 gmbus dpb (i2c-1)
Do you want to scan it? (yes/NO/selectively):

Next adapter: i915 gmbus dpd (i2c-2)
Do you want to scan it? (yes/NO/selectively):

Next adapter: DPDDC-A (i2c-3)
Do you want to scan it? (yes/NO/selectively):

Next adapter: DPDDC-C (i2c-4)
Do you want to scan it? (yes/NO/selectively):

Next adapter: DPDDC-D (i2c-5)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-bus-0000 (i2c-6)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-bus-0001 (i2c-7)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-bus-0002 (i2c-8)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-bus-0003 (i2c-9)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-aux-0003 (i2c-10)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-bus-0004 (i2c-11)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-aux-0004 (i2c-12)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-bus-0005 (i2c-13)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-aux-0005 (i2c-14)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-bus-0006 (i2c-15)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-aux-0006 (i2c-16)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-bus-0007 (i2c-17)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-aux-0007 (i2c-18)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-bus-0008 (i2c-19)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-aux-0008 (i2c-20)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-bus-0009 (i2c-21)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:01:00.0-aux-0009 (i2c-22)
Do you want to scan it? (yes/NO/selectively):

Next adapter: 0000:01:00.0 (i2c-23)
Do you want to scan it? (yes/NO/selectively):

Next adapter: Synopsys DesignWare I2C adapter (i2c-24)
Do you want to scan it? (YES/no/selectively):
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!


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)yes
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
===================================================================================

$ service kmod start
$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +46.0°C  (crit = +98.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +33.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:         +32.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:         +33.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:         +30.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:         +32.0°C  (high = +100.0°C, crit = +100.0°C)

===================================================================================

$ sudo pwmconfig
# pwmconfig revision 6243 (2014-03-20)
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed