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

[Yohow]

Is it the 17.7.2 that will solve the DAG problem?

I think only prevents that hashrate lows for incoming DAG epoch 137. New Claymore 9.8 version improves the hashrate? Thanks

17.7.2, Dosen't solve the DAG issue, Its the upcoming driver that is suppost to do that. On the other hand with Claymore's 9.8 miner he fixed the compability issue which was an issue when running claymore 9.7 together with 17.7.2. Now you can see the tempretures and fan speed.

And the claymore 9.8 dosen't boost the hashrate atleast not for me, running  RX 480.


Best regards
Harry

Perfect, so we'll wait for new drivers then. Regards!

[nadrojcote]

He's probably loling about the fact that he didnt spend 50% more for a 1070 over an 8gb rx 480/580 that will get almost the same hashrate when the dag fix comes out.

[JustCauseBIH]

Thats correct. New update will equal AMD and Nvidia in term of hashing power, as was before. Now nvidia have some advantage, but soon it will be nulled.

[uDwcHYO]

There is detailed information about the "a few minor bug fixes and improvements"? need to change version from 9.7 ?

[FFI2013]

Does the newest drivers still need the signature bypass patch

[YIz]

What's the hashrate for a Vega 64?

[doktor83]

AMD doesn't care about the mining community, but it will be a nice surprise if they do fix the DAG thing with a new driver.

[ffthomas]

@Claymore: Thank you for your work. Can you please share with me/us your instructions about updating our rigs?

I have several RX470 and RX480 rigs, all cards are working with modded bios (only memory timing changed).

First, I updated the AMD driver to 17.7.2 (withoud DDU, I just installed the new version), then restarted the rig. Second, I ran atikmdag-patcher-1.4.5, and reboot again. I logged in, started CDM 9.8. The miner works, but I can't use WattTool to set clock and voltage parameters. What should I repair, or did I miss something during the upgrading process?

AB and WattTool don't work with 17.7.2. So don't hurry to update your rigs. Also may be it's a good idea to wait new drivers from AMD that solve DAG issue if you don't want to update rigs twice.

Ahh.. OK, thanks. I misunderstood.. I thought that the DAG issue is solved already in 17.7.2. So we are waiting for the new driver, thank you for your quick answer.

[z0n0]

About this DAG fix - if I get lets say 29mh with my rx 480 now, how much more could I get if AMD fixes the DAG issue?

[BD91]

@Claymore

This might be hardware related but I'm having an issue.

I'm running two 4gb rx 480's, one is getting 22MH/s as it always has, the other however is only getting 4MH/s. very poor rate! Any idea what might be causing the problem/how to fix it?

[adaseb]

@Claymore

This might be hardware related but I'm having an issue.

I'm running two 4gb rx 480's, one is getting 22MH/s as it always has, the other however is only getting 4MH/s. very poor rate! Any idea what might be causing the problem/how to fix it?

Plug monitor in and flash your bios.

[P00P135]

About this DAG fix - if I get lets say 29mh with my rx 480 now, how much more could I get if AMD fixes the DAG issue?

Probably gain at the most 1.5Mh/s.  Go benchmark old EPOC DAGs and test it yourself.

[Skol600ml]

About this DAG fix - if I get lets say 29mh with my rx 480 now, how much more could I get if AMD fixes the DAG issue?

Same hashrate that you get with Ubiq, Musicoin and Expanse now.

[Skol600ml]

What's the hashrate for a Vega 64?

It's hard to calculate the hashrate of a VGA that isn't for sale yet. Something between 0 and 40.

[fr4nkthetank]

@Claymore

This might be hardware related but I'm having an issue.

I'm running two 4gb rx 480's, one is getting 22MH/s as it always has, the other however is only getting 4MH/s. very poor rate! Any idea what might be causing the problem/how to fix it?

Plug monitor in and flash your bios.

I think i've seen that question over 100 times in multiple threads.  Its driving me crazy.  On another note, please ignore this next message : 1QBZxAAva9msx8w7QSDkr39nbkA1QARGC7

[swalayan]

thx claymore, my rx470 4gb run stable @25mhs @75watt 

[TechPark]

Upcoming version supports Vega and fan management for latest drivers, so the only thing you need is to wait a couple of days for new drivers from AMD.

@claymore Thanks a lot . and i am happy that i didn't buy any GTX cards ) i knew that AMD will NEVER give this chance to NVIDIA . LOL

I still get the same 33 MH/s on my GTX 1070s. Mining difficulty increased for everyone whether you're AMD or NVidia. So what exactly are you LOL'ing about?

Great news! Can't wait to see 30mh/s again.

I cannot understand what exactly makes you happy!?
You will get 5% increase in hash-rate but the difficulty will go up 10-15%, so you will lose 10% on profitability!
Take a note of your earnings now and then and update us later on your feeling

Been saying this for a while, it makes no difference to AMD miners. Our profitability will remain the same. The worst hit for this upgrade will be nvidia cards, but most of them are not mining eth anyway so again all this makes zero difference in the end.

Can you enlighten me why this upgrade hits Nvidia cards the worst? I might be missing something here. Thanks.

I think I have figured out what he meant.

AMD cards are affected but Epoch changes. With every new epoch the hashrate of AMD card drops. Red rigs losing profitability on every 3rd day. NVidia cards are not affected.

With a fix of the driver AMD rigs will improve hashrate. It will consequently cause difficulty spike. Nvidia will lose profitability.

AMD will gain profitability as the improved hashrate and profitability will overcompensate the loss due to the difficulty.

If I am right I am very impressed by that guy putting such a complex explanation into 6 words
He is also wrong that  NVidia rigs not mining ETH. They do.

[Temporel]

Dual mining with latest version with 1080Ti/1080/1070 and I cant see a difference so far.

Great job anyway Claymore  !

[friedCELLS]

I'm having a strange issue. I've read the last several pages as well as searched via Google for several hours. No dice. Here's the issue:
I have 2 different GTX 970 rigs with 5 cards each. Testing them on ETH only mode. Before overclocking or anything, they all get about 18 Mh/s each. Here's the odd thing: 1 out of the 5 cards will be at around 11 MH/s.... i.e. GPU1. All speeds look equal in Afterburner. I'll restart the computer, and GPU1 will now be at 18 MH/s. But GPU2 will be down to 11. I'll restart the computer again. GPU0 will now be down to 11, all others at 18. So, it's not an issue with a card, because the dropped one changes on each restart. I have the same problem on both rigs. 1 card of 5 is always at 11-12 while the other 4 are at 18. One is an MSI board, the other is a brand new Biostar board. All have powered risers. I'll unplug one GPU, and just try with 4 GPU's. 1 card will be at 11-12, and other 3 at 18 MH/s. Restart, the slow card will be back at 18 but another card will be down to 11-12. It's driving me nuts! I downloaded the miner from Mega. One computer is running 9.7, the other 9.8. Same problem. So, it's not any particular GPU, not the miner version, not the motherboard, not the number of GPU's attached. What the heck is the problem? Somebody hacked into the miner?

[kjs]

Could you add support to enable Claymore to run with the AMD ROCm driver stack on Linux?

https://github.com/RadeonOpenCompute/ROCm

$ uname -a
Linux X10SDV16C 4.11.0-kfd-compute-rocm-rel-1.6-115 #1 SMP Sat Jul 22 17:28:42 CDT 2017 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
LSB Version:    core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.2 LTS
Release:        16.04
Codename:       xenial

OpenCL Info:

Platform ID #1
  Vendor  : Advanced Micro Devices, Inc.
  Name    : AMD Accelerated Parallel Processing
  Version : OpenCL 2.0 AMD-APP (2450.0)

  Device ID #1
    Type           : GPU
    Vendor ID      : 1
    Vendor         : Advanced Micro Devices, Inc.
    Name           : gfx900
    Version        : OpenCL 1.2
    Processor(s)   : 64
    Clock          : 1600
    Memory         : 12276/16368 MB allocatable
    OpenCL Version : OpenCL C 2.0
    Driver Version : 1.1 (HSA,LC)

����������������������������������������������������������������ͻ
�      Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.8      �
����������������������������������������������������������������ͼ

ETH: 1 pool is specified
Main Ethereum pool is asia1.ethermine.org:4444
DCR: 0 pool is specified
At least 16 GB of Virtual Memory is required for multi-GPU systems
Make sure you defined GPU_MAX_ALLOC_PERCENT 100
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool
OpenCL initializing...

AMD Cards available: 1
GPU #0: gfx900, 16368 MB available, 64 compute units
GPU #0 recognized as Vega
POOL/SOLO version
Cannot build OpenCL program for GPU 0
GPU #0: algorithm ASM
No NVIDIA CUDA GPUs detected.
Total cards: 1
AMD ADL library not found.
No pool specified for Decred! Ethereum-only mining mode is enabled
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
ETH: eth-proxy stratum mode
Watchdog enabled
Remote management (READ-ONLY MODE) is enabled on port 3333

ETH: Stratum - connecting to 'asia1.ethermine.org' <139.99.9.157> port 4444
ETH: Stratum - Connected (asia1.ethermine.org:4444)
ETH: Authorized
Setting DAG epoch #136...
Setting DAG epoch #136 for GPU0
Create GPU buffer for GPU0
GPU0, OpenCL error -48 (0) - cannot create DAG on GPU
GPU 0 failed
Setting DAG epoch #136 for GPU0
GPU0, OpenCL error -48 (0) - cannot create DAG on GPU
ETH: 08/02/17-10:22:22 - New job from asia1.ethermine.org:4444
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
ETH: GPU0 0.000 Mh/s
GPU 0 failed
Quit signal received...