Author

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 499. (Read 5806088 times)

legendary
Activity: 952
Merit: 1000
Fan no higher than the 60% I left it at.

M

Why only 60% fan? You might need to bump that a little higher.

I don't run any of my GPUs above 60%.  All but this one do just fine between 50 and 60%.  Most run in a very cooled environment (air conditioning blowing right on them), "free" from any chasis with a box fan blowing on them.  They usually run high 60s, low 70s.  This one is in my main workstation, which has cooling issues.  Usually 60% is fine, sometimes I can do 50-55% w/o a problem.  However, twice recently I found it in the low 90s, and cgminer seemed oblivious to it, even though it clearly showed the temp on the screen in cgminer.

M


Well there you go. You just answered your own question. If all your caseless, air conditioned GPUs do fine with 60% fan, but your workstation GPU (which has cooling issues) isn't fine with 60%, then I say again, bump up the fan speed! "--auto-fan --gpu-fan 25-75".
legendary
Activity: 1540
Merit: 1001
Fan no higher than the 60% I left it at.

M

Why only 60% fan? You might need to bump that a little higher.

I don't run any of my GPUs above 60%.  All but this one do just fine between 50 and 60%.  Most run in a very cooled environment (air conditioning blowing right on them), "free" from any chasis with a box fan blowing on them.  They usually run high 60s, low 70s.  This one is in my main workstation, which has cooling issues.  Usually 60% is fine, sometimes I can do 50-55% w/o a problem.  However, twice recently I found it in the low 90s, and cgminer seemed oblivious to it, even though it clearly showed the temp on the screen in cgminer.

M

hero member
Activity: 518
Merit: 500
Manateeeeeeees
My reject rates have gone to almost 2% according to cgminer after going from 2.7.0 -> 2.7.5.  The weird part is my pool (bitminter) has them at 0, so that's a plus.  How can I figure out what's happening here?

cgminer seems to be reporting lots of Duplicates (many more than usual).
legendary
Activity: 952
Merit: 1000
Fan no higher than the 60% I left it at.

M

Why only 60% fan? You might need to bump that a little higher.
legendary
Activity: 1540
Merit: 1001
Using 2.7.4.

The overheat function doesn't seem to be working right.  I have it set to 85.  Twice I've found it in the low 90s and not making any effort to shut down or cool down.

M
--temp-cutoff (default is 95)

This is in my cgminer.conf.  This isn't enough?

"temp-cutoff" : "90",
"temp-overheat" : "85",
"temp-target" : "75",

M

Is the fan working? How many mining threads do you have running?  What is the status and the temperature displayed in the main cgminer window?

Fan's working.

Two threads.

cgminer is happily mining away, listing it at 92C when I find it.  No indication it found anything wrong.  Fan no higher than the 60% I left it at.

M
member
Activity: 103
Merit: 10
it's working nicely in 2.7.4 ... don't know in 2.7.5
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Using 2.7.4.

The overheat function doesn't seem to be working right.  I have it set to 85.  Twice I've found it in the low 90s and not making any effort to shut down or cool down.

M
--temp-cutoff (default is 95)

This is in my cgminer.conf.  This isn't enough?

"temp-cutoff" : "90",
"temp-overheat" : "85",
"temp-target" : "75",

