Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux) - page 689.

bit815792215

member

Activity: 60

Merit: 10

Quote from: alfacro on November 07, 2016, 05:43:18 PM

Quote from: carlo_0000 on November 07, 2016, 05:40:42 PM

22:36:14:490 89c OpenCL error 3 #101 - -61

with 5x sapphire r9 380 2G

also with r9 270 2g, they crash with I 2

but single sapphire r9 380 2G on other computer runs at i2

same here

r9 270 2g with 1200/1500 -i 2 seem to be fine for me
edit: 270x sorry

felixbrucker

hero member

Activity: 700

Merit: 500

my 7970 went to 47 Sol/s and my 290x to 57 Sol/s, thats some nice improvement (-i 2 used), thanks

bardacuda

sr. member

Activity: 430

Merit: 254

I'm getting an extra 5% or so going from 2.0 to 2.1 and using -i 2 on Hawaii cards. CPU usage is only slightly higher and still only seeing partial consistent load across 3 cores on a 3.7GHz Thuban. Uses about 6GB of swapfile instead of 3GB on v2.0.

v2.0 (Rock-solid stable for over 19hrs)

v2.1

CPU Usage before and after

Quote from: Claymore on November 07, 2016, 05:06:45 PM

Quote from: HardwarePal on November 07, 2016, 04:59:12 PM

Dev fee 4 minutes now ?

Same question again and again... Added to FAQ on first page:

FAQ:

Q: It seems miner mines devfee more than 90 seconds.
A: No it does not, please read: https://bitcointalk.org/index.php?topic=1670733.msg16777816;topicseen#msg16777816

How would you know? You only wrote the program Cheesy

alfacro

member

Activity: 148

Merit: 10

DigiByte World

Quote from: carlo_0000 on November 07, 2016, 05:40:42 PM

22:36:14:490 89c OpenCL error 3 #101 - -61

with 5x sapphire r9 380 2G

also with r9 270 2g, they crash with I 2

but single sapphire r9 380 2G on other computer runs at i2

same here

h311m4n

sr. member

Activity: 487

Merit: 266

46S/s on RX470 4Gb
48-50 S/s on RX470 8Gb
56S/s on R390X

Thanks claymore

carlo_0000

legendary

Activity: 1281

Merit: 1003

22:36:14:490 89c OpenCL error 3 #101 - -61

with 5x sapphire r9 380 2G

also with r9 270 2g, they crash with I 2

but single sapphire r9 380 2G on other computer runs at i2

xeridea

sr. member

Activity: 449

Merit: 251

Quote from: Claymore on November 07, 2016, 05:33:41 PM

Quote from: markus124 on November 07, 2016, 05:26:09 PM

Quote from: Claymore on November 07, 2016, 05:06:45 PM

Quote from: HardwarePal on November 07, 2016, 04:59:12 PM

Dev fee 4 minutes now ?

Same question again and again... Added to FAQ on first page:

FAQ:

Q: It seems miner mines devfee more than 90 seconds.
A: No it does not, please read: https://bitcointalk.org/index.php?topic=1670733.msg16777816;topicseen#msg16777816

Claymore, maybe u can change the color of the "dev fee shares" from green to blue or something. So people stop asking. Hehe.

I'll think about it, may be it's a good idea. The problem is that as soon as "devfee: connect to..." string is appeared, some people think that devfee mining is started. I don't want to hide any devfee messages, but this misunderstanding is annoying. So may be new color for devfee time is a good idea.

I would leave "Devfee connect..." the same, change color of "Devfee share found", so it is obvious to those who don't read FAQ when it is actually dev mining, and when it is trying to connect.

arielbit

legendary

Activity: 3416

Merit: 1059

one of my 280x rig won't start mining with "-i 2", just 0 h/s and on and on .. "-i 0" and "-i 1" works

e46btc

full member

Activity: 157

Merit: 103

Claymore, is this ok that CPU overloaded again in v2.1 with "-i 1 or 2"? CPU exactly, not GPU.
And as result higher hashrate at 390x with "-i 0", but not with 1 or 2.

ghostfaceuk

sr. member

Activity: 410

Merit: 250

Quote from: Claymore on November 07, 2016, 05:33:41 PM

Quote from: markus124 on November 07, 2016, 05:26:09 PM

Quote from: Claymore on November 07, 2016, 05:06:45 PM

Quote from: HardwarePal on November 07, 2016, 04:59:12 PM

Dev fee 4 minutes now ?

Same question again and again... Added to FAQ on first page:

FAQ:

Q: It seems miner mines devfee more than 90 seconds.
A: No it does not, please read: https://bitcointalk.org/index.php?topic=1670733.msg16777816;topicseen#msg16777816

Claymore, maybe u can change the color of the "dev fee shares" from green to blue or something. So people stop asking. Hehe.

I'll think about it, may be it's a good idea. The problem is that as soon as "devfee: connect to..." string is appeared, some people think that devfee mining is started. I don't want to hide any devfee messages, but this misunderstanding is annoying. So may be new color for devfee time is a good idea.

How about yellow to make it really stand out from the rest of the text?

