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

[jjiimm_64]

Search for "Zcash" in this thread and you will see my answer.

sorry to have asked a question you obviously answered a number of times already   :-(

Thanks for the hard work!!

Jim

[1714245083]

1714245083

[1714245083]

1714245083

[1714245083]

1714245083

[fittsy]

Hi,

When I use option :

-r   Restart miner mode. "-r 0" (default) - restart miner if something wrong with GPU. "-r -1" - disable automatic restarting. -r >20 - restart miner if something
   wrong with GPU or by timer. For example, "-r 60" - restart miner every hour or when some GPU failed.
   "-r 1" closes miner and execute "reboot.bat" file ("reboot.bash" or "reboot.sh" for Linux version) in the miner directory (if exists) if some GPU failed.
   So you can create "reboot.bat" file and perform some actions, for example, reboot system if you put this line there: "shutdown /r /t 5 /f".

my miner says, that it can not find the reboot.bat, but reboot.bat is in miner directory?

Did someone have idea?

Your batch file is probably being run from another directory.  So the system is looking for the batch file in the directory you're calling the batch file from, not the directory where the reboot.bat exists.

Make sure in your batch file before the line where you run EthDcrMiner64.exe you change to the right directory. For example your batch file might look something like this instead:

Code:

I:
cd I:\crypto\Claymore\v7-beta
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe

Notice my first two lines.  I change to my I drive on this computer. Yours may be on C so you don't need to change.
Then I change to the folder where I installed Claymore.
Then I run the regular batch file commands.

If you do it this way your -r command will work even if your batch file isn't in the same folder as Claymore.

[maxmad_x]

Nope I havn't solved the problem. Rig keeps crashing with OpenCL call error. So I am running it at much less undervolting. I am using 31Mh rom for rx4480 running at 1191/2150 currently.
[
quote author=armyman link=topic=1433925.msg16591334#msg16591334 date=1476695961]

Anyone please want to help me with this ? As far as I can see , I dont see an error. No usual OpenCL call error exit... I can't see the error but the miner reboots !

I have 3 rx480s, Win 10, Crimson 16.9.3  and as you can see , for first few lines it has been working at 30.6MH each. then something has happened and the miner crashes. Can someone please help?


20:27:29:198   1590   parse packet: 247
20:27:29:198   1590   eth: job changed
20:27:29:214   1590   new buf size: 0
20:27:29:214   1590   ETH: 10/14/16-20:27:29 - New job from us1.ethpool.org:3333
20:27:29:214   1590   target: 0x0000000112e0be82 (diff: 4000MH), epoch #81
20:27:29:230   1590   ETH - Total Speed: 92.021 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00
20:27:29:230   1590   ETH: GPU0 30.688 Mh/s, GPU1 30.634 Mh/s, GPU2 30.699 Mh/s
20:27:30:042   1590   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x57b652a", "0x000000000000000000000000000000000000000000000000000000009563b0cb"]}

20:27:30:089   1590   ETH: checking pool connection...
20:27:30:089   1590   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

20:27:30:136   1590   got 39 bytes
20:27:30:136   1590   buf: {"id":6,"jsonrpc":"2.0","result":true}

20:27:30:136   1590   parse packet: 38
20:27:30:151   1590   new buf size: 0
20:27:30:230   1590   got 248 bytes
20:27:30:230   1590   buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}

20:27:30:245   1590   parse packet: 247
20:27:30:245   1590   eth: job is the same
20:27:30:261   1590   new buf size: 0
20:27:30:808   17d0   recv: 51
20:27:30:823   17d0   srv pck: 50
20:27:30:870   17d0   srv bs: 0
20:27:30:886   17d0   sent: 162
20:27:35:824   117c   recv: 51
20:27:35:824   117c   srv pck: 50
20:27:35:871   117c   srv bs: 0
20:27:35:871   117c   sent: 162
20:27:40:121   1590   ETH: checking pool connection...
20:27:40:121   1590   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

20:27:40:215   1590   got 248 bytes
20:27:40:215   1590   buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}

