Topic: [Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s) - page 2. (Read 206388 times)

Try the SRB Miner, this is the fastest cryptonight miner now for all amd cards.

https://www.srbminer.com

I like your style: 'earn a misery' is about right!

Dear Gandalph,

Please check the Hospital coin algo. This is CN-HOSP. I would like to mine with cast-xmr.

https://hospitalcoin.net/#specifications-section

Thanks the help.

How do you adjust fan speed for multiple GPUs? I keep getting errors when trying to set fan speed, men, and voltage. It all works for the first GPU, but not the others. Thanks for and guidance.

This is what I get:
setting card3 fan speed to 180
bash: /sys/class/drm/card3/device/hwmon/hwmon3/pwm1: No such file or directory

Ubunto 18.0.4 with three Vega Festivals

when trying to set fan speed and other low level functions I get this

setting card3 fan speed to 180
bash: /sys/class/drm/card3/device/hwmon/hwmon3/pwm1: No such file or directory

It works for only the first GPU. I get the above for the remaining GPUs.
What do I need to do?
I use Ubunto 18.0.4 Thanks

I have updated to the latest version of cast. My CNV8 hash rates continue to be around 1700 hs for a vega 56. Not sure why its low with me on here but it doesn't matter much anymore since the difficulty for monero just shot up so much this past 2 weeks i stopped mining it. But whattomine is saying that masari is the most profitable coin to mine with my vegas and that's what i will have them pointed at. So far im averaging around 3100 hs per card using the same settings on the cards that i use for monero. System total for 3 vegas is around 9200-9300 hs at 600 watts at the wall. At that rate im making a small profit with my farm.

Is it advisable to mine with vega 64? I am mining monero and earn a misery

I faced the same, it's due to high graphics setting used for other running programs. So an easy solution for it, just set the intensity in miner lower... like if it is running on 10/10, So you change for -intensity=6/10 or 7/10, then you'll no need to restart your pc, hope so you'll cope upon this issue. Good luck.

And can someone tell me, Core i7, 8gb ram, and two vega 64 FE are installed in the same board with the drivers of Vega FE version 18.Q4. The speed for cryptonight heavy is only 1580~1600H/s per card, and 3900 for CN lite per card... and specially 4.5 M/s for Purk coin. How can I improve it for CN heavy???

Cheers for the update

http://www.gandalph3000.com/

1.7 came up!!

ast XMR Version 1.7.0 (2019/01/24)
support for CryptoNightV8-Fast (--algo=6) for mining Stellite (XTL). The previous CryptoNightXTL algo has been removed
support for Masari (MSR) upcoming network upgrade, Masari is also switching to CryptoNightV8-Fast, so change algo to --algo=6 when the Masari network upgrade is happening (scheduled for January 26th)
support for CryptoNight-Turtle (--algo=9) for the upcoming Turtlecoin (TRTL) PoW network upgrade (at block 1,200,000)
Vega FE: option to turn --intensity up to 13 for “Fast” CryptoNight variants to gain 2% higher hash rates

Will there be support for Cryptonight-turtle?

%1 performance improvment to me.. and so far stable..  FYI  glph3k 

Has anyone tried new adrenaline driver 19.1 with vega 56 cards? Any known issue with CAST XMR?

BR,

Dear glph3k,

Please check the hospital coin, it will fork CN-HOSP (Variant 4) soon.

https://bitcointalk.org/index.php?topic=5041899.80


Thanks the help. You are awesome!

Looking for suggestions on best settings, PPTable, for Sapphire Pulse RX570 ITX 4GB, single fan cards. 

These cards are tiny, draw little power, and before the last fork, with strap pimping they would get 900+ H/s, no sweat.  For CNv8, I've tried Polaris Bios modes, SRBPolaris, and I've tried generating custom PP tables.  I have one card that hits 830-870 H/s, the rest tend to stay at 650-720 on CNv8.  I've tried various ONT settings with P7 adjusted from 1150-1286/900-925; P4 adjusted from 1850-2100/900.

I'm using Cast 1.6.6 which I have used for a long while.  Cast is working just great with my Vega 54 flashed -> 64 cards.

Any ideas?  Anything obvious that I am overlooking?

RX570 ITX 4GB -- any ideas?

@glph3k
Thanks for your great $oftware!
Can you please please update your guide "How to mine CryptoNight based crypto currencies with Radeon RX Vega 56/64 GPUs"? The values showed there are for an older build and for v7.

AscendingNight - Please add the new Hardfork from CryptoNight

Tax-Project uses the CryptoNight (AscendingNight) hash algorithm, which is optimized for CPU-based mining and GPU resistance, with the Algo specializing in fair sharing of the hashrate.
Tax forked from CN-Heavy to to their own custom variant recently and was hoping you could add support for it.

AscendingNight is similar to CryptoNight (same scratchpad implode and explode) but it utilizes a different main algorithm. While CryptoNight uses one aes step every second step, AscendingNight uses one AES every fourth step, has some substitutional parts and things like that to perform less calculations for more memory intesety.
In our private testing we came across performance boosts of 10% to 30% on Ryzen CPUs and up to 100% on older i7s.
Since the memory utilisation is still the same, the algorithm is just as fast on GPU (mathematically speaking, not tested yet).

The thing with Heavy, light and fast is just that, similar to CryptoNight, you can apply all the causal variations like CN-Heavy on AN as well (since it's just changing memory and iteration variables).

The point with the reference implementation of AscendingNight is that, while it's modular, it's still using 2MB as a scratchpad size and 2^14 iterations to increase the speeds of the validation process.
By increasing the iteration number to the casual CryptoNight step count of 2^20 you'd see an even higher boost in the performance of CPUs compared to GPUs.

The important changes were done in the post_aes macro. It can be found in here:
https://github.com/Tax-Project/Tax/blob/master/src/crypto/slow-hash.c#L264

Links
├──.Reference implementation
│.......├──..https://github.com/Tax-Project/Tax/blob/master/src/crypto/slow-hash.c
│.......├──..http://clashproject.org/tax/
│.......├──..https://github.com/Tax-Project
│.......├──..https://github.com/Tax-Project/Miner-UI
├──.Test-Pool
│.......├──..http://207.180.246.163/#
├──.Wallet
└──────.http://clashproject.org/tax/

Let me know if you need any help or further information.

As a follow up to this post, I am mining Haven.  Some additional observations -

I am seeing this same behavior with all my RX Vega 56 cards, doesn't matter what vendor or in what machine they are installed.  Interestingly, in one machine I have both Vega 56's and RX 580's installed.  When the "issue" occurs, only the Vega 56's hashrate drops....RX 580's are unaffected. 

Hello,

Am noticing an issue after upgrading to Cast XMR 1.6+....after running for several minutes (sometimes as long as an hour) the hashrate on my rigs (4xRX Vega 56) will drop by 30%.  In tandem with this drop, the miner will report at least one "network error."  Other AMD rigs I have running the same version of Cast XMR (but 10xRX 580's) are unaffected as are any NVIDIA rigs.  I have played for a long time with the overclocking settings on the RX Vega 56's, and nothing seems to help with this issue.  When the rigs with the RX Vega 56's "hiccup" the network error they drop from roughly 1500 H/s to 1200 H/s.  Have also tried the Adrenaline 18.5.1, 18.11.1, and 18.12.1 with the same results. 

Conclusion I am coming to at this point is that there is a bug in version 1.66 which causes the RX Vega 56's to "downshift" if there is a network error...is anyone else seeing the same behavior?

Cast-XMR 1.6.6 added to https://www.minermonitoring.com/



Join our discord https://discord.gg/aGGaeqq



also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark