Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[Claymore]

v11.7:

- added temperature management and overclock support for recent Nvidia cards in Windows: "-tt", "-powlim", "-cclock", "-mclock", "-tt", "-fanmax", "-fanmin" options are supported for Nvidia too.
- now "y" key also disables CrossFire.
- added "-y" option.
- fixed issue with miner restart that was required sometimes to apply overclock settings for AMD cards.
- fixed issue with rejected shares when "-esm 3" option is used.
- Linux version: fixed issue with remote management.
- some changes in watchdog routines to improve ability to restart miner after various OpenCL fails.
- a few minor bug fixes and improvements.

PS. For Nvidia "-cclock" and "-mclock" options also support delta mode, for example, "-mclock +400", see readme for details.

[1713541277]

1713541277

[1713541277]

1713541277

[1713541277]

1713541277

[1713541277]

1713541277

[1713541277]

1713541277

[1713541277]

1713541277

[Krishi]

My 1060 3gb could no longer mine since today because of the DAG, not unexpected, I knew it was coming.

My problem:
I'm now using integrated graphics for windows and my GPU is sitting quietly in the PCIe slot, no load, no VRAM usage, nothing.
Yet when I try and run the miner again i get the same problem of not enough VRAM. By using integrated graphics for windows I freed up 300-400mb of VRAM for my GPU, is that still not enough??

[salvo2002]

Thanks for the updated version @Claymore!

Quick question...on Linux [HiveOS] when I run two claymore dual instances [v11.6] eth only mode (split up a 10 card rig // -di 01234 in one mining eth and -di 56789 in the other mining etc) claymore reports the temps and fan settings for all 10 cards in both instances and I get OpenCL hangs. If I run one instance of claymore with all 10 cards its stable -- no OpenCL hangs.

I assume I get the OpenCL hangs when running two instances due to both instances trying to query temps & fan speeds at the same time. Is there a setting I am missing that only queries/controls the cards enabled in the instance 

[shereenkhan120]

I have been successfully using claymore on Windows 10 for 3 months. However, I wanted to switch to Linux for the sake stability. I tried both HiveOS and SimpleOS. However, apparently claymore connects to ethermine and then the shares get rejected and it disconnects and tries again. It was exactly the same result in both HiveOS and SimpleOS. I also tried to start the miner manually myself, in order to rule out the possibility that it might be due to some bad config, however, it was still the same result.

Here is the screenshot:
https://ibb.co/ncW5wx

I would really appreciate any input on this.

[dwdhu]

hi,
please submit your updated hashrates to
https://gpustats.com
thank you

[rufo28]

v11.7:

- added temperature management and overclock support for recent Nvidia cards in Windows: "-tt", "-powlim", "-cclock", "-mclock", "-tt", "-fanmax", "-fanmin" options are supported for Nvidia too.
- now "y" key also disables CrossFire.
- added "-y" option.
- fixed issue with miner restart that was required sometimes to apply overclock settings for AMD cards.
- fixed issue with rejected shares when "-esm 3" option is used.
- Linux version: fixed issue with remote management.
- some changes in watchdog routines to improve ability to restart miner after various OpenCL fails.
- a few minor bug fixes and improvements.

PS. For Nvidia "-cclock" and "-mclock" options also support delta mode, for example, "-mclock +400", see readme for details.

Dear Claymore,

thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.
Below the sample result logs:

=========================================================================
22:25:30:131   294c   gpu 8 nvidia powlim set ok (85%, previous value was 100%)
22:25:30:177   294c   gpu 8 nvidia setcoreclock set ok (1733MHz, previous value was 1683MHz)
22:25:30:271   294c   gpu 8 nvidia memclock set ok (6355MHz, previous value was 5505MHz)
22:25:30:302   294c   gpu 9 nvidia powlim set ok (85%, previous value was 100%)
22:25:30:349   294c   gpu 9 nvidia setcoreclock set ok (1632MHz, previous value was 1582MHz)
22:25:30:396   294c   gpu 9 nvidia memclock set ok (6355MHz, previous value was 5505MHz)
22:25:30:412   294c   gpu 10 nvidia powlim set ok (70%, previous value was 100%)
22:25:30:459   294c   gpu 10 nvidia setcoreclock set ok (1763MHz, previous value was 1733MHz)
22:25:30:506   294c   gpu 10 nvidia memclock set ok (5555MHz, previous value was 5005MHz)
22:25:47:018   294c   CUDA error 9 #102 - 46
22:25:47:097   294c   CUDA error 9 #102a - 46
22:25:47:097   294c   CUDA error 9 #103 - 46
22:25:47:097   294c   CUDA error 9 #105 - 46
22:25:47:097   294c   CUDA error 10 #102 - 46
22:25:47:112   294c   CUDA error 10 #102a - 46
22:25:47:128   294c   CUDA error 10 #103 - 46
22:25:47:128   294c   CUDA error 10 #105 - 46
22:25:47:300   2988   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
22:25:47:315   2988   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
22:25:47:519   2988   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
22:25:47:519   2988   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
22:25:47:644   2988   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
22:25:47:644   2988   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
22:25:47:753   2988   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
22:25:47:753   2988   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
22:25:47:878   2988   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
22:25:47:878   2988   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
22:25:47:987   2988   NVML: cannot get current temperature, error 999 (an internal driver error occurred)



best regards,

[fanisk21]

hi,
please submit your updated hashrates to
https://gpustats.com
thank you

good idea. but need more improvements. like how can i see the images of the rig after post the result? and the additional notes? and why 512KB rom is to big?

You should have login to users edit their results and etc.

But i think it will be done soon.

GJ anyways

[Claymore]

Dear Claymore,
thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.

If it worked before try lower clocks to see if that is the reason.

[Claymore]

Thanks for the updated version @Claymore!

Quick question...on Linux [HiveOS] when I run two claymore dual instances [v11.6] eth only mode (split up a 10 card rig // -di 01234 in one mining eth and -di 56789 in the other mining etc) claymore reports the temps and fan settings for all 10 cards in both instances and I get OpenCL hangs. If I run one instance of claymore with all 10 cards its stable -- no OpenCL hangs.

I assume I get the OpenCL hangs when running two instances due to both instances trying to query temps & fan speeds at the same time. Is there a setting I am missing that only queries/controls the cards enabled in the instance 

Use "-tt 0" to disable monitoring.

I have been successfully using claymore on Windows 10 for 3 months. However, I wanted to switch to Linux for the sake stability. I tried both HiveOS and SimpleOS. However, apparently claymore connects to ethermine and then the shares get rejected and it disconnects and tries again. It was exactly the same result in both HiveOS and SimpleOS. I also tried to start the miner manually myself, in order to rule out the possibility that it might be due to some bad config, however, it was still the same result.
I would really appreciate any input on this.

You should check the log file, it seems pool sends some string with the error after connection.

[skypara]

Tried running the 11.7 Claymore on Nvidia TITAN X. Windows 10 x 64. Latest Nvidia drivers installed, card not OCd. Windows defender off, Eset Antvirus temporary off for the testing.
start.bat file updated through nanopool.org config option. Miner starts but ends up with an error and resets with the following error message:

https://postimg.cc/image/v6f4hf16v/

Also tried 11.6 version (without the tempreratures features). Again ends up with an error although temperatures not included:

https://s31.postimg.cc/d50kx86sr/error2.jpg

Will appreciate any suggestions to get this sorted. Thanks.

[ollis miner]

@Claymore

Works like a charm - as always.
Still having issues with my AMD cards lowering hashrate for a few seconds (up to two mins) and then back to normal. Have learned to live with it, but I wonder why...

Ollis

[rigomortis]

PSA:

Seems like all new version of Claymore never can reach the reported effective hashrate.  If you guys want more shares.. use v9.8.  All newer version are skimming more shares.  Claymore just getting his share guys..

[ollis miner]

PSA:

Seems like all new version of Claymore never can reach the reported effective hashrate.  If you guys want more shares.. use v9.8.  All newer version are skimming more shares.  Claymore just getting his share guys..

Don't believe you. He has always been updating this SW to please us users.
Can you proof that the 9.8 version is better than 11.x ?

[ollis miner]

PSA:

Seems like all new version of Claymore never can reach the reported effective hashrate.  If you guys want more shares.. use v9.8.  All newer version are skimming more shares.  Claymore just getting his share guys..

Don't believe you. He has always been updating this SW to please us users.
Can you proof that the 9.8 version is better than 11.x ?

@rigomortis
Just rolled back one of my rigs to v9.8 with the same dcri suggestions as 11.7 did. Going to try it for 24h to see if you are correct - or full of bs... Time will show

Ollis

[rigomortis]

PSA:

Seems like all new version of Claymore never can reach the reported effective hashrate.  If you guys want more shares.. use v9.8.  All newer version are skimming more shares.  Claymore just getting his share guys..

Don't believe you. He has always been updating this SW to please us users.
Can you proof that the 9.8 version is better than 11.x ?

@rigomortis
Just rolled back one of my rigs to v9.8 with the same dcri suggestions as 11.7 did. Going to try it for 24h to see if you are correct - or full of bs... Time will show

Ollis

not BS bro.  i switched to the latest hoping the higher hashrate will be worth it.. but the shares are alot lower.  BTW...   you will notice a big difference if you run demion nodevfee.. which is the only legit nodevfee program.  You will see that v11.2 and higher you will not be able to divert the devfees back to yourself.  I would say version 11 is the last decent claymore version.. after that it's all bloatware.

[WhackOBill]

not BS bro.  i switched to the latest hoping the higher hashrate will be worth it.. but the shares are alot lower.  BTW...   you will notice a big difference if you run demion nodevfee.. which is the only legit nodevfee program.  You will see that v11.2 and higher you will not be able to divert the devfees back to yourself.  I would say version 11 is the last decent claymore version.. after that it's all bloatware.

So your real issue is that you can't hack the DevFee due to the move to SSL for those connections.  Sad.

[jeremyismer]

not BS bro.  i switched to the latest hoping the higher hashrate will be worth it.. but the shares are alot lower.  BTW...   you will notice a big difference if you run demion nodevfee.. which is the only legit nodevfee program.  You will see that v11.2 and higher you will not be able to divert the devfees back to yourself.  I would say version 11 is the last decent claymore version.. after that it's all bloatware.

This probably isn't the forum to complain about a devfee!

[salvo2002]

Thanks for the updated version @Claymore!

Quick question...on Linux [HiveOS] when I run two claymore dual instances [v11.6] eth only mode (split up a 10 card rig // -di 01234 in one mining eth and -di 56789 in the other mining etc) claymore reports the temps and fan settings for all 10 cards in both instances and I get OpenCL hangs. If I run one instance of claymore with all 10 cards its stable -- no OpenCL hangs.

I assume I get the OpenCL hangs when running two instances due to both instances trying to query temps & fan speeds at the same time. Is there a setting I am missing that only queries/controls the cards enabled in the instance 

Use "-tt 0" to disable monitoring.

Ahhhh, thanks! Seems to be working fine after -tt 0 is used for the second instance and the first instance manages all of the cards, although -ttli and -ttdcr won't work in the second instance.

[Balthazar]

- fixed issue with rejected shares when "-esm 3" option is used.

Doesn't seem like it's going well... Got a report from one of our users, DevFee mining is working now, but he's getting rejected shares right after DevFee.







Sometimes rejects are also happening with DevFee mining:



But this occurs much less often.

Links:

http://i67.tinypic.com/2crvqz8.png
http://i65.tinypic.com/685yxe.png
http://i64.tinypic.com/33aghlj.png
http://i65.tinypic.com/nzoc4h.png

[dubignyp]

Thank you for your work