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

I have noticed something weird.

I have 4 cards.

1xRX570 4GB Elpida.
3xRX580 4GB, 2 of which Elpida.

The RX570 hashes absolutely the same as the RX580, despite the differences in the CUs.
Both cards are running SAME straps, SAME core clocks, SAME memory clocks.

@TRM Devs - Do you have a discord channel?  

Is there a reference setup for RX574 ?

This is where it gets a little tricky, it depends on how your rig(s) behave on a dead gpu. When I push my Vega 64 on my workstation too hard to test clocks etc I get such a hard hang that I need to cycle the PCIe root hub just to get a prompt back in order to reboot, the gpu looks ok but it's dead. Never had such a hard hang on any other setup. For my Polaris cards on the same workstation, the driver handles the reset just fine by itself and I can just do a simple restart of the miner after setting clocks. So, if I were to handle this with 100% success on this specific workstation with a single script, I would need the hard reset+reboot version.

For the simple use case of a gpu drop that the driver recovers from, I would use two bat files, one that starts the miner with your normal args, then a watchdog restart script with a delay. When the watchdog script is fired, the miner will always shut down as well.

start.bat

watchdog.bat

Remember: to test your watchdog script, add " --watchdog_test" to the command line args. In the case above, that would trigger an endless cycle of restart after ~20 secs of mining.

COOL STORY BRO--

And I don't mean to be insulting, but wading through all these posts leads me to some scepticism.  Back in the day of scrypt mining (2013-2014) there would be reports of impossible clocks for R9 280X cards, clocks high enough to damage the card.

My RX 460 Baffin cards are 4GB Sapphire units, and if I push the mem clock over 1850, they are not stable.  If I could improve the TRM CNv8 hash rate with a better software configuration, I'd like to know how.  Currently my software setting is "-a cnv8 --cn_config=7-7".  It was "7+7" with TRM v0.3.7, and the same clocks.  The rejects are slightly less with TRM v0.3.8, under 1%.

Thanks for responding.       --scryptr

390H/s?

My unlocked 460 2GB was doing 525H/s on 1225/2100 on CNv7 with SGMiner-GM.

NOT ALL RX 550 GPUS HAVE THE SAME CHIP--

I don't know how chip-specific the code for the "L" prefix configurations are, but there are a variety of RX 550 cards that have cut-down Baffin chips:

QUOTE-- "Sapphire has introduced a new Radeon RX 550 variant with 25% more CUs.  It features a mostly disabled Polaris 21 chip with 10 CUs out of 16 CUs enabled compared to the standard RX 550 with 8 out of 10 CUs enabled.  The additional 2 CUs translates to an extra 128 Stream Processors on Sapphire's new variant.

This GPU can effectively be thought of as an RX 555 although it is not officially branded as such."

LINK-- https://linustechtips.com/main/topic/893799-sapphire-introduces-new-radeon-rx-550-with-25-more-cus-using-polaris-21-instead-of-polaris-12/

These RX 550 cards are sold alongside those with proper Lexa chips and have similar performance levels and power usage.  Not all retailers describe them with proper Compute Unit (CU) descriptions.  There are reports that the Polaris 21 RX 550 units can be unlocked to even more than 10 CUs.  A Lexa chip has 8 standard, a full Baffin chip has 16, and the RX 550 cut-down Baffin variants are sold with 10.

This is posted because TeamRedMiner (TRM) has reports of exceptionally high CNv8 hashrates with the Lexa and Baffin cards.  Will there be a forthcoming "B" (for Baffin) prefix for the configuration setting?  How chip-specific is the code?

My RX 460 Baffin cards, unlocked to 16 CUs and BIOS modded, only hash at 390 H/s on CNv8 with TRM.  The clocks are 1250/1850, and if I push the clocks higher, rejects increase and crashes occur.  The Lexa cards are reported to out-perform my unlocked Sapphire Nitro+ RX 460 cards

If there are any configuration tips, please post them.  Oh, and my rigs are mostly Linux.  Thanks, TRM is really shaping up!       --scryptr  

same problem with 5x vega 64 runing hiveos and teamredminer v3.8  with 2% rejected shares in nicehash,nanopool, and all of grft mining pools.how can I set diff manually in hiveos?

same problem with 5x vega 64 runing hiveos and teamredminer v3.8  with 2% rejected shares in nicehash,nanopool, and all of grft mining pools.how can I set diff manually in hiveos?

A rejected share is simply when the pool does not accept a share that you find and submit. The most common reason is that the share is submitted for an old job. CN jobs on the gpu take a while to compute, so in some cases a new job is sent out right before a job completes. Added network latency exaggerates the effect.

However, you don't have 20% rejected shares, you rather have 29/(1559+29) = 1.83% rejected shares. I'd say it's on the high side, but nothing too crazy. I don't know Nanopool's policy for accepting shares for jobs for the same network block height though.

A rejected share is simply when the pool does not accept a share that you find and submit. The most common reason is that the share is submitted for an old job. CN jobs on the gpu take a while to compute, so in some cases a new job is sent out right before a job completes. Added network latency exaggerates the effect.

