CPUtemp - A CPU Temperature Monitor

Miscellaneous tools
Message
Author
majorfoo
Posts: 448
Joined: Mon 07 Mar 2011, 22:27
Location: Wish I knew

#31 Post by majorfoo »

rcrsn51 wrote:I'm talking about the Help instructions that refer to Line 5 of CPUtemp - ie. when you click the Help button.

The CPU Frequency Scaling Tool is a separate program from CPUtemp. You can't configure one from the other.

CPUtemp is not guaranteed to find a temperature reading on all machines.
Sir, you are dealing with a dummy when it comes to this stuff.
If I enter modprobe coretemp from command line, results are

# modprobe coretemp
FATAL: Error inserting coretemp (/lib/modules/2.6.33.2/kernel/drivers/hwmon/coretemp.ko): No such device
/root

I checked /lib/modules/2.6.33.2/kernel/drivers/hwmon and coretemp.ko is already there.

Is this what you are looking for?

bios shows temperatures as listed in my first post

When I click the flamnig icon in tray i get

majorfoo
Last edited by majorfoo on Sun 28 Aug 2011, 22:20, edited 2 times in total.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#32 Post by rcrsn51 »

From the sound of things, neither CPUtemp nor CPU Frequency Scaling Tool are going to work on this machine.

majorfoo
Posts: 448
Joined: Mon 07 Mar 2011, 22:27
Location: Wish I knew

#33 Post by majorfoo »

rcrsn51 wrote:From the sound of things, neither CPUtemp nor CPU Frequency Scaling Tool are going to work on this machine.
Thanks for all your help. Appears this machine is like me- too old to cut the mustard anymore

majorfoo

User avatar
DaveS
Posts: 3685
Joined: Thu 09 Oct 2008, 16:01
Location: UK

#34 Post by DaveS »

OK, here is a little strange. Using Slacko beta. Hardinfo/sensors shows no information. Installed CPUtemp which works perfectly. Checking shows my machine uses coretemp. Hardinfo/sensors shows info BUT on re-boot hardinfo/sensors is again blank. Click the systray CPUtemp icon and the temp info is displayed as expected. Re-check hardinfo, and display is again populated.
Conclusion: I need to click on the systray icon for CPUtemp to activate output in hardinfo/sensors. Why?
Spup Frugal HD and USB
Root forever!

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#35 Post by rcrsn51 »

DaveS wrote:Conclusion: I need to click on the systray icon for CPUtemp to activate output in hardinfo/sensors. Why?
That's how the coretemp module gets loaded.

User avatar
DaveS
Posts: 3685
Joined: Thu 09 Oct 2008, 16:01
Location: UK

#36 Post by DaveS »

rcrsn51 wrote:
DaveS wrote:Conclusion: I need to click on the systray icon for CPUtemp to activate output in hardinfo/sensors. Why?
That's how the coretemp module gets loaded.
Ok. I also notice that when I close the CPUtemp information GUI with the OK button, it closes as expected, but when I close it with the window 'x' button, it closes as expected but then pops up the help dialog (using Openbox, not tried JWM).
Edit: same with JWM.
Spup Frugal HD and USB
Root forever!

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#37 Post by rcrsn51 »

DaveS wrote:Ok. I also notice that when I close the CPUtemp information GUI with the OK button, it closes as expected, but when I close it with the window 'x' button, it closes as expected but then pops up the help dialog (using Openbox, not tried JWM).
Thanks. That's fixable. Open /usr/local/bin/CPUtemp in a text editor and change Line 51 to

Code: Select all

[ "$EXIT" = "OK"  -o "$EXIT" = "abort" ] && exit

User avatar
DaveS
Posts: 3685
Joined: Thu 09 Oct 2008, 16:01
Location: UK

#38 Post by DaveS »

rcrsn51 wrote:
DaveS wrote:Ok. I also notice that when I close the CPUtemp information GUI with the OK button, it closes as expected, but when I close it with the window 'x' button, it closes as expected but then pops up the help dialog (using Openbox, not tried JWM).
Thanks. That's fixable. Open /usr/local/bin/CPUtemp in a text editor and change Line 51 to

