Bitcoin Forum
June 06, 2020, 05:36:24 PM *
News: Latest Bitcoin Core release: 0.19.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 »
  Print  
Author Topic: [ANN] TeamRedMiner 0.7.5 - AMD GPU Miner for Grin, MTP, x16rv2 and more  (Read 83225 times)
todxx
Member
**
Offline Offline

Activity: 169
Merit: 67


View Profile
September 13, 2018, 03:20:26 AM
Last edit: June 05, 2020, 11:34:18 PM by todxx
Merited by dbshck (5), CjMapope (5), suchmoon (4), deadsix (3), AngusCanine (2), styleshifter (1), rubine2323 (1)
 #1

teamredminer v0.7.5 Release
This is an optimized miner for AMD GPUs created by todxx and kerney666.

For questions/comments about kawpow, ethash, chukwa, or cryptonight algorithms, please post in this thread.
This is the cuckarood29, cuckatoo31, mtp, x16rv2, x16r, x16rt, x16s, lyra2rev3, lyra2z, and phi2 thread for this miner.

Discord server now open! Join here https://discord.gg/GDFBVX5.

Algorithms:
  • Ethash (eth, etc, etp, others)
  • Kawpow (ravencoin)
  • Cryptonight R (monero)
  • Cryptonight v8 turtle (turtlecoin, loki)
  • Cryptonight v8 half (stellite, masari)
  • Cryptonight v8 double (x-cash)
  • Cryptonight v8 reverse waltz (graft)
  • Cryptonight v8 upx2 (uPlexa)
  • Cryptonight v8
  • Cryptonight heavy
  • Cryptonight haven (haven)
  • Cryptonight saber (bittube)
  • Cryptonight conceal (conceal)
  • Chukwa (trtl)
  • x16rv2 (rvn)
  • x16r (rvn)
  • x16s (pgn, xsh)
  • x16rt (veil, gin)
  • MTP (zcoin)
  • Cuckarood29 (grin)
  • Cuckatoo31 (grin)
  • Lyra2rev3 (vtc)
  • Lyra2z
  • Phi2 (lux, argoneum)

GPUs Supported and Tested:
  • RX 5700(XT)/5600(XT) for ethash and kawpow only
  • RX 580/570/480/470
  • RX Vega 64/56
  • RX 560/550
  • Radeon VII

Windows download available here: https://github.com/todxx/teamredminer/releases/download/0.7.5/teamredminer-v0.7.5-win.zip
Linux download available here: https://github.com/todxx/teamredminer/releases/download/0.7.5/teamredminer-v0.7.5-linux.tgz
Brief readme available here: https://github.com/todxx/teamredminer

API: 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.

Software Requirements:
  • For chukwa, mtp, cryptonight algos and lyra2rev3 on linux, only amdgpu-pro drivers are supported. Version 18.30 or newer is needed for Vegas. ROCm is not supported.

This miner includes the following dev fees:
  • Ethash on Polaris GPUs: 0.75%
  • Ethash on all other GPUs: 1.0%
  • Kawpow: 2.0%
  • Cryptonight R: 2.5%
  • Cryptonight v8 turtle: 2.5%
  • Cryptonight v8 half: 2.5%
  • Cryptonight v8 double: 2.5%
  • Cryptonight v8 reverse waltz: 2.5%
  • Cryptonight v8 upx2: 2.5%
  • Cryptonight v8: 2.5%
  • Cryptonight heavy: 2.5%
  • Cryptonight haven: 2.5%
  • Cryptonight saber: 2.5%
  • Cryptonight conceal: 2.5%
  • Chukwa 2.5%
  • x16rv2 2.5%
  • x16r 2.5%
  • x16s 2.5%
  • x16rt 2.5%
  • MTP 2.5%
  • Cuckarood29 2.5%
  • Cuckatoo31 2.5%
  • Lyra2rev3: 2.5%
  • Lyra2z: 3%
  • Phi2: 3%

For reporting bugs and/or for features requests please make a post here and we'll do our best to respond.
Any feedback would be appreciated.

Changes in v0.7.5
  • Fixed broken optimizations for kawpow in 0.7.4.

Changes 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.

Changes in v0.7.3
  • Emergency patch for 4GB cards to handle a few more ETC epochs.
      A more complete patch is coming out shortly.

Changes 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.

Changes in v0.7.1
  • Fixed issue with VII ethash/kawpow on windows.

Changes 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.

Changes 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.

Changes in v0.6.0
  • Added ethash algo support.
  • Relaxed ssl/tls cert chain verification.

Changes in v0.5.9
  • Added x16rv2 for the upcoming Ravencoin fork.
  • Optimization work on x16r: +8-10% hashrate depending on clocks.
  • Optimization work on x16r: mem clock no longer as important.
  • Issue fix: kernels split into multiple binaries to fix linux amdgpu-pro driver issues.

Changes in v0.5.8
  • Added Chukwa-512 algo For Turtlecoin (trtl_chukwa).
  • Issue fix: kernels not loaded properly for Conceal.
  • Issue fix: added logic for pool reconnect on N rejected shares in a row (see --pool_max_rejects=N).

Changes in v0.5.7
  • Added CN conceal algo for Conceal (CCX).
  • Added cuckarood29 algo for grin.

Changes in v0.5.6
  • MTP improvements for Vega and Polaris (+1-3% hashrate, improved efficiency, esp Polaris)

Changes in v0.5.5
  • Added cuckatoo31 algo for grin.

Changes in v0.5.4
  • Fixed API bug for MTP, crashing when using Awesome Miner.
  • Small MTP improvements, mostly for Polaris.

Changes in v0.5.3
  • Added MTP algo for Zcoin/XZC (please read MTP_MINING.txt before mining).
  • Further small stabilization fixes for CN variants, primarily 4MB algos.

Changes in v0.5.2
  • Bugfix release only, no new added algos or features.
  • Fix for 1-2% degraded hashrate on Radeon VIIs in some scenarios.
  • Fix for Radeon VII allocation bug, causing hw errs.
  • Fix for allocation bug causing crashes for some drivers and gpus.

Changes in v0.5.1
  • Added better support for CN intensities 16*15, use --allow_large_alloc under Linux.
  • Added --no_ntime_roll for mining x16rt on e.g. bsod.pw.
  • Added Tonga device recognition.
  • Better error reporting for pool communication issues.

Changes in v0.5.0
  • Added cryptonight 4MB variants: heavy, haven and saber.
  • Added x16 algo suite: x16r, x16s, x16rt (both gin and veil).
  • Auto-tuning mode for all CN variants, see bundled guide.
  • Manual key-driven CN tuning mode available inside the miner.
  • Additional data in miner stats console output.
  • Watchdog now detecting single stuck thread when mining CN.
  • Fix: in rare cases, poolside hash for compute algos (lyra2z, phi2, lyra2rev3) only reached ~95% of expected value.

Changes in v0.4.5
  • Added cryptonight v8 upx2 for the uPlexa coin fork.
  • Reworked init procedure, added retry logic on comm errors.
  • Added section on temps to the CN_MAX_YOUR_VEGA guide.
  • Added a new howto MAP_YOUR_GPUS describing how to map gpus between miner/tools/registry.

Changes in v0.4.4
  • Added * mode specifically for modded timings on Vega GPUs. Use with e.g. --cn_config=15*15. This mode is now the default for Vegas.
  • Introduced slow start/ramp-up. Threads increase their workload slowly at start or restart after e.g. a network outage.
  • Added interleave adjustment logic. Readjusts the two threads per gpu over time to make sure they don't gravitate and get stuck.
  • Added support for forcing colors (--force_color) for windows redirected consoles (git bash, cygwin, node.js).
  • Added hotkey menu system (show stats, enable/disable gpu).

Changes in v0.4.3
  • Added cryptonight v8 turtle (--algo cnv8_trtl) algo for coins such as turtle coin and loki.
  • Added support for running CN mining single-threaded using Y+0 configurations.
  • Changed the auto config mode for Radeon VII to L30+0 as a temporary setting.

Changes in v0.4.2
  • Added cryptonight v8 half (--algo cnv8_half) algo for coins such as stellite and masari.
  • Added cryptonight v8 double (--algo cnv8_dbl) algo for coins such as x-cash.
  • Added cryptonight v8 reverse waltz (--algo cnv8_rwz) algo for coins such as graft.
  • Added support for running devices on multiple OpenCL platforms.
  • Fixed more issues with console colors on older windows versions.
  • Added more cpu verification optimization for CN/R. CN/R cpu usage should decrease ~70%.

