please include the pool fail-over in the next release. This is a very important option.
Thanks.
Just to note that I do use this mine for all of my AMD GPUs
Hi Apprentice, Apologies that we didn't get this done in this release. We recognize that pool failover is an important feature, and we will be adding it in the next release. To help us get it right, could you describe the failover and/or load balancing features you would like to see added? |
|
|
|
Team Red Miner v0.6.0 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.6.0 - Added ethash algo support.
- Relaxed ssl/tls cert chain verification.
We've added ethash algo support! We've put a ton of effort into this release to deliver what we believe is the best ethash miner for AMD GPUs. Performance advantage over existing miners will vary depending on GPU model and tuning and we've seen results ranging from +0 to +15%. Vega and VII GPUs tend to see the most benefit, with Vega56s w/ Hynix mem and VIIs doing exceptionally well. Polaris GPUs will typically see a very modest improvement in hashrate, but should also see some lowered power usage as well. Please checkout the ETHASH_GENERAL_TUNING.txt doc in the miner release package for more details on tuning. NOTE: We have observed some anomalous behavior with miner reported vs pool hashrates in competing miners. We suggest that anyone comparing miners against each other should perform long (24hr+) tests and compare poolside hashrates only. The more poolside shares that are taken into account during the test, the more accurate the results will be. We will be posting more information on this soon, as well as tools for externally verifying miner hashrates. As always, we encourage everyone to post their results and let us know how the miner performs 
|
|
|
|
Team Red Miner v0.5.9 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.5.9 - Added x16rv2 for the upcoming Ravencoin fork.
- Optimization work on x16r: +8-10% hashrate depending on clocks.
- Optimization work on x16r: mem clock no longer as important.
- Issue fix: kernels split into multiple binaries to fix linux amdgpu-pro driver issues.
We've added x16rv2 algo for the upcoming Ravencoin fork! (Also BitCash and a few others) We've also put a ton of effort to squeeze out as much performance as we could for the x16* algos in this release, with an up to 10% speed-up.
|
|
|
|
Team Red Miner v0.5.9 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.5.9 - Added x16rv2 for the upcoming Ravencoin fork.
- Optimization work on x16r: +8-10% hashrate depending on clocks.
- Optimization work on x16r: mem clock no longer as important.
- Issue fix: kernels split into multiple binaries to fix linux amdgpu-pro driver issues.
While the biggest change in this release was the addition of x16rv2, there are also some fixes for CN algos to work around driver bugs/crashes. If anyone was having issues with CN algos resulting in crashes in v0.5.8, we suggest trying v0.5.9.
|
|
|
|
Team Red Miner v0.5.8 releasedhttps://github.com/todxx/teamredminer/releasesChanges 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
|
|
|
|
Hello, @todxx ! If one card crashes, miner stops finding shares on all gpus, but continues getting jobs. is there a way to avoid this?  That is rather odd and should definitely not be happening. Can you tell us a bit more about your setup? Which OS version are you using? What version drivers are you running? Which version of the miner are you running? Do the stats still display when you press 's' ? How do you know if it's just one GPU that crashes? |
|
|
|
how to run ccx  what command line Hi qwep1, You can run CN conceal the same way as cnr, except use "cn_conceal" as the algorithm instead of "cnr". |
|
|
|
Team Red Miner v0.5.7 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.5.7 - Added CN conceal algo for Conceal (CCX).
- Added cuckarood29 algo for grin.
This release brings a couple new algos: CN conceal and cuckarood29! CN conceal is a bit picky about memory timings, so please checkout the CN_MAX_YOU_VEGA.txt doc before switching your rigs to it. How much memory is needed for cuckarood29? RX 570 4GB not work on Win7 (Blockchain drivers) [2019-08-06 07:50:40] Auto-detected AMD OpenCL platform 0 [2019-08-06 07:50:43] Initializing GPU 0. [2019-08-06 07:50:43] OpenCL enqueue error: -55 [2019-08-06 07:50:43] Warning: failed to initialize device number 0 (-28), retrying. [2019-08-06 07:50:43] OpenCL enqueue error: -55 [2019-08-06 07:50:43] Warning: failed to initialize device number 0 (-28), retrying. [2019-08-06 07:50:43] OpenCL enqueue error: -55 [2019-08-06 07:50:43] Warning: failed to initialize device number 0 (-28), retrying. [2019-08-06 07:50:44] OpenCL enqueue error: -55 [2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying. [2019-08-06 07:50:44] OpenCL enqueue error: -55 [2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying. [2019-08-06 07:50:44] OpenCL enqueue error: -55 [2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying. [2019-08-06 07:50:44] OpenCL enqueue error: -55 [2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying. [2019-08-06 07:50:44] OpenCL enqueue error: -55 [2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying. [2019-08-06 07:50:45] OpenCL enqueue error: -55 [2019-08-06 07:50:45] Warning: failed to initialize device number 0 (-28), retrying. [2019-08-06 07:50:45] OpenCL enqueue error: -55 [2019-08-06 07:50:45] Warning: failed to initialize device number 0 (-28), retrying. [2019-08-06 07:50:45] OpenCL enqueue error: -55 [2019-08-06 07:50:45] Failed to initialize device idx 0 (-28) [2019-08-06 07:50:45] Successful clean shutdown. My apologies, we should list somewhere that our c31 and c29 kernels currently only work on 8GB+ GPUs. I thought that we had a much nicer message in place than the errors that were printed for you. |
|
|
|
Team Red Miner v0.5.7 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.5.7 - Added CN conceal algo for Conceal (CCX).
- Added cuckarood29 algo for grin.
This release brings a couple new algos: CN conceal and cuckarood29! Cuckarood29 is quite picky about memory timings. Tight timings are needed to get good performance on this algo, however this algo is very memory heavy and timings that are stable on other algos may not be stable here. For ballpark hashrates, we've seen 580s run between 3.5g/s and 3.8g/s, and Vega64s range between 6g/s and 7.4g/s depending on clocks and timings.
|
|
|
|
Team Red Miner v0.5.7 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.5.7 - Added CN conceal algo for Conceal (CCX).
- Added cuckarood29 algo for grin.
This release brings a couple new algos: CN conceal and cuckarood29! CN conceal is a bit picky about memory timings, so please checkout the CN_MAX_YOU_VEGA.txt doc before switching your rigs to it.
|
|
|
|
Team Red Miner v0.5.6 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.5.6 - MTP improvements for Vega and Polaris (+1-3% hashrate, improved efficiency, esp Polaris)
As kerney666 already mentioned this release includes some improvements for MTP, getting both higher hashrate and consuming less power MTP improvements and benchmarks
To people interested in MTP: we just released an improved version in v0.5.6, todxx will update the ann title shortly. In short, you should see a little more hash (1-3%) for a overall lower power draw than before. On most Polaris cards, the power draw has been reduced significantly.
Since the Zcoin official sgminer was released with benchmark nrs vs TRM, I took the time to produce our own benchmarks, hopefully with enough data so users easily can reproduce the tests.
TRM vs Zcoin official sgminer
-----------------------------
amdgpu-pro 18.50, listed clocks are powerplay table clocks, not effective clocks.
Note that high clocks have been chosen for benchmark purposes, the one exception
being the second test set with lower clocks for the Vega 64 LC. We do recommend
tuning down clocks rather than using the benchmark configurations below.
Negative power draw difference means lower power draw for TRM.
Hashrates are short term max speed hash rates, not long term averages affected by
pad rebuild pauses.
Note: for 580s, the nrs below might differ significantly between Windows and Linux.
This is related to driver implementations and has nothing to do with the miners.
GPU CoreClk MemClk Sgminer TRM HR chg Power draw diff
Vega 64 LC 1500 1107 3.33 MH/s 3.52 MH/s + 5.7% - 5W
Vega 64 LC 1150 500 2.32 MH/s 3.00 MH/s +29.3% +20W
Vega 56@64 1407 1107 2.94 MH/s 3.12 MH/s + 6.1% - 5W
Vega 56 Hynix 1407 945 2.97 MH/s 3.15 MH/s + 6.1% - 2W
570 Nitro+ 1215 2050 1.59 MH/s 1.71 MH/s + 7.5% - 4W
580 Nitro+ 1215 2050 1.77 MH/s 1.92 MH/s + 8.5% - 3W
|
|
|
|
Any info hashrate c31 for rx 580?
Depends on the card and tuning (also the OS you're running on), but ballpark range is 0.5 to 0.6 g/s. |
|
|
|
WOW you guys, 1.35GPS on Radeon VII running C31... I really wish you guys would implement BEAM with uplift as you did grin for AMD cards. AMAZING JOB!!!
Thanks sharmanov We're working on adding some other cuckoo cycle algos first, but we would eventually like to hit the equihash algos too. It will probably be a while until we get there though. |
|
|
|
What about Ryo currency? This crypto uses cryptonight-gpu algorithm, but i don't see the algorithm in your software description.
Hi raptorman, We don't currently plan to support cn-gpu. The author of the algo is a miner developer himself and he has support for his algo in his miner: xmr-stak. |
|
|
|
I don't know why. I changed nothing with my cards. No tweaking with the cards. I'm good with the default settings. But every time I use TRM, my pc always says that Teamredminer.exe is blocked from accessing graphics card. I'm using 18.6.1 for my vega 64. If I use other miners, I don't encounter this problem. What could be causing this?
Make sure to exclude .exe file from your antivirus or windows defender and then you will not have problem. Thanks for responding but I already had exclusions for TRM. That's why I wonder what caused this because I don't have this problem if I use other miners. TRM will often push the GPU hardware harder than other miners. A lot of stock voltages/clocks on cards are very aggressive and can result in cards overheating. Have you looked at temps when you run the miner compared to other miners? Have you tried undervolting or lowering clocks? |
|
|
|
Willing to donate a few $$ (up to $100) in crypto to someone who can post results on Grin (Cuck31) on AMD R9 Nitro Fury 8GB HBM (or other Fury R9 card with 4GB HBM) with card optimized for low power usage.
There is no 4gb solver so Fury will never mine Grin31. I've started selling my Furies a while ago, only 1 left now, hope to get rid of it soon)) Our C31 implementation effectively requires 8GB or more vram. I think lolminer supports C31 on 4GB cards, but it will be quite slow. |
|
|
|
Blockchain drivers are a little bit outdated my friend! Get at least 18.6.1.
I will try using newer drivers again, problem is trying to get the Adrenalin driver to work with the VEGA FE. I haven't had luck getting the dual driver to work and all i get is the Radeon Pro drivers. That is why I have used older Blockchain driver. You may also need to adjust your clocks/voltages compared to CN. Some parts of c31 are very core/compute intensive and may require either slightly lower core clock or slightly more core voltage to keep the GPU stable as it warms up. |
|
|
|
just got my 5700XT up and running with 19.7.1 drivers. The only thing working and not correctly are: Phoenix 4.2c ethash @ 4Mhash Lolminer 0.8.3 Equihash192 @0.671 hash Lolminer 0.8.3 Equihash144 @0.202 hash so... yeah nothing else works.  i guess once everyone starts updating their software to work with navi, then we should start getting some real results. Have you tried ethminer? It should have a fallback opencl kernel for cards that it doesn't have a binary kernel for. It won't be as fast as a properly tuned kernel, but it would be an interesting data point. ethminer isn't recognizing it under opencl. I tried the --cl-only flag. Well that's a bummer. If it's not too much effort, could you post what ethminer outputs and also the output of running clinfo on the machine with the 5700xt? |
|
|
|
just got my 5700XT up and running with 19.7.1 drivers. The only thing working and not correctly are: Phoenix 4.2c ethash @ 4Mhash Lolminer 0.8.3 Equihash192 @0.671 hash Lolminer 0.8.3 Equihash144 @0.202 hash so... yeah nothing else works. i guess once everyone starts updating their software to work with navi, then we should start getting some real results. Have you tried ethminer? It should have a fallback opencl kernel for cards that it doesn't have a binary kernel for. It won't be as fast as a properly tuned kernel, but it would be an interesting data point. |
|
|
|
Team Red Miner v0.5.5 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.5.5 - Added cuckatoo31 algo for grin.
We've added cuckatoo31 for grin mining! Seems we might have been a bit late as asics are might already be here for the algo . They have been up since the coin launched. Maybe, but the diff has jumped significantly in the last few days. A week ago our profitability would have been quite good. |
|
|
|
|
Show Posts
