How should I know?


You are right. But if you put example strings for various pools, then you can combine some text and config lines. Let's say:

When I put in the config:

as you say, then the miner doesn't send a worker name to the pool with every share submitted, but the pool understands correctly, that it is from "rig2" and also shows the "Sent Hashrate" value. A little confusing, but OK )  I just suggest to add exactly this format to the sample epools.txt file

Claymore, I think, there is a bug in the config reading section.

In file epools.txt
If I don't put the space symbol between WORKER: and worker name, it always sends

14:28:22:803   b88   send: {"id":4,"method":"eth_submitWork"...}

with no worker name inside.

If I add the space symbol, everything's fine:

14:21:34:911   c8c   send: {"worker":"rig08","id":4,"method":"eth_submitWork"...}

I would also recommend to change the example config a little. Put in the epools.txt

WORKER: YourWorkerName,

instead of confusing

WORKER: ,

And, specially for dwarf:

# POOL: eth-eu.dwarfpool.com:8008, WALLET: 0x..., PSW: YourWorkerName, WORKER: YourWorkerName, ESM: 0, ALLPOOLS: 0

I mean that you have to send the worker name in the PSW field to see it on the stats page of dwarf

Mr. Claymore, when I see this n the log, I have no idea, what is this


When the answer from the pool is OK, it shows JSON data. But in this case there is no data at all. What are those 18 bytes? I even can not provide you with the data.

Background:
Mining on dwarf stratum port 8008. epools.txt via 4.2b2:

How do you get these 900-1000 of DCR? I have twice less on every of 50 pieces of R9 390 ( What command line do you use? What are the "dcri" and  "ethi" parameters? The manual tells us that "by default (-dcri 30) 390 card shows 29MH/s for Ethereum and 440MH/s for Decred. Setting -dcri 70 causes 24MH/s for Ethereum and 850MH/s for Decred" So, to get 850Mh/s in Decred you must significantly decrease Ethereum performance.

Guys, how do you set up Suprnova decred stratum in dpools.txt? I mean

stratum+tcp://dcr.suprnova.cc:2252

HOW did you get such a huge speed in Decred?! My 390 earns twice less! While doing the same speed as yours in ETH. What is the command line? What is the mem/cpu clocking?

What I do now. I just let Windows 10 to find the latest driver for AMD Radeon R9 390 wherever it wants during the install process. I really don't know the version of the driver installed. MSI Afterburner usually shows it on the top of the window. But in this case there is nothing

But the Claymore's miner works just fine anyway, regardless the driver version and the virtual memory size (it is set as by Windows default).

I deleted a symbol from the middle of the wallet address in the command line somehow. So, it was 19 digits only. This was the problem.

The only one rig has this problem.

If I start it without "-allpools 1" option it can't connect to devfee pool and exits. If I start it with this option, then it starts, gets jobs but doesdidn't send the results back. I see in the log file:



DCR is working perfect here. The problem is only with ETH.

My start command is

What could it be?

v 3.3

It's strange. After starting this version first time it says that the DAG file is corrupted on EVERY my RIG of 6. But the problem was with only one of them. The others were mining well instead. So, it looks like the DAG with the wrong CRC doesn't mean that you can't mine... Or... like something wrong with the DAG file integrity check in the miner.

But, thank you, Mr. Claymore )

There was no such a section at all ) Until I return "Enable low-level..." from "core" to "user" value. But...

If I set memory clock to 650 on my MSI R9 390 *3 then the hashrate drops to 21Mh from 31.3 ) So, I've switched back to 1100/1500

Where is this option? I can't find. Settings? First tab? There is no such an option. Latest Afterburner. 15.12 crimeson

How to understand, which particular card is GPU0 etc?

@Claymore

Mr. Claymore, it looks like your miner detects GPUs in the different order than MSI Afterburner. Is it correct? Could you, please, synchronize your method? It is not convenient to control what's happening with cards now.

Mr. Claymore, can you, please, add -dbg option or another one to duplicate the console output to the separate log file. The current dbg 0 is really too wordy.

Thanks for this update!

How to find in the log when -r option is activated? I mean, if something wrong with a GPU, how to find it in the log file. To understand the statistics.

+1 Sometimes just restarting doesn't help. It could be an option

-forcereboot X

X - number of attempts to restart the thread with no effect. If X=0 then "never"

If you mean, that the miner suddenly stops sending worker name, then I confirm. Just saw this. It should be rig1 and rig2. But actually looks like an empty name.

When do you expect to release p.1?

P.S. Many thanks for the coloring in console!

A nice miner. But help me, please, with the following.

I see om dwarf a low speed. I go to check the miner. It shows that all 5 GPU is working perfectly, the speed is as usual. But looking at one of the cards, I see it stops working. Fans are stopped and it's cold. But the miner says that everything is fine. I restart the miner and it runs good as usual. I have 3 questions.

1) Is it a bug, that miner shows a working card that is not actually working?
2) How to understand from outside, that any card stopped, to restart the miner?
3) Is it possible to add this control inside the miner?

While using the standard eth.exe I could redirect the console output to the log file and check this file from time to time. If it stopped to change, I just restarted the miner or rebooted the rig. How to monitor this miner?

P.S. Will check, if the problem persists on 1.2
P.P.S. Thanks for the coloring!!!