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

[duyquang06]

Dear glph3k,

Will you update XMR_Cast to compatible new custom cryptonight algo PoV of IPBC coin. It is not Monero V7 also.

[TheDarkAngel]

someone should test the adrenalin driver 18.3.4 out today on vega - it specifically mentions fixing some blockchain workloads performance that was lower than it should be. my rig is very unstable and it could take me hours so i'm not volunteering

"Fixed Issues: Some blockchain workloads may experience lower performance than expected when compared to previous Radeon Software releases."

I've tested and... it's working! 2050h/s vega64 liquid

[Permonik]

someone should test the adrenalin driver 18.3.4 out today on vega - it specifically mentions fixing some blockchain workloads performance that was lower than it should be. my rig is very unstable and it could take me hours so i'm not volunteering

"Fixed Issues: Some blockchain workloads may experience lower performance than expected when compared to previous Radeon Software releases."

I've tested and... it's working! 2050h/s vega64 liquid

Hi, where they are mentioned the fixing of the blockchain workloads? I did not saw it in release notes...

[Combat Fighter]

someone should test the adrenalin driver 18.3.4 out today on vega - it specifically mentions fixing some blockchain workloads performance that was lower than it should be. my rig is very unstable and it could take me hours so i'm not volunteering

"Fixed Issues: Some blockchain workloads may experience lower performance than expected when compared to previous Radeon Software releases."

I don't exactly plan to test new drivers until before the official blockchain release appeared. Stable work without failures is more important than few hashes.

This is the proof that the new amd 18-3-4 drivers for Vega do really work now giving full speed:

https://forums.overclockers.co.uk/threads/amd-18-3-4-drivers-blockchain-fix-vega-xmr-stack-2-3-0.18815432/

So you can get over 2000+h/s using xmr-stack.

Hopefully cast-xmr can be tweaked to use these as well in a near future release?

[AlexanderDumas]

I can confirm as well the new driver "march 23" works like a charm.
Same hash rate as the old blockchain drivers.

I Run the installer which ask if you want to perform a clean install: YES
Then I applied the power tables to the registry.
I also disabled the Crossfire on the registry. Although it may not be necessary anymore.
Rebooted.

Applied my overclocking via the overdrive tool.
Started Cast as usual.

I did not even need to do the "disable/enable GPU" routine.

[Permonik]

I can confirm as well the new driver "march 23" works like a charm.
Same hash rate as the old blockchain drivers.

I Run the installer which ask if you want to perform a clean install: YES
Then I applied the power tables to the registry.
I also disabled the Crossfire on the registry. Although it may not be necessary anymore.
Rebooted.

Applied my overclocking via the overdrive tool.
Started Cast as usual.

I did not even need to do the "disable/enable GPU" routine.

That is really nice.
What about power consumption?
Is it same?

[Combat Fighter]

I can confirm as well the new driver "march 23" works like a charm.
Same hash rate as the old blockchain drivers.

I Run the installer which ask if you want to perform a clean install: YES
Then I applied the power tables to the registry.
I also disabled the Crossfire on the registry. Although it may not be necessary anymore.
Rebooted.

Applied my overclocking via the overdrive tool.
Started Cast as usual.

I did not even need to do the "disable/enable GPU" routine.

Sweet, cheers for confirming I’ll give em a go later on.

Worth putting on just to save disabling/enabling drivers after a restart!

[AlexanderDumas]

I can confirm as well the new driver "march 23" works like a charm.
Same hash rate as the old blockchain drivers.

I Run the installer which ask if you want to perform a clean install: YES
Then I applied the power tables to the registry.
I also disabled the Crossfire on the registry. Although it may not be necessary anymore.
Rebooted.

Applied my overclocking via the overdrive tool.
Started Cast as usual.

I did not even need to do the "disable/enable GPU" routine.

That is really nice.
What about power consumption?
Is it same?

Yes it is about the same.
4 Vegas about 730W at the wall. All MB CPU Memory Fans.... included.

Although I think I previously  saw it at 680w sometimes, but most of the times it was just above 700w.

[tvukoman]

cant connect to webpage remote access  http://127.0.0.1:7777 --remoteaccess is enabled

What to do? Txs.

Try using "-R" instead of "--remoteaccess"

Txs!

Working, but, i must have both "-R" and "--remoteaccess" and now working. Strange.

If i put just -R without --remoteaccess cast XMR wont even start...

[Combat Fighter]

Just tested the new drivers vs the old blockchain drivers.

Hash rate is slightly down on each of my Vega's by at least 40-50 h/s (with 8x Vega 64's)

Also even though I applied the powertables, when opening OverdriveN most of the powertable settings get greyed out (I tweak some of the settings with my own profile within OverdriveN) when you apply settings.

And powerdraw is slightly up, might be because of the powertables/OverdriveN not working properly.

So. . .

Switched back using the old blockchain drivers and all working fine (better hash, power and overdriveN working properly)

Needless to say I'll be staying put for now with the blockchain drivers until things get updated.

One thing to note you don't have to reset the drivers after rebooting with the new drivers which is the only plus I can see for now.

[treanski]

a little bit off topic, can somebody provide me a vega 64 Hynix Bios? i got some PC RedDevil 56 which have hynix memory, but the RedDevil 64 Bios only supports Samsung

[rednoW]

a little bit off topic, can somebody provide me a vega 64 Hynix Bios? i got some PC RedDevil 56 which have hynix memory, but the RedDevil 64 Bios only supports Samsung

As far as I know there is no vega64 with hynix mem. Hynix hbm2 doesn't meet required vega64 memory frequencies.

[glph3k]

Hi,

finally, the days of the blockchain compute beta drivers are numbered.

Here is an update of Cast XMR. The 99% refer to the performance when the same memory clock is set.

Regards,
glph3k


Cast XMR Version 0.9.2 (2018/03/29)

  - Improvements for RX Vegas that achieve 99% the performance of the Blockchain Compute Beta driver with the latest standard Radeon Driver 18.3.4

Download Cast XMR 0.9.2 for Windows (64bit)

SHA256 hash of cast_xmr-vega-win64_092.zip:
83e35e16e4e4c57065113323ab9dfd1782935154265f9730bd18877dfbe1adfe

[AlexanderDumas]

Hi,

finally, the days of the blockchain compute beta drivers are numbered.

Here is an update of Cast XMR. The 99% refer to the performance when the same memory clock is set.

Regards,
glph3k


Cast XMR Version 0.9.2 (2018/03/29)

  - Improvements for RX Vegas that achieve 99% the performance of the Blockchain Compute Beta driver with the latest standard Radeon Driver 18.3.4

Download Cast XMR 0.9.2 for Windows (64bit)

SHA256 hash of cast_xmr-vega-win64_092.zip:
83e35e16e4e4c57065113323ab9dfd1782935154265f9730bd18877dfbe1adfe

Thank you for the update. You always deserve your fee for the miner, no doubt about that.
Actually 9.02 gave my Vegas a good performance boost of about 30/40 h/s per card.

Before with 9.01 ( and 7.xx 8.xx) the 64 was ashing at around and average of 1970/80hs and the 56 at around 1930/40hs, now with Cast 9.02 the 64 hashes at 2020hs and the 56 at 1970hs.
The new drivers indeed initially had a little drop of 10/15hs per card compared to the old Blockchain drivers, but Cast 9.02 fixed that and gave a performance boost compared to any drivers software configuration I ever used before.

I am also getting lower temperatures (2 to 3 celsius on average).

By the way, I have been running the new drivers for almost 48 hours and power draw in my case, has not changed a zic compared to the old blokchain drivers.
I even reinstalled the old blockchain drivers back for a couple of hours to make sure, but there is not power usage increase or decrease among the 2 drivers version.

hopefully every one will be able to enjoy the improvements.

[Combat Fighter]

Hi,

finally, the days of the [Suspicious link removed]pute beta drivers are numbered.

Here is an update of Cast XMR. The 99% refer to the performance when the same memory clock is set.

Regards,
glph3k


Cast XMR Version 0.9.2 (2018/03/29)

  - Improvements for RX Vegas that achieve 99% the performance of the [Suspicious link removed]pute Beta driver with the latest standard Radeon Driver 18.3.4

Download Cast XMR 0.9.2 for Windows (64bit)

SHA256 hash of cast_xmr-vega-win64_092.zip:
83e35e16e4e4c57065113323ab9dfd1782935154265f9730bd18877dfbe1adfe

Nice one!

[heavyarms1912]

Hi,

finally, the days of the blockchain compute beta drivers are numbered.

Are there any other cons to compute beta driver compared to Adrenalin?

[RAJNIFICENT]

Hi,

After upgrading to 9.1 and enabling the ratewatchdog, I'm noticing some issues.  For example I have 2 mixed rigs. 

One rig consists of 8 1070TI, 2 vega 64, 2 RX 570 (RIG A)

Other rig consists of 8 1070TI 4 Vega 56 (RIG B)

RIG A works FLAWLESSLY with the ratewatchdog argument.  I haven't dropped hashrates in over 24 hours and that's impressive considering it dropped roughly every 1000ish shares.

RIG B works somewhat.  Within 5--6 hours of running the program, rate watch works as expected, but after 8-10 hours or overnight, some of the cards drop to 56 khs... 


I don't know if you can make sense of this, but hope this helps improve upon the argument.

Thank you!

[Combat Fighter]

What's the max amount of Vega's you can run with one instance of Cast-XMR now?

[N2DCRYPT]

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!

[macsim]

I have a (maybe stupid) question, but I prefer to be sure...

If I change my driver version from Blockchain one to 18.3.4, would I need to apply soft power play tables, or is it possible to control directly the memory and core voltages with OverdriveNTool ?

Thanks !