Temperature Widget

m4f1050

Nope I was talking about the XTM5.
You can use the output of mbmon to drive the dashboard widget. We had a long thread up on this for 2.0.X, I'm sure a lot of it would be relevent here.
http://forum.pfsense.org/index.php/topic,39595.0.html

And here was my specific post:
http://forum.pfsense.org/index.php/topic,39595.msg204643.html#msg204643

Steve

Thanks! :) I "pkg_add -r mbmon" and at least I can run it in command line. So I have 3 different "temps" when I run mbmon…

Temp.= 47.0, 127.0, 79,0; Rot.= 0, 0, 0
Vcore = 1.49, 3.38; Volt. = 3.31, 4.95, 11.67, -3.06, -6.12

If -T3 is the CPU and that's in celcius I think I'm frying my CPU ATM!! But it's been running forever like this...?

EDIT 1:
Ok, T1 is my CPU temp, it went down to 46.0 when I put another fan to help the one I have temporarily. BTW I modified my functions.inc.php and I now have Temp in my GUI :D Thanks again Steve!

EDIT 2:
I changed the -I to -i to show integer (no .0 at the end)

rcfa

mbmon doesn't seem to work here
So I guess I'd need coretemp. Where can we get the required files for that (amd64/BSD 8.3)?

markuhde

@m4f1050:

If -T3 is the CPU and that's in celcius I think I'm frying my CPU ATM!! But it's been running forever like this…?

Even if it was 79, that's fine for most modern CPU's. My MacBook Pro runs about 50-60 in normal use and keeps the fan running about 2000 RPM, but doesn't start ramping up the fan speed until just under 80. Under load, it throttles the fan speed up and down to keep the CPU in the 80-90 range.

Depends on if its fahrenheit or celsius too, hehe.

I see that mbmon is getting much attention and currently we support coretemp and acpi.
The code generates a source indepent temperature array, so its possible to add mbmon to.
I will add it as a source. Its not much effort and then everyone is able to to query with his favorite toy in the BE ;)

–-

Maybe ill decide do a package too in the future, when i build up enough knowledge to do so, but lets keep the balls down for the moment :)
After all atm its just a neat patch which adds some sensors.

Steven posted a link to the coretemp modules here: http://files.pfsense.org/jimp/ko-8.1/amd64/coretemp.ko

markuhde

@ThorstenK:

Depends on if its fahrenheit or celsius too, hehe.

AFAIK, every single CPU on the market reads temperature in Celsius.

Yes, so im pretty sure that it wont be a good idea to modify the temp widgets code to print them in Fahrenheit or use that as a default. (see discussion above)
daplumpler: other People may get confused in the beginnings. I dont think we want this happening in such a critical area.

stephenw10

Here is the coretemp module from my FreeBSD install.
It's an i386 (32bit) module from FreeBSD 8.3 rel. As before:

@stephenw10:

Copy coretemp.ko into /boot/modules
Add```
coretemp_load="YES"

I don't have a 64bit install at the moment unfortunately.

Remove the .png extension.

Steve

coretemp.ko.png

m4f1050

@ThorstenK:

Depends on if its fahrenheit or celsius too, hehe.

I see that mbmon is getting much attention and currently we support coretemp and acpi.
The code generates a source indepent temperature array, so its possible to add mbmon to.
I will add it as a source. Its not much effort and then everyone is able to to query with his favorite toy in the BE ;)

–-

Maybe ill decide do a package too in the future, when i build up enough knowledge to do so, but lets keep the balls down for the moment :)
After all atm its just a neat patch which adds some sensors.

Steven posted a link to the coretemp modules here: http://files.pfsense.org/jimp/ko-8.1/amd64/coretemp.ko

From what I understand, my T1 is my CPU temp and my T3 is my chipset temp. I am guessing if it's 127.0 (always at that) that temp is not available. You can program it to check if it's 127.0 to NOT display it in the GUI… If they are interested in knowing all the temps and not just the CPU temp..

BTW I confirmed with my buddy's FB X500 with good fan that he is running T1=45C , T2=127C and T3=77C (~2C less, so I am good)

mmh. I dont think that we really want that. Maybe 127 is 1111111 and so some kind of magic value.
and "normally" such a high temperature isnt realistic to be ever shown.

Automatically deactivating a sensor just for convinience isnt a good idea in general.
It is better to implement a configuration screen (see notes about planned pach 2) which lets the user the decision to select the sensors on a per system base.

Ill push the implementation to patch 2.

rcfa

@ThorstenK:

Steven posted a link to the coretemp modules here: http://files.pfsense.org/jimp/ko-8.1/amd64/coretemp.ko

Yep, but that's for BSD 8.1, but we're running 8.3, AFAIK that's not compatible.

Thats right - Please check the last post of Steven. He posted the mod as attachment.

rcfa

@ThorstenK:

Thats right - Please check the last post of Steven. He posted the mod as attachment.

Maybe I'm dense, or you're talking about a different Steven than I think you're talking about, but all I can find is a 32-bit version for 8.3, which won't work because I'm running a 64-bit install, and a 64-bit version for 8.1, which won't work because I'm on 8.3

This is right; StevenW10 runs on 32 bit. So when your runnig a 64 bit system it might be best to create a custom kernel or to fetch the bins from a 64bit freeBSD8.3 install or use a 32bit system if everything else fails.
Hm- Idea: Its good when skilled people solve problems - When your done you maybe decide to extend the pfsense Installer to check for the availability of the kmod. This way this problem will be solved for the future :)
Edit: Sorry stephenW10 for misspelling.

stephenw10

It just requires one of you guys to download the 64bit FreeBSD 8.3 iso and extract the module from it. I'll do it tonight when it doesn't count towards my bandwidth cap if no one's done it by then.

Steve

Hi - since im on gprs right now, i cant do it till eom ;( so maybe you want to try:

ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/8.3/

hanD!

m4f1050

@ThorstenK:

mmh. I dont think that we really want that. Maybe 127 is 1111111 and so some kind of magic value.
and "normally" such a high temperature isnt realistic to be ever shown.

Automatically deactivating a sensor just for convinience isnt a good idea in general.
It is better to implement a configuration screen (see notes about planned pach 2) which lets the user the decision to select the sensors on a per system base.

Ill push the implementation to patch 2.

Yeah, that's definitely a better approach. Let the user pick. If you can't have user interaction then filtering the 127 would work I think.

mmh. it may take a week for patch two i think.
I wouldnt like it very much, but meanwhile -
What about for a config tunable, which we set for filtering out sensors with 127 degrees ?
This would be fast to implement and seems like a good compromise, what do you think ?

m4f1050

@ThorstenK:

mmh. it may take a week for patch two i think.
I wouldnt like it very much, but meanwhile -
What about for a config tunable, which we set for filtering out sensors with 127 degrees ?
This would be fast to implement and seems like a good compromise, what do you think ?

I agree, I mean, if it's there (and working) why not use it? We need to add mbmon also. I have the 32-bit version, I think the 64-bit CPUs prob. already have working coretemp32 or coretemp64?

From what i know its already available, but we have to check that. I switched machines and had to reinst Windows because of anno2070 wasnt working under wine. This has changed meanwhile 8))) So as soon as i have hsdpa again (eoMonth)- ill switch back to linux and FreeBSD :) and write the extension to include mbmon first with the tunable above.

rcfa

OK, finally got the coretemp.ko installed, etc. and now have a temperature reading of a cool 35C

Was a little bit involved, because OS X doesn't grok BSD's file system, so I ended up doing a memory stick, mounting it on the pfSense box, and then copied it with an slogin over to where it needs to go.

The config file I ended up editing with the Web GUI, because I couldn't remember the name of the non-vi editor installed on pfSense, it's not nano or pico, and of course not emacs (which I usually would use)
Why the heck keep I forgetting the name? ???

Anyway, things are working. Now it's going to be interesting to see what get's stomped over with the next upgrade that I'm just running….