You are not logged in.
Hello All,
I use Psensor, a common temperature monitoring device, and this morning when I booted normally, it only displays CPU temp and usage. Before it'd include all that plus CPU fan speed, MoBo and RAM temperatures as well. I could never get it to work for my GPU (nVidia card) but that's okay.
So, what happened to make my sensors suddenly stop working? I literally did nothing out of the ordinary. It's probably just a result of a "pacman -Syu" which I guess just says, "Welcome to Arch Linux!" but does anyone have any better ideas than just giving up?
The good news is, it seems to tax my computer a lot less to only have to deal with CPU temp monitoring.
I also found out that my CPU's thermal threshold is higher than the factory standard which finally explains what AMD meant by Black Edition processor. That's an extra 8 degrees, is what that is!
Last edited by MutantJohn (2013-04-14 00:30:24)
Offline
I had a similar problem after updating to systemd 201-1 yesterday. I saw that my lm_sensors.service was started, but loading of modules had failed. I made the module load at boot via a config file, but that's only a workaround I guess, not a solution.
Details:
I checked the status of lm_sensors.service
$ systemctl status lm_sensors.service
lm_sensors.service - Initialize hardware monitoring sensors
Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled)
Active: active (exited) since Sa 2013-04-13 11:59:48 CEST; 3h 55min ago
Process: 360 ExecStart=/usr/bin/sensors -s (code=exited, status=0/SUCCESS)
Process: 348 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE)
So modprobe couldn't load the modules (status=1/FAILURE). I looked into /etc/conf.d/lm_sensors for the module names(s), found it87 in my case. lsmod didn't show it, so it wasn't loaded. I loaded it manually with "# modprobe it87" and got my sensor output back. To make it load at boot I put a line with the module name into /etc/modules-load.d/lm_sensors.conf.
It works now, but the question remains why the autoloading suddenly fails.
Last edited by Sanne (2013-04-13 15:52:36)
If our currency were not money but appreciation and acknowledgement for what we do for others, for the community, for the benefit of all, we would have paradise on earth.
Offline
+1 here, modprobing it87 fixes the issue...
Offline
https://bugs.freedesktop.org/show_bug.cgi?id=63477
removing comments from /etc/conf.d/lm_sensors will help
Offline
I just checked this and also had the failure. Removing comments and restarting the service solved the issue. What's weird, though, is that sensors worked fine despite the failure. That is, it still gave me the output it usually does:
$ systemctl status lm_sensors.service
lm_sensors.service - Initialize hardware monitoring sensors
Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled)
Active: active (exited) since Gwe 2013-04-12 21:43:11 BST; 1 day 1h ago
Process: 889 ExecStart=/usr/bin/sensors -s (code=exited, status=0/SUCCESS)
Process: 872 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE)
$ sensors
thinkpad-isa-0000
Adapter: ISA adapter
fan1: 567 RPM
temp1: +51.0°C
temp2: +0.0°C
temp3: +51.0°C
temp4: +0.0°C
temp5: +0.0°C
temp6: +0.0°C
temp7: +25.0°C
temp8: +0.0°C
acpitz-virtual-0
Adapter: Virtual device
temp1: +51.0°C (crit = +100.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +51.0°C (high = +86.0°C, crit = +100.0°C)
Core 0: +51.0°C (high = +86.0°C, crit = +100.0°C)
Core 1: +47.0°C (high = +86.0°C, crit = +100.0°C)
And after removing the comments:
# systemctl status lm_sensors.service
lm_sensors.service - Initialize hardware monitoring sensors
Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled)
Active: active (exited) since Sad 2013-04-13 23:39:27 BST; 16s ago
Process: 6016 ExecStop=/sbin/modprobe -qabr $BUS_MODULES $HWMON_MODULES (code=exited, status=0/SUCCESS)
Process: 6026 ExecStart=/usr/bin/sensors -s (code=exited, status=0/SUCCESS)
Process: 6023 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=0/SUCCESS)
Ebr 13 23:39:27 MyComputer systemd[1]: Started Initialize hardware monitoring sensors.
# sensors
thinkpad-isa-0000
Adapter: ISA adapter
fan1: 567 RPM
temp1: +48.0°C
temp2: +0.0°C
temp3: +48.0°C
temp4: +0.0°C
temp5: +0.0°C
temp6: +0.0°C
temp7: +25.0°C
temp8: +0.0°C
acpitz-virtual-0
Adapter: Virtual device
temp1: +48.0°C (crit = +100.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +50.0°C (high = +86.0°C, crit = +100.0°C)
Core 0: +50.0°C (high = +86.0°C, crit = +100.0°C)
Core 1: +47.0°C (high = +86.0°C, crit = +100.0°C)
The only things I have in the config file are:
HWMON_MODULES="coretemp"
MODULE_0=coretemp
Maybe that gets loaded by default or something anyway? (I guess my hardware isn't very supported by what's available.)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
I removed the comments too and yes, the service is running as per usual. Thank you guys so much. I was worried that no one was going to answer this and all I could think was, I'm not the only nerd obsessed with monitoring temperatures.
I'll mark the thread as solved now.
Offline