Topic: [ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More - page 149. (Read 211877 times)

Yes, me too.

Oh my, that's the current official record I think! I haven't run my Vega64 LC at higher memclk than 1105 though, I should probably try it!

Whenever the vards initialize or not, the miner works super nice from what I have seen so far. I am busy all day optimizing my rigs for this miner. If some cards don't initialize, miner still works, just displays 0h/s for that card, and CPU usage is high, so he is probably stuck trying to initialize the cards or something.
Then, i just quit the miner and try few times and eventually all cards initialize.

I have 8 vegas and celeron 847, No matter how many times restart, can only start 6 cards. 

Done a quick test from release until now, so its about half a day. But haven't optimized anything yet.

Until now: Great job, thank you!

Vega64 LC
Adrenaline 18.6.1, Latest Win10
GPU 1700/1050, Memory 1140/960
Just the standard --cn_config 16+14
Less Power than SRB which is nice, but much more Speed: 2380-2400 per card

This was a big investment time-wise, we had to build all the support for CN stratum mining etc, so it’d be very unwise for us to not add more variants . We might also add an algo switching scheme, but haven’t decided yet.

Will be back at my desk shortly and will provide better feedback. Meanwhile, can you describe the behavior those times you’re lucky and all cards initialize ok, does mining work fine after that in those cases?

I think we need to add an option of doing a staggered initialization and a delay, that no card starts mining before the full init process has completed.

The miner is actually missing on-cpu verification, we didn’t have time to add it, so that’s not the issue at least .

          Team Red Miner version 0.3.4
[2018-10-30 15:25:55] Pool gin.f2pool.com successfully subscribed.
[2018-10-30 15:25:55] Pool gin.f2pool.com authorization succeeded.
[2018-10-30 15:25:55] Pool gin.f2pool.com set difficulty to 15.999756
[2018-10-30 15:25:55] Pool gin.f2pool.com received new job. (job_id: aKXuutTIJS)
[2018-10-30 15:25:55] Successfully initialized GPU 0: Vega with 56 CU (PCIe 10:00.0)
[2018-10-30 15:25:55] Successfully initialized GPU 1: Vega with 56 CU (PCIe 0d:00.0)
[2018-10-30 15:25:55] Dev pool connected and ready.
[2018-10-30 15:25:55] Successfully initialized GPU 2: Vega with 56 CU (PCIe 09:00.0)
Segmentation fault


i just upgrade amd-gpupro driver from 18.10 to 18.30 on hiveos(ubuntu 16.04.5),then start like above

@kerney666 very good job  
Just tested under Hive OS (drivers 18.10) on rx 480 4gb (elpida) 1250/950 1950/950 hashrate is 990 - 1000 depend on the card.
Do you plan to add other CN variants like arto, stellite and others? If yes could you add algo switching like SRBminer?

turn off hbcc... it's probably recognizing it has gfx901.

Same problem here,2-3 cards starts even a g4560 cpu with  polaris series. No problem with vegas...

hi,
yes, i have tried that. Did not work either.

Have you tried this ?

--platform=1

Guys,

I need help.


My mining rigs are riserless motherboards with 7x vega.

These boards have Celeron 3885 CPU that appears to be very slow.

When the miner starts, it in parallel initializes each card and connects to the pool. But once the shares start coming, the CPU is busy with something (probably verifying the found shares?) and never completes initialization of some cards. Sometimes 3 cards start, sometimes 6 cards start, sometimes all 7. But I have to manually stop and start the miner many times until I get lucky and initialize all 7 cards.

Is it possible to introduce some delay between card initialization and mining start, or disable CPU share verification?


Thanks!

hi,

im not able to get it to work with my vega64 or 8x vega56.
on both rigs i get the same error message “Failed to initialize device number 0.”

ive tried using -d 1, but then the error becomes device 1 is out of range.

any ideas on what to try next?

edit forgot to mention im on win 10 and 18.6.1 drivers

Thank you it works now with this tip.

Fantastic jobs guys!
You have completely eliminated the drop in profitability that the fork from CN/1 to CN/2 introduced.
4x Vegas making 8000+ h/s @ 840W

Cheers!

Baz

Mining directly to exchange does not work as you have to specify payment id. Miner can't login to nanopool using:
-u address.payment-id.user

However it works using:
-u address.user

Can you fix login to pool with payment-id included so i can mine directly to exchange?

Thank you.

Thanks for helping with the early testing dragonmike!  It really helps to have some outside validation of our numbers as a bit of a sanity check before a release
As for CN variants and other new algos, we will be adding more, but it may be a little while.  This last push to get CNv8 from the drawing board and into production has taken over a month of full time work on both our parts and we both need a bit of a breather after this one.  That said, adding CN variants now that we have the general CN infrastructure in place should be much easier.  We've also done some very initial work on x16r and it looks like there's plenty of room for improvement, but at this point we can't make any promises on what we'll be able to release and when.


Haha, I just spent a couple hours pushing my Vega FE too.  I managed to hit just over 2400h/s running at 1610MHz core and 1195MHz mem clocks!    The card was pulling about 300W alone so not very useful, but I love seeing that 2400h/s readout!


Do you know what type of memory is on your card?
I have some MSI RX470 mining edition cards that have Micron memory and so far I can only get them to about 850h/s with the best straps I could find.


Thanks vmozara!  Nice to see someone else out there pushing the higher 2300+ hashrates 
As for the driver version, we have done most of our testing on 18.6.1, so I would consider that the safest bet.  I believe kerney saw some issues with Vegas running the old blockchain drivers, so I would avoid those for Vegas.


Thanks for helping with the early testing N2DCRYPT!  We really appreciate you taking the time to kick the tires before the release!
Also I'm glad we could help get your rigs back into their old power profiles


Thanks dafuzz_rsa!  We're looking forward to cranking out some new algos after we take a little bit of a breather

Vmozara, the Adrenalin 18.6.1 drivers should work well; and that's what I'm running on all of mine--anything older than that tends to have problems with v8.