What does the acpitz-virtual sensor output refer to?
The acpitz refers to the 'ACPI thermal zone'. There was some discussion about renaming the thermal zones on the lm-sensors mailing list:
We could probably update the code so that the labels default to the ACPI thermal zone names. Sometimes these names are useful... but
From the same ...
iwlwifi_1-virtual-0 is the wireless adapter and pch_cannonlake-virtual-0 is the platform control hub. PCHs tend to run hotter than CPUs. According to these threads issues don't occur until you exceed around 80C, so at 62C that seems fine.
"iwlwifi_1-virtual-0" refers to a small M.2 form factor Intel wireless module (card) which should be replaceable. If you look on the back of your motherboard, there is a silver rectangular box where the wifi antennas connect to. This houses the physical wireless module inside, it is not a virtual device. On some boards the wifi card is exposed ...
I've found this page http://www.parhelia.ch/blog/statics/k3_keys.html (archived) explaining vast majority of SMC keys.
As for your question, I believe that TA0P and TA0p is the same thing. A0 means ambient sensor #0 and p means proximity.
TC-- are sensors for CPU/logic board.
Latest D means CPU die (sensor), and H refers to heatsink.
Using sensors-detect helped me finding the problem: The module it87 wasn't loaded. So I ran modprobe it87 which resulted in
ERROR: could not insert 'it87': Device or resource busy
Finally this link helped: I edited /etc/default/grub and added acpi_enforce_resources=lax to GRUB_CMDLINE_LINUX:
Then executed ...
It can be different for different hardware combinations. Might be best to look at your BIOS/EFI for it's sensor info (it should be correct), and try comparing those to the output from sensors.
The "Adapter: Virtual device" I'm not sure, looks similar to cpu or gpu cores.
"coretemp-isa-0000" with it's 4 cores looks like a 4 core cpu.
Last one "it8728-isa-...
Install "sensors" package.
Run "sensors-detect" to genereate the basic configuration.
TIP: Answer "yes" to everything!
Open a terminal and run "watch -n 1 sensors"!
!!!!EXTRA!!!! - Integrate with KDE/konsole:
Open a konsole and follow "Settings" -> "Configure Konsole ..." and uncheck "Use current window size on next startup."
TIP: To set an appropriate ...
The program only displays what the hardware reports, it's perfectly reliable.
Rapid changes in CPU temperature are to be expected with modern CPUs. They're aggressively adjusting their clock speeds to achieve top performance within design constraints. For example if only one core is under high load, the CPU will boost that core's clock knowing that its ...
I feel silly, should've investigated more. Here is the answer just incase I mess this up or anyone else has the same problem. Also, many thanks to @Fiisch for advice and pointing me in the right direction.
When starting fancontrol via #service fancontrol start or #fancontrol, the errors of /usr/sbin/fancontrol are not printed. Due to motherboard limitations,...
I had the same problem. The way that I found to read the CPU voltage was using cpu-x, an open source program.
This program may need a few libraries to work. In my case I needed to install libcpuid which i didn't find in the main repository, so I installed from the source.
To install libcpuid:
git clone https://github.com/anrieff/libcpuid.git
You can redirect the output of the sensors command to a file using the >> operator of the shell:
sensors >> */your/file/here*
The >> operator redirects standard output of a command to a file so in this case it will write the output of sensors to the file you name. One second is pretty frequent, so you'...