Miner cannot show 5 temps if it found 4 GPUs. If you see it, send me the complete log so I can check it. |
|
|
|
@Claymore, can you make an example line for sia-nanopool for dpools.txt? I cant figure it out...
Thanks!
POOL: http://sia-eu1.nanopool.org:9980/miner/header?address=3be0304dee313515cf401b8593a0c1df905ed13f0adaee89a8d7337d2ba8209e5ca9f297bbc2&worker=YourWorkerName This is the error i got: DCR: http error #22.
DCR: Check username and password, and/or pool state.
DCR: Failed to connect to pool (sia-eu1.nanopool.org:9980/miner/header?address=
bf7487bd3ebc25eedb38f3c815126027125f000dc8fce0ba278f8ec37db86e2737d9edac3681&wor
ker=mladost), retry in 10 sec... You asked me about dpools.txt, my answer is correct. As you can see, miner tries to mine Decred instead of Siacoin. To enable Siacoin instead of Decred, you must also specify "-dcoin sia" in command line or in config.txt. If you ask if you can mine both Decred and Sia via different pools in dpools.txt, the answer is "no", you must select one coin - either Decred or Siacoin. |
|
|
|
@Claymore, can you make an example line for sia-nanopool for dpools.txt? I cant figure it out...
Thanks!
POOL: http://sia-eu1.nanopool.org:9980/miner/header?address=3be0304dee313515cf401b8593a0c1df905ed13f0adaee89a8d7337d2ba8209e5ca9f297bbc2&worker=YourWorkerName |
|
|
|
hey I got problem since 4.6 version with my 270x mining EXP,I have update to last and problem are still here. After dev fee dag stall and it stay at 0 MH  thanks up If you mine EXP, use "-allcoins exp" option from v5.x. |
|
|
|
@claymore:
i'm overclocking my gpu's a bit by using -cclock option, hashrate is fine, but after 2 mins or so hashrate of card0 drops back to normal rate.
(in linux), any clues??
@claymore bump, i think u missed this one.. This is called throttling |
|
|
|
What about ETH solo/Siacoin solo ?
You should test it by your own. I haven't sufficient powers unfortunately. Are you serious ? How i can test Siacoin solo if it even not implemented. Waiting for block will never be found or accepted. Re-read my msg. Right now Siacoin solo is not supported as i see in ver. description. Sia solo is supported. Check readme "SAMPLE USAGE" section: ... ethpool, ethermine (and Siacoin solo): ... I solved three blocks when I tested v5.0. However, right now Siacoin diff is too high to test solo easily. |
|
|
|
I want to point about node isn't see proper miner answer. As you can see in the log SIA part works on ETH share somehow(
Now I see. Fixed, download v5.1 Beta2. Is it needed for all of us ? Only if you mine ETH (or forks) in HTTP mode (solo mode mostly). |
|
|
|
I want to point about node isn't see proper miner answer. As you can see in the log SIA part works on ETH share somehow(
Now I see. Fixed, download v5.1 Beta2. |
|
|
|
Troubles with eth solo in 5.1 (it's Shift, but I hope they are similar)
Piece of miner log with -dbg 1 switch
Node log isn't availiable for now, but it seems it simply works in mining mode (submits works on blocks and imports them). No messages about mining block((((
This log is for about 1 sec. What "mining block" messages do you expect? |
|
|
|
Please implement stratum connection for Siacoin.
As you already know, there's no stratum protocol for Siacoin yet. Fortunately, Siacoin's mining protocol is quite similar as Ethereum, many things can be adapted.
"Nicehash compatible stratum" or "stratum-mining-proxy from coinotron" style would be good.
(I prefer Nicehash version because it locks down minernonce for each miners and it would be compatible for rental service later. coinotron style stratum is also good.)
As current work polling mining method harms pool server and client performance much,
it would be much better when stratum protocol is implemented.
MiningPoolHub will implement pool side when stratum enabled miner is released.
Thanks.
I can add "stratum-mining-proxy" stratum support for Siacoin. Do you need a private version for tests, right? PM me for details. |
|
|
|
P.S. anyway to create a trigger command to auto-restart claymore if it falls below a reported hashrate threshold? For some odd reason, my rig usually reports 120+mhs hashes, but every once and awhile, something goes weird and it gets stuck at 60-80mhs hashes, and I have to restart claymore manually when ever I catch it to go back to 120+ hashes.
Hmm, I never saw such behaviour. If GPU fails it hangs or OpenCL functions fail, so miner can detect it. Anyone else with same problem? |
|
|
|
|
ANN.
I released dual miner for AMD three months ago, still noone created similar public miner for Nvidia (though may be there are private miners, I don't know). I did not expect it.
I have an agreement not to create Nvidia miners, but it is about to expire.
So you will see dual miner for Nvidia soon anyway.
|
|
|
|
Claymore, what about updating monitor manger ? I selected Siacoin for Second Coin but it's all red anyway.
I checked Remote Manager with Sia, both v1.4 and 1.5 works. What's the problem exactly? |
|
|
|
|
v5.1:
- fixed issue with crash in Ethereum solo mode.
- fixed issue in Linux version when http server does not respond.
- increased timeout to detect bad pool state when no jobs are received for a long time.
- added FAQ section to Readme.
|
|
|
|
|
Finally I confirmed issue with ETH SOLO mining, today I will release an update to fix it.
|
|
|
|
Hi!
Is some way to mix Sia and Decres pools in dpools.txt? Cannot find answer...
Thank you!
No. ver 5.0 can't work even with ETH\DCR mode which is working in previous versions (v4.7 v4.5), just copied the .bat DUAL MINING MODE ENABLED: ETHEREUM+DECRED
ETH: HTTP SOLO mode
Ethereum HTTP requests time (-etht) is set to 200 ms
Watchdog enabled
Remote management is enabled on port 3333
Setting DAG epoch #62...
DCR: Stratum - connecting to 'dcr.pool.mn' <136.243.50.159> port 4800 And than it crashed. ETH-only mode was not changed at all in v5.0. |
|
|
|
Any idea why this happens every time after several minutes of opened app? Is the huge number of rigs a problem (350)? I have to kill process with Task Manager every time. Other groups with less rigs don't have this problem..
I did not test Remote Manager with 350 records. Well, now I will try it. |
|
|
|
The problem is if I add FAQ to first post at the end, many people won't reach it. If I add it at top, many people won't read anything after FAQ  Sometimes I feel that I spent a lot of time for creating readme for nothing. Anyway, I will add FAQ soon, and it's not going to be too short; other popular questions are: - Why pool shows less hashrate than miner. - Windows 10 marks miner as a virus. - I see only one card via RDC. - I see only one card instead of two when CrossFire is enabled. - Miner works in ETH-only mode but crashes in dual mode (check PSU). |
|
|
|
weird thing is that i didnt had this before, so dunno why its doing that suddenly
The answer is how long do you mine SIA on nanopool :-) This was an issue with the pool that stopped/delayed responding to network requests. Miner probably had no explicit timeout check and decided that some execution thread was abnormally stopped. So it had to restart. On Windows some network errors detected much sooner (and as a side effect, Windows loses TCP connections instead of trying to wait a bit and recover). On Linux such connections still trying to recover for some time that exceed miner thread execution watchdog timeout. So there was no issue on Windows machines (miners just reconnected), but Linux miners aborted and restarted until pool recovered. This definitely needs a fix because any network issue with the secondary coin pool should not abort mining the primary coin. Yeah, as always, same code works in windows but fails in linux under some circumstances. I will update linux version as soon as I can build it. My linux system decided not to load for some reason and now I have to reinstall it and all software, it takes some time. Nice OS. |
|
|
|
This is something else, but I keep getting this unsupported overdrive version error messages in the log with 3x 480x, they are mining nicely tho, it's just annoying,
what can this be?
Added to OP: - Temperature/fan management for RX 480 is not supported currently. 480 card uses Overdrive v7, latest ADK SDK (v9) supports Overdrive v6, so currently AMD has no public documents about Overdrive v7 and therefore there is no way to manage temperature/fans/clocks of 480 cards. |
|
|
|
|
Show Posts
