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

[Jo82]

How do i choose Sumokoin in 9.6?

[Sharpeich]

How do i choose Sumokoin in 9.6?

--algo=2

[Jo82]

How do i choose Sumokoin in 9.6?

--algo=2

thnx man,
mining on Fairpool, 6kh during 2h30 only getting 0.5495 sumo
i should get 0.34 sumo per hour...
anyone has the same problem?

thnx

[glph3k]

Hi,

Cast XMR version 1.0 is available.

Now CryptoNight Lite variants are supported. Lite coins like Aeon, IPBC and Turtle.

With the Lite algo higher hash rates can be achieved as it only uses an 1 MB scratchpad.

Following hash rates should be reachable.

RX Vega 56/64: 4250 Lite Hashes/s
RX 470/570/480/580: 1600 Lite Hashes/s

Use the --memset option to squeeze some extra hashes. It was enabled by default in the 0.9.7 version, now it is default disabled. It is probably only recommendable if a hash rate monitor is used to reset the GPU if an hash rate is drop is detected. Btw. from my observations the 18.3.4 drivers seem more resilient against hash rate drops then the legacy blockchain beta drivers.

Regards,
Glph3k

Cast XMR Version 1.0.0 (2018/4/24)

- Support for Aeon (AEON) CryptoNight Lite variant set --algo=3 to mine
- Support for Turtlecoin (TRTL) CryptoNightV7 Lite variant set --algo=4 to mine
- Support for Interplanetary Broadcast Coin (IPBC) CryptoNight Lite IPBC variation set --algo=5 to mine
- Up to 3% performance improvement with new option --maxmem to allocate the maximum memory of the card. For Vega cards the "HBCC Memory Segment" has to be disabled in the Radeon Settings to use the option. Disadvantage is a higher risk of hash rate drops when the --maxmem option is used.

Download Cast XMR 1.0.0 for Windows (64bit)

SHA256 hash of cast_xmr-vega-win64_100.zip:
fab141ce2b3e3b32636fedfc242e9b91edc21317e108fb361368570694dd338e

[Rackam74]

- Up to 3% performance improvement with new option --maxmem to allocate the maximum memory of the card. For Vega cards the "HBCC Memory Segment" has to be disabled in the Radeon Settings to use the option. Disadvantage is a higher risk of hash rate drops when the --maxmem option is used.

And if we didn't install the Radeon Setting? I use one of the lastest driver (around 18.3.2).

[glph3k]

- Up to 3% performance improvement with new option --maxmem to allocate the maximum memory of the card. For Vega cards the "HBCC Memory Segment" has to be disabled in the Radeon Settings to use the option. Disadvantage is a higher risk of hash rate drops when the --maxmem option is used.

And if we didn't install the Radeon Setting? I use one of the lastest driver (around 18.3.2).

With Radeon Settings the AMD Adrenaline Radeon Settings is meant, the icon with the red balls circling around.

The "HBCC Memory Segment" is an option in the "Global Graphics" tab. I am not aware of another tool that can toggle the HBCC memory option, anyone?

If not the improvement is not dramatic and the stability is really worse then without the option... but if you like give it a try maybe it works for you.

Regards,
glph3k

[zeef]

Hi guys,

With new amd drivers , using vega 56 ref card i cant use overdriventool.. im stuck with wattman. But when something goes wrong the radeon settings apply the default setting. 

How can we workaround this?

How can we force the wattman to run our profile at startup, instead of manual?y

Thanks

[Nss75]

Hey guys!
What is the max hashrate for vega 64 mining haven (heavy CN)?

Just to be sure ; )

[Rackam74]

@glph3k,
I know that you mean... but i've installed only the driver, so i don't have any setting.... but still a good job, 9.8 kh/s (stable) with 5 vegas !!

[duyquang06]

Hi,

Cast XMR version 1.0 is available.

Now CryptoNight Lite variants are supported. Lite coins like Aeon, IPBC and Turtle.

With the Lite algo higher hash rates can be achieved as it only uses an 1 MB scratchpad.

