@smokey01
710 is installed on USB 3.1 memstick, (see earlier post), on ext4 partition, all in accordance with jb's instructions.
@SFR
Thanks for your intervention. After the temp icon had already disappeared in this session, I relaunched it from a terminal. A few minutes later it disappeared again. The terminal output is as follows:
Fatdog64-710 Final [4 Dec 2016]
Pmcputemp
- Attachments
-
- pmcputemp-terminal-message.png
- (10.6 KiB) Downloaded 636 times
@Yoliano: Looks like Mick set the max. allowed temperature to 99°, whereas it actually can get higher (e.g. on my Acer netbook TJMax is 105°).
I've increased it to 150°, see if it works reliably now.
Btw, there's also a min. limit (10°), but I didn't touch it, because it seems to be max's issue in your case.
Greetings!
I've increased it to 150°, see if it works reliably now.
Btw, there's also a min. limit (10°), but I didn't touch it, because it seems to be max's issue in your case.
Greetings!
- Attachments
-
- pmcputemp-0.63-x86_64-1.txz.gz
- NOTE: Remove fake .gz extension!
MD5: 7e29b070e234e49dc909288b8a720206 pmcputemp-0.63-x86_64-1.txz - (11.8 KiB) Downloaded 92 times
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
Pmcputemp
@smokey01
Many thanks for your help, anyway. It encouraged me to keep trying, which was a very valuable stimulus.
@SFR
Thanks indeed for your gracious gift of adjusted software. I downloaded it and removed the false .gz. Using gslapt, I uninstalled the existing version. Then I installed your adjusted version and launched it in a terminal. The Temp Icon appeared in the tray. Left PC running and went away for twenty minutes to have a coffee. Returned to find that the Temp Icon had disappeared! The terminal output was exactly the same as that posted previously. Launched it again and commenced typing this post. I happened to glance at the Icon and saw it disappear, a few moments ago. So no luck, I regret to have to tell you.
For your information, my PC is a Toshiba Satellite 17" Laptop, Model: C75D-B7215, with AMD A8 Quadcore processor, 8GB Ram, 1 TB HD. It is about 2 years old. It's a good machine in every way and Fd64-710 sits on it very happily and delivers a smooth and fast performance, - except for this little minor glitch! The strange thing is that Pmcputemp functioned perfectly for about six weeks after first installing 710, (previously using 702), then suddenly started this random exiting. Something must have changed, although I have not observed any other signs of change in the performance of my PC.
I am surprised at the magnitude of the temperatures that you mention in your last post. In my observation of the temps. presented by the Pmcputemp Icon, I have seen:
Immediately after Boot: 39/40 degrees.
After heavy cpu load session: 53/55 degrees. (This is maximum).
Average session: 46/49 degrees.
But I can understand that rapid, transient, high temperatures could occur under certain conditions, but are so quickly cooled that they don't get presented by the Icon. Putting two fingers in front of the cooling air vent tells me that the cooling air temperature does indeed change very quickly, both up and down. Just an observation!
I don't know if there are any other avenues to explore in this matter, so I place myself in your hands. But thank you very much indeed for your dedicated help in providing this experiment. I appreciate it very much.
Many thanks for your help, anyway. It encouraged me to keep trying, which was a very valuable stimulus.
@SFR
Thanks indeed for your gracious gift of adjusted software. I downloaded it and removed the false .gz. Using gslapt, I uninstalled the existing version. Then I installed your adjusted version and launched it in a terminal. The Temp Icon appeared in the tray. Left PC running and went away for twenty minutes to have a coffee. Returned to find that the Temp Icon had disappeared! The terminal output was exactly the same as that posted previously. Launched it again and commenced typing this post. I happened to glance at the Icon and saw it disappear, a few moments ago. So no luck, I regret to have to tell you.
For your information, my PC is a Toshiba Satellite 17" Laptop, Model: C75D-B7215, with AMD A8 Quadcore processor, 8GB Ram, 1 TB HD. It is about 2 years old. It's a good machine in every way and Fd64-710 sits on it very happily and delivers a smooth and fast performance, - except for this little minor glitch! The strange thing is that Pmcputemp functioned perfectly for about six weeks after first installing 710, (previously using 702), then suddenly started this random exiting. Something must have changed, although I have not observed any other signs of change in the performance of my PC.
I am surprised at the magnitude of the temperatures that you mention in your last post. In my observation of the temps. presented by the Pmcputemp Icon, I have seen:
Immediately after Boot: 39/40 degrees.
After heavy cpu load session: 53/55 degrees. (This is maximum).
Average session: 46/49 degrees.
But I can understand that rapid, transient, high temperatures could occur under certain conditions, but are so quickly cooled that they don't get presented by the Icon. Putting two fingers in front of the cooling air vent tells me that the cooling air temperature does indeed change very quickly, both up and down. Just an observation!
I don't know if there are any other avenues to explore in this matter, so I place myself in your hands. But thank you very much indeed for your dedicated help in providing this experiment. I appreciate it very much.
Hmm, this error message can appear only in one of two conditions: raw temperature value is less than 10000 or greater than 100000 (or 150000 with my patch).
So, maybe indeed it's a kind of unusually low/high spike in your hardware...
To know for sure, please run the attached debug packgage in terminal.
It's the original version with added debug statement, so we'll see what's the actual reading right before it exits.
Also, I've rewritten my previous patch, so now it won't exit anymore, even if the value is out of range (will be clipped instead).
Please try it after the debug one is finished.
Greetings!
So, maybe indeed it's a kind of unusually low/high spike in your hardware...
To know for sure, please run the attached debug packgage in terminal.
It's the original version with added debug statement, so we'll see what's the actual reading right before it exits.
Also, I've rewritten my previous patch, so now it won't exit anymore, even if the value is out of range (will be clipped instead).
Please try it after the debug one is finished.
Greetings!
- Attachments
-
- pmcputemp-0.63_debug-x86_64-1.txz.gz
- NOTE: Remove fake .gz extension!
MD5: 018bfa872ce1734020d61531dd90e815 pmcputemp-0.63_debug-x86_64-1.txz - (11.69 KiB) Downloaded 69 times
-
- pmcputemp-0.63-x86_64-1.txz.gz
- NOTE: Remove fake .gz extension!
MD5: e62814551135b948c362638b8de05cd5 pmcputemp-0.63-x86_64-1.txz - (11.85 KiB) Downloaded 87 times
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
Pmcputemp
@SFS
Thank you very much for your new resources. Before using them, I deleted all previous pmcputemp files, using gslapt & pfind. Cleared the decks! Made a fresh start, installed only your debug version. Ran it from Terminal and waited. Icon disappeared. Debug output OK and last page copied below. It looks as if the temp. sensor stops sending it's signal. Perhaps the sensor has a dodgy circuit component that results in a random, intermittent connection. Maybe you have a better explanation.
After that, I uninstalled the debug version and installed your version with the second patch. Ran it from a Terminal. No messages returned. It is running now as I type. It has been running for about 35 mins. and continues to display the varying core temperature. My impression is that it is more stable. It has already run longer than any of the recent, previous versions. Which tends to negate my theory above! Clearly, if the temperature display remains faithful and does not disappear, I am going to have to conduct a longer term test and report back to you, perhaps in a few days.
Look forward to hearing your conclusions. Thanks again for your most valuable help.
Still displaying!
Cheers.
Thank you very much for your new resources. Before using them, I deleted all previous pmcputemp files, using gslapt & pfind. Cleared the decks! Made a fresh start, installed only your debug version. Ran it from Terminal and waited. Icon disappeared. Debug output OK and last page copied below. It looks as if the temp. sensor stops sending it's signal. Perhaps the sensor has a dodgy circuit component that results in a random, intermittent connection. Maybe you have a better explanation.
After that, I uninstalled the debug version and installed your version with the second patch. Ran it from a Terminal. No messages returned. It is running now as I type. It has been running for about 35 mins. and continues to display the varying core temperature. My impression is that it is more stable. It has already run longer than any of the recent, previous versions. Which tends to negate my theory above! Clearly, if the temperature display remains faithful and does not disappear, I am going to have to conduct a longer term test and report back to you, perhaps in a few days.
Look forward to hearing your conclusions. Thanks again for your most valuable help.
Still displaying!
Cheers.
- Attachments
-
- pmcputemp-debug.png
- (59.15 KiB) Downloaded 449 times
That's more or less what I was expecting, but the other way around - the "out of range" reading was 0 and not above 100000.
Hard to tell why's that happening, maybe some small glitch in the sensor..?
The 2nd revision of my patch (debugless, btw, that's why there's no output in the terminal) was designed not to exit, no matter what value it gets from sensors, so it can handle that 0 well and move on.
Anyway, glad we managed to sort it out.
Greetings!
Hard to tell why's that happening, maybe some small glitch in the sensor..?
The 2nd revision of my patch (debugless, btw, that's why there's no output in the terminal) was designed not to exit, no matter what value it gets from sensors, so it can handle that 0 well and move on.
Anyway, glad we managed to sort it out.
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
@SFR,
Your debugless version is now steadily displaying in my tray, but the value displayed after startup is 10 degrees, which is implausible on fundamental grounds, and explains why it was exiting.
This is on a desktop with an AMD A10-5800K quad-core processor in an FM2 socket on an Asus F2A85-M board.
Sorry I don't have time to do much debugging. I'm getting ready to move house, and with my collection of stuff this is a major problem.
Your debugless version is now steadily displaying in my tray, but the value displayed after startup is 10 degrees, which is implausible on fundamental grounds, and explains why it was exiting.
This is on a desktop with an AMD A10-5800K quad-core processor in an FM2 socket on an Asus F2A85-M board.
Sorry I don't have time to do much debugging. I'm getting ready to move house, and with my collection of stuff this is a major problem.
The cpu temperature conundrum is as old as the hills/286, filling many tomes! They used to stick a flexi thermocouple under the base, inside the centre of the socket ,so that it brushed onto the underside of the cpu case. Some folks smeared it with HS compound to get better contact. Loads of reports, loads of different values, and, of course, not all cpu s built the same even back then. Furthermore, the recorded temperature only related to the outside of the cpu encapsulation. So one of the fabs (might've Texas?) had the great idea of putting the sensor inside the case; others followed. It wasn't clear what the nature of the sensor was, where it was sited, what measuring algorithm was in FW, and, most importantly, how and where it was interrogated, i.e some did it in BiOS, others in the OS SW, some both - giving different answers. Everyone always got different answers, anyway. Next they incorporated an extra diode within the main cpu design. There was a short hiatus during which most people either got the same answer or were happy with what they saw. Notwithstanding, most of the intangibles were still present to some extent. As Mr Moore's Law progressed and features became smaller, temperature became much more relevant. Intel had even more dramatic design failures. [Probably no excuse in their case as they doubtless have access to s.o.t.a. ir and other more direct means of sensing the internal temperatures in the lab, although there was a period when they released designs with amazing egg-boiling external temperatures.] Silver dag, solid copper HSF s weighing massive amounts, water-cooling, all saw service along the track until we had the advent of multiple cores, presently arriving at up to eight being switched in and out in FW according to function, demand and a plethora of determinants. I've lost sight of where the diode or diodes are located in which core or cores and how they're accessed and how the temperature or temperatures are interpreted or interpolated in SW??
Most of the intangibles still remain, my reported T s seem to be diminishing in both SW reports and by touch of the finger tip. But with features down to 14microns, they have to run cool(er) because those junctions are still alloys, by definition; silicon melts at 1683K, but alloys take a steep dive towards the eutectic low. If line widths get much smaller, either we'll hit the Uncertainty Principle (!) or need a bucket of liqHe. They say it might be cooler on Mars...
Most of the intangibles still remain, my reported T s seem to be diminishing in both SW reports and by touch of the finger tip. But with features down to 14microns, they have to run cool(er) because those junctions are still alloys, by definition; silicon melts at 1683K, but alloys take a steep dive towards the eutectic low. If line widths get much smaller, either we'll hit the Uncertainty Principle (!) or need a bucket of liqHe. They say it might be cooler on Mars...
That 10° lasts only for some initial period of time right after startup or is it permanent?prehistoric wrote:@SFR,
Your debugless version is now steadily displaying in my tray, but the value displayed after startup is 10 degrees, which is implausible on fundamental grounds, and explains why it was exiting.
This is on a desktop with an AMD A10-5800K quad-core processor in an FM2 socket on an Asus F2A85-M board.
Sorry I don't have time to do much debugging. I'm getting ready to move house, and with my collection of stuff this is a major problem.
If the latter, do you get normal readings if you use
Code: Select all
sensorsNo rush, take your time.
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
Hello,
Just did the step from FD631 to 710. Everything's OK so far.
Has someone tried to do a MyPaint (1.2) package for FD710? I am stuck with some unresolvable error messages, claiming that a pygtkcompat cannot be found, when it is actually there. Some version conflict within Python maybe? IDK, given up on it, it's not that important.
Is there a distribution where one could scavenge packages? Or is it more or less 'compile yourself'?
Hanvon graphics tablet works, after compiling the Hanvon driver. The included Hanwang.ko does not work (and never did for the ArtMaster tablet).
Stellarium and Celestia SFS from 631 work.
Cheers
Norman
Just did the step from FD631 to 710. Everything's OK so far.
Has someone tried to do a MyPaint (1.2) package for FD710? I am stuck with some unresolvable error messages, claiming that a pygtkcompat cannot be found, when it is actually there. Some version conflict within Python maybe? IDK, given up on it, it's not that important.
Is there a distribution where one could scavenge packages? Or is it more or less 'compile yourself'?
Hanvon graphics tablet works, after compiling the Hanvon driver. The included Hanwang.ko does not work (and never did for the ArtMaster tablet).
Stellarium and Celestia SFS from 631 work.
Cheers
Norman
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
The reading seems permanent. Here's what I get from sensorsSFR wrote:...
That 10° lasts only for some initial period of time right after startup or is it permanent?
If the latter, do you get normal readings if you usecommand?Code: Select all
sensors
...
Code: Select all
# sensors
radeon-pci-0008
Adapter: PCI adapter
temp1: +2.0°C (crit = +120.0°C, hyst = +90.0°C)
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +6.1°C (high = +70.0°C)
(crit = +70.0°C, hyst = +69.0°C)Such low readings seem to be quite common for k10temp:
https://bbs.archlinux.org/viewtopic.php?id=208303 wrote:k10temp-pci-00c3
Adapter: PCI adapter
temp1: +11.0°C (high = +70.0°C)
(crit = +80.0°C, hyst = +77.0°C)
https://forums.opensuse.org/showthread.php/497668-k10temp-reports-impossibly-low-temperatures wrote:k10temp-pci-00c3
Adapter: PCI adapter
temp1: +12.0°C (high = +70.0°C)
(crit = +90.0°C, hyst = +87.0°C)
Greetings!https://askubuntu.com/questions/254305/what-is-my-cpu-temperature wrote:k10temp-pci-00c3
Adapter: PCI adapter
temp1: +7.4 C (high = +70.0 C)
(crit = +90.0 C, hyst = +87.0 C)
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
Well, it appears so, but (at least in case of k10temp; coretemp and even k8temp seem to be more realistic) those values have not much to do with an actual, physical temperature:
Greetings!
Bottom line is: as long as it's below high/crit, it's ok, regardless how weird it looks. They're just numbers...https://www.kernel.org/doc/Documentation/hwmon/k10temp wrote:Tctl is the processor temperature control value, used by the platform to control cooling systems. Tctl is a non-physical temperature on an arbitrary scale measured in degrees. It does _not_ represent an actual physical temperature like die or case temperature. Instead, it specifies the processor temperature relative to the point at which the system must supply the maximum cooling for the processor's specified maximum case temperature and maximum thermal power dissipation.
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
I can't remember if anyone tried to do a MyPaint package. You can check the official and contributed package repositories with the Gslapt package manager. Start the Fatdog Control Panel, select the System tab, double click the Gslapt icon, press Ctrl+P to edit preferences, select the Source tab and add repositories (mine lists three repos: http://distro.ibiblio.org/fatdog/packages/710/ - official, http://distro.ibiblio.org/fatdog/contrib/packages/710/ - default - http://smokey01.com/fd710/packages/ - default), click OK, click the Update icon, finally enter your search term in the Search input field. "mypaint" returns nothing.chiron² wrote:Hello,
Has someone tried to do a MyPaint (1.2) package for FD710? I am stuck with some unresolvable error messages, claiming that a pygtkcompat cannot be found, when it is actually there. Some version conflict within Python maybe? IDK, given up on it, it's not that important.
You can try and run MyPaint as an AppImage. Download the MyPaint AppImage, set the file executable, click the appimage icon in rox filer to execute it. If it doesn't run open a terminal window in the folder where the appimage file is located, and run the file from the command line. Error messages in the terminal will help you figure out what's wrong.
There's an appimage here: https://transfer.sh/OXbic/MyPaint-1.3.0 ... 4.AppImage
It'll stay there for 3 or 4 more days. The MyPaint github site automatically builds an AppImage of the latest commit, and uploads it to transfer.sh, which has a 14 day retention policy. The latest AppImage url is listed at the end of the Travis build log here: https://travis-ci.org/mypaint/mypaint. The build log changes when the project team commit something new.
I briefly tested the above AppImage. It seemed to work BUT, all toolbar icons were blank, and I couldn't exit the application. I suggest you start it from the command-line. Before I tested I installed the gtk3 package (use Gslapt), and loaded the devx SFS (use the SFS Manager, which is found next to Gslapt in the Fatdog control panel).
Fatdog packages are stored as slackware TXZ packages, but they aren't taken from slackware, they are all self-compiled. There's a thread for user-contributed packages - follow the "+packages" link in my signature.Is there a distribution where one could scavenge packages? Or is it more or less 'compile yourself'?
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
Thanks. That AppImage thing seems to be a good idea, I have some AppImages running. Would be good, if there was also a stable version of MyPaint. But I will try and see what happens.
One other issue just popped up. When I start 'Set default Soundcard' from the controlpanel, A large Window opens, telling me about XDialog and it's options. After closing this window, a small Xdialog appears 'Operation cancelled, nothing changed'.
Starting in Terminal gives the following output: (The german in the beginning means that /var/lib .../names can not be opened for reading, because file or directory not found, don't think that's part of the problem, My ThinkPad doesn't have BT)
It doesn't say in which line of code it's missing list parameters.
Probably a pretty easy one for the devs?
EDIT I commented out the line looking for the BT. That error is gone, but otherwise still the same. Tried to run without X, from CLI, the same behavior, without the XDialog error message. But still, immediately after start, 'Operation canceled, nothing changed'
Cheers
Norman
One other issue just popped up. When I start 'Set default Soundcard' from the controlpanel, A large Window opens, telling me about XDialog and it's options. After closing this window, a small Xdialog appears 'Operation cancelled, nothing changed'.
Starting in Terminal gives the following output: (The german in the beginning means that /var/lib .../names can not be opened for reading, because file or directory not found, don't think that's part of the problem, My ThinkPad doesn't have BT)
Code: Select all
# fatdog-default-soundcard.sh
awk: Kommandozeile:1: Fatal: Die Datei »/var/lib/bluetooth/*/names« kann nicht zum Lesen geöffnet werden (Datei oder Verzeichnis nicht gefunden)
Xdialog: missing list parameters !
Xdialog v2.3.1 by Thierry Godefroy <xdialog@free.fr> (v1.0 was
written by Alfred at Cyberone Internet <alfred@cyberone.com.au>).
Xdialog home page available at: http://xdialog.dyns.net/
... and so on, XDialog options explained
Probably a pretty easy one for the devs?
EDIT I commented out the line looking for the BT. That error is gone, but otherwise still the same. Tried to run without X, from CLI, the same behavior, without the XDialog error message. But still, immediately after start, 'Operation canceled, nothing changed'
Cheers
Norman
So, I tested the MyPaint AppImage, with the same results as step. Somewhat runs, but no icons in the toolbar. Background color is gray, and cannot be changed. In Xenialpup64, the AppImage works, and also displays the adequate icons in the toolbar. Some gdkpixbuf issue yet again? Since XP does not handle my graphics tablet, I will just stick around and meanwhile use the GIMP.
Hi Chiron Raised to the the Power of Two,chiron² wrote:So, I tested the MyPaint AppImage, with the same results as step. Somewhat runs, but no icons in the toolbar. Background color is gray, and cannot be changed. In Xenialpup64, the AppImage works, and also displays the adequate icons in the toolbar. Some gdkpixbuf issue yet again? Since XP does not handle my graphics tablet, I will just stick around and meanwhile use the GIMP.
Nothing to add to the conversation here other than to ask you: how did you get that "raised to the power of two" in your name, and furthermore, how did you get the forum signup to accept it?? Did you use a special keycode, character map, and most of all what did you do to get it past the forum signup, where it allows no special characters?? Spill da beans, science-math man!!
