SigiSinatra
Newbie
Offline
Activity: 50
Merit: 0
|
|
June 06, 2019, 02:03:58 PM |
|
Can you please add timerolling on/off option ? I can't use miner on some pools because off timerolling. Thank You.
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
June 06, 2019, 02:49:26 PM |
|
Can you please add timerolling on/off option ? I can't use miner on some pools because off timerolling. Thank You.
Interesting, can you PM an example? I’m guessing this might be x16rt?
|
|
|
|
SigiSinatra
Newbie
Offline
Activity: 50
Merit: 0
|
|
June 06, 2019, 03:30:29 PM Last edit: June 06, 2019, 04:56:52 PM by SigiSinatra |
|
Can you please add timerolling on/off option ? I can't use miner on some pools because off timerolling. Thank You.
Interesting, can you PM an example? I’m guessing this might be x16rt? Yes, I was trying to mine Veil (x16rt) on bsod pool. https://i.imgur.com/accBnkP.pngSome pool owners suggested to set timerolling off by default. So far, I can mine Veil only on one "small" pool with teamredminer. All other pools reject shares.
|
|
|
|
ku4eto
Jr. Member
Offline
Activity: 194
Merit: 4
|
|
June 06, 2019, 05:20:14 PM Last edit: June 06, 2019, 07:04:56 PM by ku4eto |
|
Kerney, the issue with the GPU dying, because of reaching 81*C continues. Miner API becomes unresponsive, and i gotta do hard reset, otherwise with a "emergency" reset, the GPU does not boot. This kind of GPU dying is new to me, usually the miner detects it as DEAD somehow, or the OS crashes.
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
June 06, 2019, 07:57:55 PM |
|
Can you please add timerolling on/off option ? I can't use miner on some pools because off timerolling. Thank You.
Interesting, can you PM an example? I’m guessing this might be x16rt? Yes, I was trying to mine Veil (x16rt) on bsod pool. Some pool owners suggested to set timerolling off by default. So far, I can mine Veil only on one "small" pool with teamredminer. All other pools reject shares. We’ll fix it shortly, I would guess an update is out by tomorrow, if not sooner.
|
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
|
June 06, 2019, 10:09:26 PM |
|
Just one question. Is it better to run the SCAN autotuning with the AMD MEM TWEAK turned off? Does auto tuning eliminate AMD MEM TWEAK or is it better to use the well-known AMD mem tweak setting with autotuning?
|
|
|
|
todxx (OP)
Member
Offline
Activity: 176
Merit: 76
|
|
June 06, 2019, 11:37:16 PM |
|
Just one question. Is it better to run the SCAN autotuning with the AMD MEM TWEAK turned off? Does auto tuning eliminate AMD MEM TWEAK or is it better to use the well-known AMD mem tweak setting with autotuning?
You'll want to apply your memory timing adjustments (and voltage/clock settings) before doing the auto-tune. The auto-tune tests a number of different TRM settings, it does not change any timings/clocks/voltages on the GPUs. It's also probably a good idea to re-run the auto-tune after changing clocks or timings to make sure that the best config didn't change.
|
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
|
June 07, 2019, 01:05:55 AM |
|
Just one question. Is it better to run the SCAN autotuning with the AMD MEM TWEAK turned off? Does auto tuning eliminate AMD MEM TWEAK or is it better to use the well-known AMD mem tweak setting with autotuning?
You'll want to apply your memory timing adjustments (and voltage/clock settings) before doing the auto-tune. The auto-tune tests a number of different TRM settings, it does not change any timings/clocks/voltages on the GPUs. It's also probably a good idea to re-run the auto-tune after changing clocks or timings to make sure that the best config didn't change. thx. i test 1 rig(6*hynix CNR). before i use 15*15=11880HR 994W(11.94h/w) now quick test say 13*13:AAA=12050HR 1040W(11.58h/w). Hr is better but HR per Wat is lower Haven is GREAT. Before (srb) i have 10900HR 960W or 11300HR 1010W now TRM 12100Hr 920W
|
|
|
|
Vampire_sumy
Member
Offline
Activity: 110
Merit: 10
|
|
June 07, 2019, 06:16:20 AM |
|
Hi, do you have any plans to add cn_gpu algo into trm ?
|
|
|
|
nordmann666
Member
Offline
Activity: 363
Merit: 16
|
|
June 07, 2019, 07:08:31 AM |
|
great update...but only one rig is working...other one make some trouble
i set different voltages (560-575mv) but TRM shows 875mv on each GPU?! on the other rigs it shows me different voltages (but not the numbers i set in ODNT)
and i tried RVN - the RPC reconnect problem with suprnova - if i set the "--pool_broken_rpc" i dont get shares in tuning mode - only get shares without the "--pool_broken_rpc" (but reconnects sucks)
|
|
|
|
todxx (OP)
Member
Offline
Activity: 176
Merit: 76
|
|
June 07, 2019, 07:18:53 AM |
|
great update...but only one rig is working...other one make some trouble
i set different voltages (560-575mv) but TRM shows 875mv on each GPU?! on the other rigs it shows me different voltages (but not the numbers i set in ODNT)
and i tried RVN - the RPC reconnect problem with suprnova - if i set the "--pool_broken_rpc" i dont get shares in tuning mode - only get shares without the "--pool_broken_rpc" (but reconnects sucks)
Suprnova doesn't seem to like extra nonce subscription on its pools. Can you try again with the --pool_no_ensub option?
|
|
|
|
ALEX_RAA
Newbie
Offline
Activity: 78
Merit: 0
|
|
June 07, 2019, 12:33:02 PM |
|
it's strange situation: - win 10 1709, updates are off - pagefile 75gb - mixed rig: 5x-rx570(4gb)+3x-vega56 (ref, not flashed, sams memory)
trm 0.4.5 with my manual timings tuning: cnr 11.77kh/s (vegas gives 2230-2250) trm 0.5 with auto-tuning gives only 11kh/s (vegas gives only 1980-1950)
autotuning from trm 0.5 set for all vegas 14+14:AAA, but if i manualy change it to 14*14:AAA there is no difference
but my manual timings for vegas is from trm help file so i don't understand =]
p.s. on my other rigs all vegas works even faster with trm 0.5 and autotuning
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
June 07, 2019, 01:23:43 PM |
|
it's strange situation: - win 10 1709, updates are off - pagefile 75gb - mixed rig: 5x-rx570(4gb)+3x-vega56 (ref, not flashed, sams memory)
trm 0.4.5 with my manual timings tuning: cnr 11.77kh/s (vegas gives 2230-2250) trm 0.5 with auto-tuning gives only 11kh/s (vegas gives only 1980-1950)
autotuning from trm 0.5 set for all vegas 14+14:AAA, but if i manualy change it to 14*14:AAA there is no difference
but my manual timings for vegas is from trm help file so i don't understand =]
p.s. on my other rigs all vegas works even faster with trm 0.5 and autotuning
Wow, that sounds very strange. Do you have other ref V56s in the other rigs using the same timings? If so, what does the auto-tuning choose for those gpus?
|
|
|
|
ALEX_RAA
Newbie
Offline
Activity: 78
Merit: 0
|
|
June 07, 2019, 01:44:55 PM |
|
Wow, that sounds very strange. Do you have other ref V56s in the other rigs using the same timings? If so, what does the auto-tuning choose for those gpus?
i have other rigs with vega56 ref (sams mem) but different brends, they all use lucky timings from trm help file on one rig autotune sets 14*13:AAA and on another 14*14:AAA but all of my vegas56 (expect those x3 that i describe before) gives average 2230-2300 h/s on cnr p.s. may be i don't know it's problem from motherboard?! i have h110 asrock btc pro (13 pci-e) and celeron 2.8ghz, 4gb ram
|
|
|
|
ALEX_RAA
Newbie
Offline
Activity: 78
Merit: 0
|
|
June 07, 2019, 02:36:00 PM |
|
i'm an idiot! I thought that trm is use timings... but this auto-tune is only trm tuning. All is good for me now, just setup up timings for that rig
|
|
|
|
kerney666
Member
Offline
Activity: 658
Merit: 86
|
|
June 07, 2019, 02:40:05 PM |
|
i'm an idiot! I thought that trm is use timings... but this auto-tune is only trm tuning. All is good for me now, just setup up timings for that rig
Got it. You have my utmost respect for coming clean .
|
|
|
|
seefatlow
Jr. Member
Offline
Activity: 80
Merit: 1
|
|
June 07, 2019, 05:39:06 PM |
|
Team Red Miner v0.5.0 releasedhttps://github.com/todxx/teamredminer/releasesChanges 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.
We've added new algos for 4MB/heavy CN variants! Now you can mine haven/bittube with TRM We've also added more finetuning options, as well as built-in auto-tuning to find the best config! Kudos Todd and Kerney for releasing not just 1 algo but a whole bunch of them. You guys have truly outdone yourselves this time. BTW, I am unable to access the Github download site. It says site not found. Any ideas?
|
|
|
|
SigiSinatra
Newbie
Offline
Activity: 50
Merit: 0
|
|
June 07, 2019, 05:53:40 PM |
|
Team Red Miner v0.5.0 releasedhttps://github.com/todxx/teamredminer/releasesChanges 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.
We've added new algos for 4MB/heavy CN variants! Now you can mine haven/bittube with TRM We've also added more finetuning options, as well as built-in auto-tuning to find the best config! Kudos Todd and Kerney for releasing not just 1 algo but a whole bunch of them. You guys have truly outdone yourselves this time. BTW, I am unable to access the Github download site. It says site not found. Any ideas? Try here : https://github.com/todxx/teamredminer/releases
|
|
|
|
todxx (OP)
Member
Offline
Activity: 176
Merit: 76
|
|
June 07, 2019, 07:26:02 PM |
|
Team Red Miner v0.5.1 releasedhttps://github.com/todxx/teamredminer/releasesChanges 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.
This release addresses a few minor issues people have reported in the v0.5.0 release.
|
|
|
|
fmz89
Legendary
Offline
Activity: 1762
Merit: 1002
|
|
June 08, 2019, 01:58:47 AM |
|
V0.5 amazing , very stable on poolhash
|
|
|
|
|