[Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s)

[xpulse]

First off, thanks so much glph3k! I've been using your miner since the beginning, it's come a long way since then!

Like many vega owners/miners, I've been waiting for the day when using the August BC drivers is no longer necessary. Seems that day is here!

I'm getting full speeds on all 56/64 cards with your updated miner and the new 18.3.4 Adrenalin drivers. No more disable/enable needed!

I'm also hoping to get my Vega FEs switched over soon as well, but Overdriven Tool does not support Vega FE yet on the new drivers.

I will say that I did notice the same issue that RAJNIFICENT mentioned on several of my rigs. I've reduced some clocks and added some voltage, fingers crossed that that solves it.

Also wanted to say I'm liking your --ratewatchdog argument. From what I've seen, it picks up the slight drops in hashrate pretty well. Vega mining is getting close to plug and play!

I have no luck to get it work with Vega FE, it crashed drivers for this card. 64 works well.
Did you have any luck with FE?

[N2DCRYPT]

I have no luck to get it work with Vega FE, it crashed drivers for this card. 64 works well.
Did you have any luck with FE?

I had no trouble installing the new drivers on my 3 FE rig... but I don't think I tried to run CAST because ODTool wasn't working, and I decided to just switch back to BC drivers. I may try later if I get the time!

[mk111]

I am still on Blockchain Beta drivers and 0.9.2 gave me about 15h/s extra per Vega 56.
Good work glph3k!

[polofitted007]

Anybody want to help me out...

So I updated to the driver, using the latest cast xmr but i I only getting GPU0 found when I have too. 

1.  What should the config file be?
2.  Do I have to do anything to setup double thread?
3.  Any advice would be great

Thanks!

[N2DCRYPT]

Anybody want to help me out...

So I updated to the driver, using the latest cast xmr but i I only getting GPU0 found when I have too.  

1.  What should the config file be?
2.  Do I have to do anything to setup double thread?
3.  Any advice would be great

Thanks!

Do you have "-G 0,1" in your config?

And no, shouldn't have to setup any threads.

[polofitted007]

That worked, getting 3300 H/S out of 2 56's, does that sound right? 

Also, do I need to turn off crossfire still?

Once again, Thanks!

[N2DCRYPT]

That worked, getting 3300 H/S out of 2 56's, does that sound right? 

Also, do I need to turn off crossfire still?

Once again, Thanks!

That's low. And no, don't think you'll have to with the new drivers...

Sounds like you're new here... which would mean that you haven't gotten all into SoftPowerPlay tables and all that, and registry edits to turn off Crossfire, etc. For in depth, check out vegaminingblogspot. Probably the best and most concise guide (although much of that is no longer needed with the new drivers and CAST). You should overclock your memory, either with Wattman or Overdriven tool.

If you don't care about power consumption and undervolting, try putting your memclock at 950 MHz for both cards and report back on your hashrate 

[polofitted007]

That worked, getting 3300 H/S out of 2 56's, does that sound right? 

Also, do I need to turn off crossfire still?

Once again, Thanks!

That's low. And no, don't think you'll have to with the new drivers...

Sounds like you're new here... which would mean that you haven't gotten all into SoftPowerPlay tables and all that, and registry edits to turn off Crossfire, etc. For in depth, check out vegaminingblogspot. Probably the best and most concise guide (although much of that is no longer needed with the new drivers and CAST). You should overclock your memory, either with Wattman or Overdriven tool.

If you don't care about power consumption and undervolting, try putting your memclock at 950 MHz for both cards and report back on your hashrate 

Once again, thanks(Beleive it or not, I have had the vegas up and running until a month ago for 6 months, hands off.  Used the script provided in that vegamining guide)...

Im just being silly.  I will install overdrive and update the soft play tables.  I don't know why i though the new miner did all of that with just the updated driers.  Ill report back once i overclock and change the registry...

[polofitted007]

Ok, Overdrive in working, and softplay applied, now getting 1900 H/S..... YAAAAAYYYYYY

[SpainPoul]

What is the best pool?

