Topic: T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 49. (Read 174976 times)

0.18.1

* Add "progpow-veriblock" algorithm (for Veriblock)
* Add "progpow-veil" algorithm (for VEIL's upcoming fork)
* Add "megabtx" algorithm (for Bitcore)
* Remove CUDA dependency for "kawpow"/"progpow" algorithms
* From now on "stratum+tcp" automatically selects the most commonly used pool protocol for a given algorithm (use "stratum1+tcp" and "stratum2+tcp" to override it)

Bug fixes:
* Occasional crashes on miner shutdown
* Miner wouldn't start if some of the GPUs aren't supported even though they are deselected via "-d"
* (ethash) Consuming memory on the GPUs deselected by "-d"
* (Web UI) "Update available" pop-up kept showing up upon monitoring page refresh

Maybe, not sure at this point.
Thanks for suggestion.

Not until there are pools available that support the new algo

Hey Trex,

is it possible to add CTXC Cortex?

Would be awesome!

Don't u plan to add new qureno algo?

0.17.3
* ethash optimisations (1-2% on some cards, see --kernel in the help file for more details)
* Add x33 algorithm (for Qureno)

Bug fixes:
* Add --worker parameter to mitigate the issue with usernames containing dots
* Improved compatibility with various mining pools / protocols

HiveOs power limit :
90W -> ~ 25
120W -> ~ 30
(Micron memory) works stable than claymore (nicehash)

What do you have on gtx 1070 on ETH, 30+?

On gtx1070 works perfect! thanks

"Add "ethash" algorithm (for Ethereum). For Nicehash mining use "nicehash+tcp://" pool url prefix."

This will be a problem when mining at NiceHash and using a management software like AwesomeMiner with multiple GPUs and Miners. Setting that prefix would also use the same prefix on other miners, which wont work. And so we cant use T-Rex for Ethereum.

Is it possible to just auto detect the pool? Thank you!

0.17.2
* Add "ethash" algorithm (for Ethereum). For Nicehash mining use "nicehash+tcp://" pool url prefix.
* Add "progpowz" algorithm (for Zano)
* Add "--pci-indexing" parameter: orders GPUs by PCI Bus Id (same as "--ab-indexing" but starts with 0)
* Add "--gpu-init-mode" parameter: enables sequential DAG generation to reduce load on power supplies
* Print hash rate if no shares have been found for more than 1 minute to indicate miner's activity

Bug fixes:
* CUDA 11 build not working on some algorithms (x25x and similar), and with RTX cards
* "GPU is idle" error when generating DAG on low-end cards
* "nan(ind)" in share rejection GPU stats
* Log files not rotated correctly

Should be fixed in 0.17.2

X16Rv2 broken. Win 7

20200910 10:34:49 T-Rex NVIDIA GPU miner v0.16.2  -  [CUDA v11.0]
20200910 10:34:50 r.555a9ecfbe3a
20200910 10:34:50
20200910 10:34:50 NVIDIA Driver v445.87
20200910 10:34:50 CUDA devices available: 5
20200910 10:34:50
20200910 10:34:50 WARN: DevFee 1% (x16rv2)
20200910 10:34:50
20200910 10:34:50 URL : stratum+tcp://x16rv2.na.mine.zpool.ca:3637
20200910 10:34:50 USER: *****
20200910 10:34:50 PASS: c=BTC
20200910 10:34:50
20200910 10:34:50 Starting on: x16rv2.na.mine.zpool.ca:3637
20200910 10:34:50 ApiServer: HTTP server started on 0.0.0.0:4067
20200910 10:34:50 -------------------------------------------------------
20200910 10:34:50 For control navigate to: http://192.168.1.112:4067/trex
20200910 10:34:50 -------------------------------------------------------
20200910 10:34:50 ApiServer: Telnet server started on 0.0.0.0:4068
20200910 10:34:50 WARN: GPU #0[10000]: ASUS GeForce GTX 1060 3GB, intensity set to 20
20200910 10:34:50 Authorizing...
20200910 10:34:50 WARN: GPU #1[20000]: Gigabyte GeForce GTX 1060 3GB, intensity set to 20
20200910 10:34:50 Authorized successfully.
20200910 10:34:50 WARN: GPU #2[30000]: ASUS GeForce GTX 1060 3GB, intensity set to 20
20200910 10:34:51 WARN: GPU #3[50000]: ASUS GeForce GTX 1060 3GB, intensity set to 20
20200910 10:34:51 WARN: GPU #4[70000]: ASUS GeForce GTX 1060 3GB, intensity set to 20
20200910 10:34:57 WARN: New difficulty: 8 (0.03125)
20200910 10:34:57 x16rv2 block 378814, diff 12.451
20200910 10:34:57 Hash order DADE165098E2C923
20200910 10:34:57 ERROR: Can't find nonce with device [ID=1, GPU #1], cuda exception in [Algorithm::find_nonces, 206], an illegal memory access was encountered
20200910 10:34:57 WARN: Messy shutdown...
20200910 10:34:57 ERROR: Can't find nonce with device [ID=0, GPU #0], cuda exception in [Algorithm::find_nonces, 206], an illegal memory access was encountered
20200910 10:34:57 ERROR: Can't find nonce with device [ID=4, GPU #4], cuda exception in [Algorithm::find_nonces, 206], an illegal memory access was encountered
20200910 10:34:57 ERROR: Can't find nonce with device [ID=2, GPU #2], cuda exception in [Algorithm::find_nonces, 206], an illegal memory access was encountered
20200910 10:34:57 ERROR: Can't find nonce with device [ID=3, GPU #3], cuda exception in [Algorithm::find_nonces, 206], an illegal memory access was encountered
20200910 10:34:57 Main loop finished.
20200910 10:34:57 ApiServer: stopped listening on 0.0.0.0:4067
20200910 10:34:57 ApiServer: stopped listening on 0.0.0.0:4068
20200910 10:34:59 WARN: WATCHDOG: T-Rex does not exist anymore, restarting...

0.16.2
* (UI, API) Show which GPU generated nonce/solution for share submission
* (UI, API) Show per-GPU rejected/total share statistics
* (Web monitoring page) Auto-saving web monitoring page preferences (dark theme, chart on/off etc.)
* Add "--low-load" cmd line parameter to optionally opt in for using CUDA kernels that put less stress on the GPUs where running regular kernels cause instability. See "t-rex -h" or "t-rex-help.txt" for more details. Currently this is only applicable to "kawpow" and DAG generation in particular.

Bug fixes:
* "can't init enumerate, code -6" error when applying memory tweaks to P102/104/106 cards
* "can't init 999, 0x800b01a" error when applying memory tweaks on Windows 7
* memory tweaks stuck after the miner termination
* memory tweaks becoming inactive in case of network issues or overclock adjustments
* setting intensity through the web monitoring page is broken

Got it thx.... I needed to open T-REX app. properties and set "it" as run as administrator.  

When you run as admin it changes your folder to the Windows\system32 folder. You have to change directory back to your folder with the miner to launch it. Basic windows command line navigation stuff....

  Running cuda 11 decreased my hashrate without --mt. I'm unable to get it to run with --mt as Administrator through my batch file.  Error ... not recognized as an internal or external command. So I'm back to  T-REX 0.15.8  Running MTP algo win 10.

EDIT: I needed to open T-REX app. properties and set "it" as run as administrator.

I use T-rex for Kawpow (1080Ti´s) but still more rejected on Miningpoolhub (0.6%).

Hm, i set mt 1 to test mining MTP, but if any mt parameter is set I can't change intensity through web interface, it remains same as in config forever.

ps This disappointing bug aside this update is quite good cos unlike ethpill --mt 1(only tried 1 so far) affects 1070 as well. Still even 1080Ti got better hashrate with mt 1 than with pill and mt-0. Lets hope OC will remain stable!

0.16.1
* Add memory tweaks for GDDR5 and GDDR5X cards (10xx series)
  --mt  Memory tweak mode (default: 0 - disabled). Range from 0 to 6.

* (kawpow, progpow) Faster DAG generation

NOTE:
Memory tweak mode

General recommendation is to start with 1, and then increase only if the GPU is stable.
The effect is similar to that of ETHlargementPill and can potentially increase hashrate by up to 7% when mining kawpow.
Supported on graphics cards with GDDR5 or GDDR5X memory only.
Requires running the miner with administrative privileges ("Run As Administrator" / "sudo").
Can be set to a comma separated list to apply different values to different cards.
Example: --mt 4 (applies tweak mode #4 to all cards that support this functionality)
                --mt 3,3,3,0 (applies tweak mode #3 to all cards except the last one)