Code: Select all

[ "$EXIT" = "OK"  -o "$EXIT" = "abort" ] && exit
Done... fixed :)
Spup Frugal HD and USB
Root forever!

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#39 Post by rcrsn51 »

I have uploaded v1.5 with this fix applied.

jpeps
Posts: 3179
Joined: Sat 31 May 2008, 19:00

#40 Post by jpeps »

Works nicely; scaling even works. Curious what this is reading, though, since this intel processor (dell laptop--bios from 1994) has no sensors, although a thermal monitor is listed the hardware description. I can't get any info using dstat --thermal script (complains there's no kernel ACPI support. Pwidgets doesn't work either (I think it looks for /proc/eee )

edit: I see...it reads /sys/class/thermal/thermal_zone0/temp.
Last edited by jpeps on Tue 22 Nov 2011, 01:59, edited 1 time in total.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#41 Post by nooby »

I've started a new thread for my personal problem

http://www.murga-linux.com/puppy/viewtopic.php?t=73658

text like this
neither Snow Puppy 5 and Slacko5.3 with CPUtemp installed can show
temp now it only display eeepc-isa-000

But it show Thrm tem as 52 and that started the fan at a low repm.
I had tested puppeee44 and unfortunately had a unclean shut down
and after that CPUtemp stopped working. it did not help reinstall it either.

I guess I can boot with pfix=ram if I knew how to do that in asus eeepc 900 it fail to stop when I use isolinux boot. I guess I have to rename the savefile to something else so it boot fresh maybe that restore the
default settings of the thermometer sensors?
I have renamed the save file now so it failed to load it while booting
nope that did not help it get the reading of cupu temp back

setting up will take a while so I have to go to bed now.


hope that somebody want to help me with this thing.

any idea welcome. but I have to go to bed now.

seems odd that the sensors can go broken after I hit some button on the software set up. Would it help to start up xandros once more maybe
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
seneka77
Posts: 26
Joined: Thu 19 Jan 2012, 02:44
Location: World, Euroope, Spain, Andalucia, Cádiz, Sanlúcar de Barrameda
Contact:

#42 Post by seneka77 »

Thanks a lot for the pet =)
It is very useful for me, so i need to check temp with some process.
Is it possibel to get CPUtemp that check temperatures every 3,4 seconds? It could be great.

Dont know why in my laptop (Dell inspiron1501), hardinfo just display temp of one core. Any idea how to solve it?
Also check Harddisk(samsung hm08011) temp is good, and no idea how to get here... in win Everest app can do it.

snayak
Posts: 422
Joined: Wed 14 Sep 2011, 05:49

#43 Post by snayak »

Will this work for Wary 500?
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]

[url]http://srinivas-nayak.blogspot.com/[/url]

Pelo

temperature alert

#44 Post by Pelo »

could it be possible to be alerted whem temperature is too high ?
Hello everybody.
I have and old computer with cooling not operating. Would it be possible that there is a flash alert on my desktop when i must stop using the computer , the more often when my cd player works.
Merci.

toronado
Posts: 95
Joined: Wed 04 Sep 2013, 21:09

#45 Post by toronado »

I installed the pet and it didn't display a temp, so I followed the help to run sensors-detect and got the following result:

Code: Select all

Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `w83627hf':
  * ISA bus, address 0x290
    Chip `Winbond W83697HF/F/HG Super IO Sensors' (confidence: 9)
So do I go to /usr/local/bin/CPUtemp and edit line 5? What exactly do I put there?

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#46 Post by rcrsn51 »

What kind of processor is this?

From the command line, run: modprobe w83627hf

What messages do you get?

toronado
Posts: 95
Joined: Wed 04 Sep 2013, 21:09

#47 Post by toronado »

modprobe w83627hf produced no output in the terminal. (it acts as if I just hit enter without typing anything)

CPU: AMD Athlon(tm) XP 2000+ (1.667 MHz)

