Puppy Linux Discussion Forum

[davids45]

G'day 01micko,

New install of Quirky-7.0.3 (32 bit version) produced a pink icon reading around 62C.

Running your script to see full temperature details:

[01micko]

New version posted - see main post

[davids45]

G'day 01micko,

I have installed pmcputemp-0.61 in four Full Pups and get the same value near enough .

F'rinstance here's a shot of my Slacko Full, where I included the lmsensors output and a bodgied-up Temp-cpu widget all of which seem to agree . The /root/.config/pmcputemp file is also in the screenshot.

'Sensors' output describes 'temp1' as the graphics card temp? - the same as your previous scripts I tried on this computer.

I will try pmcputemp-0.61 on some other computers around here when I get the time.

Wonder what others will find on other machines?

Thanks for the personalised app.

David S.
(A poor-man )

[01micko]

Well David, looks like we (finally!) may have sorted it out for you.


New version 0.63 .. see main post.

[davids45]

G'day 01micko,

I have quickly deleted the old /root/.config/pmcputemp directory for 0.61 and installed 0.63 to several full Pups.

Task-bar display was consistent (blue, about "32C" which is about 15C above ambient here)
The cpu core frequencies given in the "hover-box" seemed correct as one did occasionally change as I watched.
As a retired scientist, I could quibble with the meaningfulness of three decimal places shown for the core frequencies - surely to the nearest MHz is adequate (unless it's too difficult to cull the probably superfluous post-decimal zeros)?

I will try 0.63 on a different old desktop in the attic when I get the chance. It ran 0.61 OK, so should be good with 0.63.

[off-topic] "Interestingly" this attic computer gives a more informative 'sensors' output than the HP I'm now on. I'll try your scripts too to probe this computer.
I'm trying to create a working generic version of the Temp_cpu widget, based on lmsensors & pwidgets, but suspect each computer/motherboard/cpu/kernel/? will need tailoring by its user because of the variable responses by each computer/motherboard/cpu/etc to requests for hardware outputs from lmsensors or similar. [/off-topic]

Thanks for your persistence,
David S.

[OscarTalks]

Thought I would report some findings with pmcputemp-0.63 compiled from source in Dpup Wheezy 3.5.2.11 remastered.

Was given an old desktop yesterday. AMD Duron Spitfire CPU running at just under 900 MHz with SiS chipset MoBo. 256 MB RAM plus 1.5 GB of swap which I created in the 20 GB HD. Frugal install of above Pup in ext3 partition in the remainder of the HD.

Initial try of pmcputemp did not work, got the "Not working on your system" window, but I had seen some temperature readouts in the bios and when I ran Radky's PupSysinfo > devices > sensors it gave me 3 CPU temperature readouts.

I investigated the loaded modules and it looks like PupSysinfo is modprobing 5 modules. Is that possible? They are:-

hwmon
hwmon_vid
it87
k8temp
k10temp

These modules are not loaded at normal boot but after running PupSysinfo I am able to try pmcputemp again and get it to work.

The temp1_input and temp2_input and temp3_input files become available in a directory /sys/devices/platform/it87.656
Without these modules the entire it87.656 directory does not exist.
Looks like the it87 hardware monitoring driver module is needed

If I add those 5 modules via boot manager I can then have pmcputemp start with a script in /root/Startup and all seems fine. Maybe this will offer a suggestion for something that can go into a future version of pmcputemp.

By the way, this is a puny old single-core CPU so if temp1 is the readout we want then do we know what temp2 and temp3 actually are?

[gcmartin]

Had "pmcputemp" report discrepancies reported on the LxPUP64 thread.

So, Ran these commands on same DELL AIO desktop with LxPUP64.

[nilsonmorales]

For spanish users

[01micko]

@nilsonmorales - thanks! However your pet doesn't include the .po file. Could you please post one so I can include it in the git source code. TIA.

-----------------------------------------------------

@gcmartin - intels are so inconsistent! At least with AMD i have found only one inconsistency, reported by Oscar above

Please try the attached script. Unzip - make executable - overwrite the existing version in /usr/bin/

-----------------------------------------------------

@davids45 - the 3 decimal resolution stays - see GC's pic in his link for why

EDIT: attachment fixed, sorry about that

-----------------------------------------------------

@OscarTalks - try the script attached on a clean boot (ie: drop all your relevant module loading in bootmanager). I've added it87 to my modprobe loop so hopefully that picks up the dependent modules too.

-

Thanks @all.

[nilsonmorales]

01micko Im sorry, forget the .po

[01micko]

Thanks nilsonmorales

-----------------------------------------------

I have pushed the translation and some small changes to github, including the script change. Oscar, you may want to grab that version. I haven't updated packages yet and won't until I get some feedback from the script change.

[OscarTalks]

I will try the script from Github if it is modified. The one from the forum did give me an error in line 12 when run from terminal.

[01micko]

Hi Oscar!

Thanks for testing and sorry for messing up the script.. fixed now. You did the right thing fixing those bugs and continuing. The module *should* load, or at least try to load.

Was the terminal some gdkpixbuf error? If so it's nothing to do with the script, that's a bug in pmcputemp if there is no icon present, a timing error which doesn't happen all the time, and it only happens on first run before the /root/.config/pmcputemp directory is created. It's fixed at github, but I want to see if it works for you before I post a new version.

[OscarTalks]

Something is still not quite right with it. As it stands it loads k10temp (and hwmon) but not it87 or the other 2 modules (hwmon_vid and k8temp) so it still does not work.

I don't really know very much about the code, but just poking around I find that all 5 modules load and it appears to work if I just comment out the break and continue lines.

The terminal error I mentioned was just the missing characters it complained about when I just ran the script on its own from terminal but that is OK now. The gdkpixbuf thing also happens on first run but if you have now fixed that then it is just the module loading that still needs a tweak I guess.

[01micko]