FW-7541D wrong temperature
-
Hi!
My pfSense replies a wrong temperature!
sysctl -a | grep temperature
dev.cpu.3.temperature: 9.0C
dev.cpu.2.temperature: 9.0C
dev.cpu.1.temperature: -1
dev.cpu.0.temperature: -1I contact the support team of Lannerinc and their recommendation was to install "lm-sensors" an sent me a config file "sensors3.conf". Unfortunatly I can't download the package from the site http://www.lm-sensors.org"!
Any Ideas? Do you kwow, where I can download it? I tried "apt-get lm-sensors" - "apt-get not found".
Thx.
Thomas
-
This is FreeBSD, not Linux.
-
Thx! An what should I do now …
-
If it doesn't work with one of the options in System > Advanced > Miscellaneous > Thermal Sensors then probably nothing.
-
I tried both possibilities. Same result 9 degrees …
-
-
Hmm, that should work with the Intel on-die sensor. That's an Atom D525 right?
Steve
-
Hmm, that should work with the Intel on-die sensor. That's an Atom D525 right?
Steve
On Linux the FW-7541D (Atom D525 with w83627dhg chip) uses the "w83627ehf" kernel module for sensor info. Possibly a clue for the FreeBSD case.
Lonnie
-
Mmm, lm-sensors uses the SuperIO chip but the Intel Coretemp driver reads from the in the on-die sensor via a CPU register. It should be reading those without a problem.
The fact it's only reading from 1 core seems suspicious. Like maybe it got a dead core or somehow a different CPU. The 7541had a number of variants but they all had the D525.
Perhaps you are running on a customised box OP?
Steve
-
The info from Lannerinc was to use 'lm-sensors' and they sent me a config file.
Do you knowe where I can download lm-sensors an how I can install it? www.lm-sensors.org is dead!
Thomas
-
You can't use lmsensors in FreeBSD, there's no port as far as I know.
There used to be an equivalent program or sorts, mbmon, but I think that too is obsolete these days.
It looks like you have either an odd cpu or more likely an odd BIOS that is returning the wrong values. Not much can be done I'm afraid.
Does it show correctly in the BIOS hardware health screen?
Steve
-
The Bios shows the right temperatures:
System Temperature: 50*C/122*F CPU Temperature: 38*C/100*F
The pfSense Dashboard shows 10*C!
No idea! :-\Thomas
-
What do see returned by:
sysctl dev.cpu
For reference:
dev.cpu.3.temperature: 52.0C dev.cpu.3.coretemp.throttle_log: 0 dev.cpu.3.coretemp.tjmax: 100.0C dev.cpu.3.coretemp.resolution: 1 dev.cpu.3.coretemp.delta: 48 dev.cpu.3.cx_method: C1/hlt dev.cpu.3.cx_usage_counters: 16826 dev.cpu.3.cx_usage: 100.00% last 8616us dev.cpu.3.cx_lowest: C1 dev.cpu.3.cx_supported: C1/1/0 dev.cpu.3.%parent: acpi0 dev.cpu.3.%pnpinfo: _HID=none _UID=0 dev.cpu.3.%location: handle=\_PR_.P004 dev.cpu.3.%driver: cpu dev.cpu.3.%desc: ACPI CPU dev.cpu.2.temperature: 52.0C dev.cpu.2.coretemp.throttle_log: 0 dev.cpu.2.coretemp.tjmax: 100.0C dev.cpu.2.coretemp.resolution: 1 dev.cpu.2.coretemp.delta: 48 dev.cpu.2.cx_method: C1/hlt dev.cpu.2.cx_usage_counters: 12970 dev.cpu.2.cx_usage: 100.00% last 17us dev.cpu.2.cx_lowest: C1 dev.cpu.2.cx_supported: C1/1/0 dev.cpu.2.%parent: acpi0 dev.cpu.2.%pnpinfo: _HID=none _UID=0 dev.cpu.2.%location: handle=\_PR_.P003 dev.cpu.2.%driver: cpu dev.cpu.2.%desc: ACPI CPU dev.cpu.1.temperature: 53.0C dev.cpu.1.coretemp.throttle_log: 0 dev.cpu.1.coretemp.tjmax: 100.0C dev.cpu.1.coretemp.resolution: 1 dev.cpu.1.coretemp.delta: 47 dev.cpu.1.cx_method: C1/hlt dev.cpu.1.cx_usage_counters: 15998 dev.cpu.1.cx_usage: 100.00% last 11984us dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_supported: C1/1/0 dev.cpu.1.%parent: acpi0 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%location: handle=\_PR_.P002 dev.cpu.1.%driver: cpu dev.cpu.1.%desc: ACPI CPU dev.cpu.0.temperature: 53.0C dev.cpu.0.coretemp.throttle_log: 0 dev.cpu.0.coretemp.tjmax: 100.0C dev.cpu.0.coretemp.resolution: 1 dev.cpu.0.coretemp.delta: 47 dev.cpu.0.cx_method: C1/hlt dev.cpu.0.cx_usage_counters: 23983 dev.cpu.0.cx_usage: 100.00% last 7565us dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_supported: C1/1/0 dev.cpu.0.%parent: acpi0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%location: handle=\_PR_.P001 dev.cpu.0.%driver: cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.%parent:
Steve
-
dev.cpu.3.temperature: 9.0C dev.cpu.3.coretemp.throttle_log: 0 dev.cpu.3.coretemp.tjmax: 100.0C dev.cpu.3.coretemp.resolution: 1 dev.cpu.3.coretemp.delta: 91 dev.cpu.3.cx_usage: 100.00% last 4183us dev.cpu.3.cx_lowest: C1 dev.cpu.3.cx_supported: C1/1/0 dev.cpu.3.%parent: acpi0 dev.cpu.3.%pnpinfo: _HID=none _UID=0 dev.cpu.3.%location: handle=\_PR_.P004 dev.cpu.3.%driver: cpu dev.cpu.3.%desc: ACPI CPU dev.cpu.2.temperature: 9.0C dev.cpu.2.coretemp.throttle_log: 0 dev.cpu.2.coretemp.tjmax: 100.0C dev.cpu.2.coretemp.resolution: 1 dev.cpu.2.coretemp.delta: 91 dev.cpu.2.cx_usage: 100.00% last 179us dev.cpu.2.cx_lowest: C1 dev.cpu.2.cx_supported: C1/1/0 dev.cpu.2.%parent: acpi0 dev.cpu.2.%pnpinfo: _HID=none _UID=0 dev.cpu.2.%location: handle=\_PR_.P003 dev.cpu.2.%driver: cpu dev.cpu.2.%desc: ACPI CPU dev.cpu.1.temperature: -1 dev.cpu.1.coretemp.throttle_log: 0 dev.cpu.1.coretemp.tjmax: -1 dev.cpu.1.coretemp.resolution: -1 dev.cpu.1.coretemp.delta: -1 dev.cpu.1.cx_usage: 100.00% last 4288us dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_supported: C1/1/0 dev.cpu.1.%parent: acpi0 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%location: handle=\_PR_.P002 dev.cpu.1.%driver: cpu dev.cpu.1.%desc: ACPI CPU dev.cpu.0.temperature: -1 dev.cpu.0.coretemp.throttle_log: 0 dev.cpu.0.coretemp.tjmax: -1 dev.cpu.0.coretemp.resolution: -1 dev.cpu.0.coretemp.delta: -1 dev.cpu.0.cx_usage: 100.00% last 193us dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_supported: C1/1/0 dev.cpu.0.%parent: acpi0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%location: handle=\_PR_.P001 dev.cpu.0.%driver: cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.%parent:
Strange, isn't it …
Thomas
-
???
Yeah, what's going on there… Are you sure it's actually a D525?
Steve
-
I hope so …
CPU Type: Intel(R) Atom(TM) CPU D525 @ 1.80GHz 4 CPUs: 1 package(s) x 2 core(s) x 2 HTT threads
Lanner's recommendation was to install lm-sensors and the sent me a config file for this (see sensors3.conf).
Thomas
-
I hope so …
CPU Type: Intel(R) Atom(TM) CPU D525 @ 1.80GHz 4 CPUs: 1 package(s) x 2 core(s) x 2 HTT threads
Lanner's recommendation was to install lm-sensors and the sent me a config file for this (see sensors3.conf).
Thomas
I also have a FW-7541D, but running Linux, and the "coretemp" module does not work properly with Linux on that box, which I presume is basically what FreeBSD/pfSense uses. With "coretemp" I get:
coretemp-isa-0000 Adapter: ISA adapter Core 0: +8.0 C (crit = +100.0 C) Core 1: N/A (crit = +100.0 C)
It would seem using lm-sensors is the only way to to get the temperature, which does work properly.
-
Is it possible to run lm-sensor on FreeBSD/pfSense?
Thomas
-
No, there is no lmsensors in FreeBSD.
The closest thing is mbmon.
You would have to manually install that thoughSteve
-
Do you thing, that mbmon will work. How can I read then the temperature - only via ssh or also on the dashboard?
How can I install mbmon?
Thomas
-
You can try:
pkg add http://pkg.freebsd.org/FreeBSD:10:amd64/release_3/All/xmbmon-205_14.txz
then
rehash
then
mbmon -D
But installing FreeBSD packages isn't recommended.
Steve
-
I there any risk if i install the package?
How can I deinstall the package restless?
Thomas
-
I installed it on my D525 box here and there was no issue. It did't find any hardware though.
You can remove it with 'pkg delete X' if you need to.
You could just carry on without knowing the exact temperature though. It's probably not important. ;)
Steve
-
mbmon -D
Probe Request: none >>> Testing Reg's at ISA-IO <<< [ISA Port IO-Base:0x290] Probing Winbond/Asus/LM78/79 chip: CR40:0xFF, CR41:0xFF, CR42:0xFF, CR43:0xFF CR44:0xFF, CR45:0xFF, CR46:0xFF, CR47:0xFF CR48:0xFF, CR49:0xFF, CR4A:0xFF, CR4B:0xFF CR4C:0xFF, CR4D:0xFF, CR4E:0xFF, CR4F:0xFF CR56:0xFF, CR58:0xFF, CR59:0xFF, CR5D:0xFF CR3E:0xFF, CR13:0xFF, CR17:0xFF, CRA1:0xFF CR20:0xFF, CR22:0xFF, CR23:0xFF, CR24:0xFF CR27:0xFF, CR29:0xFF, CR2A:0xFF, CR2B:0xFF No Hardware Monitor found!! InitMBInfo: No such file or directory
And now?
Thomas
-
Use a thermometer? :P
I'm out of suggestions at this point.
Steve