I dabbled with Power Management on my HP dv6tqe laptop. Here's what I have been learning.
Preparing to monitor. Install the required monitors/sensors.
Install lm_sensors
lm_sensors installation
[mochapenguin@dv6tqe ~]$ sudo dnf install lm_sensors Last metadata expiration check: 2:27:57 ago on Sun Sep 11 01:35:12 2016. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: lm_sensors x86_64 3.4.0-4.fc24 fedora 145 k lm_sensors-libs x86_64 3.4.0-4.fc24 fedora 46 k Transaction Summary ================================================================================ Install 2 Packages Total download size: 191 k Installed size: 483 k Is this ok [y/N]: y Downloading Packages: (1/2): lm_sensors-libs-3.4.0-4.fc24.x86_64.rpm 407 kB/s | 46 kB 00:00 (2/2): lm_sensors-3.4.0-4.fc24.x86_64.rpm 988 kB/s | 145 kB 00:00 -------------------------------------------------------------------------------- Total 122 kB/s | 191 kB 00:01 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Installing : lm_sensors-libs-3.4.0-4.fc24.x86_64 1/2 Installing : lm_sensors-3.4.0-4.fc24.x86_64 2/2 Verifying : lm_sensors-3.4.0-4.fc24.x86_64 1/2 Verifying : lm_sensors-libs-3.4.0-4.fc24.x86_64 2/2 Installed: lm_sensors.x86_64 3.4.0-4.fc24 lm_sensors-libs.x86_64 3.4.0-4.fc24 Complete!
Run sensors-detect to prepare a configuration for your system.
[mochapenguin@dv6tqe ~]$ sudo sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Hewlett-Packard HP Pavilion dv6 Notebook PC [058D100000244720001620100] (laptop)
# Board: Hewlett-Packard 1657
# Kernel: 4.7.2-201.fc24.x86_64 x86_64
# Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (6/42/7)
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 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'... Yes
Found `ITE IT8518E Super IO'
(no support yet)
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):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)
Module i2c-dev loaded successfully.
Next adapter: i915 gmbus ssc (i2c-0)
Do you want to scan it? (yes/NO/selectively):
Next adapter: i915 gmbus vga (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: i915 gmbus panel (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: i915 gmbus dpb (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: i915 gmbus dpd (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: DPDDC-B (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: Radeon i2c bit bus 0x90 (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: Radeon i2c bit bus 0x91 (i2c-8)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: Radeon i2c bit bus 0x92 (i2c-9)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: Radeon i2c bit bus 0x93 (i2c-10)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: Radeon i2c bit bus 0x94 (i2c-11)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: Radeon i2c bit bus 0x95 (i2c-12)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: Radeon i2c bit bus 0x96 (i2c-13)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: Radeon i2c bit bus 0x97 (i2c-14)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: SMBus I801 adapter at 6040 (i2c-15)
Do you want to scan it? (YES/no/selectively): YES
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
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
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)
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): YES
Unloading i2c-dev... OKInstall hddtemp
[mochapenguin@dv6tqe ~]$ sudo dnf install hddtemp [sudo] password for mochapenguin: Last metadata expiration check: 2:52:34 ago on Sun Sep 11 01:35:12 2016. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: hddtemp x86_64 0.3-0.35.beta15.fc24 fedora 60 k Transaction Summary ================================================================================ Install 1 Package Total download size: 60 k Installed size: 134 k Is this ok [y/N]: y Downloading Packages: hddtemp-0.3-0.35.beta15.fc24.x86_64.rpm 355 kB/s | 60 kB 00:00 -------------------------------------------------------------------------------- Total 43 kB/s | 60 kB 00:01 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Installing : hddtemp-0.3-0.35.beta15.fc24.x86_64 1/1 Verifying : hddtemp-0.3-0.35.beta15.fc24.x86_64 1/1 Installed: hddtemp.x86_64 0.3-0.35.beta15.fc24 Complete!
Check out the sensors
[mochapenguin@dv6tqe ~]$ sensors acpitz-virtual-0 Adapter: Virtual device temp1: +47.0°C (crit = +99.0°C) radeon-pci-0100 Adapter: PCI adapter temp1: N/A (crit = +120.0°C, hyst = +90.0°C) coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +47.0°C (high = +86.0°C, crit = +100.0°C) Core 0: +47.0°C (high = +86.0°C, crit = +100.0°C) Core 1: +47.0°C (high = +86.0°C, crit = +100.0°C) Core 2: +46.0°C (high = +86.0°C, crit = +100.0°C) Core 3: +44.0°C (high = +86.0°C, crit = +100.0°C)
No comments:
Post a Comment