todxx, So far, I only have 1 RX570 working in my server / workstation hardware. (BTW, previous version with lyra2z worked fine. 3.1, I think) Other RX570's in my celeron 6 card rig working great. Here is dmesg from a failing machine. FYI it's the whole thing since I don't know what parts will be helpful to you. Also, these machines boot up from PXE and xmr-stak starts by default. I went in and manually stopped it and started teamredminer before capturing the log. (Same workflow for working and non-working rigs) https://pastebin.com/eVszbM85There's a few errors reported by the amdgpu driver. Some of these I remember seeing in older drivers that I thought were now fixed. Is this the 18.30 driver or the 17.30 driver? |
|
|
|
Hey Todxx
I quickly installed 18.40 driver and now it seems to work. All 12 GPUs initialized & started mining.
The bad news: the hashrate is lower than on xmr-stak with 16.60 driver. For RX 550 the best driver is by far the 16.60 drivers.
Could you maybe look into this, to make it work with 16.60 driver?
On the other hand: with the 18.40 driver xmr-stak instantly crashes the driver upon starting.
Also tested with 17.40 drivers which is reasonably comparable with 16.60 drivers.
xmr-stak: ~5100 H/s for 12 RX 550 Sapphire Lexa
teamredminer: ~5000 H/s for 12 RX 550 Sapphire Lexa
Same settings.
Not running this at max settings, if I really push it I can reach 480-500 H/s but the bad silicon ones (1-2 in each rig will crash).
Could you guys finetune RX 550/560 a little more? I could also provide some RX 550/560 + SSH connection if you need to test. I got various models.
I'm afraid you hit a bit of a short coming of our tuning with the RX 550s/560s  . We only got a couple 550s and 560s to test with about a week ago, and we haven't been able to do much tuning for them yet. Thank you for the kind offer of ssh access, we might just take you up on it  I'll sync up with kerney tomorrow and we'll make a game plan for addressing the RX 550/560 tuning. Btw, which cn_config setting did you use for the 550s? |
|
|
|
This is exactly the symptoms I get. Never finishes initializing the card/s. These are the configurations on which I'm having failures with teamredminer 3.5.0 and 3.6.0 -- IBM X36550-M3, Ubuntu server 16.04, kernel 4.4, amdgpu-pro 17.30, 2x MSI Radeon RX560 Aero 4GB HP z600, Ubuntu server 16.04 and 18.04, kernel 4.4 and 4.15, amdgpu-pro 17.30 and 18.30, ASUS ROG Strix RX570 4GB Currently have 2 6GPU boxes with much less robust CPU's running just great and at least 1 of the z600's is also running great with teamredminer 3.5.0. Tried watching journalctl when starting the miner. No errors noted. And again, xmr-stak is very stable on these systems, just not as high hashrate. Team Red Miner v0.3.6 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.3.6 - Added support for Rx550 cards (gfx804).
- Improved stability on larger rigs, especially with weaker cpus.
- Improved error reporting on failed initialization.
Hopefully this is another step to achieving stability on larger rigs, especially with weaker cpus. It has been tested by one of the forum users who had both early initialization issues, then stability issues. His rigs have gone from crashing every 30-120 mins to running smoothly for 15+ hours except for (I think) a single crash due to insufficient voltage. I believe we have more work to do though, we'll monitor carefully and try to address all problems that appear. For people with specific startup issues that are willing to help us nail them down and solve them, please reach out to me with a PM. The ANN post will be updated shortly by todxx. Linux kernel 4.13, 16.60 driver getting this with 12 RX 550 Lexa Pro in rig [2018-11-02 04:33:39] Stats GPU 0 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 1 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 2 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 3 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 4 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 5 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 6 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 7 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 8 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 9 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU10 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU11 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats Total - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s
[2018-11-02 04:33:39] Pool pool.supportxmr.com received new job. (job_id: cRROY+SGvbG/T+sPA/wgUhFRvJDF)
[2018-11-02 04:33:39] Pool pool.supportxmr.com set difficulty to 5000 still nothing after 5 minutes... compared it to my Vega rig and there it says "successfully initited…". It never does that with the RX 550 on Linux. So it never finishes initialization. I tried 1 card on Windows, there it worked. Hey cryptomanman, It's strange that you're having issues with that RX 570. So far I've only see initialization issues on with Vegas when running 18.30 and newer drivers. Can you try to run the miner again and see if there are any amdgpu/drm errors reported by the kernel driver? With Vegas I've noticed that the driver will occasionally have problems and report tons of errors in dmesg/kernel logs. |
|
|
|
Team Red Miner v0.3.6 releasedhttps://github.com/todxx/teamredminer/releasesChanges in v0.3.6 - Added support for Rx550 cards (gfx804).
- Improved stability on larger rigs, especially with weaker cpus.
- Improved error reporting on failed initialization.
Hopefully this is another step to achieving stability on larger rigs, especially with weaker cpus. It has been tested by one of the forum users who had both early initialization issues, then stability issues. His rigs have gone from crashing every 30-120 mins to running smoothly for 15+ hours except for (I think) a single crash due to insufficient voltage. I believe we have more work to do though, we'll monitor carefully and try to address all problems that appear. For people with specific startup issues that are willing to help us nail them down and solve them, please reach out to me with a PM. The ANN post will be updated shortly by todxx. Linux kernel 4.13, 16.60 driver getting this with 12 RX 550 Lexa Pro in rig [2018-11-02 04:33:39] Stats GPU 0 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 1 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 2 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 3 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 4 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 5 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 6 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 7 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 8 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 9 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU10 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU11 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats Total - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s
[2018-11-02 04:33:39] Pool pool.supportxmr.com received new job. (job_id: cRROY+SGvbG/T+sPA/wgUhFRvJDF)
[2018-11-02 04:33:39] Pool pool.supportxmr.com set difficulty to 5000 still nothing after 5 minutes... compared it to my Vega rig and there it says "successfully initited…". It never does that with the RX 550 on Linux. So it never finishes initialization. I tried 1 card on Windows, there it worked. Hey MoneroCrusher, Those 16.60 drivers are a bit out of date. All of the linux testing we've done has been with 18.30+ drivers on ubuntu 18.04. Would it be possible for you to test with 18.30 or 18.40 drivers on an Ubuntu 18.04 install? |
|
|
|
Hi guys! I have a problem with connect to pool.minexmr.com in this miner.
I mine to long XMR wallet address on Exchange (without payment ID).
In another miner (srb, jce and etc.) everything ok with connection to pool, but only in teamredminer i have a fail.
Does someone have the same problem?
Hey plox99, I just tested one of my rigs running against pool.minexmr.com and it worked fine. Can you post what your batch file or command line is for running the miner? Feel free to PM me if you don't want to post it publicly. |
|
|
|
Dear, please add the option --bus-order, as in JCE, SRB. Very useful for simply identifying problem cards in rigs with a large number of video cards.
When the miner starts, you can see the PCIE ID, open your device manager, find the VEGA card, and you can see the same PCIE ID. I know that this can be done. But this is not convenient, especially when the card falls off after a while. Sorting by bus number is convenient because it has such an OverdriveNTtool. http://prntscr.com/lcjc3tIdeally, there should be a sorting by bus number based on the value of the --pcie_fmt parameter. That is, for Linux, 'hex' is more preferable, for Windows - 'dec' We will look into this as an option in the future. What you can do for the time being is manually reorder the cards using the -d option. If you use the option "-d 2,3,0,1", this will result in the GPUs in the miner being reordered so that GPU0 is actually device 2, GPU1 is device 3, GPU2 is device 0, and GPU3 is device 1. It's a bit annoying to setup, but it will work with the current version we have today until we can add an option to do it automatically. |
|
|
|
|
New release versions 0.3.5 posted!
The most relevant change in this release for lyra2z and phi2 is that the GPU initialization has been changed to be sequential by default. This is to prevent problems that occur on some slower CPUs (such as celerons).
To make the miner perform a faster parallel init like in v0.3.4, use the option --init_style=3.
You can read the full changes in the main post, but the rest are mostly bug fixes for CNv8 related issues.
|
|
|
|
New release version 0.3.5 posted! This version should fix: - problems with initializing GPUs running on low-end cpus (such as celerons)
- errors with using payment-ids with pools
- having the miner select the wrong opencl platform by default.
|
|
|
|
Platform Name: AMD Accelerated Parallel Processing
Number of devices: 2
Device Type: CL_DEVICE_TYPE_GPU
Vendor ID: 1002h
Board name: Radeon RX Vega
Device Topology: PCI[ B#3, D#0, F#0 ]
Max compute units: 64
Max work items dimensions: 3
Max work items[0]: 1024
Max work items[1]: 1024
Max work items[2]: 1024
Max work group size: 256
Preferred vector width char: 4
Preferred vector width short: 2
Preferred vector width int: 1
Preferred vector width long: 1
Preferred vector width float: 1
Preferred vector width double: 1
Native vector width char: 4
Native vector width short: 2
Native vector width int: 1
Native vector width long: 1
Native vector width float: 1
Native vector width double: 1
Max clock frequency: 1750Mhz
Address bits: 64
Max memory allocation: 4244635648
Image support: Yes
Max number of images read arguments: 128
Max number of images write arguments: 64
Max image 2D width: 16384
Max image 2D height: 16384
Max image 3D width: 2048
Max image 3D height: 2048
Max image 3D depth: 2048
Max samplers within kernel: 16
Max size of kernel argument: 1024
Alignment (bits) of base address: 2048
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: No
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: Yes
Round to +ve and infinity: Yes
IEEE754-2008 fused multiply-add: Yes
Cache type: Read/Write
Cache line size: 64
Cache size: 16384
Global memory size: 8573157376
Constant buffer size: 4244635648
Max number of constant args: 8
Local memory type: Scratchpad
Local memory size: 32768
Max pipe arguments: 16
Max pipe active reservations: 16
Max pipe packet size: 4244635648
Max global variable size: 3820172032
Max global variable preferred total size: 8573157376
Max read/write image args: 64
Max on device events: 1024
Queue on device max size: 8388608
Max on device queues: 1
Queue on device preferred size: 262144
SVM capabilities:
Coarse grain buffer: Yes
Fine grain buffer: Yes
Fine grain system: No
Atomics: No
Preferred platform atomic alignment: 0
Preferred global atomic alignment: 0
Preferred local atomic alignment: 0
Kernel Preferred work group size multiple: 64
Error correction support: 0
Unified memory for Host and Device: 0
Profiling timer resolution: 1
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: No
Queue on Host properties:
Out-of-Order: No
Profiling : Yes
Queue on Device properties:
Out-of-Order: Yes
Profiling : Yes
Platform ID: 00007FFB858EFFD0
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2580.6 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2580.6)
Extensions: cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_khr_gl_depth_images cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image cl_khr_mipmap_image_writes cl_amd_liquid_flash
My command line is teamredminer.exe -a cnv8 -o stratum+tcp://cryptonightv8.eu.nicehash.com:3367 -u xxx -p x --api_listen=0.0.0.0:4028 and the output is Mining Engine Process started, PID: 18540 > Team Red Miner version 0.3.4 > [2018-10-31 01:33:17] Failed to initialize device number 0. Hope it helps. Hey geck, Can you post your entire clinfo output? If you have more than one opencl platform you may need to specify the AMD platform with the --platform option. |
|
|
|
I tested this last night on two rigs (RX570's and Vega 56's). Great work indeed. It's hands down the fastest and least power-consuming CN miner around. For everyone's benefit, I got most hashrate using --cn_config=7+7 on the 570's and 16+14 on the Vegas so far, for virtually no increase in power draw. Net net a gain of about 4% hashrate at 7% less power than SRBminer. Well done. EDIT: looking forward to you releasing the same sort of improvements on the other CN variants (heavy/heaven/fast etc) and other algos that are grossly unoptimised for AMD hardware (looking at you x16r)!  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. what clocks? EDIT: sidenote... for the lulz I increased clock speeds on the Vega56's to 1590... Hashrate went up to 2150 h/s!  But power went up quite massively as well (over 225W per GPU). 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! Have you tried using --cn_config=7+7 ?
Yup there is no change at all. All my AMD's are 4GB and never get more than 820kh with cryptonight  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. this looks promising. Especially in a sea of viruses and trojan miners that we had here. I wish i had any lefover merit to give to you I tested at my home PC and now i will proceed to update my rigs. It seems your dev fee is high but it is well deserved. Test at home PC: Adrenalin 18.10.2, win 10 1809, vega 64 custom cooling, power table 85% from vega guide (unfortunate vega), core 1550/900 mem 1150/900 All consumption below is entire system consumption from the wall JCE miner: 2080H/s @ 300W SRBminer: 2130H/s @ 300W TeamRedMiner: 2300H/s @ 285W  I will provide here results from optimized Vega rigs later on. Is there any special driver version you recommend for Vega? Thanks! 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. Posting to confirm that the advertised hashrates and power draws for this miner are legitimate. Quite an impressive release from kerney666 and todxx; personally, I've had issues switching over rigs to v8 because of the increased power draw, and this miner has alleviated those problems, while giving increased hashrate!
My Vega 64s are currently working at about 2100 H/s and Vega 56's are running 2000 H/s with lower power draw and higher hashrates than I was running on SRBMiner.
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 Absolutely amazing results. Well done!
Looking forward to seeing what else you guys have to offer
Thanks dafuzz_rsa! We're looking forward to cranking out some new algos after we take a little bit of a breather |
|
|
|
Great to see some work from you again! Ive just tested it real quick on my Vega and 470 Rig. The power consumption is amazing! Vega 56 2016H/s @ 164 Watts RX 470 1008H/s @ 126 Watts Crazy stuff. Ill have to do some more tests. Unfortunately i dont have any merit points left  Thanks rubine! It's been quite the push to get this release out. Thanks for giving it a spin so quickly. Your RX 470 power is a bit higher than what we've been seeing, what clocks are you running on it? Hello tested on windows 10 with 6*RX580, it doesn't launch unfortunatly. i tryed without Antivirus and without OC.
I got the message "failed to list OpenCL devices".
Can it be a driver problem ? i have blockchain drivers.
Thank you
Hi flux, As rubine mentioned, it's likely that you have more than one opencl platform, and the miner uses the first platform by default. If adding the --platform=1 option that rubine suggested doesn't work, could you run clinfo on the command line and post the output? |
|
|
|
New release v0.3.4 posted! This version now includes cryptonight v8 support! Also better reporting of GPU hashrates and reporting of submitted/accepted/rejected shares. Please note that we have changed how we report GPU hashrates. Hashrates reported by the miner are now the full GPU hashrates. Previously hashrates reported were after dev fee deduction. Since we expect a lot of questions and comments about cryptonight v8, we have created a new thread for it here. Please post any cryptonight v8 related comments and questions in that thread. |
|
|
|
teamredminer v0.10.10This is an optimized miner for AMD GPUs and Xilinx FPGAs created by todxx and kerney666. Download is available in the github releases section.TRM official website: https://www.teamredminer.comTRM discord server: https://discord.gg/RGykKqBBelow is a list of mining operating systems and management software that have built-in support for teamredminer: This miner supports a range of algorithms. Please see the list below for details. The miner is configured via command line only, please run with the --help option to print a short help message for how to use the command line options. GPU SupportGPUs supported and tested: - Navi - RX 5700(XT)/5600(XT)/5500(XT) for supported algos in the table below.
- Big Navi - RX 6900XT, RX 6800(XT), RX 6700(XT), RX6600XT - same support as for Navi.
- RDNA3 - 7900XT, 7900XTX, see Navi30 in the table below for supported algos.
- Vega - RX Vega 64/56, Vega FE, Radeon VII (Vega 2)
- Polaris - RX 580/480/570/470/560/460/550
- Fiji - R9 Fury/Fury X/Nano, MI8 (supported but with very limited testing).
- Tonga/Antigua - R9 285/285X/380/380X, W7100, S7150 (beta support from 0.8.2. Only ethash+kawpow available.)
Supported GPU algorithms and their respective dev fees: | GPU Algorithm | Fee | | Ethash on Polaris GPUs | 0.75% | | Ethash on all other GPUs | 1.0% | | Kawpow | 2.0% | | Verthash | 2.0% | | Autolykos2 | 2.0% | | Ton | 1.0% | | Kaspa | 1.0% | | Ironfish | 1.0% | | Nimiq | 2.5% | | Cryptonight R | 2.5% | | Cryptonight v8 upx2 | 2.5% | | Cryptonight v8 turtle | 2.5% | | Cryptonight v8 half | 2.5% | | Cryptonight v8 double | 2.5% | | Cryptonight v8 rwz | 2.5% | | Cryptonight v8 | 2.5% | | Cryptonight heavy | 2.5% | | Cryptonight haven | 2.5% | | Cryptonight saber | 2.5% | | Cryptonight conceal | 2.5% | | Chukwa-512 (Turtlecoin) | 2.5% | | Chukwa-1024 (Turtlecoin) | 2.5% | | x16r | 2.5% | | x16rv2 | 2.5% | | x16s | 2.5% | | x16rt | 2.5% | | MTP | 2.5% | | Cuckatoo31 | 2.5% | | Cuckarood29 | 2.5% | | Lyra2rev3 | 2.5% | | Lyra2z | 3.0% | | Phi2 | 3.0% |
Some algorithms are not supported on some GPU architectures and/or drivers. Below is the compatiblity table: | Navi30 | Navi | Vega | Polaris | Fiji | Tonga | | Ethash | Y | Y | Y | Y | Y | Y | | Kawpow | N | Y | Y | Y | Y | Y | | Verthash | Y | Y | Y | Y | Y | N | | Autolykos2 | Y | Y | Y | Y | Y | Y | | Firopow | N | Y | Y | Y | Y | Y | | Ton | N | Y | Y | Y | Y | Y | | Kaspa | Y | Y | Y | Y | Y | Y | | Ironfish | Y | Y | Y | Y | Y | Y | | Nimiq | N | Y | Y | Y | Y | N | | Cryptonight R | N | N | L | L | L | N | | Cryptonight v8 upx2 | N | N | L | L | L | N | | Cryptonight v8 turtle | N | N | L | L | L | N | | Cryptonight v8 half | N | N | L | L | L | N | | Cryptonight v8 double | N | N | L | L | L | N | | Cryptonight v8 rwz | N | N | L | L | L | N | | Cryptonight v8 | N | N | L | L | L | N | | Cryptonight heavy | N | N | L | L | L | N | | Cryptonight haven | N | N | L | L | L | N | | Cryptonight saber | N | N | L | L | L | N | | Cryptonight conceal | N | N | L | L | L | N | | Chukwa-512 | N | N | L | L | L | N | | Chukwa-1024 | N | N | L | L | L | N | | x16r | N | N | Y | Y | Y | N | | x16rv2 | N | N | Y | Y | Y | N | | x16s | N | N | Y | Y | Y | N | | x16rt | N | N | Y | Y | Y | N | | MTP | N | Y | Y | Y | Y | N | | Cuckatoo31 | N | N | Y | Y | Y | N | | Cuckarood29 | N | N | Y | Y | Y | N | | Lyra2rev3 | N | N | L | L | L | N | | Lyra2z | N | N | L | L | L | N | | Phi2 | N | N | L | L | L | N |
Support legend: - Y = Supported
- N = Not supported
- L = Limited support: algos are supported on windows and linux with amdgpu-pro drivers, not supported on ROCm drivers.
FPGA SupportFPGA Devices supported and tested in Linux (Windows is not currently supported): - Xilinx Varium C1100
- SQRL Forest Kitten 33 - performance limited by product design, see guide for details
- Xilinx/TUL/Osprey U50C/ECU50
- TUL TH53/55
- Osprey E300 (vu33p, vu33p_CIV, vu35p, vu35p_CIV, vu9p, vu13p)
- Bittware CVP13
- SQRL BCU1525/TUL BTU9P/Osprey ECU200/Aleo U200/VCU1525
- SQRL JC33, JC35, JC13 on JCC2L/F carriers
Supported FPGA algorithms and their respective dev fees: | FPGA Algorithm | Fee | | Ethash | 4.0% | | Kaspa | 10.0% |
FPGA device/algo compatibility table: | Ethash | Kaspa | | C1100 | Y | Y | | FK33 | Y | Y | | U50C/ECU50 | Y | Y | | TH53 | Y | Y | | TH55 | Y | Y | | E300 (vu35p_CIV) | Y | Y | | E300 (others) | N | Y | | CVP13 | N | Y | | BCU1525/BTU9P/ECU200/U200 | N | Y | | JC33/JC35/JC13 on JCC2L/F | N | Y |
The miner reports GPU hash rates every 30 seconds. These are the full GPU hash rates before dev fee deduction (your pool hashrate will be slightly lower). The miner includes a read-only api based on the sgminer-5.5 API. Both the json and text formats are supported. For more details, we refer to the sgminer api documentation. The miner also includes a Claymore miner compatible API with support for a subset of the API. For reporting bugs and/or for features requests, please open an issue on this project's github issue tracker. For example command lines please see the batch/shell scripts in the miner download packages. Miner command line options are available hereRelease Notesv0.10.10Changes- 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 support for JC13s and JCC2F carriers.
- FPGA: Added support for vu13ps on E300 boards.
v0.10.9Changes- GPU: Added support for RDNA3 / 7900XT gpus (ethash, autolykos2, kaspa, verthash incl dual combos supported).
- FPGA: Added support for JC33s and JC35s on JCC2Ls
- FPGA: Added support for E300 with vu33p, vu33p_CIV, vu35p, and vu9p parts.
- FPGA: Added support for Alveo U200 active cooled variant.
v0.10.8Changes- GPU: Kawpow on Polaris 4GB gpus extended to epoch 369 (end of April 2023).
- GPU: Tiny Kaspa gpu hashrate boost across all gpus (+0.1%).
- GPU: Added triple ERG+KAS+ZIL and ETH+KAS+ZIL mining support, add both --kas and --zil sections to enable.
- GPU: R-mode support in dual/triple ZIL mining. Specify --eth_config=R inside --zil ... --zil_end to enable.
- GPU: Fixed HiveOS ERG+KAS issues with stray hw errs reported on RDNA2 gpus.
- GPU: Fixed additional small issues with dual zil mining paired with older algos.
- GPU: Fixed hw err issues for verthash when running with R-mode kernel params.
v0.10.7Changes- GPU: Added dual ERG+KAS mining support for all supported gpus (see DUAL_ERGO_MINING.txt).
- GPU: Fixed semi-broken dual zil mining for older algos (Nimiq, Argon2, x16r, and others).
- FPGA: Added support for running higher than 700MHz on Kaspa.
- FPGA: Added voltage control for TH53, TH55, and FK33.
- FPGA: Added support for Kaspa on VCU1525 and Aleo U200 boards.
- FPGA: Possible fix for crashes after network outage when mining Kaspa.
- FPGA: Added description of FK33 voltage mod, see FPGA_FK33_MOD.txt.
v0.10.6Changes- General: Added fix for Kaspa mining on MiningRigRentals.
- FPGA: Added Kaspa support for CVP13 and VCU1525 clones (BCU, BTU, ECU)
- FPGA: Renamed E300 to E335C in preparation for supporting additional FPGA devices on E300 boards.
- FPGA: Fixed broken TH53 temp/voltages display.
v0.10.5.1Changes- GPU: Kaspa single algo - fixed critical bug sometimes delaying shares, resulting in pool rejects.
- GPU: Kaspa single algo - fixed solo mining against the Kaspa stratum bridge or other setups with no extranonce sent.
v0.10.5Changes- GPU: Kaspa single algo mining rewritten for minimal latency, optimizing for the Kaspa 1 sec block time.
- GPU: Ethash+Kaspa dual mining now added, use --kas ... --kas_end. The setup is identical to ETH+TON. See the update DUAL_ETH_MINING.txt guide for more details.
- FPGA: Added KASPA single algo mining.
- FPGA: Added core clock throttling based on regulator current limits for devices that support it (C1100, U50C, FK33)
- FPGA: Added additional --debug voltage/current measurement prints for devices that support it (C1100, U50C, FK33)
v0.10.4.1Changes- GPU: Fixed Kaspa kernels for BC-160 (gfx1011) and Radeon VII family on older PAL drivers.
- GPU: Fixed rare cases of ethash false alerts of dead gpus.
v0.10.4Changes- GPU: Added KASPA single algo mining (fee 1.0%, use -a kas).
- GPU: Added simpler way of forcing hashrate reports for kawpow/firopow (use --prog_hash_report).
- GPU: Fixed missing hashrate reports in some cases for kawpow/firopow with multiple pools.
v0.10.3.1Changes- GPU: Fixed issues with the Autolykos2 pad prebuild for some gpus/rigs.
- GPU: Handled bad user config situations with multiple dag caches specified for ZIL.
v0.10.3Changes- GPU: Added next height pad prebuild for Ergo/Autolykos2 to raise effective hashrate over time.
- GPU: Better execution of R/B/C modes for ethash with dual zil mining.
- GPU: Added simple example scripts for ETC+ZIL, ERG+ZIL, RVN+ZIL.
- GPU: Added R-mode zil cache support with --eth_dag_cache=0.
- GPU: Added argument --eth_no_job_logs to suppress pool job logging.
- GPU: Fixed some issues pools using miningcore, mainly ergo and verthash pools.
v0.10.2Changes- GPU: Tweaked Polaris ethash tuning to work better with the new smooth-power setup.
- GPU: Fix for Autolykos crashing on Polaris and 4GB GPUs.
- GPU: Fix for Eth+Ton dual mining crashes with new smooth-power setup.
- GPU: README about smooth power available: smooth power overview.
v0.10.1Changes- FPGA: Added new more efficient ethash bitstreams that use less power and can run at lower voltage.
- FPGA: Added new SC firmware for C1100 and U50C/ECU50 that allows voltages down to 625mV vccint and 1050mV vcchbm.
- FPGA: Added 32-bit linux armhf build for running on zynq/raspberry pi boards.
- FPGA: Added support for the Osprey E300, this will be integrated into the onboard firmware.
- FPGA: Fixed API not reporting correct Alive/Sick/Dead status for FPGAs.
- GPU: Reworked smooth power for improved stability, primarily on Polaris and Vega gpus.
- GPU: Added --eth_smooth_power to control the smooth power scheduling feature.
- GPU: Fixed cases of stuck ethash tuning during single algo mining.
- GPU: Fixed rare network-related crashes for ethash mining, often with ssl enabled.
- GPU: Fixed bug causing Autolykos hashrate drop on VIIs.
v0.10.0 (R-mode public release)Changes- GPU: R-mode introduced. See separate documentation. Applicable for Vegas/VIIs/Navi10/Big Navi.
- GPU: Smooth power transitions for ethash family algos.
- GPU: Added support for multiple --api_listen and --api_listen2 endpoints (up to 8 total).
- FPGA: Fixed crash bug with > 16 fpgas running in a single miner instance.
- GPU: Added argument --gpu_sdma=on|off for special situations. For example, BC-250 needs --gpu_sdma=off.
v0.9.4.7 (R-mode public beta)Changes- GPU: Hopefully fixed R-mode low hashrate issues on random Navi gpus.
v0.9.4.6 (R-mode public beta)Changes- GPU: R-mode introduced. See separate documentation. Applicable for Vegas/VIIs/Navi10/Big Navi.
- GPU: Smooth power transitions for ethash family algos.
- GPU: Added support for multiple --api_listen and --api_listen2 endpoints (up to 8 total).
- FPGA: Fixed crash bug with > 16 fpgas running in a single miner instance.
v0.9.4.2Changes- GPU: Fixed eth+ton issue that could lead to a higher eth shares stale rate. Primarily for large gpus (6800/6900XT) with aggressive tuning.
- GPU: Internal split of binaries helping some Vegas and Navis with crash issues on ethash from 0.9.2 and forward.
- FPGA: Added initial support for TUL TH53/TH55.
v0.9.4.1- Replaced by 0.9.4.2 due to bug with dual mining device selection.
v0.9.4Changes- GPU: Navi/Big Navi rewrite for eth+ton, increased hashrates on both algos and more stable setup.
- GPU: Navi/Big Navi eth+ton rigs with stale eth issues should be fixed.
- GPU: Pool outage for dual algo now results in eth mining only instead of pausing. This will reduce crashes.
- GPU: Fixed a potential deadlock when mining eth+ton. Rigs that have gotten strange "crashes" should upgrade, especially when coupled with a network or pool outage.
- GPU: Added --dual_tuner_step and --dual_tuner_period to configure the dual tuner accuracy.
- GPU: Fixed race bug for ethash where gpus could accidentally build a dag for epoch 0 at startup.
- GPU: RaveOS fix for running the TRM wss proxy for Nimiq and certain TON pools.
v0.9.3Changes- GPU: Added Polaris support for dual ETH+TON (full eth + 600-750 MH/s ton per gpu). All AMD gpus now supported.
- GPU: Updated DUAL_ETH_MINING.txt with information for all AMD gpus.
- GPU: Added support for TON Pool (ton-pool.com). See TON_MINING.txt for details.
- GPU: Fixed bug that could cause stale shares on gpus disabled for dual mining.
v0.9.2.1Changes- GPU: Fixed a critical bug for Polaris and Vegas on Windows and Linux amdcl2, only reaching 50% poolside hashrate.
- GPU: Added support for selecting dual algo devices using a "-d x,y,z,..." argument inside the --ton .. -ton_end clause.
v0.9.2Changes- GPU: Added TON algo for single algo mining on all gpu generations (see TON_MINING.txt).
- GPU: Added dual ETH+TON mining for Navi and Big Navi gpus (see DUAL_ETH_MINING.txt). Vega and Polaris upcoming shortly.
- GPU: Added dual mining tuner based on scoring weights (see --dual_tuner_weights).
- GPU: Faster initial ethash tuning on startup.
- FPGA: Added --fpga_max_jtag_mhz for limiting the JTAG communication frequency used.
- FPGA: Fixed DNA for vu35p - now matches Vivado hardware manager and NextJTAG.
v0.9.1Changes- FPGA: Updated FPGA_GUIDE.txt with new devices, voltage tuning, and more.
- FPGA: Added U50C/ECU50 FPGA suppport.
- FPGA: Added custom SC firmware for C1100 and U50C.
- FPGA: Added TRM SC firmware programming support, see --fpga_update_fw.
- FPGA: Added voltage control for C1100 and U50C (using new firmware), see --fpga_vcc_int, etc options.
- FPGA: Added support for additional FK33 sensors (hbm voltage, current sensors).
- FPGA: Added support for DNAs in the --fpga_devices option.
- FPGA: Added --fpga_allow_unsafe option for disabling safety limits.
- FPGA: Added timeout for ethash DAG gen on FPGAs.
- GPU: Added --eth_ignore_abort_fail to disable intensity adjustment due to failed aborts.
- GPU: Added better handling of dead gpu logging in corner cases that previously didn't mention a specific gpu.
v0.9.0Changes- Added initial FPGA ethash support. See FPGA_GUIDE.txt for details.
v0.8.7Changes- General: added offline benchmark mode for (almost) all algos (see --benchmark).
- Network: improved situations with the "Dev pool failed to connect." error message appearing. Users in China should preferably run with "--dev_location=cn".
- Network: added experimental support for DNS-over-HTTPS (see --dns_https and --dns_https_sni).
v0.8.6.3Changes- Autolykos2: emergency release to support larger pad size from block 614400. Some GPUs (mainly Vegas) will need higher core clocks to achieve the same performance as previous versions due to larger pads breaking some previous optimizations. More optimizations to come in future releases.
- Autolykos2: added argument --autolykos_ignore_diff for certain pools that aren't compatible with the ERGO reference miner pool implementation.
- Progpow: fixed wrong --help text for --prog_micro_tune.
v0.8.6.2Changes- Firopow/MTP: added a synthetic algo 'mtp_firopow' that will use the correct algo given the system time and shut down the miner at the time of the Firo fork on Oct 26.
- Ethash/progpow: split the ethash and progpow algos into separate binaries, mainly for some Vegas that ran into stability issues going from 0.8.5 to 0.8.6.
- Autolykos2: added support for Tonga.
- Advanced SSL usage: changed the default SSL behavior to not provide a SNI hostname during handshake. See the updated --help section on the -o argument for how to force a SNI hostname being sent.
v0.8.6Changes- Firopow: new algo added for Firo's upcoming fork (see start_firo.sh/bat). Only testnet mining is available before the fork, see start_firo_testnet.sh/bat.
- Firopow/kawpow: rewrote tuning guide (see KAWPOW_FIROPOW_TUNING.txt).
- Firopow/kawpow: slight hashrate improvements, mainly from choosing full gpu tuning by default and adding a micro-tuning mechanism for Polaris gpus (see new argument --prog_micro_tune).
- Autolykos2: added high score support and display of submitted share difficulty.
- General: fixed Radeon VII support on recent win drivers. NOTE: HBCC must be DISABLED for all Vegas.
- General: fixed broken fan control for Navis on some driver versions.
- General: improved Windows compute mode enable with automatic elevation (with --uac) and restart of gpus.
v0.8.5Changes- General: added Windows clocks/voltage/built-in timings control (beta functionality). See section in --help and CLOCKS_VOLTAGE_CONTROL.txt.
- General: fixed some issues with Windows fan control, mostly for Big Navi gpus.
- General: added mem temp limits (stop/resume), see --mem_temp_limit and --mem_temp_resume.
- Ethash: added support for forcing ethash pool hashrate reports (see --eth_hash_report).
- Ethash: fixed hashrate reports for Crazypool when using failover pools.
- Autolykos2: added extranonce subscription support for e.g. Nicehash.
v0.8.4Changes- General: Added fix for failure to load GPU kernels on newer drivers, e.g. Big Navi on Adrenalin 21.6.x.
- Emergency patch: fixed Haven mining generating mostly hw errs after the recent hard fork.
v0.8.3Changes- General: added Autolykos2 algo for ERGO (very good target for Vega 56/64, see the AUTOLYKOS_TUNING.txt guide).
- General: improved and simplified dual ZIL mining for ethash/kawpow/verthash/autolykos2 (see the new DUAL_ZIL_MINING.txt guide).
v0.8.2.1Changes- Bugfix: fixed windows issue with intermittently reading zero gpu stats and blasting fans (bug in 0.8.2).
- Verthash: added --verthash_max_uploads=N to control the upload of the verthash table to gpus at startup. Some chipsets get issues running > 4 gpus concurrently. Typical error is that multiple gpus die immediately at startup when running the full rig, but work fine if you only run 3-4 gpus.
- Verthash: fixed support for 550 2GB gpus.
v0.8.2Changes- General: added Verthash algo for Vertcoin.
- General: added Tonga and Antigua support for ethash and kawpow.
- General: extended support to 24 gpus (previously max 16 gpus possible).
- General: better handling of driver issues related to gpu clocks/temps stats.
- General: now showing sensor power in stats output.
- General: fixed device name parsing in ROCm 4.1 and newer win drivers.
- API: added sensor power, jnct temp and mem temp to API output.
- Ethash: added --eth_micro_delay for weaker psus (see help section for details).
- Ethash: fixed watchdog DEAD gpus on small gpus building kawpow DAG.
- Kawpow: now working fully with MiningPoolHub, regardless of bad seedhash values.
v0.8.1.1Changes- Patched v0.8.1 with new devices ids for 6700XT support.
v0.8.1Changes- General: basic Big Navi support added (ethash, kawpow, mtp, nimiq supported algos). See the ETHASH_TUNING_GUIDE.txt for a short section on Big Navis.
Driver support missing on Windows for fan control and mem temp.
- Ethash: display gpus now use A-mode by default to prevent failed allocation and low hashrates.
- Stats: handling of negative temperatures under Linux.
- Eth+zil: added new pool strategy 'min_epoch' for dual pool connection switching (see start_zil_eth.bat/.sh example script).
v0.8.0NotesBiggest 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.
Changes- Ethash: VII kernel rewrite and new C-mode with boost feature (see guide).
- Ethash: Navi kernel slight optimization and new B-mode for lower core clock and power.
- Ethash: Vega kernel rewrite and new B-mode for lower core clock and power.
- Ethash: Polaris kernel rewrite and new B-mode for slightly higher perf.
- Ethash: added share processing timeout and default for Binance pool (see --pool_share_limit_ms).
- Claymore API: fixed leak that stopped serving requests after 32k api calls.
- Claymore API: added password support (see --cm_api_password).
- Logging: added log rotation support (see --log_rotate).
- Logging: log files now contain the miner welcome message so the version is stored.
- Kawpow: now mining ok at MiningPoolHub even though their seedhash is broken.
- Fan control: added min/max fan speed range (see --fan_control).
- General: added argument to turn off duplicate pci bus id filtering (see --allow_dup_bus_ids).
v0.7.22Notes- NAVI KERNEL REWRITE! Over the last month we've been working on new kernels. The first one released is for Navi. The main feature is lower power consumption, hashrate will remain about the same but depends somewhat on clocks. NOTE: please let the miner retune any existing --eth_config arguments for all Navi gpus, the new values will be significantly lower.
- Claymore API now supported, meaning you can use EthMan to monitor TRM rigs.
Changes- Ethash: Kernel rewrite for Navi. Should now be more stable and use less power. Vega/Polaris still in the works.
- General: Slightly reworked init procedure again to address some rigs running better on <= 0.7.18 than >= 0.7.19.
- General: Added Claymore compatible API, see the --cm_api_listen option.
v0.7.21NotesQuick release that addresses situations where Ethash with capped DAG on 4GBs would crash after 5-10 mins when running at 4078-4080MB. Changes- Ethash: improved probability for high (4078-4080MB) ethash 4GB capped allocation running stable over time.
v0.7.20NotesETH is now approaching the start of the 4GB death with the upcoming switch to epoch 382. TRM was the first miner to add support for mining with 4GB gpus with a partial DAG, here called "extended mining". However, it has always required manual configuration. This release adds a default conservative cap at 4072MB for DAG storage on 4GB gpus for out-of-the-box execution of the miner. For maximum performance, miners are still advised to manually tune their rig(s) with the --eth_4g_max_alloc argument. Most rigs runs stable with a higher value than 4072, which makes a significant difference for upcoming ETH epochs. For more detailed instructions, our Ethash 4GB guide has also been updated and is available at https://github.com/todxx/teamredminer/blob/master/doc/ETHASH_4GB_HOWTO.txtChanges- Ethash: added default capped DAG allocation for 4GBs at 4072MB (see --eth_4g_max_alloc).
- Ethash: bugfix for crashes using --eth_dag_cache on 4GB gpus.
v0.7.19Notes- Ethash solo-miner share high-score list added, use --high_score to enable.
- Ethash single buffer dag for a small power save. Only available on recent drivers and should in theory always be an improvement. It is not verified 100% stable yet and therefore not the default in this version. Enable with --eth_dag_buf=A to test.
- Miner gpu initialization procedure rewritten. The init procedure should now hopefully be much more stable, especially on Navis in general and even more so for 5600(XT)s.
Changes- General: added adjustable ratio support for quota and load_balance pool strategies (see --pool_ratio).
- General: rewrote the miner init procedure to be more stable in general.
- General: fixed issue where output blocking could cause mining work to stop.
- General: reduced main binary size.
- Ethash: reintroduced single DAG buffer support for recent drivers allowing large single allocations (see --eth_dag_buf).
- Ethash: added high score list of the 15 highest value shares found since start (see --high_score).
- Ethash: small improvements in keeping the gpu busy over epoch switches.
- Ethash: fixed bug that would cause deadlocks in rare occasions.
- Ethash: bugfix - dag cache wasn't enabled for 4GB gpus.
v0.7.18Notes- Support for the ETC fork added. Run with "-a etchash" for easiest support, see "--eth_variant_mode" in the help for more info.
- ETH+ZIL miners: add "--eth_dag_cache=0" to use a second dag cache and prebuild epoch 0 immediately at miner start.
- Ethash miners relying on ramp-up and stagger for stability: the default mode of these tweaks has been changed to off. They now need to be enabled with --eth_ramp_up and --eth_stagger. While helping a number of rigs, these tweaks caused increased instability of others, making the choice of a good default mode difficult.
Changes- Added etchash support (see algo etchash and --eth_variant_mode).
- Added dag cache support, mostly intended for eth+zil mining (see --eth_dag_cache).
- Fixed hex char parsing in enable/disable submenu, can now work with >= 10 gpus.
- Changed the default for ethash ramp-up and staggering to false (see --eth_ramp_up and --eth_stagger).
- Added check for broken win setups with duplicated opencl platforms and/or devices.
v0.7.17Changes- BETA: Added fan control, see --help section or USAGE.txt. Enable with --fan_control.
- Fixed deadlock bug that could happen when using multiple pools with the failover strategy.
- Added option for not sending stale shares (see --no_stale_submit).
- Added watchdog check for early gpu init hangs.
- Added example watchdog scripts for win/linux.
v0.7.16NotesBETA RELEASE - small fixes for Turtlecoin's new algo chukwa2. Changes- Chukwa2: fixed kernels loading for Radeon VII gpus.
- Chukwa2: fixed mem footprint for 2GB gpus.
v0.7.16bNotesBETA RELEASE - adds Turtlecoin's new algo chukwa2. Not tested as rigorously as other versions. Only use for the Turtlecoin fork. NOTE: Navi gpus are NOT supported on chukwa2 for now. Support will be added if there's sufficient interest. Changes- Added algo trtl_chukwa2 for the Turtlecoin fork on 2020-10-22.
v0.7.15NotesSmall bugfix release. Changes- Ethash: fixed bug for ZIL (epoch 0) mining on 4GB gpus (bug appeared in 0.7.14).
- Ethash: reverted to v0.7.10 kernels for stability purposes except for ROCm-based rigs.
v0.7.14NotesThis release wraps up our work for 4GB gpus mining ethash. Linux 4GB are verified to mine up to and including epoch 381 on drivers 18.50/19.30/19.50/20.10. After that, we have added support for extended mining from epoch 382 and up. Extended mining is a trade-off between hashrate and being able to mine at all, gpus will lose additional hashrate for every extra epoch. Please see the Linux section in the ETHASH_4GB_HOWTO.txt for more details and instructions. Changes- Ethash: verified Linux support for 4GB gpus up to and including epoch 381.
- Ethash: added support for extended 4GB mining from epoch 382 and up.
- Kawpow: cleaned up false hw errs for some block heights.
v0.7.13Notes- Windows user with 4GB rigs - see the new guide ETHASH_4GB_HOWTO.txt for instructions.
Changes- Added better default Windows dag allocation strategy on 4GB gpus.
- Added experimental support for resetting gpus before mining (Windows only).
- Added argument for manual adjustment of 4GB dag allocation (see --eth_4g_alloc_adjust=X,Y,Z,...).
- Added protection against broken dev servers with additional random server selection mechanism.
v0.7.12Notes- Bugfix release: v0.7.11 could crash with rejected ethash shares.
Changes- Fixed print format bug on ethash rejected shares.
v0.7.11Notes- Ethash additions: printing share diff in GH (always enabled), hashrate watchdog (see --eth_hashwatch).
- Better debug support: --long_timestamps, --pool_debug.
- We've found certain motherboard/bios combinations that due to kernel and/or driver bugs have issues with the first or last gpu in rigs. If you see excessive hw errors reported on a single gpu, and switching around gpus still always generates errors in the first or last gpu, try using --eth_dag_alloc_patch.
Changes- Added DAG allocation patch under linux for certain mobo/bios combinations (see --eth_dag_alloc_patch).
- Added ethash hashrate watchdog (see --eth_hashwatch).
- Added ethash abort mechanism for Vegas on ROCm (see --eth_direct_abort). Not useful in other contexts.
- Added pool traffic debug (use --pool_debug).
- Added print of share difficulty for ethash family algos. Unit is always GH.
- Added microsec timestamp resolution in logs (use --long_timestamps).
- Regression bug: argon2/chukwa was broken in 0.7.10, now working again.
- Turned off compute mode checks for non-Polaris gpus.
v0.7.10Notes- Ethash 4GB rigs, especially on win, should use --eth_alloc_epoch=N with N being the max epoch that the gpus can allocate. This will avoid DAG reallocation issues.
- For Navi rigs having issues with eth+zil or Nicehash mining with frequent DAG switching, try using --eth_dag_slowdown=9.
Changes- Added default log filename (trm_<algo>_<yyyymmdd_hhmmss>.log)
- Added ethash forced initial allocated epoch ( --eth_alloc_epoch=N). Note: HIGHLY recommended for 4GB rigs.
- Added ethash family DAG build slowdown configuration (--eth_dag_slowdown=N, default value 4).
- Added ethash family DAG build staggering across gpus (disable with --eth_no_stagger).
- Added ethash family intensity ramp-up (disable with --eth_no_ramp_up).
- Added option for forcing dev fee region (see --dev_location).
- Added MTP for Navi gpus.
- Added MTP ramp-up after pad rebuild.
- Fixed error printouts on failed watchdog script execution on Linux.
- Stats: now shows more clocks and temps, and also adds gpu state in hashrate prints (see --short_stats to disable).
- Added checks for and enabling compute mode and disabling crossfire on Windows (see --enable_compute).
v0.7.9Changes- Fixes for mixed rig mining on Linux.
- Added --eth_epoch argument for easier epoch testing.
- Added --eth_aggr_mode for automatic aggressive 'B' mode on Polaris 8GB gpus.
- Added --watchdog_disable argument.
v0.7.8Changes- Upgrade for the upcoming Haven hard fork (July 20, 2020).
- Tiny Nimiq optimizations (1-2% max, mostly Vega and Navi).
- Fixed CPU usage issue when redirecting stdin to /dev/null.
- Fixed pool name returned by API for Nimiq.
v0.7.7Changes- Added support for Nimiq Polaris/Vega (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.
- Added support for Nimiq Navi.
- Added support for icemining Nimiq solo mining mode (set -p m=solo).
v0.7.6Changes- 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.
v0.7.5Changes- Fixed broken optimizations for kawpow in 0.7.4.
v0.7.4Changes- 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.
v0.7.3Changes- Emergency patch for 4GB cards to handle a few more ETC epochs.
A more complete patch is coming out shortly.
v0.7.2Changes- 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.
v0.7.1Changes- Fixed issue with VII ethash/kawpow on windows.
v0.7.0Changes- 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.
|
|
|
|
Any idea when you expect the CNv8 release?
Have you tested it on Linux with multiple Vegas?
We're hoping to get CNv8 out in the next couple days. We have not yet tested it on a linux system running multiple vegas, but we have tested it on a linux system with 7 x 470s and everything ran fine. I would expect the same for a system with multiple Vegas. Do note that CNv8 will require amdgpu-pro drivers version 18.30 or newer on linux for both Polaris and Vega cards. We do not initially plan to support CNv8 on ROCm. |
|
|
|
|
New release v0.3.3 posted!
This release contains:
API Support
ROCm Support (again)
PCIe Bus Identification
Stats interval option
Unfortunately, we did not get our CNv8 implementation stable enough to release in this version and we decided to hold it back until the next release.
|
|
|
|
Any update on the API? Hey soothaa, We have the API mostly done, but we need to do a bit more testing. Unfortunately, because we're so busy getting cnv8 working, we don't have the time to do a separate release for just the API before doing another release for cnv8. We should have the next release out with API and cnv8 support by Oct 18th, hopefully a bit sooner. |
|
|
|
@alucard20724 Don't think we've tested on that driver version. Can you run "clinfo" from a command prompt, it will dump all opencl platforms and devices on your box. Then, scroll up and locate the section for a Vega 56 that looks like this (might be one at the very bottom of the output): Platform ID: 00007FF8044C4AB0
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2527.10 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2527.10)
Before asking you to dump the whole thing here, can you tell me if you see the string "gfx900" or something else for the name? I normally have gfx901, not a gfx900. I've had that same issue before. I normally rename the gfx900.bin to gfx901.bin in the miners that require a .bin file just verified clinfo, it's "gfx901" oh.. and how about api support? We will address the gfx901 issue in the next release, but for the time being you can try disabling HBCC on the cards while mining. Adding API support is on our todo list, but we don't have an estimate on when we'll get it released yet. |
|
|
|
|
New version v0.3.2 posted!
This version adds support for windows and the linux amdgpu-pro/PAL drivers for Vega!
Unfortunately we had to temporarily remove ROCm support to get this release out in a timely manner. We will be adding ROCm support back in the future.
There are no new features other than supporting new platforms/drivers, so existing users do not need to update if they're already happy with their setups.
|
|
|
|
todxx - good to see you back on the forum.
Looking forward to seeing what magic you can do to improve performance on my Vega56 cards. I've been using tdxminer 0.2.2.2 since release I think!
Thanks.
Thanks ajmulh! Glad to see you're enjoying the miner You can do solo extraction support on these algorithms. I think you will have so many more fans.
I have been searching for a long time than you can get a solo for Lyra2z. but only cpuminer-opt-3.8.8.1 for today could connect directly to the wallet!
I'm afraid solo support isn't on our todo list right now. You could setup your own pool for solo mining though. There are a number of open source pool software packages available out there (e.g. yiimp, nomp, node-stratum-pool, etc). API support please...
It's on the todo list, we'll get there in time. Right now we are focusing on getting a windows release out and adding algos. Is there anyway you can make this miner work on the AMDGPU Pro PAL driver? Specifically version 18.30? The issue is Cryptonight full rate hashing is not really supported until that version. This miner is the only one that must use ROCm. You have support for AMDGPU Pro but it is only legacy OpenCL support on the driver and not PAL support. Can you please support PAL or I guess Windows but I'd rather just have PAL support so my builds just work... at this point I need to have an image for all other miners then a seperate ROCm image for this miner.
I understand your frustration, and we are looking into supporting the PAL driver. Previously the opencl Vega driver that shipped with AMDGPU Pro was based on ROCm, but an older, broken version of ROCm that was relatively useless for mining (no riser support). Supporting the PAL driver is on our todo list, but we don't know when we'll get this feature out. It will depend on how much work it will be to support the PAL driver and we are still investigating that. |
|
|
|
|
New release v0.3.1 posted!
Anyone running phi2 should switch to the new release as soon as possible.
This release addresses problems with phi2 that resulted in rejected shares and low pool-side hashrate.
Unfortunately the fix also resulted in slightly lower performance for phi2 by a few percent.
|
|
|
|
|
Show Posts
