FW-7541D wrong temperature

esquire1968

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: -1

I 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

doktornotor

This is FreeBSD, not Linux.

esquire1968

Thx! An what should I do now …

doktornotor

If it doesn't work with one of the options in System > Advanced > Miscellaneous > Thermal Sensors then probably nothing.

esquire1968

I tried both possibilities. Same result 9 degrees …

whosmatt

@esquire1968:

I tried both possibilities. Same result 9 degrees …

I'd just ignore it.

stephenw10

Hmm, that should work with the Intel on-die sensor. That's an Atom D525 right?

Steve

lra

@stephenw10:

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

stephenw10

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

esquire1968

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

stephenw10

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

esquire1968

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

stephenw10

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

esquire1968

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

stephenw10

???

Yeah, what's going on there… Are you sure it's actually a D525?

Steve

esquire1968

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

cpu.JPG_thumb
sensors3.conf.txt
readme.txt

lra

@esquire1968:

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.

esquire1968

Is it possible to run lm-sensor on FreeBSD/pfSense?

Thomas

stephenw10

No, there is no lmsensors in FreeBSD.

The closest thing is mbmon.
You would have to manually install that though

Steve

esquire1968

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