Following hash rates should be reachable.

RX Vega 56/64: 4250 Lite Hashes/s
RX 470/570/480/580: 1600 Lite Hashes/s

Use the --memset option to squeeze some extra hashes. It was enabled by default in the 0.9.7 version, now it is default disabled. It is probably only recommendable if a hash rate monitor is used to reset the GPU if an hash rate is drop is detected. Btw. from my observations the 18.3.4 drivers seem more resilient against hash rate drops then the legacy blockchain beta drivers.

Regards,
Glph3k

Cast XMR Version 1.0.0 (2018/4/24)

- Support for Aeon (AEON) CryptoNight Lite variant set --algo=3 to mine
- Support for Turtlecoin (TRTL) CryptoNightV7 Lite variant set --algo=4 to mine
- Support for Interplanetary Broadcast Coin (IPBC) CryptoNight Lite IPBC variation set --algo=5 to mine
- Up to 3% performance improvement with new option --maxmem to allocate the maximum memory of the card. For Vega cards the "HBCC Memory Segment" has to be disabled in the Radeon Settings to use the option. Disadvantage is a higher risk of hash rate drops when the --maxmem option is used.

Download Cast XMR 1.0.0 for Windows (64bit)

SHA256 hash of cast_xmr-vega-win64_100.zip:
fab141ce2b3e3b32636fedfc242e9b91edc21317e108fb361368570694dd338e

Thank for hard working !!!!!

[Aris_Eng]

- Up to 3% performance improvement with new option --maxmem to allocate the maximum memory of the card. For Vega cards the "HBCC Memory Segment" has to be disabled in the Radeon Settings to use the option. Disadvantage is a higher risk of hash rate drops when the --maxmem option is used.

And if we didn't install the Radeon Setting? I use one of the lastest driver (around 18.3.2).

With Radeon Settings the AMD Adrenaline Radeon Settings is meant, the icon with the red balls circling around.

The "HBCC Memory Segment" is an option in the "Global Graphics" tab. I am not aware of another tool that can toggle the HBCC memory option, anyone?

If not the improvement is not dramatic and the stability is really worse then without the option... but if you like give it a try maybe it works for you.

Regards,
glph3k

Thanks for the update. I have been putting it through its paces, and so far, using blockchain drivers on vega64, devcon (to switch off HBCC) and memory timings, I am getting 2030H/s per vega, no stability issues on cryptonight.

I'll start trying crytponightv7 and cryptonight_heavy soon.

[coke15]

hi

still have the same prob with 1.0: cast stop hashing,not hanging but power at 100%     no hbcc, --memmax
when i close cast,rig reboot.

you say" drop hash" reset card,maybe it"s that?

somebody has the problem with blochain driver and regmod?

[Nss75]

Well tell us your hashrate on CN heavy with vega 64.

I get around 1500-1600h/s per vega 64 mining haven.
I can share my settings if needed.

Thanks to you gandalf,  i just get a low drop  (from 9700 to 9200) with 6 vegas 64 on heavy CN: your software rocks.

[Sharpeich]

Thanks for the update. I have been putting it through its paces, and so far, using blockchain drivers on vega64, devcon (to switch off HBCC) and memory timings, I am getting 2030H/s per vega, no stability issues on cryptonight.

I'll start trying crytponightv7 and cryptonight_heavy soon.

if crytponightv7 shows 2030H/s then +3% with --memmax should result with unbelievable 2100H/s ! but i never saw those numbers on my vega64

[chup]

Thanks for the update. I have been putting it through its paces, and so far, using blockchain drivers on vega64, devcon (to switch off HBCC) and memory timings, I am getting 2030H/s per vega, no stability issues on cryptonight.

I'll start trying crytponightv7 and cryptonight_heavy soon.

Do You mind explaining how to use devcon for HBCC switch off and memory timings on Vega?

[rednoW]

Thanks for the update. I have been putting it through its paces, and so far, using blockchain drivers on vega64, devcon (to switch off HBCC) and memory timings, I am getting 2030H/s per vega, no stability issues on cryptonight.

