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

Try --opencl 0 or 1 or 2 then use the -G command to assign the GPU's you want to use example -G 0,1,2,3

Hi guys, I tried to run the software but every time I launch it tells me I do not have the block chain drivers but I do..

Cast doesnt take directly 1.5% of your earnings, but nanopool does.

1.5% fee to Cast dev .
1.0% fee to Nanopool
2.5% total
Example:
If i earned $1,038/month ,, $27  goes to  cast+nanopool
right ?

vega 56 = 3 x rx470

hi
    ive got a multiple card rig with one vega 56 in it anyway of telling the miner to only use  the vega card

 many thanks

I did a little research and it seems that when Windows apps write to stdout on the console it's line-buffered and when they write to a stream/file they use a larger buffer (looks like a couple kB).  I PM'd Gandalph to see if he'd publish a tweaked build with a few flush() commands in there.  Once he does that we can scrape the output and wrap it with a GUI/websvc.

 No.

 It's an issue with how Nicehash works - your hashrate gets switched to a different user fairly often and any work that was "in process" at that point automatically becomes outdated when the switch happens.

Try it like this:


If this works feel free to change the address.

what im doing wrong?

cast_xmr-vega.exe -s stratum+tcp://pool.electroneum.space:3333 -u wallet

and getting erro about no pool server or username configured

Found a 0% (for now) fee pool and using it with a fixed diff reduced the outdate shares from 4% to 2% or less. I had a request for info on the pool chart and the developer emailed back in what I would consider record time for support of such a miniscule request. I am impressed.

Pool fee is at 0% and will remain there until certain conditions are met. Well documented on site.

https://moneroocean.stream

Very nice software. But it's just up ahead. There is something you can do for both performance and additional settings. I used it for Vega. I started using other software unwillingly because I could not intervene as much as I wanted.

I'm following...

no  but i had burn some rx470 like that too, after i restart ring  some fire came out the card, 1 after 2 week, an other after a big month
already send 4 x 470 back  on a total of  12 sapphire 470's

1 was still working but smell burn (got repaird)
1 got fire at the 6pin power connector (currently in rma)


i notice on the vega56   msi, sapphire,gygabyte .. the gpu's are exactly the same except the sticker , are they exactly the same ? maybe manufactured in the same place lol



is there a topic where people share they dead gpu's ?

because it s look like i m unlucky or is it just normal so much dead gpu's?

i have  4msi 270's (3years old) all fan are dead (i replace each 1 fan with my dead 380's fan), 1gpu died 4month ago

my 380's  more than 2 years old
have 5 asus 380's  1 dead (powersupply won't start)
6 sapphire 380's (2 dead, 1 money back in warranty after 11month)
6x xfx 380's (none dead but 3 gpu have 1 fan (spin at start but don't spin in windows, unless you put fan at 100%, this happen after i clean the gpu with air , did they spin to fast?now i always hold the fan so it don't spin)

5x 570's sapphire  all fine (less than 1 year)
5x 560  all fine too

5 vega all fine now but i notice i have a bad one, use more power and memory won't past 890 without error

ha yes i forgot also have  5x gtx 1060 3g  ino3d (less than a year old)  1 dead currently in rma

One of my 1 week old vega 64 MSI cards died this morning. I had thermal max set to 75C with a target of 70C. The card that died was always, from day one, running about 800RPM faster fan speed than the other 3 I have (2 MSI, 1 Sapphire) just to keep the temps the same. As the week progressed I noticed that the fan speed gradually continued to increase  from 2800RPM - 3300RPM. The other cards ran about 2300RPM at 69-70C consistently.

Last night at about 12:30AM the mining rig shutdown. When I woke up I went down stairs to see what was up. I could see nothing wrong, looking the machine over, everything appeared to be fine. Pushed the power button and witnessed a flame burst out of that card that was running hotter from day one.

Freaking crazy! Anyone else seeing issues with Vega64 cards like that?

Also what does this mean for Avg Search Time???

[10:23:54] Shares: 65 Accepted, 0 Errors | Hash Rate Avg: 4022.8 H/s | Avg Search Time: -1275.3 sec

So I noticed this morning that the the 8hr pool report was exactly the same as last night. Odd! So I shut down Cast and proceeded to tune XMR-STAK. It took me about an hour to get it up due to dll issues and a neighbor visiting. And then there was about two hours of up and down tuning intensities. I am using a blanket of 1928 on all the 56s and 64s and it is solid for an hour at 11950 h/s and with xmr stack also using half the cpu those 50 are added to the GPUs. So all and all I should be 0.5% ahead due to dev fee reduction from 1.5 to 1. I am sure the 64s have some left in them but I will wait a bit to squeeze the last few h/s out of them. Probably won't mess with it until I add two more cards to the rig.

Oh and the pool 8hr report it still stuck with no hashes in the last 4.5hrs on that pool


So far I am impressed with XMR-STAK. Easy to tune if you make the time to do it. Multi-pool failover! API! LOG!

пoдcкaжитe ктo знaeт кaк в бaтникe пpoпиcaть пapoль чтoб зaйки в нacтpoйки нa xmr.nanopool.org и выcтaвить cyммy вывoдa, тaк кaк пo yмoлчaнию cтoит 1 XMR, этo oчeнь дoлгo. A бeз пapoля oн нe измeняeтcя пишeт нeпpaвильныe пapoль(нo этo пoнятнo вeдь пapoль в бaтникe нe пpoпиcaн) Зa paнee cпacибo.!

Hmmm

I do see the wild swings in cast, but the long terms are always 11900 to 12150 on the pool. Current 8hr is 12.15 and has been since it recovered from 11.7 due to me adjusting some router setting and knocking the miner off line for a little while this afternoon.

I have XMR Stak ready to fire up and have had for over a week, but Cast has been performing to well to change right before the holiday. Ever since I starting using autohotkey to send an "s" to print status once an hour all the cast hangs and hiccups have stopped. My 6 Vegas are always running around 12015h/s and I can see no reason to think there is an issue with the pool data agreeing.

I will see about running XMR STAK in a couple of weeks when another two Vegas arrive. So far the two time I started it it crashed, because I tried to just copy others intensities off the net and I didn't have time to tune it on that day.

I would recommend testing a week or so with this and same with XMR-Stak.  My hash rate was 11600 (6 vegas) in CAST and 11200 in XMR-Stak. 

However my results on my pool (supportxmr) where the following:

Cast - 10.7 average over the week.
XMR-Cast 11.3 average over the week. (I ran at 1% fee as well)

I also noticed my graph was much more "steady" with XMR-Stak, with much less huge dips than with Cast.  I'm not sure if its just me, but something seemed off.

A week isn't a HUGE sample size I know, but those results are pretty drastic imho.

I see for russian gaid Vega 56 monero best result 1970 Mh https://www.youtube.com/watch?v=TuU3bcLcU_M All settings in file archive

you need to change your opencl flag to either 0, 1, or 2, etc.  This has been mentioned quite a bit in this forum/thread