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

[zorvalth]

This now means that the algorithm does not require additional files, which opens the way Asic .

No asics, I just decided to solve issues with DAG files completely, I planned to do it later but after Wolf0's phrase "goddamned DAGs" I understood that I must do it right now Now I generate DAGs directly on GPUs so no DAG files are used at all.

And no slowdowns on restart?

If you have HDD, not SSD, you will see that v4.0 starts much faster. If you have slow CPU you will see the same.

So it doesnt take 10 mins on every restart to generate the dag on the gpu mem directly? You Rock!

[1713255027]

1713255027

[1713255027]

1713255027

[1713255027]

1713255027

[1713255027]

1713255027

[elzium]

It took under 10 seconds on 270x

[Marvell1]

@claymore is the solo mining proxy bits in on the version 4 ?


also how does it work with no DAG i'm confused

*edit dag on the GPU** not sure what that means but you're the developer lol

[Claymore]

Solo mining support and Linux version are planned, I'm working on it.

[o00o]

@ Claymore

I updated to v3.3 from a previous 3.x version and was no longer able to mine due to failing to create a big buffer.  I was forced to revert to v 1.2 to resolve the issue as any other builds replicate the problem.  Absolutely no changes were made to the system in question; all I did was close the previously working miner and updated the directory's contents. All environment variables have been set as well as 2 x 8 GB pagefiles and I've also removed temp files as well as the dag directory which I additionally decided to provide an alternate one on a seperate hard drive to hopefully eliminate the problem.  I also tried renaming the dag files successfully created by QTminer in hopes of using them with Claymore's but that also didn't work. My other rig which is also Hawaii based surprisingly doesn't suffer from this symptom.  I just gave v4.0 a try but still suffer from the same error.

Any feedback would be much appreciated!

[madmartyk]

4.0 installed and working great. Only .5 MH less on the speed.

[Claymore]

4.0 installed and working great. Only .5 MH less on the speed.

It must have same speed.
If you are sure that v3.3 works faster for current epoch #47 - PM me the log files for both v4.0 and v3.3 so I can check it.

[madmartyk]

4.0 installed and working great. Only .5 MH less on the speed.

It must have same speed.
If you are sure that v3.3 works faster for current epoch #47 - PM me the log files for both v4.0 and v3.3 so I can check it.

I was still on 3.2, never upgraded to 3.3

[Claymore]

4.0 installed and working great. Only .5 MH less on the speed.

It must have same speed.
If you are sure that v3.3 works faster for current epoch #47 - PM me the log files for both v4.0 and v3.3 so I can check it.

I was still on 3.2, never upgraded to 3.3

v3.2 uses "-ethi 16" by default, v3.3 and v4.0 use "-ethi 8" by default, so add "-ethi 16" to command line to use same settings. If you still have different speeds with "-ethi 16", PM logs for both versions.

[Trimegistus]

After six hours. Still working rock solid, in the cold systems room.

Many thanks Trimegistus...

Good news! You're welcome 

[madmartyk]

4.0 installed and working great. Only .5 MH less on the speed.

It must have same speed.
If you are sure that v3.3 works faster for current epoch #47 - PM me the log files for both v4.0 and v3.3 so I can check it.

I was still on 3.2, never upgraded to 3.3

v3.2 uses "-ethi 16" by default, v3.3 and v4.0 use "-ethi 8" by default, so add "-ethi 16" to command line to use same settings. If you still have different speeds with "-ethi 16", PM logs for both versions.

That did it

[murders10]

Thank God - no DAG files anymore.
the best thing u ever did Claymore.

Thank you.

[tlmoscow]

Good job! Waiting for proxy & webstats/monitor!

[crazyearner]

Fairly interesting to see this mining with ETH-only produces a higher rate than using eth miner even with 1% fee taken out is a big improvement.

Not sure how you guys tweekd or what tweed and improved on it but ya done something so my 1% is welcomed.

Only thing I do notice a drop on is earnings when dual mining is on with decred and see a 20 to 30% drop in hash on pool and get a fair few rejected shares on Decred too. Mining goes to about 50MH out of 60MH using R9 x280x gpus and tried changing settings but makes no odds most I managed to cut it down to is 20 to 25%. Any advise on how can improve this. Thinking to just mine ETH mode only.

[revelacaogr]

look something crazy!

BitClub Mines Block 409008 and Gets a $136,000 Fee

http://bitcoinist.net/bitclub-network-mines-colossal-fee/

[crazyearner]

look something crazy!

BitClub Mines Block 409008 and Gets a $136,000 Fee

http://bitcoinist.net/bitclub-network-mines-colossal-fee/

And what does this have to do with the miner and ETH?. Nothing. So post this elsewhere wayyyy off topic.

[markoz]

on my 270 rigs i get slower hrate

v3.2 ~ 57.2

v4.0 with ethi 16 ~ 55.9

cards are 5-10c hotter that on v3.2

will test it on 380

edit: on 380 everything is ok

[Claymore]

on my 270 rigs i get slower hrate

v3.2 ~ 57.2
v4.0 with ethi 16 ~ 55.9
cards are 5-10c hotter that on v3.2
will test it on 380
edit: on 380 everything is ok

At this moment I have a few reports about slower hashrate. And after checking all they are not true.
Two reports were about previous epoch #46 for v3.2 and epoch #47 for v4.0, that's the reason.
Two reports were about "-ethi 8" that is used in 3.3 and v4.0 that uses "-ethi 8" by default.
And one report was related to both reasons at once

If you are still sure that v4.0 is slower with "-ethi 16" option on epoch #47 than previous versions on same epoch - PM me logs for both versions so I can check the reason.

[Trimegistus]

If you are still sure that v4.0 is slower with "-ethi 16" option on epoch #47 than previous versions on same epoch - PM me logs for both versions so I can check the reason.

v4 is working flawlessly on my rigs and on my PC 

[MacT]

@Claymore in my command line i use ethermine with eth-proxy:

Code:

EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal 0x8d5ad572f59fbc5bb********266d3083ea9290.RigName -epsw x -esm 0 -mode 1 -wd 1 -r 1 -dbg -1  -etha 1

Because there is no way to check if my failover is set properly does it suppose to look like that:

Code:

POOL: us1.ethermine.org:4444, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290, PSW: x, WORKER:RigName , ESM: 0, ALLPOOLS: 0
POOL: eth-eu.dwarfpool.com:8008, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290, PSW: x, WORKER:RigName , ESM: 0, ALLPOOLS: 0

or should i put the name of the worker after the wallet separated wit dot?

 Unplug your net for a few seconds and it should fail.