WOW!
and
THANKS!
keep it up
AMD should release 390x claymore edition
Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1409. (Read 6590757 times)
April 12, 2016, 03:18:14 AM
just want to say
WOW!
and
THANKS!
keep it up
AMD should release 390x claymore edition
WOW!
and
THANKS!
keep it up
AMD should release 390x claymore edition
April 12, 2016, 02:58:38 AM
Dwarfpool don't submit share, if I use format myaddress/rigN
April 12, 2016, 02:22:15 AM
Yeah.. being able to mine to my own running proxy is a must for me. "Login.worker style"..
Nice work none the less.
Nice work none the less.
I will add Login.worker support very soon.
Why do you need a proxy anyway?
Because if you have 20+ rigs, you only need to change proxy settings to do adjustments.
In this case, with new mining software, it's a different story, but still if you want to switch pools after that. A proxy is VERY handy
Ok then I'll create a proxy for my miner, it's not a big deal.
You'll make a lot of people very happy.
Again, great work!
Don't mind the 1% fee at all! Well deserved!
April 12, 2016, 02:09:55 AM
Yeah.. being able to mine to my own running proxy is a must for me. "Login.worker style"..
Nice work none the less.
Nice work none the less.
I will add Login.worker support very soon.
Why do you need a proxy anyway?
Because if you have 20+ rigs, you only need to change proxy settings to do adjustments.
In this case, with new mining software, it's a different story, but still if you want to switch pools after that. A proxy is VERY handy
Ok then I'll create a proxy for my miner, it's not a big deal.
April 12, 2016, 02:08:27 AM
Yeah.. being able to mine to my own running proxy is a must for me. "Login.worker style"..
Nice work none the less.
Nice work none the less.
I will add Login.worker support very soon.
Why do you need a proxy anyway?
Because if you have 20+ rigs, you only need to change proxy settings to do adjustments.
In this case, with new mining software, it's a different story, but still if you want to switch pools after that. A proxy is VERY handy
April 12, 2016, 02:04:36 AM
Although my drivers are crashing, I haven't gone full test mode.. I had a pretty busy day to even think about start testing properly = reformat my PC, re-install drivers and run "correctly".
I'll be back tomorrow with some test results. Got plenty of GPUs to squeeze to the limit as power is not one of my nemesis'.
I'll be back tomorrow with some test results. Got plenty of GPUs to squeeze to the limit as power is not one of my nemesis'.
April 12, 2016, 01:51:17 AM
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.
April 12, 2016, 01:35:37 AM
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
April 12, 2016, 12:50:48 AM
Yeah.. being able to mine to my own running proxy is a must for me. "Login.worker style"..
Nice work none the less.
Nice work none the less.
I will add Login.worker support very soon.
Why do you need a proxy anyway?
April 11, 2016, 11:57:05 PM
Yeah.. being able to mine to my own running proxy is a must for me. "Login.worker style"..
Nice work none the less.
Nice work none the less.
April 11, 2016, 10:54:55 PM
no support for coinotron?
why Login.Worker not supported?
why Login.Worker not supported?
Im hoping he can get it so that login.worker works.
For now i wont use it.
April 11, 2016, 10:52:40 PM
no support for coinotron?
why Login.Worker not supported?
why Login.Worker not supported?
April 11, 2016, 09:54:16 PM
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.
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.
April 11, 2016, 09:41:00 PM
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 ?
April 11, 2016, 07:33:57 PM
During the DAG change some GPUs don't mine properly and get error
OpenCL - cannot write big buffer with DAG
OpenCL - cannot write big buffer with DAG
Confirming just happened and it's always GUP 0
April 11, 2016, 07:32:22 PM
During the DAG change some GPUs don't mine properly and get error
OpenCL - cannot write big buffer with DAG
OpenCL - cannot write big buffer with DAG
April 11, 2016, 07:25:20 PM
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
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
April 11, 2016, 07:22:04 PM
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.
April 11, 2016, 07:17:11 PM
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!
This proxy--> https://github.com/sammy007/ether-proxy
Thanks!
April 11, 2016, 06:35:47 PM
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.
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.
Jump to: