Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 907.

bakano

newbie

Activity: 1

Merit: 0

Quote from: bilbo333 on May 02, 2017, 12:29:01 PM

Thank you for your reply. I see dwarfpool and nanopool no longer have DCR pools. Where is the best place to mine DCR?

Does running more than one instance of Claymore increase total watts used?

Check out http://yiimp.ccminer.org/

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: Teress on May 02, 2017, 12:15:53 PM

Quote from: EdjOne on May 02, 2017, 10:52:58 AM

Quote from: Teress on May 02, 2017, 10:19:07 AM

Quote from: EdjOne on May 02, 2017, 03:43:40 AM

Hi Claymore and Community.

I'm switched from 8.0 to 9.3 and noticed that time of share accepted increased 2-3 times. And totally effected pool average hashrate.
See below, (dual-mining or single mode result the same):

Version 8.0
ETH: Share accepted (62 ms)!

Version 9.3
ETH: Share accepted (156 ms)!
ETH: Share accepted (172 ms)!

So, seems this affect hashrate and I lost around 10% in 24 hours period.

Any suggestion are welcome, thanks in advance.

Yes, I have also on v9.3 increased share submit time, from 31 to 70 ms on v9.0 to 150 ms and more on v9.3. Thats a huge step back, because it causes less accepted shares and huge drop on accepted hashrate on pool.
So I'm back on v9.0

(RX470 4GBs, RX480 4 and 8GBs, nanopool)

Also lots of ETH: Job timeout, disconnect, retry in 20 sec....

Back to 9.0 is not a solution..... Need proper improvement or advice.

Lets hope Claymore read it and will find a solution.

I cannot confirm it, I see the same time. What CPU do you have and what CPU load do you see in Task Manager in "good" and "bad" versions?

bilbo333

newbie

Activity: 18

Merit: 0

Quote from: Xardas2014 on May 01, 2017, 06:18:24 PM

Quote from: bilbo333 on May 01, 2017, 04:35:58 PM

Hello. I have a couple questions to throw to the brain trust:

I am wondering if anyone out there is still mining SIA along with Ethereum? Does it makes sense as a second coin?

Also, I am running 2 RX 480's and I have a sapphire r9 270x. Any drawbacks to running an older, slower card with two new cards?

I am seeing the following hashrates 27.2 27.2 11.1

Thank you

You will make more using the 270x to mine something like ZCL or ZEC, Use the -di in your commandline .bat. Set the 480's to mine ETH and DCR. Set the 270x to mine ZCL. You will have two instances of Claymore open.

Thank you for your reply. I see dwarfpool and nanopool no longer have DCR pools. Where is the best place to mine DCR?

Does running more than one instance of Claymore increase total watts used?

Teress

full member

Activity: 224

Merit: 102

Quote from: EdjOne on May 02, 2017, 10:52:58 AM

Quote from: Teress on May 02, 2017, 10:19:07 AM

Quote from: EdjOne on May 02, 2017, 03:43:40 AM

Hi Claymore and Community.

I'm switched from 8.0 to 9.3 and noticed that time of share accepted increased 2-3 times. And totally effected pool average hashrate.
See below, (dual-mining or single mode result the same):

Version 8.0
ETH: Share accepted (62 ms)!

Version 9.3
ETH: Share accepted (156 ms)!
ETH: Share accepted (172 ms)!

So, seems this affect hashrate and I lost around 10% in 24 hours period.

Any suggestion are welcome, thanks in advance.

Yes, I have also on v9.3 increased share submit time, from 31 to 70 ms on v9.0 to 150 ms and more on v9.3. Thats a huge step back, because it causes less accepted shares and huge drop on accepted hashrate on pool.
So I'm back on v9.0

(RX470 4GBs, RX480 4 and 8GBs, nanopool)

Also lots of ETH: Job timeout, disconnect, retry in 20 sec....

Back to 9.0 is not a solution..... Need proper improvement or advice.

Lets hope Claymore read it and will find a solution.

EdjOne

newbie

Activity: 5

Merit: 0

Quote from: Teress on May 02, 2017, 10:19:07 AM

Quote from: EdjOne on May 02, 2017, 03:43:40 AM

Hi Claymore and Community.

I'm switched from 8.0 to 9.3 and noticed that time of share accepted increased 2-3 times. And totally effected pool average hashrate.
See below, (dual-mining or single mode result the same):

Version 8.0
ETH: Share accepted (62 ms)!

Version 9.3
ETH: Share accepted (156 ms)!
ETH: Share accepted (172 ms)!

So, seems this affect hashrate and I lost around 10% in 24 hours period.

Any suggestion are welcome, thanks in advance.

Yes, I have also on v9.3 increased share submit time, from 31 to 70 ms on v9.0 to 150 ms and more on v9.3. Thats a huge step back, because it causes less accepted shares and huge drop on accepted hashrate on pool.
So I'm back on v9.0

(RX470 4GBs, RX480 4 and 8GBs, nanopool)

Also lots of ETH: Job timeout, disconnect, retry in 20 sec....

Back to 9.0 is not a solution..... Need proper improvement or advice.

FaithlessCoinMob

newbie

Activity: 5

Merit: 0

I can't believe people are having trouble with msi cards and hynix memory! First of all, with the 4gb hynix cards use the 1500memstraps! Second, lower the gpu speed (1095-1191mhz range). Finally, start with a voltage offset of at least -14 in watttool. You should be able to set the mem to 1900mhz, but you may have to lower the p7 mem/gpu voltages even further. I'm getting 27/730 eth/dcr hashrate with 9.3 -dcri27 on a 4gb 470 msi gaming x. My msi ref 480's 4gb with hynix mem have the memclock at 2000 with everything else the same and the hashrate is ~28.6/800 eth/dcr. According to kill-a-watt all of the 480's use <100w for dual mining, and all the 470's <90w. I've got dozens of polaris cards and for me msi is the best for mining!

Teress

full member

Activity: 224

Merit: 102

Quote from: EdjOne on May 02, 2017, 03:43:40 AM

Hi Claymore and Community.

I'm switched from 8.0 to 9.3 and noticed that time of share accepted increased 2-3 times. And totally effected pool average hashrate.
See below, (dual-mining or single mode result the same):

Version 8.0
ETH: Share accepted (62 ms)!

Version 9.3
ETH: Share accepted (156 ms)!
ETH: Share accepted (172 ms)!

So, seems this affect hashrate and I lost around 10% in 24 hours period.

Any suggestion are welcome, thanks in advance.

Yes, I have also on v9.3 increased share submit time, from 31 to 70 ms on v9.0 to 150 ms and more on v9.3. Thats a huge step back, because it causes less accepted shares and huge drop on accepted hashrate on pool.
So I'm back on v9.0

(RX470 4GBs, RX480 4 and 8GBs, nanopool)

Also lots of ETH: Job timeout, disconnect, retry in 20 sec....

666mrga999

newbie

Activity: 106

Merit: 0

I get 4-5% more effective speed (24h average) on pool side with 9.3 patch (ethermine).
From 89 MHps tp 94 MHps effective average speed.

Is this intended Claymore? Please confirm

tnx

ffthomas

full member

Activity: 160

Merit: 100

Quote from: Claymore on April 29, 2017, 03:36:52 PM

Quote from: DevonMiner on April 29, 2017, 03:23:24 PM

Quote from: Claymore on April 29, 2017, 03:04:18 PM

v9.3:
- improved dual mining speed stability in ASM mode.
- added "-altnum" option for alternative GPU indexing.
- a few minor bug fixes and improvements.

Oh bugger ... just spent the last hour updating all my rigs to 9.2 ... LOL Cheesy

Thanks Claymore, not complaining!

Soon I will add ability to update miners on all rigs with EthMan so it will be easy.

@claymore: WOW!! That will be a very useful feature, thanks!

AzzAz

legendary

Activity: 1030

Merit: 1006

Quote from: bayloth on May 02, 2017, 06:59:15 AM

