Author

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

member
Activity: 66
Merit: 10

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!
newbie
Activity: 27
Merit: 0
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 Smiley) 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 Smiley


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.
member
Activity: 81
Merit: 10

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
member
Activity: 66
Merit: 10

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
legendary
Activity: 1564
Merit: 1027
Amd wants you to use their WattMan, no 3rd party. Rollback to older driver this will be solved...

Right, but how can we set Wattman values automatically after a reboot/crash? WattTool  is perfect for that!
donator
Activity: 1610
Merit: 1325
Miners developer
@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.
newbie
Activity: 36
Merit: 0
@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?


Amd wants you to use their WattMan, no 3rd party. Rollback to older driver this will be solved...
member
Activity: 66
Merit: 10
Hi! I'm getting the FAILOVER 4 fault, so I'm going to edit epools.txt? For ethermine the command line should be "-allpools 1" and "ESM 0" right? And in the "epools.txt" I must write -allpools 1 and ESM 0 too? My main pool is eu1.ethermine.org:1444, alternative pools will be eu1.ethermine.org:4444, eu2:ethermine.org:14444, eu2.ethermine.org:4444, us1, us2 or asian server? Which is better? I'm from spain. Thanks!
full member
Activity: 160
Merit: 100
@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 (without using 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?
newbie
Activity: 46
Merit: 0

Is it the 17.7.2 that will solve the DAG problem?
sr. member
Activity: 378
Merit: 250
Thank you, working great!

7 x 1070's were getting 198 mh/s on eth and 3040 on decred. Now getting 203 mh/s and 3100 each. Not quite 3-5% increase but still an increase.

From 9.7 > 9.8 you saw an increase?  Did you see any increase on ETH only?  

On 9.7 I was running dcri at 38 to get the numbers above. Now I'm running dcri at 55 and able to keep ETH at 200 but decred is able to go up to 3700 which seems to be the sweet spot for profitability. So while I didn't get the 3-5% increase straight out of the box, with some tweaking, there is a noticeable improvement.

I also just tried single mining ETH right now. On 9.7 I was getting 212 mh/s, and now I'm getting 218 which would be just about under a 3% increase in performance --> which leads me to think the dual mining has increased significantly with this build. I wonder if adjusting each card individually for power/memory will respond differently in 9.8. Each card is pulling just over 31.xx mh/s on single mining. Although 218 mh/s single mining is slightly less profitable than 200 mh/s and dual mining another coin.
Can you share your powerlimit and oc settings?
newbie
Activity: 5
Merit: 0
Hi Claymore and all,

I'm facing intermittent issue.

The Rig can run from an hour to over 14 hours without any issues but the issue occurs as shown below:

20:37:39:527   1044   NVML: cannot get current temperature, error 15
20:37:39:589   1044   NVML: cannot get fan speed, error 15
20:37:39:636   1044   srv bs: 0
20:37:39:636   c08   NVML: cannot get current temperature, error 15
20:37:39:636   1044   sent: 235
20:37:39:636   c08   NVML: cannot get fan speed, error 15
20:37:39:652   1524   NVML: cannot get current temperature, error 15
20:37:39:652   1524   NVML: cannot get fan speed, error 15

Almost same problem with him. Any body can help if "NVML: cannot get current temperature, error 15" message appear always with 6 VGA rig?

After that it is working stable with 5 VGA only (1 disconnect automatically).

Thanks you.
newbie
Activity: 32
Merit: 0
v9.8:

- added Vega cards support (ASM mode).
- added fan/OC support for 17.7.2 (and higher) drivers.
- fixed issue with -ttli and -ttdcr option for Nvidia cards.
- improved support for systems with more than 10 GPUs, check readme for "-di" and "-mode" options description for details.
- a few minor bug fixes and improvements.

Thank you for the quick updates, much appreciated here!
legendary
Activity: 1246
Merit: 1024
hello guys,

with claymore 9.8 can also mining BCC (Cash!) ?

Or which kind of software we need for mining Bitcoincash??


Thank you

Luisa

No. You need ASIC hardware the same as Bitcoin at this time.
member
Activity: 163
Merit: 10
hello guys,

with claymore 9.8 can also mining BCC (Cash!) ?

Or which kind of software we need for mining Bitcoincash??


Thank you

Luisa
hero member
Activity: 2548
Merit: 626
From this point of view, I think weird API is better than no API at all.


Wrong, no API had been better, as people would just use other tools, they used earlier.
This way they blame the miner software, like you said.
sr. member
Activity: 2604
Merit: 326
I'd like to say a bit more about ADL (library that is used to manage clocks/voltage/fan). I have been working with ADL API for a couple of years, so I have some experience.
When you use ADL, you must ask what version of API supports your GPU. For example, Tahiti reports v5, Hawaii v6.
Every API version uses own set of functions, sample code can be found in ADL SDK. I implemented v5 and v6 and it worked fine for some time.
Then in some drivers AMD disabled underclocking via ADL for some reason, API calls report "OK" but GPU still uses old clocks.
Then AMD releases Polaris cards which report API v7. And no new ADL SDK was released so no headers for new API or any samples. We had to wait for a couple of months before it was finally released.
I added code that uses v7 and it worked fine, except one thing: if I set fan 50%, API sets it to 41% or 46% and I have no idea why. I had to change fan management logic to make it work properly with this issue.
Then in some drivers AMD changed something again and OC stopped working, partially or completely.
Then AMD releases new drivers and Hawaii cards started to report that they use API v7 instead of v6. But in this mode they support v7 a bit differently than Polaris so I had to change my code again to support this new "feature" of drivers.
Then AMD releases 17.7.2 and API v7 returns "not supported" error code. After some research I found that AMD added new functions for API v7 and blocked old functions. So this time they decided not to create API v8, but changed functions for already released API version. It's awesome. No new ADL SDK is released for these changes, so again no headers or code samples for "new" API v7. Finally I made it work, but sometimes it works with strange issues, currently I try to find the reason.
Vega support in ADL has own problems currently, for example, you can set fan to 90% but then there is no way to set it to any lower value.
For Linux, AMD decided to drop ADL support completely in gpu-pro drivers and use new way that I have to support too.

So ADL is the most weird API I've ever seen, but when you see that some options don't work as expected, probably you will blame the miner Smiley
On other hand, when I decided to add fan/OC management I found that Nvidia has no public API for it at all. From this point of view, I think weird API is better than no API at all.


Still, bad way to do things from AMD, breaking compatibility is always bad idea, specially when you can fry the card doing it...who wants API that OCs your
card and stops fan at the same time? Cheesy
donator
Activity: 1610
Merit: 1325
Miners developer
I'd like to say a bit more about ADL (library that is used to manage clocks/voltage/fan). I have been working with ADL API for a couple of years, so I have some experience.
When you use ADL, you must ask what version of API supports your GPU. For example, Tahiti reports v5, Hawaii v6.
Every API version uses own set of functions, sample code can be found in ADL SDK. I implemented v5 and v6 and it worked fine for some time.
Then in some drivers AMD disabled underclocking via ADL for some reason, API calls report "OK" but GPU still uses old clocks.
Then AMD releases Polaris cards which report API v7. And no new ADL SDK was released so no headers for new API or any samples. We had to wait for a couple of months before it was finally released.
I added code that uses v7 and it worked fine, except one thing: if I set fan 50%, API sets it to 41% or 46% and I have no idea why. I had to change fan management logic to make it work properly with this issue.
Then in some drivers AMD changed something again and OC stopped working, partially or completely.
Then AMD releases new drivers and Hawaii cards started to report that they use API v7 instead of v6. But in this mode they support v7 a bit differently than Polaris so I had to change my code again to support this new "feature" of drivers.
Then AMD releases 17.7.2 and API v7 returns "not supported" error code. After some research I found that AMD added new functions for API v7 and blocked old functions. So this time they decided not to create API v8, but changed functions for already released API version. It's awesome. No new ADL SDK is released for these changes, so again no headers or code samples for "new" API v7. Finally I made it work, but sometimes it works with strange issues, currently I try to find the reason.
Vega support in ADL has own problems currently, for example, you can set fan to 90% but then there is no way to set it to any lower value.
For Linux, AMD decided to drop ADL support completely in gpu-pro drivers and use new way that I have to support too.

So ADL is the most weird API I've ever seen, but when you see that some options don't work as expected, probably you will blame the miner Smiley
On other hand, when I decided to add fan/OC management I found that Nvidia has no public API for it at all. From this point of view, I think weird API is better than no API at all.
full member
Activity: 259
Merit: 108
Thank you, working great!

7 x 1070's were getting 198 mh/s on eth and 3040 on decred. Now getting 203 mh/s and 3100 each. Not quite 3-5% increase but still an increase.

From 9.7 > 9.8 you saw an increase?  Did you see any increase on ETH only?  

On 9.7 I was running dcri at 38 to get the numbers above. Now I'm running dcri at 55 and able to keep ETH at 200 but decred is able to go up to 3700 which seems to be the sweet spot for profitability. So while I didn't get the 3-5% increase straight out of the box, with some tweaking, there is a noticeable improvement.

I also just tried single mining ETH right now. On 9.7 I was getting 212 mh/s, and now I'm getting 218 which would be just about under a 3% increase in performance --> which leads me to think the dual mining has increased significantly with this build. I wonder if adjusting each card individually for power/memory will respond differently in 9.8. Each card is pulling just over 31.xx mh/s on single mining. Although 218 mh/s single mining is slightly less profitable than 200 mh/s and dual mining another coin.
member
Activity: 92
Merit: 10
Thank you, working great!

7 x 1070's were getting 198 mh/s on eth and 3040 on decred. Now getting 203 mh/s and 3100 each. Not quite 3-5% increase but still an increase.

From 9.7 > 9.8 you saw an increase?  Did you see any increase on ETH only? 
Jump to: