Quote from: peterboy1 on February 05, 2018, 06:13:17 AM

what do you mean by most claymore's params work? i cant even control fans in this nor voltages and clocks.

will you implement it in the future?

Yes, we are working on this right now. It would take one or two weeks at least though.

Quote from: akuci on February 05, 2018, 11:35:11 AM

Quote from: Teress on February 05, 2018, 08:54:31 AM

Hi developers. Great job. I have a wish. I love you print all infos in the console, but for better reading it, couuld you please make a sumarization info in some rectangle or divided by the line of "*" symbols? I mean something like this:

Eth: Mining Pirl on eu.pirlpool.eu:8002
Eth speed: 138.635 MH/s, shares: 3/0/0, time: 0:00
GPUs: 1: 24.949 MH/s (0) 2: 24.950 MH/s (0) 3: 25.073 MH/s (1) 4: 24.952 MH/s (2) 5: 19.359 MH/s (0) 6: 19.351 MH/s (0)
Eth: Mining Pirl on eu.pirlpool.eu:8002
Eth speed: 138.635 MH/s, shares: 3/0/0, time: 0:00
GPUs: 1: 24.949 MH/s (0) 2: 24.950 MH/s (0) 3: 25.073 MH/s (1) 4: 24.952 MH/s (2) 5: 19.359 MH/s (0) 6: 19.351 MH/s (0)

***************************************************************
Eth: Accepted shares 3 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 71.9 GH (!)
Eth: Average speed (5 min): 138.129 MH/s
***************************************************************

Eth: Mining Pirl on eu.pirlpool.eu:8002
Eth speed: 138.635 MH/s, shares: 3/0/0, time: 0:00
GPUs: 1: 24.949 MH/s (0) 2: 24.950 MH/s (0) 3: 25.073 MH/s (1) 4: 24.952 MH/s (2) 5: 19.359 MH/s (0) 6: 19.351 MH/s (0)
Eth: Mining Pirl on eu.pirlpool.eu:8002
Eth speed: 138.635 MH/s, shares: 3/0/0, time: 0:00
GPUs: 1: 24.949 MH/s (0) 2: 24.950 MH/s (0) 3: 25.073 MH/s (1) 4: 24.952 MH/s (2) 5: 19.359 MH/s (0) 6: 19.351 MH/s (0)
Eth: Mining Pirl on eu.pirlpool.eu:8002
Eth speed: 138.635 MH/s, shares: 3/0/0, time: 0:00
GPUs: 1: 24.949 MH/s (0) 2: 24.950 MH/s (0) 3: 25.073 MH/s (1) 4: 24.952 MH/s (2) 5: 19.359 MH/s (0) 6: 19.351 MH/s (0)

+1 for this. Dev please notice us. Cheesy

Ok, but this means that two more lines will be "wasted" for formatting and the standard console window has only 25 lines. As a compromise we will put one line of something in the beginning of the detailed stats block but not after it - an empty line should suffice to separate it from the normal log lines.

Quote from: Rewqpro on February 05, 2018, 11:36:00 AM

BTW, I am sorry if this question already has been arised, but what is hashrate for FUry X GPUs?

Our Fury X does 29.85 MH/s with 1000 MHz core and 500 MHz memory. The voltage is 1100 mV and the power draw is 125W according to GPU-Z. Oddly enough, on low DAG epochs (e.g. bellow 100) it does a couple of MH/s more so it is slightly dependent on the DAG size but not nearly as much as 280X for example.

Quote from: superbogel on February 05, 2018, 05:28:08 PM

Hi,

I updated to 2.6 and it keeps on crashing now :

with this error :

CUDART error in CudaProgram.cu

any solutions?

There should be a line number and error code with this message. However there were no changes in this code between 2.5 and 2.6 so the error probably happens because of DAG overallocation, which is on by default (allocating slightly larger DAG buffer to avoid new allocation for the next two DAG epochs). You can add -eres 0 to disable this feature. If the error continues to happen, please see the answer to questin P007 in the first post of this thread.

Quote from: grubiorz on February 06, 2018, 01:03:23 PM

Please add the fan control parameter like fanmin in claymore.

Working on this, will appear in the next two versions.