Author

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

full member
Activity: 196
Merit: 100
Hi guys,
Is there any command how to avoid of using integrated gpu?
Because of this, I am unable to run this program. Its keep saying no blockchain detected and so on.
Thank you!
--opencl selects the cl index to use. try 0 1 2 3 4 etc.
member
Activity: 275
Merit: 11
Hi guys,
Is there any command how to avoid of using integrated gpu?
Because of this, I am unable to run this program. Its keep saying no blockchain detected and so on.
Thank you!
member
Activity: 75
Merit: 10
Cast XMR - Highspeed CryptoNight (Monero/Bytecoin/DigitalNote/Intense) Miner for Radeon RX Vega GPUs

For the next version on Windows, would it be possible to have some way of listing identifying information about the cards assigned to 'GPUx'? This could be done with the device property 'Driver key' (Registry entry) or Bus position. Even if it was in some keypress menu vs regular output, it would be helpful.

It seems that each program has its own enumeration, and it doesn't seem that 0, 1, 2, etc correspond specifically to any other enumeration. Windows Device manager has an order that seems to differ from Wattman, which differs from OverdriveNTool, etc.

I agree it's not Cast's job, but would be a godsend for troubleshooting.
full member
Activity: 162
Merit: 100
It's not possible to work the miner on Vega with Claymore 10.2 on 7970 ?

It say BLockchain driver not detected.
WIthout 7970 it work.

I think the combo is not possible ?


Use this on Vega :
cast_xmr-vega -I 9 --opencl 0 -G 1 -S cryptonight.eu.nicehash.com:3355 -u xxx.Vega  --nicehash %*

and this on 7970

-xpool stratum+ssl://cryptonight.eu.nicehash.com:33355
-xwal xxx.7970
-xpsw x
-di 1
newbie
Activity: 28
Merit: 0
Hello guys, Im running vega56 on latest amd driver 17.10.3. The hashrate in eth is good - about 43mh but i could not reach more than 1100h/s in xmr...
I also noticed that GPU Workload feature is missing in radeon settings. Then how can I enable this option?
Hi, this option is not supported for vegas. Not yet. I did not find this option too.

Thanks! I installed blockchain driver aug23. When I started the cast miner the speed was 2000h/s for 5 seconds then suddenly the driver crashed. In the next attempt miner gave "[Suspicious link removed]pute driver not detected!" and the speed almost 1/2 less. I also receive this error when I enable HBCC.
Another issue - core voltage is too high 1.05 - 1.1v. In eth mining I can reduce it to 0.825-0.86mv...    
newbie
Activity: 1
Merit: 0
Help
How to connect to stratum+tcp://  (minergate) pool?
member
Activity: 275
Merit: 11
Hello guys, Im running vega56 on latest amd driver 17.10.3. The hashrate in eth is good - about 43mh but i could not reach more than 1100h/s in xmr...
I also noticed that GPU Workload feature is missing in radeon settings. Then how can I enable this option?
Hi, this option is not supported for vegas. Not yet. I did not find this option too.
newbie
Activity: 28
Merit: 0
Hello guys, Im running vega56 on latest amd driver 17.10.3. The hashrate in eth is good - about 43mh but i could not reach more than 1100h/s in xmr...
I also noticed that GPU Workload feature is missing in radeon settings. Then how can I enable this option?
full member
Activity: 190
Merit: 100

While the general conclusion of this statement is correct, I must disagree on your assessment of the RX 4xx/5xx hashrate.  With Blockchain drivers, modded BIOS, and Samsung memory, you can easily achieve over 925 h/s.
Actually, I'm curious to know how you got 900+ with 580. I never managed to get more than 820h/s, even with my 8Gb Samsung ones. I mine with xmr-stak-amd, two threads per gpu using 512 intensity & 4 workers per thread.

Could you explain a bit more please ?

Youre intensity is too low (512 was good a few month back in sgminer).
Recomended now is 896, but instable for me; I use 872). You can try other values.
full member
Activity: 190
Merit: 100
you should get 2kh/s with vega56 and 2.07kh/s with vega56 with right tuning. 150-160watt.

So what could be the problem that I'm only getting 1300-1400?  I've already tweaked Wattman and the card is running pretty cool.

xmr-stak uses two threads per card, is Cast doing something like that internally and transparent to the user?

Sounds like HBCC isn't enabled, which seems to happen after a system restart. Have you tried resetting your cards within Windows? This always fixes my issues. There's a reference to a Microsoft file called devcon.exe - You have to jump through a couple of hoops to get it, but just follow this (and 'amd64' just means x64).

