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

[HashashInnC]

Thanks a lot claymore you miner it's too good , thanks to the second coin my incoming keep growing with no problem even with my high energy prize

[fr4nkthetank]

@Claymore First, I want to thank you for your great software. Second, I wanna know what is your opinion about miner not working on Win7 with Blockchain drivers? Is it a problem with drivers or in miner?

Try the procedure for installing the leaked unofficial driver fix.  By robinh00d (https://bitcointalk.org/index.php?topic=2068446.0).  It worked for me.  If not, just upgrade to win10

[Kumic]

When was the last time claymore posted on here? He must be on vacation.

Hoping he can fix the new driver issue with voltages.

Claymore
31    Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.8 (Windows/Linux)   on: August 01, 2017, 02:38:07 PM
''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. ''


Buddy if this sounds like a vacation to you then I don't know what to tell you.
It's not enough to just snap your fingers and see money falling from a sky.

[jackbox]

@Claymore. I have an issue where one GPU is randomly dropping to 1.X MH/s and the rig becomes sluggish. Can you have a watchdog type setting where if any GPU drops below a set hashrate for more than X minutes the rig will reboot? This would be of great value.

[Claymore]

Ethermine states that they have found and fixed the issue with DAG #128.

[Sparkly]

@Claymore. I have an issue where one GPU is randomly dropping to 1.X MH/s and the rig becomes sluggish. Can you have a watchdog type setting where if any GPU drops below a set hashrate for more than X minutes the rig will reboot? This would be of great value.

For ETH it is already available as a switch called -minspeed and it works fine for the issue you are describing, just set it to be somewhat below what you normally get from your rig.

[rigshome]

@Claymore First, I want to thank you for your great software. Second, I wanna know what is your opinion about miner not working on Win7 with Blockchain drivers? Is it a problem with drivers or in miner?

Try the procedure for installing the leaked unofficial driver fix.  By robinh00d (https://bitcointalk.org/index.php?topic=2068446.0).  It worked for me.  If not, just upgrade to win10

Thank you for suggestion. It's working!

[ffthomas]

Ethermine states that they have found and fixed the issue with DAG #128.

Thank you for the notification.

[Marvell1]

@Claymore First, I want to thank you for your great software. Second, I wanna know what is your opinion about miner not working on Win7 with Blockchain drivers? Is it a problem with drivers or in miner?

Try the procedure for installing the leaked unofficial driver fix.  By robinh00d (https://bitcointalk.org/index.php?topic=2068446.0).  It worked for me.  If not, just upgrade to win10

stop saying upgrade to win 10, my god Im sick of hearing that. I have win 10 on all my rigs and
all three i tried with the blockchain driver dont work, the same no opencl card detected
error only in claymore.

only robin hood driver works

[nadrojcote]

When was the last time claymore posted on here? He must be on vacation.

Hoping he can fix the new driver issue with voltages.

More like when was the last time you actually read the posts.

You're right he has posted, I just missed them.

From now on Ill check his profile to find his most recent posts.

[yobigd20]

When was the last time claymore posted on here? He must be on vacation.

Hoping he can fix the new driver issue with voltages.

Claymore
31    Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.8 (Windows/Linux)   on: August 01, 2017, 02:38:07 PM
''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. ''


Buddy if this sounds like a vacation to you then I don't know what to tell you.
It's not enough to just snap your fingers and see money falling from a sky.

as a fellow software engineer whose used both apis, claymore is 100% correct on this.  we have to probe dlls calls and look at assembly code to figure out their shitty non-public apis and every time they make a new driver version they seem to f up something like they were on crack at the time they made the release.  being able to set the vega fan to 90% but never less than that is a new one lol that definitely explains why the hell the fan keeps running on high after i kill the damn app.

[greatauror28]

@Claymore First, I want to thank you for your great software. Second, I wanna know what is your opinion about miner not working on Win7 with Blockchain drivers? Is it a problem with drivers or in miner?

Try the procedure for installing the leaked unofficial driver fix.  By robinh00d (https://bitcointalk.org/index.php?topic=2068446.0).  It worked for me.  If not, just upgrade to win10

stop saying upgrade to win 10, my god Im sick of hearing that. I have win 10 on all my rigs and
all three i tried with the blockchain driver dont work, the same no opencl card detected
error only in claymore.

only robin hood driver works

Interesting, blockchain driver and Claymore 9.8 worked with my Win10 seamlessly.
Maybe you're just unlucky.

Anyway, since upgrading to the above setup and dual-mining dcr, I now see incorrect ETH shares (about 10 in a 24-hr period) and lots of rejected DCR shares (113 out of 7600).

Anyone?

[Ursul0]

@Claymore First, I want to thank you for your great software. Second, I wanna know what is your opinion about miner not working on Win7 with Blockchain drivers? Is it a problem with drivers or in miner?

Try the procedure for installing the leaked unofficial driver fix.  By robinh00d (https://bitcointalk.org/index.php?topic=2068446.0).  It worked for me.  If not, just upgrade to win10

stop saying upgrade to win 10, my god Im sick of hearing that. I have win 10 on all my rigs and
all three i tried with the blockchain driver dont work, the same no opencl card detected
error only in claymore.

only robin hood driver works

Interesting, blockchain driver and Claymore 9.8 worked with my Win10 seamlessly.
Maybe you're just unlucky.

Anyway, since upgrading to the above setup and dual-mining dcr, I now see incorrect ETH shares (about 10 in a 24-hr period) and lots of rejected DCR shares (113 out of 7600).

Anyone?

I had custom dag fix driver installed and running fine on my win10(anniversary) rigs. and now I've got amd blockchain beta doing well on all my 470&480.
almost all the cards are doing 28+ (just a few shitty ones and displays are slightly below 28)

[Ursul0]

and in regard to stability and invalid/rejected shares do look at your setup and make sure your cards are configured proper.
even with mem errors on hynix I'm still getting exactly what I'm expecting

[wOvAN]

AMD Radeon Software Crimson™ ReLive 17.8.1 WHQL Beta  -- includes dag fix?

[Ursul0]

AMD Radeon Software Crimson™ ReLive 17.8.1 WHQL Beta  -- includes dag fix?

huh... apparently it does not.
also it seems that there will be no more updates to the "dag fix beta" driver from AMD...

[fredeq]

AMD Radeon Software Crimson™ ReLive 17.8.1 WHQL Beta  -- includes dag fix?

huh... apparently it does not.
also it seems that there will be no more updates to the "dag fix beta" driver from AMD...

They could at least fix it for win7 ><

[doktor83]

what kind of updates do you want? It works.
Maybe they could update it so the hashrate rises, like from 30mhs to 35mhs.
If they can 'fix' and give back 'lost' hash, they could 'fix' it to give more mhs.  

[Chipychop]

hi everybody

changed my mind to mine dual now instead of eth solo, and I am dissapointed with my results

I only get 28 mh/s on every gtx 1070 and 280 mh/s on decred but I saw people with similar oc: 72% power limit, -60 core and +550 memory clock, obtaining around 700 mh/s on decred

eth only I usually get 30 mh/s

otherway, on siacoin I get 27 mhs and around 500 mhs

so what is the problem here?

any help?

[Frippster]

hi everybody

changed my mind to mine dual now instead of eth solo, and I am dissapointed with my results

I only get 28 mh/s on every gtx 1070 and 280 mh/s on decred but I saw people with similar oc: 72% power limit, -60 core and +550 memory clock, obtaining around 700 mh/s on decred

eth only I usually get 30 mh/s

otherway, on siacoin I get 27 mhs and around 500 mhs

so what is the problem here?

any help?

I have cards that have a dramatic drop from 75% power limit to 74%... i.e a 2mh/s drop. Try upping your power limit and see if thats it.