v0.10.7 release.

README.md

@@ -1,4 +1,4 @@
-# teamredminer v0.10.6
+# teamredminer v0.10.7
 This is an optimized miner for AMD GPUs and Xilinx FPGAs created by todxx and kerney666.
 
 **Download is available in the [github releases section](https://github.com/todxx/teamredminer/releases).**
@@ -115,7 +115,7 @@ FPGA Devices supported and tested in Linux (Windows is not currently supported):
 - TUL TH53/55
 - Osprey E300
 - Bittware CVP13
-- SQRL BCU1525/TUL BTU9P/Osprey ECU200
+- SQRL BCU1525/TUL BTU9P/Osprey ECU200/Aleo U200/VCU1525
 
 Supported FPGA algorithms and their respective dev fees:
 
@@ -144,6 +144,16 @@ For command line options see the [USAGE.txt](USAGE.txt) file that comes with the
 
 ## Release Notes
 
+### v0.10.7
+#### Changes
+- 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.6
 #### Changes
 - General: Added fix for Kaspa mining on MiningRigRentals.

USAGE.txt

@@ -1,4 +1,4 @@
-          Team Red Miner version 0.10.5.1
+          Team Red Miner version 0.10.7
 Usage: teamredminer [OPTIONS]
 Options:
   -a, --algo=ALGORITHM      Selects the mining algorithm.  Currently available:
@@ -154,6 +154,8 @@ Pool config options:
                               just one pool will make that pool receive twice the hashrate as the other pools 
                               since their ratio will still be the default value of 1.
       --pool_debug          Logs all pool traffic.
+      --pool_comb_sub_auth  This setting handles broken pools for some situations and sends the subscribe and authorize
+                              messages together as a batch. 
 
 Global pool options:
       --pool_connect_TO=SEC Set the time-out for attempting to connect to a pool. SEC is the time to wait in

doc/DUAL_ERGO_MINING.txt

@@ -0,0 +1,63 @@
+Team Red Miner Dual Coin ERGO Mining
+====================================
+
+2022-12-22 Initial version
+
+Overview
+--------
+To mine using autolykos2+kaspa (which is the only supported dual
+algo), take a working TRM autolykos2 command line and add a KAS
+section in the middle or at the end:
+
+--kas -o stratum+tcp://pool.woolypooly.com:3112 -u <kaspa wallet>.<worker> -p x --kas_end
+
+If you don't want to dual mine on all devices, you can add a device
+selection argument inside the --kas .. --kas_end clause. If you only
+want to dual mine on gpu 0 and gpu 3 you would use:
+
+--kas -d 0,3 -o stratum+tcp://pool.woolypooly.com:3112 -u <kaspa wallet>.<worker> -p x --kas_end
+
+The dual mining setup for autolykos2 lets the user split the capacity
+between autolykos2 and the second algo using the --dual_intensity
+argument (please see the separate section below).
+
+Power draw in dual mining will often be HIGH, especially on Vegas and
+Polaris gpus. It depends on what clocks you're coming from. Use core
+clock adjustments and the argument --dual_intensity (see --help or
+USAGE.txt) to keep power draw in check.
+
+Last, see the dual mining section in USAGE.txt or the miner's --help
+output for additional arguments.
+
+
+Dual Intensity Tuning
+---------------------
+For autolykos2 dual mining, you can balance the primary and dual algo
+using the --dual_intensity argument:
+
+- The argument range is 0.0-1.0. Zero means full autolykos2 mining, 1.0
+  means full dual algo.
+
+- If you don't specify the --dual_intensity argument, the dual
+  auto-tuner will scan the range and choose a sensible value per
+  gpu. You can observe the tuning results in the rightmost column in
+  the miner stats output.
+
+- You can enumerate values per gpu with a comma-separated list, e.g.
+  --dual_intensity=0.4,0.4,0.7,0.7
+
+- If the list is shorter than the number of gpus, the first value is
+  used for the remainder of the gpus. This implies that a single value
+  passed with --dual_intensity=0.3 will be used for all gpus.
+
+- The argument can be placed anywhere on the command line, it does not
+  need to be inside the --kas .. --kas_end range.
+
+- It is _not_ recommended to use extreme values close to zero or one,
+  for such setups it's better to simply mine a single algo instead.
+
+- Dual intensity values will typically end up in the 0.25-0.75 range.
+
+- If you want to control the dual auto-tuner behavior, TRM provides
+  the --dual_tuner_weights=X:Y:Z argument. This argument is described
+  in detail in USAGE.txt and the miner's --help output.

doc/DUAL_ETH_MINING.txt

@@ -1,21 +1,23 @@
 Team Red Miner Dual Coin ETH Mining
 ===================================
 
+2022-10-16 Updated for Kaspa dual mining.
+
 TL;DR
 -----
-To mine ETH+TON (which is the only supported dual algo at the moment),
-take a working TRM ethash command line and add a TON section in the
+To mine Ethash+Kaspa (or TON, which is a dead algo at the time of writing),
+take a working TRM ethash command line and add a KAS section in the
 middle or at the end:
 
---ton -o stratum+tcp://ton.hashrate.to:4002 -u <ton wallet>.<worker> -p x --ton_end
+--kas -o stratum+tcp://pool.woolypooly.com:3112 -u <kaspa wallet>.<worker> -p x --kas_end
 
 If you don't want to dual mine on all devices, you can add a device
-selection argument inside the --ton .. --ton_end clause. If you only
+selection argument inside the --kas .. --kas_end clause. If you only
 want to dual mine on gpu 0 and gpu 3 you would use:
 
---ton -d 0,3 -o stratum+tcp://ton.hashrate.to:4002 -u <ton wallet>.<worker> -p x --ton_end
+--kas -d 0,3 -o stratum+tcp://pool.woolypooly.com:3112 -u <kaspa wallet>.<worker> -p x --kas_end
 
-TRM's dual mining setup let's the user split the capacity between
+TRM's dual mining setup lets the user split the capacity between
 ethash and the second algo using the standard --eth_config
 argument. The higher intensity, the more capacity for ethash and less
 for the dual algo. Therefore, you SHOULD remove any existing
@@ -29,16 +31,21 @@ gpus. It depends on what clocks you're coming from for ethash. Use
 core clock adjustments and the argument --dual_intensity (see --help
 or USAGE.txt) to keep power draw in check.
 
-Last, see the TON dual mining section in USAGE.txt or the miner's
+Note: Kaspa has a very short block time (1 sec). This very frequent job
+switching means the ethash hashrate might take a small hit from what the
+tuner outputs as expected hashrate. Hashrate will also vary slightly between
+30 sec hashrate prints. This is fully normal.
+
+Last, see the dual mining section in USAGE.txt or the miner's
 --help output for additional arguments.
 
 
 Overview
 --------
 From v0.9.2, TRM includes support for true dual mining together with
 ethash. All AMD gpus are now supported. Subsequent releases might add
-support more dual mining algos - the single supported dual algo
-currently is TON.
+support more dual mining algos. There are currently two supported dual
+algos: Kaspa (KAS) and TON.
 
 TRM's dual mining is configurable in the sense that the user decides
 how the gpu capacity should be split between the two algos. This is
@@ -52,36 +59,36 @@ good trade-off between running a very competitive ethash hashrate
 close to the max possible while also providing room for the dual algo
 to operate.
 
-Dual mining ETH+TON
+Dual mining ETH+KAS
 --------------------
-To dual mine ethash and TON, do as follows:
+To dual mine ethash and Kaspa, do as follows:
 
 1) Start with a working ethash configuration for TRM.
 
 2) If you have an --eth_config argument, remove the intensities. You
-   can keep the A/B-mode setting.
+   can keep the A/B/R-mode setting.
 
-3) Add a TON argument section that contains the pool(s) you want to
-   use for dual TON mining. This follows the same principle as TRM's
-   dual ZIL mining setup. This added argument will enable dual TON
-   mining on the Icemining pool:
+3) Add a Kaspa argument section that contains the pool(s) you want to
+   use for dual Kaspa mining. This follows the same principle as TRM's
+   dual ZIL mining setup. This added argument will enable dual Kaspa
+   mining on the woolypooly pool:
 
-   --ton -o stratum+tcp://ton.hashrate.to:4002 -u <ton wallet>.<worker> -p x --ton_end
+   --kas -o stratum+tcp://pool.woolypooly.com:3112 -u <kaspa wallet>.<worker> -p x --kas_end
 
-   It's fully possible to insert the --ton ... --ton_end arguments
+   It's fully possible to insert the --kas ... --kaspa_end arguments
    into e.g. a Hive flight sheet's custom miner arguments section to
    enable dual mining, while still using Hive's builtin support for
    configuring the ethash mining.
 
 4) If you only want to dual mine on a smaller selection of gpus, you
-   can add a device selection argument inside the ton argument
+   can add a device selection argument inside the kas argument
    list. For example, if you want to dual mine on gpu 0, 1 and 4 in
    the rig but just do plain ethash on the rest you would use:
 