20:27:40:231   1590   parse packet: 247
20:27:40:231   1590   eth: job is the same
20:27:40:246   1590   new buf size: 0
20:27:40:824   1468   recv: 51
20:27:40:840   1468   srv pck: 50
20:27:40:887   1468   srv bs: 0
20:27:40:887   1468   sent: 162
20:27:45:825   514   recv: 51
20:27:45:841   514   srv pck: 50
20:27:45:888   514   srv bs: 0
20:27:45:903   514   sent: 162
20:27:47:372   1580   ETH: put share nonce 4ef7ab1c0ff574f1
20:27:47:372   1580   ETH round found 1 shares
20:27:47:388   1590   ETH: 10/14/16-20:27:47 - SHARE FOUND - (GPU 1)
20:27:47:403   1590   send: {"id":4,"method":"eth_submitWork","params":["0x4ef7ab1c0ff574f1","0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xf70b5bbcbe4143debf392fc7bb00587fa0901077d9e2652f967a15d56e33db83"]}

20:27:47:497   1590   got 39 bytes
20:27:47:497   1590   buf: {"id":4,"jsonrpc":"2.0","result":true}

20:27:47:497   1590   parse packet: 38
20:27:47:513   1590   ETH: Share accepted (110 ms)!

20:27:47:513   1590   new buf size: 0
20:27:50:060   1590   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x57bb1bb", "0x000000000000000000000000000000000000000000000000000000009563b0cb"]}

20:27:50:138   1590   got 39 bytes
20:27:50:138   1590   buf: {"id":6,"jsonrpc":"2.0","result":true}

20:27:50:154   1590   parse packet: 38
20:27:50:154   1590   new buf size: 0
20:27:50:169   1590   ETH: checking pool connection...
20:27:50:185   1590   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

20:27:50:263   1590   got 248 bytes
20:27:50:263   1590   buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}

20:27:50:279   1590   parse packet: 247
20:27:50:279   1590   eth: job is the same
20:27:50:294   1590   new buf size: 0
20:27:50:841   740   recv: 51
20:27:50:857   740   srv pck: 50
20:27:50:904   740   srv bs: 0
20:27:50:904   740   sent: 162
20:27:51:060   1414   GPU0 t=76C fan=40%, GPU1 t=70C fan=32%, GPU2 t=76C fan=40%
20:27:51:060   1414   em hbt: 0, fm hbt: 62,
20:27:51:060   1414   watchdog - thread 0, hb time 187
20:27:51:060   1414   watchdog - thread 1, hb time 500
20:27:51:076   1414   watchdog - thread 2, hb time 562
20:27:51:076   1414   watchdog - thread 3, hb time 250
20:27:51:076   1414   watchdog - thread 4, hb time 328
20:27:51:076   1414   watchdog - thread 5, hb time 15

Have you solved the problem?

Also are your cards overclocked or reference?
[/quote]

[windeagle]

I got an interesting case.

I have rx470 cards for mining whose BIOS have been updated, and the version of Claymore is v7.1. When Eth-only mining, I got totally 137MH/s; and when Eth and SC dual mining with -dcri's value 15, I got Eth's total speed 140MH/s.

Does anybody else get the same?

[o00o]

I got an interesting case.

I have rx470 cards for mining whose BIOS have been updated, and the version of Claymore is v7.1. When Eth-only mining, I got totally 137MH/s; and when Eth and SC dual mining with -dcri's value 15, I got Eth's total speed 140MH/s.

Does anybody else get the same?

Quite a few of us for that matter.

[costi.kocev]

Hi,

When I use option :

-r   Restart miner mode. "-r 0" (default) - restart miner if something wrong with GPU. "-r -1" - disable automatic restarting. -r >20 - restart miner if something
   wrong with GPU or by timer. For example, "-r 60" - restart miner every hour or when some GPU failed.
   "-r 1" closes miner and execute "reboot.bat" file ("reboot.bash" or "reboot.sh" for Linux version) in the miner directory (if exists) if some GPU failed.
   So you can create "reboot.bat" file and perform some actions, for example, reboot system if you put this line there: "shutdown /r /t 5 /f".

my miner says, that it can not find the reboot.bat, but reboot.bat is in miner directory?

Did someone have idea?

Your batch file is probably being run from another directory.  So the system is looking for the batch file in the directory you're calling the batch file from, not the directory where the reboot.bat exists.

Make sure in your batch file before the line where you run EthDcrMiner64.exe you change to the right directory. For example your batch file might look something like this instead:

Code:

I:
cd I:\crypto\Claymore\v7-beta
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe

Notice my first two lines.  I change to my I drive on this computer. Yours may be on C so you don't need to change.
Then I change to the folder where I installed Claymore.
Then I run the regular batch file commands.

If you do it this way your -r command will work even if your batch file isn't in the same folder as Claymore.

Hi, Now I Understand Thank you, I will try.

[voidwalker]

I am trying to switch from putting options in start.bat file in config.txt file, for easier remote administration of the configs. But I have one problem. How do I keep each worker name unique for pool monitoring while sending the same config.txt to miners from EthMan ? Is there some option to keep worker name unique, separate of config.txt?
IF the answer is no, then I suggest to claymore that he should have an option to start the miner with a -workername paramater in start.bat and maybe put an alias variable in the config.txt like $worker, which the miner replaces wherever it finds with the worker name, so it could work for both coins minerd.

[scavern]

Is a newer version of claymore miner required for the upcoming hardforks?

[vapourminer]

Is a newer version of claymore miner required for the upcoming hardforks?

no. the pool you mine at takes care of that, the miner does not have to do anything.

you do have to update your wallet, such as mist, though. the link to the new software is here:

https://www.reddit.com/r/ethereum/comments/57z3zi/hard_fork_in_less_than_24_hours_upgrade_your/

[fittsy]

I am trying to switch from putting options in start.bat file in config.txt file, for easier remote administration of the configs. But I have one problem. How do I keep each worker name unique for pool monitoring while sending the same config.txt to miners from EthMan ? Is there some option to keep worker name unique, separate of config.txt?
IF the answer is no, then I suggest to claymore that he should have an option to start the miner with a -workername paramater in start.bat and maybe put an alias variable in the config.txt like $worker, which the miner replaces wherever it finds with the worker name, so it could work for both coins minerd.

Load ETHMan.exe.  Click on help tab at top.

From the help file:

Notes:

- You can send same file to several miners at once.
  Before sending a file, all strings %NAME% will be replaced with miner names.
  For example, you send epools.txt which contains this line:
      POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/%NAME%, PSW: x
  Every miner will get own epools.txt with their names, for example:
     POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/Rig1, PSW: x

[PeaMine]

For ethash auto switching on MPH, what's the command line suppose to be?
You connect with:
us-east.ethash-hub.miningpoolhub.com:12020

I am using:
EthDcrMiner64.exe -cvddc 1130,1130 -mvddc 975,975 -cclock 1340,1340 -mclock 2150,2150 -eworker gpu -dcri 30,30 -epool stratum+tcp://us-east.ethash-hub.miningpoolhub.com:12020 -ewal name.gpu -epsw x -dpool stratum+tcp://hub.miningpoolhub.com:20550 -dwal name.gpu -dpsw x -dcoin sia -esm 2 -mode 0 -powlim 50,50 -tstop 89,89 -tt 81,81 -ttli 86,86 -allpools 1 -estale 1 -mport 0
They mentioned -allcoins 1 is also needed perhaps?
Is my -esm 2 correct?

[GreatOrchid]

looking for command line for nvida on nicehash with eth and lbry coins

[cscheat]

hi claymore

is there anyway to switch pool instantly without restarting the miner?

[ryen123]

looking for command line for nvida on nicehash with eth and lbry coins

ethdcrminer64 -epool stratum+tcp://daggerhashimoto.usa.nicehash.com:3353 -ewal wallet.worker -epsw x -esm 3 -allpools 1 -dpool stratum+tcp://lbry.usa.nicehash.com:3356 -dwal wallet.worker -dpsw x -dcoin lbc

[amirheavy666]

