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

[StellarX88]

I have some issues with the vegas not hashing as expected across 2 -3 miners. Hope someone can help

I use this script (http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html) for 2 miner PCs but 1 of them (4x vega64s), only 2 vegas hash at around 1970~, the remaining 2 hash at 1600+h/s .

the other PC (5x vega 56 at stock bios) hashes at only 1400-1500h/s.


I've reset the vegas in both PCs but it doesnt improve.


has anyone tried the JJ's script and hash monitor to automatically reset if the hashrate drops?

Not sure if you ever read the entire thread, I have shared my modified version here albeit at an older JJ version & Cast version. Feel free to update it to latest one accordingly.

https://bitcointalk.org/index.php?topic=2256917.msg25631033#msg25631033

thanks

So all I have to do is edit

$vidTool += 'OverdriveNTool.exe -r1 -p1Vega64' # Expects to be in same folder as this script

and

$global:CAST_XMRcmdline = "-S cryptonight.hk.nicehash.com:3355 -u 1C58yRKSf1ctSKBpP9FrSrDTjzYaRPPumD.VegaLuno -G 1 --remoteaccess"   # CAST_XMR arguments. Not required, REMARK out if not needed


Can i remove the remoteaccess part?

You will need the remote access part for the hash monitor to work.

I think the following link should be more updated to v2.9.

https://drive.google.com/open?id=1TnicWxpB1TtGQCe_cuXND8ha-XsgQsU1

I have detailed my change log inside, you will also most likely need to define the minimum vega hashrate for a restart for your case (I use 1 card so it's a simple 1750000, for your simple use case you can multiply it with the number of cards you have, or if you prefer a restart by checking each card individually).

If you need it to be tweaked somewhat specifically on a per card basis, I can see about modifying the script to fit your use case. Hit me up on Skype (mo.jin.ee) if you would like to do so.

[ntshb]

I have some issues with the vegas not hashing as expected across 2 -3 miners. Hope someone can help

I use this script (http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html) for 2 miner PCs but 1 of them (4x vega64s), only 2 vegas hash at around 1970~, the remaining 2 hash at 1600+h/s .

the other PC (5x vega 56 at stock bios) hashes at only 1400-1500h/s.


I've reset the vegas in both PCs but it doesnt improve.


has anyone tried the JJ's script and hash monitor to automatically reset if the hashrate drops?

Not sure if you ever read the entire thread, I have shared my modified version here albeit at an older JJ version & Cast version. Feel free to update it to latest one accordingly.

https://bitcointalk.org/index.php?topic=2256917.msg25631033#msg25631033

thanks

So all I have to do is edit

$vidTool += 'OverdriveNTool.exe -r1 -p1Vega64' # Expects to be in same folder as this script

and

$global:CAST_XMRcmdline = "-S cryptonight.hk.nicehash.com:3355 -u 1C58yRKSf1ctSKBpP9FrSrDTjzYaRPPumD.VegaLuno -G 1 --remoteaccess"   # CAST_XMR arguments. Not required, REMARK out if not needed


Can i remove the remoteaccess part?

You will need the remote access part for the hash monitor to work.

I think the following link should be more updated to v2.9.

https://drive.google.com/open?id=1TnicWxpB1TtGQCe_cuXND8ha-XsgQsU1

I have detailed my change log inside, you will also most likely need to define the minimum vega hashrate for a restart for your case (I use 1 card so it's a simple 1750000, for your simple use case you can multiply it with the number of cards you have, or if you prefer a restart by checking each card individually).

If you need it to be tweaked somewhat specifically on a per card basis, I can see about modifying the script to fit your use case. Hit me up on Skype (mo.jin.ee) if you would like to do so.

I've edited the settings to

$vidTool += 'OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Vega64 -p2Vega64 -p3Vega64 -p4Vega64'

$global:CAST_XMRcmdline = "-S pool.supportxmr.com:7777 -u walletaddress.Vega64-3 -G 0,1,2,3 --remoteaccess"

as long as I change these 2 lines that;s fine right?

  why is the hashdiff so high? i mean vegas are hashing at 2000 per card?

[StellarX88]

I have some issues with the vegas not hashing as expected across 2 -3 miners. Hope someone can help

I use this script (http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html) for 2 miner PCs but 1 of them (4x vega64s), only 2 vegas hash at around 1970~, the remaining 2 hash at 1600+h/s .

the other PC (5x vega 56 at stock bios) hashes at only 1400-1500h/s.


I've reset the vegas in both PCs but it doesnt improve.


has anyone tried the JJ's script and hash monitor to automatically reset if the hashrate drops?

Not sure if you ever read the entire thread, I have shared my modified version here albeit at an older JJ version & Cast version. Feel free to update it to latest one accordingly.

https://bitcointalk.org/index.php?topic=2256917.msg25631033#msg25631033

thanks

So all I have to do is edit

$vidTool += 'OverdriveNTool.exe -r1 -p1Vega64' # Expects to be in same folder as this script

and

$global:CAST_XMRcmdline = "-S cryptonight.hk.nicehash.com:3355 -u 1C58yRKSf1ctSKBpP9FrSrDTjzYaRPPumD.VegaLuno -G 1 --remoteaccess"   # CAST_XMR arguments. Not required, REMARK out if not needed


Can i remove the remoteaccess part?

You will need the remote access part for the hash monitor to work.

I think the following link should be more updated to v2.9.

https://drive.google.com/open?id=1TnicWxpB1TtGQCe_cuXND8ha-XsgQsU1

I have detailed my change log inside, you will also most likely need to define the minimum vega hashrate for a restart for your case (I use 1 card so it's a simple 1750000, for your simple use case you can multiply it with the number of cards you have, or if you prefer a restart by checking each card individually).

If you need it to be tweaked somewhat specifically on a per card basis, I can see about modifying the script to fit your use case. Hit me up on Skype (mo.jin.ee) if you would like to do so.

I've edited the settings to

$vidTool += 'OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Vega64 -p2Vega64 -p3Vega64 -p4Vega64'

$global:CAST_XMRcmdline = "-S pool.supportxmr.com:7777 -u walletaddress.Vega64-3 -G 0,1,2,3 --remoteaccess"

as long as I change these 2 lines that;s fine right?

  why is the hashdiff so high? i mean vegas are hashing at 2000 per card?

You will know why if you ever bother reading through the changelog that I have detailed together with the modified JJ Hash Monitor script, or if you happen to read up more on Cast-XMR monitoring result port comparison on the very guide that Circus Dad has put together comparing xmr-stak vs cast-xmr : http://vega.miningguides.com/p/castxmr-vs-xmrstak.html

I really don't want to be cynical when it comes to the community helping each other, but when almost every single help that comes the way could actually be solved by oneself bothering to read up more on so many documentation online I really can't help bringing myself to be rather disappointed altogether.

[Bhaal1]

Hi All,

I've been working on a simple GUI wrapper around the miner to monitor it in a more user-friendly way and to restart the miner automatically if the hashrate drops below a specified amount.  I'm sure there's lots of bugs (very little validation in the GUI), but it might be useful for some of you.

https://github.com/anadventureisu/cast-xmr-ui

https://i.imgur.com/wpSvkSL.png

so how do i install it?

You have to compile for yourself... I did it and it works like a charm.

I have one questions which is not quit clear to me... If i check nicehash in the GUI...is it then allowed or disabled?

Cheers

[dragonmike]

I've got a bit of a weird issue...
One of my six Vega56 flashed to 64 is hashing at 120h/s slower than the other 5. At first, I thought it was the one with the dummy plug in, but I switched the plug to another card and it's still that same GPU3 that's hashing slower... The other ones hash on avg at 1970 h/s, GPU3 does 1850.

They're all clocked the same (1025@1V iirc) and temps are in the low 60's.

Any ideas (apart from the card being inferior)?

[Cyan_Antares]

I've got a bit of a weird issue...
One of my six Vega56 flashed to 64 is hashing at 120h/s slower than the other 5. At first, I thought it was the one with the dummy plug in, but I switched the plug to another card and it's still that same GPU3 that's hashing slower... The other ones hash on avg at 1970 h/s, GPU3 does 1850.

They're all clocked the same (1025@1V iirc) and temps are in the low 60's.

Any ideas (apart from the card being inferior)?

Vegas 56 are awesome. I'd check if it's a raiser issue. Bad raisers can cause certain problems, one of them being that a card could perform more slowly than others. However I wouldnt bother with them seeing that the difference is "small", imho. Btw, have you tried to decrease the temperatures?

[syncro2017]

I just managed to buy one Vega 56! Can't wait to get it delivered

[neogeo]

Just an update on my previous posts, after about an hour playing with different intensity settings in xmr-stak i was able to achieve 95% of the hash rate that cast-xmr gives me

Play as i am and reach a heaven:
my settings for example

               "threads": 2,
               "rawintensity": 944,
               "worksize": 8

When "threads: 1" then "rawintensity: 1888" but better results You will have with threads:2...
Play with settings.

[anadventureisu]

so how do i install it?

There's a releases page.  You can download the ZIP and extract it somewhere (e.g. Desktop).  Just double-click cast-xmr-ui.exe after that.

If you have any more issues, please feel free to open a ticket on GitHub.

[anadventureisu]

I have one questions which is not quit clear to me... If i check nicehash in the GUI...is it then allowed or disabled?

Cheers

Allowed.  Checking "Use NiceHash Nonce" adds the --nicehash option to the command line to enable NiceHash.

Note, I have binary releases on the releases page too.  Star the project to get notified of new versions.  Working on integrating the driver restart that devcon.exe does!

[dragonmike]

I've got a bit of a weird issue...
One of my six Vega56 flashed to 64 is hashing at 120h/s slower than the other 5. At first, I thought it was the one with the dummy plug in, but I switched the plug to another card and it's still that same GPU3 that's hashing slower... The other ones hash on avg at 1970 h/s, GPU3 does 1850.

They're all clocked the same (1025@1V iirc) and temps are in the low 60's.

Any ideas (apart from the card being inferior)?

Vegas 56 are awesome. I'd check if it's a raiser issue. Bad raisers can cause certain problems, one of them being that a card could perform more slowly than others. However I wouldnt bother with them seeing that the difference is "small", imho. Btw, have you tried to decrease the temperatures?

Ah yes... The risers... Wait... I've got an Onda D1800!

Nah temps are fine. All cards are very closely matched.

Maybe this specific card is just running at its max for that voltage. I might try just increasing that one a notch and see what happens.

Do you know if Cast XMR uses the same GPU number as OverdriveNtool?

[StellarX88]

I've got a bit of a weird issue...
One of my six Vega56 flashed to 64 is hashing at 120h/s slower than the other 5. At first, I thought it was the one with the dummy plug in, but I switched the plug to another card and it's still that same GPU3 that's hashing slower... The other ones hash on avg at 1970 h/s, GPU3 does 1850.

They're all clocked the same (1025@1V iirc) and temps are in the low 60's.

Any ideas (apart from the card being inferior)?

Vegas 56 are awesome. I'd check if it's a raiser issue. Bad raisers can cause certain problems, one of them being that a card could perform more slowly than others. However I wouldnt bother with them seeing that the difference is "small", imho. Btw, have you tried to decrease the temperatures?

Ah yes... The risers... Wait... I've got an Onda D1800!

Nah temps are fine. All cards are very closely matched.

Maybe this specific card is just running at its max for that voltage. I might try just increasing that one a notch and see what happens.

Do you know if Cast XMR uses the same GPU number as OverdriveNtool?

I only have 2 cards set up at the moment and Cast-Xmr is indeed mirroring overdriveNTool GPU number. Could be a 50 50 flux.

[ntshb]

I have some issues with the vegas not hashing as expected across 2 -3 miners. Hope someone can help

I use this script (http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html) for 2 miner PCs but 1 of them (4x vega64s), only 2 vegas hash at around 1970~, the remaining 2 hash at 1600+h/s .

the other PC (5x vega 56 at stock bios) hashes at only 1400-1500h/s.


I've reset the vegas in both PCs but it doesnt improve.


has anyone tried the JJ's script and hash monitor to automatically reset if the hashrate drops?

Not sure if you ever read the entire thread, I have shared my modified version here albeit at an older JJ version & Cast version. Feel free to update it to latest one accordingly.

https://bitcointalk.org/index.php?topic=2256917.msg25631033#msg25631033

thanks

So all I have to do is edit

$vidTool += 'OverdriveNTool.exe -r1 -p1Vega64' # Expects to be in same folder as this script

and

$global:CAST_XMRcmdline = "-S cryptonight.hk.nicehash.com:3355 -u 1C58yRKSf1ctSKBpP9FrSrDTjzYaRPPumD.VegaLuno -G 1 --remoteaccess"   # CAST_XMR arguments. Not required, REMARK out if not needed


Can i remove the remoteaccess part?

You will need the remote access part for the hash monitor to work.

I think the following link should be more updated to v2.9.

https://drive.google.com/open?id=1TnicWxpB1TtGQCe_cuXND8ha-XsgQsU1

I have detailed my change log inside, you will also most likely need to define the minimum vega hashrate for a restart for your case (I use 1 card so it's a simple 1750000, for your simple use case you can multiply it with the number of cards you have, or if you prefer a restart by checking each card individually).

If you need it to be tweaked somewhat specifically on a per card basis, I can see about modifying the script to fit your use case. Hit me up on Skype (mo.jin.ee) if you would like to do so.

I've edited the settings to

$vidTool += 'OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Vega64 -p2Vega64 -p3Vega64 -p4Vega64'

$global:CAST_XMRcmdline = "-S pool.supportxmr.com:7777 -u walletaddress.Vega64-3 -G 0,1,2,3 --remoteaccess"

as long as I change these 2 lines that;s fine right?

  why is the hashdiff so high? i mean vegas are hashing at 2000 per card?

You will know why if you ever bother reading through the changelog that I have detailed together with the modified JJ Hash Monitor script, or if you happen to read up more on Cast-XMR monitoring result port comparison on the very guide that Circus Dad has put together comparing xmr-stak vs cast-xmr : http://vega.miningguides.com/p/castxmr-vs-xmrstak.html

I really don't want to be cynical when it comes to the community helping each other, but when almost every single help that comes the way could actually be solved by oneself bothering to read up more on so many documentation online I really can't help bringing myself to be rather disappointed altogether.

thanks for your help

[ntshb]

I have some issues with the vegas not hashing as expected across 2 -3 miners. Hope someone can help

I use this script (http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html) for 2 miner PCs but 1 of them (4x vega64s), only 2 vegas hash at around 1970~, the remaining 2 hash at 1600+h/s .

the other PC (5x vega 56 at stock bios) hashes at only 1400-1500h/s.


I've reset the vegas in both PCs but it doesnt improve.

[ntshb]

\i seem to be drawing more power with cast xmr than xmr stak

853w for 4 vega 64 (1325/1025mhz 925/900mv) on cast xmr compared to 1000w for 6 cards for xmr stak

[bytiges]

Let's do a poll regardin Aftermarket Vega56 / Vega64 :

Type of Card using ?
What rate are you getting?
What memory does the card have ?
What is your P7 (GPU) and P3 (Memory) Voltage / Frequency ?

[Kapz786]

Anybody tried this with Radeon Rx 580?

For me, I get a lot of errors and there is a big difference between the reported hashrate (1400 H/s) and the one noted by the pool (950 H/s).

Any way to make this work with the Rx series?

This is the best mining software I have found for a bios modded RX 580. Got me about 20% more than STAK XMR

[Bhaal1]

I have one questions which is not quit clear to me... If i check nicehash in the GUI...is it then allowed or disabled?

Cheers

Allowed.  Checking "Use NiceHash Nonce" adds the --nicehash option to the command line to enable NiceHash.

Note, I have binary releases on the releases page too.  Star the project to get notified of new versions.  Working on integrating the driver restart that devcon.exe does!

Thanks

[syncro2017]

Just an update on my previous posts, after about an hour playing with different intensity settings in xmr-stak i was able to achieve 95% of the hash rate that cast-xmr gives me

Play as i am and reach a heaven:
my settings for example

               "threads": 2,
               "rawintensity": 944,
               "worksize": 8

When "threads: 1" then "rawintensity: 1888" but better results You will have with threads:2...
Play with settings.

Same here, even with RX 570 im getting around 30-50 h/s higher with 2 threads! keep on tuning

[commonorx]

Just an update on my previous posts, after about an hour playing with different intensity settings in xmr-stak i was able to achieve 95% of the hash rate that cast-xmr gives me

Play as i am and reach a heaven:
my settings for example

               "threads": 2,
               "rawintensity": 944,
               "worksize": 8

When "threads: 1" then "rawintensity: 1888" but better results You will have with threads:2...
Play with settings.

Same here, even with RX 570 im getting around 30-50 h/s higher with 2 threads! keep on tuning

Oh I thought this was the CAST XMR thread.