Edit: Just tried clicking on the flame icon again and it is now producing output! Not sure why. Thanks.

Tried typing "sensors" at the command prompt and got the same identical output as your CPUtemp program. (when I tried that before installing your pet it produced nothing)

Code: Select all

sh-4.1# sensors
w83697hf-isa-0290
Adapter: ISA adapter
in0:          +1.78 V  (min =  +0.10 V, max =  +2.05 V)
in2:          +3.36 V  (min =  +0.64 V, max =  +2.66 V)  ALARM
in3:          +3.02 V  (min =  +0.00 V, max =  +0.58 V)  ALARM
in4:          +3.12 V  (min =  +0.00 V, max =  +0.51 V)  ALARM
in5:          +0.54 V  (min =  +0.51 V, max =  +0.00 V)  ALARM
in6:          +0.85 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:          +3.33 V  (min =  +0.00 V, max =  +0.06 V)  ALARM
in8:          +3.44 V  (min =  +0.58 V, max =  +1.41 V)  ALARM
fan1:        1939 RPM  (min = 9375 RPM, div = 4)  ALARM
fan2:           0 RPM  (min = 1739 RPM, div = 4)  ALARM
temp1:        +33.0 C  (high =  +8.0 C, hyst =  +2.0 C)  ALARM  sensor = thermistor
temp2:        +36.5 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
beep_enable: enabled

Did this pet include the lm-sensors when I installed it?

Perhaps OT, but would also like to get the hddtemp to work.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#48 Post by rcrsn51 »

So do I go to /usr/local/bin/CPUtemp and edit line 5? What exactly do I put there?

Code: Select all

modprobe w83627hf

toronado
Posts: 95
Joined: Wed 04 Sep 2013, 21:09

#49 Post by toronado »

rcrsn51 wrote:
So do I go to /usr/local/bin/CPUtemp and edit line 5? What exactly do I put there?

Code: Select all

modprobe w83627hf
OK, I get it now. It wouldn't work after reboot until I edited the CPUtemp file. Works great now. Thanks!

linuxcbon
Posts: 1312
Joined: Thu 09 Aug 2007, 22:54

#50 Post by linuxcbon »

hi,
A little feedback.
Can you make separate pets : lm_sensors and your application , so it doesn't get mixed ?
It worked : I run sensors-detect , in the end it says

Code: Select all

To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):
#----cut here----
# Chip drivers
modprobe it87
/usr/local/bin/sensors -s
#----cut here----
I run the modprobe it87 as asked above and then typing "sensors" shows :

Code: Select all

# /usr/local/bin/sensors 
it8718-isa-0228
Adapter: ISA adapter
in0:          +1.04 V  (min =  +0.00 V, max =  +4.08 V)
in1:          +1.84 V  (min =  +0.00 V, max =  +4.08 V)
in2:          +3.33 V  (min =  +0.00 V, max =  +4.08 V)
+5V:          +3.01 V  (min =  +0.00 V, max =  +4.08 V)
in4:          +3.04 V  (min =  +0.00 V, max =  +4.08 V)
in5:          +3.22 V  (min =  +0.00 V, max =  +4.08 V)
in6:          +4.08 V  (min =  +0.00 V, max =  +4.08 V)  ALARM
in7:          +2.00 V  (min =  +0.00 V, max =  +4.08 V)
Vbat:         +3.20 V  
fan1:        2303 RPM  (min =   10 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:           0 RPM  (min =    0 RPM)
temp1:        +34.0 C  (low  = +127.0 C, high = +127.0 C)  sensor = thermistor
temp2:        +39.0 C  (low  = +127.0 C, high = +70.0 C)  sensor = thermal diode
temp3:        +47.0 C  (low  = +127.0 C, high = +127.0 C)  sensor = thermistor
cpu0_vid:    +1.050 V
intrusion0:  OK
It seems the in6: ALARM is a bug, since, it's normal ?
Another bug : +5V: +3.01 V...
The CPU temperatures seem correct.

Post Reply