HOWTO: Temperature Monitoring with coretemp in Sysinfo widget
-
Give me your whole file after the patch was applied and I can tell you what went wrong.
Usually something like this is caused by applying a patch to another version of the file. Mine was 2.0.1 amd64, so if you apply the patch to anything else, it is likely to break if the file has changed and you just blindly apply the patch :)Hello,
sorry but I was very busy, I send tot you a pm with the file. It's the same version.
Thanks -
Hi!
I've done exactly like U wrote but it doesn't work…
I attached my files so u can look if there is something wrong. I'm not getting any errors in any case.But when I'm running sysctl -a | grep temperature it doesnt do anything…
[2.0.1-RELEASE][root@pfsense.localdomain]/root(14): sysctl -a | grep temperature [2.0.1-RELEASE][root@pfsense.localdomain]/root(15):I've allready wrote kldload coretemp but if I'm doing it again it will just print a message: File exists
[2.0.1-RELEASE][root@pfsense.localdomain]/root(15): kldload coretemp kldload: can't load coretemp: File existsWhat's wrong? :)
-
If you don't get a sysctl value at the command line the widget will never work.
What cpu do you have?Steve
-
If you don't get a sysctl value at the command line the widget will never work.
What cpu do you have?Steve
AMD Athlon
64 X2 Dual Core Processor 6000+ -
-
-
Yes, the name is a little ambiguous. Glad it worked I've not ever run it myself. ;)
Steve
-
Works as described, I patched manually. Thanks great work show-p1984!
-
I tried this on my system, but it did not work :(. I have a AMD Athlon
XP 3200+ and I used the amdtemp.ko module.Any sugestions???
-
The amdtemp module supports AMD K8 microarchitecture or newer. The Athlon XP is K7.
To get the temperature of earlier CPUs you could try using mbmon. You will have to do some coding to make it work with this widget though.
Steve
-
Thanks! This is great and should be included in the default install IMO!!
Again, Thanks alot!
Cheers
E -
Hello,
I tried applying the patch that is located in the main post. I downloaded the package system patch and have tried it via command line with the same result. When I test the patch I get errors saying it cant be applied cleanly. Is this due to showp1984 stuff? should it be removed? not that experienced with troubleshooting patches..Output of full patch apply test:
/usr/bin/patch –directory=/ -t -p4 -i /var/patches/50be92a047646.patch --check --forward
Hmm... Looks like a unified diff to me...
The text leading up to this was:|diff -Naur /home/showp1984/Desktop/a/usr/local/www/includes/functions.inc.php /home/showp1984/Desktop/b/usr/local/www/includes/functions.inc.php
|--- /home/showp1984/Desktop/a/usr/local/www/includes/functions.inc.php 2012-08-07 01:01:33.902057913 +0200+++ /home/showp1984/Desktop/b/usr/local/www/includes/functions.inc.php 2012-08-06 06:13:12.000000000 +0200 No file to patch. Skipping... Hunk #1 ignored at 136. Hunk #2 ignored at 151. 2 out of 2 hunks ignored--saving rejects to a/usr/local/www/includes/functions.inc.php.rej Hmm... The next patch looks like a unified diff to me... The text leading up to this was:
|diff -Naur /home/showp1984/Desktop/a/usr/local/www/widgets/widgets/system_information.widget.php /home/showp1984/Desktop/b/usr/local/www/widgets/widgets/system_information.widget.php
|--- /home/showp1984/Desktop/a/usr/local/www/widgets/widgets/system_information.widget.php 2012-08-07 01:01:27.446742521 +0200+++ /home/showp1984/Desktop/b/usr/local/www/widgets/widgets/system_information.widget.php 2012-08-06 06:10:46.000000000 +0200 No file to patch. Skipping... Hunk #1 ignored at 232. 1 out of 1 hunks ignored--saving rejects to a/usr/local/www/widgets/widgets/system_information.widget.php.rej done -
I haven't actually tried this but looking at the patch file it's obviously been built against two files on the OPs desktop machine.
Since this is a relatively minor change to only two files I suggest you simply edit the two files manually.
Steve
-
Stephen,
I was able to do the manual edits prior to posting. I was just wondering why the patch wasn't working. It would have just saved me some time editing that's all. Thought maybe i was doing something wrong with the patch.btw thanks to the OP for working on this. I do appreciate it. Now if i could just get this info on LCDProc everything would be golden. :-D
-
For some reason i can't get coretemp to automatically load upon reboot. I can ssh over and run kldload coretemp and i am up and running. I did edit the loader.conf.local and added coretemp_load="yes". The module is in /boot/modules as well.
Am I missing something else to enable pfsense to load this on boot if i have to reboot the firewall?
-
File permissions perhaps?
Looks like you're doing everything correctly.Steve
-
File permissions perhaps?
Looks like you're doing everything correctly.Steve
What would i be looking for in relation to file permission? is there a way to test (fake boot process) to see if it would give me an error and why it wouldnt load?
-
should i add the line to loader.conf? or would that be bad? Wasnt sure if the .local may not be utilized for some reason? just thinking out loud.
-
should i add the line to loader.conf? or would that be bad? Wasnt sure if the .local may not be utilized for some reason? just thinking out loud.
/boot/loader.conf may change on reinstall; /boot/loader.conf.local is guaranteed to remain untouched by a reinstall.
You might see an error report on coretemp during the early boot (before the kernel is started).
-
Worked just fine on my Jetway MB with pfSense 2.0.2
coretemp.ko was already in /boot/kernel folder
Edited all files manually