you don't need HBCC it doesn't do anything. Just deactivate/activate your cards in windows device manager does the trick (driver's buggy).

here's how to automate it: https://bitcointalksearch.org/topic/m.23926484
newbie
Activity: 74
Merit: 0
full member
Activity: 196
Merit: 100
What is the max number of cards right now with blockchain drivers aug23 ? 4, 8 or more ?
full member
Activity: 675
Merit: 100
you should get 2kh/s with vega56 and 2.07kh/s with vega56 with right tuning. 150-160watt.

So what could be the problem that I'm only getting 1300-1400?  I've already tweaked Wattman and the card is running pretty cool.

xmr-stak uses two threads per card, is Cast doing something like that internally and transparent to the user?

Sounds like HBCC isn't enabled, which seems to happen after a system restart. Have you tried resetting your cards within Windows? This always fixes my issues. There's a reference to a Microsoft file called devcon.exe - You have to jump through a couple of hoops to get it, but just follow this (and 'amd64' just means x64).

It's working great now, 1870 H/s on my Vega 56.  HBCC isn't required, nor is 8GB of RAM.  Just disable and enable the GPU using Device Manager after booting.
newbie
Activity: 47
Merit: 0
I have problem, i have 2 rx580 with blockchain drivers installed. First i removed with DDU and then installed the blockchain drivers again from amd website but whatever i do, i cannot get working with miner keep seeing my onboard gpu which is hd 610, and says no blockchain drivers recognised. I cleaned all drivers with DDU, i downloaded older blockchain driver version, updated to recent one, i tried everything but same error again, what should i do? As extra, i tried many altcoin with these cards, only claymores miners are working except for Cryptonight, i tried many algos i can only mine zec and ethereum with dual mining, nothing else is working with my cards, some miners gives me error that no opencl device found even i open with and without --opencl 0. Some of them gives error about hardware monitoring, i connected monitor and disconnected but nothing changes i am really tired of this.
newbie
Activity: 2
Merit: 0

While the general conclusion of this statement is correct, I must disagree on your assessment of the RX 4xx/5xx hashrate.  With Blockchain drivers, modded BIOS, and Samsung memory, you can easily achieve over 925 h/s.
Actually, I'm curious to know how you got 900+ with 580. I never managed to get more than 820h/s, even with my 8Gb Samsung ones. I mine with xmr-stak-amd, two threads per gpu using 512 intensity & 4 workers per thread.

Could you explain a bit more please ?
member
Activity: 75
Merit: 10
you should get 2kh/s with vega56 and 2.07kh/s with vega56 with right tuning. 150-160watt.

So what could be the problem that I'm only getting 1300-1400?  I've already tweaked Wattman and the card is running pretty cool.

xmr-stak uses two threads per card, is Cast doing something like that internally and transparent to the user?

Sounds like HBCC isn't enabled, which seems to happen after a system restart. Have you tried resetting your cards within Windows? This always fixes my issues. There's a reference to a Microsoft file called devcon.exe - You have to jump through a couple of hoops to get it, but just follow this (and 'amd64' just means x64).
newbie
Activity: 8
Merit: 0
Has someone been able to use it with 5-6 gpus? for me it ends up crashing after a few min/secs
full member
Activity: 675
Merit: 100
you should get 2kh/s with vega56 and 2.07kh/s with vega56 with right tuning. 150-160watt.

So what could be the problem that I'm only getting 1300-1400?  I've already tweaked Wattman and the card is running pretty cool.

xmr-stak uses two threads per card, is Cast doing something like that internally and transparent to the user?
member
Activity: 87
Merit: 10
you should get 2kh/s with vega56 and 2.07kh/s with vega56 with right tuning. 150-160watt.

And what is the right tuning for this 150-160watt?
member
Activity: 91
Merit: 29
So I have tried several different pools and no matter what I do I end up getting roughly 5% rejected shares due to expired job.

2 KH - 5% = 1.9 KH

Sort of evens the mining software playing field if you look at it that way.

Has anyone solved the rejected shares problem yet?
Is there a fix in the works?


The problem is system immanent and the outdated shares correlate with the job time which should be 120 seconds for Monero.

As the high hashrate is achieved by the high parallel processing of the hashes, the Vega computes 4000 Hashes at once, so for the outdate shares:

To calculate 4000 hashes with 2000 Hashes per second it takes about 2 seconds for the flight to get the results.

2 seconds round trip time divided by 120 seconds average job time gives an maximum dead time of 1,7%. If the job time decreases the rate will increase but will also decrease when job time goes up.

I see about 2% outdated shares after running 24 hours, which is perfect in line with the prediction.

One idea is to faster cancel the current job if a new job is incoming could have the outdated percentage to less then 1%. Currently evaluating if it has an benefit... maybe in an upcoming version....
Jump to: