Claymore's CryptoNote AMD GPU Miner v11.3

[Eastwind]

I think Claymore has milked the last bit from his excellent miner.

[Claymore]

Claymore, i remember very often updates of your miner, what causes of stopping ? No potential of improving ?

Currently I don't see any ways to improve performance. But I promised to release a minor update, I'm uploading it right now.

[Claymore]

v9.2 is available:

- Improved stability in some cases.
- Added 285 card native support.

[tearsdontfall]

in my core i5 4th generation i get about 186+ h/s ...


but the speed is not constant 186+ ... most of the time it goes down to 100+ ...


is there any way i can make it constant speed of 180+ ??


please tell me

[minerador]

Claymore: can you build v9.2 for Linux?

[Claymore]

Claymore: can you build v9.2 for Linux?

Not right now, but I will do it.

[FakeAccount]

ESET detects a virus in the latest download zip from mega.

[Claymore]

ESET detects a virus in the latest download zip from mega.

https://bitcointalk.org/index.php?topic=647251.msg7908079#msg7908079

[MarkMJ]

Hello dear,

I will testing this next month,in my opinion currently it is waste of time. 

[Hueristic]

What are the li options? Just "1"? I would like to lower the intensity further as it seems to interfere with my 2d renders. I've tried "0" and "2" with no success.
This is not clear at all.

-li   Low intensity mode. Specify "-li 1" if you don't want Windows to freeze.

Also both of these setting say Fastest for R9-270/x, which is it or are the equal?

"-a 1" fastest mining mode for 290/290x and 270/270x cards.
"-a 4" fastest mining for recent cards (280x, 270/270x etc).

HD7950 Tahiti (basically 280 right?)

To see your current hashrate remember to hit "m" key and then you have to select the GPU number usually "0" on single card systems.

-h 832 does work best

-a parameter rates (these are with low intensity -li 1)

no command (auto mode) == 472 - 473 h/s <<-- alot of variance so I cannot tell what mode was chosen
-a 0 == 474 h/s
-a 1 == 466 h/s
-a 2 == 455 h/s
-a 3 == 448 h/s
-a 4 == 472 h/s

Using this command line for anyone that wants to try it and might be having issues with the syntax (getting unrecognized command errors).

NsGpuCNMiner.exe -o stratum+tcp://xmr.crypto-pool.fr:6666 -a 1 -tt 80 -h 832 -li 1 -di 0 -wd 1 -u 44VYnAXVVH2bRvpC2vSYuZPpdXUpsVyc8WkSymZuPQNKSD3485C8PKPGPMbT53mRNBS7y2q9FkQCS1N 1zmt5YLWMQ8es9gH -p x

The line is so long sometimes things like wordwrap in notepad will ad a carriage return after the space character before the wallet address so make sure there is only one space between every parameter.

[Claymore]

What are the li options? Just "1"? I would like to lower the intensity further as it seems to interfere with my 2d renders. I've tried "0" and "2" with no success.
This is not clear at all.

-li   Low intensity mode. Specify "-li 1" if you don't want Windows to freeze.

Any values that are not specified in readme file are not supported. Same for all options. So either don't specify "-li" option, or use "-li 1".

Also both of these setting say Fastest for R9-270/x, which is it or are the equal?

"-a 1" fastest mining mode for 290/290x and 270/270x cards.
"-a 4" fastest mining for recent cards (280x, 270/270x etc).

This is because for some cards some modes have very similar speed.

no command (auto mode) == 472 - 473 h/s <<-- alot of variance so I cannot tell what mode was chosen

Miner always reports what mode was chosen, like this:  "GPU #0: -a 1 mode selected".

[Hueristic]

What are the li options? Just "1"? I would like to lower the intensity further as it seems to interfere with my 2d renders. I've tried "0" and "2" with no success.
This is not clear at all.

-li   Low intensity mode. Specify "-li 1" if you don't want Windows to freeze.

Any values that are not specified in readme file are not supported. Same for all options. So either don't specify "-li" option, or use "-li 1".

Also both of these setting say Fastest for R9-270/x, which is it or are the equal?

"-a 1" fastest mining mode for 290/290x and 270/270x cards.
"-a 4" fastest mining for recent cards (280x, 270/270x etc).

