Team Red Miner v0.10.10 released!https://github.com/todxx/teamredminer/releasesThis release primarily adds support for Ironfish using the stratum protocol proposed by TRM, which enables miners to run at a much higher hashrate than previously. Confirmed pools with support at this time are Herominers and Flexpool. Other pools are welcome to inspect the forked ironfish on Kerney666's github (trm_stratum branch) to implement support. README highlights:- GPU: Added support for ironfish (-a ironfish, only the fast stratum protocol v2 supported).
- GPU: Dual mining support for ironfish with ERG and ethash (use --iron ... --iron_end).
- GPU: Addressed sluggish and lagging display with KAS solo mining (and ironfish).
- GPU: Added support for the ZIL ZMP protocol. Use zil:// in --zil .. --zil_end or normal pool configs.
- GPU: Added event script for calling external scripts on e.g. algo switching, see --event_script.
- GPU: Added support for switching between separate clocks/voltages on windows for zil switching.
- FPGA: Added kaspa support for JC13s and JCC2F carriers.
- FPGA: Added kaspa support for vu13ps on E300 boards.
|
|
|
|
Team Red Miner v0.8.0 released!https://github.com/todxx/teamredminer/releasesBiggest release in a long while with rewritten ethash kernels and new mining modes for all gpu types! Users are highly(!) recommended to take a few minutes to read the 0.7-to-0.8 migration guide and the new ethash tuning guide. Key highlights: - Polaris: Efficiency and slight hashrate increase. B-mode reintroduced for added hash. B-mode must be enabled with --eth_aggr_mode or --eth_config=Bxxx.
- Vega 56/64: greatly improved base kernel for efficiency. New B-mode that can shave off additional 1-2W on top of the A-mode kernel. B-mode must be enabled manually with --eth_config (--eth_aggr_mode does not apply). Tuning numbers have changed - do NOT keep your old static --eth_config values.
- Radeon VII: huge boost with its new C-mode but requires a special Linux setup. Can now do 100 MH/s on most air cooled VIIs. See tuning guide.
- 5700/5700XT: can shave off as much as 8-9W(!) of power using the new B-mode and dropping core clk+voltage. B-mode now the default mining mode. Unless you retune your core clk+voltage you will see a tiny power draw increase instead and not benefit from the upgrade, so read the migration guide.
- 5600XT: new B-mode has a much smaller effect. A-mode remains the default mining mode. See new tuning guide for more details.
- The dag cache is NOT compatible with the new B/C-modes. ETH+ZIL switchers have to choose between caching the epoch 0 dag and using the new mining modes.
- Ethash 4GB kernels NOT rewritten in this release, performance remains the same as in 0.7.x.
- See the migration guide for hashrate and power draw comparisons between 0.7.21 and 0.8.0.
|
|
|
|
i have issue rig stil mining but ethermine status 0 mhs reported sometimes in 2-3days mining, randomly happen
share continue nothing change but reported hashrate gone and avegare & current status slowly downturn, seems weird, no error happening on console/miner
right now i tried different dns, something weird happen lately
this happen atleast when defi craze start, at first september, i.m using 0.6.1 btw, skipped 0.7.9 cause using 2% more power consumption
any idea new version trm will come out?
TRM 0.7.15
https://github.com/todxx/teamredminer/tree/5a7ce1ec7fbfda947de3d267979b536ffc6fd99b why not see this version on first page on this topic? i see 0.7.9 last version. My apologies. I've been slacking a bit on updating the main page. It is now up to date. |
|
|
|
i have try this on ubuntu linux with amdgpu 18.40 with 5 rx470 modded bios, previous mining with claymore 15 is ok. after 352 cannot mining any ethash miner app. --platform=1 not work, vga on board not on and not monitor connect.
./teamredminer --platform=0 -a ethash -o stratum+tcp://eu1.ethermine.org:4444 -u 0x06030e479c965aDE02e10814355309Ac9c2fb670.myriglab -p x
Team Red Miner version 0.7.8
[2020-07-31 20:12:37] Pool eu1.ethermine.org: Ethermine ethash auto mode detected, setting --eth_stratum=ethproxy
[2020-07-31 20:12:37] Failed to probe OpenCL device idx 0 on selected platform 0, will be excluded.
[2020-07-31 20:12:37] Failed to probe OpenCL device idx 1 on selected platform 0, will be excluded.
[2020-07-31 20:12:37] Failed to probe OpenCL device idx 2 on selected platform 0, will be excluded.
[2020-07-31 20:12:37] Failed to probe OpenCL device idx 3 on selected platform 0, will be excluded.
[2020-07-31 20:12:37] Failed to probe OpenCL device idx 4 on selected platform 0, will be excluded.
[2020-07-31 20:12:37] Successful clean shutdown.
my clinfo is
Number of platforms 1
Platform Name AMD Accelerated Parallel Processing
Platform Vendor Advanced Micro Devices, Inc.
Platform Version OpenCL 2.1 AMD-APP (2686.5)
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd cl_amd_event_callback cl_amd_offline_devices
Platform Host timer resolution 1ns
Platform Extensions function suffix AMD
...
Hi takasungi, It appears that for some reason the drivers you are using do not support the CL_DEVICE_GLOBAL_FREE_MEMORY_AMD property which we use to check the available memory on GPUs. I would suggest installing newer 19.x or 20.x drivers as the easiest fix. |
|
|
|
Team Red Miner v0.7.7 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.7.7 - Added support for Nimiq (dumb mode only).
- Integrated a Nimiq node.js network proxy into the miner.
- Fixed Nimiq bug that could lose shares, especially against lower vardiff pools.
- Fixed Nimiq bug that could cause duplicate shares on startup for low-diff pools.
- Fixed regression bug for ethash Nicehash, correct stratum mode now used again.
We now support Nimiq!
|
|
|
|
Team Red Miner v0.7.6 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.7.6 - Fixed broken keyboard input in tmux+screen sessions (e.g. Hive OS).
- Added support for 5500(xt).
- Fixed Linux watchdog support for hard driver crashes (script was not executed).
- Fixed kawpow nicehash extranonce support.
Another bug-squashing release 
|
|
|
|
Due to the fact that unlike many respectable and honest developers who allow users to see when devfee process begins and ends, I suggest the following:
Block “dev2.teamredminer.com” within your router and then launch this software.
Check your router’s documentation to see if this feature is available. If not, you can always get a cheap Pi and install Pi-hole to block it.
Sure, you will be mining at a little slower rate but it’s worth it because you might have been losing a lot more!
FWIW, I am aware of at least 2 groups on github who have expressed their interest to investigate this software and make it much cheaper to use.
There is a penalty for blocking the dev fee in our miner, as I'm sure you've seen since the miner will constantly print error messages saying so when it can't connect to the dev pool. If you are not comfortable paying a dev fee while using this software (or any other software), I suggest using open source miner software instead. There are many projects out there and I would be happy to point you to some if you can't find any yourself. Looking through your post history I see you've been a proponent of removing the dev fee from Claymore's miner using various proxy hacks. So it seems like you're being dishonest about your intentions, and disrespectful to miner developers by trying to cheat their dev fee. In fact you have yourself clearly stated that you feel "entitled" to use other's hard work for free: ...
As for competition discussion, I am actually a lot more acquainted in human nature who loves things with a shiny sticker that reads: FREE!
So, no matter how low CM and or any other mining software developer - including your upcoming software ask for, there will be always a huge percentage of us in this very forum complaining “how dare you ....” and ask for links to their FREE version - because humans are entitled to everything-free and or open-sourced so I can easily replace your wallet address with my own!
|
|
|
|
Team Red Miner v0.7.5 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.7.5 - Fixed broken optimizations for kawpow in 0.7.4.
We had a kawpow bug slip into the previous released version. This bug caused Vegas to run slower than necessary and caused occasional hw errors in the miner for Navi and Polaris GPUs. The bug is fixed in this release.
|
|
|
|
Team Red Miner v0.7.4 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.7.4 - Increased ethash support on 4GB GPUs up to epoch 380-383
- Implemented split ethash dag buffers for 8GB GPUs to support DAGs over 4GB
- Kawpow optimizations (Navi +2.25%, Vega +1.25%, Polaris +0.25%)
- Added gpu enable/disable API support.
- Windows TDR detection/handling/warning.
- Monitor detection on Windows/Linux with intensity adjustment.
- Fix for ethash pool hashrate reporting stopping after network outage.
The big push in this release is extending ethash support for 4GB GPUs on higher epochs. Version 0.7.3 stopped working at epoch 351 which ETC has now crossed. Anyone running 4GB GPUs on ETC or Nicehash should update to this version as soon as possible. We also managed to squeeze in some optimizations for Kawpow. As you can see above Navi and Vega benefit the most from these optimizations.
|
|
|
|
Team Red Miner v0.7.2 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.7.2 - Fixed kawpow dag build DEAD gpu issue on windows Adrenalin 2020 drivers.
- Fixed Navi 5600(xt) support on windows.
- Fixed mining on Vegas on older amdgpu-pro drivers.
- Fixed ADL reporting of stats on windows for newer cards.
This release is mostly another round of bug clean-up for various driver issues users have been reporting. We've also added a kawpow tuning guide to help new users tune GPUs on kawpow.
|
|
|
|
Hi! Has anyone tried POLARIS? On RX488, RX478 the hashrate is lower on the new version 0.7.1 by 0.7 from small rig. Please tell me how to fix it. Win_10 Adrenalin_18.6.1 TRM_0.6.1  TRM_0.7.1  Hi primavera8989, One of the changes that we forgot to mention is that we do not use the B mode for polaris 8GB gpus by default starting in v0.7.0. To get the miner to use the B mode again you can add the following option: --eth_config=B |
|
|
|
Team Red Miner v0.7.1 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.7.1 - Fixed issue with VII ethash/kawpow on windows.
This release is just a quick bug fix to get VIIs working on windows again for ethash/kawpow.
|
|
|
|
Team Red Miner v0.7.0 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.7.0 - Added kawpow algo for Ravencoin.
- Added Navi support for kawpow and ethash.
- Changed device ordering to be pcie bus based by default, added --opencl_order option.
- Fixed issue with --list devices not working without other args.
- Reformatted help message to hopefully make it easier to read.
- Added multipool example scripts.
- Removed ssl/tls server name verification (was re-added with TLS SNI fix)
- Fixed an unhandled signal bug that would cause rare crashes.
- Fixed multi-pool API bug.
This release is a long time coming and starts the beginning of our support for Navi GPUs! We have also added support for Kawpow for Ravencoin! CAUTION: Kawpow is a very hot algo! Start with low clocks when testing! The following are some rough performance figures for kawpow: RX 5700XT: 28+Mh/s Radeon VII: 40+Mh/s RX Vega56/64: 25+Mh/s RX 580: 14+Mh/s RX 570: 13+Mh/s Again, this algo can get very hot very quickly, so we suggest starting with the following core clocks for initial testing and tuning from there: RX 5700XT: 1400MHz Radeon VII: 1400MHz RX Vega56/64: 1000MHz RX 570/580: 1000MHz If you do give it a spin, please post your results here. We love seeing how the miner runs on everyone's rigs Edit: Ten minutes after release and we have our first bug We've received reports that VIIs on windows do not work for ethash/kawpow. We are working on a fix now.
|
|
|
|
Team Red Miner v0.6.1 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.6.1 - Added pool failover and load balancing.
- Added better error messages when failing to allocate eth DAG buffers.
- Added server name for TLS SNI.
- Added automatic setting for environment variables for 4GB GPUs.
- Extended maximum length of usernames and passwords (for some merged mining setups).
- Added report of pool stats.
- Changed initial pool auto detect mode to eth proxy.
- Various fixes for submitting hashrate to pools.
It's been a long time coming, but we finally did it; we added pool failover support We also added pool hashrate stats to help with tracking multi-pool use. For the more advanced users, we also support load balancing pool strategies. (See the --help output for more info) If you want to try it out, there is an example start_multipool.sh/bat file included in the miner packages.
|
|
|
|
Team Red Miner v0.6.1 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.6.1 - Added pool failover and load balancing.
- Added better error messages when failing to allocate eth DAG buffers.
- Added server name for TLS SNI.
- Added automatic setting for environment variables for 4GB GPUs.
- Extended maximum length of usernames and passwords (for some merged mining setups).
- Added report of pool stats.
- Changed initial pool auto detect mode to eth proxy.
- Various fixes for submitting hashrate to pools.
It's been a long time coming, but we finally did it; we added pool failover support We also added pool hashrate stats to help with tracking multi-pool use. For the more advanced users, we also support load balancing pool strategies. (See the --help output for more info) If you want to try it out, there is an example start_multipool.sh/bat file included in the miner packages.
|
|
|
|
Hello. It seems that the load on the Grin29 Radeon VII is not optimal enough. the card's power consumption jumps back and forth. Are there plans to fix this in future versions?
Unfortunately that's just the nature of the cuckoo algos. They start out with a very compute intensive first step and then the following steps are memory intensive. So the power will go up during the compute parts and down during the memory parts. |
|
|
|
Yes, I'm find it and enable allready. Now waiting for bug reproduction...
Questions on eth mining:
- if I have 8Gb cards but want to use A varinat of config. What best config would be for A? The same number as for B, or not?
- it's need to add option to force autoconfig only with A config.
- is there some command for setting intensity? For lowering mining intensity on some card.
Thanks for your work! Waiting updates.
You can specify configs for the cards like with the cn_config, but it's eth_config instead. To make all cards run A mode, you can use --eth_config=A You can set a specific mode and intensity with something like so: --eth_config=A300 You can also provide a list with one entry per card, like so: --eth_config=A300,B400,A,B And it's need to optimize speed... On Phoenix with double kernels my RX 580 gives about 600KH/s (about 2%) more speed. Even if 0,65% dev fee not true, speed on TRM eth too low in compare with PM.
I'm guessing you haven't read any of the last ~20 posts in this thread. You might want to go back and look through them a bit. TL;DR: Phoenix miner reports hashrate ~2.9% higher than it actually gets. So by your measurement, we're getting about 0.9% better actual hashrate (I.E. your pool hashrate will go up 0.9%). |
|
|
|
kerney666, Today my rig, connected to nicehash with TRM eth start to recieve connections errors from pool and reconnect again and again but always connection refused by pool. I noticed this only after more than an hour of this errors while I had my way home...
I thought that my connection is dead, or pool on service... But closing miner and restart him solves the problem.
What it was?
Hi UnclWish, We've seen things like this happen in the past when a pool has banned an IP, but that usually only happens if the miner does something like submit a lot of invalid shares. Do you have a log of when this happened? I'd be interested to see the part of the log when it stopped mining and started having this problem. No, I haven't rejected shares. Only several. And I didn't change anything with connection, even didn't restarted it. So my IP stays the same. How to enable logging? I make log and when problem repeats post it here. You can enable logging by adding the following option to the command line: --log_file=trm_log.txt Where trm_log.txt is the name of the log file to write out. |
|
|
|
kerney666, Today my rig, connected to nicehash with TRM eth start to recieve connections errors from pool and reconnect again and again but always connection refused by pool. I noticed this only after more than an hour of this errors while I had my way home...
I thought that my connection is dead, or pool on service... But closing miner and restart him solves the problem.
What it was?
Hi UnclWish, We've seen things like this happen in the past when a pool has banned an IP, but that usually only happens if the miner does something like submit a lot of invalid shares. Do you have a log of when this happened? I'd be interested to see the part of the log when it stopped mining and started having this problem. |
|
|
|
Thanks for the heads-up, we'll do our best to support it by the fork. |
|
|
|
|
Show Posts
