|
1. Job timeout, disconnect, retry in 20 sec...
Dwarfpool has some problems. Not only today but for a few days already. Check dwarfpool thread.
2. With the normal ethminer you can set an email option while mining on dwarfpool
Use "-epsw YOUREMAIL".
|
|
|
|
Is there a way to NOT send 'reported hashrate' to ethermine.org? That feature adds a focus grabbing green bar to the charts there that makes it difficult to get the popup numbers I actually want to see.
Use undocumented option "-erate 0". Available in all v4.x. It will be documented in next update. |
|
|
|
Thank you for the release. But i can't understand why my own monitor utility connected direct to the wallet shows the hashrate only for original ethminer. My request code "{"jsonrpc":"2.0","method":"eth_hashrate", "params":[],"id":71}";Maybe you can look at this issue ? Miner does not send hashrate in http mode. I thought it is useless. So you can see sum hashrates from all ethminers somehow? Explain how you do it and I will check it. |
|
|
|
My miner does not use any sources from ethminer, so any bugs/fixes related to ethminer are not related to it. |
|
|
|
completely useless bug report follows, but I feel obligated to offer it.
4.1, dual mining in linux. after several days,
read(): Resource temporarily unavailable
read(): Resource temporarily unavailable
read(): Resource temporarily unavailable
read(): Resource temporarily unavailable
read(): Resource temporarily unavailable
read(): Resource temporarily unavailable
read(): Resource temporarily unavailable
read(): Resource temporarily unavailable
read(): Resource temporarily unavailable
attempts to restart just hang.
Was fixed a few days ago, re-download v4.1 or use 4.2. |
|
|
|
v4.2 Beta2: Fixed issue with fans.
About wrong GPU indexes: I explained it a few times, now added to "KNOWN ISSUES" in OP.
If I do not use the fan speed options, do I need to upgrade to the V4.2 Beta 2? Or what is the issue with fans? By default (no "-tt" option or "-tt 1") v4.2 Beta resets fans management to default, i.e. AMD drivers will manage fans. So it's ok if you don't use Afterburner to manage fans, but will cause a problem if Afterburner is used. v4.2 Beta2 does not reset fans management so Afterburner can manage fans. |
|
|
|
|
v4.2 Beta2: Fixed issue with fans.
About wrong GPU indexes: I explained it a few times, now added to "KNOWN ISSUES" in OP.
|
|
|
|
Hello, This regards the following error: "OpenCL error - 4 - cannot create DAG on GPU" 4 cards mine and one doesn't. If I change the cards or PCI slots, the problem will move from GPU to another. Where before it was GPU1, then it became GPU 4. I am running windows 8.1 from a 64usb drive. When formatting the USB drive I formatted it the maximum amount of virtual memory, which was 59gb or so. I can't imagine what is giving this issue. After 10 minutes or less this dual miner requested to shut down because it was out of memory also. Any ideas for solutions please? I've noticed I'm not the only one who has had this issue but I could not find a resolution for them. This is the .bat file I am running: setx GPU_SINGLE_ALLOC_PERCENT 100 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_USE_SYNC_OBJECTS 1 setx GPU_MAX_HEAP_SIZE 100 setx GPU_FORCE_64BIT_PTR 0 EthDcrMiner64.exe -epool us2.ethermine.org:4444 -ewal address -epsw x -eworker Worker01 -ethi 8 -mode 1 I tested if it is this is hardware related also. Disconnected a random card. Then 4 cards mined without errors. Reconnected that card, and now disconnected another card. This second lot of 4 cards also mined without any errors, hence eliminating the idea that this is a hardware issue. Cheers Claymore, do you have any advice on this please? I have 20 R9 280xs that would love to start mining with your program  "clEnqueueNDRangeKernel" function returns "CL_MEM_OBJECT_ALLOCATION_FAILURE" error from your log. It is something system-related. Actually this question is to AMD drivers developers team, not to me, I have no ideas why OpenCL cannot reserve GPU memory for DAG on your system, sorry. |
|
|
|
That sounds great. Can you give us any hints as to how it will work? I need update to the newest version of the miner (from 3 to 4) but if the utility has to work with a newer version of the miner, I may just wait until that version comes out.
Yes this utility will not work with v4.2 because this version does not support remote management. |
|
|
|
v4.2:
- added support for Ethereum solo mining.
- added "-gser" option.
- added "-eres" option.
- added "-powlim" option.
- added "-etht" option.
- "-tt 1" (default) now does not manage fans but shows GPU temperature and fan status.
- added support for "client.reconnect" stratum command for Decred.
so we can point this version to eth-proxy? Yes it will work, but currently HTTP mode is not intended to work with proxies, so probably worker names will not work, I did not check it. Why do you want to use eth-proxy? Proxy between miner and pool can cause delays and other problems. It's much easier to change pools once than to change it on several miners. The HTTP requests on a local network won't have much delay and eth-proxy is connected via stratum to the pool, right? For some reason I just have a personal preference for it, I guess. I thought you were always going to add a single-instance proxy to the miner setup and this was a step towards your monitoring implementation, maybe I misunderstood. I will release an utility for monitoring and changing settings for all miners at once. So right now using a proxy can be useful, but in a few days it will have no benefits. Also, eth-proxy can help with Ethereum pools, but not with Decred pools. |
|
|
|
v4.2:
- added support for Ethereum solo mining.
- added "-gser" option.
- added "-eres" option.
- added "-powlim" option.
- added "-etht" option.
- "-tt 1" (default) now does not manage fans but shows GPU temperature and fan status.
- added support for "client.reconnect" stratum command for Decred.
so we can point this version to eth-proxy? Yes it will work, but currently HTTP mode is not intended to work with proxies, so probably worker names will not work, I did not check it. Why do you want to use eth-proxy? Proxy between miner and pool can cause delays and other problems. |
|
|
|
-eres this setting is related to Ethereum mining stability. Every next Ethereum epoch requires a bit more GPU memory, miner can crash during reallocating GPU buffer for new DAG.
To avoid it, miner reserves a bit larger GPU buffer at startup, so it can process several epochs without buffer reallocation.
This setting defines how many epochs miner must foresee when it reserves GPU buffer, i.e. how many epochs will be processed without buffer reallocation. Default value is 2.
If we use big eres, will that affect the mining speed? Like bigger DAG?
-eres does not change mining speed at all. It just changes the buffer size. So if you don't have any problems with GPUs you can set "-eres 5" to make miner use the same buffer for five epochs (25 days). By default -eres is "2" so after 10 days miner will have to reallocate GPU buffers and may crash. Buffer size itself is not related to the mining speed. Mining speed is slower with every next epoch because the data size in the buffer is growing. |
|
|
|
|
v4.2:
- added support for Ethereum solo mining.
- added "-gser" option.
- added "-eres" option.
- added "-powlim" option.
- added "-etht" option.
- "-tt 1" (default) now does not manage fans but shows GPU temperature and fan status.
- added support for "client.reconnect" stratum command for Decred.
|
|
|
|
|
It takes a lot of time to test solo mode, I put all my cards on it, but still not enough and I have to wait for many hours, network diff is too high. Anyway, even if I cannot find a block, I will release v4.2 in a few hours because it works with eth-proxy so it must work with geth as well.
|
|
|
|
Hi Claymore
Could you please check 390x coreclock issue, when i mine with genoil miner clock is same as msi afterburner setting
but with your miner it drops around 950 with slight fluctuations.
tanx
I have MSI 390X stock, afterburner shows correct clock 1040MHz, no drops. Probably your card throttles, check its temperature. |
|
|
|
|
This utility will be available in a few days, I'm already working on it.
|
|
|
|
Even with ethi 20 there are no differences as well. so what are the ethi doing then? hmm
In recent versions, max -ethi value is 16. This parameter is related to the number of hashes that GPU checks in one round. Small values allow you to reduce GPU load and reduce Windows freezes. After some value it is useless to increase this parameter because GPU is already loaded 100%. |
|
|
|
Claymore - do you think further optimizations for fiji chips are possible? Memory controller usage seems to be sitting pretty low, and I get the feeling after playing with intensities that there's more room left for optimization.
It seems a higher ethi allows for increased decred hashrate without ethash loss. I am now pushing ~30MH/s ethash and 1650MH/s decred with ethi 20 and dcri 110. With ethi 16, dcri can't go that high without losing a chunk of ethash. Compare that to 30MH and under 1000MH/s decred max with lower ethi.
I tried several ways to improve performance for fiji but they failed. Had to postpone these attempts because of other features. However, I don't think that it is possible to get big speedup. @Claymore
Could you make the ethi intensity change easily adjustable like dcri? So that I could test the speed out on different ethi without closing the miner. Currently ethi 8 and ethi 16 has no difference on my rate, which I don't know why.. You have any idea about that?
Default -ethi 8 is good. Setting values between 8 and 16 almost will not change hashrate, but high values will cause more latency when miner gets new job because there is no way to cancel current GPU round. I need a proxy for group management, so in other words I want to point a bunch of rigs using this miner to a proxy so I don't have to mess with each rig individually but I would be able to just edit/change the proxy config.
The problem with dwarfpool stratum-proxy is that it works only one way Stratum=>getwork, and I need a proxy that support Stratum<=>Stratum, any Ideas ?
Or use an utility that can connect to miners and show their status and also allows you to send them updated pools settings, this way you can apply new settings for all rigs at once. |
|
|
|
|
Within 24 hours I will release version with Ethereum solo mining support (and with some new options/features).
|
|
|
|
|
Miner shows GPU temps and fan speed every 30 seconds if you specified "-tt" parameter to manage fans.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
|
|
|
|
|
Show Posts