This is because for some cards some modes have very similar speed.

no command (auto mode) == 472 - 473 h/s <<-- alot of variance so I cannot tell what mode was chosen

Miner always reports what mode was chosen, like this:  "GPU #0: -a 1 mode selected".

OK so It's li 1 or nothing, got it. THX

[Jamsheed]

Nice specs

[bitwolf]

Will there be an update for some performance improvement or a little fee decrease after the rise of the price?

[adaseb]

I added an old 6870 GPU to one of my Pitcarin rigs. And for some reason it keeps disconnecting from the pool and getting errors such as "Low Difficulty Share".

My 6990 doesn't have any issues and my R9 270X alone don't run into any of these issues.


Any ideas?

[Claymore]

I added an old 6870 GPU to one of my Pitcarin rigs. And for some reason it keeps disconnecting from the pool and getting errors such as "Low Difficulty Share".

My 6990 doesn't have any issues and my R9 270X alone don't run into any of these issues.

Any ideas?

1. Make sure that you use Catalyst 14.6 or older.
2. Make sure that you use "-a 3" for 5xxx/6xxx cards.
3. For tests make sure that you don't overclock GPUs and PSU can handle all GPUs.

[adaseb]

I added an old 6870 GPU to one of my Pitcarin rigs. And for some reason it keeps disconnecting from the pool and getting errors such as "Low Difficulty Share".

My 6990 doesn't have any issues and my R9 270X alone don't run into any of these issues.

Any ideas?

1. Make sure that you use Catalyst 14.6 or older.
2. Make sure that you use "-a 3" for 5xxx/6xxx cards.
3. For tests make sure that you don't overclock GPUs and PSU can handle all GPUs.

Ahh thanks


a -3 seems to have fixed the issue, before it was on a -4 for that older 6870 card.

[adaseb]

Ran into another issue. Every few 20-30 mins or so I keep getting this

02:58:02:697   974   watchdog - thread 0, hb time 1060
02:58:02:697   974   watchdog - thread 1, hb time 2714
02:58:02:697   974   watchdog - thread 2, hb time 1731
02:58:02:697   974   watchdog - thread 3, hb time 686
02:58:02:697   974   watchdog - thread 4, hb time 1809
02:58:02:697   974   watchdog - thread 5, hb time 624
02:58:02:697   974   watchdog - thread 6, hb time 62
02:58:02:697   974   watchdog - thread 7, hb time 66986
02:58:02:697   974   WATCHDOG: Thread 7 hangs in OpenCL call, you need to restart miner
02:58:02:697   974   WATCHDOG: GPU memory error, you need to restart miner
02:58:02:697   974   Restarting OK, exit...


02:58:02:787   854   Job changed, drop current round

Any idea how to find out which thread 7 is?

[Claymore]

Ran into another issue. Every few 20-30 mins or so I keep getting this

Any idea how to find out which thread 7 is?

Make sure you use v9.2. If so, GPU_id = Thread_id / 2. So it's GPU #3 (i.e. 4th card).

[MrJay]

Any idea what could be causing this:

09:29:03:320   f9c   buf: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"124601006298325","job":{"blob":"0100beffc9a80519953029eb35686e6603c415a5ce146464a18fc5d4a2ba148c54fce948f82f4e0 0000000e347b57b530720a0174765f22dd11afec72266a4aca2468563cb9692cc5c52ee03","job_id":"148032830562442","target":"7b5e0400"},"status":"OK"}}

09:29:03:320   f9c   parse packet: 303
09:29:03:325   f9c   new buf size: 0
09:29:03:325   f9c   DevFee: Pool Diff 15000
09:29:04:244   f64   GPU 2, GpuMiner k1a failed -4
09:29:04:246   6ec   GPU 3, GpuMiner k1a failed -4
09:29:04:249   f64   GPU memory allocation failed. Try to set at least 16 GB of Virtual Memory: Computer Properties / Advanced System Settings / Performance / Advanced / Virtual Memory

5x 290 rig, I have virtual memory set to 16GB, no overclock, I've actually set memory down to 1250 from stock 1300.

Thanks.

Edit: using 13.12 drivers with 9.2 13.12.