CPU temp

lucke · 2006-10-09 21:41:23

I'm not sure whether loading cpufreq_ondemand sets the governor automatically to ondemand governor. Just check with cpufrequtils.

If you have module autoloading set in rc.conf, it could be that those modules are loaded after boot (check with lsmod), but I think that's not the case. Just add powernow-k8 and cpufreq_ondemand to MODULES array in rc.conf, just like you put daemons in DAEMONS array.

--edit--

And modprobe w83627ehf (add it to rc.conf too) and run sensors. You should see some output with temps/rpms.

--edit--

Don't follow instructions provided by sensors-detect - just say as stated in a previous edit ;-)

Seb74 · 2006-10-09 21:49:21

I dont have time to fix cool 'n quiet now, I need to sleep. But I just made a try for sensors (rebooting now).

I created a /etc/modules.conf and added:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

Then I pasted at the end of rc.conf this:
#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83627ehf
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

Lets see what happens....if the system comes up at all now

EDIT: Oh forgot that last thing, some file needed to be copied to rc.d or something....it never ends
Oh yeah, easy when that lm_sensors file isn't to be found in my system.

Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.

# find / -name lm_sensors.init
[root@seb74 xxx]#

# sensors
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!

lucke · 2006-10-09 21:53:16

Ihihi, it's fun to use BBS for almost real-time communication :-P

You shouldn't have created modprobe.conf or pasted that to rc.conf - just add that w83627ehf module to MODULES array and forget about i2c-isa/dev - they will be loaded when needed. Forget about everything sensors-detect said, there are nicer ways of doing this under Arch (as stated above).

Seb74 · 2006-10-09 21:55:26

lucke wrote:

Ihihi, it's fun to use BBS for almost real-time communication :-P
You shouldn't have created modprobe.conf or pasted that to rc.conf - just add that w83627ehf module to MODULES array and forget about i2c-isa/dev - they will be loaded when needed. Forget about everything sensors-detect said, there are nicer ways of doing this under Arch (as stated above).

Yeah, cool

So, I shall delete all I did to all config-files???

I created a /etc/modules.conf and added:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

Then I pasted at the end of rc.conf this:
#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83627ehf
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

Delete all that, and just add that one module to array/vector in rc.conf?

lucke · 2006-10-09 21:57:57

Yeah, delete modules.conf and that line, add module to array.

To avoid reboot, check whether "modprobe w83627ehf; sensors" (as root) works as expected.

Seb74 · 2006-10-09 21:59:05

lucke wrote:

Yeah, delete modules.conf and that line, add module to array.
To avoid reboot, check whether "modprobe w83627ehf; sensors" (as root) works as expected.

Already rebooted

$ sensors
w83627ehf-isa-0290
Adapter: ISA adapter
Case Fan: 697 RPM (min = 336 RPM, div = 16)
CPU Fan: 703 RPM (min = 511 RPM, div = 16)
fan3: 0 RPM (min = 4272 RPM, div = 4)
fan4: 0 RPM (min = 9782 RPM, div = 2)
Sys Temp: +34 C (high = -19 C, hyst = -125 C)
CPU Temp: +29.0 C (high = +80.0 C, hyst = +75.0 C)
temp3: +36.0 C (high = +80.0 C, hyst = +75.0 C)

Dont believe my CPU-temp? Check this one out

http://seb74.no-ip.com/server/Inside.jpg

lucke · 2006-10-09 22:03:32

Well, I have passive Ninja on my CPU and temp is alike.

Anyway, seems sensors work properly, eh?

Now only install cpufrequtils and check how things are with cpufreq.

Seb74 · 2006-10-09 22:03:50

So, for own reference before I go to bed now and forget everything, for sensors to work I did:

Install lm_sensors
Run sensors-detect

Dont care about what the output tells me to do.
Instead just add that module w83627ehf to the MODULES-vector in rc.conf.
Reboot and its done, run "sensors" to get the output.

And indeed, its a nice short output, not like others I've seen with tens of rows with voltages and everything.

Great, thanks alot for the help. I'll have to dig deeper into Cool 'n Quiet tomorrow and see if its possible to get it up and running too.

EDIT: Wonder what temp3 might be. And wonder why fan3 and fan4 are there when nothing is to read for them....

lucke · 2006-10-09 22:07:04

Yeah, that's it. Few easy steps, aren't those?

That was quite crazy, adding/editing posts, I must admit. Well, at least it works.

Sleep well.