Changes in V0.4.1
  • Removed server name verification for SSL connections. (Pools like supportxmr now work with SSL)
  • Fixed bug causing GPUs to fail to initialize on some systems.
  • Fixed bug causing GPUs to only run one thread (but display 2x hashrate)
  • Fixed bug where having GPU_MAX_WORKGROUP_SIZE set too high would cause GPUs to crash.
  • Fixed bug where older windows versions would get no console output.
  • Added work-around for driver bug in linux amdgpu-pro drivers resulting in low pool-side hash for polaris cards in rare cases.
  • Added some cpu verification optimizations.  CN/R cpu usage should decrease about 15%.

Changes in v0.4.0
  • Added cryptonight R support.  (--algo cnr)
  • Added support for ssl/tls pool connections using the stratum+ssl:// prefix.
  • Added colors (and an option to disable them).
  • Slight performance increase for lyra2rev3 (~0.5%).
  • Fix for occasional crashes when pool disconnects.
  • Added more messages regarding not being connected to dev pool.
  • Changed printing to not block mining progress if stdout writes block.

Changes in v0.3.10
  • Slight performace improvement for Vegas on lyra2rev3
  • Pool stratum protocol work-arounds for some pools, fixing duplicate share error.
  • Changed handling of unrecognized pool rpcs to be ignored instead of causing a reconnect.
  • Fix for duplicate shares on 480/580/Vega56 cards with lyra2rev3.

Changes in v0.3.9
  • Added support for lyra2rev3 on amdgpu-pro and windows. ROCm support coming in later version.
  • Fixed API bug with not reporting dead GPUs

Changes in v0.3.8
  • Added support for fan speed and temperatures.
  • Added watchdog function for gpu init stuck, dead gpu, over-temp gpu, and non-responding pool.
  • Added new optional 'L' config prefix for low-end cards like lexa/baffin for a 10+% speed-up on some cards
  • Added an option for writing out a log file.
  • Added cycling through multi-entry dns records when connecting to pools.
  • Added a pool-connect timeout.
  • Added measurement and displaying of pool response times.
  • Added support for 80-byte headers for Phi2 algo (for non-LUX coins).
  • Slightly tuned the '+' mode for polaris, some GPUs will show slight performance increase.
  • Fixed bug with API interface occasionally getting stuck.

Changes in v0.3.7
  • Redesigned GPU initialization, should now be less error prone.
  • Added clean shutdown to reduce driver/GPU crashes.
  • Added staggered GPU start-up to reduce GPU crashes.
  • Added CPU verification for CNv8 and associated --no_cpu_check option.
  • Fixed crash on pool authentication error.
  • Added --pool_broken_rpc work-around option for pools that violate json rpc spec.
  • Added option to reorder by PCIe bus numbers.
  • Added --list_devices option to show available devices.
  • Added changed stats formatting to indicate which numbers are accepted/rejected/hw-error shares.
  • Added uptime to stats.

Changes 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.

Changes in v0.3.5
  • Changed GPU initialization to be sequential by default and added --init_style option for faster init styles.
  • Fixed network buffer size issue preventing the use of very long usernames/passwords/rig_ids.
  • Added opencl platform auto-detection for AMD platforms when --platform is not specified.

Changes in v0.3.4
  • Added CryptoNight v8 (CNv2) support
  • Changed stats display to include pool hashrate and better formatting
  • Added parallel GPU initialization
  • Added output of submitted/accepted/rejected shares.
  • Changed hashrate reported to be full GPU hashrate (previously hashrate reported was after dev fee deduction)

Changes in v0.3.3
  • ROCm support reintroduced
  • API support based on the sgminer API
  • Improved GPU platform detection
  • PCIe bus id printed on startup and is available over API
  • Added option for periodic stats interval

Changes in v0.3.2
  • Added windows support/build
  • Added vega PAL driver support
  • Removed ROCm support (temporarily)
  • Removed libjansson dependency

Changes in v0.3.1
  • Fixed phi2 issues with rejected shares and low pool-side hashrate.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1591464984
Hero Member
*
Offline Offline

Posts: 1591464984

View Profile Personal Message (Offline)

Ignore
1591464984
Reply with quote  #2

1591464984
Report to moderator
1591464984
Hero Member
*
Offline Offline

