Claymore's CryptoNote AMD GPU Miner v11.3 - page 215.

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: gaalx on March 29, 2015, 02:13:58 PM

Are mined now Monero on Claymore GPU Miner 9.2 beta. So it is not clear how to set the frequency. One rig working 947-1250, and the second 1100-1250 (based on CPU info). Accordingly, various profits. Which team is responsible for setting the frequency? -gpu-engine 1000 -gpu-memclock 1500 - the program gives that does not know the command.

Miner does not support overclocking. You can use MSI AfterBurner for that. Or "GPUs Control Utility v1.1" that you can download by link in OP of this topic: https://bitcointalksearch.org/topic/claymores-xpm-primecoin-gpu-miner-v132-693680

gaalx

sr. member

Activity: 411

Merit: 250

Are mined now Monero on Claymore GPU Miner 9.2 beta. So it is not clear how to set the frequency. One rig working 947-1250, and the second 1100-1250 (based on CPU info). Accordingly, various profits. Which team is responsible for setting the frequency? -gpu-engine 1000 -gpu-memclock 1500 - the program gives that does not know the command.

MrJay

member

Activity: 115

Merit: 10

Quote from: Claymore on March 25, 2015, 07:03:15 AM

Try to increase size of physical RAM, for 4 290 cards at least 4GB is necessary, 5 cards may require even more. You can also try to increase size of virtual memory.

I came home to the rig only showing 4 cards and the 5th's fan spinning at 100%. moved the 5th card in to a different pci slot, increased virtual mem to 18GB:

5x Sapphire R9 290 Tri X @ 1000/1250

Speed: 3731 h/s, TotalHashes: 503585K, DevHashes: 12588K Mining time: 38:14

10:07:25:440   99c   GPU 0: HashCnt = 1280, time = 1698 ms, hashrate = 753 h/s
10:07:25:480   99c   Round
10:07:25:880   594   GPU 4: HashCnt = 1280, time = 1702 ms, hashrate = 752 h/s
10:07:25:905   594   Round
10:07:26:035   eb0   GPU 1: HashCnt = 1280, time = 1697 ms, hashrate = 754 h/s
10:07:26:070   eb0   Round
10:07:26:100   890   GPU 3: HashCnt = 1280, time = 1696 ms, hashrate = 754 h/s
10:07:26:115   890   Round
10:07:26:705   77c   GPU 2: HashCnt = 1280, time = 1746 ms, hashrate = 733 h/s
10:07:26:740   77c   Round

Looking good.

Tiger78

member

Activity: 83

Merit: 10

For 7790(260x) managed to obtain the best values in the config: -h 256-a 4.
Here's what happened:

Quote

09:42:03:659   bc8   GPU 4: HashCnt = 256, time = 1102 ms, hashrate = 232 h/s
09:42:03:674   580   GPU 3: HashCnt = 256, time = 1101 ms, hashrate = 232 h/s
09:42:03:694   bc8   Round
09:42:03:704   7ec   GPU 2: HashCnt = 256, time = 1121 ms, hashrate = 228 h/s
09:42:03:709   580   Round
09:42:03:719   d10   GPU 1: HashCnt = 256, time = 1122 ms, hashrate = 228 h/s
09:42:03:744   d10   Round
09:42:03:754   730   GPU 0: HashCnt = 256, time = 1117 ms, hashrate = 229 h/s
09:42:03:764   730   Round
09:42:04:769   bcc   GPU 4: HashCnt = 256, time = 1075 ms, hashrate = 238 h/s
09:42:04:779   bcc   Round
09:42:04:804   d54   GPU 3: HashCnt = 256, time = 1079 ms, hashrate = 237 h/s
09:42:04:809   d54   Round
09:42:04:814   c90   GPU 2: HashCnt = 256, time = 1074 ms, hashrate = 238 h/s
09:42:04:824   c90   Round
09:42:04:839   398   GPU 1: HashCnt = 256, time = 1077 ms, hashrate = 237 h/s
09:42:04:849   398   Round
09:42:04:854   aa4   GPU 0: HashCnt = 256, time = 1074 ms, hashrate = 238 h/s
09:42:04:864   aa4   Round
09:42:05:869   bc8   GPU 4: HashCnt = 256, time = 1072 ms, hashrate = 238 h/s
09:42:05:894   bc8   Round
09:42:05:909   580   GPU 3: HashCnt = 256, time = 1079 ms, hashrate = 237 h/s
09:42:05:919   7ec   GPU 2: HashCnt = 256, time = 1075 ms, hashrate = 238 h/s

MrJay

member

Activity: 115

Merit: 10

Thanks for the reply, I've got 8GB in the system, will try increasing the virtual memory.

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: MrJay on March 25, 2015, 04:44:47 AM

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.

Try to increase size of physical RAM, for 4 290 cards at least 4GB is necessary, 5 cards may require even more. You can also try to increase size of virtual memory.

MrJay

member

Activity: 115

Merit: 10

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.

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: adaseb on March 23, 2015, 04:18:18 AM

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).

adaseb

legendary

Activity: 3808

Merit: 1723

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

Quote

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 Sad

02:58:02:697 974 WATCHDOG: GPU memory error, you need to restart miner Sad

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?

adaseb

legendary

Activity: 3808

Merit: 1723

Quote from: Claymore on March 22, 2015, 04:22:12 AM

Quote from: adaseb on March 22, 2015, 12:15:18 AM

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.

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: adaseb on March 22, 2015, 12:15:18 AM

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

legendary

Activity: 3808

Merit: 1723

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?

bitwolf

full member

Activity: 186

Merit: 100

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

Jamsheed

newbie

Activity: 31

Merit: 0

Nice specs Wink

Hueristic

legendary

Activity: 3836

Merit: 4969

Doomed to see the future and unable to prevent it

Quote from: Claymore on March 16, 2015, 01:31:16 PM

Quote from: Hueristic on March 16, 2015, 11:31:03 AM

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.

Quote

-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".

Quote from: Hueristic on March 16, 2015, 11:31:03 AM

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

Quote

"-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.

Quote from: Hueristic on March 16, 2015, 11:31:03 AM

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

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: Hueristic on March 16, 2015, 11:31:03 AM

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.

Quote

-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".

Quote from: Hueristic on March 16, 2015, 11:31:03 AM

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

Quote

"-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.

Quote from: Hueristic on March 16, 2015, 11:31:03 AM

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

legendary

Activity: 3836

Merit: 4969

Doomed to see the future and unable to prevent it

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.

Quote

-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?

Quote

"-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.

MarkMJ

hero member

Activity: 714

Merit: 500