Seb74 · 2006-10-10 05:00:55

lucke wrote:

Yeah, that's it. Few easy steps, aren't those?
That was quite crazy, adding/editing posts, I must admit. Well, at least it works.
Sleep well.

Yeah, really crazy
Thanks
I just wonder how everyone are supposed to do this right without direct help like I got. I mean "no no, dont do like the installprogram says, do this way instead"

Anyway, I managed to strip one unneccesary ugly row from the output by the option -A, and also managed to ignore one or two unused FAN's, so now looks like this.

$ sensors -A
w83627ehf-isa-0290
Case Fan: 697 RPM (min = 336 RPM, div = 16)
CPU Fan: 691 RPM (min = 511 RPM, div = 16)
Sys Temp: +34 C (high = +45 C, hyst = +40 C)
CPU Temp: +28.0 C (high = +45.0 C, hyst = +40.0 C)
temp3: +35.5 C (high = +80.0 C, hyst = +75.0 C)

BUT, I would love to get rid of those stupid "comments" inside the parantheses....I dont want to have the program compute some high/low-tresholds for my temps, it doesn't know what its doing anyway. 336RPM, thats silly. I dont need/want it, but that config-file is such a monster
You dont happen to know how to disable that shit, and just have a clean readout of temps/RPM's?

Anyway maybe doesn't matter since I for some reason dont manage to have PHP print this.....it can print my uptime by exec("uptime") but when I switch that for exec("sensors -A") nothing is shown

lucke · 2006-10-10 09:08:51

To isolate Celsius/RPM digits, use the following commands:

sensors | grep "CPU Temp" | cut -d " " -f 3 | sed s/+//
sensors | grep "CPU Fan" | cut -d " " -f 3
sensors | grep "Case Fan" | cut -d " " -f 3

If it doesn't work passed directly to PHP, you could always put it into some files, like:

sensors1

#!/bin/bash
sensors | grep "CPU Temp" | cut -d " " -f 3 | sed s/+//

and then "chmod +x sensors1" and copy it into PHP's exec path (I don't know anything about PHP, honestly).

Seb74 · 2006-10-10 17:27:00

Found out its simple in php, I just print the elements in the output-vector that I want to show.
"Problem" is that I dont want those silly stuff inside the paranthesis....min and div and hysteris and whatever. Need to refresh my php-skills a bit so I can print up until the "(" comes and skip rest of the line.

Anyway, thanks a lot. Gotta start looking some more at Cool 'n Quiet also....would be great to get that running. Then the server is just perfect (not there yet though hehe, but almost)

EDIT: Code probably sucks since I haven't touched php in a year or two, but I got it working all by myself with a loop inside a loop, reading up to the first "(".