[polofitted007]

What is the best pool?

I'm using mine2gether to mine TRTL

[RAJNIFICENT]

First off, thanks so much glph3k! I've been using your miner since the beginning, it's come a long way since then!

Like many vega owners/miners, I've been waiting for the day when using the August BC drivers is no longer necessary. Seems that day is here!

I'm getting full speeds on all 56/64 cards with your updated miner and the new 18.3.4 Adrenalin drivers. No more disable/enable needed!

I'm also hoping to get my Vega FEs switched over soon as well, but Overdriven Tool does not support Vega FE yet on the new drivers.

I will say that I did notice the same issue that RAJNIFICENT mentioned on several of my rigs. I've reduced some clocks and added some voltage, fingers crossed that that solves it.

Also wanted to say I'm liking your --ratewatchdog argument. From what I've seen, it picks up the slight drops in hashrate pretty well. Vega mining is getting close to plug and play!

Hi, please share your success / failures.  I'm trying to reduce my overclock, however my hashrates on one rig continues to drop.  If I can get rate watch to work as designed, dude my life would be complete.

[AlexanderDumas]

That worked, getting 3300 H/S out of 2 56's, does that sound right? 

Also, do I need to turn off crossfire still?

Once again, Thanks!

That's low. And no, don't think you'll have to with the new drivers...

Sounds like you're new here... which would mean that you haven't gotten all into SoftPowerPlay tables and all that, and registry edits to turn off Crossfire, etc. For in depth, check out vegaminingblogspot. Probably the best and most concise guide (although much of that is no longer needed with the new drivers and CAST). You should overclock your memory, either with Wattman or Overdriven tool.

If you don't care about power consumption and undervolting, try putting your memclock at 950 MHz for both cards and report back on your hashrate 

I think he will care about power consumption, because between using the "power tables" and not, there is about 90W per card difference.

160W VS 250W.

[polofitted007]

That worked, getting 3300 H/S out of 2 56's, does that sound right? 

Also, do I need to turn off crossfire still?

Once again, Thanks!

That's low. And no, don't think you'll have to with the new drivers...

Sounds like you're new here... which would mean that you haven't gotten all into SoftPowerPlay tables and all that, and registry edits to turn off Crossfire, etc. For in depth, check out vegaminingblogspot. Probably the best and most concise guide (although much of that is no longer needed with the new drivers and CAST). You should overclock your memory, either with Wattman or Overdriven tool.

If you don't care about power consumption and undervolting, try putting your memclock at 950 MHz for both cards and report back on your hashrate 

I think he will care about power consumption, because between using the "power tables" and not, there is about 90W per card difference.

160W VS 250W.

My power rarte is .052 so I don't mine the xtra power...

[AlexanderDumas]

That worked, getting 3300 H/S out of 2 56's, does that sound right? 

Also, do I need to turn off crossfire still?

Once again, Thanks!

That's low. And no, don't think you'll have to with the new drivers...

Sounds like you're new here... which would mean that you haven't gotten all into SoftPowerPlay tables and all that, and registry edits to turn off Crossfire, etc. For in depth, check out vegaminingblogspot. Probably the best and most concise guide (although much of that is no longer needed with the new drivers and CAST). You should overclock your memory, either with Wattman or Overdriven tool.

If you don't care about power consumption and undervolting, try putting your memclock at 950 MHz for both cards and report back on your hashrate 

I think he will care about power consumption, because between using the "power tables" and not, there is about 90W per card difference.

160W VS 250W.

My power rarte is .052 so I don't mine the xtra power...

well.... The extra watts are extra heat on your hardware and more wear and tear on GPU and PSU, and even if you do not mind the extra power, why wasting it?

[heavyarms1912]

That worked, getting 3300 H/S out of 2 56's, does that sound right? 

Also, do I need to turn off crossfire still?

Once again, Thanks!

That's low. And no, don't think you'll have to with the new drivers...

Sounds like you're new here... which would mean that you haven't gotten all into SoftPowerPlay tables and all that, and registry edits to turn off Crossfire, etc. For in depth, check out vegaminingblogspot. Probably the best and most concise guide (although much of that is no longer needed with the new drivers and CAST). You should overclock your memory, either with Wattman or Overdriven tool.

If you don't care about power consumption and undervolting, try putting your memclock at 950 MHz for both cards and report back on your hashrate 

I think he will care about power consumption, because between using the "power tables" and not, there is about 90W per card difference.

160W VS 250W.

My power rarte is .052 so I don't mine the xtra power...

Do it to save electricity regardless of the price.  it's not even a big task.  and you can reduce the heat dissipated by a lot & reduce the fan noise.

[polofitted007]

That worked, getting 3300 H/S out of 2 56's, does that sound right?  

Also, do I need to turn off crossfire still?

Once again, Thanks!

That's low. And no, don't think you'll have to with the new drivers...

Sounds like you're new here... which would mean that you haven't gotten all into SoftPowerPlay tables and all that, and registry edits to turn off Crossfire, etc. For in depth, check out vegaminingblogspot. Probably the best and most concise guide (although much of that is no longer needed with the new drivers and CAST). You should overclock your memory, either with Wattman or Overdriven tool.

If you don't care about power consumption and undervolting, try putting your memclock at 950 MHz for both cards and report back on your hashrate  

I think he will care about power consumption, because between using the "power tables" and not, there is about 90W per card difference.

160W VS 250W.

My power rarte is .052 so I don't mine the xtra power...

Do it to save electricity regardless of the price.  it's not even a big task.  and you can reduce the heat dissipated by a lot & reduce the fan noise.

How else will you get 1900 H/S without overclocking?  I bought the GPU to mine, therefore I am going to use it up

[heavyarms1912]

That worked, getting 3300 H/S out of 2 56's, does that sound right?  

Also, do I need to turn off crossfire still?

Once again, Thanks!

That's low. And no, don't think you'll have to with the new drivers...

Sounds like you're new here... which would mean that you haven't gotten all into SoftPowerPlay tables and all that, and registry edits to turn off Crossfire, etc. For in depth, check out vegaminingblogspot. Probably the best and most concise guide (although much of that is no longer needed with the new drivers and CAST). You should overclock your memory, either with Wattman or Overdriven tool.

If you don't care about power consumption and undervolting, try putting your memclock at 950 MHz for both cards and report back on your hashrate  

I think he will care about power consumption, because between using the "power tables" and not, there is about 90W per card difference.

160W VS 250W.

My power rarte is .052 so I don't mine the xtra power...

Do it to save electricity regardless of the price.  it's not even a big task.  and you can reduce the heat dissipated by a lot & reduce the fan noise.

How else will you get 1900 H/S without overclocking?  I bought the GPU to mine, therefore I am going to use it up

Almost everyone out there with Vega and mining get 1900 MH/s

I get 1960 MH/s @ 1408 Mhz core /1100 Mhz HBM2 frequency (875mV on core) on Vega56 bios modded to Vega 64 and using soft_pp power table.  The power consumption is 150-160w on wall.
All info can be found in the below guide
http://vega.miningguides.com/

[End3rWiggin]

It's not working quite right for me

* Used DUU to uninstall drivers, and installed new Adrenaline drives.
* Disabled Crossfire and set Profiles to custom and custom voltage to on.
* Wrote Soft PP tables to registry.
* Restarted.

So everything works great at the start - 2000H/s and lower temperatures, same voltages and power consumption.
But after about 20min it just stops working entirely, if I press q to quit it just hangs, and I have to restart the system.

Back on blockchain drivers

[N2DCRYPT]

Yeah... so I got a little too excited too soon. Definitely have my overclocks well within previous working ranges, and yet after mining for a while cards will randomly start hashing ~100-200 H/s. Very strange... I can exit the miner without it hanging and having to restart, but still, can't be around to monitor the machines.

Will probably pull out the old JJHashRateMonitor modified for CAST and see if that can take care of it, since --ratewatchdog can't fix this problem. We're getting close though!