Re: [ANN] TeamRedMiner 0.5.8 - Cryptonight/Chukwa Thread - High hashrate, Low Power
Team Red Miner v0.5.8 released
https://github.com/todxx/teamredminer/releases
Changes in v0.5.8
The main change in this release is that we've added support for the Chukwa algo for Turtle Coin!
This algo runs particularly well on the VIIs, so if you have some I suggest giving it a spin
https://github.com/todxx/teamredminer/releases
Changes in v0.5.8
- Added Chukwa-512 algo For Turtlecoin (trtl_chukwa).
- Issue fix: kernels not loaded properly for Conceal.
- Issue fix: added logic for pool reconnect on N rejected shares in a row (see --pool_max_rejects=N).
The main change in this release is that we've added support for the Chukwa algo for Turtle Coin!
This algo runs particularly well on the VIIs, so if you have some I suggest giving it a spin
hey todxx,
Got some issues over here,
*Well my system consists of Vega 64 STRIX OC running over HIVE OS (latest version 0.6-73@190922)
now here's the problem
-I tested Chukwa via TRM 0.5.8 ,posted my test results here before too.
-After a day , I tried running CNR as usual on TRM 0.5.8,well cards won't even initialize even after 10 mins.
-So Went back to TRM 0.5.7 (had CNR running over this about a week with great stability)
-Well now on TRM 0.5.7 one of my Gpu goes dead in 5 mins.
-Downgraded hive os to 0.6-69@190922
-Again TRM 0.5.7 one of my Gpu goes dead in 15 mins.
-Downgraded linux amd pro drivers from 19.40 to 18.40
-Again TRM 0.5.7 one of my Gpu goes dead in 15 mins.
>> well in short TRM 0.5.8 messed my system (not a accusation! I'm very much happy using TRM since inception
) just need to find what went wrong. <<as I have different OC profiles for CNR (used for a month) & chukwa, theres no question of memory timings.
could there be issues of card stuck with voltage?
kindly help
Hi!
We're aware of issues on HiveOS Vega images for the 0.5.8 release for CN + variants, got notified today. We should soon be releasing 0.5.9 that includes x16rv2 and we'll make sure that runs ok with HiveOS on our own test rigs. What is strange is that you had issues when you rolled back to TRM 0.5.7 for cnr, I'm sorry I can't really say what's going on there. Given a clean reboot of the rig and applying the same clocks as you used before for cnr, nothing should have changed really? I assume you're still seeing the issues?