Page 3 of 4
Posted: Sun 20 Nov 2011, 21:20
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
Posted: Tue 31 Jan 2012, 15:20
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.
Posted: Mon 13 Feb 2012, 13:14
by snayak
Will this work for Wary 500?
temperature alert
Posted: Fri 03 Aug 2012, 05:39
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.
Posted: Thu 24 Oct 2013, 02:38
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?
Posted: Thu 24 Oct 2013, 03:16
by rcrsn51
What kind of processor is this?
From the command line, run: modprobe w83627hf
What messages do you get?
Posted: Thu 24 Oct 2013, 03:47
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.
Posted: Thu 24 Oct 2013, 08:17
by rcrsn51
So do I go to /usr/local/bin/CPUtemp and edit line 5? What exactly do I put there?
Posted: Fri 25 Oct 2013, 06:13
by toronado
rcrsn51 wrote:So do I go to /usr/local/bin/CPUtemp and edit line 5? What exactly do I put there?
OK, I get it now. It wouldn't work after reboot until I edited the CPUtemp file. Works great now. Thanks!
Posted: Wed 25 Dec 2013, 18:55
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.
Posted: Wed 25 Dec 2013, 19:01
by linuxcbon
Nice, now hardinfo displays the sensors, I will ask Barry to add the modprobe and your application...
Posted: Wed 25 Dec 2013, 19:24
by rcrsn51
linuxcbon wrote:Can you make separate pets : lm_sensors and your application , so it doesn't get mixed ?
I'd rather not. I slightly modify the sensors binary to be compatible with the CPUtemp script. It works better if they are packaged together. If you look in CPUtemp, you will see the full path /usr/local/bin/sensors so it doesn't use some other version already installed.
It seems the in6: ALARM is a bug, since, it's normal ?
Another bug : +5V: +3.01 V...
The CPU temperatures seem correct.
There are ways of fine-tuning sensors so the output makes sense with your hardware.
I run the modprobe it87 as asked above
Not all processors need this module.
I will ask Barry to add the modprobe and your application...
Add them to what? BK has retired.
Posted: Wed 25 Dec 2013, 19:51
by linuxcbon
rcrsn51 wrote:I'd rather not. I slightly modify the sensors binary to be compatible with the CPUtemp script. It works better if they are packaged together. If you look in CPUtemp, you will see the full path /usr/local/bin/sensors so it doesn't use some other version already installed.
What did you modify ? Ok so there can be 2 "sensors" , one in /usr/bin and one in /usr/local/bin ?
rcrsn51 wrote:There are ways of fine-tuning sensors so the output makes sense with your hardware.
How ?
rcrsn51 wrote:Add them to what? BK has retired.
To any puppy he wants, he is still active, even retired. It doesn't matter. I can ask, he can do what he wants.
Posted: Wed 25 Dec 2013, 20:55
by rcrsn51
linuxcbon wrote:What did you modify ?
I remove the degree symbol because there were problems getting it to display correctly in non-English character sets.
Ok so there can be 2 "sensors" , one in /usr/bin and one in /usr/local/bin ?
Yes. IIRC, some Puppy builders are including the sensors package.
How ?
The procedure is described in the sensors documentation. I have never tried it.
Posted: Wed 25 Dec 2013, 21:42
by 01micko
rcrsn51 wrote:linuxcbon wrote:What did you modify ?
I remove the degree symbol because there were problems getting it to display correctly in non-English character sets.
Ok so there can be 2 "sensors" , one in /usr/bin and one in /usr/local/bin ?
Yes. IIRC, some Puppy builders are including the sensors package.
How ?
The procedure is described in the sensors documentation. I have never tried it.
IIRC, the script/source (yes I had some affect in C/C++ sources too, could have been me though) must be encoded UTF-8 for the degree symbol, however, this may fall over if the users opts for non UTF-8 locale.
Posted: Thu 09 Jan 2014, 18:53
by linuxcbon
To display correct voltage values, the software needs to be corrected with a "correction" file : /etc/sensors.conf
Those "correction factors" depend on the mother board model. People who love maths can calculate them.
Example :
Code: Select all
chip "it8718-*"
compute in3 @ * (6.8/10+1), @ / (6.8/10+1)
Posted: Fri 10 Jan 2014, 02:16
by ardvark
Hi...
Works nice, thank you!
Regards...
Posted: Mon 17 Feb 2014, 04:03
by Mercedes350se
I have a missing
libgio-2.0.so.0
Where to get it? I am using 4.1.2.
Posted: Mon 17 Feb 2014, 05:06
by ardvark
Mercedes350se wrote:I have a missing
libgio-2.0.so.0
Where to get it? I am using 4.1.2.
Hi...
Does the file below solve this issue?
Regards...
Posted: Mon 17 Feb 2014, 10:19
by Mercedes350se
Sure does. Thank you.
Interestingly if I run CPUtemp in console I get 47C but hardinfo>sensors returns 42C. Hmm.