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

I am also mining haven but with 9.6.  I tried the latest version (v 1.0) but was having all sorts of stability problems.  Even upgrading my video drivers to 18.3.4 I still had issues.

Geez, really don’t know what to tell you.  I’ve never mined Sumo, but been mining Haven with little problem, and it also uses Heavy.  Been running Cast v 1.0.

Just an update on this....the only algo I am having trouble with is Heavy, and specifically Sumokoin.  This is universal, across all my machines running Cast.  Have tested both with EasyHash and HashVault with same result.  Anyone have a solution to this? 

It's not XMR_Cast false. My rigs got virus mining ETH....
It show chinese app and using Claymore 9.7 to mining. F*** this shit.

I am getting the error "Share Rejected - Unauthenticated" after running fine for several hours on the latest version.  I lost 173 found shares before I discovered the error (a few hours worth of work).  Since there is no way to reload the pool, I have to quit the program and restart it.  Any idea what causes this error?  Can the program be written to detect when this happens and automatically reload the pool or restart the program?

Hey guys...are you running fixed difficulity? My IP was also banned so I went back to variable difficuity and moved to a different pool...no problems after that....

Same thing with me....  works fine on cryptonightv7 ... but heavy?

I tried the biggest port, same problem: Rejected by the Pool: Unauthorized,  after circa 200 accepted shares. But why?

I use 2 miner rig with the same IP, maybe could it be a problem?

Well i get 18500h/s per vega 64 with the New update lol. Using CN heavy!
Probably à "," bug!

I haven't tried Cryptonight Heavy yet (want to try Haven, after reading AlexanderDumas post), but by the looks of it, it seems related to the fact that you are mining Cryptonight Heavy? It is more computational expensive than CryptonightV7. My 4GB RX 570 is getting around 860H/s on CryptonightV7.

On 1.0, heavy algo, cast suddenly turn off the tool for no reason, switched back to XTL (v7)....

//update : Still force close, idk why, switch back 0.9.6 not help...

even v7 ....

//update: okie on 0.9.2

Sorry, typo...meant =2.  Still not working.

Yes, having the same problem as of version 1.0.0........

Algo is 2, not -2.

Hello Everyone,

I am a fan of Cast XMR, running it on several machines.  I have run into trouble lately with the fork however, beginning with version 0.92.  Most issues I was able to workaround / resolve, but the one remaining issue is using the CryptoNight-Heavy algo (Sumokoin).  With version 0.96, I was able to manually set the algo using =-2.  Hashrates were low, however, hovering in the 1500 KHash/s range.  When I upgraded to 1.0.0, Cast seemed to disregard the flag (at least there was no confirmation on startup it was using the Heavy algo) and immediately generated a socket error when trying to connect to the pool (on Hashvault, it tells me there has been a fork and that I should be using a different miner).  I have been able to reproduce this issue on several machines with no apparent workaround. 

Anyone have a solution to this issue or do we need to wait until the release of the next version?

Thanks in advance,
Fox

hi , can you share yours vega 56 softpowerplay settings ?
with stock bios vega 56 , i can do better than 1300hs rate in haven mining
i use the softpowerplaytable found on this guide http://vega.miningguides.com/#SoftTables

Hey all,

Just wanted to say thanks for making this software.....I have tried using the latest version (1.0.0) but have been unable to get it to work smoothly..Went back to the previous version of 9.6 and that seems to work ok...some small problems I am looking for some help with:

1)  In my rig I have seven RX470 (8gb hynix) and one RX570 (4gb hynix).  I am unable to get the RX570 to hash above 680 h/s.  I bios modded the card with polaris one-click and am using the stock clock settings of 1200 and 1950. Changing the clocks have no effect on the hash rate. I am getting about 800 h/s on my RX470's.  Currently I am mining haven with cryptonight heavy (algo=2).  What am I doing wrong with my RX570?  Here is my command line sequence:

cast_xmr-vega -S haven.ingest.cryptoknight.cc:5533 -u hvxxxxxxxxxxxxxxx.248000 --algo=2 -G 0,1,2,3,4,5,6,7 --ratewatchdog --forcecompute (note using static difficulty).

2)  When I test each of the the RX470s I am getting about 830 h/s but when running all together I'm getting 800 h/s.  Any idea why?  Anyway to fix this?

3)  One suggestion..please, please in the next edition have a fixed location for the temperature and fan speed.  This is really a hassle trying to track down temperature and fan speed when the information is moving target on the screen.

4)  Are there any other commands that are user accessible?  For example intensity? Power?  

Thanks...

Radman

Usually, a banned IP means your hashrate is too high for the port you’re connected to.  Try going to the next higher hashrate port on the pool.

937mV and it keeps stable?

Do you use some specific Mem. Timings? And at what Voltage do you run these cards? I still can't get near to 800H/s @ 1250/2020 (running @ 975V)
[/quote]

Yes, custom timings and that's what makes it reach 800. I haven't optimized it for voltages yet but they all run around 937mV.