-   --ton -d 0,1,4 -o stratum+tcp://ton.hashrate.to:4002 -u <ton wallet>.<worker> -p x --ton_end
+   --kas -d 0,1,4 -o stratum+tcp://pool.woolypooly.com:3112 -u <kaspa wallet>.<worker> -p x --kas_end
 
 5) If power draw is too high, or your card end up with strange low
-   hashrates for either eth or ton, use the --dual_intensity argument
+   hashrates for either eth or kaspa, use the --dual_intensity argument
    to use less power and avoid being power throttled. This argument
    will limit the gpu capacity used for the dual algo. Accepted values
    are 0.0-1.0, where 0.6 means 60% capacity is used. You can provide
@@ -119,7 +126,7 @@ Test on a single gpu and be prepared for a 30-40% increase in power
 draw. We suggest lowering the core clk as well. If the power draw is
 too high for your setup, you can either throttle the whole gpu by
 lower the core clk, or use the argument --dual_intensity=X to reduce
-the gpu capacity used by the dual ton. By using
+the gpu capacity used by the dual algo. By using
 e.g. --dual_intensity=0.5 the dual algo will only use 50% of the
 available gpu resources after ethash. This is a way of keeping power
 draw lower by still keeping core clk high, which is necessary on an
@@ -132,17 +139,17 @@ mining (or C-mode for Radeon VIIs if available).
 
 Polaris
 Polaris gpus run dual mining quite well. You can often use your
-standard eth clocks, and gain 600-750 MH/s ton for an additional power
-draw of 35-45W at the wall per gpu. Use clocks/voltages or the
---dual_intensity argument to lower power draw at the cost of either
-lower hashrates for both algos, or just lower the dual algo using
+standard eth clocks, and gain a decent dual algo hashrate for an 
+additional power draw of 35-45W at the wall per gpu. Use clocks/voltages
+or the --dual_intensity argument to lower power draw at the cost of 
+either lower hashrates for both algos, or just lower the dual algo using
 --dual_intensity.
 
 
 Dual Mining Ethash Modes and Intensity
 --------------------------------------
-All ethash mining modes (A/B/C) are available in dual mining as well,
-and behave like they do for single algo ethash mining. The B/C-modes
+All ethash mining modes (A/B/C/R) are available in dual mining as well,
+and behave like they do for single algo ethash mining. The B/C/R-modes
 are often very helpful when dual mining on Vegas and Navis since they
 help keep a higher eth hashrate even when lowering the core clk in
 order to keep power draw in check. For Polaris gpus, the mode does not