Bitcoin Forum
May 07, 2024, 05:21:26 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 [87] 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 ... 150 »
  Print  
Author Topic: [ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More  (Read 211398 times)
livada
Newbie
*
Offline Offline

Activity: 417
Merit: 0


View Profile WWW
July 20, 2019, 06:11:51 PM
 #1721

Thanks man! Working properly  Cool

teamredminer.exe -a cn_haven -o stratum+tcp://YOURPOOL -u YOURWALLET -p YOURMINER --platform=0 --init_style=3 -d 0,1,2,3 (I have 4 GPUs) --cn_config 7+7:CBB,7+7:CAB,7+7:CBB,7+7:CAB (best config for my RX570s)

Huh how this work properly for you? you have vega card.this setings have to small HR for vega.

try this : 16+14:AAA or  15+15:CBB

teamredminer.exe -a cn_haven -o stratum+tcp://YOURPOOL -u YOURWALLET -p YOURMINER --platform=0 --init_style=3 -d 0,1,2,3 (I have 4 GPUs) --cn_config 16+14:AAA,16+14:AAA,16+14:AAA,16+14:AAA

My config is for RX570s after auto tuning with 0.5.3 version, Vegas use different settings because they are much more powerfull.

i not ask you. see my post .i quote hmgp he have vega card and i ask how this setngs work fine vith vega. why you answer i dont now.
1715059286
Hero Member
*
Offline Offline

Posts: 1715059286

View Profile Personal Message (Offline)

Ignore
1715059286
Reply with quote  #2

1715059286
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715059286
Hero Member
*
Offline Offline

Posts: 1715059286

View Profile Personal Message (Offline)

Ignore
1715059286
Reply with quote  #2

1715059286
Report to moderator
wacholek
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
July 23, 2019, 01:39:36 PM
 #1722

@todxx, Hello, When will TRM support turtle's new algo "chukwa"  and loki's new algo "RandmXL"?

Hi! We're currently working on other algos. For Turtle, we might take a swing at chukwa at some point. For Loki, and any other RandomX-derived algo, I don't see us spending the time, there's no point producing gpu code that no one would run.

Rondom X will be used by many coins: Monero; Graft (GRFT) is considering, Triton-SAO (XTRI) is considering and others will follow.

For Turtlecoin and its algo, it shouldn't be forgotten that TRTL is the 3rd most forked CN coin (After Bytecoin and Monero), so smaller projects should also adopt chukwa.

Unfortunately, the nr of projects using an algo is irrelevant when the returns on a Vega 64 are -90% of a Ryzen 3900x, and just wait for the next gen Threadripper... Instruction caches are blown up, SIMD parallelism is close to impossible to utilize, caches are much too small to support the chosen L1/L2/L3 hierarchy, just to mention three major mismatches between the algo and how a GPU is constructed. People need to stop dreaming about RandomX on gpus.


Not even starting to consider GPU for Random-X, maybe I confused you. My bads. Point is, integrate Random-X fur CPUs because a lot of projects will switch to it.


That could be a major improvement in TeamRedMiner functionality. Joined mining CPU-RandomX and GPU-Grincuckatoo31 or CPU/GPU UPX2 mining since I think for now the most profitable CPU algo. I bet there is a room for improvement over xmrig-upx.
issie81
Hero Member
*****
Offline Offline

Activity: 760
Merit: 500

CryptoZilla


View Profile
July 23, 2019, 07:15:46 PM
 #1723

Any word on hashrate MTP vega 56 on 0.5.6?
kerney666
Member
**
Offline Offline

Activity: 658
Merit: 86


View Profile
July 23, 2019, 10:11:35 PM
 #1724

Any word on hashrate MTP vega 56 on 0.5.6?

Hi! You're in the wrong thread, I did post a few benchmarks vs the zcoin sgminer in our compute thread here: https://bitcointalk.org/index.php?topic=5027811.msg51894635#msg51894635

However, those benchmarks are at higher clocks to not penalize any specific miner in the benchmark. I would clock down to hit a better efficiency, but it takes good knowledge on how to play the Vega. A few quick tests on a V56@64 ref, at-the-wall readings:

1407@900, 1107@900: 3.12 MH/s, ~230W
1212@850,  800@850: 2.69 MH/s, ~180W

Now for the kicker config (imho) for this card. You need a Powerplay table that sets 1150@800mV for core p-state 1 and 500@800mV for mem p-state, then lock the gpu in p-state 1 for core+mem. This lowers the soc clk significantly as well, making it possible to run stable at 800mV.

1150@800,  500@800: 2.78 MH/s, ~170W
Rakly3
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
July 24, 2019, 01:32:37 AM
Last edit: July 24, 2019, 02:55:43 AM by Rakly3
 #1725

Huh how this work properly for you? you have vega card.this setings have to small HR for vega.

try this : 16+14:AAA or  15+15:CBB

teamredminer.exe -a cn_haven -o stratum+tcp://YOURPOOL -u YOURWALLET -p YOURMINER --platform=0 --init_style=3 -d 0,1,2,3 (I have 4 GPUs) --cn_config 16+14:AAA,16+14:AAA,16+14:AAA,16+14:AAA
Try 14*13 and 13*13
all my vega 56@64 do 2200+ h/s CNr. A Vega 56 with 64 bios still only has 56 CU's.
1200 clk, 1050 mem, 860mV (one card needs 875mV, so don't fixate too much on the exact number. I started tuning them all at 900mV (Samsung)
If they are actual real 64's, then 16*14 should work fine.

--cn_config=14*13 --auto_tune=SCAN --auto_tune_runs=2
I notice from your post you are using the + tweak, Vega work best with *
Nonetheless, SCAN will go through every possible tweak for you.
You MUST use cn_config= , without = your custom settings don't apply and the miner will just do a quick short tune with default settings.
The helpfiles that come with TRM are currently somewhat outdated.
Also, if all your cards use the exact same tweak, you don't have set it for every device. Smiley
Make sure to set the runs to 2, else it's gonna take a whole day of tuning (6 runs default) at values below optimal.



My RX460 2G do, with TRM 0.5.6 + mmpOS over 500h/s
(Hynix and Samsung mem, 1000mV, lower than that they all at some point fail. Straps copy/pasted ofcourse.)
4+3 for 16CU and 3+3 for 14CU
4G cards could try 5+4 and 4+4
:BAB is a good default tweak on these cards.
livada
Newbie
*
Offline Offline

Activity: 417
Merit: 0


View Profile WWW
July 24, 2019, 09:18:26 AM
Last edit: July 24, 2019, 09:29:25 AM by livada
 #1726

Huh how this work properly for you? you have vega card.this setings have to small HR for vega.

try this : 16+14:AAA or  15+15:CBB

teamredminer.exe -a cn_haven -o stratum+tcp://YOURPOOL -u YOURWALLET -p YOURMINER --platform=0 --init_style=3 -d 0,1,2,3 (I have 4 GPUs) --cn_config 16+14:AAA,16+14:AAA,16+14:AAA,16+14:AAA
Try 14*13 and 13*13
all my vega 56@64 do 2200+ h/s CNr. A Vega 56 with 64 bios still only has 56 CU's.
1200 clk, 1050 mem, 860mV (one card needs 875mV, so don't fixate too much on the exact number. I started tuning them all at 900mV (Samsung)
If they are actual real 64's, then 16*14 should work fine.

--cn_config=14*13 --auto_tune=SCAN --auto_tune_runs=2
I notice from your post you are using the + tweak, Vega work best with *
Nonetheless, SCAN will go through every possible tweak for you.
You MUST use cn_config= , without = your custom settings don't apply and the miner will just do a quick short tune with default settings.
The helpfiles that come with TRM are currently somewhat outdated.
Also, if all your cards use the exact same tweak, you don't have set it for every device. Smiley
Make sure to set the runs to 2, else it's gonna take a whole day of tuning (6 runs default) at values below optimal.



My RX460 2G do, with TRM 0.5.6 + mmpOS over 500h/s
(Hynix and Samsung mem, 1000mV, lower than that they all at some point fail. Straps copy/pasted ofcourse.)
4+3 for 16CU and 3+3 for 14CU
4G cards could try 5+4 and 4+4
:BAB is a good default tweak on these cards.

you not see this: ? teamredminer.exe -a cn_haven

wee talk to hAVEn algo not  cnr.
in haveven all may vega(hynix) on SCAN give + for best  results not *
samsung vega give identical with + and *
i use --cn_config= . this is only copy paste for other post(my mistake)
Rakly3
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
July 24, 2019, 09:43:32 PM
 #1727

you not see this: ? teamredminer.exe -a cn_haven

Sorry no, I didn't.
It won't happen again!! ;-)
DonFreddi
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
July 28, 2019, 12:59:50 PM
 #1728

My RX460 2G do, with TRM 0.5.6 + mmpOS over 500h/s
(Hynix and Samsung mem, 1000mV, lower than that they all at some point fail. Straps copy/pasted ofcourse.)
4+3 for 16CU and 3+3 for 14CU
4G cards could try 5+4 and 4+4
:BAB is a good default tweak on these cards.

My fanless 460 2G too, makes my 580 look stupid lol.
emaugust
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
July 30, 2019, 12:43:47 AM
 #1729

Does this miner support algo switching as necessary for the MoneroOcean pool?
GKumaran
Member
**
Offline Offline

Activity: 204
Merit: 10


View Profile
July 30, 2019, 03:44:57 AM
 #1730

Check this out : https://github.com/Kerney666/meta-miner
Readme : https://github.com/Kerney666/meta-miner/blob/master/TRM-HOWTO.txt
kerney666
Member
**
Offline Offline

Activity: 658
Merit: 86


View Profile
July 30, 2019, 12:42:11 PM
 #1731


Note: this has also been merged into MoneroOcean's original repo for meta-miner, packaged properly in releases. It can be found here: https://github.com/MoneroOcean/meta-miner
HughHashner
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
July 30, 2019, 12:42:30 PM
 #1732

Does this miner support algo switching as necessary for the MoneroOcean pool?

Actually kerney's changes have been checked into the master branch now

https://github.com/MoneroOcean/meta-miner

I use MetaMiner to run TRM for all the algos it supports & XMRig-AMD for the ones it doesn't.
micax1
Hero Member
*****
Offline Offline

Activity: 708
Merit: 502


View Profile
August 03, 2019, 09:54:33 AM
 #1733

guys,
any suggestion on how to fix:

Code:
[2019-08-03 12:52:06] Auto-detected AMD OpenCL platform 0
[2019-08-03 12:52:07] Initializing GPU 0.
[2019-08-03 12:52:08] Initializing GPU 1.
[2019-08-03 12:52:09] Initializing GPU 2.
[2019-08-03 12:52:09] Initializing GPU 3.
[2019-08-03 12:52:10] Initializing GPU 4.
[2019-08-03 12:52:11] Initializing GPU 5.
[2019-08-03 12:52:12] Initializing GPU 6.
[2019-08-03 12:52:13] Initializing GPU 7.
[2019-08-03 12:52:14] Initializing GPU 8.
[2019-08-03 12:52:14] Initializing GPU 9.
[2019-08-03 12:52:15] Initializing GPU10.
[2019-08-03 12:52:21] Comm buf exit code timeout (fffffffe/8279/1364128554/1364128554/00000000).
[2019-08-03 12:52:21] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 12:52:26] Comm buf exit code timeout (fffffffe/8279/1963683322/1963683322/00000000).
[2019-08-03 12:52:26] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 12:52:32] Comm buf exit code timeout (fffffffd/8279/2128370346/2128370346/00000000).
[2019-08-03 12:52:32] Warning: failed to initialize device number 10 (-42), retrying.

Thanks.
micax1
Hero Member
*****
Offline Offline

Activity: 708
Merit: 502


View Profile
August 03, 2019, 11:10:00 AM
 #1734

that`s my typical init:

Code:
Miner:   teamredminer
Version: 0.5.6

          Team Red Miner version 0.5.6
[2019-08-03 14:01:50] Auto-detected AMD OpenCL platform 0
[2019-08-03 14:01:51] Initializing GPU 0.
[2019-08-03 14:01:52] Initializing GPU 1.
[2019-08-03 14:01:53] Initializing GPU 2.
[2019-08-03 14:01:54] Initializing GPU 3.
[2019-08-03 14:01:55] Initializing GPU 4.
[2019-08-03 14:01:55] Initializing GPU 5.
[2019-08-03 14:01:56] Initializing GPU 6.
[2019-08-03 14:01:57] Initializing GPU 7.
[2019-08-03 14:01:58] Initializing GPU 8.
[2019-08-03 14:01:59] Initializing GPU 9.
[2019-08-03 14:02:04] Comm buf exit code timeout (fffffffe/8279/-1320809326/-1320809326/00000000).
[2019-08-03 14:02:04] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:10] Comm buf exit code timeout (fffffffe/8279/1797097106/1797097106/00000000).
[2019-08-03 14:02:10] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:15] Comm buf exit code timeout (fffffffe/8279/978782290/978782290/00000000).
[2019-08-03 14:02:15] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:21] Comm buf exit code timeout (fffffffe/8279/-1271224750/-1271224750/00000000).
[2019-08-03 14:02:21] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:26] Comm buf exit code timeout (fffffffe/8279/-325876078/-325876078/00000000).
[2019-08-03 14:02:26] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:32] Comm buf exit code timeout (fffffffe/8279/-1610001454/-1610001454/00000000).
[2019-08-03 14:02:32] Warning: failed to initialize device number 9 (-42), retrying.
] Comm buf exit code timeout [2019-08-03 14:02:37] Comm buf exit code timeout (fffffffe/8279/-799468782/-799468782/00000000).
[2019-08-03 14:02:37] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:43] Comm buf exit code timeout (fffffffe/8279/-1791289070/-1791289070/00000000).
[2019-08-03 14:02:43] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:48] Comm buf exit code timeout (fffffffe/8279/301566738/301566738/00000000).
[2019-08-03 14:02:48] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:54] Comm buf exit code timeout (fffffffe/8279/1666831058/1666831058/00000000).
[2019-08-03 14:02:54] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:54] Initialize retry attempt successful for device number 9, continuing.
[2019-08-03 14:02:54] Initializing GPU10.
[2019-08-03 14:03:00] Comm buf exit code timeout (fffffffe/8279/1994231994/1994231994/00000000).
[2019-08-03 14:03:00] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:05] Comm buf exit code timeout (fffffffe/8279/1427017386/1427017386/00000000).
[2019-08-03 14:03:05] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:11] Comm buf exit code timeout (fffffffe/8279/-325728470/-325728470/00000000).
[2019-08-03 14:03:11] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:16] Comm buf exit code timeout (fffffffe/8279/-1641368678/-1641368678/00000000).
[2019-08-03 14:03:16] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:22] Comm buf exit code timeout (fffffffe/8279/1826234794/1826234794/00000000).
[2019-08-03 14:03:22] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:27] Comm buf exit code timeout (fffffffe/8279/-1995357398/-1995357398/00000000).
[2019-08-03 14:03:27] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:33] Comm buf exit code timeout (fffffffe/8279/-2145515174/-2145515174/00000000).
[2019-08-03 14:03:33] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:38] Comm buf exit code timeout (fffffffe/8279/493747626/493747626/00000000).
[2019-08-03 14:03:38] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:44] Comm buf exit code timeout (fffffffe/8279/663788218/663788218/00000000).
[2019-08-03 14:03:44] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:49] Comm buf exit code timeout (fffffffd/8279/-1366668886/-1366668886/00000000).
[2019-08-03 14:03:49] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:55] Comm buf exit code timeout (fffffffd/8279/1025767818/1025767818/00000000).
[2019-08-03 14:03:55] Failed to initialize device idx 10 (-42)
[2019-08-03 14:03:55] Successful clean shutdown.

teamredminer exited, waiting to cooldown a bit

          Team Red Miner version 0.5.6
[2019-08-03 14:03:58] Auto-detected AMD OpenCL platform 0
[2019-08-03 14:03:59] Initializing GPU 0.
[2019-08-03 14:04:00] Initializing GPU 1.
[2019-08-03 14:04:01] Initializing GPU 2.
[2019-08-03 14:04:01] Initializing GPU 3.
[2019-08-03 14:04:02] Initializing GPU 4.
[2019-08-03 14:04:08] Comm buf exit code timeout (fffffffe/8279/1209154322/1209154322/00000000).
[2019-08-03 14:04:08] Warning: failed to initialize device number 4 (-42), retrying.
[2019-08-03 14:04:13] Comm buf exit code timeout (fffffffe/8279/1916155282/1916155282/00000000).
[2019-08-03 14:04:13] Warning: failed to initialize device number 4 (-42), retrying.
[2019-08-03 14:04:14] Initialize retry attempt successful for device number 4, continuing.
[2019-08-03 14:04:14] Initializing GPU 5.
[2019-08-03 14:04:15] Initializing GPU 6.
[2019-08-03 14:04:16] Initializing GPU 7.
[2019-08-03 14:04:17] Initializing GPU 8.
[2019-08-03 14:04:17] Initializing GPU 9.
[2019-08-03 14:04:23] Comm buf exit code timeout (fffffffe/8279/1175757266/1175757266/00000000).
[2019-08-03 14:04:23] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:04:28] Comm buf exit code timeout (fffffffe/8279/13725970/13725970/00000000).
[2019-08-03 14:04:28] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:04:34] Comm buf exit code timeout (fffffffe/8279/-1078895214/-1078895214/00000000).
[2019-08-03 14:04:34] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:04:39] Comm buf exit code timeout (fffffffe/8279/480017874/480017874/00000000).
[2019-08-03 14:04:39] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:04:40] Initialize retry attempt successful for device number 9, continuing.
[2019-08-03 14:04:40] Initializing GPU10.
[2019-08-03 14:04:41] Initializing GPU11.
[2019-08-03 14:04:42] Initializing GPU12.
[2019-08-03 14:04:43] Watchdog thread starting.
[2019-08-03 14:04:43] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, t - tuning mode, q - quit
[2019-08-03 14:04:43] Entered GPU ENABLE menu, press 0-9,A-F as the next key to enable gpu 0-15, or any other key to exit.
[2019-08-03 14:04:43] Exiting gpu enable sub-menu.
[2019-08-03 14:04:43] Entered GPU Tuning Mode menu, press 0-9,A-F as the next key to enable gpu 0-15.
[2019-08-03 14:04:43] Successfully initialized GPU 0: Polaris with 12 CU (PCIe 01:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Exiting gpu tuning sub-menu.
[2019-08-03 14:04:43] Entered GPU DISABLE menu, press 0-9,A-F as the next key to enable gpu 0-15.
[2019-08-03 14:04:43] GPU 4 is now disabled.
[2019-08-03 14:04:43] Entered GPU Tuning Mode menu, press 0-9,A-F as the next key to enable gpu 0-15.
[2019-08-03 14:04:43] Exiting gpu tuning sub-menu.
[2019-08-03 14:04:43] Entered GPU ENABLE menu, press 0-9,A-F as the next key to enable gpu 0-15, or any other key to exit.
[2019-08-03 14:04:43] Exiting gpu enable sub-menu.
[2019-08-03 14:04:43] Entered GPU Tuning Mode menu, press 0-9,A-F as the next key to enable gpu 0-15.
[2019-08-03 14:04:43] Exiting gpu tuning sub-menu.
[2019-08-03 14:04:43] Successfully initialized GPU 1: Polaris with 12 CU (PCIe 02:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 2: Polaris with 12 CU (PCIe 03:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 3: Polaris with 12 CU (PCIe 04:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 4: Polaris with 12 CU (PCIe 05:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 5: Polaris with 12 CU (PCIe 09:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 6: Polaris with 12 CU (PCIe 0b:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 7: Polaris with 12 CU (PCIe 0d:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 8: Polaris with 12 CU (PCIe 10:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 9: Polaris with 12 CU (PCIe 11:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU10: Polaris with 12 CU (PCIe 12:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU11: Polaris with 12 CU (PCIe 13:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU12: Polaris with 12 CU (PCIe 14:00.0) (CN 4+3:AAA)
[/size]


No CPU Usage/mining during that.

it starts in 2-3-4 attempts.. any ideas?
kerney666
Member
**
Offline Offline

Activity: 658
Merit: 86


View Profile
August 03, 2019, 04:03:25 PM
 #1735

that`s my typical init:

Code:
Miner:   teamredminer
Version: 0.5.6

          Team Red Miner version 0.5.6
[2019-08-03 14:01:50] Auto-detected AMD OpenCL platform 0
[2019-08-03 14:01:51] Initializing GPU 0.
[2019-08-03 14:01:52] Initializing GPU 1.
[2019-08-03 14:01:53] Initializing GPU 2.
[2019-08-03 14:01:54] Initializing GPU 3.
[2019-08-03 14:01:55] Initializing GPU 4.
[2019-08-03 14:01:55] Initializing GPU 5.
[2019-08-03 14:01:56] Initializing GPU 6.
[2019-08-03 14:01:57] Initializing GPU 7.
[2019-08-03 14:01:58] Initializing GPU 8.
[2019-08-03 14:01:59] Initializing GPU 9.
[2019-08-03 14:02:04] Comm buf exit code timeout (fffffffe/8279/-1320809326/-1320809326/00000000).
[2019-08-03 14:02:04] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:10] Comm buf exit code timeout (fffffffe/8279/1797097106/1797097106/00000000).
[2019-08-03 14:02:10] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:15] Comm buf exit code timeout (fffffffe/8279/978782290/978782290/00000000).
[2019-08-03 14:02:15] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:21] Comm buf exit code timeout (fffffffe/8279/-1271224750/-1271224750/00000000).
[2019-08-03 14:02:21] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:26] Comm buf exit code timeout (fffffffe/8279/-325876078/-325876078/00000000).
[2019-08-03 14:02:26] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:32] Comm buf exit code timeout (fffffffe/8279/-1610001454/-1610001454/00000000).
[2019-08-03 14:02:32] Warning: failed to initialize device number 9 (-42), retrying.
] Comm buf exit code timeout [2019-08-03 14:02:37] Comm buf exit code timeout (fffffffe/8279/-799468782/-799468782/00000000).
[2019-08-03 14:02:37] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:43] Comm buf exit code timeout (fffffffe/8279/-1791289070/-1791289070/00000000).
[2019-08-03 14:02:43] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:48] Comm buf exit code timeout (fffffffe/8279/301566738/301566738/00000000).
[2019-08-03 14:02:48] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:54] Comm buf exit code timeout (fffffffe/8279/1666831058/1666831058/00000000).
[2019-08-03 14:02:54] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:02:54] Initialize retry attempt successful for device number 9, continuing.
[2019-08-03 14:02:54] Initializing GPU10.
[2019-08-03 14:03:00] Comm buf exit code timeout (fffffffe/8279/1994231994/1994231994/00000000).
[2019-08-03 14:03:00] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:05] Comm buf exit code timeout (fffffffe/8279/1427017386/1427017386/00000000).
[2019-08-03 14:03:05] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:11] Comm buf exit code timeout (fffffffe/8279/-325728470/-325728470/00000000).
[2019-08-03 14:03:11] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:16] Comm buf exit code timeout (fffffffe/8279/-1641368678/-1641368678/00000000).
[2019-08-03 14:03:16] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:22] Comm buf exit code timeout (fffffffe/8279/1826234794/1826234794/00000000).
[2019-08-03 14:03:22] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:27] Comm buf exit code timeout (fffffffe/8279/-1995357398/-1995357398/00000000).
[2019-08-03 14:03:27] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:33] Comm buf exit code timeout (fffffffe/8279/-2145515174/-2145515174/00000000).
[2019-08-03 14:03:33] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:38] Comm buf exit code timeout (fffffffe/8279/493747626/493747626/00000000).
[2019-08-03 14:03:38] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:44] Comm buf exit code timeout (fffffffe/8279/663788218/663788218/00000000).
[2019-08-03 14:03:44] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:49] Comm buf exit code timeout (fffffffd/8279/-1366668886/-1366668886/00000000).
[2019-08-03 14:03:49] Warning: failed to initialize device number 10 (-42), retrying.
[2019-08-03 14:03:55] Comm buf exit code timeout (fffffffd/8279/1025767818/1025767818/00000000).
[2019-08-03 14:03:55] Failed to initialize device idx 10 (-42)
[2019-08-03 14:03:55] Successful clean shutdown.