Quote from: adly3000 on May 02, 2017, 06:40:13 AM

Quote from: bayloth on May 02, 2017, 06:31:53 AM

Hi there
I got problem
   ETH: Job timeout, disconnect, retry in 20 sec....
My worker:
   - 6x MSI rx 480 4g gaming x
   - windows 10 64bit
   - Claymore v 9.3
   - crimson v 15.12
   - firewall off
   - my .bat setting:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
ethdcrminer64 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX.rig1 -mport 0 -mode 1 -eworker t1 -esm 1

Please help me. thanks!

Remove "-eworker t1" and try again it should be:
ethdcrminer64 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX/rig1 -mport 0 -mode 1 -esm 1
otherwise try different pool. as dwarf sometimes fail to connect

Removed -ewoker t1 + change pool to asia1.ethermine.org:4444 but still got this problem Sad

(((

15.12 and 480s! You want to be 1st to make it happen? Use any between 16.9.1 to 16.11.5

Yutard

newbie

Activity: 56

Merit: 0

Quote from: fisheth on May 01, 2017, 08:57:50 AM

hi guys,my gpu rx480 4gb,anyone can help mod it?speed just 24.xx mh/s
really appreciate it

You can search the forum. It is quite easy.

bayloth

newbie

Activity: 5

Merit: 0

Quote from: adly3000 on May 02, 2017, 06:40:13 AM

Quote from: bayloth on May 02, 2017, 06:31:53 AM

Hi there
I got problem
   ETH: Job timeout, disconnect, retry in 20 sec....
My worker:
   - 6x MSI rx 480 4g gaming x
   - windows 10 64bit
   - Claymore v 9.3
   - crimson v 15.12
   - firewall off
   - my .bat setting:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
ethdcrminer64 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX.rig1 -mport 0 -mode 1 -eworker t1 -esm 1

Please help me. thanks!

Remove "-eworker t1" and try again it should be:
ethdcrminer64 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX/rig1 -mport 0 -mode 1 -esm 1
otherwise try different pool. as dwarf sometimes fail to connect

Removed -ewoker t1 + change pool to asia1.ethermine.org:4444 but still got this problem Sad

(((http://imageshack.com/a/img923/3708/dfSgZu.jpg

adly3000

newbie

Activity: 55

Merit: 0

Quote from: bayloth on May 02, 2017, 06:31:53 AM

Hi there
I got problem
   ETH: Job timeout, disconnect, retry in 20 sec....
My worker:
   - 6x MSI rx 480 4g gaming x
   - windows 10 64bit
   - Claymore v 9.3
   - crimson v 15.12
   - firewall off
   - my .bat setting:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
ethdcrminer64 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX.rig1 -mport 0 -mode 1 -eworker t1 -esm 1

Please help me. thanks!

Remove "-eworker t1" and try again it should be:
ethdcrminer64 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX/rig1 -mport 0 -mode 1 -esm 1
otherwise try different pool. as dwarf sometimes fail to connect

bayloth

newbie

Activity: 5

Merit: 0

Hi there
I got problem
   ETH: Job timeout, disconnect, retry in 20 sec....
My worker:
   - 6x MSI rx 480 4g gaming x
- windows 10 64bit
   - Claymore v 9.3
   - crimson v 15.12
   - firewall off
   - my .bat setting:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
ethdcrminer64 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX.rig1 -mport 0 -mode 1 -eworker t1 -esm 1

Please help me. thanks!

r79

newbie

Activity: 2

Merit: 0

Quote

did you put

Quote

#!/bin/sh

as first line?

yes

Quote

Are you running as root... shutdown often need to be root (via sudo, but as server you cannot ask a password...).

I start claymore with an @reboot cron in a screen, so technically it should be running as root (the screen is in the "root"-screenlist).

Quote

To trace maybe you can add "-x'" to trace the script.

Quote

#!/bin/sh -x

add echo command before and after, in case problem is with shutdown itself...

Good idea, did not get to that when I fiddled around with it yesterday evening, gonna check that at home.

Quote

I run something like

/sbin/shutdown -r 1
(restart in 1 minute)

You put this command in a "restart.sh" file inside the claymore folder or into bin? I was lazy and just put a "restart" into my script, I'll check your way aswell (sounds wise giving the cards some time to cool before rebooting).

Quote

It works well, and I even send email including a journalctl extract with ssmtp during the last minute.

Holy damn, that sounds epic Cheesy

AlainC

member

Activity: 91

Merit: 10

Quote from: r79 on May 02, 2017, 05:41:24 AM

Been fiddling around with the -r 1 param, but I could not make it work.
...

did you put

Quote

#!/bin/sh

as first line?
Are you running as root... shutdown often need to be root (via sudo, but as server you cannot ask a password...).

To trace maybe you can add "-x'" to trace the script.

Quote

#!/bin/sh -x

add echo command before and after, in case problem is with shutdown itself...

I run something like

/sbin/shutdown -r 1
(restart in 1 minute)

check the path of shutdown with

Quote

whereis shutdown

It works well, and I even send email including a journalctl extract with ssmtp during the last minute.

woodaxe

member

Activity: 129

Merit: 10

Running 6x 470 nitro + oc 8gig one card hashes at 19m/hs the others at 29 m/hash i assume the one running at 19 M/hash is the card ive got the monitor plugged into do i need a dummy plug and to use teamviewer to get the card up to 29 m/hash the same as the others and if so any links to suitable dummy plugs for sale

some help would be good thanks in advance

infowire

newbie

Activity: 96

Merit: 0

Quote from: Claymore on April 11, 2016, 11:30:36 AM

NVIDIA DRIVERS:

9xx cards in Windows 10 x64: you have to use old drivers (for example, 352.xx) and miner built for cuda6.5.

GTX 970

The driver 352.84 did not work, still MH's 3.x. I use 347.52 and it works except i can't run:
C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi" -acp UNRESTRICTED"
C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi" -ac 3505,1455
It works on 352.84... but MH's is 3....

Edit: 350.12 Works! http://www.nvidia.com/download/driverResults.aspx/83819/en-us

r79

newbie

Activity: 2

Merit: 0

Been fiddling around with the -r 1 param, but I could not make it work.

Working on Ubuntu 16.04:
- I created "reboot.sh" in the claymore-dir, put in the reboot command, chmod 755, tested it manually, worked flawlessly.
- waited for the miner to crash, apparently the miner did try to reboot using the script, but it seems like the script never got called.

Is there any way to debug this? Any way to test it? What does Claymore call exactly? Is it beeing called as the superuser, as I'm starting ethdcrminer as root?

Any help is highly appreciated

pwpwpw

hero member

Activity: 908

Merit: 503

Quote from: notbatman on May 01, 2017, 11:07:50 PM

Quote from: meeekz on May 01, 2017, 10:46:51 PM

Quote from: notbatman on May 01, 2017, 09:03:32 PM

Quote from: meeekz on May 01, 2017, 08:56:14 PM

What can I expect from the
MSI Radeon RX 570 GAMING X
getting 22 from my RX470 Gaming X

You can expect a month long wait while you RMA their defective crap. I'm betting eventually they just hand me back the garbage cards and tell me to eat it.

What cards are you recommending - sub $200 with 22+ hashrate

Buyer beware with MSI, my Gigabyte RX card is working perfectly.

I heard r9 390 MSI cards OC the best and have the highest hashrate/stability, the RX series MSI suck ? About gigabyte, I bought 3years ago 3x r9 280x gigabyte and 5x asus dc2t, all of the gigabyte still run, after almost 24/7 3 years and 4 of the asus died within a year, all had fan failures withing 6months but 1 simply can't display anything, crashes during driver load. So in my opinion, gigabyte is pretty good, it's usually the cheapest card and maybe I've been lucky but they are quite durable, right now they are on zec mining with 380hour+ uptime. All I know, avoid asus, it's pretty easy now that they are priced the highest tho Cheesy

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 907. (Read 6590565 times)