Posts: 1591464984

View Profile Personal Message (Offline)

Ignore
1591464984
Reply with quote  #2

1591464984
Report to moderator
acith
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
September 13, 2018, 01:22:38 PM
 #2

I update teamredviwer on my ethos 1.3.2 but speed is same as tdxminer 0.2.2 about 3.51 Mhz.  

This command to run

 /opt/miners/tdxminer/teamredminer -a lyra2z -o stratum+tcp://alien-mining-pool.com:4560 -u CTRMseqndNj5txpaYT8RWX5eJqMvdqfV5n.tongEth -p x

https://www.img.live/images/2018/09/13/ethor_teamredminer.png

Why? 
N2DCRYPT
Jr. Member
*
Offline Offline

Activity: 138
Merit: 5


View Profile
September 13, 2018, 01:31:42 PM
 #3

Kerney666! I was wondering how long you'd stay mining Lyra2z under the radar  Grin

Everyone is still waiting for Windows support due to the reduced power draw opportunities with the PPT registry mods. Doing this is Linux is still a nightmare.

Profitability has gone down a lot though; lots of hashrate migration from other coins, as you predicted. Which is probably why you've reappeared and have your name on a release  Roll Eyes

I know you previously mentioned concern with GPL licenses or what not. The dev of MKXminer apparently doesn't have any such concern, and he just released a lyra2z mod of his miner. Your previously mentioned hashrates are much more competitive, but he will have some draw simply because his is available for Windows.
kerney666
Member
**
Offline Offline

Activity: 574
Merit: 84


View Profile
September 13, 2018, 02:19:01 PM
 #4

@acith: I apologize, we could have been much more transparent in this regard. The only difference is the much higher clocks in the benchmark to match what (in our experience) people are actually running with. There has been no work on the lyra2z kernel in this release, the addition of phi2 is the main change. Sorry if this was misleading.

@N2DCRYPT: we will be releasing a Windows version with these kernels shortly. This miner is written completely from scratch, not violating a single license, which is also why it's lacking some of the standard features you would expect. The mkxminer release is a mystery. In my analysis, his lyra2z kernel run at 7.4 MH/s _before_ dev fee, then he uses sgminer's load balancing for his dev pool, but no one gets the numbers he has posted. It seems to me he is running with 15-20% dev fee and the numbers he posted are rather the raw numbers.
N2DCRYPT
Jr. Member
*
Offline Offline

Activity: 138
Merit: 5


View Profile
September 13, 2018, 02:37:10 PM
 #5

@acith: I apologize, we could have been much more transparent in this regard. The only difference is the much higher clocks in the benchmark to match what (in our experience) people are actually running with. There has been no work on the lyra2z kernel in this release, the addition of phi2 is the main change. Sorry if this was misleading.

@N2DCRYPT: we will be releasing a Windows version with these kernels shortly. This miner is written completely from scratch, not violating a single license, which is also why it's lacking some of the standard features you would expect. The mkxminer release is a mystery. In my analysis, his lyra2z kernel run at 7.4 MH/s _before_ dev fee, then he uses sgminer's load balancing for his dev pool, but no one gets the numbers he has posted. It seems to me he is running with 15-20% dev fee and the numbers he posted are rather the raw numbers.


@kerney666

Wonderful! I'm excited to put it to the test and will keep tabs on this thread. There are enough other tools in windows to make up for any standard features in miner (such as temp monitoring, core and mem clocking, etc.), so don't think that's as much of a concern for windows miners, and I hope you won't delay any release because of that.

That makes sense in regard to MKX; his prior Lyra2rev2 miner had lower apparent hashrate in the miner because the rest was going to devfee. If he accidently posted the real numbers, the difference is probably also going to dev fee (which makes for a pretty high devfee %!).

Also, I have to ask, and not trying to tread on any toes, just seeking clarity: on your prior thread you mentioned the possibility of Vega 64's with up to 10.5 MH/s using your GCN ASM kernel. Are the currently lower posted numbers due to: 1. devfee for future windows release actually being >3%; 2. current kernel used is not as powerful as your prior kernel; 3. numbers posted will be updated in the future for a possibly faster assembly kernel?? (hope it's 3  Grin)

Thanks for responding, good to see you in the forum again!  Smiley

todxx
Member
**
Offline Offline

Activity: 169
Merit: 67


View Profile
September 14, 2018, 09:49:08 AM
 #6

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.
dragonmike
Hero Member
*****
Offline Offline

Activity: 1190
Merit: 556


VEIL - PRIVACY WITHOUT COMPROMISE


View Profile
September 14, 2018, 11:57:17 AM
 #7

The mkxminer release is a mystery. In my analysis, his lyra2z kernel run at 7.4 MH/s _before_ dev fee, then he uses sgminer's load balancing for his dev pool, but no one gets the numbers he has posted. It seems to me he is running with 15-20% dev fee and the numbers he posted are rather the raw numbers.
Annoying as well is the fact he drops his (buggy) miner onto the forums, and the hashrate people achieve is quite a bit off what he claims... and then he disappears.



▄▄                                  ▄▄
 ███▄                            ▄███
  ██████                      ██████
   ███████                  ███████
    ███████                ███████
     ███████              ███████
      ███████            ███████
       ███████▄▄      ▄▄███████
        ██████████████████████
         ████████████████████
          ██████████████████
           ████████████████
            ██████████████
             ███████████
              █████████
               ███████
                █████
                 ██
                  █
veil|     PRIVACY     
     WITHOUT COMPROMISE.       
▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂
|   NO ICO. NO PREMINE. 
   X16RT GPU Mining. Fair distribution.   
|      The first Zerocoin-based Cryptocurrency       
   WITH ALWAYS-ON PRIVACY.   
|



                   ▄▄████
              ▄▄████████▌
         ▄▄█████████▀███
    ▄▄██████████▀▀ ▄███▌
▄████████████▀▀  ▄█████
▀▀▀███████▀   ▄███████▌
      ██    ▄█████████
       █  ▄██████████▌
       █  ███████████
       █ ██▀ ▀██████▌
       ██▀     ▀████
                 ▀█▌




   ▄███████
   ████████
   ███▀
   ███
██████████
██████████
   ███
   ███
   ███
   ███
   ███
   ███




     ▄▄█▀▀ ▄▄▄▄▄▄▄▄ ▀▀█▄▄
   ▐██▄▄██████████████▄▄██▌
   ████████████████████████
  ▐████████████████████████▌
  ███████▀▀▀██████▀▀▀███████
 ▐██████     ████     ██████▌
 ███████     ████     ███████
▐████████▄▄▄██████▄▄▄████████▌
▐████████████████████████████▌
 █████▄▄▀▀▀▀██████▀▀▀▀▄▄█████
  ▀▀██████          ██████▀▀
      ▀▀▀            ▀▀▀
schriss
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
September 14, 2018, 12:21:07 PM
 #8

Eagerly waiting for Windows Support, hoping to get similar speeds as Linux miners on my Vegas 64.
edwinosky
Jr. Member
*
Offline Offline

Activity: 69
Merit: 1


View Profile
September 14, 2018, 02:52:07 PM
 #9

doing tests with this miner, here I leave the results
GPU0 Asus rogstrix evo rx560 4gb
GPU1 MSI gaming rx580 4gb
GPU2 MSI armor rx480 4gb
GPU3 MSI Armor rx470 4gb
GPU4 MSI Amor 570 8gb

these are the results when extracting LUXCOIN

[2018-09-14 10:38:29] Stats GPU 0 - phi2: 2.220Mh/s (2.216Mh/s) 
[2018-09-14 10:38:29] Stats GPU 1 - phi2: 4.766Mh/s (4.752Mh/s) 
[2018-09-14 10:38:29] Stats GPU 2 - phi2: 4.355Mh/s (4.346Mh/s) 
[2018-09-14 10:38:29] Stats GPU 3 - phi2: 4.279Mh/s (4.274Mh/s) 
[2018-09-14 10:38:29] Stats GPU 4 - phi2: 4.223Mh/s (4.274Mh/s) 
[2018-09-14 10:38:29] Stats Total - phi2: 19.844Mh/s (19.861Mh/s)

but if I try to extract other coins from the something phi2 throws an error

Pool eu.bsod.pw successfully subscribed.
[2018-09-14 10:50:51] Pool eu.bsod.pw authorization succeeded.
[2018-09-14 10:50:51] Pool eu.bsod.pw set difficulty to 1.000000
[2018-09-14 10:50:51] Pool eu.bsod.pw failed to parse server rpc: {"id":null,"method":"mining.notify","params":["910","17747d5c843cbfa080ced42945ff11a0db3b1d54e64124b210228d4600000000","01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff1b02aa3b04a6ca9b5b08","62736f642e736f6c6f00000000000232c4eb0b000000001976a914f47f5396f1b4e8e662d1fad73 07b32805d84994788ac4ba6e111000000001976a9148810a5dac6c6216192420ae23f6f48a4fdf6 6b9188ac00000000",["6e42aeaebc5e15d6bd3f7fabb4d6f84addeb526e424b78376f274a9f16297cc4"],"20000000","1c123e5a","5b9bcaa6",true]}
kerney666
Member
**
Offline Offline

Activity: 574
Merit: 84


View Profile
September 14, 2018, 04:10:59 PM
 #10

@edwinosky To the best of my knowledge there is only one phi2 coin, LUX. The stratum data in your error message does not look like LUX, it's missing two fields for the extended headers. Can you provide your full command line when you get that error message? I'm guessing you are mining some other algo on BSOD than phi2. I've tested against both ports 6667 and 11518 on eu.bsod.pw for phi2, seems to work fine.
edwinosky
Jr. Member
*
Offline Offline

Activity: 69
Merit: 1


View Profile
September 14, 2018, 05:16:14 PM
 #11

./teamredminer -a phi2 -o stratum+tcp://eu.bsod.pw:2436 -u AX8iyvLTQL16DLSSm95ry8cKwfqvorTpfs -p c=MIA

I try to extract MixAir to take advantage of the low difficulty but I throw that error, I have already tried in other pools and also the same...
fluxy12
Jr. Member
*
Offline Offline

Activity: 143
Merit: 1


View Profile
September 14, 2018, 05:19:35 PM
 #12

Please can you do a custom miner on hiveos ?
kerney666
Member
**
Offline Offline

Activity: 574
Merit: 84


View Profile
September 14, 2018, 06:45:57 PM
 #13

@edwinosky

Ah, look at that, another phi2 coin. Ok, so we need to release a new version that supports both 80 bytes and 144 bytes block header for phi2 in order to support MIA. Will keep you posted.
PKBO
Newbie
*
Offline Offline

Activity: 120
Merit: 0


View Profile
September 14, 2018, 06:50:13 PM
 #14

Nice to see you back td.
edwinosky
Jr. Member
*
Offline Offline

Activity: 69
Merit: 1


View Profile
September 14, 2018, 07:05:04 PM
 #15

@kerney666 thank you friend, I'll be attentive to updates
SigiSinatra
Newbie
*
Offline Offline

Activity: 44
Merit: 0


View Profile
September 14, 2018, 10:49:19 PM
 #16

Seems like MCLK is irrelevant for phi2 just like for lyra2z ?
kerney666
Member
**
Offline Offline

Activity: 574
Merit: 84


View Profile
September 14, 2018, 11:28:43 PM
 #17

@SigiSinatra

Memclk is a tad more important for phi2, but really not much. You could potentially lose a few pct points by downclocking it too much. On the other hand, a few saved watts might be the better choice, YMMV. Testing on your own cards with a wattmeter and knowing your $/kwh price is probably the best way to go.
5BTC
Copper Member
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
September 15, 2018, 09:56:46 PM
 #18

Are you guys planning on optimizing lyra2z any further in this miner?
Blazin
Newbie
*
Offline Offline

Activity: 44
Merit: 0


View Profile
September 18, 2018, 01:25:56 AM
 #19

Nice to have you back, todxx. I thought you had abandoned your miner.

My Vega 64 gets 6.5 MH. I also have performance intentionally restricted to make it run cooler (any significant amount of fan noise just annoys everyone in my house), so that number is probably lower than what other people get.
Dima05
Newbie
*
Offline Offline

Activity: 82
Merit: 0


View Profile
September 18, 2018, 10:24:46 AM
 #20

Nice to have you back, todxx. I thought you had abandoned your miner.

My Vega 64 gets 6.5 MH. I also have performance intentionally restricted to make it run cooler (any significant amount of fan noise just annoys everyone in my house), so that number is probably lower than what other people get.

can I have something with my hands.
but my speed has remained the same. 580-4gb = 3.3-3.5
single + phi
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!