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

[phzi]

I cannot find any Ethereum mining info on "f2pool.com". Perhaps it does not accepts wallet addresses but requires Login.Worker username format, such pools are not supported.

https://www.f2pool.com/help
"
eth.f2pool.com:8008

How to mine Ethereum at F2Pool?

Please configure your eth-proxy set either WALLET to your payout address or MONITORING_EMAIL to your F2Pool user name or login email. If you leave MONITORING_EMAIL empty, the workers page is available at https://www.f2pool.com/eth/<account>. Otherwise you can also check your account info on your logged-in dashboard.
"

Based on the console output, it just seems your miner doesn't understand the work JSON.

[Genoil]

tested mode 1 against my 1.0.7b on ye olde 7950. mine seems just a bit faster (like 100KH/s), although the difference is more likely to be result of a different way of calculating the hashrate than a real difference in performance.

[adaseb]

tested mode 1 against my 1.0.7b on ye olde 7950. mine seems just a bit faster (like 100KH/s), although the difference is more likely to be result of a different way of calculating the hashrate than a real difference in performance.

Yeah I noticed the same thing, however with his miner my GPUs are all at 100% pretty much with yours they range from 97-99%. So who knows which is faster. Impossible to test since speeds are almost the same.


Claymore, do you know when MiningPoolHub will be added ?

[Jacques21]

for some reason it shows 0.00 mh/s

[melloyellow]

nanopool doesn't seem to work with the stratum port, 9999.  The miner finds and submits shares, they just don't show up in stats.

[Claymore]

I will check/fix all pools that you mention here within 24 hours.
PS. It seems dwarfpool (at least eth-eu.dwarfpool.com:8008) is working properly now, no rejects. So the problem was on their side.

[melloyellow]

I will check/fix all pools that you mention here within 24 hours.
PS. It seems dwarfpool (at least eth-eu.dwarfpool.com:8008) is working properly now, no rejects. So the problem was on their side.

It looks like it has something to do with adding the worker name to the end of the eth address at nanopool.  I erased my workername and the rig showed up.

Thanks Claymore.

[helipotte]

Will support for solo mining be added?  Maybe solo mining using a "proxy" like Etherproxy.  Format is //192.168.1.50/miner/50/miner_name

This proxy-->  https://github.com/sammy007/ether-proxy

Thanks!

[phzi]

I will check/fix all pools that you mention here within 24 hours.

Claymore the man!

Ethereum's "stratum" is a bit of a disaster.  Tons of different implementations that vary slightly.

[Nikolaj]

thanks for the very nice tool claymore !

btw It seems that there are some issues with the values reported:

client side 25.401 ETH, pool side 18
client side 1260 DCR, pool side 800

[adaseb]

During the DAG change some GPUs don't mine properly and get error

OpenCL - cannot write big buffer with DAG

[murders10]

During the DAG change some GPUs don't mine properly and get error

OpenCL - cannot write big buffer with DAG

Confirming just happened and it's always GUP 0 

[fr4nkthetank]

I have heard through the grapevine you can have the miner up and running, then load sgminer and mine something else ?  how does this affect the gpu ?

[bensam1231]

Looks as though AMD miners aren't seeing a huge benefit from merge mining on lower end AMD GPUs. Higher end ones are giving a boost in DCR mining. I'm guessing this due to the fact that the GPU is actually being utilized and it's not completely memory locked.

Nvidia GPUs would see probably pretty close to full utilization on DCR considering they're pretty memory bound with ample GPU processing.

Consider making it compatible with Nvidia GPUs as well... they also support OCL, so it wouldn't need to change to support CUDA.

[peteycamey]

no support for coinotron?

why Login.Worker not supported?

[Jacques21]

no support for coinotron?

why Login.Worker not supported?

Im hoping he can get it so that login.worker works.

For now i wont use it.

[Eliovp]

Yeah.. being able to mine to my own running proxy is a must for me. "Login.worker style"..

Nice work none the less.

[Claymore]

Yeah.. being able to mine to my own running proxy is a must for me. "Login.worker style"..

Nice work none the less.

I will add Login.worker support very soon.
Why do you need a proxy anyway?

[Ayers]

this work with the proxy for dwarf? because i'm mining with a sensible increase in profit with that proxy i don't want to give up to it

[Claymore]

this work with the proxy for dwarf? because i'm mining with a sensible increase in profit with that proxy i don't want to give up to it

It seems many people don't understand how it works so I need to put some explanations here.
What is dwarfpool proxy (eth-proxy)?
Official Ethereum miner does not support Stratum protocol, it supports HTTP protocol only. It causes less profit because of delays.
A proxy was created to fix it, so official Ethereum miner is locally connected to the proxy by HTTP protocol, for local network delays due to HTTP protocol are small. Proxy is connected to the pool via Stratum protocol so it has small delays too. Currently most pools support Stratum and you have to use HTTP-to-Stratum proxy to make official miner work with pools properly. Of course you can try to connect official miner to a pool directly via HTTP but you will lose 10-20% shares because of a short block time in Ethereum.
My miner does not use HTTP protocol, it uses Stratum. So you should connect it directly to the pool at Stratum port and it will work a bit faster than official miner via proxy because there is no proxy between miner and pool.