I'll start trying crytponightv7 and cryptonight_heavy soon.

if crytponightv7 shows 2030H/s then +3% with --memmax should result with unbelievable 2100H/s ! but i never saw those numbers on my vega64

No problem getting 2100k/s with vega64 and samsung mem

clocks are 1408/1140@875mv, rock stable.
first card is vega56 flashed to 64
And sorry 2 srb doctor, I'm greedy bastard sometimes ))

[carlosmonaco]

Thanks for the update. I have been putting it through its paces, and so far, using blockchain drivers on vega64, devcon (to switch off HBCC) and memory timings, I am getting 2030H/s per vega, no stability issues on cryptonight.

I'll start trying crytponightv7 and cryptonight_heavy soon.

if crytponightv7 shows 2030H/s then +3% with --memmax should result with unbelievable 2100H/s ! but i never saw those numbers on my vega64

No problem getting 2100k/s with vega64 and samsung mem
https://i.imgur.com/8pQa0Zr.png
clocks are 1408/1140@875mv, rock stable.
first card is vega56 flashed to 64
And sorry 2 srb doctor, I'm greedy bastard sometimes ))

Can u share your PP TABLES ? I'm stuck around 1800h/s

[rednoW]

Thanks for the update. I have been putting it through its paces, and so far, using blockchain drivers on vega64, devcon (to switch off HBCC) and memory timings, I am getting 2030H/s per vega, no stability issues on cryptonight.

I'll start trying crytponightv7 and cryptonight_heavy soon.

if crytponightv7 shows 2030H/s then +3% with --memmax should result with unbelievable 2100H/s ! but i never saw those numbers on my vega64

No problem getting 2100k/s with vega64 and samsung mem

clocks are 1408/1140@875mv, rock stable.
first card is vega56 flashed to 64
And sorry 2 srb doctor, I'm greedy bastard sometimes ))

Can u share your PP TABLES ? I'm stuck around 1800h/s

My PP tables won't help you as they are very specific for liquid bios and old blockchain drivers.
But it is easy to get the same result using latest 18.3.4 driver and softpowerplay mod with overdriventool (based on your own bios).
Just make it work with clocks and volts I posted above and don't forget about good cooling. You need to keep your temps low for HBM2 on such high clocks

[carlosmonaco]

Thanks for the update. I have been putting it through its paces, and so far, using blockchain drivers on vega64, devcon (to switch off HBCC) and memory timings, I am getting 2030H/s per vega, no stability issues on cryptonight.

I'll start trying crytponightv7 and cryptonight_heavy soon.

if crytponightv7 shows 2030H/s then +3% with --memmax should result with unbelievable 2100H/s ! but i never saw those numbers on my vega64

No problem getting 2100k/s with vega64 and samsung mem

clocks are 1408/1140@875mv, rock stable.
first card is vega56 flashed to 64
And sorry 2 srb doctor, I'm greedy bastard sometimes ))

 

Can u share your PP TABLES ? I'm stuck around 1800h/s

My PP tables won't help you as they are very specific for liquid bios and old blockchain drivers.
But it is easy to get the same result using latest 18.3.4 driver and softpowerplay mod with overdriventool (based on your own bios).
Just make it work with clocks and volts I posted above and don't forget about good cooling. You need to keep your temps low for HBM2 on such high clocks

I tried my best ^^ I'm using reference card 56 with 64 bios.
OverdriveNtool is not working with 18.3.4 and I can't run above 1090 even on old driver. ( this is the same for all my card (20 cards))

[rednoW]

I tried my best ^^ I'm using reference card 56 with 64 bios.
OverdriveNtool is not working with 18.3.4 and I can't run above 1090 even on old driver. ( this is the same for all my card (20 cards))

OverdriveNtool is working like a charm with newest drivers.
Here is a screen of my Sapphire Pulse Vega56 with shitty hynix mem mining cryptonight-heavy @ 140watt