After replacing my motherboard I try to get Psensor working correctly but still I cannot get the right temperature for my CPUcore temp, it's always -127C degrees. I installed lm-sensors and everything it's needed to check the temp, so after running:
sudo sensors-detectI answered yes to everything and it found:
Driver `f71882fg':
* ISA bus, address 0x295
Chip `Fintek F71882FG/F71883FG Super IO Sensors' (confidence: 9)I ran:
sudo service kmod startwhen I do:
sudo modprobe f71882fgI get:
modprobe: ERROR: could not insert 'f71882fg': Device or resource busythe output of dmesg | tail says:
[47593.565779] f71882fg: Found f71882fg chip at 0x290, revision 32
[47593.565857] ACPI Warning: SystemIO range 0x00000290-0x00000297 conflicts with OpRegion 0x00000295-0x00000296 (\IP__) (20140424/utaddress-258)
[47593.565870] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driverWhat would be my further actions?
2 Answers
As Oli says, you only need the coretemp module to read Intel CPU core temperature.
I have a similar problem with my w83667hg hardware monitor driver. The workaround is to add acpi_enforce_resources=lax to the kernel command line. To that end
edit
/etc/default/gruband insertacpi_enforce_resources=laxinto the parameter string ofGRUB_CMDLINE_LINUX, e. g.GRUB_CMDLINE_LINUX='acpi_enforce_resources=lax'then run
update-gruband reboot.
I'd skip lm-sensors and just read from /sys/class/thermal/thermal_zone0/temp. This should be automatically registered for an ACPI chip. The unit is millidegrees Celsius.
$ cat /sys/class/thermal/thermal_zone0/temp
47000There may be many thermal_zoneN devices. In my experience, the CPU is usually the first (and one for each core) but I'm not sure I'd depend on that always being the case.
For other devices that aren't registered through the thermal sysfs API, you would need lm-sensors or something similar.