<?php
$cpu = array();
exec("sensors -A",$cpu);
$uptime = exec("uptime");
print "<b>Server time and uptime:</b> " . exec("uptime") . "<br><br>";
for ($i = 1; $i <= 4; $i++) {
$match = "(";
$find = strpos($cpu[$i], $match);
for ($j = 0; $j <find>

lucke · 2006-10-10 17:40:38

Well, you can apparently just exec the commands I posted.

Seb74 · 2006-10-10 18:45:49

Did it even nicer now, with bold "titles"

<?php
    $cpu = array();
    exec("sensors -A",$cpu);
    $uptime = exec("uptime");
    print "<b>Server time and uptime:</b> " . exec("uptime") . "<br>";
    for ($i = 1; $i <= 4; $i++) {
      $matchfirst = ":";
      $matchend = "(";
      $find = strpos($cpu[$i], $matchfirst);
      $find2 = strpos($cpu[$i], $matchend);
      print "<b>";

      for ($j = 0; $j <= $find; $j++)
        echo $cpu[$i][$j];
      print "</b>";

      for ($j = $find + 1; $j <find2>

Doesn't seem to work to paste the code here....looks strange and stuff missing at the end. Oh well

http://seb74.no-ip.com/

johnisevil · 2006-10-10 19:24:03

Seb74 wrote:

lucke wrote:
Yeah, delete modules.conf and that line, add module to array.
To avoid reboot, check whether "modprobe w83627ehf; sensors" (as root) works as expected.
Already rebooted
$ sensors
w83627ehf-isa-0290
Adapter: ISA adapter
Case Fan: 697 RPM (min = 336 RPM, div = 16)
CPU Fan: 703 RPM (min = 511 RPM, div = 16)
fan3: 0 RPM (min = 4272 RPM, div = 4)
fan4: 0 RPM (min = 9782 RPM, div = 2)
Sys Temp: +34 C (high = -19 C, hyst = -125 C)
CPU Temp: +29.0 C (high = +80.0 C, hyst = +75.0 C)
temp3: +36.0 C (high = +80.0 C, hyst = +75.0 C)
Dont believe my CPU-temp? Check this one out
http://seb74.no-ip.com/server/Inside.jpg

My Athlon 64 FX60 usually idles around that same temperature with the stock HSF. No aftermarket cooling here.

Seb74 · 2006-10-10 19:40:51

johnisevil wrote:

Seb74 wrote:
lucke wrote:
Yeah, delete modules.conf and that line, add module to array.
To avoid reboot, check whether "modprobe w83627ehf; sensors" (as root) works as expected.
Already rebooted
$ sensors
w83627ehf-isa-0290
Adapter: ISA adapter
Case Fan: 697 RPM (min = 336 RPM, div = 16)
CPU Fan: 703 RPM (min = 511 RPM, div = 16)
fan3: 0 RPM (min = 4272 RPM, div = 4)
fan4: 0 RPM (min = 9782 RPM, div = 2)
Sys Temp: +34 C (high = -19 C, hyst = -125 C)
CPU Temp: +29.0 C (high = +80.0 C, hyst = +75.0 C)
temp3: +36.0 C (high = +80.0 C, hyst = +75.0 C)
Dont believe my CPU-temp? Check this one out
http://seb74.no-ip.com/server/Inside.jpg
My Athlon 64 FX60 usually idles around that same temperature with the stock HSF. No aftermarket cooling here.

Actually I have a hard time believing that. Some sensors dont show the correct temp either.
My 3000+ with stock on idled around 35C. My new X2 4600+ idles around 36C with a Zalman on it.
Either somethings wrong, or that FX60 is one cool motherf***er

Seb74 · 2006-10-10 19:45:31

Sorry for the newbie-question, but does lsmod show all modules I've run modprobe on???

This is what it shows anyway.

lsmod
Module Size Used by
ipv6 261472 26
joydev 10112 0
ppdev 8456 0
evdev 9984 0
lp 11464 0
ehci_hcd 30984 0
r8169 26504 0
parport_pc 27688 1
uhci_hcd 22552 0
serio_raw 6788 0
rtc 12416 0
ppp_generic 26912 0
slhc 6912 1 ppp_generic
parport 37004 3 ppdev,lp,parport_pc
shpchp 38200 0
pci_hotplug 29440 1 shpchp
pcspkr 3328 0
w83627ehf 11020 0
i2c_isa 5120 1 w83627ehf
i2c_core 20224 2 w83627ehf,i2c_isa
usbcore 125728 3 ehci_hcd,uhci_hcd
ide_disk 14592 3
generic 5636 0 [permanent]
via82cxxx 8964 0 [permanent]
ide_core 134784 3 ide_disk,generic,via82cxxx

Does this mean I dont have the powernow or cpufreq modules installed anymore, that they dissapeared at reboot?
If so I'm happy cause I just decided not to mess with Cool 'n Quiet and dont want any shit loaded that I dont need and that might mess something up. I dont want to take any risks for only 5-10W less.....60W idle is totally ok for now, and the system is so nice, everything works perfect. Dont want to touch anything more now

Thanks

lucke · 2006-10-10 20:52:48

Yeah, lsmod shows all the loaded modules. If you haven't added powernow and ondemand to rc.conf, they won't be loaded.

It's your call, but there's no risk of fscking things up - and powersaving could be actually more substantial (wish I had some wattmeter). Just load those modules and use cpufreq-set from cpufrequtils to set the governor to ondemand and you're all set.

Seb74 · 2006-10-10 20:57:20

lucke wrote:

Yeah, lsmod shows all the loaded modules. If you haven't added powernow and ondemand to rc.conf, they won't be loaded.
It's your call, but there's no risk of fscking things up - and powersaving could be actually more substantial (wish I had some wattmeter). Just load those modules and use cpufreq-set from cpufrequtils to set the governor to ondemand and you're all set.

We'll see we'll see....
In XP Cool 'n Quiet only dropped watt from 62 or so to around 54....around 8W less. Not very much.

Thanks a lot for your help anyway, cool to have rpm's and temps on the server webpage

xterminus · 2006-10-10 21:02:47

Seb74 wrote:

Actually I have a hard time believing that. Some sensors dont show the correct temp either.
My 3000+ with stock on idled around 35C. My new X2 4600+ idles around 36C with a Zalman on it.
Either somethings wrong, or that FX60 is one cool motherf***er

lm_sensors has a hard time if your bios swaps out motherboard and cpu temps. In my case (nforce2 mobo), CPU temp in sensors is atcually MOBO temp, and visa versa.

Also, if you have a sensor enabled in your bios that is not connected, you can get some REALLY odd temperature readings from that device. I used to have a power-supply temp sensor enabled in my bios (but no way to actually *read* the temp in that PS), and would get fluctations on that sensor which ranged from 5C to 300C When a high value would return, sensors would start to freak out, which was annoying.

lucke · 2006-10-11 07:54:08

Seb74 wrote:

In XP Cool 'n Quiet only dropped watt from 62 or so to around 54....around 8W less. Not very much.

I wonder, what watt difference do you get between idle with and without C'n'Q enabled on your X2 4600+ box?

Seb74 · 2006-10-11 08:13:13

lucke wrote:

Seb74 wrote:
In XP Cool 'n Quiet only dropped watt from 62 or so to around 54....around 8W less. Not very much.
I wonder, what watt difference do you get between idle with and without C'n'Q enabled on your X2 4600+ box?

From 83W to 99W, so quite some difference there. But that CPU draws more power also, and maybe the dual cores make the difference larger too.

Anyway my server is very quiet now. Only moving parts in it (except the perfectly vibrationisolated harddrive) are three very low RPM 120mm, and the whole box is covered in damping materials, so you barely hear it 4-5 meters away if its silent in the room
Almost as silent as my old P3 server that I gave up cause it finally started getting instable

Eliatamby · 2006-10-11 13:15:53

xterminus wrote:

Seb74 wrote:
Actually I have a hard time believing that. Some sensors dont show the correct temp either.
My 3000+ with stock on idled around 35C. My new X2 4600+ idles around 36C with a Zalman on it.
Either somethings wrong, or that FX60 is one cool motherf***er
lm_sensors has a hard time if your bios swaps out motherboard and cpu temps. In my case (nforce2 mobo), CPU temp in sensors is atcually MOBO temp, and visa versa.

You can swap values around in the config file. E.g. I swapped my "Chipset " temp with my "CPU" temp

Seb74 · 2006-10-11 17:05:58

I get the right values anyway, same readings as in bios and in Windows. But yeah, I've heard about people too who has CPU/Mobo mixed up.

Eldanen · 2006-12-15 17:20:35

Sensors-detect told me I needed module w83627ehf, but when I try to modprobe it, I get this error:

[root@myhost lue]# modprobe w83627ehf
FATAL: Error inserting w83627ehf (/lib/modules/2.6.19-ARCH/kernel/drivers/hwmon/w83627ehf.ko): No such device
[root@myhost lue]#

Any advice?

Arch Linux

#26 2006-10-09 21:41:23

Re: CPU temp

#27 2006-10-09 21:49:21

Re: CPU temp

#28 2006-10-09 21:53:16

Re: CPU temp

#29 2006-10-09 21:55:26

Re: CPU temp

#30 2006-10-09 21:57:57

Re: CPU temp

#31 2006-10-09 21:59:05

Re: CPU temp

#32 2006-10-09 22:03:32

Re: CPU temp

#33 2006-10-09 22:03:50

Re: CPU temp

#34 2006-10-09 22:07:04

Re: CPU temp

#35 2006-10-10 05:00:55

Re: CPU temp

#36 2006-10-10 09:08:51

Re: CPU temp

#37 2006-10-10 17:27:00

Re: CPU temp

#38 2006-10-10 17:40:38

Re: CPU temp

#39 2006-10-10 18:45:49

Re: CPU temp

#40 2006-10-10 19:24:03

Re: CPU temp

#41 2006-10-10 19:40:51

Re: CPU temp

#42 2006-10-10 19:45:31

Re: CPU temp

#43 2006-10-10 20:52:48

Re: CPU temp

#44 2006-10-10 20:57:20

Re: CPU temp

#45 2006-10-10 21:02:47

Re: CPU temp

#46 2006-10-11 07:54:08

Re: CPU temp

#47 2006-10-11 08:13:13

Re: CPU temp

#48 2006-10-11 13:15:53

Re: CPU temp

#49 2006-10-11 17:05:58

Re: CPU temp

#50 2006-12-15 17:20:35

Re: CPU temp

Board footer