teamredminer exited, waiting to cooldown a bit

          Team Red Miner version 0.5.6
[2019-08-03 14:03:58] Auto-detected AMD OpenCL platform 0
[2019-08-03 14:03:59] Initializing GPU 0.
[2019-08-03 14:04:00] Initializing GPU 1.
[2019-08-03 14:04:01] Initializing GPU 2.
[2019-08-03 14:04:01] Initializing GPU 3.
[2019-08-03 14:04:02] Initializing GPU 4.
[2019-08-03 14:04:08] Comm buf exit code timeout (fffffffe/8279/1209154322/1209154322/00000000).
[2019-08-03 14:04:08] Warning: failed to initialize device number 4 (-42), retrying.
[2019-08-03 14:04:13] Comm buf exit code timeout (fffffffe/8279/1916155282/1916155282/00000000).
[2019-08-03 14:04:13] Warning: failed to initialize device number 4 (-42), retrying.
[2019-08-03 14:04:14] Initialize retry attempt successful for device number 4, continuing.
[2019-08-03 14:04:14] Initializing GPU 5.
[2019-08-03 14:04:15] Initializing GPU 6.
[2019-08-03 14:04:16] Initializing GPU 7.
[2019-08-03 14:04:17] Initializing GPU 8.
[2019-08-03 14:04:17] Initializing GPU 9.
[2019-08-03 14:04:23] Comm buf exit code timeout (fffffffe/8279/1175757266/1175757266/00000000).
[2019-08-03 14:04:23] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:04:28] Comm buf exit code timeout (fffffffe/8279/13725970/13725970/00000000).
[2019-08-03 14:04:28] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:04:34] Comm buf exit code timeout (fffffffe/8279/-1078895214/-1078895214/00000000).
[2019-08-03 14:04:34] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:04:39] Comm buf exit code timeout (fffffffe/8279/480017874/480017874/00000000).
[2019-08-03 14:04:39] Warning: failed to initialize device number 9 (-42), retrying.
[2019-08-03 14:04:40] Initialize retry attempt successful for device number 9, continuing.
[2019-08-03 14:04:40] Initializing GPU10.
[2019-08-03 14:04:41] Initializing GPU11.
[2019-08-03 14:04:42] Initializing GPU12.
[2019-08-03 14:04:43] Watchdog thread starting.
[2019-08-03 14:04:43] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, t - tuning mode, q - quit
[2019-08-03 14:04:43] Entered GPU ENABLE menu, press 0-9,A-F as the next key to enable gpu 0-15, or any other key to exit.
[2019-08-03 14:04:43] Exiting gpu enable sub-menu.
[2019-08-03 14:04:43] Entered GPU Tuning Mode menu, press 0-9,A-F as the next key to enable gpu 0-15.
[2019-08-03 14:04:43] Successfully initialized GPU 0: Polaris with 12 CU (PCIe 01:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Exiting gpu tuning sub-menu.
[2019-08-03 14:04:43] Entered GPU DISABLE menu, press 0-9,A-F as the next key to enable gpu 0-15.
[2019-08-03 14:04:43] GPU 4 is now disabled.
[2019-08-03 14:04:43] Entered GPU Tuning Mode menu, press 0-9,A-F as the next key to enable gpu 0-15.
[2019-08-03 14:04:43] Exiting gpu tuning sub-menu.
[2019-08-03 14:04:43] Entered GPU ENABLE menu, press 0-9,A-F as the next key to enable gpu 0-15, or any other key to exit.
[2019-08-03 14:04:43] Exiting gpu enable sub-menu.
[2019-08-03 14:04:43] Entered GPU Tuning Mode menu, press 0-9,A-F as the next key to enable gpu 0-15.
[2019-08-03 14:04:43] Exiting gpu tuning sub-menu.
[2019-08-03 14:04:43] Successfully initialized GPU 1: Polaris with 12 CU (PCIe 02:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 2: Polaris with 12 CU (PCIe 03:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 3: Polaris with 12 CU (PCIe 04:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 4: Polaris with 12 CU (PCIe 05:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 5: Polaris with 12 CU (PCIe 09:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 6: Polaris with 12 CU (PCIe 0b:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 7: Polaris with 12 CU (PCIe 0d:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 8: Polaris with 12 CU (PCIe 10:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU 9: Polaris with 12 CU (PCIe 11:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU10: Polaris with 12 CU (PCIe 12:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU11: Polaris with 12 CU (PCIe 13:00.0) (CN 4+3:AAA)
[2019-08-03 14:04:43] Successfully initialized GPU12: Polaris with 12 CU (PCIe 14:00.0) (CN 4+3:AAA)


No CPU Usage/mining during that.

it starts in 2-3-4 attempts.. any ideas?

We have a special initialization procedure compared to other miners which is more sensitive to configured clocks etc. For pushed mem clocks, we sometimes get these retries before succeeding. You want those clocks for your mining though, so we had to add logic for handling failed inits with automatic retries. If mining is working fine after that, you're all good, although I know it might look a little weird with these error messages and retries.

Maybe I'm misinterpreting things though - are you saying it takes 2-3-4 attempts to get a "successful" start like the above, and you have to restart a nr of times manually to get there? Or, is it starting 100% of the time in the end, but with the errors and retry attempts in the logs above?
micax1
Hero Member
*****
Offline Offline

Activity: 708
Merit: 502


View Profile
August 05, 2019, 06:41:52 PM
 #1736

We have a special initialization procedure compared to other miners which is more sensitive to configured clocks etc. For pushed mem clocks, we sometimes get these retries before succeeding. You want those clocks for your mining though, so we had to add logic for handling failed inits with automatic retries. If mining is working fine after that, you're all good, although I know it might look a little weird with these error messages and retries.

Maybe I'm misinterpreting things though - are you saying it takes 2-3-4 attempts to get a "successful" start like the above, and you have to restart a nr of times manually to get there? Or, is it starting 100% of the time in the end, but with the errors and retry attempts in the logs above?


Well I wish it were every time like that... sometimes it never gets there.. and i have to restart..
but if you say that`s because of overclock - i can try to lower it a bit...
todxx (OP)
Member
**
Offline Offline

Activity: 176
Merit: 76


View Profile
August 05, 2019, 09:40:45 PM
 #1737

Team Red Miner v0.5.7 released

https://github.com/todxx/teamredminer/releases

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


This release brings a couple new algos: CN conceal and cuckarood29!

CN conceal is a bit picky about memory timings, so please checkout the CN_MAX_YOU_VEGA.txt doc before switching your rigs to it.
angelbbs
Full Member
***
Offline Offline

Activity: 1162
Merit: 209


View Profile
August 06, 2019, 04:52:23 AM
 #1738

Team Red Miner v0.5.7 released

https://github.com/todxx/teamredminer/releases

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


This release brings a couple new algos: CN conceal and cuckarood29!

CN conceal is a bit picky about memory timings, so please checkout the CN_MAX_YOU_VEGA.txt doc before switching your rigs to it.

How much memory is needed for cuckarood29?
RX 570 4GB not work on Win7 (Blockchain drivers)

[2019-08-06 07:50:40] Auto-detected AMD OpenCL platform 0
[2019-08-06 07:50:43] Initializing GPU 0.
[2019-08-06 07:50:43] OpenCL enqueue error: -55
[2019-08-06 07:50:43] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:43] OpenCL enqueue error: -55
[2019-08-06 07:50:43] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:43] OpenCL enqueue error: -55
[2019-08-06 07:50:43] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:44] OpenCL enqueue error: -55
[2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:44] OpenCL enqueue error: -55
[2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:44] OpenCL enqueue error: -55
[2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:44] OpenCL enqueue error: -55
[2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:44] OpenCL enqueue error: -55
[2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:45] OpenCL enqueue error: -55
[2019-08-06 07:50:45] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:45] OpenCL enqueue error: -55
[2019-08-06 07:50:45] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:45] OpenCL enqueue error: -55
[2019-08-06 07:50:45] Failed to initialize device idx 0 (-28)
[2019-08-06 07:50:45] Successful clean shutdown.
todxx (OP)
Member
**
Offline Offline

Activity: 176
Merit: 76


View Profile
August 06, 2019, 05:47:49 AM
 #1739

Team Red Miner v0.5.7 released

https://github.com/todxx/teamredminer/releases

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


This release brings a couple new algos: CN conceal and cuckarood29!

CN conceal is a bit picky about memory timings, so please checkout the CN_MAX_YOU_VEGA.txt doc before switching your rigs to it.

How much memory is needed for cuckarood29?
RX 570 4GB not work on Win7 (Blockchain drivers)

[2019-08-06 07:50:40] Auto-detected AMD OpenCL platform 0
[2019-08-06 07:50:43] Initializing GPU 0.
[2019-08-06 07:50:43] OpenCL enqueue error: -55
[2019-08-06 07:50:43] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:43] OpenCL enqueue error: -55
[2019-08-06 07:50:43] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:43] OpenCL enqueue error: -55
[2019-08-06 07:50:43] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:44] OpenCL enqueue error: -55
[2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:44] OpenCL enqueue error: -55
[2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:44] OpenCL enqueue error: -55
[2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:44] OpenCL enqueue error: -55
[2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:44] OpenCL enqueue error: -55
[2019-08-06 07:50:44] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:45] OpenCL enqueue error: -55
[2019-08-06 07:50:45] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:45] OpenCL enqueue error: -55
[2019-08-06 07:50:45] Warning: failed to initialize device number 0 (-28), retrying.
[2019-08-06 07:50:45] OpenCL enqueue error: -55
[2019-08-06 07:50:45] Failed to initialize device idx 0 (-28)
[2019-08-06 07:50:45] Successful clean shutdown.

My apologies, we should list somewhere that our c31 and c29 kernels currently only work on 8GB+ GPUs.
I thought that we had a much nicer message in place than the errors that were printed for you.
qwep1
Hero Member
*****
Offline Offline

Activity: 610
Merit: 500


View Profile
August 06, 2019, 06:09:16 AM
Last edit: August 06, 2019, 07:02:32 AM by qwep1
 #1740

how to run ccx Huh what command line

              ▄▄██▄▄
          ▄▄██████████▄▄
      ▄▄██████████████████▄▄
  ▄▄██████████▀▀ ▀▀██████████▄▄
▄█████████▀▀          ▀▀█████████▄
██████▀▀        ▄▄        ▀▀██████
██████      ▄▄██████▄▄      ██████
██████    ██████████████    ██████
██████    ██████████████    ██████
██████    ██████████████    ██████
██████      ▀▀██████▀▀      ██████
██████          ▀▀        ▄▄██████
▀█████    ▄▄          ▄▄█████████▀
   ▀▀█    ████▄▄ ▄▄██████████▀▀
          ████████████████▀▀
          ▀▀██████████▀▀
              ▀▀██▀▀
P H O R E

     █
    █
   █
  █
   █
    █
   █
  █
 █
    KryptKoin rebranded to Phore   
     █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █
PoS 3.0  -  Masternodes  -  Obfuscation


     █
    █
   █
  █
   █
    █
   █
  █
 █
.


            ▄▄██▄▄
        ▄▄██████████▄▄
    ▄▄████████▀▀████████▄▄
 ▄████████▀▀      ▀▀████████▄
▐█████▀▀              ▀▀█████▌
▐████       ▄▄██▄▄       ████▌
▐████    ▄██████████▄    ████▌
▐████    ████████████    ████▌
▐████    ▀██████████▀    ████▌
▐████       ▀▀██▀▀       ████▌
 ▀███                 ▄▄█████▌
    ▀    █▄▄      ▄▄████████▀
         █████▄▄████████▀▀
         ▀██████████▀▀
            ▀▀██▀▀
Pages: « 1 ... 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 [87] 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 ... 150 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!