dudee

member

Activity: 99

Merit: 10

2x rx470 1080/1880 moded bios, 42/41 h/s 16.10 driver, -i 2
CPU load 70%

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: markus124 on November 07, 2016, 05:26:09 PM

Quote from: Claymore on November 07, 2016, 05:06:45 PM

Quote from: HardwarePal on November 07, 2016, 04:59:12 PM

Dev fee 4 minutes now ?

Same question again and again... Added to FAQ on first page:

FAQ:

Q: It seems miner mines devfee more than 90 seconds.
A: No it does not, please read: https://bitcointalk.org/index.php?topic=1670733.msg16777816;topicseen#msg16777816

Claymore, maybe u can change the color of the "dev fee shares" from green to blue or something. So people stop asking. Hehe.

I'll think about it, may be it's a good idea. The problem is that as soon as "devfee: connect to..." string is appeared, some people think that devfee mining is started. I don't want to hide any devfee messages, but this misunderstanding is annoying. So may be new color for devfee time is a good idea.

markus124

hero member

Activity: 574

Merit: 500

Quote from: Claymore on November 07, 2016, 05:06:45 PM

Quote from: HardwarePal on November 07, 2016, 04:59:12 PM

Dev fee 4 minutes now ?

Same question again and again... Added to FAQ on first page:

FAQ:

Q: It seems miner mines devfee more than 90 seconds.
A: No it does not, please read: https://bitcointalk.org/index.php?topic=1670733.msg16777816;topicseen#msg16777816

Claymore, maybe u can change the color of the "dev fee shares" from green to blue or something. So people stop asking. Hehe.

Za1n

legendary

Activity: 1078

Merit: 1011

Quote from: xeridea on November 07, 2016, 05:14:01 PM

Quote from: Za1n on November 07, 2016, 05:08:09 PM

Added another 5% or so on all my rigs with older cards using the -i 2 switch.

On my Rigs with newer cards, such as the RX series, I actually seen a slight decrease versus version 2.0. I have tried all three intensity levels and even the -i 2 gives a bit less sols and the CPU usage is greater than in version 2.0. I am still playing around as it might have been my lowered clocks, but it seems this version was geared more toward the older cards.

I get about 2-3H/s boost on all my 470s and 480s, 4GB and 8GB versions, most sapphire some others. Just have dual cores, mostly celerons, one APU. You can try setting ZecMiner priority to above normal in task manager, it may help slightly. Also check if other processes are using much CPU. Surely there is more room for improvement on Polaris, but I got boost from 1.1 -> 2.0 -> 2.1

Thanks for the suggestion. I might play around a bit more, but according to Claymore's last post this version was mainly for the older cards anyway. I don't run anything but the miner and VNC on the rigs once I get them dialed in, so I doubt setting the task priority higher will help much, but I will test it out anyway.

simhash

newbie

Activity: 9

Merit: 0

10% improvement on 290. Great work as always Claymore. Let's push it to 100 Sol/s shall we Grin

ReFLex001

newbie

Activity: 5

Merit: 0

Sapphire Radeon RX 470 OC 4.0 GB + mod bios, -i 0

http://image.prntscr.com/image/e07162a034b84faaad3ec4944f9987e1.png

Za1n

legendary

Activity: 1078

Merit: 1011

Quote from: Claymore on November 07, 2016, 05:09:26 PM

Quote from: Za1n on November 07, 2016, 05:08:09 PM

Added another 5% or so on all my rigs with older cards using the -i 2 switch.

On my Rigs with newer cards, such as the RX series, I actually seen a slight decrease versus version 2.0. I have tried all three intensity levels and even the -i 2 gives a bit less sols and the CPU usage is greater than in version 2.0. I am still playing around as it might have been my lowered clocks, but it seems this version was geared more toward the older cards.

Yes I did not have time to improve performance on Polaris yet.

Thanks for the clarification! Great job though on increasing the performance on the older cards. Now I know to focus on tweaking them and not worry about my RX rigs for now, I'll keep them on V2.0.

flyingdutchmen

full member

Activity: 210

Merit: 100

Digital Crypto Wealth Management Platform

Will there be a miner for mining two coins at the same time, like ZEC and ETH?

xeridea

sr. member

Activity: 449

Merit: 251

Quote from: Za1n on November 07, 2016, 05:08:09 PM

Added another 5% or so on all my rigs with older cards using the -i 2 switch.

On my Rigs with newer cards, such as the RX series, I actually seen a slight decrease versus version 2.0. I have tried all three intensity levels and even the -i 2 gives a bit less sols and the CPU usage is greater than in version 2.0. I am still playing around as it might have been my lowered clocks, but it seems this version was geared more toward the older cards.

I get about 2-3H/s boost each version on all my 470s and 480s, 4GB and 8GB versions, most sapphire some others. Just have dual cores, mostly celerons, one APU. You can try setting ZecMiner priority to above normal in task manager, it may help slightly. Also check if other processes are using much CPU. Surely there is more room for improvement on Polaris, but I got boost from 1.1 -> 2.0 -> 2.1

TR8888

hero member

Activity: 525

Merit: 500

@ claymore

Random error.. Any idea's? (2.1 w8 x64, 280x x4 rig, all stock)

Code:

31:699	cbc	got 291 bytes
21:08:31:699	cbc	buf: {"id":null,"method":"mining.notify","params":["5","04000000","c3d27dbc4f25977cea7d7ab625d97dc6adf409cce299e8caf1a3ded421000000","700ccd8188f596fead7818159d5a75fc0c7531eaaed730e8bdea7be76b112588","0000000000000000000000000000000000000000000000000000000000000000","46ed2058","64972d1d",true]}

21:08:31:709	cbc	parse packet: 290
21:08:31:714	cbc	new buf size: 0
21:08:31:724	cbc	ZEC: 11/07/16-21:08:31 - New job from zcl.coinmine.pl:7007
21:08:31:729	cbc	target: 0x0016b2db (diff: 2887H)
21:08:31:734	cbc	ZEC - Total Speed: 194.782 H/s, Total Shares: 111, Rejected: 0, Time: 00:02
21:08:31:734	cbc	ZEC: GPU0 48.580 H/s, GPU1 46.684 H/s, GPU2 49.641 H/s, GPU3 49.792 H/s
21:08:36:345	ec	GPU0 t=58C fan=57%, GPU1 t=57C fan=57%, GPU2 t=64C fan=64%, GPU3 t=59C fan=59%
21:08:36:350	ec	em hbt: 0, fm hbt: 31, 
21:08:36:350	ec	watchdog - thread 0, hb time 156
21:08:36:355	ec	watchdog - thread 1, hb time 78
21:08:36:360	ec	watchdog - thread 2, hb time 0
21:08:36:365	ec	watchdog - thread 3, hb time 78
21:08:36:365	ec	watchdog - thread 4, hb time 62
21:08:36:370	ec	watchdog - thread 5, hb time -16
21:08:36:370	ec	watchdog - thread 6, hb time 15
21:08:36:375	ec	watchdog - thread 7, hb time 94
21:08:43:862	fd8	GPU returned incorrect data! 424b112
21:08:53:424	fd8	GPU returned incorrect data! fc9b503
21:09:05:307	af4	GPU returned incorrect data! e0b4f1d6
21:09:06:887	ec	GPU0 t=58C fan=58%, GPU1 t=57C fan=57%, GPU2 t=64C fan=64%, GPU3 t=59C fan=59%
21:09:06:892	ec	em hbt: 0, fm hbt: 16, 
21:09:06:897	ec	watchdog - thread 0, hb time 16
21:09:06:907	ec	watchdog - thread 1, hb time 109
21:09:06:917	ec	watchdog - thread 2, hb time 47
21:09:06:927	ec	watchdog - thread 3, hb time -31
21:09:06:932	ec	watchdog - thread 4, hb time 78
21:09:06:937	ec	watchdog - thread 5, hb time 0
21:09:06:937	ec	watchdog - thread 6, hb time 125
21:09:06:942	ec	watchdog - thread 7, hb time 31
21:09:29:642	9a8	ZEC: put share nonce 16ef
21:09:29:647	9a8	ZEC round found 1 shares
21:09:29:657	cbc	ZEC: 11/07/16-21:09:29 - SHARE FOUND - (GPU 3)
21:09:29:657	cbc	send share: {"id": 4, "method": "mining.submit", "params": ["cheese1191.PC6","5","46ed2058","ef160000000000000000000000000000000000000000000000000000","fd4005006b4a22c10732c9ef44b134bbed1eb9269857a2782df9c2156ced
21:09:29:687	cbc	got 36 bytes
21:09:29:692	cbc	buf: {"id":4,"result":true,"error":null}

21:09:29:702	cbc	parse packet: 35
21:09:29:707	cbc	ZEC: Share accepted (47 ms)!

21:09:29:707	cbc	new buf size: 0
21:09:36:459	fd8	GPU returned incorrect data! 11c884d6
21:09:37:419	ec	GPU0 t=58C fan=58%, GPU1 t=57C fan=57%, GPU2 t=65C fan=65%, GPU3 t=59C fan=59%
21:09:37:424	ec	em hbt: 0, fm hbt: 62, 
21:09:37:429	ec	watchdog - thread 0, hb time 140
21:09:37:434	ec	watchdog - thread 1, hb time 31
21:09:37:439	ec	watchdog - thread 2, hb time 62
21:09:37:439	ec	watchdog - thread 3, hb time 140
21:09:37:444	ec	watchdog - thread 4, hb time 31
21:09:37:449	ec	watchdog - thread 5, hb time 109
21:09:37:449	ec	watchdog - thread 6, hb time 109
21:09:37:454	ec	watchdog - thread 7, hb time 31
21:09:37:719	fd8	GPU returned incorrect data! edc8702
21:09:39:805	fd8	GPU returned incorrect data! b3228d3
21:09:42:240	af4	GPU returned incorrect data! f14d425
21:09:43:716	fd8	GPU returned incorrect data! c78f4ed3

Topic: Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux) - page 689. (Read 3839163 times)