M
The line of code related to that specifically says if the temp is above temp-cutoff it will change the device status to RECOVERING.
That's why I suggested that.
It will show the device status as 'REST' and give a message as below.
It also requires both --auto-gpu and --auto-fan
It also requires ADL working - which you will see via the GPU showing it's temperature.
Code:
        if (engine && ga->autoengine) {
                if (temp > cgpu->cutofftemp) {
                        applog(LOG_WARNING, "Hit thermal cutoff limit on GPU %d, disabling!", gpu);
                        *denable = DEV_RECOVER;
                        newengine = ga->minspeed;

                        cgpu->device_last_not_well = time(NULL);
                        cgpu->device_not_well_reason = REASON_DEV_THERMAL_CUTOFF;
                        cgpu->dev_thermal_cutoff_count++;

Edit: of course if there is a bug and it's not working as expected in the current 2.7.5 - yep we'll need to chase it down and fix it.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
could that be a driver issue

The last stable release is 2.7.5. Maybe try an upgrade first? Wink

Don't be an asshat.  2.7.5 is the latest release.  It is not stable for everyone.  Just because it works for you, doesn't mean that everyone else should be using it.

Wow... rough night?

The last stable release in the 2.6 series was 2.6.6. The current last stable release is 2.7.5. Maybe help Kano and Con with debugging info if the versions you are using are stable and the latest ones don't work?
Or if anyone is interested in additions after 2.7.5 Smiley

The master branch in my git has a rather large number of commits I've worked on in the last 24 hours (and a couple before that)
The list is: debug control in the API, generic HW error handling for all devices except ztex, Diff1 information, BFL identify via a led flash, BFL throttle counter in 'notify' and a few other bit and pieces.

The pull request is here: https://github.com/ckolivas/cgminer/pull/310 that shows them all.
That is simply my master branch - and each change I've done I keep adding to that pull request.

Anyone interested in any of those additions feel free to compile my master and let me know if you have any problems.
I haven't changed the ztex code coz I don't have any ztex hardware and the original code does some weird shit dealing with HW errors - if someone has a ztex and has time to visit IRC I could add some changes in another branch and get them to test it also.

Thanks for anyone who can test this.

Edit: of course this is what I am running on my 2 rigs - BFL, and ICA+GPU
legendary
Activity: 1540
Merit: 1001
Using 2.7.4.

The overheat function doesn't seem to be working right.  I have it set to 85.  Twice I've found it in the low 90s and not making any effort to shut down or cool down.

M
--temp-cutoff (default is 95)

This is in my cgminer.conf.  This isn't enough?

"temp-cutoff" : "90",
"temp-overheat" : "85",
"temp-target" : "75",

M
sr. member
Activity: 349
Merit: 250
could that be a driver issue

The last stable release is 2.7.5. Maybe try an upgrade first? Wink

Don't be an asshat.  2.7.5 is the latest release.  It is not stable for everyone.  Just because it works for you, doesn't mean that everyone else should be using it.

Wow... rough night?

The last stable release in the 2.6 series was 2.6.6. The current last stable release is 2.7.5. Maybe help Kano and Con with debugging info if the versions you are using are stable and the latest ones don't work?
sr. member
Activity: 378
Merit: 250
Why is it so damn hot in here?
could that be a driver issue

The last stable release is 2.7.5. Maybe try an upgrade first? Wink

Don't be an asshat.  2.7.5 is the latest release.  It is not stable for everyone.  Just because it works for you, doesn't mean that everyone else should be using it.

The last "stable release" in my case is 2.6.1., on one of my systems, and 2.5.3 on another.
sr. member
Activity: 438
Merit: 250
reinstalled drivers fixed it
 thx  Smiley
sr. member
Activity: 349
Merit: 250
could that be a driver issue

The last stable release is 2.7.5. Maybe try an upgrade first? Wink
sr. member
Activity: 438
Merit: 250
could that be a driver issue
sr. member
Activity: 438
Merit: 250
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Using 2.7.4.

The overheat function doesn't seem to be working right.  I have it set to 85.  Twice I've found it in the low 90s and not making any effort to shut down or cool down.

M
--temp-cutoff (default is 95)
legendary
Activity: 1540
Merit: 1001
Using 2.7.4.

The overheat function doesn't seem to be working right.  I have it set to 85.  Twice I've found it in the low 90s and not making any effort to shut down or cool down.

M
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Is it possible to point each device to a different pool with one instance of cgminer?
No
legendary
Activity: 1973
Merit: 1007
Is it possible to point each device to a different pool with one instance of cgminer?
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Thanks Cheesy

I did actually find it after searching my IRC logs.
ZMX
It seems I did know it back in May from the forum but I had forgotten it.
Jump to: