 Show Posts
|
|
Pages: [1] 2 3 4 »
|
|
3
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.6.1 - Ethash/Cryptonight/Chukwa Thread
|
on: January 06, 2020, 11:56:23 PM
|
One Vega 56 referent (64 bios, samsung mem) have hardware errors:
[48C, fan 71%] ethash: 48.36Mh/s, avg 48.54Mh/s, pool 47.27Mh/s a:9112 r:0 hw:164
Any recomendations?
txs
Not all memory is the same - some can take more aggressive timings, some less. I would trim back your timings changes to a minimum set (and reduce REF), and build from there: --REF 15600 --RFC 248 --RAS 30 --RP 12 --RC 44 --RCDRD 14 This will prob get you to 99.5%+ of your list anyway. If these still don't work - try reducing REF more (try 11700), then maybe RC, then RP - those are your biggest movers. Also, are you sure you need 850mv for those settings? All of my vegas (including the flashed 56) are running 930cclk/1028mclk @ 800mv for 47.4MH/s. EDIT: Take a look at your temperatures (esp mem) on the two different cards as well. Higher mem temps cause faster charge decay requiring more frequent refreshes (i.e. lower REF). Mine do just fine w/ REF=15600, but mem temps are all in the high 50's to low 60's. txs pbfarmer! With your memtweak timings just finished test 24 hour with 0 hw errors ;-) HBM temperature is low 70's on all cards (can't do much on that, small room with no window for cooling, just one fan, and few holes for fresh air) Never tried so low mV (800), i don't have power play table for 800, is it possible to running 800 mV with ppt build for 850 mV? |
|
|
|
|
4
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.6.1 - Ethash/Cryptonight/Chukwa Thread
|
on: January 05, 2020, 04:56:48 PM
|
One Vega 56 referent (64 bios, samsung mem) have hardware errors:
[48C, fan 71%] ethash: 48.36Mh/s, avg 48.54Mh/s, pool 47.27Mh/s a:9112 r:0 hw:164
already lowered clocks and mem in Overdrive Ntool:
960/850 core and 1055/850 mem
memtweak:
--CL 20 --RAS 30 --RCDRD 14 --RCDWR 12 --RC 44 --RP 14 --RRDS 3 --RRDL 6 --RTP 5 --FAW 12 --CWL 8 --WTRS 4 --WTRL 9 --WR 14 --REF 17000 --RFC 249
Another card hash 49.1 with same memtweak and 976/850 1075/850 without hw errors.
Any recomendations?
txs
Try with 875 mV for both core and memory.... txs, but that will increase VDDC in TRM to 906 mV and power consumption go up for 20W from the wall. In all other algo, i can mine without hw errors with 850 mV with that card... |
|
|
|
|
5
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.6.1 - Ethash/Cryptonight/Chukwa Thread
|
on: January 05, 2020, 12:12:09 PM
|
|
One Vega 56 referent (64 bios, samsung mem) have hardware errors:
[48C, fan 71%] ethash: 48.36Mh/s, avg 48.54Mh/s, pool 47.27Mh/s a:9112 r:0 hw:164
already lowered clocks and mem in Overdrive Ntool:
960/850 core and 1055/850 mem
memtweak:
--CL 20 --RAS 30 --RCDRD 14 --RCDWR 12 --RC 44 --RP 14 --RRDS 3 --RRDL 6 --RTP 5 --FAW 12 --CWL 8 --WTRS 4 --WTRL 9 --WR 14 --REF 17000 --RFC 249
Another card hash 49.1 with same memtweak and 976/850 1075/850 without hw errors.
Any recomendations?
txs
|
|
|
|
|
6
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner-MULTI CPU & AMD GPU Miner 0.2.0
|
on: December 27, 2019, 09:42:36 PM
|
|
hi Doktor!
I'm back to your miner. Used to mine with GPU and SRBMiner.
Now GPU mine ETH, but i try CPU Core i3 8100 with multi randomx, (autoconfig) and have resulted with 1920 H/s on average.
Is it ok result for this cpu and algo, and is it some better profitable coin for cpu mining?
Please advice me, stuck with cryptonight algo coins for years, never look any other algo...
Keep up a good work!
txs
|
|
|
|
|
7
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.6.1 - Ethash/Cryptonight/Chukwa Thread
|
on: December 14, 2019, 07:03:24 PM
|
Hi I need to before mine, disable\enable all gpus , You mentioned this feature in version 4.4 onwards
How to activate it?
my config is:
-d 0,1,2 -o stratum+tcp://turtlecoin.herominers.com:10382 -u wallet address -p name -a trtl_chukwa --api_listen
Here is for Vega gpu put in .bat (watch out for proper path) and put devcon.exe to that folder: "C:\TEAMREDMINER\Devcon.exe" disable "PCI\VEN_1002&DEV_687F" timeout /t 3 "C:\TEAMREDMINER\Devcon.exe" enable "PCI\VEN_1002&DEV_687F" timeout /t 3 |
|
|
|
|
8
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: AMD Mem Tweak - Read/modify mem timings on the fly - [Vega Friendly] [Win/Linux]
|
on: April 17, 2019, 09:15:22 PM
|
Hi Guys,
Zorg33 said to me share this set, because it's impossible, but working good for me:
--CL 12 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 10 --RRDS 3 --RRDL 3 --RTP 5 --FAW 20 --CWL 7 --WTRS 4 --WTRL 9 --WR 16 --WRRD 1 --RDWR 19 --REF 17550 --MRD 8 --MOD 15 --PD 8 --CKSRE 10 --CKSRX 10 --RFC 250
Vega56 @ 64 sapphire samsung ram, Win10, 18.6.1 and 18.5.1 classic 1408/900core 1100/900mem
Turtle 22+
ETH 51+
Cr-Lite 10K khs (1600/990 1100/900, but crashed, 9600kh 1408/900 1100/900 super stable after 24h)
Ok, now after 16 hours of running, i can say: superb!  Reference Vega 56 (64bios) at 20.7 kh/s 1280/870 1090/900 ODT L20+20 (TRM) Asus Strix Vega 64 at 21.32 kh/s 1280/870 1090/880 ODT, L18+18 (TRM) Driver 18.6.1., GPU temp 66 C (have problem with small space for rig, so results could be even better), power for 3 Vegas + 1 RX570 from the wall 710W. |
|
|
|
|
9
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: AMD Mem Tweak - Read/modify mem timings on the fly - [Vega Friendly] [Win/Linux]
|
on: April 12, 2019, 09:36:08 PM
|
|
Here is my first test.
Driver: 18.6.1 with Dragonmike PPT (txs Mike :-))
Rig: 2x Vega56 reference (V64 bios) + 1x Vega 64 Strix + 1x RX570
Miner: TeamRedMiner 0.4.3
Core: 1280/870mV Mem: 1100/870mV (in OverdriveNtool)
Todxx settings for Vegas, with "i" selected only Vegas: --i 0,2,3 --CL 20 --RAS 33 --RCDRD 12 --RCDWR 5 --RC 44 --RP 10 --RRDS 3 --RRDL 3 --RTP 5 --FAW 16 --CWL 7 --WTRS 4 --WTRL 9 --WR 16 --WRRD 1 --RDWR 19 --REF 3900 --MRD 8 --MOD 15 --PD 8 --CKSRE 10 --CKSRX 10 --RFC 300
Same settings of the miner and Turtle/Loki mining:
Vega 56 (64 bios) from 19.2 to 20.3 hk/s ;-) L20+20
Vega 64 Asus Strix from 19.5 to 13.2 hk/s ;-( L24+24
So, for reference card work nice, but need to tune for every card...
Tested Vega 64 Strix config in miner from L18+18 to L28+28 including 20+20 etc...
Best result:
Vega 64 Asus Strix from 19.5 to 19.9 hk/s L20+20
One of the "problematic" Vega56 after 30 min running got 4 rejected share invalid result too... So I have to tune this card more...
Is there any suggestion?
Power: from 680W to 705W = 25W more for rig from the wall.
CNR same settings quick run: Vega 56 got +100 H/s.
Txs Eliovp!
|
|
|
|
|
10
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.4.3 - Cryptonight Thread - High hashrate, Low Power
|
on: April 05, 2019, 06:06:34 PM
|
I've noticed that accessing Teamviewer will crash my rig when running low clocks and high intensities. Also, I'm now using a staggered approach: I set higher clocks and voltages, start the miner, and once all cards are up and hashing, apply lower clocks. Just a little script with overdriventool on a timer. Works wonders.
Teamviewer crash my rig only on trtl. on other algo work fine.
For local network on win10 pro you should try remote desktop app. Great, simple, Microsoft app, never have problems. On android tablet I use the same app to connect on remote rig. |
|
|
|
|
11
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.4.3 - Cryptonight Thread - High hashrate, Low Power
|
on: April 02, 2019, 06:24:18 PM
|
Sorry dude, I only just saw this.
If you want to revert to 18.6.1 and try my PPT table, I'm happy to send it to you.
Just dm me your email address in that case.
I'm using reference Sapphire RX Vega 56 with 64 bios, so the ppt will reflect that.
I had SoC set to 1200 previously and that wreaked total havoc in my cards' behaviour. Always massive pain to get the cards stable, needed to increase core voltages massively and they just behaved erratically. Getting SoC back to 1107 sorted everything.
Dragonmike, PM is sent. I have another hard disk with installation of miner on win10 1709 with 18.6.1. driver (that system I used until now). So I can easily test, just boot from another disk ;-) txs |
|
|
|
|
12
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.4.3 - Cryptonight Thread - High hashrate, Low Power
|
on: April 01, 2019, 09:18:48 PM
|
Just Update win 10 pro (to last version) + driver to 19.3.2 version from 18.6.1 because no need for ppt table and read that this driver is OK. Update OverdriveNtool to last 0.28.beta 1 too.
Strange: CNR on 19.3.2 work just like on 18.6.1 driver but Turtle algo with 19.3.2 driver on Vega 56 (64 bios) or Vega 64 (Asus) drop hashrate from 18 kh/s to 10 kh/s
Did someone try turtle algo on 19.3.2?
Seems like I am not the only one. I had similar results. L28+28 gives 10-11 Khs. Try 26+26, it would work fine around 17-18.5 Khs still not as good as other folks who can get L28+28 with earlier drivers. heavyarms1912 txs! Confirmed: Asus Strix Vega 64, 26+26 on 19.3.2 driver results with 19,4 kh/s (on 18.6.1 result was about 18,5 kh/s) Reference Vega 56 (64bios), 26+26 on 19.3.2. driver 18 kh/s (on 18.6.1 result was equal) Here is test on 19.3.2 for CNR algo, after testing all configs, this is the best results with power from the wall (for rig). Testing Vega from 13+13 to 16+15 and 5+5 to 8+7 on rx570 with all combinations. EDIT: Reference Vega cards can do more, I put clock down because overheating (small space about two m2 without windows, just small holes and one small bathroom fan ;-)) ╔═════════════════════════════╦═════════╦══════╦══════╦══════════╦══════════╦════════╦════════╦═════════╗ ║ Card ║ Memory ║ Algo ║ kh/s ║ Core ║ Mem ║ Config ║ Driver ║ Power W ║ ╠═════════════════════════════╬═════════╬══════╬══════╬══════════╬══════════╬════════╬════════╬═════════╣ ║ Asus Strix Vega 64 ║ Samsung ║ CNR ║ 2210 ║ 1520/920 ║ 1100/910 ║ 16+14 ║ 19.3.2 ║ 787 ║ ╠═════════════════════════════╬═════════╬══════╬══════╬══════════╬══════════╬════════╬════════╬═════════╣ ║ Reference Vega 56 Gigabyte x 2 ║ Samsung ║ CNR ║ 1970 ║ 1408/950 ║ 1050/950 ║ 14+14 ║ 19.3.2 ║ 787 ║ ╠═════════════════════════════╬═════════╬══════╬══════╬══════════╬══════════╬════════╬════════╬═════════╣ ║ Rx570 4GB Nitro+ ║ Elpida ║ CNR ║ 940 ║ 1180/850 ║ 1980/900 ║ 7+7 ║ 19.3.2 ║ 787 ║ ╚═════════════════════════════╩═════════╩══════╩══════╩══════════╩══════════╩════════╩════════╩═════════╝ |
|
|
|
|
15
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.4.3 - Cryptonight Thread - High hashrate, Low Power
|
on: March 30, 2019, 10:40:47 PM
|
OK. I have been trying over several days to replicate the results from pbfarmer on cnv8_trtl and I can say that I am unable to get the efficiency reported by him. Any attempt to reach close to his reported voltage levels of 805mv to 840mV resulted in random DEAD GPUs(stuck in enqueue) after 20-30 minutes hashing or significant hashrate drop per GPU Even at 870mV, I am still unable to get a stable system running. Dead GPUs and hashrate drop to 15kH/s still occurs after several tens of minutes of mining. And the weird thing is hashrate drops happens to Hynix mem GPUs only.  Somehow CN-TRTL algo is more taxing that CN_R? I am able to run CN_R without failures for a week and with lower voltage settings (850mV - 870mV). I can't seem to do this for CN_TRTL My settings are as below. But the hashrates aren't sustainable GPUs : Ref Vega 64 and Vega 56 reference bios V64 cclk/memclk 1220/1100 @ 870mV L28+28 (Samsung mem) - 19.5kH/s V56 cclk/memclk 1220/940 @ 870mV L24+24 (Samsung mem) - 19.3kH/s (Hynix mem) - 18.7 kH/s ATW power draw 190W per GPU Adrenalin Driver 18.6.1 Kerney/Todd, Any ideas what could possibly be wrong? Unoptimized CN_TRTL code? That's quite weird, out of my six reference Vega56's (flashed to 64), 4 are hashing rock solid at 1408@825 core / 1107 mem and the weaker two cards get 850mV. I reckon I could potentially go even lower. Have you fiddled with your power play tables? Is your SoC set higher? That's quite typical for instability, I can sing a song or two about it... DragonMike, my SOC on reference V56 (bios V64) is 1199, i think it is becouse i use "Safe" ppt file that u/Hellea make. That is only ppt table that for some reason work stable. I want to try lower SOC to 1107. Can you (or someone) share ppt with lover SOC 1107 that work ok for reference V56 (bios changed to V64 samsung mem)? txs |
|
|
|
|
16
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.8.1 - native algo switching
|
on: March 22, 2019, 08:36:22 PM
|
I think it is v4 problem. 1.8.1 is better than 1.8.0 but still not 100% stable. It was no problem on other algos in srbminer, eth rock stable, mined beam for weaks rock stable, everything i was trowing at vegas just worked. Then it came v4 and it came problems. I just love srbminer cause it is best miner for vega cards, but when v4 cam and it was unstable, i tried other miners for v4, you have at lleast 4 of them, and they crash even faster, teamredminer crashed under 10min on same settings as srbminer. Tried to underclock gpu,mem for stability and same. Problem is only on v4, other algos are fine  Something is very bad with new algo, just put loop in bat file and it will at least run again when it crashes The whole concept of how v4 works is bad on gpu's. Compiling code on every new block, then need to release that memory, but it is known that the amd cl_release api is buggy and it wont always work as it should. For cpu's this concept of create code + compile is not a problem , but for gpu's it is. I am trying out various things, hope for the best hi doc v4 algor , designed for cpu not gpu. do you test new amd driver ? it's very good. it's work for few day just few crash .  Haha, no, i test only on 18.6.1 and blockchain. Which new version do you refer to? Radeon-Software-Adrenalin-2019-Edition-19.3.2-Mar14 you don't need soft power table . just overdriventool 0.2.8 . you can edit p0 to p7 and new fan setting. and memory timing .... I use it too with overdriventool and very good stability and more hashes than 18.6.1  U should consider look at it doktor xD Interesting. On 18.6.1 too long time here... Can you share pics of the settings on new overdriveNtool 0.2.8 without ppt? |
|
|
|
|
17
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.4.2 - Cryptonight Thread - High hashrate, Low Power
|
on: March 16, 2019, 11:21:09 PM
|
@todxx @kerney666 - i'm struggling w/ some stability issues. linux/0.4.1/cnr/15+15 on an 8x64 rig - can run fine for 1hr or 6 hrs, but seems to always fall over eventually. I'm definitely at oc/uv thresholds, but where normally I could isolate crashes to specific cards and adjust settings, in this case it's a different card every time. It's not temps (all under 45c) or hardware errors (none reported by miner or syslog.) I'm wondering if it's maybe following network hiccups or dev fee switching? Tho i can't find any messaging in the logs - any way we can get network/dev fee notices in the logs? I'm also seeing init discrepancies - tho not as bad as 0.4.0 - but sometimes random cards underperform by 10-15h/s run-to-run (was more like 40-50 on 0.4.0), so possibly something to do w/ that?
Also, tried 0.4.2, and it falls over w/in seconds for the same settings - seems much harsher on init for some reason.
When switch to CNR algo, same problem with stability. Run 2 or 8 hours but than crash (and watchdog not restart miner). I noticed that always one card is crashing (unlike you). Put 10 power more on the core 1408/960mV + lower memory to 1050 on problematic Vega 56 reference + 15+15 config solved stability problems. For that card, 15+15 is better for stability. Normaly best results reference Vega56 flashed to 64 is 14+14. Now running 1 day and 5 hours without crash. So try go up with core power with all cards... |
|
|
|
|
18
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.4.0 - CN v8/R - Vega 64 2200+h/s Rx470 1025+h/s Low Power
|
on: March 11, 2019, 06:26:04 AM
|
|
Miner failed to start over after crash:
log:
[2019-03-10 23:17:44] GPU 3: detected DEAD (03:00.0), will execute restart script start_reset_skript.bat
[2019-03-10 23:17:44] Watchdog triggering miner shutdown after restart script execution.
[2019-03-10 23:17:44] Shutting down...
[2019-03-10 23:17:44] GPU 1 CN thread 1 exiting.
[2019-03-10 23:17:44] GPU 2 CN thread 0 exiting.
[2019-03-10 23:17:44] GPU 0 CN thread 0 exiting.
[2019-03-10 23:17:45] GPU 0 CN thread 1 exiting.
[2019-03-10 23:17:45] GPU 2 CN thread 1 exiting.
[2019-03-10 23:17:45] GPU 1 CN thread 0 exiting.
[2019-03-10 23:17:54] GPU 3 thread 0 shutdown timed out.
[2019-03-10 23:17:54] GPU 3 thread 1 shutdown timed out.
Miner program is open "freezed" with this last note:
Team Red Miner version 0.4.0
[2019-03-10 23:18:22] Auto-detected AMD OpenCL platform 1
I have reset script that work just fine with Vertcoin in 0.3.10 version (disable / enable vegas with devcon, apply overdriveNtool profiles, start miner again)
Any help?
|
|
|
|
|
19
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.3.8 - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2
|
on: February 14, 2019, 08:19:05 PM
|
stupid q, but put in start.bat teamredminer.exe --help and add pause, but miner just close. No help displayed, without pause same result. What I'm doing wrong? txs Hard to say what you're doing wrong. If I put this in a .bat file in the same dir as the miner .exe, then double-click it in Windows explorer, I get the help page displayed and the expected pause: File: teamredminer.exe --help
pause
Output: ...
--log_file=FILENAME Enables logging of miner output into the file
specified by FILENAME.
--help Display this help message and exit.
C:\testing\teamredminer-v0.3.8-win>pause
Press any key to continue . . .
Can someone post results of the --help commands. Please, i still cant view results. EDIT: Solved. Problem is because i put miner on desktop folder, so .bat file ask full path to enter for some reason. When try in C: all work. Stupid... EDIT 2: And now when put full path to logfile.txt file "C:\Users\User\Desktop\....", finaly log file works also :-) |
|
|
|
|
20
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] TeamRedMiner 0.3.10 - Optimized AMD GPU Miner for lyra2rev3, lyra2z, phi2
|
on: February 10, 2019, 11:24:51 AM
|
Bloody hell it does work... Memory is shown at 500MHz (on the Vega 56's).
I'm testing on x16RT currently (which isn't very memory bound either) and I've dropped power draw massively. Hallelujah.
EDIT: on the Vegas, disabling P1 to P3 works, on the Polaris cards it won't, so I set the values of P1 and P2 equal to P0.
Hmm, for some reason, I cant disable P1 on Vega cards in ONT... What i'm doing wrong, is it because power play table or driver (use 18.6.1), or clocks? Also, try to put p0 mem to 500/800 but cant... mem: p0 167 / 800 p1 500 / 800 p2 and p3 disabled GPU: p0 to p6 disabled p7 1408 / 930 EDIT: Dragonmike, I can disable P1 P2 and P3 on Polaris (RX570 4GB Nitro+), but Vega... |
|
|
|
|
