pmcputemp -temperature monitor
pmcputemp -temperature monitor
This is pmcputemp - simple tray icon that shows CPU temperature.
see HERE for latest pets.
Translations need updating for added dialogs
New feature shows the CPU frequency in real time in the tooltip (see below)
It is the successor to tempicon which is now discontinued, but if it still works for you feel free to use it.
The old one started life as a mash up of shell scripting and C rendering the icon at first in .XPM then later in .SVG image format. Of course there is a script in that thread somewhere where there is a 'proof of concept' using technosaurus' SIT tray utility.
The all new pmcputemp (pm = poor man's) builds the icon with cairo and renders a .PNG. It's 99% C except for a once only run script to find your temperature sensor output, which in the future may be rewritten in C. For more info see my github page - https://github.com/01micko/pmcputemp, where you can find the latest source, but also I have uploaded a tarball - https://01micko.com/src/pmcputemp-0.63.tar.xz.
I have built slacko64, Tahr pets
Here is the fatdog package: https://01micko.com/fatdog64/pmcputemp- ... 6_64-1.txz (NOTE: not updated yet! NB: jamesbond will be putting latest version in FD repo)
Others are attached below.
There are NLS translations to be done/fixed UPDATE- it, fr and zh are fixed thanks to xanad, charlie6 and icake
Translators: the .pot file is in the package. Need updating for 0.63. Thank you
see HERE for latest pets.
Translations need updating for added dialogs
New feature shows the CPU frequency in real time in the tooltip (see below)
It is the successor to tempicon which is now discontinued, but if it still works for you feel free to use it.
The old one started life as a mash up of shell scripting and C rendering the icon at first in .XPM then later in .SVG image format. Of course there is a script in that thread somewhere where there is a 'proof of concept' using technosaurus' SIT tray utility.
The all new pmcputemp (pm = poor man's) builds the icon with cairo and renders a .PNG. It's 99% C except for a once only run script to find your temperature sensor output, which in the future may be rewritten in C. For more info see my github page - https://github.com/01micko/pmcputemp, where you can find the latest source, but also I have uploaded a tarball - https://01micko.com/src/pmcputemp-0.63.tar.xz.
I have built slacko64, Tahr pets
Here is the fatdog package: https://01micko.com/fatdog64/pmcputemp- ... 6_64-1.txz (NOTE: not updated yet! NB: jamesbond will be putting latest version in FD repo)
Others are attached below.
There are NLS translations to be done/fixed UPDATE- it, fr and zh are fixed thanks to xanad, charlie6 and icake
Translators: the .pot file is in the package. Need updating for 0.63. Thank you
- Attachments
-
- tooltip.png
- New feature
- (7.46 KiB) Downloaded 3535 times
-
- pmcputemp.jpg
- How it appears; goes green, then red as it gets hotter.
- (4 KiB) Downloaded 4299 times
Last edited by 01micko on Tue 09 Jun 2020, 06:47, edited 10 times in total.
Puppy Linux Blog - contact me for access
- xanad
- Posts: 400
- Joined: Fri 28 Feb 2014, 14:56
- Location: 2 locations: MonteRosa Alp and Milano
- Contact:
pmcputemp italian translation
----
.mo + .po
----
.mo + .po
- Attachments
-
- pmcputemp_it.tar.gz
- (982 Bytes) Downloaded 872 times
Last edited by xanad on Thu 26 Mar 2015, 17:40, edited 1 time in total.
[url]http://www.xanad.tk[/url] Html5 Parallax
xanad, thank you, but I need the .po file too please
Git repo is updated with Chinese .po : CN,HK,TW thanks to icake
Git repo is updated with Chinese .po : CN,HK,TW thanks to icake
Puppy Linux Blog - contact me for access
Mick,
1. rc file name is a bit odd (pcutemprc - sounds like a typo)
2. if the file in the config file cannot be read, the program goes into infinite loop. This code looks suspect:I think you should only read once; if you've got an error just show "err"or something.
3. "find /sys/devices/ -type f -name temp1_input" returns two entries, and pmcputemp.sh chooses the first one (the bad one).
The first entry cannot be read (test -r $sys returns true but read p < $sys returns error), and because of that the program goes to infinite loop. If I manually edit the conf file with the second entry, then the program works nicely.
4. When the about window is open the temp is not updated and all operations are suspended. E.g. I click on the icon, I get an about window. While the window is open, temp. is not updated. If (while the about window is still open) I click the icon again, nothing seems to happen. But as soon as I close the about window, another about window shows up. If I click the icon 3 times when the about window is shown, the about window will be shown 3 times afterwards.
1. rc file name is a bit odd (pcutemprc - sounds like a typo)
2. if the file in the config file cannot be read, the program goes into infinite loop. This code looks suspect:
Code: Select all
while(!feof(ft)) {
fscanf(ft, "%d", &temp_val);
}
3. "find /sys/devices/ -type f -name temp1_input" returns two entries, and pmcputemp.sh chooses the first one (the bad one).
Code: Select all
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/hwmon/hwmon0/temp1_input
/sys/devices/platform/coretemp.0/hwmon/hwmon1/temp1_input
4. When the about window is open the temp is not updated and all operations are suspended. E.g. I click on the icon, I get an about window. While the window is open, temp. is not updated. If (while the about window is still open) I click the icon again, nothing seems to happen. But as soon as I close the about window, another about window shows up. If I click the icon 3 times when the about window is shown, the about window will be shown 3 times afterwards.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Thank you xanad.
---------------------------------------------------------------------------------------------------------
Hopefully that kills any endless loop. Hmm.. I probably should test for more sane result, becuase we are expecting a 5 digit result. (to do)
Thanks for report!
Cheers
---------------------------------------------------------------------------------------------------------
Woops.. fixed!jamesbond wrote: 1. rc file name is a bit odd (pcutemprc - sounds like a typo)
Ah, ok, so I simplified by removing the feof call and checking the status of fscanf()jamesbond wrote: 2. if the file in the config file cannot be read, the program goes into infinite loop. This code looks suspect:I think you should only read once; if you've got an error just show "err"or something.Code: Select all
while(!feof(ft)) { fscanf(ft, "%d", &temp_val); }
Code: Select all
int success = fscanf(ft, "%d", &temp_val);
if (success < 1) {
fprintf(stderr,_("Failed to read temperature, giving up."));
exit (1);
}
Yeah this is a bit of a problem. The real solution is to go the same way as HardInfo. I'll think about that.jamesbond wrote: 3. "find /sys/devices/ -type f -name temp1_input" returns two entries, and pmcputemp.sh chooses the first one (the bad one).The first entry cannot be read (test -r $sys returns true but read p < $sys returns error), and because of that the program goes to infinite loop. If I manually edit the conf file with the second entry, then the program works nicely.Code: Select all
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/hwmon/hwmon0/temp1_input /sys/devices/platform/coretemp.0/hwmon/hwmon1/temp1_input
Should be a fairly simple fix. On to it soon. EDIT: simply switching from Xlib to gtk solves that but I will have to factor in gtk3 support, not urgent though so I'll disable gtk3 support for now.jamesbond wrote: 4. When the about window is open the temp is not updated and all operations are suspended. E.g. I click on the icon, I get an about window. While the window is open, temp. is not updated. If (while the about window is still open) I click the icon again, nothing seems to happen. But as soon as I close the about window, another about window shows up. If I click the icon 3 times when the about window is shown, the about window will be shown 3 times afterwards.
Thanks for report!
Cheers
Puppy Linux Blog - contact me for access
New version is uploaded, thanks for all translations and bug reports.
@jamesbond. Most of your bugs should be fixed now, except for the script, but at least the endless loop should not occur now.
Code: Select all
# git log --pretty
commit 206fab593452d86a97393b4cf74459e2fb5209ec
Author: 01micko <01micko@gmail.com>
Date: Fri Mar 27 12:23:41 2015 +1000
Bump version
commit 0178b12807e3a78629a47c768a012cf66c7023aa
Author: 01micko <01micko@gmail.com>
Date: Fri Mar 27 12:22:53 2015 +1000
Add check for a sane temperature value
commit 7849bb84574a3c317a00d12f6f5bfba798a52b15
Author: 01micko <01micko@gmail.com>
Date: Fri Mar 27 12:17:49 2015 +1000
pmcputemp.c: disable show_about() on click, menu only. Change reading of tem
commit d5d818215e642627958c0113e345a567af43fd09
Author: 01micko <01micko@gmail.com>
Date: Fri Mar 27 12:16:36 2015 +1000
about.c: change window from XWindow to GTK
commit e86dbb3f6fb5e89812354d5b34e9384f513c03a5
Author: 01micko <01micko@gmail.com>
Date: Fri Mar 27 12:15:32 2015 +1000
about.h: change function from show_xlib() to show_about()
commit 0a273dd6d83682e82532b94b056ef3f4008b7fed
Author: 01micko <01micko@gmail.com>
Date: Fri Mar 27 12:11:37 2015 +1000
configure: temporarily disable gtk3 build. Add .pot to install
commit 24ac0b627ef2c8f10aa9297f36b799081492c687
Author: 01micko <01micko@gmail.com>
Date: Fri Mar 27 07:01:17 2015 +1000
Update it translation : xanad
commit b2d0e5147b64e75e1e03f0d00f16c1ae987bcd9b
Author: 01micko <01micko@gmail.com>
Date: Fri Mar 27 06:52:46 2015 +1000
Fix name of rc file : jamesbond
commit 5c1a5b360c6c989b7934ebce5e5e8076fcbcceb4
Author: 01micko <01micko@gmail.com>
Date: Thu Mar 26 23:05:52 2015 +1000
Added proper Chinese translations for CN, HK and TW, removed old version. Th
Puppy Linux Blog - contact me for access
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Thanks Oscar, the packages don't have the issue, uploaded to github now.
Also fixed the link to the source in main post pointing to the latest - it's the same (ie : has the fixed script).
Also fixed the link to the source in main post pointing to the latest - it's the same (ie : has the fixed script).
Puppy Linux Blog - contact me for access
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
This is rather queer. It compiles and runs OK in Dpup Wheezy and Slacko 5.7
In Precise 5.7.1 it seems to compile OK but then when I try to run it I get a *** Stack Smashing *** issue. The version compiled in Wheezy runs in Precise with no errors.
In Precise 5.7.1 it seems to compile OK but then when I try to run it I get a *** Stack Smashing *** issue. The version compiled in Wheezy runs in Precise with no errors.
Code: Select all
# pmcputemp
loading coretemp
/sys/devices/platform/coretemp.0/temp2_input is written to /root/.config/pmcputemp
An attempt has been made to create a configuration file
*** stack smashing detected ***: pmcputemp terminated
======= Backtrace: =========
/lib/libc.so.6(__fortify_fail+0x45)[0xb6eee0e5]
/lib/libc.so.6(+0x10409a)[0xb6eee09a]
pmcputemp[0x8049760]
pmcputemp[0x804978c]
pmcputemp[0x8049fbf]
/lib/libc.so.6(__libc_start_main+0xf3)[0xb6e034d3]
pmcputemp[0x8049421]
======= Memory map: ========
08048000-0804b000 r-xp 00000000 07:01 8604 /initrd/pup_rw/usr/bin/pmcputemp
0804b000-0804c000 r-xp 00002000 07:01 8604 /initrd/pup_rw/usr/bin/pmcputemp
0804c000-0804d000 rwxp 00003000 07:01 8604 /initrd/pup_rw/usr/bin/pmcputemp
0804d000-0808f000 rwxp 00000000 00:00 0 [heap]
b671c000-b6738000 r-xp 00000000 07:00 2399 /initrd/pup_ro2/lib/libgcc_s.so.1
b6738000-b6739000 r-xp 0001b000 07:00 2399 /initrd/pup_ro2/lib/libgcc_s.so.1
b6739000-b673a000 rwxp 0001c000 07:00 2399 /initrd/pup_ro2/lib/libgcc_s.so.1
b673a000-b673c000 rwxp 00000000 00:00 0
b673c000-b6773000 r-xp 00000000 07:01 8209 /initrd/pup_rw/usr/lib/locale/en_GB/LC_CTYPE
b6773000-b6774000 r-xp 00000000 07:01 8208 /initrd/pup_rw/usr/lib/locale/en_GB/LC_NUMERIC
b6774000-b6775000 r-xp 00000000 07:01 8207 /initrd/pup_rw/usr/lib/locale/en_GB/LC_TIME
b6775000-b677a000 r-xp 00000000 07:01 8206 /initrd/pup_rw/usr/lib/locale/en_GB/LC_COLLATE
b677a000-b677b000 r-xp 00000000 07:01 8205 /initrd/pup_rw/usr/lib/locale/en_GB/LC_MONETARY
b677b000-b677c000 r-xp 00000000 07:01 8204 /initrd/pup_rw/usr/lib/locale/en_GB/LC_MESSAGES/SYS_LC_MESSAGES
b677c000-b677d000 r-xp 00000000 07:01 8202 /initrd/pup_rw/usr/lib/locale/en_GB/LC_PAPER
b677d000-b677e000 r-xp 00000000 07:01 8201 /initrd/pup_rw/usr/lib/locale/en_GB/LC_NAME
b677e000-b677f000 r-xp 00000000 07:01 8200 /initrd/pup_rw/usr/lib/locale/en_GB/LC_ADDRESS
b677f000-b6780000 r-xp 00000000 07:01 8199 /initrd/pup_rw/usr/lib/locale/en_GB/LC_TELEPHONE
b6780000-b6781000 r-xp 00000000 07:01 8198 /initrd/pup_rw/usr/lib/locale/en_GB/LC_MEASUREMENT
b6781000-b6782000 r-xp 00000000 07:01 8197 /initrd/pup_rw/usr/lib/locale/en_GB/LC_IDENTIFICATION
b6782000-b6785000 rwxp 00000000 00:00 0
b6785000-b678a000 r-xp 00000000 07:00 7002 /initrd/pup_ro2/usr/lib/libXdmcp.so.6.0.0
b678a000-b678b000 r-xp 00004000 07:00 7002 /initrd/pup_ro2/usr/lib/libXdmcp.so.6.0.0
b678b000-b678c000 rwxp 00005000 07:00 7002 /initrd/pup_ro2/usr/lib/libXdmcp.so.6.0.0
b678c000-b678e000 r-xp 00000000 07:00 7245 /initrd/pup_ro2/usr/lib/libXau.so.6.0.0
b678e000-b678f000 r-xp 00001000 07:00 7245 /initrd/pup_ro2/usr/lib/libXau.so.6.0.0
b678f000-b6790000 rwxp 00002000 07:00 7245 /initrd/pup_ro2/usr/lib/libXau.so.6.0.0
b6790000-b67b6000 r-xp 00000000 07:00 4919 /initrd/pup_ro2/lib/libexpat.so.1.5.2
b67b6000-b67b7000 ---p 00026000 07:00 4919 /initrd/pup_ro2/lib/libexpat.so.1.5.2
b67b7000-b67b9000 r-xp 00026000 07:00 4919 /initrd/pup_ro2/lib/libexpat.so.1.5.2
b67b9000-b67ba000 rwxp 00028000 07:00 4919 /initrd/pup_ro2/lib/libexpat.so.1.5.2
b67ba000-b67cd000 r-xp 00000000 07:00 4905 /initrd/pup_ro2/lib/libresolv-2.15.so
b67cd000-b67ce000 ---p 00013000 07:00 4905 /initrd/pup_ro2/lib/libresolv-2.15.so
b67ce000-b67cf000 r-xp 00013000 07:00 4905 /initrd/pup_ro2/lib/libresolv-2.15.so
b67cf000-b67d0000 rwxp 00014000 07:00 4905 /initrd/pup_ro2/lib/libresolv-2.15.so
b67d0000-b67d3000 rwxp 00000000 00:00 0
b67d3000-b67f0000 r-xp 00000000 07:00 2511 /initrd/pup_ro2/lib/libselinux.so.1
b67f0000-b67f1000 r-xp 0001c000 07:00 2511 /initrd/pup_ro2/lib/libselinux.so.1
b67f1000-b67f2000 rwxp 0001d000 07:00 2511 /initrd/pup_ro2/lib/libselinux.so.1
b67f2000-b67f5000 r-xp 00000000 07:00 2400 /initrd/pup_ro2/lib/libdl-2.15.so
b67f5000-b67f6000 r-xp 00002000 07:00 2400 /initrd/pup_ro2/lib/libdl-2.15.so
b67f6000-b67f7000 rwxp 00003000 07:00 2400 /initrd/pup_ro2/lib/libdl-2.15.so
b67f7000-b680b000 r-xp 00000000 07:00 2386 /initrd/pup_ro2/lib/libz.so.1.2.3.4
b680b000-b680c000 r-xp 00013000 07:00 2386 /initrd/pup_ro2/lib/libz.so.1.2.3.4
b680c000-b680d000 rwxp 00014000 07:00 2386 /initrd/pup_ro2/lib/libz.so.1.2.3.4
b680d000-b682c000 r-xp 00000000 07:00 7291 /initrd/pup_ro2/usr/lib/libxcb.so.1.1.0
b682c000-b682d000 r-xp 0001f000 07:00 7291 /initrd/pup_ro2/usr/lib/libxcb.so.1.1.0
b682d000-b682e000 rwxp 00020000 07:00 7291 /initrd/pup_ro2/usr/lib/libxcb.so.1.1.0
b682e000-b6836000 r-xp 00000000 07:00 6375 /initrd/pup_ro2/usr/lib/libxcb-render.so.0.0.0
b6836000-b6837000 r-xp 00008000 07:00 6375 /initrd/pup_ro2/usr/lib/libxcb-render.so.0.0.0
b6837000-b6838000 rwxp 00009000 07:00 6375 /initrd/pup_ro2/usr/lib/libxcb-render.so.0.0.0
b6838000-b6839000 rwxp 00000000 00:00 0
b6839000-b683b000 r-xp 00000000 07:00 6013 /initrd/pup_ro2/usr/lib/libxcb-shm.so.0.0.0
b683b000-b683c000 r-xp 00001000 07:00 6013 /initrd/pup_ro2/usr/lib/libxcb-shm.so.0.0.0
b683c000-b683d000 rwxp 00002000 07:00 6013 /initrd/pup_ro2/usr/lib/libxcb-shm.so.0.0.0
b683d000-b6865000 r-xp 00000000 07:00 4914 /initrd/pup_ro2/lib/libpng12.so.0.46.0
b6865000-b6866000 r-xp 00027000 07:00 4914 /initrd/pup_ro2/lib/libpng12.so.0.46.0
b6866000-b6867000 rwxp 00028000 07:00 4914 /initrd/pup_ro2/lib/libpng12.so.0.46.0
b6867000-b68fc000 r-xp 00000000 07:00 7011 /initrd/pup_ro2/usr/lib/libfreetype.so.6.8.0
b68fc000-b6900000 r-xp 00094000 07:00 7011 /initrd/pup_ro2/usr/lib/libfreetype.so.6.8.0
b6900000-b6901000 rwxp 00098000 07:00 7011 /initrd/pup_ro2/usr/lib/libfreetype.so.6.8.0
b6901000-b6994000 r-xp 00000000 07:00 7226 /initrd/pup_ro2/usr/lib/libpixman-1.so.0.24.4
b6994000-b6998000 r-xp 00092000 07:00 7226 /initrd/pup_ro2/usr/lib/libpixman-1.so.0.24.4
b6998000-b6999000 rwxp 00096000 07:00 7226 /initrd/pup_ro2/usr/lib/libpixman-1.so.0.24.4
b6999000-b69a0000 r-xp 00000000 07:00 2517 /initrd/pup_ro2/lib/librt-2.15.so
b69a0000-b69a1000 r-xp 00006000 07:00 2517 /initrd/pup_ro2/lib/librt-2.15.so
b69a1000-b69a2000 rwxp 00007000 07:00 2517 /initrd/pup_ro2/lib/librt-2.15.so
b69a2000-b69a3000 rwxp 00000000 00:00 0
b69a3000-b69dd000 r-xp 00000000 07:00 4885 /initrd/pup_ro2/lib/libpcre.so.3.12.1
b69dd000-b69de000 r-xp 00039000 07:00 4885 /initrd/pup_ro2/lib/libpcre.so.3.12.1
b69de000-b69df000 rwxp 0003a000 07:00 4885 /initrd/pup_ro2/lib/libpcre.so.3.12.1Aborted
#
Oscar in England
hey ally
Make sure you didn't put the binary in ~/Startup. If you did put it back in /usr/bin.
FatDog-700 comes with a Startup folder in /etc/xdg/Startup. Use that one. Make a symlink either by opening /usr/bin and /etc/xdg/Startup and dragging pmcputemp into /etc/xdg/Startup and choosing 'symlink' from the rox menu.
Otherwise run this-
Restart X and you should be ok, if not try a reboot. If not again try reinstalling the program (uninstall first).
eg:
----------------------------------------------------------------------------------------------------------
Hi Oscar.
Interesting problem. Ultimately it indicates a bug in the program, usually not allocating enough space in memory for a variable. See http://www.drdobbs.com/security/anatomy ... /240001832. I'll have to find the bug and squash it. I wonder if it happens in tahr? I built the binary for tahr in a VM, which doesn't have a temp sensor so I couldn't test it.
As for it only occurring when compiled in Ubuntu, it's because they have a permanent flag set to gcc set >> -fstack-protector. You could try adding -fno-stack-protector to the CFLAGS var in the Makefile which will make the binary build but obviously doesn't fix the bug. ref << http://www.thegeekstuff.com/2013/02/sta ... tacks-gcc/.
LATER
Oscar, I did a bare metal install in tahr (see rant) and it exhibits the bug too. I've narrowed it down to the paint_icon() function because if you comment the 2 paint_icon() calls and have an icon already in the config dir the program runs fine albeit without updating the temperature. (caveat: I did have to bump up the allocation for a couple of the char[] values too, so it wasn't only there).
-----------------------------------------------------------------------------------------------------------
<rant>
How come, after 45 downloads of the tahr version no one piped up and said "this program is shit, doesn't work".
No wonder developers like tempestuous and rcrsn51 pull there programs after a 20 or so downloads and no reports. I can totally understand why they get pissed off. Used to piss me off getting the same 10 or 20 testers of my isos when there were literally hundreds of downloads according to the server logs.
Does anyone wonder why motivation is thin around here?
</rant>
tahr version is pulled for now.
Make sure you didn't put the binary in ~/Startup. If you did put it back in /usr/bin.
FatDog-700 comes with a Startup folder in /etc/xdg/Startup. Use that one. Make a symlink either by opening /usr/bin and /etc/xdg/Startup and dragging pmcputemp into /etc/xdg/Startup and choosing 'symlink' from the rox menu.
Otherwise run this-
Code: Select all
cd /etc/xdg/Startup/
ln -s ../../../usr/bin/pmcputemp . #that is a dot after a space on the end of this line
cd -
eg:
Code: Select all
removepkg pmcputemp-0.50-x86_64-1.txz
installpkg pmcputemp-0.50-x86_64-1.txz
Hi Oscar.
Interesting problem. Ultimately it indicates a bug in the program, usually not allocating enough space in memory for a variable. See http://www.drdobbs.com/security/anatomy ... /240001832. I'll have to find the bug and squash it. I wonder if it happens in tahr? I built the binary for tahr in a VM, which doesn't have a temp sensor so I couldn't test it.
As for it only occurring when compiled in Ubuntu, it's because they have a permanent flag set to gcc set >> -fstack-protector. You could try adding -fno-stack-protector to the CFLAGS var in the Makefile which will make the binary build but obviously doesn't fix the bug. ref << http://www.thegeekstuff.com/2013/02/sta ... tacks-gcc/.
LATER
Oscar, I did a bare metal install in tahr (see rant) and it exhibits the bug too. I've narrowed it down to the paint_icon() function because if you comment the 2 paint_icon() calls and have an icon already in the config dir the program runs fine albeit without updating the temperature. (caveat: I did have to bump up the allocation for a couple of the char[] values too, so it wasn't only there).
-----------------------------------------------------------------------------------------------------------
<rant>
How come, after 45 downloads of the tahr version no one piped up and said "this program is shit, doesn't work".
No wonder developers like tempestuous and rcrsn51 pull there programs after a 20 or so downloads and no reports. I can totally understand why they get pissed off. Used to piss me off getting the same 10 or 20 testers of my isos when there were literally hundreds of downloads according to the server logs.
Does anyone wonder why motivation is thin around here?
</rant>
tahr version is pulled for now.
Puppy Linux Blog - contact me for access
Bugfixed Tahr version is posted. Thanks to @OscarTalks who had enough balls to say my shit program did not work!
Oscar, all sources uploaded to usual locations.
------------------------------
Footnote:
That "bug" is exactly why I don't use Ubuntu. They use the -fstack-protector as a pretense for "security". I call bullshit on that one. To fix the bug, and no other action necessary in this particular instance, I had to move a local var to global. Right. That's not Ubuntu's fault, it's gcc's, but you would think, with their wealth of resources, that they'd test something as simple as that eh?
Welcome to GNU..
Oscar, all sources uploaded to usual locations.
------------------------------
Footnote:
That "bug" is exactly why I don't use Ubuntu. They use the -fstack-protector as a pretense for "security". I call bullshit on that one. To fix the bug, and no other action necessary in this particular instance, I had to move a local var to global. Right. That's not Ubuntu's fault, it's gcc's, but you would think, with their wealth of resources, that they'd test something as simple as that eh?
Welcome to GNU..
Puppy Linux Blog - contact me for access
Temp now comes, ... but goes?
G'day 01micko,
<embarrassed>
I tried your latest cpu-temp yesterday after downloading it (.50) a day or so ago, and saw nothing happening, so thought it was something I had missed or it was the old-ish desktop I'm using (a work discard).
</embarrassed>
Read Oscar's post so tried to run 0.50 from a terminal and got the same response as he did.
Have now downloaded and run 0.51 (clicked the .pet) and nothing happened.
Went to a terminal and ran pmcputemp and the temp icon appeared on the task bar. A comfortable 34C.
Closed the terminal and the temp icon also disappeared .
Somehow I think this Cheshire-Cat behaviour is not what you intended (given all your very good earlier, rich-man's cpu-temp pets)?
I'm running this on Dpup Wheezy-3.5.2.11, by the way.
David S.
<embarrassed>
I tried your latest cpu-temp yesterday after downloading it (.50) a day or so ago, and saw nothing happening, so thought it was something I had missed or it was the old-ish desktop I'm using (a work discard).
</embarrassed>
Read Oscar's post so tried to run 0.50 from a terminal and got the same response as he did.
Have now downloaded and run 0.51 (clicked the .pet) and nothing happened.
Went to a terminal and ran pmcputemp and the temp icon appeared on the task bar. A comfortable 34C.
Closed the terminal and the temp icon also disappeared .
Somehow I think this Cheshire-Cat behaviour is not what you intended (given all your very good earlier, rich-man's cpu-temp pets)?
I'm running this on Dpup Wheezy-3.5.2.11, by the way.
David S.
Hi David.
Don't mind my rant
To start the prog when X starts drag the binary from /usr/bin to /root/Startup and choose 'symlink' if in normal Tahr Puppy, applies to slacko too.
Or, if you want to be more adventurous, create a text file named pmcputemp.desktop in /root/.config/autostart containing the following.
The .desktop method only applies to recent puppies as in >slacko-5.7 and tahr pup.
A universal pinstall to cover older (woof2) and newer (woof-ce) will be supplied in upcoming pet versions. and a puninstall to clean up after.
Don't mind my rant
To start the prog when X starts drag the binary from /usr/bin to /root/Startup and choose 'symlink' if in normal Tahr Puppy, applies to slacko too.
Or, if you want to be more adventurous, create a text file named pmcputemp.desktop in /root/.config/autostart containing the following.
Code: Select all
[Desktop Entry]
Encoding=UTF-8
Type=Application
NoDisplay=true
Name=pmcputemp
Exec=pmcputemp
A universal pinstall to cover older (woof2) and newer (woof-ce) will be supplied in upcoming pet versions. and a puninstall to clean up after.
Puppy Linux Blog - contact me for access
Icons now with binary to Startup
G'day 01micko,
Thanks for the quick reply.
Just for the record, I'm now in slacko-5.9.3 and had the same issue again with 0.51 - nothing with the simple click-on-the-pet and a Cheshire-Cat behaviour with the temp icon running 0.51 from the console.
The message on the console was:
Now I'll try dragging the /usr/bin binary to the /root/Startup and see what happens.
David S.
[Follow-up]
Tried both Slacko-5.9.3 and Dpup Wheezy with the binary pmcputemp in the Startup directory.
Both working....but giving quite different values:
Wheezy = 36
Slacko = 75
I recall something similar with some older cpu temp apps. It looked like there were different temperatures reported because the software in different Pups was looking at different read-outs. Some older (rich-man's) temp monitors had a right-click "more" option which displayed more machine temperatures.
How can I check which is which, as I'd be surprised if slacko is truly "hotter" than wheezy.
David S.
Thanks for the quick reply.
Just for the record, I'm now in slacko-5.9.3 and had the same issue again with 0.51 - nothing with the simple click-on-the-pet and a Cheshire-Cat behaviour with the temp icon running 0.51 from the console.
The message on the console was:
but without a final # line. X-ing the console and the temp icon also went. I hope it means something to you.# pmcputemp
loading coretemp
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/hwmon/hwmon0/temp1_input is written to /root/.config/pmcputemp
An attempt has been made to create a configuration file
Now I'll try dragging the /usr/bin binary to the /root/Startup and see what happens.
David S.
[Follow-up]
Tried both Slacko-5.9.3 and Dpup Wheezy with the binary pmcputemp in the Startup directory.
Both working....but giving quite different values:
Wheezy = 36
Slacko = 75
I recall something similar with some older cpu temp apps. It looked like there were different temperatures reported because the software in different Pups was looking at different read-outs. Some older (rich-man's) temp monitors had a right-click "more" option which displayed more machine temperatures.
How can I check which is which, as I'd be surprised if slacko is truly "hotter" than wheezy.
David S.
David,
That message is expected. It happens every time on the first run unless you installed over the top of an old version. As said, I'll put an install script in the next version. Oversight.
try these commands (I've left the output so you can see what to expect)
The temp1_input should be the one I'm after and show correct temp, or could be temp2_input since your processor is intel (loads coretemp module). You might see temp3 and so on depending on number of cores, but the first one usually heats up the most. As you can see mine is 41°. The "find" command will list them in the same order. You can manually copy that over the entry in the configuration file at /root/.config/pmcputemp/pmcputemprc . I'm working on a more robust test.
BTW, sometimes different kernels can react strangely with CPUs and cause high temps, I have seen it myself on numerous occasions and usually I change kernels or use a different puppy version.
That message is expected. It happens every time on the first run unless you installed over the top of an old version. As said, I'll put an install script in the next version. Oversight.
try these commands (I've left the output so you can see what to expect)
Code: Select all
# find /sys -type f -name 'temp*'
/sys/devices/pci0000:00/0000:00:18.3/temp1_crit
/sys/devices/pci0000:00/0000:00:18.3/temp1_crit_hyst
/sys/devices/pci0000:00/0000:00:18.3/temp1_input
/sys/devices/pci0000:00/0000:00:18.3/temp1_max
# find /sys -type f -name 'temp*' -exec cat '{}' \;
72000
70000
41375
70000
#
The temp1_input should be the one I'm after and show correct temp, or could be temp2_input since your processor is intel (loads coretemp module). You might see temp3 and so on depending on number of cores, but the first one usually heats up the most. As you can see mine is 41°. The "find" command will list them in the same order. You can manually copy that over the entry in the configuration file at /root/.config/pmcputemp/pmcputemprc . I'm working on a more robust test.
BTW, sometimes different kernels can react strangely with CPUs and cause high temps, I have seen it myself on numerous occasions and usually I change kernels or use a different puppy version.
Puppy Linux Blog - contact me for access
0.60 is out with pinstall (and puninstall)
delete /root/.config/pmcputemp before install.
Please uninstall old version with package manager.
Sources and github updated.
Thanks to the Chatswood connections of davids45 and jamesbond
delete /root/.config/pmcputemp before install.
Please uninstall old version with package manager.
Sources and github updated.
Thanks to the Chatswood connections of davids45 and jamesbond
Code: Select all
commit 1a1c0fb0550de2ca11c7299b17c219ef5be86c88
Author: 01micko <01micko@gmail.com>
Date: Sun Mar 29 17:59:08 2015 +1000
bump version to 0.60
commit a4bedd0c450092a3f9dd0c75d46a8456fac87aed
Author: 01micko <01micko@gmail.com>
Date: Sun Mar 29 17:58:16 2015 +1000
pmcputemp.c : add more checks and bail out when neededXy
commit 6cb82f4eebfb4704a1b2fd7074dc7a83d7697717
Author: 01micko <01micko@gmail.com>
Date: Sun Mar 29 17:56:46 2015 +1000
update starter script : jamesbondXy
commit e2183ae8faf906f1ebac3e3b0642a87e4fd56ebf
Author: 01micko <01micko@gmail.com>
Date: Sat Mar 28 21:44:48 2015 +1000
Bump version a minor point
commit fac7ef4c3b33fe8633ae38a65f81caa2fc8b1973
Author: 01micko <01micko@gmail.com>
Date: Sat Mar 28 21:37:24 2015 +1000
pmcputemp.c: bugfix for ubuntu based distros concerning stack errors. This t
commit 4d3bc82deda5baa977ee6e4fde7a952fb80fd18a
Author: 01micko <01micko@gmail.com>
Date: Sat Mar 28 21:35:43 2015 +1000
Bugfix configure: remove .pot from installation
commit afc4d024b4686910fe8edb8609a90f6184fb3a28
Author: 01micko <01micko@gmail.com>
Date: Fri Mar 27 20:19:41 2015 +1000
Update script re commit b2d0e5147b64e75e1e03f0d00f16c1ae987bcd9b
Puppy Linux Blog - contact me for access