Hi Claymore,
I have this error just before miner restarts. Sometimes after 50+ hours, sometimes after 20-30 hours of mining. I use Nicehash miner.
This is a peak to the log file:
This is not the log of my miner, so it is completely useless for me. @Claymore I have a problem with one of my RX480 cards. In the log I see before every crash the same message: WATCHDOG: GPU 1 hangs in OpenCL call Now I want to find out which of my GPUs this is! When I start claymore with the parameter " DI -1", can I be sure that it is directly pointing to GPU 1 or does the ordering changes? If you did not use "-di" when it showed this message, then "-di 1" will select the card you want to find. Another way is to start miner as usual and press "1" key to disable GPU1 and check its temperature after a minute, it will be cooler than others. |
|
|
|
@Claymore hi!!!
I have some 2gb cards and they can mine exp, musicoin , ubiq ect... and i can make Profit ! İf ı add -nofee 1 no problem miner works . Otherwise miner stops when try to mine eth for you. Can u fix that issue ?? I am sure lots of ppl has 2gb cards and needs this. Thx !!!
Try "-allcoins exp" option. Sometime EthMan stops work properly - show all rigs offline and if i try close there are error message "Cannot terminate an externally created thread". Need kill and restart process via ProcessExplorer.
How many rigs in EthMan do you have? Currently I'm rewriting some parts of EthMan, network routines too, probably it will help. |
|
|
|
Claymores miner is reading my RX 580 as a RX 480. I have 2 RX 480's as well. Is this normal?
It is normal. |
|
|
|
Claymore - When "s" is pressed for information can you add shares found per GPU? I know it doesn't really matter but I think it would be interesting to see if one is finding more shares than the other over time.
+1. Asked before of this. No answer. Here you can see all my messages: https://bitcointalk.org/index.php?action=profile;u=306958;sa=showPostsCheck this one: https://bitcointalk.org/index.php?topic=1433925.msg18855705#msg18855705This info can be useful only if miner is working for >100 hours, for shorter periods values will be almost random and you will think that something is bad with some card and ask why... I will add it and I will refer to this message every time when someone asks me that question  |
|
|
|
I think I have identified a problem in the API output of the miner. When I'm running it on my system where I have one AMD and one nVidia card, I get the following temperature and fan reading from the API:
"79;4772;59"
The expected output should be on the format GPU#0 Temp; GPU#0 Fan; GPU#1 Temp; GPU#1 Fan
"79;47;72;59"
The result is that Awesome Miner doesn't display the correct temperature and fan information when mining.
I'll check it and fix in next update if I can confirm it. Claymore - When "s" is pressed for information can you add shares found per GPU? I know it doesn't really matter but I think it would be interesting to see if one is finding more shares than the other over time.
Yes it is almost useless info. But ok I will add it in next update. i would like to read data from json format somebody can explain this value: (unknow)
{"result": ["9.3 - ETH", "21", "182724;51;0", "30502;30457;30297;30481;30479;30505", "0;0;0", "off;off;off;off;off;off", "53;71;57;67;61;72;55;70;59;71;61;70", "eth-eu1.nanopool.org:9999", "0;0;0;0"]}
9.3 version
21 ? unknow
182724 hashrate, share, reject
30502 hashrate for gpus
0;0;0 unknow
off;oof unknow
53,71 temp/fan %
eth-eu miningpool
0;0;0;0 unknow
I will describe json format soon. 21 - working time, in minutes. "0;0;0" - hashrate, share, reject for second coin "off;off;off;off;off;off" - hashrate for gpus for second coin "0;0;0;0" Eth Invalid Shares, Eth Pool Switches, second coin Invalid Shares, second coin Pool Switches |
|
|
|
If it's stopping also whatever is running in the command prompt then hats off to M$ for a awesome feature. /sarcasm off
Exactly. |
|
|
|
Hi All,
I currently trying to use 9.3 to Mine Eth but it does not seem to work properly with Dwarfpool, it connects but does not receive any jobs and then Disconnects, I have tried other pools and they works mining Eth and Dwarfpool EXP works fine, I have been able to connect in the past, any ideas anyone?
Regards,
Andy
I use Dwarfpool with 9.3 and have no issues. Here are my settings: EthDcrMiner64.exe -wd 0 -epool eth-us2.dwarfpool.com:8008 -ewal 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.worker1 -epsw x -mport -3332 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal AccountName.worker1 -dpsw 1 -dcri 25 -allpools 1 It seems Dwarfpool blocks default wallet address that is used in readme as a sample wallet, I see it for EXP at least. So make sure that you changed it to your wallet address. In the log file you will see "socket closed remotely" message in this case, this pool just closes connection if it does not like the wallet. |
|
|
|
Hello Claymore / forum,
I really need a hand with this one, not sure how to fix:
Check FAQ section in readme or OP. |
|
|
|
On both version - v9.0 and v9.3 I have the same cpu usage on (latest G4560 3.5 GHz) about 1-2% overall cpu usage of whole system
If you are sure that the reason is the miner, not your pool or internet connection, you can create two log files and PM them, I will compare them. |
|
|
|
Hi Claymore and Community.
I'm switched from 8.0 to 9.3 and noticed that time of share accepted increased 2-3 times. And totally effected pool average hashrate.
See below, (dual-mining or single mode result the same):
Version 8.0
ETH: Share accepted (62 ms)!
Version 9.3
ETH: Share accepted (156 ms)!
ETH: Share accepted (172 ms)!
So, seems this affect hashrate and I lost around 10% in 24 hours period.
Any suggestion are welcome, thanks in advance.
Yes, I have also on v9.3 increased share submit time, from 31 to 70 ms on v9.0 to 150 ms and more on v9.3. Thats a huge step back, because it causes less accepted shares and huge drop on accepted hashrate on pool. So I'm back on v9.0 (RX470 4GBs, RX480 4 and 8GBs, nanopool) Also lots of ETH: Job timeout, disconnect, retry in 20 sec.... Back to 9.0 is not a solution..... Need proper improvement or advice. Lets hope Claymore read it and will find a solution. I cannot confirm it, I see the same time. What CPU do you have and what CPU load do you see in Task Manager in "good" and "bad" versions? |
|
|
|
@Claymore - your warning system on ethmon is not working properly. When the batch file runs, it always returns "1" for %2 variable, regardless of whether the rig is overheating, low hash, or offline - it will always return "1". Please fix this! Thanks!
Just check it, it works properly. My test: 1. Start miner and EthMan. 2. Add miner to EthMan, set zero delay for BAT file. 3. In miner properties, set target hashrate x2 more than miner produces. BAT is started immediately, sample.bat shows "Problem ID: 3". 4. Return target hashrate to zero. 5. Set target temperature as 10C. BAT is started immediately, sample.bat shows "Problem ID: 2". If you get some different result, let me know step-by-step guide how to reproduce the issue. |
|
|
|
I'm confused.
Why did you set both "-di" and "-gmap" to the same value? This way you changed order in list of GPUs, then did the same for the list of temperatures. So both list will match again. But original (default) match is not good for your system. That's the answer. Use "-di" only, remove "-gmap". |
|
|
|
v9.3:
- improved dual mining speed stability in ASM mode.
- added "-altnum" option for alternative GPU indexing.
- a few minor bug fixes and improvements.
Oh bugger ... just spent the last hour updating all my rigs to 9.2 ... LOL  Thanks Claymore, not complaining! Soon I will add ability to update miners on all rigs with EthMan so it will be easy. That could be tricky... but interesting. not sure if 9.3 is any better it still seems to need "-eqlim 288" form my 470s and still jumps around 0.3-1.3% of hash EDIT: well maybe it has a notch higher speed than 9.2 ... like 0.2% This is a bug of Linux drivers, it reports wrong number of CUs: https://community.amd.com/thread/207051It seems this bug was finally fixed in 16.60 drivers, so you can try to use it and see if it works properly without -eqlim option. If you cannot use 16.60, miner will fix 14->36, so it must work fine for RX480 (see the string "14 CUs is wrong, use 36" in the log). However, due to this bug there is no way to detect if you use RX480 or RX470, so for RX470 you should use "-eqlim 256" (32CUs * 8 ). |
|
|
|
Slower than 9.1 and 9.2, and no speed improvement on etc only  back 9.2 version It would be very useful to mention what GPU you use. |
|
|
|
v9.3:
- improved dual mining speed stability in ASM mode.
- added "-altnum" option for alternative GPU indexing.
- a few minor bug fixes and improvements.
Oh bugger ... just spent the last hour updating all my rigs to 9.2 ... LOL Thanks Claymore, not complaining! Soon I will add ability to update miners on all rigs with EthMan so it will be easy. |
|
|
|
|
v9.3:
- improved dual mining speed stability in ASM mode.
- added "-altnum" option for alternative GPU indexing.
- a few minor bug fixes and improvements.
|
|
|
|
ClayMore 9.2 is strange-asm 2, ETH SOLO ASUS, Gigabyte, MSI / Hynix, Samsung / 470, 480 SO -dcri is: 3, 13, 25, 45, 50, 55On all 6 rigs diffrent -dcri  BUT hashrate increase if compare with ClayMore 8.1 The next release of the miner might solve this problem. For ASM mode, best -dcri value depends on many factors like clocks, memory manufacturer, etc. It is not a bug. If you don't like to spend time trying to find best -dcri value - use "-asm 0" though it can be a bit slower. May be in future I will add automatic adjustment for -dcri. I managed to get speed similar to v9.0 with speed stability better than in v9.2. I will release new version in 2-3 days including this and some other improvements.
@Claymore the release will be today? Yes I will release new version within a few hours. |
|
|
|
@Claymore the latest 9.2 version consume the Eth for the DCR even with lowering the -dcri in ver 8.1 was getting 31.1MH Eth + 575 MH DCR per card and stable with temp 55~58 now 30.8 MH eth + 450 DCR unstable with 61 ~ 65 TEMP Please undo the changes i cannot run the old 8.1 ver cz DCR stopped there "-asm 0" is for you. |
|
|
|
|
I managed to get speed similar to v9.0 with speed stability better than in v9.2. I will release new version in 2-3 days including this and some other improvements.
|
|
|
|
|
Show Posts