FOR THIS :
--------------------------------
ethdcrminer64 -epool stratum+tcp://daggerhashimoto.usa.nicehash.com:3353 -ewal wallet.worker -epsw x -esm 3 -allpools 1 -dpool stratum+tcp://lbry.usa.nicehash.com:3356 -dwal wallet.worker -dpsw x -dcoin lbc

---------------------------------
first question :
what we must do for  "WALLET LBRY"?  any site is exist for create wallet?



and second question

 WE MUST have a username for nicehash pool or not  for using this code?
ethdcrminer64 -epool stratum+tcp://daggerhashimoto.usa.nicehash.com:3353 -ewal wallet.worker -epsw x -esm 3 -allpools 1 -dpool stratum+tcp://lbry.usa.nicehash.com:3356 -dwal wallet.worker -dpsw x -dcoin lbc


thanks

[moroz]

Claymore, is there any chance to change the logic of pool failover?

Traditional failover (up/down) is kinda useless for ethereum pools. They usually are up, however find kadzillion excuses to reject shares.
I'm talking specifically about dwarfpool and ethermine. Time by time they catch a glitch and reject 100% of the shares.

The latest was dwarfpools "corrupt DAG". At the same time older GPUs on expanse dwarfpool with same miner (7.2) mined ok, so this was obviously issue on the pool side.
The pool is up, but 100% rejecting shares. This doesn't force the miner to switch to failover pool. As a result farm is not just generating rejected shares for half of the night, but also consumes full power for nothing.

Handling this situation miner-side is quite easy, 5 consecutive rejects = GTFO for 1 hour. I don't pretend that numbers 5 rejects and 1 hours are optimal, they are just suggestions.

[amirheavy666]

FOR THIS :
--------------------------------
ethdcrminer64 -epool stratum+tcp://daggerhashimoto.usa.nicehash.com:3353 -ewal wallet.worker -epsw x -esm 3 -allpools 1 -dpool stratum+tcp://lbry.usa.nicehash.com:3356 -dwal wallet.worker -dpsw x -dcoin lbc

---------------------------------
first question :
what we must do for  "WALLET LBRY"?  any site is exist for create wallet?



and second question

 WE MUST have a username for nicehash pool or not  for using this code?
ethdcrminer64 -epool stratum+tcp://daggerhashimoto.usa.nicehash.com:3353 -ewal wallet.worker -epsw x -esm 3 -allpools 1 -dpool stratum+tcp://lbry.usa.nicehash.com:3356 -dwal wallet.worker -dpsw x -dcoin lbc


thanks

ANY GUIDE ?

[Claymore]

hi claymore

is there anyway to switch pool instantly without restarting the miner?

Place pool(s) in "epools.txt". In runtime in v7.2 you can press "r" key to reload this file so you can apply new pool immediately.

[Claymore]

Claymore, is there any chance to change the logic of pool failover?

Traditional failover (up/down) is kinda useless for ethereum pools. They usually are up, however find kadzillion excuses to reject shares.
I'm talking specifically about dwarfpool and ethermine. Time by time they catch a glitch and reject 100% of the shares.

The latest was dwarfpools "corrupt DAG". At the same time older GPUs on expanse dwarfpool with same miner (7.2) mined ok, so this was obviously issue on the pool side.
The pool is up, but 100% rejecting shares. This doesn't force the miner to switch to failover pool. As a result farm is not just generating rejected shares for half of the night, but also consumes full power for nothing.

Handling this situation miner-side is quite easy, 5 consecutive rejects = GTFO for 1 hour. I don't pretend that numbers 5 rejects and 1 hours are optimal, they are just suggestions.

If you got 100% rejected shares, miner will switch pool in several minutes. Miner checks latest 10 shares that it sent, if pool rejected >5 shares, miner will disconnect. After 3 disconnects it will select next pool in the list. If you have a log file that demonstrates that it does not work - PM me it so I can check it.

[giagge]

Guys i dont understand to create a worker on ethpool.org .

use this .bat ethpool:
   EthDcrMiner64.exe -epool us1.ethpool.org:3333 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x

I want create 3 workers .