--max-temp has no effect #15
Comments
|
CPU temperature doesn't work on Windows, it always reads 0C.
…On Fri, Jun 23, 2017 at 1:57 PM, M0E-lnx ***@***.***> wrote:
Just getting into trying this out. Works great for the most part, but
running the miner with the --max-temp option and argument has no effect
at all. The CPU will overheat to the point that it shuts my laptop down
which is a good thing, instead of having it catch on fire.
This is running on an Intel I5 M560. I tried the upstream cpuminer-multi
project, compiled with identical build options, and that does does respect
the --max-temp option.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#15>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQTWjuutzP6DcGa3Rczg8WK-3e2V-Iehks5sG_yNgaJpZM4OD3iv>
.
|
|
this is on linux 64bit
…On Jun 26, 2017 9:22 PM, "JayDDee" ***@***.***> wrote:
CPU temperature doesn't work on Windows, it always reads 0C.
On Fri, Jun 23, 2017 at 1:57 PM, M0E-lnx ***@***.***> wrote:
> Just getting into trying this out. Works great for the most part, but
> running the miner with the --max-temp option and argument has no effect
> at all. The CPU will overheat to the point that it shuts my laptop down
> which is a good thing, instead of having it catch on fire.
>
> This is running on an Intel I5 M560. I tried the upstream cpuminer-multi
> project, compiled with identical build options, and that does does
respect
> the --max-temp option.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#15>, or mute the thread
> <https://github.com/notifications/unsubscribe-
auth/AQTWjuutzP6DcGa3Rczg8WK-3e2V-Iehks5sG_yNgaJpZM4OD3iv>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABd4fYJv3JsfgNHVmg6_VBv1VWT3H9tcks5sIGddgaJpZM4OD3iv>
.
|
|
It works for me, you'll need to provide more info. In addition to program output try this command: |
CPU INFOhwmon valuesI do not have a /sys/devices/platform/coretemp.0/hwmon/hwmon1/temp1_input PROGRAM OUTPUTLaunch command used: OutputTEMP READING (shortly after launching)I stopped it before it went any further, but it has gone all the way up to 104C and eventually shuts my box down. Hope this helps. |
|
Thanks for the data, I understand the problem now. Until a new release is built you can make the following changes from cpuminer-multi. tpruvot/cpuminer-multi@2220b21 Please confirm it works. |
|
Yep! That sure does it. |
|
Thanks for testing. I planning on revising the fix to remove two sensors that appear to report HDD temps: The others either report CPU temp or do not exist. Can you confirm? |
|
I do have a /sys/class/hwmon/hwmon0/temp2_input and that reports temp As I understand, on this particular cpu (not sure about others) temp2 reports temp for core 0 and temp4 reports temp for core 2. The cpu has 2 physical cores, My best guess is that those are as follow CORE 0 = physical - temp reported by temp2_input *virtual used for the lack of a better term. |
|
I'm still investigating this issue. It appears the hwmon sensors can vary from motherboard to The currrent logic used is to poll sensors in some order for the first one that returns a value. With no apparent elegant solution one possible approach is to scan for the highest tempeature Multi CPU system can be another complicating issue. |
|
You are correct. There are many sensors reporting temp on different systems. Would it be possible to maybe probe what lm_sensors report? It may offer some hint as to where or which sensor to read. If it helps, here is my output of the I imagine something (although maybe not all that elegantly) can be done with this. since my paths in cat For example, I have a core 0 and core 2 reported by Just an idea, like I said, maybe not the most elegant way of doing it. |
|
you said: "my paths in cat /sys/class/hwmon/hwmon0 match core numbers." |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just getting into trying this out. Works great for the most part, but running the miner with the
--max-tempoption and argument has no effect at all. The CPU will overheat to the point that it shuts my laptop down which is a good thing, instead of having it catch on fire.This is running on an Intel I5 M560. I tried the upstream
cpuminer-multiproject, compiled with identical build options, and that does does respect the --max-temp option.The text was updated successfully, but these errors were encountered: