if the rig is MIXED, miner does not extend available memory of 1060 3GB version on Windows10 (2xAMD and 2x1060 3GB). Then it gives an dag size error. However, if the rig is full of 1060 3GB version,there is no problem. Can you fix this?
https://imgur.com/uifs4om
https://imgur.com/h8kYUb7
Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 264. (Read 6590718 times)
April 24, 2018, 01:45:13 PM
April 24, 2018, 12:23:39 PM
DO NOT USE MEW (MYETHERWALLET ONLINE)
https://www.reddit.com/r/MyEtherWallet/comments/8ek0jj/think_i_got_scammedphishedhacked/
GOOGLE DNS IS HACKED!
https://www.reddit.com/r/MyEtherWallet/comments/8ek0jj/think_i_got_scammedphishedhacked/
GOOGLE DNS IS HACKED!
Thanks for the update and letting everybody know. Did they steal a lot of ethereum coin? When the hack start?
I'm going to read the article on Reddit now.
April 24, 2018, 10:59:14 AM
DO NOT USE MEW (MYETHERWALLET ONLINE)
https://www.reddit.com/r/MyEtherWallet/comments/8ek0jj/think_i_got_scammedphishedhacked/
GOOGLE DNS IS HACKED!
https://www.reddit.com/r/MyEtherWallet/comments/8ek0jj/think_i_got_scammedphishedhacked/
GOOGLE DNS IS HACKED!
April 24, 2018, 10:38:26 AM
You are correct. The reason is that you send same jobid and jobheader for both main and devfee connections, the only difference is extranonce
Yes, you are right. Job is global and the same for every miner who works on it within its own nonce space. This guarantees unique mining results for every session. The only event when job id changes is getting new block from the network. Another thing is that server remembers the content of last 6 job packages and corresponding results are accepted as well, though with lower reward. April 24, 2018, 07:35:56 AM
start.bat---6*1060 gaming X 6gb 11.7???(Nvidia cards in Windows: "-tt", "-powlim", "-cclock", "-mclock", "-tt", "-fanmax", "-fanmin" )
April 24, 2018, 06:37:08 AM
I re-uploaded v11.7 with these changes:
- fixed issue with "-esm 3" (again).
- fixed issue with Nvidia fan control (Windows only)
Please re-download v11.7 if you have any of these issues, it must write "b583" to the log at the beginning.
- fixed issue with "-esm 3" (again).
- fixed issue with Nvidia fan control (Windows only)
Please re-download v11.7 if you have any of these issues, it must write "b583" to the log at the beginning.
April 24, 2018, 05:27:59 AM
- 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.But this occurs much less often.
You are correct. The reason is that you send same jobid and jobheader for both main and devfee connections, the only difference is extranonce and I don't handle this case properly.
I will upload an update within a couple of hours.
April 24, 2018, 03:40:25 AM
Thank you for your work
April 24, 2018, 01:33:41 AM
- 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
April 23, 2018, 11:57:02 PM
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.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
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.
April 23, 2018, 10:32:44 PM
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!
April 23, 2018, 10:18:28 PM
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.
April 23, 2018, 06:19:28 PM
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..
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.
April 23, 2018, 05:53:46 PM
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..
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
April 23, 2018, 04:35:51 PM
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..
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 ?
April 23, 2018, 04:26:43 PM
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..
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..
April 23, 2018, 04:22:06 PM
@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
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
April 23, 2018, 03:20:07 PM
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.
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.
April 23, 2018, 03:18:22 PM
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
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.
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.
April 23, 2018, 03:09:23 PM
Dear Claymore,
thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.
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.
Jump to: