Temperature Widget

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….

stephenw10

It's ee (easy editor) ;)

Cino

@rcfa:

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

wish mine was at 35c, 60c right now :-(

stephenw10

Here's the 64bit coretemp.ko from FreeBSD 8.3 for anyone else.
Remove the .png extension.

Steve

coretemp.ko.png

kalu

Temperature widget is not available (or not supported) on our nano bsd alix boards..
:(

rcfa

@kalu:

Temperature widget is not available (or not supported) on our nano bsd alix boards..
:(

What kind of CPUs do these have? If the CPU doesn't have built-in sensors (like e.g. the intel Core CPUs or the intel Atom CPUs), or the motherboard doesn't have a temperature sensor that's somehow published (e.g. ACPI), then it's got to be a no-go.

gerdesj

@rcfa:

@kalu:

Temperature widget is not available (or not supported) on our nano bsd alix boards..
:(

What kind of CPUs do these have? If the CPU doesn't have built-in sensors (like e.g. the intel Core CPUs or the intel Atom CPUs), or the motherboard doesn't have a temperature sensor that's somehow published (e.g. ACPI), then it's got to be a no-go.

Mine (PC Engines thing) shows this in dmesg:

CPU: Geode(TM) Integrated Processor by AMD PCS (498.05-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x5a2 Family = 5 Model = a Stepping = 2
Features=0x88a93d <fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>AMD Features=0xc0400000 <mmx+,3dnow!+,3dnow!>… and this further down which probably doesn't help:

ACPI Error: A valid RSDP was not found (20101013/tbxfroot-309)
ACPI: Table initialisation failed: AE_NOT_FOUND
ACPI: Try disabling either ACPI or apic support.

Cheers
Jon</mmx+,3dnow!+,3dnow!></fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>

rcfa

Not sure if the GEODE chips have built-in temp sensors but if so, you'd likely have to install the amdtemp.ko module analog to us intel guys having to install the coretemp.ko module.

http://www.freebsd.org/cgi/man.cgi?query=amdtemp&apropos=0&sektion=0&manpath=FreeBSD+9.0-RELEASE&arch=default&format=html

m4f1050

@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….

I enabled SSH on pfSense and I connect from both Win7 and OS X. What I do on OS X is open a terminal shell and type "ssh 192.168.0.1 -l admin" it will then ask me for a password. On Win7 I use putty. After that when I get to the menu on pfSense I select option 8, and on pfSense's shell I ftp to my machine and transfer files that way. I also use nano "pkg_add -r nano"

…finally back on hsdpa :)

I think we agree that we have different installations all over the world.
And so we have special needs to handle. One might need to use a coretemp module (or acpi or mbmon) , on another system it crashes.

We cant force everyone to acpi or coretemp. We need to support the freedom for everyone, to use what he needs to as long as this doesnt hit the freedom of another one.

For this reason, the current plan for the widget is to support mbmon, acpi and coretemp
and to implement a config screen for us users, so we can select the sensors we need.

rcfa

@ThorstenK:

For this reason, the current plan for the widget is to support mbmon, acpi and coretemp
and to implement a config screen for us users, so we can select the sensors we need.

Not like I care, but what about amdtemp.ko ?

lets see "coretemp" as a symbol for Processor specific modules.
Its not about the name, its about the freedom of the admin to install what he needs to support special requirements.