However, you don't have 20% rejected shares, you rather have 29/(1559+29) = 1.83% rejected shares. I'd say it's on the high side, but nothing too crazy. I don't know Nanopool's policy for accepting shares for jobs for the same network block height though.

Hi Guys.

My "rig" running with the latest version of this miner more than 24 hours, and I have lot of rejected shares.. around 20%
I use two Asus RX580 card, GPU0 is DUAL-OC-4G with Eplida memory, GPU1 is ROG-STRIX-O8G with Hynix memory.
I tried more BIOS mod, and default BIOS and lot of settings, but the results is same... any ideas?

Here is my log:

What is the "rejected share" exactly?

[2018-11-30 17:36:57] Pool xmr-eu2.nanopool.org share accepted. (GPU1) (a:1558 r:28) (75 ms)
[2018-11-30 17:37:09] Stats Uptime: 1 days, 04:23:05
[2018-11-30 17:37:09] GPU 0 [57C, fan 49%] cnv8: 967.9 h/s, avg 970.2 h/s, pool 936.0 h/s a:797 r:14 hw:0
[2018-11-30 17:37:09] GPU 1 [55C, fan 45%] cnv8: 955.6 h/s, avg 959.2 h/s, pool 893.7 h/s a:761 r:14 hw:0
[2018-11-30 17:37:09] Total                cnv8: 1.924kh/s, avg 1.929kh/s, pool 1.830kh/s a:1558 r:28 hw:0
[2018-11-30 17:37:39] Stats Uptime: 1 days, 04:23:35
[2018-11-30 17:37:39] GPU 0 [56C, fan 49%] cnv8: 970.2 h/s, avg 970.1 h/s, pool 935.7 h/s a:797 r:14 hw:0
[2018-11-30 17:37:39] GPU 1 [55C, fan 45%] cnv8: 955.7 h/s, avg 959.2 h/s, pool 893.4 h/s a:761 r:14 hw:0
[2018-11-30 17:37:39] Total                cnv8: 1.926kh/s, avg 1.929kh/s, pool 1.829kh/s a:1558 r:28 hw:0
[2018-11-30 17:37:41] Pool xmr-eu2.nanopool.org received new job. (job_id: 3089)
[2018-11-30 17:38:09] Stats Uptime: 1 days, 04:24:05
[2018-11-30 17:38:09] GPU 0 [57C, fan 49%] cnv8: 970.1 h/s, avg 970.2 h/s, pool 935.4 h/s a:797 r:14 hw:0
[2018-11-30 17:38:09] GPU 1 [56C, fan 45%] cnv8: 955.6 h/s, avg 959.2 h/s, pool 893.2 h/s a:761 r:14 hw:0
[2018-11-30 17:38:09] Total                cnv8: 1.926kh/s, avg 1.929kh/s, pool 1.829kh/s a:1558 r:28 hw:0
[2018-11-30 17:38:23] Pool xmr-eu2.nanopool.org received new job. (job_id: 3090)
[2018-11-30 17:38:31] Pool xmr-eu2.nanopool.org received new job. (job_id: 3091)
[2018-11-30 17:38:31] Pool xmr-eu2.nanopool.org share rejected. (GPU0) Error code: -1 - Block expired (a:1558 r:29) (39 ms)
[2018-11-30 17:38:39] Stats Uptime: 1 days, 04:24:35
[2018-11-30 17:38:39] GPU 0 [57C, fan 49%] cnv8: 970.1 h/s, avg 970.1 h/s, pool 935.1 h/s a:797 r:15 hw:0
[2018-11-30 17:38:39] GPU 1 [54C, fan 43%] cnv8: 955.6 h/s, avg 959.2 h/s, pool 892.9 h/s a:761 r:14 hw:0
[2018-11-30 17:38:39] Total                cnv8: 1.926kh/s, avg 1.929kh/s, pool 1.828kh/s a:1558 r:29 hw:0
[2018-11-30 17:38:44] Pool xmr-eu2.nanopool.org received new job. (job_id: 3092)
[2018-11-30 17:39:09] Pool xmr-eu2.nanopool.org share accepted. (GPU0) (a:1559 r:29) (76 ms)

teamredminer.exe -a cnv8 -o stratum+tcp://xmr-eu2.nanopool.org:14444 -u hereismylongestideverseen.mz -p x -d 0,1 --cn_config 6+7,7+8 --pool_broken_rpc --watchdog_script=miner_watchdog.bat --log_file=miner_log.txt

What Elpida straps do you use to get that hashrate? I've rx550 baffin 12CU unlocked, gets 520 h/s with 3+3

Yes, it's very impressive. For 1 month I was trying to fix the card BIOS and it helps a lot that her memory is Elpida. In Windows with CRYPTONIGHTV7 pi? Anei 550 hash with XMR-Stak 2.4. Respectively the Baffin 570 hash. In Linux the Baffin always had a low hashrate.